1 / 6

Software Design

Software Design. ‘Requirements’ defines The goals the system needs to satisfy. ‘Specification’ defines The externally-observable behaviour of the system. ‘Architecture’ defines The major system-level components Their methods of interaction Technology used ‘Design’ of a component

korlando
Download Presentation

Software Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Design • ‘Requirements’ defines • The goals the system needs to satisfy. • ‘Specification’ defines • The externally-observable behaviour of the system. • ‘Architecture’ defines • The major system-level components • Their methods of interaction • Technology used • ‘Design’ of a component • The code that needs to be written. • We will focus exclusively on OO design. CSC407

  2. Output of Design • A document: • Prose description • UML • Classes • Associations • Methods • Attributes • Object diagrams • Sequence and collaboration diagrams • Statechart and activity diagrams • Formulae & algorithms • Must relate to the architecture • Can reference the requirements and specification • Must be sufficient to allow coding to commence CSC407

  3. Necessary Background • Experience in OO programming • Experience in OO analysis • An understanding of OO concepts • Encapsulation (data hiding) • Objects, classes, meta-classes • Classes v.s. interfaces (types) • Inheritance, multiple inheritance • Polymorphism (run-time typing) • Implementation inheritance v.s. interface inheritance CSC407

  4. Goal • To teach you to create good OO designs. • What you need: • Tools (UML notation) • Experience • How we will teach you: • UML in tutorials • Next best thing to experience: • Other people’s experience • Design Patterns CSC407

  5. Object-Oriented Design • Take OOA and extend to build the ‘Problem Domain Component’ • Design the ‘Human Interaction Component’ • Design the ‘Task Management Component’ • Design the ‘Data Management Component’ [Peter Coad & Edward Yourdon, OOD, Yourdon Press, 1991] CSC407

  6. Problem Domain Component • Reuse design and programming classes. • Group problem-domain-specific classes and establish a protocol by adding generalization classes. • Accommodate inheritance limitations in implementation language. • Add design classes • Associations • Run-time modifiability • … • Improve performance • Speed, memory, perceived speed • Support the data management component CSC407

More Related