Exercise #1 - Defining a Requirements Analysis Process
Defining a process can be challenging. Sometimes it hard to know where to start. In this exercise, your goal is to define some pre-determined areas that are essential to any process, but especially important for Requirements Analysis.
In this exercise, we will build on the same case study as in the last exercise.
Here is the synopsis:
A company is considering the purchase of a new customer relationship management system (CRM) to replace a variety of methods and tools that are being used across the organization. Senior management feels that a unified system would be an advantage so that information can be more easily shared across the enterprise.
New information:
There is no existing Requirements Management process in place, so although you have already started identifying business needs in a previous exercise, you have been tasked with the job of defining a basic process for eliciting, documenting, reviewing and maintaining user requirements.
The objective is to define what deliverables (i.e., the requirements specification for a selected area of the solution) will be produced and when.
The major process areas are:
Your job in this exercise is to define the following process components needed for the Identification (Recording) of Requirements:
Input - What information is needed from the stakeholders?
Output - What will be produced from this process?
Procedure - What are the steps to be followed?
Check - What is the exit criteria? What will need to be reviewed?
Tools - Will any tools be used, if so, which ones?
Techniques - Will any specific techniques be used, if so, which ones?
Standards - Which standards will be needed to be followed?
Defining a process can be challenging. Sometimes it hard to know where to start. In this exercise, your goal is to define some pre-determined areas that are essential to any process, but especially important for Requirements Analysis.
In this exercise, we will build on the same case study as in the last exercise.
Here is the synopsis:
A company is considering the purchase of a new customer relationship management system (CRM) to replace a variety of methods and tools that are being used across the organization. Senior management feels that a unified system would be an advantage so that information can be more easily shared across the enterprise.
New information:
There is no existing Requirements Management process in place, so although you have already started identifying business needs in a previous exercise, you have been tasked with the job of defining a basic process for eliciting, documenting, reviewing and maintaining user requirements.
The objective is to define what deliverables (i.e., the requirements specification for a selected area of the solution) will be produced and when.
The major process areas are:
- Identification of requirements (recording)
- Analysis of requirements
- Specification of requirements (documenting)
- Changes of requirements (tracking and updating)
- Quality assurance (ensuring adherence to process)
Your job in this exercise is to define the following process components needed for the Identification (Recording) of Requirements:
Input - What information is needed from the stakeholders?
Output - What will be produced from this process?
Procedure - What are the steps to be followed?
Check - What is the exit criteria? What will need to be reviewed?
Tools - Will any tools be used, if so, which ones?
Techniques - Will any specific techniques be used, if so, which ones?
Standards - Which standards will be needed to be followed?
Last modified: Thursday, 1 May 2014, 1:14 PM