Comprehensive & Robust Requirements Specification Process
Comprehensive & Robust Requirements Specification Process (CRRSP)
The Comprehensive & Robust Requirements Specification Process or CRRSP(pronounced crisp) is a methodology for gathering, defining and validating software requirements. CRRSP is not a step-by-step restrictive process, but an adaptable framework, intended to be customized by the Business Analysis teams that will select the elements of the process that are appropriate for their needs.
History
CRRSP was developed in 2008, by a senior Business Analyst named Barbara Davis after years of research and refinement through hands-on experiences as a senior Business Analyst and Business Analyst Center of Excellence Practice Director with organizations such as [[UST_Global|UST Global], and Safeway.
Relationship to Other Methodolgies
The unique approach to software requirements allows for application with almost any type of project methodology and for a a flexible and adapatable starting point at which to apply the methodology. CRRSP differs from other methodologies such as Waterfall, RAD (Rapid Application Development), Agile and RUP in that it is specifically a methodology for defining and validating the requirements within the context of the larger project life cycle while these others are project methodologies that define the overall project life cycle itself.
One of the primary factors in CRRSP is that it evolves requirements through High, Mid and Low Level Requirements via an increasingly deeper dive on the requirements collateral.
Stages
The key stages in the CRRSP requirements methodology are: Research & Elicitation, Analysis, Elaboration & Specification and Validation [1]. It is characterized by the detailed validation steps, tools and techniques as well as the unique analysis deliverables and traceability products.
Research & Elicitation
The goal of the Research & Elicitation stage is to understand and research the business drivers, goals & objectives, project artifacts created to date and create workflow to help illustrate the current state and desired future state, and ultimately defines the mid-level requirements.
Analysis
In analyzing the mid-level requirements, the analyst uses Gap Assessment (which is a more detailed form of Gap Analysis) and Cause & Effect or Decision Tables to outline scenarios and further evolves the high level requirements into mid-level requirements.
Elaboration & Specification
Elaboration & Specification is simply the stage of coherently documenting and authoring the requirements document into a format that will ultimately be passed onto the design, development and testing teams to be utilized in the creation of their products and deliverables. It generates refined business rules, refined workflow schemas, and the low level requirements.
Validation
Validation uses a combination of ambiguity techniques derived from Requirements Based Testing [2] and Logic Modeling [3]. These techniques include an Ambiguity Log, Ambiuity Review and an Ambiuity Walk-through(s) involving the design, development & testing teams to establish clarity and completeness of the requirements. The reviews and walk-through(s) utilize a clear set of criteria [4] for the reviewers so that they can ensure the information is complete, consistent, and accurate, and written in language that clearly states and defines the intended functioning of the new software.
Benchmarking
Proponents of this methodology are able to apply a specialized formula which can determine the effectiveness of requirements activities by benchmarking and measuring against the established benchmark [5].
References
- ^ Barbara Davis, Requirements Networking Group, January 20,2010, "[1]", November 22, 2010
- ^ Jaideep, IT Knowledge Exchange, Mar 2, 2009, "[2]", November 22, 2010
- ^ RUSH Project, Research Utilization, May 31, 2009, "[3]", November 22, 2010
- ^ Richard Bender, Bender RBT, Date Unknown, "[4]", November 22, 2010
- ^ Barbara Davis, Requirements Networking Group, January 18,2010, "[5]", November 22, 2010
External links
- [6] Access to the CRRSP Community on Requirements Networking Group