Software Design
- 2. Software Design Conversion of Software Requirements to something that developers can code Software Modelling Model Scaling Communication
- 3. Required Skills Software Engineering Requirements Analysis Communication
- 4. Software Modelling Verify and Understand Requirements Reduce Code and Effort Duplication Streamline Process of Software Development and Test Planning Assist in Agile Development by Providing a Feedback Loop
- 5. Static Modelling All About Class Types Entities Functional Finite State Automata
- 6. Domain Modelling Assume Finite State Automata Use the Project Glossary Hands On: Domain Modelling
- 7. Dynamic Modelling Use Cases Sequence Diagrams This does NOT drive the software structure – static modelling does that.
- 8. ICONIX Process Static Modelling and Dynamic Modelling in Parallel (Probably better to build the static models first) Be aware of your build flow.
- 9. Model Scaling A single domain model is only useful for small applications Requirements Breakdown means Model Breakdown Model Breakdown means Component Architecture
- 10. Model Breakdown Rationalise the Terminology (user/customer/account etc) Build High Level Domain Models Analyse and Isolate Sub-Components Continue to breakdown as required
- 11. Component Architecture SOA or Non-SOA? Separate CRM and eCommerce? Separate Reporting System? Staff Management, HR etc?
- 12. Scale Back Up Convert links between domain objects to links between domain models Define APIs at Model not Object level
- 13. Communicate the Architecture Explain How the Domain Model is Built Map Domain Models to Requirements Explain Terms in Mapping Explain Each Component
- 14. Compartmentalisation Lay Out Requirements into a Diagram Lay Out Models into a Diagram Map the Diagrams Build Domain Models for each Component
- 15. Communication Diagrams Are Not Architecture Communication is Architecture You Have 2 Audiences: Technical and Non- Technical Communicate According to Audience
- 16. Frameworks Frameworks Can Buy Time Time Is Money Incorporate at the Domain Model Stage Make Design Decisions Compatible With the Framework
- 17. Points Of Study Communication Skills Language Skills UML and Software Modelling Frameworks