final srs contents

8/2/2019 Final SRS Contents

1/5

1.0 Introduction1.1 Purpose

1.2 Scope

1.3 Definition, Acronyms, and Abbreviations

1.4 References1.5 Overview

2.0 Overall Description2.1 Product Perspective

2.2 Interfaces2.2.1 System Interfaces

2.2.2 User Interfaces2.2.3 Software Interfaces

2.2.4 Hardware Interface

2.2.5 Communication Interface2.3 Product Function2.4 User Characteristics2.5 Constraints

2.6 Architecture Design2.6.1 Process Model

2.7 Process Flow Diagram2.7.1 DFDs

2.8 Database Design2.8.1 ER Diagram

2.9 Use Case Diagrams

2.10 Assumptions and Dependencies


2/5

1.0 IntroductionIntroduction to current system

1. An overview of the entire SRS2. Write this document that you are telling what the system must do

3. Designers can ultimately build it

1.1 Purpose

1. Identification of purpose of Software Requirements Specification (SRS)2. Identification of intended audience for whom the SRS is designed

3. Define and describe the operations, interfaces, functional, non-functional,optional requirements of the product

4. Design constraints

5. Other factors necessary to provide a complete and comprehensive

description of the requirements for the software6. Origin of the requirements

1.2 Scope

1. Scope of SRS Topics covered2. Product Features

a. Identify the software product to be produced by name

b. Explain what the software product(s) will, and, if necessary, will not doc. Describe the application of the software being specified, including

relevant benefits, objectives, and goalsd. Should be an executive-level summary. Do not enumerate the whole

requirements list here3. Used in the future phases of the software development cycle

4. The success criteria for the system is based in the level up to which thefeatures described in this document are implemented in the system

1.3 Definition, Acronyms, and Abbreviations

1. Definitions of all terms2. Acronyms, and abbreviations required to properly interpret the SRS

3. Information can be provide in appendices if required

1.4 References

1. Provide a complete list of all documents referenced elsewhere in the SRS

(Billing System of XYZ inc., Any protocols, technology so designers knowwhere to find them)2. Identify each document by title, report number (if applicable), date, and

publishing organization3. Specify the sources from which the references can be obtained.

1.5 Overview

1. Describe what the rest of the SRS contains2. Explain how the SRS is organized

2.0 Overall Description1. Describe the general factors that affect the product and its requirements.


3/5

2. This section does not state specific requirements. Instead, it provides a

background for those requirements and makes them easier to understand.3. Tell the requirements in plain English for the consumption of the customer

not for the developers.

2.1 Product Perspective1. Type of product? (Independent, Totally self contained, part of a larger

system

2. Relation with the other products?a. Component of a larger system relates the requirements of the larger

system to functionality of the software and identifies interfaces betweenthat system and the software.

b. Independent compare its similarity and differences to other systems inthe marketplace

c. Research-oriented what related research compares to the system you

are planning to build.3. Where it will be used? (LMS Used by college to improve the efficiency of thelibrarian, staff and students.)

4. To whom it will be benefited? (The library staff and management of college.)

5. What does it provide?6. To whom it will have Interactions? (The library staff, students, lecturers,

management and visitors.)7. Interaction with other systems? (Internet, Security System, Payment

System, Inventory System, Accounting System)8. Block Diagram of the product (To provide the context)

9. Major components of the larger system, interconnections, and external

interfaces10. Block Diagram of the product, interconnections, and external

interfaces

2.2 Interfaces

2.2.1 System Interfaces

1. External systems that you have to interact with

2. Identify the functionality of the software to accomplish the systemrequirement and the interface description to match the system

2.2.2 User Interfaces

1. Description of how the system will interact with its users (GUI, CommandLine, Biometric Device, Punch Card, Touch Screen or some other type of

interface)2. The logical characteristics of each interface between the software product

and its users.3. All the aspects of optimizing the interface with the person who must use the

system4. Are there special interface requirements? (General and in case of

disabilities)


4/5

2.2.3 Software Interfaces

1. Specify the use of other required software products and interfaces withother application systems. For each required software product, include:

a. Name

b. Mnemonic

c. Specification numberd. Version numbere. Source

(IBM DB2 9.7)2. For each interface, provide:

a. Discussion of the purpose of the interfacing software as relatedto this software product. (DB2 as Database component)

b. Definition of the interface in terms of message content andformat. (Data Definitions, Tables)

A key point to remember is that you do NOT want to specify software here that

you think would be good to use. This is only for customer-specified systemsthat you have to interact with. Choosing DB2 as a DB without a customerrequirement is a Design choice, not a requirement. This is a subtle but importantpoint to writing good requirements and not over-constraining the design.

2.2.4 Hardware Interfaces

1. Logical characteristics of each interface between the software product andthe hardware components of the system.

2. This includes configuration characteristics.3. What devices are to be supported, how they are to be supported and

protocols.

4. This is not a description of hardware requirements for the product.5. Detailing the actual hardware devices your application will interact with and

control.

2.2.5 Communication Interfaces

1. Specify the various interfaces to communications (Local network protocolsetc.)

2. If you are using a custom protocol to communicate between systems, then

document that protocol here so designers know what to design.3. If it is a standard protocol, you can reference an existing document or RFC.

2.3 Product Function

1. Summary of the major functions that the software will perform2. The higher-level specification (if one exists) that allocates particular

functions to the software product.3. The functions should be organized in a way that makes the list of functions

understandable to the customer or to anyone else reading the document forthe first time. (Language form)

4. Textual or graphic methods can be used to show the different functions andtheir relationships. Such a diagram is not intended to show a design of a

product but simply shows the logical relationships among variables.


5/5

2.4 User Characteristics1. General characteristics of the intended users of the product. (Educational

level, experience, and technical expertise)

2. No specific requirements

2.5.1 Constraints1. Provide a general description of any other items that will limit the

developer's options.2. Regulatory policies

3. Hardware limitations4. Interface to other applications

5. Parallel operation6. Audit functions

7. Control functions

8. Higher-order language requirements9. Protocols10. Reliability requirements11. Criticality of the application

12. Safety and security considerations

2.5.2 Assumptions and Dependencies1. Factors that affect the requirements stated in the SRS.

2. These factors are not design constraints on the software but are, rather, anychanges to them that can affect the requirements in the SRS.

final srs contents

Documents