User Tools

Site Tools


start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
start [2015/09/08 17:50] jonathanstart [2015/09/08 18:54] (current) jonathan
Line 3: Line 3:
  
 ===== EECS 4090 Short Description  ===== ===== EECS 4090 Short Description  =====
- 
- 
  
 A well-designed software product is more than just a computer program. A software product consists of quality code, a well thought out design developed via disciplined professional engineering standards, appropriate literate documentation including requirements, design and testing documents, a manual, and the appropriate installation files and instructions needed to get the product to work. The product has to be correct (i.e. it must satisfy all the requirements specified by the client), usable, efficient, safe and maintainable. A well-designed software product is more than just a computer program. A software product consists of quality code, a well thought out design developed via disciplined professional engineering standards, appropriate literate documentation including requirements, design and testing documents, a manual, and the appropriate installation files and instructions needed to get the product to work. The product has to be correct (i.e. it must satisfy all the requirements specified by the client), usable, efficient, safe and maintainable.
Line 17: Line 15:
  
 Students must apply sound mathematics, good engineering design, and algorithms throughout the project. However, they will also need to apply heuristics and design patterns, or “rules of thumb”, where sound, well-understood algorithms are not available. Any such heuristics must be clearly identified and supported by arguments that justify their choice. The teams will be required to show that the heuristic cannot fail in a way that will violate safety restrictions or other restrictions designated as critical.  Students must apply sound mathematics, good engineering design, and algorithms throughout the project. However, they will also need to apply heuristics and design patterns, or “rules of thumb”, where sound, well-understood algorithms are not available. Any such heuristics must be clearly identified and supported by arguments that justify their choice. The teams will be required to show that the heuristic cannot fail in a way that will violate safety restrictions or other restrictions designated as critical. 
 +
 +===== Grading and Milestones=====
 +
 +  * 10%: **Precise Requirements Document** (December 2015)
 +  * 10%: **Design Document** and some working code (January 2016)
 +  * Most code working (February 2016)
 +  * **Testing Document** and all code working (April 2016)
 +  * Presentation (May 2016?)
 +  * Final revised documents, deployment of code, and user manual
start.1441734607.txt.gz · Last modified: 2015/09/08 17:50 by jonathan

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki