1. ITEC 370
Lecture 13
Design

2. Review Questions? Presentation of project on F Design patterns
Business formal
Treat as if you are presenting what you are building for a company
Design patterns
What are some of the design patterns we talked about on M?
Did you see any you could use in your project?
Have you ever implemented one of them before?

3. Objectives
Finishing up the design process

4. Start Have description of system, what it is supposed to do Resources
Document
Person who wrote the document
Computers
Redbull?

5. Goal Describe how the system is going to be built Tools UML
Design Patterns
Knowledge from previous ITEC classes

6. How? Good question Many different options to consider
Personalized to each team
Strengths / weaknesses
Different approaches

7. Top down When you hear top down what comes to mind?
Broad strokes followed by more precise
Typical OO type approach

8. Bottom up Technical subsystems
Once designed figure out how to string them together
Problems
Some subsystems may share functionality (duplication)
Sprawl is an issue because of lack of direction

9. Abstraction What is it? Where is it useful? When should it be used?
When is it abused?

10. Refinement
Given a rough set of class diagrams, what could you change to make it better?
Combining functionality
Separating functionality
Changing granularity level
Adding / removing abstractions

11. What is the driving principle behind your software system?
Architecture
What is the driving principle behind your software system?
Design patterns
Command pattern
Data flow architecture
MVC

12. Data structures
What / Where / How is getting stored?
When / How is it retrieved?
Advantages / Disadvantages of different approaches (run-time / coding time)
Should you build your own?

13. Information hiding
What is “viewable” at each part of the system
Security
Communication

14. Goals What is really important to the project? Reusability Modularity
Extensibility
Usability
Fault tolerance
Maintainability
Security

15. Process
Decide the goals for the design (may not be customer / requirements oriented)
Reusability, modularity, etc…
Agree on the approach (top down / bottom up)
Determine architecture for system (MVC)
Choose granularity of design
Produce material using a tool
Trace each requirement to a part of the design!

16. Fin Hand a document / zip to a developer Sit back and watch them code
Work isn’t over though
Verification that they are building it right
Code inspections

17. Review
The design process itself