Software Requirements Specification

Part One of the SRS

The four assignments being accomplished in the first four weeks of this class will introduce you to several different aspects that must be considered during the process of requirements development on a project. To implement this requirements development process, you will need to choose 1 of the following 3 scenario options and carry that option throughout the course to the final project:

OPTION 1: Organization X providing online banking services
OPTION 2: Organization Y providing defense contracting services
OPTION 3: Organization Z providing airline reservation services
The goal of the overall final project will be to ensure that you can practice requirements engineering methodologies within your chosen scenario and have the skills required to develop software requirements specifications and to understand project requirements and associated risks and designs, after interacting with customers; therefore, in this first individual project you will need to work with the customer at the project kick-off to perform requirements elicitation, identification, definition, and the required documentation described.

Describe how the requirements engineering team worked with the clients to perform project requirements discovery or elicitation and identification, and show the customer your SRS specification outline. Provide the following in this first assignment: Describe some of the preparations you will need to make technically in preparation of the requirements kick-off meeting. Describe some of the skills needed by the developer to adequately elicit software requirements and the intended outcome of the requirements elicitation process. Provide an outline for the SRS specification document to be delivered in Week 5 of the course (Note: this will be carried over and expanded on in your Final Project). A reference list in proper APA format must be provided. Clarifications: At a minimum, you must provide a purpose of the software requirements specification (SRS) and the SRS product, and detailed descriptions of the interaction that happened between the client and the requirements engineering segments. The overall purpose of the SRS document will be to specify the requirements imposed on the system, its computer software configuration items (CSCIs), manual operations, and other system components that will be exchanging data as part of this system. The outline of the SRS would be something similar to the following: Introduction: This should provide an overview of the entire SRS and should have the purpose of the document and include the scope, definitions, acronyms, abbreviations, and any references that are applicable. References: Provide a list of all documented references in the SRS, and include the date or title report number Overall Description: Describe the general factors that affect the airline reservation system product and its requirements; this provides a background for the requirements (product perspective, functions, user characteristics, constraints, etc.). Specific Requirements/Functionality: This section contains all of the “shall” requirements needed to identify the functions of the airline reservation system. Usability: This identifies requirements that affect usability. Reliability: Requirements affecting the reliability of the system should be listed here, such as availability, mean time between failure (MTBF), mean time to repair (MTTR), accuracy, maximum bugs, or defect rate. Performance: This section should include specific system response times for transactions of the airline reservation system, throughput, resource utilization, and so on. Supportability: The requirements affecting the supportability or maintainability of the system go in this section. Design Constraints: This may include architectural or design constraints, prescribed use of certain tools or procedures, purchased components, and software languages. Licensing: Any licensing enforcement requirements or other usage restrictions on the airline reservation software are listed here. Requirements Verification: This section states the requirements verification process, methods, test, demonstration, analysis and inspection methods used to perform verification. Requirements Traceability: This contains the CSCI requirement and the traceability of the requirement to the system. Appendices: This section may contain the use-case storyboards, user interface prototypes, or other information either related or not related to the requirements.

