systems analysis and design in a changing world, tuesday, feb 27
TRANSCRIPT
![Page 1: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/1.jpg)
Systems Analysis and Design in a Changing World, Tuesday, Feb 27
![Page 2: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/2.jpg)
2
Today’s Schedule
Domain Model Class Diagram Hierarchies in OO Classes Class Diagram Notation For Thursday, March 1
Try out ERDs & Class Diagrams in Visual Paradigm
![Page 3: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/3.jpg)
3
Recall … Where We Are Headed
![Page 4: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/4.jpg)
4
Event Table: Catalog of Information about Each Use Case
How do the “events” in Activity Diagram fit?
![Page 5: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/5.jpg)
5
“Things” in Problem Domain
Define system requirements by understanding system information that needs to be stored
Store information about things in the problem domain that people deal with when they do their work
Analysts identify these types of things by considering each use case in the event table
– What things does the system need to know about and store information about?
![Page 6: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/6.jpg)
6
Data Entities Compared to Objects
![Page 7: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/7.jpg)
7
Entity Relationship Diagram
![Page 8: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/8.jpg)
8
The Class Diagram
Unified Modeling Language (UML) diagram Domain model class diagram
– Models things in the users’ work domain– Used to define requirements for OO (very similar
to entities in ERD) Design class diagram
– Models software classes – Adds methods as behaviors – Used in the design activity
![Page 9: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/9.jpg)
9
UML Class Symbol
![Page 10: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/10.jpg)
10
Domain Model Class Diagram
No methods shown in domain model– Domain classes are not software classes
Very similar to ERD in Figure 5-25– UML and domain model can be used in place of ERD in traditional approach
![Page 11: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/11.jpg)
11
UML Multiplicity of Associations
![Page 12: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/12.jpg)
12
UML Domain Class Model
![Page 13: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/13.jpg)
13
More Complex Class Concepts
Generalization/specialization hierarchies– General superclasses to specialized subclasses– Inheritance allows subclasses to share
characteristics of their superclasses
![Page 14: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/14.jpg)
14
A Generalization/Specialization Class Hierarchy for Motor Vehicles
![Page 15: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/15.jpg)
15
Whole-part hierarchies
Object and its parts– Aggregation – parts can exist separately– Composition – parts can’t exist separately
Hand has fingers and thumb
![Page 16: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/16.jpg)
16
RMO Domain Model Class Diagram
![Page 17: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/17.jpg)
17
Design Class Diagram Notation: Software Classes with Methods
![Page 18: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/18.jpg)
18
Course Enrollment Design Class Diagram
![Page 19: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/19.jpg)
19
Summary – Modeling for Requirements
Analysis phase – defines system requirements
Models created to further learning process, reduce complexity, communicate with team members, and document requirements
Many types of models used – Mathematical, descriptive, graphical
![Page 20: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/20.jpg)
20
Summary – Use Events and Things
Key early step in modeling is to identify and list– Events that require a use case in the system – Things users deal with in work environment
Use cases (activities) are identified from user goals and business events that trigger elementary business processes
![Page 21: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/21.jpg)
21
Summary – Identifying Events
Business events occur at a specific time and place– External events, temporal events, and state events
Event table records event, trigger, source, use case, response, and destination– A catalog of information about each use case
![Page 22: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/22.jpg)
22
Summary – Using Things
“Things” are what user deals with and system remembers, such as customer placing an order
Traditional approach uses entity-relationship diagrams (ERD) for data entities, attributes of data entities, and relationships between entities
Object-oriented approach uses UML class diagrams for classes, attributes, methods of class, and associations among classes – Domain model class diagram (requirements activity)– Design class diagram (design activity)
![Page 23: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/23.jpg)
23
Now you try it …
Page 193, #15, Computer Lab– #15 What are the “things” and relationships?
(skip ERD)– #16 Draw a Class Diagram– Now draw it in Visual Paradigm!
![Page 24: Systems Analysis and Design in a Changing World, Tuesday, Feb 27](https://reader035.vdocuments.mx/reader035/viewer/2022062717/56649e215503460f94b0da90/html5/thumbnails/24.jpg)
24
For Thursday, March 1
Be ready to do Case Study Real Estate Multiple Listing Service System (p. 195)
ERDs & Class Diagrams in Visual Paradigm Assignment #7, Due Sunday, March 4