Slide 1 Chapter 7 Structural Modeling. Slide 2 Key Ideas A structural or conceptual model describes the structure of the data that supports the business.

Slides:



Advertisements
Similar presentations
Systems Analysis and Design with UML Version 2.0, Second Edition
Advertisements

UML an overview.
UML (cont.) “The Unified Modeling Language User Guide” by G. Booch, J. Rumbaugh and I. Jacobson ● Classes ● Relationships ● Class diagrams ● Examples.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 12Slide 1 Software Design l Objectives To explain how a software design may be represented.
Object-oriented modeling Class/Object Diagrams
Stereotypes Stereotypes provide the capability to create a new kind of modeling element. –They can be used to classify or mark modeling elements. –A type.
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
UML Class Diagram. UML Class Diagrams2 Agenda What is a Class Diagram? Essential Elements of a UML Class Diagram Tips.
Object-Oriented Analysis and Design
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
Lecture 4 Class Responsibility Collaboration Cards
7M701 1 Class Diagram advanced concepts. 7M701 2 Characteristics of Object Oriented Design (OOD) objectData and operations (functions) are combined 
PowerPoint Presentation for Dennis, Wixom & Tegarden Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
Requirements Analysis 2 What objects collaborate to achieve the goal of a use case?
Sharif University of Technology1 Design and Use-case Realization Software Engineering Laboratory Fall 2006.
Classes Chapter 4. Terms and Concepts A class is a description of a set of objects that share the same attributes, operations, relationships, and semantics.
PowerPoint Presentation for Dennis, Wixom & Tegarden Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
Prof. Dr. Nizamettin AYDIN
ZEIT2301 Design of Information Systems Structural Design: Class Diagrams School of Engineering and Information Technology Dr Kathryn Merrick.
1 A Student Guide to Object- Orientated Systems Chapter 4 Objects and Classes: the basic concepts.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 8 Slide 1 Chapter 9 Structuring System Data Requirements.
Unified Modeling Language, Version 2.0
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 4th Edition Copyright © 2012 John Wiley & Sons, Inc. All rights.
R McFadyen Chapter 7 Conceptual Data Modeling.
CSIS3600 Systems Analysis and Design Class Identification and Class Diagrams.
Structural Modeling Chapter 7
Slide 1 Structural Modeling Chapter 7. Slide 2 Key Ideas A structural or conceptual model describes the structure of the data that supports the business.
Object oriented classification Classification is the process of checking to see if an object belongs to a category or a class, is regarded as a basic attribute.
Structural Modeling. Objectives O Understand the rules and style guidelines for creating CRC cards, class diagrams, and object diagrams. O Understand.
CS3773 Software Engineering Lecture 04 UML Class Diagram.
7-1 © Prentice Hall, 2004 Chapter 7: Conceptual Data Modeling Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
7-1 © Prentice Hall, 2007 Chapter 7: Conceptual Data Modeling Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 15: Object-Oriented Data Modeling Modern Database Management 9 h Edition Jeffrey A.
Unit 3 Conceptual Data Modeling. Key Concepts Conceptual data modeling process Classes and objects Attributes Identifiers, candidate keys, and primary.
Databases : Data Modeling 2007, Fall Pusan National University Ki-Joune Li.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 03. Classes,
UML Class Diagram Trisha Cummings. What we will be covering What is a Class Diagram? Essential Elements of a UML Class Diagram UML Packages Logical Distribution.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Haley Wixom, and David Tegarden Chapter 7: Structural Modeling.
Lecture 6: Structural Modeling
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
What is a Structural Model?
Structural Modeling Chapter 7. Key Ideas A structural or conceptual model describes the structure of the data that supports the business processes in.
1 Structural Modeling Chapter 7. 2 Key Ideas A structural or conceptual model describes the structure of the data that supports the business processes.
Design Model Lecture p6 T120B pavasario sem.
Domain Classes – Part 1.  Analyze Requirements as per Use Case Model  Domain Model (Conceptual Class Diagram)  Interaction (Sequence) Diagrams  System.
Chapter 17 – Object- Oriented Design. Chapter Goals To learn about the software life cycle To learn about the software life cycle To learn how to discover.
Class Diagram Chapter 21 Applying UML and Patterns Craig Larman.
PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Haley Wixom, and David Tegarden Chapter 7: Structural Modeling.
CS212: Object Oriented Analysis and Design Lecture 33: Class and Sequence Diagram.
Class diagrams Terézia Mézešová.
Structural Modeling. Introduction A Structural model is a formal way of representating the objects that are used and created by a business system One.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Haley Wixom, and David Tegarden Chapter 7: Structural Modeling.
Object Oriented Programming and Data Abstraction Earl Huff Rowan University.
Class Diagrams Revisited. Parameterized Classes Parameterized Classes - are used to represent relationships between templates.
Chapter 5: Structural Modeling
Systems Analysis and Design with UML Version 2.0, Second Edition
Structural Modeling.
Chapter 5: Structural Modeling
Advanced Java Programming
Object Oriented Analysis and Design
Domain Class Diagram Chapter 4 Part 2 pp
تحليل انظمة و تصميمها الوحدة الخامسة أ.محمد زكي شبير.
INFS 6225 Object Oriented Systems Analysis & Design
SYS466 Domain Classes – Part 1.
Understand and Use Object Oriented Methods
Copyright 2007 Oxford Consulting, Ltd
System Analysis and Design
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Presentation transcript:

