project 1

Final Project for CSC440

Project 1 deliverable: Requirements Specification with User signoff. Submit your spec to me and to the user group. Someone from the user team has to send an email to sign off on the specs. The user can state concerns in the email. Having some concerns or limits on acceptance is fine.

Deliverable schedule:

For the first deliverable (in Fall 2015 it is 9/14), you are writing a draft only, but it should have the preface, introduction, user requirements definition, and appendix complete.
The final deliverable (in Fall it is 9/23) will be the complete document. Each group of 3 or 4 (orders or warehouse) creates one document though the two groups serving the same client need to have specifications that basically fit each other. The User signoff can be done in class, so please come to class Wednesday with one printed copy of your document for each group.

Parts of document: (Note that you need all parts, but I am only expecting the User Requirements and System Requirements section to be thorough.)

Chapter	Description
Preface	Describe expected reader Version History (empty at this point perhaps)
Introduction	Describe need for system; Function of system in very broad terms (5 sentence max) How system will work with other systems How system fits larger organization's business plan
Glossary	Define any terms a user or programmer may need to know to read this. (Remember both read this.)
User requirements definition	Services the system will provide to the user NonFunctional requirements description (what the system will do that is not directly something the user knows, such as maximum system data size and product and process standards)
System Architecture	High level overview of anticipated system architecture. Describe Broadly System modules you will create (maybe only one) Describe Broadly System modules that exist that you will use. List systems you will interface to Describe hardware and major tool choices (such as Java) Include one box diagram with all the modules in your system and all the systems to which your system interfaces. Include the number of computers and who will use each computer. Include at least one standard architectural model found in your book or documented on the internet that you will use for this system.
System requirements spec	Describe the exact tasks the system will do to implement the user requirements. (note that this must be above a coding and class definition level. It is still at a high level, but lower than user requirements. All system requirements put together should accomplish everything written in the user requirements section
System Models	Include at least one use case At least one activity diagram At least one sequence diagram At least one state diagram
System Evolution	Describe some future changes you might want a designer to consider. Come up with at least one.
Appendices	Include documentation of one example of each of the following methods of elicitation: Interview Scenario Use case Ethnography (just describe a part of the user's day)