Part Two
Now that you have completed your Requirements Kick-off Meeting and understand the expectations of the client or customer, you must now provide an initial set of software/system requirements needed to capture the functions of the airline reservation system (or the online banking services or defense contracting services, depending on which option you chose). Provide the following in this assignment: Complete the introduction, references, and overall description to provide the start of your SRS document. Around 2–3 sentences per section will be expected. Provide 5 specific requirements/functionality for Section 4, 1 requirement each for Sections 6–8, and 10, and for Section 9, provide 2–3 design constraints. Provide at least 1 paragraph about your requirements verification process, methods, test, demonstration, analysis, and inspection methods used to perform verification. Transfer all of your requirements created in the previous sections to a Matrix to be provided in Section 12; this will contain the CSCI requirement and the traceability of the requirement to the system. Introduction: This should provide an overview of the entire SRS and should have the purpose of the document and include the scope, definitions, acronyms, abbreviations, and any references that are applicable. References: Provide a list of all documented references in the SRS, and include the date or title report number. Overall Description: Describe the general factors that affect the airline reservation system product and its requirements; this provides a background for the requirements (product perspective, functions, user characteristics, constraints, etc.). Specific Requirements/Functionality: This section contains all of the “shall” requirements needed to identify the functions of the airline reservation system. Usability: This identifies requirements that affect usability. Reliability: Requirements affecting the reliability of the system should be listed here, such as availability, COOP, MTBF, MTTR, accuracy, maximum bugs, or defect rate. Performance: This section should include specific system response times for transactions of the airline reservation system, throughput, resource utilization, and so on. Supportability: The requirements affecting the supportability or maintainability of the system go in this section. Design Constraints: This may include architectural or design constraints, prescribed use of certain tools or procedures, purchased components, and software languages. Licensing: Any licensing enforcement requirements or other usage restrictions on the airline reservation software are listed here. Requirements Verification: This section states the requirements verification process, methods, test, demonstration, analysis and inspection methods used to perform verification. Requirements Traceability: This contains the CSCI requirement and the traceability of the requirement to the system. In the Appendices, provide merely the names of the use case diagrams that you intend to produce, as next week your real set of diagrams will drive a more comprehensive set of requirements being captured in the SRS. Ensure that the paper follows APA format (no running header or abstract is expected). Ensure all references are captured in the main body of the paper. Clarification: You will be creating the requirements on your own. That said they should be relevant to the system chosen(Online Banking Services)

Part Three
A test specification provides designers with what needs to be known in order to perform a specific test, and to validate and verify the requirement to be tested. The test script is divided into the test script, which is the generic condition to be tested, and one or more test cases within the test script. Provide a test script and test case for at least 3 of your requirements identified in your requirements specification. Provide the following format: Test script: Test script ID Test description (generic condition being tested) System or subsystem being tested Type of test (functional, security, performance) Input data sources Expected results Priority (mandatory or critical; important; desirable) Pass/Fail criteria (allowable delta between degree of mismatch between actual and expected results) Traceability (ties back to functions, modules, data structures) Test Case: Test Case ID and test script number (which script this test case is exercising) Input test transaction data values Initial environment and configuration, initial state of system required for this test Test driver ID (if a real driver is needed) Expected results (output test data values) Ensure that the Word document follows this format and that actual SRSs you identified in your original SRS specification are being identified in the test script/case.

Part Four
This is a Power point slide Show. Several phases of the requirements project have now been completed; however, it will be critical to inform the customer of your requirements management practices and plan. Additionally, the customer must verify that your team did follow the requirements management standards implemented by Software Engineering Institute Carnegie Mellon. In a PowerPoint presentation, provide the following to illustrate the actions taken to implement requirements management: Title slide Topics of Discussion slide Summary of IEEE Standards used during the requirements management process (i.e., IEEE Std 1233 – 1998; IEEE Std 830-1998, SEI CMMI) Introduction and Purpose of Requirements Management (REQM) within CMMI Goals and Practices used during REQM for your project Identification of at least 1 Requirements Management tool or software, which would be used in support of your project at a major corporation (i.e., DOORs, Requisite Pro, CASE Spec, Open Source RM, CORE) Use of requirements management to produce metrics Summary slide Reference slide in APA format Each major topic presented from the Summary of the IEEE Standards to the Goals and Practices used during REQM should have 2–3 sentences of explanation or expansion placed in the speaker notes of each slide. References must be placed either on the slide or in the speaker notes in APA format. The overall length of the presentation should be 8–11 slides in PowerPoint. Part Five In the final week, you have met with the customer and provided a real description of the software requirements engineering process from inception through validation, described functional and nonfunctional requirements, and described how you would perform requirements management and engineering, analysis, and development. Use case diagrams have been produced to define the SRSs developed with customer feedback. Customers desire verification and validation of the requirements, traceability and test documentation, therefore, this process was revealed in detail in the previous assignment. Now, it will be your task in this assignment, Appendix A, to do the following: Prove the effectiveness of the agile methods used to development the requirements, documentation, and software by describing the agile approach or activities used for the development Describe the methodology (practices, tools) and techniques (developing use cases) used to develop your final Software Requirements Specification (SRS) This Appendix A should be added to your final SRS document delivered in Unit 5.

Sample Solution

ACED ESSAYS