Modelling Concepts Based on Chapter 5 Bennett, McRobb and Farmer

Slides:



Advertisements
Similar presentations
COMP1007 Introduction to Requirements Analysis © Copyright De Montfort University 2002 All Rights Reserved COMP1007 Introduction to Requirements Analysis.
Advertisements

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.
Requirements Analysis 8. 1 Storyboarding b508.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis Human.
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.
03/12/2001 © Bennett, McRobb and Farmer Modelling Concepts Based on Chapter 5 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and.
IMS1805 Systems Analysis Topic 3: Doing Analysis (continued from previous weeks)
03/12/2001 © Bennett, McRobb and Farmer Activity Diagrams Based on Chapter 5 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and.
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.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
System Analysis & Design
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 4 - System modelling Dr Richard Clayton.
A Development Process Lecture Oo13 Objectory based method.
1 WXGC6102: Object-Oriented Techniques Modelling Concepts References: Chapter 5 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design.
Systems Analysis and Design in a Changing World, 3rd Edition
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
© 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 
2 2009/10 Object Oriented Technology 1 Topic 2: Introduction to Object-Oriented Approach Reference: u Ch.16 Current Trends in System Development (Satzinger:
© 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.
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)
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
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
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
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.
Diagrams. Typically, we view the static parts of a system using one of the four following diagrams. 1. Class diagram 2. Object diagram 3. Component diagram.
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.
1 Team Skill 3 Defining the System Part 1: Use Case Modeling Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and.
Development Process Based on Chapter 5 Bennett, McRobb and Farmer
Chapter 5 – System Modeling
Use Case Analysis Chapter 6.
Fundamentals of Object Oriented Modeling
Introduction to UML.
Systems Analysis and Design in a Changing World, Fourth Edition
Object Interaction – Interaction Overview Diagrams Timing Diagrams
Chapter 4: Business Process and Functional Modeling, continued
Software Engineering Lecture 4 System Modeling The Analysis Stage.
Chapter 5 – System Modeling
Object-Oriented Analysis and Design
What is UML? What is UP? [Arlow and Neustadt, 2005] October 5, 2017
Systems Analysis and Design With UML 2
Unified Modeling Language
System Modeling Chapter 4
Business System Development
The Object Oriented Approach to Design
CSE 303 – Software Design and Architecture
Object-Oriented Design
Informatics 121 Software Design I
Introduction to UML.
Object oriented analysis and design
Appendix A Object-Oriented Analysis and Design
IS0514 Lecture Week 3 Use Case Modelling.
Object Interaction – Sequence Diagrams
Rational Rose 2000 Instructor Notes Use Case Realization Structure
Appendix 3 Object-Oriented Analysis and Design
Refining the Requirements Model
Presentation transcript:

Modelling Concepts Based on Chapter 5 Bennett, McRobb and Farmer Object Oriented Systems Analysis and Design Using UML 4th Edition, McGraw Hill, 2010 © 2010 Bennett, McRobb and Farmer

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

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

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

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

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

© 2010 Bennett, McRobb and Farmer Write Chapter Review Chapter Author Printer Typesetter Reviewer Typeset Book Correct Proofs Reset Book Print Book [book complete] [book not complete] Revise Chapter An Example of a Diagram An activity diagram of the tasks involved in producing a book. This is a diagram of producing a book. It is highly simplified! © 2010 Bennett, McRobb and Farmer

© 2010 Bennett, McRobb and Farmer Write Chapter Review Chapter Author Printer Typesetter Reviewer 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 This is meant to be a magnifying glass! It is looking into the Write Chapter activity to show a lower level of detail. Switch of the animation if you don’t like it. You can make the point, made in the book, that these activities could be broken down further, but it may not be useful to do so. There are also activities, such as Stare out of Window, Make Coffee, Change CD (all of which I have just done) that are essential to the process of writing, but represent unnecessary detail. (You could make the point that there might be other purposes for which these would be relevant. For example, someone studying the creative process or a time and motion study of how productively authors use their time.) © 2010 Bennett, McRobb and Farmer

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

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

Relationship between Models and Diagrams Use Case Diagrams are one view of the Use Case Model in the Requirements Model Requirements Model Use Cases Interface Prototypes Requirements List Initial System Architecture Model Glossary Use Case Model Use Case Diagrams One View of the Use Case Model © 2010 Bennett, McRobb and Farmer

© 2010 Bennett, McRobb and Farmer Examples of Models 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 © 2010 Bennett, McRobb and Farmer

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

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

© 2010 Bennett, McRobb and Farmer Models in UML 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) © 2010 Bennett, McRobb and Farmer

Packages, Sub-systems and Models UML has notation for showing subsystems and models, and also for packages, which are a mechanism for organising models (e.g. in CASE tools) Use Cases Use Case Model «subsystem» Campaign Management Package Sub-system Model © 2010 Bennett, McRobb and Farmer

© 2010 Bennett, McRobb and Farmer Developing Models 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 © 2010 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. OK Quit Campaign: Campaign Selection Zeta Systems Yellow Partridge Lynch Properties Holborn Motors Client: In a system development project that uses an iterative life cycle, different models that represent the same view may be developed at different levels of detail as the project progresses. For example, the first use case model of a system may show only the obvious use cases that are apparent from the first iteration of requirements capture. After a second iteration, the use case model may be elaborated with more detail and additional use cases that emerge from discussion of the requirements. Some prototypes may be added to try out ideas about how users will interact with the system. After a third iteration, the model will be extended to include more structured descriptions of how the users will interact with the use cases and with relationships among use cases. (Use cases are explained in Chapter 6.) The number of iterations is not set at three. Any phase in a project will consist of a number of iterations, and that number will depend on the complexity of the system being developed. Iteration 3 Structured use cases. Structured use case descriptions. Prototypes. OK Quit Campaign: Campaign Selection Yellow Partridge Lynch Properties Holborn Motors Zeta Systems Client: © 2010 Bennett, McRobb and Farmer

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

© 2010 Bennett, McRobb and Farmer References Booch, Rumbaugh and Jacobson (1999) Bennett, Skelton and Lunn (2005) (For full bibliographic details, see Bennett, McRobb and Farmer) © 2010 Bennett, McRobb and Farmer