03/12/2001 © Bennett, McRobb and Farmer 2002 1 Modelling Concepts Based on Chapter 5 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and.

Slides:



Advertisements
Similar presentations
Requirements Analysis Moving to Design b521.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis.
Advertisements

COMP1007 Introduction to Requirements Analysis © Copyright De Montfort University 2002 All Rights Reserved COMP1007 Introduction to Requirements Analysis.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 12Slide 1 Software Design l Objectives To explain how a software design may be represented.
Solutions to Review Questions
© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
© 2010 Bennett, McRobb and Farmer1 Requirements Analysis 1: Requirements and Classes Based on Chapter 7 of Bennett, McRobb and Farmer: Object Oriented.
A Brief Introduction. Acknowledgements  The material in this tutorial is based in part on: Concurrency: State Models & Java Programming, by Jeff Magee.
Unified Modeling Language
03/12/2001 © Bennett, McRobb and Farmer Class Design Based on Chapter 14 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design.
03/12/2001 © Bennett, McRobb and Farmer 2002 Refining the Requirements Model Based on Chapter 8 of Bennett, McRobb and Farmer: Object Oriented Systems.
Requirements Analysis 8. 1 Storyboarding b508.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis Human.
Use Case Analysis Chapter 6.
03/12/2001 © Bennett, McRobb and Farmer Avoiding the Problems Based on Chapter 3 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Introduction to UML Visual modeling Models and its importance
HCI Designing Interface Objects. The presentation layer How prototyping can be used to try out different interface designs How to model boundary classes.
7M822 UML Introduction 7 September 2010.
03/12/2001 © Bennett, McRobb and Farmer Activity Diagrams Based on Chapter 5 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and.
Kari R. Schougaard, PhD Stud. Værktøjer og Teknikker, 2006 UNIVERSITY OF AARHUS Department of Computer Science Unified Modeling Language Visual language.
03/12/2001 © Bennett, McRobb and Farmer Development Process Based on Chapter 5 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and.
03/12/2001 © Bennett, McRobb and Farmer Use Case Diagrams Based on Chapter 6 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and.
03/12/2001 © Bennett, McRobb and Farmer Requirements Capture Based on Chapter 6 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Refining the Requirements Model
CM602: Effective Systems Development Principles of Implementation Components Component and Deployment Diagrams.
IS0514 Lecture - Week 2 Best Practice Development Methodology.
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 4 - System modelling Dr Richard Clayton.
Modelling information systems
Software Development Processes
1 WXGC6102: Object-Oriented Techniques Modelling Concepts References: Chapter 5 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design.
IS0514Slide 1 IS0514 Lecture - Week 1 (Semester 2) Business Systems Development Tools and Techniques.
Systems Analysis and Design in a Changing World, 3rd Edition
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Object-Oriented Analysis and Design Fall 2009.
1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
03/12/2001 © Bennett, McRobb and Farmer 2005 Refining the Requirements Model Based on Chapter 8 of Bennett, McRobb and Farmer: Object Oriented Systems.
© Bennett, McRobb and Farmer Avoiding the Problems Based on Chapter 3 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design.
© 2010 Bennett, McRobb and Farmer1 Development Process Based on Chapter 5 Bennett, McRobb and Farmer Object Oriented Systems Analysis and Design Using.
 What is Modeling What is Modeling  Why do we Model Why do we Model  Models in OMT Models in OMT  Principles of Modeling Principles of Modeling 
© 2010 Bennett, McRobb and Farmer1 Object Interaction – Interaction Overview Diagrams Timing Diagrams Based on Chapter 09 Bennett, McRobb and Farmer Object.
UML as a Specification Language for Embedded Systems. By, Mir Ahmed Ali, Asst. Professor, ECM department, SNIST. By, Prof. Narsiah sir, Director of School.
© 2010 Bennett, McRobb and Farmer1 Requirements Analysis 2: Realizing Use Cases Based on Chapter 7 of Bennett, McRobb and Farmer: Object Oriented Systems.
03/12/2001 © Bennett, McRobb and Farmer Modelling Concepts Based on Chapter 5 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 1: Introduction.
Week 04 Object Oriented Analysis and Designing. What is a model? A model is quicker and easier to build A model can be used in simulations, to learn more.
© Bennett, McRobb and Farmer 2005
Models and Diagrams. Models A model is an abstract representation of something real or imaginary. Like a map, a model represents something A useful model.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Object Oriented Analysis and Design Introduction to Rational Rose.
UML. Model An abstract representation of a system. Types of model 1.Use case model 2.Domain model 3.Analysis object model 4.Implementation model 5.Test.
WELCOME TO OUR PRESENTATION UNIFIED MODELING LANGUAGE (UML)
Chapter 5 – System Modeling 1. Systems and the Real World A real-world situation or problem Thinks about Makes comparisons A system that helps to understand.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 14 Slide 1 Object-Oriented Design.
Development Process Based on Chapter 5 Bennett, McRobb and Farmer
Use Case Analysis Chapter 6.
Introduction to UML.
Object Interaction – Interaction Overview Diagrams Timing Diagrams
Chapter 4: Business Process and Functional Modeling, continued
Modelling Concepts Based on Chapter 5 Bennett, McRobb and Farmer
Systems Analysis and Design With UML 2
Introduction to Unified Modeling Language (UML)
Use Case Analysis Chapter 5.
System Modeling Chapter 4
Business System Development
Introduction to UML.
IS0514 Lecture Week 3 Use Case Modelling.
Object Interaction – Sequence Diagrams
Refining the Requirements Model
Presentation transcript:

03/12/2001 © Bennett, McRobb and Farmer Modelling Concepts Based on Chapter 5 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design Using UML, (2 nd Edition), McGraw Hill, 2002.

