umlclass - 02 Modeling: UML class diagrams 19 Jan 2011...

Info iconThis preview shows pages 1–7. Sign up to view the full content.

View Full Document Right Arrow Icon
02 Modeling: UML class diagrams 19 Jan 2011 CSCD08S Software Engineering 1 02 modeling CSCD08 Software Engineering 1 Intro to Software Modeling: UML Class Diagrams CSCD08 Software Engineering
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
02 Modeling: UML class diagrams 19 Jan 2011 CSCD08S Software Engineering 2 02 modeling CSCD08 Software Engineering 2 UML Overview b You will be expected to demonstrate fluency in a few of the most widely used forms of UML: h Use cases h Sequence diagrams h Class diagrams b Does this stuff really matter? b Yes, and not just to satisfy a curriculum point. h UML has become the dominant notational tool in (academia and) industry for communicating requirements and designs for development. h Informal (napkin sketch of system design) and formal (working document to guide developers writing code). h If you can’t read and write UML, you’ll be in trouble.
Background image of page 2
02 Modeling: UML class diagrams 19 Jan 2011 CSCD08S Software Engineering 3 02 modeling CSCD08 Software Engineering 3 Why Model? b Natural language, s.a. English, imprecise, ambiguous h requirements h user stories b Large software -> communication h requires precision, not ambiguity h at right level of detail/abstraction for task at hand b Code is too detailed as basis for getting “big picture” understanding of modules b Modeling helpful for communication and understanding of: h application domain (what’s that?) h system requirements h structure and behavior of the code you are about to write
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
02 Modeling: UML class diagrams 19 Jan 2011 CSCD08S Software Engineering 4 02 modeling CSCD08 Software Engineering 4 Why Model? b Helps you to visualize what you want to build b Creates a shared language among developers, designers, domain experts, testers, etc. b Helps you express precise statements about structure and behavior b Can facilitate prototyping and simulation b Sets expectations and provides templates for implementation b Allows you to explore scenarios without having to build them first b Provides a structure to guide the process of transforming requirements into code (e.g. Iconix)
Background image of page 4
02 Modeling: UML class diagrams 19 Jan 2011 CSCD08S Software Engineering 5 02 modeling CSCD08 Software Engineering 5 Class Diagrams b Perhaps the most important for OO designs; expresses many details of an OO design: adapted from Easterbrook type
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
UML class diagrams 19 Jan 2011 CSCD08S Software Engineering 6 02 modeling CSCD08 Software Engineering 6 Class Diagrams: Basic Building Blocks Window size: Size visibility: boolean display() hide() Class name attributes aka fields operations aka methods b A class describes a group of objects with: h similar properties (attributes), h common behaviour (operations), h common relationships to other objects, h common meaning (“semantics”). b
Background image of page 6
Image of page 7
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 02/05/2011 for the course CS 8 taught by Professor Alanrosselet during the Winter '11 term at University of Toronto- Toronto.

Page1 / 37

umlclass - 02 Modeling: UML class diagrams 19 Jan 2011...

This preview shows document pages 1 - 7. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online