Develop Initial Notes of the Structure/Functionality of the System

The generated Software Requirements Specification (SRS) document will be submitted to the instructor via the Assignments Folder no later than the date and time shown above to avoid losing points per the rules stated in the Syllabus. It is your responsibility to review the policies for the assignments and projects specified in the Syllabus and adhere to all guidelines. There is no extra ‘make-up work’ for points lost on this project. Students are encouraged to use the Chat Room feature to ask other students questions about the project as they work through generating the SRS.

SCENARIO

You have been asked to lead a software development effort for Defense-Specialists Corporation, a large defense company in the United States. Your team must develop the software needed to operate a fictionalnetwork of groundbased tracking stations. The effort should be completed within twelve (12) months. The US government customer stresses the need to balance development costs, quality of the software, overall operability and functionality, and delivery time.

In this project, you will perform preliminary system engineering and create an analysis model for this system. 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 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. Your SRS must be testable, flexible, and traceable.

Please develop a SRS by writing and decomposing functional requirements for afictionalnetwork of groundbased tracking stations. The SRS should contain software components for the ground based tracking stations. Key attributes of the ground based tracking stations shall be the capability to be controlled by a human-computer interface (HCI) to send software commands, operate 24/7, communicate with other ground tracking stations, and receivetelemetry and video images from overhead government satellites.

STATEMENT OF WORK (SOW)

The US government customer has contracted various work efforts out to build the next generation fora fictionalnetwork of ground based tracking stations. The network of ground based tracking stations is used to track a constellation of overhead government satellites that are closely monitoring hostile countries. Defense-Specialists Corporation is the prime contractor to develop the software needed to operate the network of ground based tracking stations.The software developed by Defense-Specialists Corporation equips government operators of theground stationswith the ability to monitor the health and status, perform maintenance and issue resolution, and continuous tracking of the overhead satellite constellation.

SRS TEMPLATES

Please use either of the following templates to develop your SRS

IEEE Std 830-1998: IEEE recommended practice for software requirements specifications, posted in the Reserved Readings section on the Class Menu. The entire outline for the SRS is provided in section 5. 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 or Object-Oriented Analysis/Design (OOA/D) methodology. 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.

Note: Whatever your choice, you must address and write section 3 of the template to successfully address the requirements for the SRS.

Adaptable Process Model (ADP) template for Software Requirements Specification. Download the Pressman suggested outline of the SRS at McGraw-Hill's SEPA Web site at

Make any reasonable assumptions based on your understanding of the problem that allow you to address as many sections of your chosen SRS template as possible. I do not expect, or require, that you completely address all sections of the template. However, your SRS must address, and be built around, the required deliverables specified below. (You must incorporate the below requirements into the appropriate sections of your chosen SRS template).

THE ASSIGNMENT

1.Demonstrate your understanding of the US government’s SOW by producing a preliminary documentation of the structure/functionality of the fictionalnetwork of ground based tracking stations. The basic objective here is to determine the major tasks in the development of theground stations and to begin documenting the structure and functionality. Much of this information should fit into the introductory and system functionality/description sections of the SRS.

2.Download your preferred SRS template. Pay special attention to the following required deliverables on which the bulk of your grade will be decided. (Please read the “project descriptions” in the project description section of the Syllabus for additional context and information on course projects).

Produce an architectural context diagram (ACD) for the ground stations. An ACD models how the system interacts with external entities (See figure 9.6 on page 257 of the Pressman text for an example; also see Module 1, Figure 1.5 of the course module commentary).
Produce a context-level (Level 0) Data Flow Diagram (DFD) for the tracking system. The context level 0 DFD focuses on the flow of data through a system (See figure 7.1on page 188 of the Pressman text for an example).
Refine your DFD to level 1 (see figure 7.2 on page 190). It may also be necessary to include process specifications to ensure that your DFD is defined to the lowest possible specification for design. If you prefer an object-oriented approach, you may supplement your use cases by using an activity diagram to depict the flow of interaction within a specific scenario.
Produce a class diagram, or an Entity Relationship Diagram (ERD) of the tracking system. (See figure 6.10 on page 174 of the Pressman text, or figure 2.8 of the module 2 course module commentaries for examples of a class diagram).
Identify the customers, users, and other stakeholders of the ground stations. Produce a use case diagram for the tracking system (See figure 5.2 on page 138 or figure 2.6 of the course module commentaries for examples of use case diagrams). Use the module 2, Table 2.2 of the course module commentaries and/or the template example on page 136 to develop (at least two) scenarios for the system.
Produce a state diagram for the tracking system. (See figure 7.4 on page 192).

Make sure your work is neat and legible. Your charts, illustrations and diagrams can be done using any word processing, drawing, and/or software CASE drawing tool (or by hand) as long as it is neat and organized. Embed or scan any diagrams that you create in your SRS document—do not upload them separately.

Arrange your output so that all steps are in order. Number all steps. Turn in your assignment by the due date/time (January 27, 2013). Don’t forget to put your name on your project. Please contact the instructor before the due date if you have any questions or concerns. Please use the Ask the Instructor conference to post any questions about this project.

Note: The late projects policy stated in the Syllabus will be strictly enforced. Projects received after the due date and time will be considered late and be subject to the late projects policies in the Syllabus. Assistance cannot be guaranteed on the day this project is due! Plan ahead.