Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 - Domain Classes.

Slides:



Advertisements
Similar presentations
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System modeling 2.
Advertisements

Objectives Explain how events can be used to identify use cases that define requirements Identify and analyze events and resulting use cases Explain how.
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
Chapter 14 (Web): Object-Oriented Data Modeling
Overview Objective: refine information gathered
2Object-Oriented Analysis and Design with the Unified Process Events and Use Cases  Use case  Activity the system carries out  Entry point into the.
6. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain how events can be used to identify use cases that define requirements.
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
Chapter 5: Modeling Systems Requirements: Events and Things
1 Web-Enabled Decision Support Systems Entity-Relationship Modeling Prof. Name Position (123) University Name.
Systems Analysis and Design in a Changing World, Tuesday, Feb 27
Modeling System Requirements:
SA Capstone Requirements and Design Week 5 SYST Winter 2013 Instructors: Jerry Kotuba & Joe Varrasso Some slides adapted from: Systems Analysis.
Systems Analysis and Design in a Changing World, Fifth Edition
1 A Student Guide to Object- Orientated Systems Chapter 4 Objects and Classes: the basic concepts.
OBJECT AND CLASES: THE BASIC CONCEPTS Pertemuan 8 Matakuliah: Konsep object-oriented Tahun: 2009.
Entity Relationship Diagrams Objectives s Learn the Elements of the E-R model (entities, attributes, and relationships) s Show how to apply the E-R model.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 8 Slide 1 Chapter 9 Structuring System Data Requirements.
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
SA Capstone Requirements and Design Week 5 SYST Winter 2014
Conceptual Data Modeling. What Is a Conceptual Data Model? A detailed model that shows the overall structure of organizational data A detailed model.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
Systems Analysis and Design in a Changing World, Fifth Edition
UML Diagrams: Class Diagrams The Static Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
R McFadyen Chapter 7 Conceptual Data Modeling.
Association Class Generalization/Specialization Whole-Part Page More Associations 1.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 Domain Classes.
CS3773 Software Engineering Lecture 04 UML Class Diagram.
CHAPTER 13 (ONLINE): OBJECT-ORIENTED DATA MODELING © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1 Modern Database Management 11 th Edition.
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.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN: AN AGILE, ITERATIVE APPROACH SATZINGER.
Unit 3 Conceptual Data Modeling. Key Concepts Conceptual data modeling process Classes and objects Attributes Identifiers, candidate keys, and primary.
7-1 © Prentice Hall, 2007 Week 5: Conceptual Data Modeling Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
Domain Modeling Part2: Domain Class Diagram Chapter 4 pp part 2 1.
© 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 13 (Online): Object-Oriented Data Modeling Modern Database Management 10 th Edition.
CHAPTER 13: OBJECT-ORIENTED DATA MODELING (OVERVIEW) © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1 Modern Database Management 11 th Edition.
1 ITEC 3010 “Systems Analysis and Design, I” LECTURE 5: Modeling System Requirements [Prof. Peter Khaiter]
Jerry KotubaSYST39409-Object Oriented Methodologies1 Object Oriented Methodologies Week05/06.
The Static Analysis Model Class Diagrams Prof. Hany H. Ammar, CSEE, WVU, and Dept. of Computer Science, Faculty of Computers and Information, Cairo University.
Objectives Explain how events can be used to identify use cases that define requirements Identify and analyze events and resulting use cases Explain.
Modeling system requirements. Purpose of Models Models help an analyst clarify and refine a design. Models help simplify the complexity of information.
5 Systems Analysis and Design in a Changing World, Fifth Edition.
Modeling System Requirements: Events and Things. Objectives Explain the many reasons for creating information system models Describe three types of models.
What is a Structural Model?
Object-Oriented Data Modeling
Object Oriented Analysis: Associations. 2 Object Oriented Modeling BUAD/American University Class Relationships u Classes have relationships between each.
Object-Oriented Modeling: Static Models. Object-Oriented Modeling Model the system as interacting objects Model the system as interacting objects Match.
Static Modeling Chapter 8 Part of Requirements Modeling Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
 Week08.  Review Schedule Weeks 8-14  This week o Review last class o Introduce Class Diagrams o ICE-03 Sheridan SYST Engineering Quality Systems.
Exam 1 Review Dr. Bernard Chen Ph.D. University of Central Arkansas.
Chapter 4 Basic Object-Oriented Concepts. Chapter 4 Objectives Class vs. Object Attributes of a class Object relationships Class Methods (Operations)
CHAPTER 13: OBJECT-ORIENTED DATA MODELING (OVERVIEW) Modern Database Management 11 th Edition Jeffrey A. Hoffer, V. Ramesh, Heikki Topi © 2013 Pearson.
Class Diagram Lecture # 1. Class diagram A Class Diagram is a diagram describing the structure of a system shows the system's classes Attributes operations.
Lecture # 14 Chapter # 5 The Relational Data Model and Relational Database Constraints Database Systems.
Class Diagram Associations Class Diagrams, Class Stereotypes, Class Associations Dr. Neal CIS 480.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
5 Chapter 5: Modeling Systems Requirements: Events and Things Systems Analysis and Design in a Changing World.
UML Diagrams: Class Diagrams The Static Analysis Model
Object-Oriented Modeling
DATA REQIREMENT ANALYSIS
Copyright © 2014 Hassan Gomaa and Robert Pettit
Class diagram Description
Domain Class Diagram Chapter 4 Part 2 pp
Software Engineering Lecture #11.
Systems Analysis – ITEC 3155 Modeling System Requirements – Part 2
Database EER.
Presentation transcript:

Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 - Domain Classes

