Softwa e Requirements Specifications Document S360 Software Requirements Specification (SRS) Decumert The document in shis file is an annotated outline for specifying software req tirements, adapted from the IEEE Guide to Software Requirements Specifications (Std 830.1993). Rasler, Habegger, Packer Page 1 of 20 on26i6Software Requirements Specifications Document 360 Habegger, Parker, Rasler Egg Jan Communicator Software Requirements Specification Do:ument Version: (n) Date: (mm/dd/yyyy) Rasler, Habegger, Pasker Page 2 of 20 or26i6Software Requirements Specifications Document Tabie of Contents 2+ Intoduction Ld Pupose 1.2 Scope 1.3 Definitions, Acronyms, and Abbreviasions 1A References 1S uverviow 2 The Iverall Description 1.1 System Imerfaces 1.2 laterfaces 13 Hadware Inerfaces 1.3 Sofiwaze Interfaces 1.5 Cousmmun:cations Luterfaces 1.6 Memory Coustraints perations 2.118 Site Adaptation Requirements 2.2 Product Functions 2.3 User Characteristics 24 Constraints 2.5 assumptions and Dependencies 2d Apportioning of Requirements 3. Specific Requirements E ternal interfaces 3.2 Functions 4.3 Performance Requirements 4.4 Logical Database Requirements 3.5 Design Constraints 4.5.1 Standards Compliance 3.6 Software System Atiributes 3.6.1 xeliability 3.62 Ar aiability 3.63 Securit 3.644 Maintainability 3.65 Forability Organizing the Specific Requirements 1 System Mode 3.7.2 User Class Rasler, Habegger, Parker Page 3 of 20 or26i6 5 R 2 B 4 M4 1s 16 16 16 16 Is a v7 r 1g Is3.7.3 Objects 3.7.4 Feature 7.5 Stimulus 3.7.6 Response 3.7.7 Functional Hierarchy 4.8 Additional Comments 4. Change Management Process 5, Document Approvals 6. Supporting information Rasler, Habegger, Parker Software Requirements Specifications Document Page 4 of 20 or26i6 19 19 9 19 19 19 2»Software Requirements Specifications Document 1. Introduction The fol’owing subsections of tae Software Reuirements Specifications {SRS) outlines the prrpose of .his document in zelation to che groduct specified: The Egg Jam Communicator (EIC). 1.1 Ferpose The purpose of this Software Requirements Specifications document is to list and detail the requirements inherent in the construction and maintenance of the Egg Jam Communicator It is intended for the use of the client to verify that all required specifications for the EIC have been listed and considered. Further, the SRS will be used by the development team to ensure that all required design parameters are incorporated into the final product 1.2 Scope Software product to be produced: Software aspect of the Egg Jam Communicator Creation of a system that mechanizes the process of determining when and where a chicken egg flow problem (egg jam) occurs on a system of conveyors through the chicken egg packaging process. Mechanical units will be installed along separate conveyors to track the flow of eggs down that specific conveyor, these units will report to a software program designed to determine if the flow is normal or abnormal. In the case of abnormal flow, the system should alert the user in real-time as to which specific line the problem has occurred on. In actual use, thousands of feet of conveyor lines would need to searched manually in the instance of a jam, this system would minimize the searching, thus minimizing the labor cost needed to fix the problem. Also the system eliminates unnecessary loss in performance, by alerting a user even when the packaging system is not in use. EJC: Egg Jam Communicator UART: Universal Asynchronous Reciever/Transmitter BS2P40: BASIC stamp 2p 40-pin microcontroller module CAT-S: Serial twisted pair category 5 RJ45 style cabling 1.4 References In this subsection: (1) Provide a compiete list of ail documents referenced etsewnere i te SRS Rasler, Habegger, Parker Page § of 20 or26i6Software Requirements Specifications Document (2) Identify each document by publishing organization (3) Specify the sources from which the references can be obtained. title, report number (‘f applicable), date, and This information can be provided by reference to an appendiz or to another document. If your application uses specific protocols or RFC’, then reference them here so designers know where to find them. Over This document is segmented in such a way that the scope of the primary sections 1-2 is most suitable for those not involved in the construction of the Egg Jam Communicator. The primary section 3 is most suitable for those involved in the construction of the software. 2. The Overall Desc: 2.1 Product Perspective This product is being created in an environment with the following already established requisites: A production line is already established with individual conveyors fed from lines of chicken coops into primary Lines that feed into the packaging area, and a windows PC with touch screen exists at the user-operated packaging area A preexisting product already established at the intended location is best described as a mechanical sorting device that uses optical recognition and software to remove specific sized eggs from the conveyor. The mechanized solution being elaborated upon in this document will work, and be implemented along side this preexisiting system. Put the product into perspective with other related products. Ifthe product is independent and totally self-contained, it should be so stated here. If the SRS defines a product that is a component of a larger system, as frequently occurs, then this subsection relates the requirements of the larger system to functionality of the software and identifies interfaces between that system and the software. If vou are building a real system, compare its similarity and differences to other systems in the marketplace. If vou are doing a research-oriented project, what related research compares to the system you are planning to build. A block diagram showing the major components of the larger system, imterconmections, and external interfaces can be helpful. This is not a design or architecture picture. It is more to provide context, especially if your system will interact with external actors. The system you are building should be shown as a blacs box. Let the design document present the internals The following subsections describe how the software operates inside various constraints. Rasler, Habegger, Parker Page 6 of 20 or26i6Software Requirements Specifications Document 2.1.1 System Interfaces List each system interface and idemify the functionality of the software to accomplish the system requirement and the interface description to match the system. These are external systems that you have to interact with. For instance, ifyou are building a business application that interfaces with the existing employee payroll system, what is the API 10 that system that designer's will need to use? This software system must interface with an existing system that detects egg size and removes eggs that are too large for packing. The two systems will share theexisting touch sereen GUI; menu options to access alarms indicated by the EJC will be incorporated into the GUL Likewise, the sensor system must be integrated into the existing conveyor system. These will be installed according to specifications made by the client. 2.1.2 Interfaces A preexisting interface exists for the mechanized egg sorting device. The Egg Jam Communicator will necessarily be integreated into this preexisting interface. The interface includes a GUI developed specific for a preexisting touch screen for user input and display. The touch screen input will drive the user adjustable parameters, alert toggles, and so on. ‘The GUL aspect specific for this application should allow easily adjustable parameters, and should provide a viewable Specifi: (1) The logical characteristics of each interface between the software product and its users: (2) All the aspects of optimizing the interface with the person who must use the system This is a description of how the system will interact with its users. Is there a GUI, a command line or some other type of interface? Are there special interface requirements? Ifyou are designing for the general student population for instance, what is the impact of ADA (American with Disabilities Act) on your interface? 2.1.3 Hardware Interfaces Mechanical counter devices should be installed on the conveyor in such a way as to gauge the flow rate of that particular conveyor belt. These sensors communicate with a conveyor specific microcontroller(BS2P40), and utilizing a UART to communicate via serial lines, these serial transmissions should be converted to a USB specified Rasler, Habegger, Parker Page 7 of 20 or26i6Software Requirements Specifications Document transmission. This USB transmission will interface with a preexisting PC that should interpret and drive the communication of the whole system. Specify the logical characteristics of each interface between the software product and the hardware components of the system. This inchides configuration characteristics. It also covers such matters as what devices are to be supported, how they are to be supported and protocols. This is not a description of hardware requirements in the sense that “Zhis program must run on a Mac with 64M of RAM”. This section is for detailing the actud hardware devices your application will interact with and control. For instance, if vou are controlling Xi" type home devices, what is the interface to those devices? Designers should be able to look at this and know what hardware they need to worry about in the design. Many business type applications will have no hardware interfaces. If none, just state “The system has no hardware interface requirements” If vou just delete sections that are not applicable, then readers do not know if- a. this does not apply or b. you forgot to include the section in the first place. 2.1.4 Software Interfaces 2.1.4.1 Software Interface of BS2P40: The Sponsor specific microcontrollers require PBASIC to communicate serially with the UARTS. 2.1.4.2 Software Interface of the primary program: The primary program will handle communication to the UARTs. This level of communication should be programmed for the Windows Environment, The communication data should interface with software that knows the state of each conveyor, utilizing algorithms to determine if an alert or response is necessary. This level of the software interfaces with a GUI, making alerts as necessary, and describing the status of the conveyors. The preexisting touch screen should offer the user the ability to modify intemal settings of the software, specifically including the ability to modify sensitivity settings and alert settings Specify the use of other required software products and interfaces with other application systems. For each required software product, include: (1) Name (2) Mnemonic (3) Specification number (4) Version number (3) Source For each interface, provide. Rasler, Habegger, Parker Page 8 of 20 or26i6Software Requirements Specifications Document (1) Discussion of the purpose of the interfacing software as related to this software product (2) Definition of the interface in terms of message content and format Here we document the APIs, versions of software that we do not have to write, but that our system has to use. For instance if your customer uses SOL Server 7 and you are required to use that, then you need to specifi ie 2.1.4.1 Microsoft SOL Server /. The system must use SOL Server as its database component. Conimunication with the DB is through ODBE connections. The system must provide SQL data table definintions to be provided to the company DBA for setup. d 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 eustomer-spe ified systems that you have 10 interact with. Choosing SOL Server 7 as a DB without a customer requirement is a Design choice, not a requirement. This is a subtle but important point to writing good requirements and not over-constraining the design. 2.1.5 Communications Interfaces 2.1.5.1 Communication Interface for UART to primary program software: The commuciation to the UARTs to the PC will be established after the purchase of the chips, the specific chip will determine the protocol necessary, and may come prepackaged with the chip. The data will be transmitted over Cat-5 serial cable. 2.1.5.2 Communication Interface from UARTs to BS2P40: These two components will communicate at the hardware level as specified by the microcontroller and UART choosen. 2.1.5.3 Communication Interface from BS2P40 to conveyor positioned egg detector: These two components will communicate at the hardware level as specified by the microcontroller. Specify the various interfaces to commuications such as local network protocols, ete. These are protocols you will need to directly interact with. Ifyou happen to use web services transparently to your application then do not list it here. If you are using a custom protocol to communicate between systems, then document that protocol here so designers know what to design. Ifit is a standard protocol, you can reference an existing document or RFC. 2.1.6 Memory Constraints Rasler, Habegger, Parker Page 9 of 20 or26i6Software Requirements Specifications Document This systems memory requirements will not exceed the memory allowance of the preexisting system. Specify any applicable characteristics and limits on primary and secondary memory Don't just make up something here. If all the customer's machines have only 128K of RAM, then your target design has got to come in under 128K so there is an actual requirement. You could also cite market research here for shrink-wrap type applications “Focus groups have determined that our target market has setween 256-512M of RAM, therefore the design footprint should not exceed 256M.” If there are no memory constraints, so state 2.1.7 Operations Specify the normal and special operations required by the user such as (1) The various modes of operations in the user organization (2) Periods of interactive operations and periods of unattended operations (3) Data processing support functions (4) Backup and recovery operations (Note: This is sometimes specified as part of the User Interfaces section.) If'vou separate this from the UL stuff earlier, then cover business process type stuff that would impact the design. For instance, if the company brings all their systems down at midnight for data backup that might impact the design. These are all the work tasks that impact the design of an application, but which might not be located in software. In this section: (L) Define the requirements for any data or initialization sequences that are specific 10 a given site, mission, or operational mode (2) Specify the site or mission-related features that should be modified to adapt the software to a particular installation Ifany modifications to the customer's work area would be required by your system, then document that here. For instance, "1 100Kw backup generator and 10000 BTU air conditioning system must be installed at the user site prior to software installation” This could also be software-specific like, “New data tables created for this system must be installed on the company’s existing DB server and populated prior to system activation.” Any equipment the customer would need to buy or any software setup that needs to be done so that your system will install and operate correctly should be documented here. 2.2 Product Functions Rasler, Habegger, Parker Page 10 0220 or26i6Software Requirements Specifications Document Provide a summary of the major functions that the software will perform. Sometimes the function summary that is necessary for this part can be taken directly from the section of the higher-level specification (if one exists) that allocates particular functions to the software product. For clarity. (1) 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. (2) Textual or graphic methods can be used to show the different functions and their relationships. Such a diagram is not intended to show a design of a product but simply shows the logical relationships among variables. AH, Finalty the real meat of section 2. This describes the functionality of the system in the language of the customer. What specifically does the system that will be designed have to do? Drawings are good, but remember this isa description of what the system needs to do, not how you are going to build it. (That comes in the design document) 2.3 User Characteristics Describe those general characteristics of the intended users of the product including educational level, experience, and technical expertise. Do not state specific requirements but rather provide the reasons why certain specific requirements are later specified in section 3. What is it about your potential user base that will impact the design? Their experience and comfort with technology will drive UL design. Uther characteristics might actually influence internal design of the system. 2.4 Constraints Provide a general description of any other items that will limit the developer's options. These can include: () Regulatory policies (2) Hardware limitations (for example, signal timing requirements) (3) Interface to other applications (4) Parallel operation (3) Audit functions (6) Conirol functions (7) Higher-order language requirements (8) Signal handshake protocols (for example, XON-XOFF, ACK-NACK) (9) Reliability requirements (10) Criticaiity of the application (LD) Safety and security considerations Rasler, Habegger, Parker Page 11 of 20 or26i6Software Requirements Specifications Document This section captures non-functional requirements in the customers language. A more formal presentation of these will occur in section 3. 2.5 Assumptions and Dependencies List each of the factors that affect the requirements stated in the SRS. These factors are not design constraints on the software but are, rather, any changes to them that can affect the requirements in the SRS. For example, an assumption might be that a specific operating system would be available on the hardware designated for the sofware product. If. in fact, the operating system were not available, the SRS would then have to change accordingly. This section is catch-all for everything else that might influence the design of the system and that did not fit in any of the categories above. 2.6 Apportioning of Requirements. Identify requirements that may be delayed until future versions of the system. Affer you ook at the project plan and hours available, you may realize that you just camot get everything done. This section divides the requirements into different sections for development and delivery. Remember to check with the customer ~ they should prioritize the requirements and decide what does and does not get done. This can also be useful if you are using an iterative life cycle model to specify which requirements will map to which interation. 3. Specific Requirements This section contains all the software requirements at a level of detail sufficient to enable designers 10 design a system to satisfy those requirements, and testers to test that the system satisfies those requirements. Throughout this section, every stated requirement should be externally perceivable by users, operators, or other external systems. These requirements should include at a minimum a description of every input (stimulus) into the system, every output (response) from the system and all functions performed by the system in response to an input or in support of an output. The following principles apply: (1) Specific requirements should be stated with ail the characteristics of a good SRS correct unambiguous complete consistent ranked for importance and/or stability verifiable modifiable © traceable (2) Specific requirements should be cross-referenced 10 earlier documents that relate Rasler, Habegger, Parker Page 12 of 20 or26i6Software Requirements Specifications Document (3) All requirements should be uniquely identifiable (usually via munbering like 3.1.2.3) (4) Careful attention should be given to organizing the requirements to maximize readability (Several alternative organizations are given at end of document) Before examining specific ways of organizing the requirements it is helpful to understand the various items that comprise requirements as described in the following subclasses. This section reiterates section 2, but is for developers not the customer. The customer buys in with section 2, the designers use section 3 to design and build the actual application. Remember this is not design. Do not require specific software packages, etc unless the customer specifically requires them. Avoid over-consiraining your design. Use proper terminology The system shall... A required, must have feature The system should... A desired feature, but may be deferred til later The system may... An optional, nice-to-have feature that may never make it 10 implementation. Each requirement should be uniquely identified for traceability. Usually, they are numbered 3.1, 3.1.1, 3.1.2.1 etc. Each requirement should also be testable. Avoid imprecise statements like, “The system shail be easy to use” Well no xidding, what does that mean? Avoid “motherhood and apple pie” type statements, “The system shall be developed using good software engineering practice” Avoid examples, This is a specification, a designer should be able to read this spec and build the system without bothering the customer again. Don't say things like, “The system shall accept configuration information such as name and address.” The designer doesn't know if that is the only two data elements or if there are 200. List every piece of information that is required so the designers can build the right UI and data tables. 3.1 External interfaces This contains a detailed description of all inputs into and outputs from the software system. It complements the interface descriptions in section 2 but does not repeat information there. Remember section 2 presents information oriented to the customer/user while section 3 is oriented to the developer. It contains both content and format as follows: Name of item Description of purpose Source of input or destination of output Valid range, accuracy andor tolerance Units of measure Rasler, Habegger, Parker Page 13 of 20 or26i6Software Requirements Specifications Document Timing Relationships to other inputs/outputs Screen formats/organization Window formats/organization Data formats Command formats End messages 3.2 Functions 3.2.1. Presentation Layer 3.2.1.1 Display current state of conveyors 1.2 Alert when state is inappropriate 1.3 User interface adjustable parameters for sensitivity settings, ete. 1.4 Operate on Windows platform 1.5 Integrate touch screen capabilities . Communication Layer 3.2.2.1 Set up software on components for communication 2 Integrate serial communication into Application 3.2.3 Business Layer 3.2.3.1 GUI diiver for presentation layer 3.2.3.2 Communicate between persistence layer and presentation layer for settings, state, etc. 3.2.3.3 Bridge between high level software and low level communication software 3.2.3.4 Main driving software application 3.2.4, Persistence Layer 3.2.4.1 Log files for debugging 3.2.4.2 Settings files . Hardware Layer 3.2.5.1 Install hardware counters Install communication lines 5.3 Install communication controllers A Integrate into already built workstation 3.3 Performance Requirements Rasler, Habegger, Parker Page 14 of 20 or26i6Software Requirements Specifications Document This subsection specifies both the static and the dynamic numerical requirements placed on the software or on human interaction with the software, as a whole. Static numerical requirements may include: (a) The munber of terminals to be supported (b) The number of simultaneous users to be supported (©) Amount and type of information to be handled Static numerical requirements are sometimes identified under a separate section entitled capacity Dynamic numerical requirements may include, for example, the numbers of transactions and tasks and the amount of data to be processed within certain time periods for both normal and peak workload conditions. All of these requirements should be stated in measurable terms. For example, 95% of the transactions shall be processed in less than I second rather than, An operator shall not heave to wait for the transaction fo complete. (Note: Numerical limits applied to one specific finction are normally specified as part of the processing subparagraph description of that function.) 3.4 Logical Database Requirements This section specifies the logical requirements for any information that is to be placed into a database. This may include. Types of information used by various functions Frequency of use Accessing capabilities Data entities and their relationships Imegrity constrains Data retention requirements Ifthe customer provided you with data models, those can be presented here. ER diagrams (or static class diagrams) can be useful here to show complex data relationships. Remember a diagram is worth a thousand words of confusing text Rasler, Habegger, Parker Page 1S of 20 or26i6Software Requirements Specifications Document 3.5 Design Constraints Specifir design constraints that can be imposed by other standards, hardware limitations, exe. 3.5.1 Standards Compliance Specify the requirements derived from existing standards or regulations. They might include. (D) Report format (2) Data naming (3) Accounting procedures (4) Audit Tracing For exanple, this could specify the requirement for software to trace processing activity Such traces are needed for some applications to meet mininum regulatory or financial standards. An audit trace requirement may, for example, state that all changes to a payroll database nust be recorded in a trace file with before and after values 3.6 Software System Attributes There are a number of attributes of software that can serve as requirements. Itis important that required attributes by specified so that their achievement can be objectively verified. The following items provide a partial list of examples. These are also known as non-functional requirements or quallity attributes. These are characteristics the system must possess, but that pervade (or cross-cut) the design. These requirements have to be testable just like the functional requirements. Its easy to start philosophizing here, but keep it specific. 3.6.1 Reliability Specify the factors required to establish the required reliability of the software system at time of delivery. Ifyou have MIBF requirements, express them here. “his doesn't refer to just having a program that does not crash. This has a specific engineering meaning. 3.6, Specify the factors required to guarantee a defined availability level for the entire system such as checkpoint, recovery, and restart. This is somewhat related to reliability. Some systems run only infrequently on-demand (like MS Word). Some systems have to run 24/7 (like an e-commerce web site). The required availability will greatly impact the design. What are the requirements for system recovery from a failure? “The system shall allow users to restart the application after failure with the loss of at most 12 characters of input” Rasler, Habegger, Parker Page 16 of 20 or26i6Software Requirements Specifications Document 3.6.3 Security Specifi the factors that would protect the software from accidental or malicious access, use, modification, destruction, or disclosure. Specific requirements in this area could include the need to: © Utilize certain cryptographic techniques Keep specific log or history data sets Assign certain functions to different modules Restrict conmunications between some areas of the program Check data integrity for critical variables 3.6.4 Maintai Specify attributes of software that relate to the ease of maintenance of the software itself There may be some requirement for certain modularity, imerfaces, complexity, etc. Requirements should not be placed here just because they are thought to be good design practices. Ifsomeone else will maintain the system 3.6.5 Portability Specify attributes of software that relate to the ease of porting the software to other host machines and/or operating systems. This may include: Percentage of components with host-dependent code Percentage of code that is host dependent Use of a proven portable language Use of a particular compiler or language subset Use of a particular operating system Once the relevant characteristics are selected, a subsection should be written for each, explaining the rationale for including this characteristic and how it will be tested and measured. A chart like this might be used to identify the key characteristics (rating them High or Medium), then identifving which are preferred when trading off design or implementation decisions (with the ID of the preferred one indicated in the chart to the right). The chart below is optional (it can be confusing) and is for demonstrating tradeoff analysis between different non-functional requirements. H/MIL is the relative priority of that non-functional requirement. ID _| Characteristic HUML |1 |2 [3 |4 [5 {6 [7 [8 |" [10 [41 [ae Correctness Efficiency Flexibility Tntegrity/ Securit Interoperability aye] |9) > Rasler, Habegger, Parker Page 17 of 20 or26i6Software Requirements Specifications Document 6 | Maintainability 7_ [Portability 8 Reliability 9 [Reusabili 10_[Testabilit 11 [Usability 12 [Availability Definitions of the quality characteristics not defined in the paragraphs above follow. * Correctness - extent to which program satisfies specifications, fuifills user's ‘mission objectives + Efficiency - amount of computing resources and code required to perform function + Flexibility - effort needed to modify operational program + Interoperability - effort needed to couple one system with another + Reliability - extent to which program performs with required precision + Reusability - extent to which it can be reused in another application + Testability - effort needed to test to ensure performs as intended + Usability - effort required to learn, operate, prepare input, and interpret ouput THE FOLLOWING (3.7) is not really a section, it is talking about how to organize requirements you write in section 3.2, At the end of this template there are a bunch of alternative organizations for section 3.2. Choose the ONE best for the system you are writing the requirements for. 3.7 Organizing the Specific Requirements For anything but trivial systems the detailed requirements tend to be extensive. For this reason, it is recommended that careful consideration be given to organizing these in a manner optimal for understanding. There is no one optimal organization for all systems. Different classes of systems lend themselves to different organizations of requirements in section 3. Some of these organizations are described in the following subclasses 3.7.1 System Mode Some systems behave quite differently depending on the mode of operation. When organizing by mode there are two possible outlines. The choice depends on whether interfaces and performance are dependent on mode. 3.7.2 User Class Some systems provide different sets of functions to different classes of users. Rasler, Habegger, Parker Page 18 of 20 or26i6Software Requirements Specifications Document 3.7.3 Objects Objects are real-world entities that have a counterpart within the system. Associated with each object is a set of attributes and functions. These functions are also called services, methods, or processes. Note that sets of objects may share attributes and services. These are grouped together as classes. 37.4 Feature A feature is an externally desired service by the system that may require a sequence of inputs to effect the desired result. Each feature is generally described in as sequence eof stimulus-response pairs. 3.2.5 Stimulus Some systems can be best organized by describing their functions in terms of stimuli 3.7.6 Response Some systems can be best organized by describing their functions in support of the generation of a response. 3.7.7 Functional Hierarchy When none of he above organizational schemes prove helpful, the overall functionality cam be organized into a inerarchy of finctions organized by either comnnon inputs, common outputs, or conmnon internal data access. Data flow diagrams and data dictionaries can be use dot show the relationships between anxd among the functions and data. 3.8 Additional Comments Whenever a new SRS is contemplated, more than one of the organizational techniques given in 3.7 may be appropriate. In such cases, organize the specific requirements for multiple hierarchies tailored to the specific needs of the system under specification. Three are many notations, methods, and automated support tools available to aid in the documentation of requirements. For the most part, their usefulness is a function of organization. For example, when organizing by mode, finite state machines or state charts may prove helpful; when organizing by object, object-oriented analysis may prove helpful; when organizing by feature, stimulus-response sequences may prove helpful, when organizing by functional hierarchy, data flow diagrams and data dictionaries may prove helpful Rasler, Habegger, Parker Page 19 of 20 or26i6Software Requirements Specifications Document In any of the outlines below, those sections called “Functional Requirement i” may be described in native language, in pseudocode, in a system definition language, or in four subsections titled: Introduction, Inputs, Processing, Outputs. 4. Change Management Process Identify the change management process to be used to identify, fog, evaluate, and update the SRS to reflect changes in project scope and requirements. How are you going to control changes to the requirements. Can the customer just call up and ask for something new? Does your team have to reach consensus? How do changes to requirements get submitted to the team? Formally in writing, email or phone call? 5. Document Approvals Identify the approvers af the SRS document. Approver naine, signature, and date should be used. 6. Supporting Information The supporting information makes the SRS easier to use. It includes. © Table of Coments © Index © Appendices The Appendices are not always considered part of the actual requirements specification and are not always necessary. They may include: (a) Sample VO formats, descriptions of cost analysis studies, results of user surveys (8) Supporting or background information that can help the readers of the SRS (c) A description of the problems to be solved by the software (a) Special packaging instructions for the code and the media to meet security, export, initial loading, or other requirements When Appendices are included, the SRS should explicitly state whether or not the Appendices are to be considered part of the requirements. Rasler, Habegger, Parker Page 20 of 20 or26i6