P. 1
Final SRS Contents

Final SRS Contents

|Views: 14|Likes:
Published by Surabhi Gupta

More info:

Published by: Surabhi Gupta on May 02, 2012
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOCX, PDF, TXT or read online from Scribd
See more
See less





1.0 Introduction 1.1 Purpose 1.2 Scope 1.3 Definition, Acronyms, and Abbreviations 1.4 References 1.5 Overview 2.0 Overall Description 2.1 Product Perspective 2.2 Interfaces 2.2.

1 System Interfaces 2.2.2 User Interfaces 2.2.3 Software Interfaces 2.2.4 Hardware Interface 2.2.5 Communication Interface 2.3 Product Function 2.4 User Characteristics 2.5 Constraints 2.6 Architecture Design 2.6.1 Process Model 2.7 Process Flow Diagram 2.7.1 DFDs 2.8 Database Design 2.8.1 ER Diagram 2.9 Use Case Diagrams 2.10 Assumptions and Dependencies

Define and describe the operations. Other factors necessary to provide a complete and comprehensive description of the requirements for the software 6.3 Definition.2 Scope 1.. 1. Explain how the SRS is organized 2. and goals d. date. Any protocols. Definitions of all terms 2. . Product Features a. and Abbreviations 1. objectives. Explain what the software product(s) will. Scope of SRS – Topics covered 2.4 References 1. Provide a complete list of all documents referenced elsewhere in the SRS (Billing System of XYZ inc. Identify each document by title.0 Overall Description 1. non-functional. Information can be provide in appendices if required 1. optional requirements of the product 4. Do not enumerate the whole requirements list here 3.0 Introduction Introduction to current system 1. Describe the general factors that affect the product and its requirements. Identification of purpose of Software Requirements Specification (SRS) 2. report number (if applicable). Acronyms. Origin of the requirements 1. Should be an executive-level summary.5 Overview 1. Identification of intended audience for whom the SRS is designed 3. Describe what the rest of the SRS contains 2. Designers can ultimately build it 1. and abbreviations required to properly interpret the SRS 3. Used in the future phases of the software development cycle 4. An overview of the entire SRS 2. Design constraints 5. and. The success criteria for the system is based in the level up to which the features described in this document are implemented in the system 1. will not do c.1. including relevant benefits. interfaces. if necessary. functional. Identify the software product to be produced by name b. technology so designers know where to find them) 2. and publishing organization 3.1 Purpose 1. Specify the sources from which the references can be obtained. Write this document that you are telling what the system must do 3. Acronyms. Describe the application of the software being specified.

Are there special interface requirements? (General and in case of disabilities) . interconnections.2 Interfaces 2.2 User Interfaces 1. Touch Screen or some other type of interface) 2. To whom it will have Interactions? (The library staff.) 5. Interaction with other systems? (Internet.1 System Interfaces 1. management and visitors. Major components of the larger system. 2. Accounting System) 8. lecturers. Where it will be used? (LMS Used by college to improve the efficiency of the librarian. Description of how the system will interact with its users (GUI. interconnections. To whom it will be benefited? (The library staff and management of college.) 4. Independent – compare its similarity and differences to other systems in the marketplace c. 3.2. Tell the requirements in plain English for the consumption of the customer not for the developers. External systems that you have to interact with 2. it provides a background for those requirements and makes them easier to understand. Block Diagram of the product – (To provide the context) 9. Type of product? (Independent.) 7. Biometric Device. students. Relation with the other products? a. The logical characteristics of each interface between the software product and its users. Identify the functionality of the software to accomplish the system requirement and the interface description to match the system 2. Component of a larger system – relates the requirements of the larger system to functionality of the software and identifies interfaces between that system and the software.1 Product Perspective 1.2. and external interfaces 2. Inventory System. Payment System. 3. Research-oriented – what related research compares to the system you are planning to build. This section does not state specific requirements. part of a larger system 2. All the aspects of optimizing the interface with the person who must use the system 4. Instead. What does it provide? 6. Security System. and external interfaces 10. Command Line. staff and students. Block Diagram of the product. 3. Punch Card. b. Totally self contained.2.

Tables) A key point to remember is that you do NOT want to specify software here that you think would be good to use. include: a. 5. This is only for customer-specified systems that you have to interact with. 2. 4. Logical characteristics of each interface between the software product and the hardware components of the system. 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 for the first time. This is not a description of hardware requirements for the product. The higher-level specification (if one exists) that allocates particular functions to the software product.) 2.7) 2. then document that protocol here so designers know what to design.2. If it is a standard protocol. Choosing DB2 as a DB without a customer requirement is a Design choice. Detailing the actual hardware devices your application will interact with and control.5 Communication Interfaces 1. Such a diagram is not intended to show a design of a product but simply shows the logical relationships among variables. (Language form) 4. you can reference an existing document or RFC. If you are using a custom protocol to communicate between systems. 3. 2. . Source (IBM DB2 9. This includes configuration characteristics. For each interface. What devices are to be supported.3 Product Function 1. Discussion of the purpose of the interfacing software as related to this software product. Summary of the major functions that the software will perform 2. Textual or graphic methods can be used to show the different functions and their relationships. Specify the use of other required software products and interfaces with other application systems. 3. Definition of the interface in terms of message content and format. not a requirement. Version number e. Specification number d. Mnemonic c.3 Software Interfaces 1. 3. (Data Definitions.2. 2.4 Hardware Interfaces 1. For each required software product. provide: a. how they are to be supported and protocols. Name b. 2.2. (DB2 as Database component) b. Specify the various interfaces to communications (Local network protocols etc. This is a subtle but important point to writing good requirements and not over-constraining the design.2.

4 User Characteristics 1. and technical expertise) 2. rather.5. 2. Parallel operation 6. .5. Interface to other applications 5. (Educational level. Audit functions 7.1 Constraints 1. Hardware limitations 4. Higher-order language requirements 9. Control functions 8. General characteristics of the intended users of the product. Criticality of the application 12. No specific requirements 2. 2. any changes to them that can affect the requirements in the SRS. Protocols 10. Factors that affect the requirements stated in the SRS.2 Assumptions and Dependencies 1.2. Safety and security considerations 2. Provide a general description of any other items that will limit the developer's options. experience. Regulatory policies 3. Reliability requirements 11. These factors are not design constraints on the software but are.

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->