In this column, I use a common situation facing many requirements engineers to illustrate that "one size does not fit all" when it comes to selecting a project-specific requirements engineering process. I then recommend a metaprocess for constructing such a process based on the use of a preexisting process framework and its associated repository of reusable process components. I conclude the column with a brief discussion of some of the benefits and risks associated with this approach.
CITATION STYLE
Firesmith, D. (2004). Creating a project-specific requirements engineering process. Journal of Object Technology. Journal of Object Technology. https://doi.org/10.5381/jot.2004.3.5.c4
Mendeley helps you to discover research relevant for your work.