Slide 1 Chapter 7 Structural Modeling

Slide 2 Key Ideas A structural or conceptual model describes the structure of the data that supports the business processes in an organization.. The structure of data used in the system is represented through CRC cards, class diagrams, and object diagrams.

Slide 3 STRUCTURAL MODELS

Slide 4 Purpose of Structural Models Reduce the “semantic gap” between the real world and the world of software Create a vocabulary for analysts and users Represent things, ideas, and concepts of importance in the application domain

Slide 5 Classes Templates for creating instances or objects Concrete Abstract Typical examples: Application domain, user interface, data structure, file structure, operating environment, document, and multimedia classes

Slide 6 Attributes Units of information relevant to the description of the class Only attributes important to the task should be included

Slide 7 Operations Action that instances/objects can take Focus on relevant problem- specific operations (at this point)

Slide 8 Relationships Generalization Enables inheritance of attributes and operations Aggregation Relates parts to wholes Association Miscellaneous relationships between classes

Slide 9 CLASS-RESPONSIBILITY- COLLABORATION CARDS

Slide 10 Responsibilities and Collaborations Responsibilities Knowing Doing Collaboration Objects working together to service a request

Slide 11 A CRC Card

Slide 12 Back of CRC Card

Slide 13 CLASS DIAGRAMS

Slide 14 Example Class Diagram

Slide 15 Class Diagram Syntax A CLASS AN ATTRIBUTE AN OPERATION AN ASSOCIATION Class 1 -attribute +operation () Attribute name/ derived attribute name operation name () 1..*0..1 ______verb phrase____

Slide 16 More on Attributes Derived attributes /age, for example can be calculated from birth date and current date Visibility Public Protected Private

Slide 17 More on Operations Constructor Creates object Query Makes information about state available Update Changes values of some or all attributes

Slide 18 Generalization and Aggregation Generalization shows that a subclass inherits from a superclass Doctors, nurses, admin personnel are kinds of employees Aggregation classes comprise other classes Health team class comprised of doctor, nurses, admin personnel classes

Slide 19 More on Relationships Class can be related to itself (role) Multiplicity Exactly one, zero or more, one or more, zero or one, specified range, multiple disjoint ranges Association class

Slide 20 Simplifying Class Diagrams The view mechanism shows a subset of information Packages show aggregations of classes (or any elements in UML)

Slide 21 Object Diagrams

Slide 22 CREATING CRC CARDS AND CLASS DIAGRAMS

Slide 23 Object Identification Textual analysis of use-case information Nouns suggest classes Verbs suggest operations Creates a rough first cut Common object list Incidents Roles

Slide 24 Patterns Useful groupings of classes that recur in various situations Transactions Transaction class Transaction line item class Item class Location class Participant class

Slide 25 Steps for Object Identification and Structural Modeling 1. Create CRC cards by performing textual analysis on the use-cases. 2. Brainstorm additional candidate classes, attributes, operations, and relationships by using the common object list approach. 3. Role-play each use-case using the CRC cards. 4. Create the class diagram based on the CRC cards. 5. Review the structural model for missing and/or unnecessary classes, attributes, operations, and relationships. 6. Incorporate useful patterns. 7. Review the structural model.

Slide 26 Create CRC cards. Examine common object lists. Role-play the CRC cards. Create the class diagram. Review the class diagram. Incorporate patterns. Review the model.

Slide 27

Slide 28

Slide 29 Summary CRC cards capture the essential elements of a class. Class and object diagrams show the underlying structure of an object- oriented system. Constructing the structural model is an iterative process involving: textual analysis, brainstorming objects, role playing, creating the diagrams, and incorporating useful patterns.