Systems Analysis and Design in a Changing World, 6th Edition 2 Things in the Problem Domain Two Techniques for Identifying them Brainstorming Technique Use a checklist of all of the usual types of things typically found and brainstorm to identify domain classes of each type Noun Technique Identify all of the nouns that come up when the system is described and determine if each is a domain class, an attribute, or not something we need to remember

Systems Analysis and Design in a Changing World, 6th Edition 3 Brainstorming Technique

Systems Analysis and Design in a Changing World, 6th Edition 4 Partial List of Nouns for RMO

Systems Analysis and Design in a Changing World, 6th Edition 5 Details about Domain Classes Attribute— describes one piece of information about each instance of the class Customer has first name, last name, phone number Identifier or key One attribute uniquely identifies an instance of the class. Required for data entities, optional for domain classes. Customer ID identifies a customer Compound attribute Two or more attributes combined into one structure to simplify the model. (E.g., address rather than including number, street, city, state, zip separately). Sometimes an identifier or key is a compound attribute.

Systems Analysis and Design in a Changing World, 6th Edition 6 Attributes and Values Class is a type of thing. Object is a specific instance of the class. Each instance has its own values for an attribute

Systems Analysis and Design in a Changing World, 6th Edition 7 Associations Among Things Association— a naturally occurring relationship between classes (UML term)

Systems Analysis and Design in a Changing World, 6th Edition 8 Minimum and Maximum Multiplicity Associations have minimum and maximum constraints minimum is zero, the association is optional If minimum is at least one, the association is mandatory

Systems Analysis and Design in a Changing World, 6th Edition 9 The Domain Model Class Diagram Class A category of classification used to describe a collection of objects Domain Class Classes that describe objects in the problem domain Class Diagram A UML diagram that shows classes with attributes and associations (plus methods if it models software classes) Domain Model Class Diagram A class diagram that only includes classes from the problem domain, not software classes so no methods

Systems Analysis and Design in a Changing World, 6th Edition 10 A Simple Domain Model Class Diagram Note: This diagram matches the semantic net shown previously A customer places zero or more orders An order is placed by exactly one customer An order consists of one or more order items An order item is part of exactly one order

Systems Analysis and Design in a Changing World, 6th Edition 11 Domain Model Class Diagram for a bank with many branches

Systems Analysis and Design in a Changing World, 6th Edition 12 Domain Model Class Diagram for course enrollment at a university Where is each student’s grade remembered in this model? Each section has many grades and each grade is association with a student Each student has many grades and each grade is association with a section

Systems Analysis and Design in a Changing World, 6th Edition 13 Refined Course Enrollment Model with an Association Class CourseEnrollment Association class— an association that is treated as a class in a many to many association because it has attributes that need to be remembered, such as grade

Systems Analysis and Design in a Changing World, 6th Edition 14 More Complex Issues about Classes: Generalization/Specialization Relationships Generalization/Specialization A hierarchical relationship where subordinate classes are special types of the superior classes. Often called an Inheritance Hierarchy Superclass the superior or more general class in a generalization/specialization hierarchy Subclass the subordinate or more specialized class in a generalization/specialization hierarchy Inheritance the concept that subclasses classes inherit characteristics of the more general superclass

Systems Analysis and Design in a Changing World, 6th Edition 15 Generalization/Specialization Inheritance for RMO Three Types of Sales Abstract class— a class that allow subclasses to inherit characteristics but never gets instantiated. In Italics (Sale above) Concrete class— a class that can have instances

Systems Analysis and Design in a Changing World, 6th Edition 16 Generalization/Specialization Inheritance for the Bank with Special Types of Accounts A SavingsAccount has 4 attributes A CheckingAccount Has 5 attributes Note: the subclasses inherit the associations, too

Systems Analysis and Design in a Changing World, 6th Edition 17 More Complex Issues about Classes: Whole Part Relationships Whole-part relationship— a relationship between classes where one class is part of or a component portion of another class Aggregation— a whole part relationship where the component part exists separately and can be removed and replaced (UML diamond symbol, next slide) Computer has disk storage devices Car has wheels Composition— a whole part relationship where the parts can no longer be removed (filled in diamond symbol) Hand has fingers Chip has circuits

Systems Analysis and Design in a Changing World, 6th Edition 18 Whole Part Relationships Computer and its Parts Note: this is composition, with diamond symbol. Whole part can have multiplicity symbols, too (not shown)