[ghetto-software] ATTN GROUP: Req. Def. important notes
- From: Nathan E Moore <nmoore4@xxxxxxxxxxx>
- To: ghetto-software@xxxxxxxxxxxxx
- Date: Mon, 8 Mar 2004 11:33:11 -0500 (EST)
Here is the Introduction revision.
I hope that all work is posted by 6pm as discussed yesterday, so that
Lee will have more time to produce the final document.
Also, Lee: I suggest looking at the sample requirment documents to add
some finesse to the layout, i'm also going to attach our cover sheet
from the proposal for this document (nathan.pdf). You don't have to
add it to the latec doc if its a pain in the ass, I can just staple it
to the front. Good luck and please bring a copy or post it to the list
before lecture tomorrow. Submit it even if Vicki and Damien have not
given you their segments yet.
I will be posting the general constraints and assumptions portion later
today.
Nathan
Purpose:
The purpose of this document, "Requirements Definition", is to clarify
the requirements as stated to Ghetto Software Inc. by the client Operations
Manager Greg Mundy for the West Virginia International Airport. This document
will be the foundation for development of Clear Skys 1.0. The intended
audience for this document are those stakeholders and owners of West Virginia
International Airport. This will give WV International Airport an opportunity
to clarify and ambiguous requirements and to correct any mistakes made on our
part regarding the functionality of this system.
Scope :
The product being developed by Ghetto-Software Inc. is called Clear
Skys 1.0. The purpose of this software supoprt system is to replace an
existing software system at West Virginia International Airport which
has been in existance for fifteen years. The current system in place
supports: safety, security, efficiency, and compliance with FAA rules
of the Airport. The new system will consist of four major subsystems:
Air Space Manager, Ground Operations Manager, Gate and Schedule
Manager, Emergency Management. This software, at a minimum, will:
handle the simultaneous takeoff and departure schedules of multiple
aircrafts, administer gate and runway assignments for aircrafts,
provide an interface for a variety of users to view different types of
information about aircraft schedules, and facilitate landing of
unscheduled aircrafts in emergencies.
Definitions and Abbreviations:
FAA: Federal Aviation Administration
IEEE: Institute of Electrical and Electronics Engineers
WV: West Virginia
(more to be added as document develops)
Refereneces:
IEEE 830 - Guideline for standard requirements definition documents.
Pressman, Roger. Software Engineering: A Practitioner's Approach. New
York: McGraw-Hill, 2001.
Overview:
Part II of this document, entitled General Description, will place
Clear Skys 1.0 in perspective with regard to integration of other
systems. Part II will describe how the sytem will be developed and the
intended installation method. It will provide a list of functions of
the four major subsystems defined in this document. It will describe
the intended user with regards to education level, experience,
technical expertise, and user training. It will define the general
constraints as put forth by the customer WVIA, which will limit the
design/implementation of the system inculding: regulatory policies,
hardware limitations, and interfaces to other applications. The
General Description segment will also assess and evaluate risk and
interdependancy with external systems/sources.
Other related posts:
