Artifact: Stakeholder Needs

Stakeholder Needs	This artifact contains any type of requests a stakeholder (customer, end user, marketing person, and so on) might have on the system to be developed. It also contains references to any type of external sources to which the system must comply.
Worker:	System Analyst
Template:	Stakeholders Needs template
Purpose Brief Outline Timing Responsibility

Purpose

The purpose of this document is to capture all requests made on the result of the project, as well as how these requests have been addressed. Although the system analyst is responsible for this document, many people will contribute to it: marketing people, end users, customers—anyone who is considered to be a stakeholder to the result of the project.

Examples of external sources the Stakeholder Needs artifact can refer to are:

• Statement of work
• Request for proposal
• Mission statement
• Problem statement
• Business rules
• Laws and regulations
• Legacy systems
• Business models
• Any results from requirements elicitations sessions and workshops

Brief Outline

1.   Introduction
        An introduction to the document, its purpose and intended audience.

2.   Overview of the Product
        A summary of the contents of the Vision document.

3.   Functionality

   3.1   <request number one>
            A  brief description of the request. Document what decision has been made on how to address the request.

4.   Usability

   4.1   <request number one>
            A  brief description of the request. Document what decision has been made on how to address the request. 

5.   Reliability

   5.1   <request number one>
            A  brief description of the request. Document what decision has been made on how to address the request.

6.   Performance

   6.1   <request number one>
            A  brief description of the request. Document what decision has been made on how to address the request.

7.   Supportability

   7.1   <request number one>
            A  brief description of the request. Document what decision has been made on how to address the request.

8.   Business Rules and Regulations
        List references to rules and regulations to which the system needs to comply.

   8.1   <reference number one>
            A  brief description of the reference. Document what decision has been made on how to address the request.

9.   Technology Rules and Limitations
        List architecture standards, legacy systems, or any other external technology factor to which the system needs to comply.

   9.1   <reference number one>
            A  brief description of the reference. Document what decision has been made on how to address the request.

Timing

Stakeholder needs are collected during the inception and elaboration phases.

Responsibility

A system analyst is responsible for the integrity of the Stakeholder Needs document, ensuring that:

• All stakeholders have been given the opportunity to add items to this document.
• All items in this document are taken into consideration when developing detailed requirements in the use-case model and the supplementary specifications.