This document discusses software requirements specification (SRS) which defines the needs of clients and users and forms the basis of software development. SRS includes functional requirements, which define the system's functionality, and non-functional requirements, which constrain the system's functions. Non-functional requirements fall into three categories: product requirements specifying system behavior; organizational requirements from development policies; and external requirements from safety and legal standards. An SRS document includes sections on introduction, general description, specific requirements, and appendices. It must specify only external system behavior, constraints on implementation, and be easy to change.
%in kempton park+277-882-255-28 abortion pills for sale in kempton park
Software engeneering
1. SOFT SKILLS AND PERSONALITY DEVELOPMENT
Topic: Software Engineering
Submitted By
MOHAMMAD AZHAR UD DIN
Roll No:13YYSB6009
2. SOFTWARE REQUIREMENT SPECIFICATION(SRS)
• Software requirements specification SRS is the starting point of software
development activity .
• Software requirements specification is the medium through which the
client and the user needs are accurately specified . SRS forms the basis of
software development . Software requirements can be classified into:
1. Functional requirements
2. Non functional requirements
3. • FUNCTIONAL REQUIREMENTS: The functional requirements of a system deals
with the functionality or services that the system is expected to provide . These
requirements depend on the type of software being developed , the expected users of
the software and the type of system being develop .
• NON-Functional Requirements: Non-functional requirements define constraints
on the function or service offered by the system . They include reliability , security ,
response time , capabilities of i/o device and data representation used in the system
interfaces .Non- functional requirements also arise due to user needs , organization
policies and due to external factors such as safety regulation and privacy legislation .
4. There Are 3 Types Of Non-functional Requirements:
1. Product requirements
2. Organizational requirements
3. External requirements
• PRODUCT REQUIREMENTS: Product requirements specify the behavior or the
characteristics of the software .
These include:
Efficiency requirements ( performance –how fast the system should execute and
memory requirements)
Reliability requirements (that sets the limits of failure rate .)
Portability requirements (deal with inter-operability with other software and
hardware systems)
Usability requirements
5. Organizational Requirements: The organizational requirements come from the policies
and procedures of the organizational developing the software product .for eg:
1. Process standards to used .
2. Implementation of programming language or design method to be used .
3. Delivery requirements specifying when the software product along with documentation
needs to delivered .
6. External Requirements: is a broad area covering all the requirements desired from
external factors of the system and development process . For eg
1. Inter-operability requirements defining the safety and privacy regulations to be followed
other organization
2. Legislation requirements defining the safety and privacy regulations to be followed to
ensure that the system operates within the law .
3. Ethical requirements ensure that the system is acceptable to its users and the general
public .
7. STRUCTURE OF S.R.S
Introduction
Purpose of the requirements document
Scope of the product
Definition , acronym and abbreviations
References
overview
General description
Product perspective
Product functions
User functions
System constraints
8. SPECIFIC SYSTEM REQUIREMENTS
Functional requirements
Non-functional requirements
External interface requirements
APPENDICES
INDEX
Section 3 of the documents is the most substantial part . Due to the wide variety in organization practices , this
section cannot have a standard structure . System requirements specification can document external interfaces ,
system function and performance , specify logical database requirements , design constraints and quality
characteristics .
9. SRS document must satisfy the following 6 requirements :
1. Specify only external system behavior
2. Specify constraints on the implementation
3. Must be easy to change
4. Serve as reference tools for system maintenance
5. Record forethought about the life cycle of the system .
6. Enumerate acceptable responses to undesired events .