One-file will before lecture slides will available to be downloaded as opposed to the current system of printing out each slide from the web.

Peer evaluations due Tuesday

Next Class: Design and Implementation

User Interface - usability goals

Example: Learn system in 30 minutes

System Requirements - physical and environmental factors

Performance Requirements - performs according to users expectations

Example: no delay more than xxx seconds

Pure end user time is not a good requirement for online systems due to the lack of control over the network traffic.

Good requirements should be able to be evaluated.

• "Easy to use" is not a good requirement
• "Can be learned in 30 minutes" can be validated

Goal – take information from customer and make it technical enough for the programmers to implement and simple enough for the customer to understand.

Should be a joint effort between the developer and the customer.

• Separate functionality from the implementation. F(2) = 5 instead of x + 3 = 5. The function has the same functionality but the details are hidden.
• Take into consideration that the system is part of an existing environment
• Specification should be complete, formal, and technical enough to move to the implementation
• You system should be able to adapt if the environment is constantly changing

Introduction – goals, concepts, tells who you are and what your doing

Bibliography – sources used, why decisions were made

Appendix – graphs, charts, complex algorithms

Information Description – Description of technical side. Talks about the interfaces between the programs.

Functional Description – talks about design constraints and helps later users understand why things were done the way they were done.

Validation Criteria – Testing and testing plans, special considerations that were not addressed in the other requirements, performance criteria. This section is a review of the requirements.