CS 481			Final Report			5 Dec.

	Your grade for CS 481 depends on a final report and a 15 minute
	professional presentation Friday 13 Dec. in S 155.  

	The final report consists of a detailed project description and
	a specification of the system requirements.  I insist upon a 
	detailed project description and a first version of system
	requirements.  I realize you are quite busy at this time of the
	year.  The deadline for the report is 6 AM Sat. 14 Dec.


	Detailed project description

	The project description contains a detailed overview of the work you 
	will perform in fulfillment of your senior project.  It includes
	a name for the project, the name of the sponsoring company and
	detailed contact information for your sponsor. 

	The first draft of the detailed project description is the 
	document you sent me if you obtained my approval for a project.
	The final description should address any concerns I raised.
	

	System requirements

	A detailed specification of the requirements of the system is one
	of the first tasks in the development process.  Clients, domain
	experts, system analysts and other stakeholders participate in the
	development of the requirements for the application.  These initial
	requirements are analyzed for correctness (Are they the right
	requirements for the application?), completeness (Do they account
	for all the application must do?) and consistency (Does one 
	requirement clash with another one?).  This analysis leads to a
	revised set of requirements.  The process continues until all
	stakeholders agree on a final set of requirements.  

	These requirements are transformed into a set of software requirements
	for developers.  The software requirements specify the external
	behavior of the application and document the interfaces between 
	the application and its environment.  They focus on what the 
	application must do, rather than how it does it.

	A requirements specification normally includes the following.

	o  the purpose of the system
	o  the information the system will store for a long period of time
	o  the system features that assist in conducting business
	o  the system features that facilitate a more efficient way of
	       conducting business
	o  the system features required to interact with other related systems.

	The requirements document often forms the basis for a formal or
	informal contract between clients and developers.

	Development of the document requires consultation with the manager
	and its clients.  The clients will participate in various
	interactions with the application.  A scenario or use case describes
	each interaction.  Each scenario identifies the usage with a name
	and the participating clients.  It includes a short process 
	description of no more than a few paragraphs.  

	Development also requires consultation with the system analysts of
	other systems with which the application may interact.