Software Requirements

CHAPTER III

Learning Outcomes
Basic terminology in software requirements. Product vision and project scope document. Difference between functional and non functional requirements. (NFRs). Types of NFRs. Requirements engineering process steps. Techniques for requirements elicitation.

COMPUTER ERA
Development of a use case model. Validation of software requirements. IEEE standard for writing a software requirements specification documents.

Software Analysis
What the software under development is supposed to do. Defining the scope of the software to be developed. Capturing and documenting its users requirements. Knowing the various constraints that have to be met. Understanding the interfaces with external systems, entities and users.

Product Vision and Project Scope

Document facilitates in establishing the business requirements and aligning them with the software requirements specification (SRSs).

Three main sections

1. Business requirements and context. 2. Product vision. 3. Project scope and limitations.

Requirements Engineering

Is a subset of software engineering that deals with the use of sound techniques for the development and management of software requirements.

Requirements development includes four main steps:

1. 2. 3. 4. Elicitation Analysis Specification Maintenance

Elicitation of Functional Requirements

Elicitation: is a crucial step toward obtaining effective software requirements. It results in clearly understanding and learning the needs of software users and then communicating those needs to the software developers.

Process of Elicitation
Extraction Discovery or invention Acquisition or elaboration of the stakeholders. Persons performing the elicitation step: System Analyst Business Analyst Requirement Engineer

Developer

Analyst

Software requirements specifications

Non Functional requirements

Product vision and project scope

Software Analysis

Analysis Model

Functional Requirements

Client

User

Elicitation Techniques
Interviews or questionnaires Task analysis and scenarios Preliminary requirements domain analysis Brainstorming Workshops, meetings and/or observations Practicing Prototyping

Interviewing Technique
Is an informal technique that is used at the beginning of the elicitation process to engage the various participants.

Questionnaire Technique
Is also used at the of the elicitation process to poll the participants and stakeholders and to obtain their thoughts on issues related to the system. The question should have to be clear, concise and appropriate to the issues of the project.

Task Analysis Technique

Based on the identification of the uses of the system and the description of the interactions between the users and the system.

Preliminary Requirements

Initial set of requirements. Proposed by the expert requirements engineer and are passed to the various stakeholders for discussion.

Group Meetings
That include all participants and stakeholders are also useful to start the elicitation process. Cohesiveness, openness and transparency are key to communications features during group meetings.

Brainstorming sessions
Informal meetings in which stakeholders meet and discuss the various desirable functionalities and services to be offered by the system. The meetings are not meant to make decisions or discuss the feasibility of the ideas proposed.

Elicitation of Non Functional Requirements

Related to the quality aspects of the system being developed or the functionalities provided by the system.

Template Provided By

www.animationfactory.com
500,000 Downloadable PowerPoint Templates, Animated Clip Art, Backgrounds and Videos