[ghetto-software] Intro Part I

From: Nathan E Moore <nmoore4@xxxxxxxxxxx>
To: ghetto-software@xxxxxxxxxxxxx
Date: Mon, 1 Mar 2004 09:50:24 -0500 (EST)

Here is a rough draft for Part I of the Def Doc.  As of 9:50 only

Nathan
and
Cord

have posted anything for Def Doc.  Will check throughout the day.

Nathan Moore

Purpose :
        
        The purpose of this definitions document is to clarify the requirements 
stated by the client Operations Manager Greg Mundy for the West Virginia 
International Airport.  

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.

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.

[ghetto-software] Intro Part I

Other related posts: