Let's start by discussing requirements as a discipline performed in the context of a software application development process such as the Rational Unified Process (RUP) -- just to name one as a common reference. A documented, repeatable process such as Rational Unified Process places structure around the activities performed and the resulting artifacts, also known as deliverables. Related to the analyst's role, RUP includes the following...
Requirements discipline artifacts
Now let's focus specifically on the activities and resulting artifacts of the requirements discipline -- again using Rational Unified Process as a common frame of reference:
|Activity||Description||Key resulting artifacts|
|Analyze the problem||Capture a common vocabulary, develop vision, identify end-user classes, and develop requirements management plan.|
|Understand stakeholder needs||Capture a common vocabulary, develop vision, elicit stakeholder requests, identify end users and manage dependencies.||
|Define the system||Develop vision, capture a common vocabulary, identify end users and manage dependencies.|
|Manage the scope||Develop vision, manage dependencies and prioritize user goals.|
|Refine the system definition||Detail user goals and detail software requirements.|
|Manage changing requirements||Review requirements, manage dependencies and structure user goal modeling.|
The requirement artifacts as key inputs
The artifacts resulting from the requirements discipline are inputs to the activities for the subsequent disciplines (for example, analysis and design) in the project lifecycle as shown in Figure 1. Within each of these subsequent disciplines are their respective activities and resulting artifacts.
FIGURE 1: Rational Unified Process discipline relationships
There are numerous artifacts (deliverables) that follow the software requirements specification. That is, the software requirements specification is a key input to multiple activities and resulting artifacts within an application development process. A short list of examples of resulting artifacts from activities performed in disciplines that follow the requirements discipline is included in the table that follows. Each organization should define their application development process, which includes defined roles, activities and artifacts. The process should also indicate relationships between the roles and activities that span across each discipline in order to understand the order that activities are performed.
|Discipline following requirements||Example RUP resulting artifacts|
|Analysis and design|
|Configuration and change management|
Dig deeper on Penetration Testing
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.