software engineering 67

/in /by

The first doc with running header table contents etc

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.

  • After you choose your scenario option, you are tasked to create the shell for your software requirements specification document (SRS) using the outline below.
  • This week you need to complete sections 1 through 4 as follow:
    • 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.
  • Use the following outline for your SRS document shell. Note that only sections 1 through 4 needs to be populated with content this week:
    1. 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.
    2. References: Provide a list of all documented references in the SRS, and include the date or title report number
    3. 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.).
    4. Specific Requirements/Functionality: This section contains all of the “shall” requirements needed to identify the functions of your selected system. Based on your discussing with the customer, provide 5 specific requirements/functionality for Section 4.
    5. Usability: This identifies requirements that affect usability.
    6. Reliability: Requirements affecting the reliability of the system should be listed here, such as availability, COOP, MTBF, MTTR, accuracy, maximum bugs, or defect rate.
    7. Performance: This section should include specific system response times for transactions of the system, throughput, resource utilization, and so on.
    8. Supportability: The requirements affecting the supportability or maintainability of the system go in this section.
    9. Requirements Verification: This section states the requirements verification process, methods, test, demonstration, analysis and inspection methods used to perform verification.

Doc 2 to be completed added in with doc 1

This week you will perform requirements analysis. Using the details you provided in the “Specific Requirements/Functionality” section, you need to extract the use cases and create a use case diagram by following these steps:

  • Identify the actors
  • Identify the Use Cases (at least 5) and write a brief description of each
  • Identify the actors and the Use cases relationship
  • Use the above to create your use case diagram using UML notation.
  • Outline at least 2 individual Use Cases with details.

Add your use case diagram and use cases outline to your SRS document Appendix.

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.

Doc 3 to be added docs 1 and 2

This week you will continue working on your SRS document and you will focus on the following sections:

  1. Usability

    2. : This identifies requirements that affect usability.

  2. Reliability: Requirements affecting the reliability of the system should be listed here, such as availability, COOP, MTBF, MTTR, accuracy, maximum bugs, or defect rate.
  3. Performance: This section should include specific system response times for transactions of the system, throughput, resource utilization, and so on.
  4. Supportability: The requirements affecting the supportability or maintainability of the system go in this section.
  5. Requirements Verification: This section states the requirements verification process, methods, test, demonstration, analysis and inspection methods used to perform verification.

Add 2 requirements each for Sections 5 through 8.

In section 9, discuss your requirements verification process, methods, test, demonstration, analysis, and inspection methods used to perform requirements verification.

Ensure that the paper follows APA format.

Doc 4 to be added to docs 1-3

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)

Add your test script and test cases to your SCR document Appendix.

Doc 5 final doc to be added to 1-4

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)

Add your test script and test cases to your SCR document Appendix.