PRESENTATION ON REQUIREMENT AND SPECIFICATION

Presented by: Saroj Aryal Queries:

www.fb.com/sarojsaroza

ACKNOWLEDGEMENT During the design of this presentation our

group are very encouraging souls who are supporting each other in the group. We cannot stay without giving sincere thanks to each other.

We are greatful to our subject teacher Mr. Ramesh Singh Saud for playing the role of guidance and giving us such a presentation which was impossible without him.

-Presenters

OBJECTIVE Understand the concepts of user

requirements and system requirement . Understand the differences between

functional and non-functional requirements. Understand how requirements may be

organized in a software requirements documents.

CONTENTS Software Requirements

User Requirements System Requirements

Functional and Non-Functional Requirements Software Requirements Documents

SOFTWARE REQUIREMENTS Introduction: Requirements are descriptions of the services that a

software system must provide and the constraints under which it must operate. Requirements can range from high-level abstract statements

of services or system constraints to detailed mathematical functional specifications.

Requirements Engineering is the process of establishing the services that the customer requires from the system and the constraints under which it is to be developed and operated.

These requirement reflects the need of customer for a system that helps solve problem such as controlling, placing an order or finding information.

There are two types of software requirements: User Requirements System Requirements

USER REQUIREMENTS It is the statement in natural language plus

diagrams, of what services the system the system is expected to provide and constraints under which it must operate.

It is more abstract. Each and every requirement of user should

be clearly defined so the it will be easy for developer to include the user demanded feature in the software.

It may be expanded into several system requirements.

SYSTEM REQUIREMENT It is the set out the system’s functions,

services and operational constraints in detail. Every requirement for the system must be in

detail or in precise view so the it will be easy to understand the system n develop the software accordingly.

It should also define exactly what is to be implemented during the development.

In this, the contract between the system buyer and software developer is made.

User Requirement

Client Manager

System End Users

Client Engineers

Contractor Manager

System Architects

System Requirement

System End User

Client Engineer

System Architects

Software Developers

FUNCTIONAL REQUIREMENT The Functional Requirement for a system

describes what the system do. These requirement depends on the type of

software being developed. Functional System Requirement:

The functional system requirement describes the systems functions, its input and outputs, exceptions etc. in detail.

Functional system requirement vary from general requirements covering what the system should do very specific requirements reflecting local ways of working or an organization’s existing systems.

FUNCTIONAL REQUIREMENT Functional User Requirement:

The functional user requirement define specific facilities to be provided by the system.

These is taken from the user requirement document.

FUNCTIONAL REQUIREMENTS Some of the more typical functional

requirements include: Business Rules Transaction corrections, adjustments and cancellations Administrative functions Authentication Authorization levels External Interfaces Certification Requirements Reporting Requirements Historical Data Legal or Regulatory Requirements

NON-FUNCTIONAL REQUIREMENTS In simple, it describes how the system works. They are the requirements that are not directly

concerned with the specific services delivered by the system to its users.

They relate to emergent system properties such as reliability, response time storage occupancy.

Non-Functional Requirements such as performance, security or availability, usually specify constrain characteristics of the system as a whole.

It affects the overall architecture of the system rather than the individual components.

It arises through user needs, because of budget constrains, organizational policies, hardware system and others external factors.

NON FUNCTIONAL REQUIREMENTS Some typical non-functional requirements

are: Performance – for example Response Time,

Throughput. Capacity Availability Reliability Maintainability Serviceability Security Regulatory Manageability Environmental Usability

SOFTWARE REQUIREMENT DOCUMENTS The software requirement document is also

called the software requirement specification. It is an official statement of what the system

developers should implement. It should include both the user requirements

for a system and a detailed specification of a system requirements. Sometimes the user and system requirements are integrated in single description.

Requirement Documents are essential when an outside contractor is developing the software system.

CONCLUSION From this presentation we came to know about

the System requirements, User requirements. We also discussed about the Functional and Non-Functional Requirements similarly we also came to know about Software Requirement Document., which all we discussed in presentation.

Thank You..!