Chapter 5 Domain Model
Terms in this set (21)
a conceptualization process to help the development team understand the application domain.
enables the team to establish a common understanding.
Five steps in domain modeling
1. Collecting information about the application domain
3. Classifying brainstorming results
4. Visualizing the domain model using a UML class diagram
5. Performing inspection and review
What is a model?
a conceptual representation of something.
Why do we need model?
A model facilitates the team members and users to communicate their perception and design ideas.
We need a reference framework for design and implementation.
We need models during the maintenance phase to perform enhancement maintenance.
Types of Models
Use case model
State behavior model
Design class diagram
Use Case Diagram
shows the business processes and their relationships to actors.
UML class diagram (without operations) describing the application domain concepts and relationships.
Domain modeling in the OO paradigm views the real world as consisting of
- that relate to each other, and
- interact with each other
an abstraction of objects with similar properties and behavior
define properties of class of objects
define behaviors of class of objects
an instance of a class
defining/storing together properties and behavior of a class/object
shielding implementation detail to reduce change impact to other part of a program
one thing can assume more than one form
UML Class Diagram
Shows the classes, their attributes and operations, and relationships between the classes.
Domain model is represented by a class diagram without showing the operations.
Every instance of a subclass is also an instance of the superclass.
relationships of a superclass are also relationships of subclasses.
One object is part of another object. Also called part-of relationship.
ex. engine is part of a car
class or attribute
defines properties and operations for an association between two classes.
YOU MIGHT ALSO LIKE...
Academic Word Lists - AWL Sublists
ACCTMIS 4620 Chapter 14
OTHER SETS BY THIS CREATOR
Section 5: Server Based Compute Services
Section 2: AWS Structure and Organization
Section 4: IAM (Identity and Access Management)
Cloud Solutions Architect General Terminology
THIS SET IS OFTEN IN FOLDERS WITH...
Chapter 4 Requirements Elicitation
Chapter 7 Use Case
Chapter 8 Actor-System Interaction Modeling
Chapter 9 Object Interaction Model