© Bennett, McRobb and Farmer In This Lecture You Will Learn: n What is meant by a model n The distinction between a model and a diagram n The UML concept of a model

© Bennett, McRobb and Farmer What is a Model n Like a map, a model represents something else n A useful model has the right level of detail and represents only what is important for the task in hand n Many things can be modelled: bridges, traffic flow, buildings, economic policy

© Bennett, McRobb and Farmer Why Use a Model? n A model is quicker and easier to build n A model can be used in a simulation n A model can evolve as we learn n We can choose which details to include in a model n A model can represent real or imaginary things from any domain

© Bennett, McRobb and Farmer Modelling Organizations Organizations are human activity systems. n The situation is complex n Stakeholders have different views n We have to model requirements accurately, completely and unambiguously n The model must not prejudge the solution

© Bennett, McRobb and Farmer What is a Diagram? n Abstract shapes are used to represent things or actions from the real world n Diagrams follow rules or standards n The standards make sure that different people will interpret the diagram in the same way 40°

© Bennett, McRobb and Farmer An Example of a Diagram n An activity diagram of the tasks involved in producing a book. Write Chapter Review Chapter AuthorPrinterTypesetterReviewer Typeset Book Correct Proofs Reset Book Print Book [book complete] [book not complete] Revise Chapter

© Bennett, McRobb and Farmer Write Chapter Review Chapter AuthorPrinterTypesetterReviewer Typeset Book Correct Proofs Reset Book Print Book [book complete] [book not complete] Revise Chapter Hiding Detail Plan Chapter Produce First Draft Revise Draft [satisfied] [not satisfied] Add Exercises Add References to Bibliography Write Chapter

© Bennett, McRobb and Farmer Diagrams in UML n UML diagrams consist of: –icons –two-dimensional symbols –paths –Strings n UML diagrams are defined in the UML specification. Plan Chapter Produce First Draft Revise Draft [satisfied] [not satisfied] Add Exercises Add References to Bibliography Write Chapter

© Bennett, McRobb and Farmer Diagrams vs Models n A diagram illustrates some aspect of a system. n A model provides a complete view of a system at a particular stage and from a particular perspective. n A model may consist of a single diagram, but most consist of many related diagrams and supporting data and documentation.

© Bennett, McRobb and Farmer Examples of Models n Requirements Model –complete view of requirements –may include other models, such as a Use Case Model –includes textual description as well as sets of diagrams

© Bennett, McRobb and Farmer Examples of Models n Behavioural Model –shows how the system responds to events in the outside world and the passage of time –an initial model may just use Collaboration Diagrams –a later model will include Sequence Diagrams and Statecharts

© Bennett, McRobb and Farmer Models in UML n A system is the overall thing that is being modelled n A sub-system is a part of a system consisting of related elements n A model is an abstraction of a system or sub-system from a particular perspective n A model is complete and consistent at the chosen level of abstraction

© Bennett, McRobb and Farmer Models in UML n Different models present different views of the system, for example: –use case view –design view –process view –implementation view –deployment view (Booch et al., 1999)

© Bennett, McRobb and Farmer Packages, Sub-systems and Models n UML has notation for showing sub- systems and models, and also for packages, which are a mechanism for organising models (e.g. in CASE tools) Use CasesUse Case Model Campaign Management PackageModelSub-system

© Bennett, McRobb and Farmer Developing Models n During the life of a project using an iterative life cycle, models change along the dimensions of: –abstraction—they become more concrete –formality—they become more formally specified –level of detail—additional detail is added as understanding improves

© Bennett, McRobb and Farmer Development of the Use Case Model Iteration 1 Obvious use cases. Simple use case descriptions. Iteration 2 Additional use cases. Simple use case descriptions. Prototypes. Iteration 3 Structured use cases. Structured use case descriptions. Prototypes. Spring Jewellery Campaign 1997 Spring Jewellery Campaign 2001 Spring Jewellery Campaign 2002 Summer Collection 1998 OKQuit Campaign: Campaign Selection Holborn Motors Lynch Properties Yellow Partridge Zeta Systems Client: Yellow Partridge Spring Jewellery Campaign 1997 Spring Jewellery Campaign 2001 Spring Jewellery Campaign 2002 Summer Collection 1998 OKQuit Campaign: Campaign Selection Holborn Motors Lynch Properties Yellow Partridge Zeta Systems Client: Yellow Partridge Spring Jewellery Campaign 2002 OKQuit Campaign: Campaign Selection Holborn Motors Lynch Properties Yellow Partridge Zeta Systems Client: Spring Jewellery Campaign 1997 Spring Jewellery Campaign 2001 Spring Jewellery Campaign 2002 Summer Collection 1998 OKQuit Campaign: Campaign Selection Holborn Motors Lynch Properties Yellow Partridge Zeta Systems Client: Yellow Partridge Spring Jewellery Campaign 1997 Spring Jewellery Campaign 2001 Spring Jewellery Campaign 2002 Summer Collection 1998 OKQuit Campaign: Campaign Selection Holborn Motors Lynch Properties Yellow Partridge Zeta Systems Client: Yellow Partridge Spring Jewellery Campaign 2002 OKQuit Campaign: Campaign Selection Holborn Motors Lynch Properties Yellow Partridge Zeta Systems Client:

© Bennett, McRobb and Farmer Summary In this lecture you have learned about: n What is meant by a model n The distinction between a model and a diagram n The UML concept of a model

© Bennett, McRobb and Farmer References n Booch, Rumbaugh and Jacobson (1999) (For full bibliographic details, see Bennett, McRobb and Farmer)