A study of design methods and their use in the correct implementation, maintenance and evolution of software systems. Topics include design, implementation, testing, documentation needs and standards, support tools. Students design and implement components of a software system. Weekly 1.5 hour laboratory (starting 2017). Prerequisites: General prerequisites; including SC/MATH 1090 3.00; LE/EECS 2031 3.00.

Software designers are experts at developing software products that are correct, robust, efficient and maintainable. Correctness is the ability of software products to perform according to specification. Robustness is the ability of a software system to react appropriately to abnormal conditions. Software is maintainable if it is well-designed according to the principles of abstraction, modularity, and information hiding. At the end of the course, students will be able to:

1. Specification: Describe software specifications via Design by Contract, including the use of preconditions, postconditions, class invariants, loop variants and invariants
2. Construction: Implement specifications with designs that are correct, efficient and maintainable.
3. Testing: Develop systematic approaches to organizing, writing, testing and debugging software.
4. Analysis: Develop insight into the process of moving from an ambiguous problem statement to a well-designed solution.
5. Architecture: Design software using appropriate abstractions, modularity, information hiding, and design patterns.
6. Tools: Develop facility in the use of an IDE for editing, organizing, writing, debugging, testing and documenting code including the use of BON/UML diagrams for documenting designs. Also the ability to deploy the software in an executable form.
7. Documentation: Develop the ability to write precise and concise software documentation that also describes the design decisions and why they were made.

The course outline is a guideline to topics that will be discussed in the course, and when they will be discussed. It is a tentative outline and may be modified during the term.

• Course overview
• Notes on Eiffel
• Classes
• Objects

• Modularity
• Agents and Tuples
• Documenting ADT
• Memory management
• Generic types

Victoria Day, University is closed

• Assertions
• Top down design

• Bank 1-5
• Dictionaray

• Design within a class
• Design by contract
• eSpec and TDD
• Notes on eSpec
• Exceptions

Assignment 1 Due on midnight

• BON static model
• Inheritance
• Polymorphism and dynamic typing

• Inheritance adaptation
• Multiple inheritance
• Inheritance and uses design
• Inheritance and Design by Contract

Midterm test

• Adapter pattern
• MVC
• Design patterns
• Observer pattern
• BON dynamic model

Deadline to drop the course without grade

• Global objects
• Singleton
• Composite

• Visitor
• Iterator
• Command
• Command do-undo case study

• Decorator
• State

• Review

Civic Holiday, University closed

Study days

Summer term ends

Exams will be scheduled on August 11-19, 2016 Specific information will be provided in the later time.