Srs computer science

Scenario

You have been asked to lead a software development team to build a system fulfilling the Statement of Need below. Your team is employed by a small company. The customer wants a project that balances reasonable development cost, timely delivery, software quality, and functionality.

In this project, you will perform preliminary system engineering and create an analysis model for this system. (See Module 3, Figure 3.1 of the course module commentaries for an overview of the elements of an analysis model). Completing this project will require that you do the following:

· Develop initial notes of the structure/functionality of the system.

· Produce an initial system specification document for the system.

· Develop a detailed scenario based model by writing use cases and develop an activity diagram.

· Create a behavioral model that identifies events with a use case

Completing this project will require that you produce a software requirements specification (SRS) document for the system The SRS that you create will be a combination of the System Specification (SS) and the SRS; your SRS must include the essential components of the SS in the SRS.

Your SRS will provide the foundation for Projects 2 through 4, so it must:

· Describe the customer requirements

· Establish the basis for software design

· Be testable, flexible, and traceable.

Statement of Need

John and Jane are starting a bed-and-breakfast (B&B) in a small New England town. They will have three bedrooms for guests. They want a system to manage the reservations and to monitor expenses and profits. When a potential customer calls for a reservation, they will check the calendar, and if there is a vacancy, they will enter the customer name, address, and phone number, dates, agreed upon price, credit card number, and room numbers. Reservations must be guaranteed by 1 day’s payment. Reservations will be held without guarantee for an agreed upon time. If not guaranteed by that date, the reservation will be dropped.

SRS Template

Please use the IEEE template to develop your SRS. The IEEE Std 830-1998: IEEE recommended practice for software requirements specifications is posted in the Reserved Readings section on the Class Menu. The entire outline for the SRS is provided in section 5, Figure 1. Familiarize yourself with the type of information and diagrams to be provided in a SRS.

· You may follow either of two paths; Structured Analysis/Design (SSA/D) methodology (i.e. organize your requirements by functional hierarchy) or Object-Oriented Analysis/Design (OOA/D) methodology (i.e. organize your requirements by objects). The contents of your SRS will be somewhat dependent upon this choice.

· Look at the IEEE Standard 830 - 1998 Annex A. Annex A has suggested formats for your SRS. If you are following the SSA/D methodology, use template A.7. For OOA/D, use A.4.

· Template A.4 allows you to organize your requirements by objects. For example, objects in a patient monitoring system include patients, sensors, nurses, physicians, medicines, etc. Each object has a set of attributes and each object performs a set of functions, services, methods, or processes. Note that objects may share attributes and services that can be grouped together as classes.