SRS document (Coursework Sample)
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. 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, and any references that are applicable. 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 the airline reservation system. 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 airline reservation system, throughput, resource utilization, and so on. 8.Supportability: The requirements affecting the supportability or maintainability of the system go in this section. 9.Design Constraints: This may include architectural or design constraints, prescribed use of certain tools or procedures, purchased components, and software languages. 10.Licensing: Any licensing enforcement requirements or other usage restrictions on the airline reservation software are listed here. 11.Requirements Verification: This section states the requirements verification process, methods, test, demonstration, analysis and inspection methods used to perform verification. 12.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.
source..Name
Institution
Instructor
Title
Table of Contents TOC \o "1-3" \h \z \u Introduction PAGEREF _Toc393637715 \h 3Intended audience and reading suggestions PAGEREF _Toc393637716 \h 3Project Scope PAGEREF _Toc393637717 \h 3References PAGEREF _Toc393637718 \h 3Functional requirements PAGEREF _Toc393637719 \h 3Overall description PAGEREF _Toc393637720 \h 4a.Login PAGEREF _Toc393637721 \h 4b.Enrollment PAGEREF _Toc393637722 \h 4c.Book flights: PAGEREF _Toc393637723 \h 4d.Reserve seats PAGEREF _Toc393637724 \h 4e.Flight schedules PAGEREF _Toc393637725 \h 5f.My account PAGEREF _Toc393637726 \h 5g.Logout PAGEREF _Toc393637727 \h 5Safety requirements PAGEREF _Toc393637728 \h 5Security requirements PAGEREF _Toc393637729 \h 6Software quality attributes PAGEREF _Toc393637730 \h 6Other requirements PAGEREF _Toc393637731 \h 6
Introduction
Airline flight booking system version 1.0 is a system that aims to provide online services to customers both members and nonmembers. It includes services like online booking of flight, online seat reservation, online flight cancellation and any other very important problems that the user may want to be solved on flight matters.
Intended audience and reading suggestions
This document is intended for system developers, project managers, system testers, article writers and even students and other interested parties in the field of system development and documentation. This document is created in such a way that its reading and ease of understanding should be done from the topmost page in that order to the last page. Any kind of reading from the last pages or those which are at the middle while confuse the reader.
Project Scope
The system will be a website that will allow interaction between the users and the system. Clients will be able to perform different tasks such as searching for available flights, reserving seats booking flights, cancelling flights and editing member information. Member users are required to login into their account prior to flight booking. If at all one is not member they are required to create an account.
References
* Xiong, J. (2011). New software engineering paradigm based on complexity science: An introduction to NSE. New York: Springer.
* Pressman, R. S. (2010). Software engineering: A practitioner's approach. New York: McGraw-Hill Higher Education.
* Agarwal, B. B., Tayal, S. P., & Gupta, M. (2010). Software engineering & testing: An introduction. Sudbury, Mass: Jones and Bartlett.
* United States. (1915). S.R.S. document. Washington, D.C.
Functional requirements
1. System must be able to link reserved seat(s) to unique user account and flights.
2. System returns from flight seat(s) to user only available/unreserved seat(s).
3. User must be able to select flight seat(s) to reserve after booking of flight(s).
4. System must be able to randomly assign seats to user, if user fails to reserve seat(s) prior to flight.
5. System must be able to display confirmation of seats and display user flight(s) information.
6. System must block other users from reserving or viewing reserved seat(s) that user has elected
Overall description
We can subdivide the project into 7 main features. Details of each of the following functions can be found in Section 3.
Login
Allows the user to log in to the system with his/her frequent flyer number and password.
Enrollment
Unregistered users enroll and to create a new account with the website. In order to create a new account, the user has to provide personal information. The system will verify and auto-generates a unique frequent flyer.
Inputs:First name, last name, email address and frequent flyer number
Output: Frequent flyer number.
Precondition: The user must not have an existing account with the website function
Book flights:
Allows the user to book a flight online & handles transactions for payments.
Available seats are shown for the departing and returning flights booked by the user.
Reserve seats
Once the flight seats are selected, the user confirms the seat selection. From that point, the seats are removed from available/unreserved seats and the user’s booking is linked to those particular seats. If the user fails to reserve a seat prior to flight takeoff, the user is randomly assigned a seat from available seats 30 minutes prior to initial take-off time. This function is offered immediately after booking the user can wait and use the function to book seats any time after up until 30 minutes prior their flight.
Inputs: User information used to determine previously booked flights. Selected seats to be reserved by user.
Source: Inputs are from the user except flight information which is retrieved by the system.
Output: Selected seats.
Destination: The changes are committed on completion of the ‘reserve seats’ function to account information.
Flight schedules
Allows anyone to view flight status and information.
<...
Other Topics:
- Warehouse Management SystemDescription: Definition of a problem and highlights the requirements specification that leads to the development of a Warehouse Management System Coursework...4 pages/≈1100 words| APA | Literature & Language | Coursework |
- Information Systems ProjectDescription: Information Systems Project Literature and Language Coursework...4 pages/≈1100 words| APA | Literature & Language | Coursework |
- Claude Monet and ImpressionismDescription: Claude Monet and Impressionism Literature and Language Coursework...5 pages/≈1375 words| APA | Literature & Language | Coursework |