Title: Modeling System Requirements:
1- Chapter 5
- Modeling System Requirements
- Events and Things
- Part 2
2Things and System Requirements
- Things define what information the system needs
to store - Things become models in the analysis phase
- In the traditional approach, they become data
entities - In the object-oriented approach they become
Objects -
3Types of Things
4Developing an Initial List of Things
- Step 1 Identify all nouns about the system
- Use the event table
- Step 2 Define all types/categories of
information needed - Augment event list with information from current
systems, forms, other documents - Step 3 Refine list and record assumptions or
issues to explore - Is this a thing that the system needs to know
about (e.g., product inquiry)? - In scope?
- System needs to remember more than one?
- Look for and eliminate synonyms
- Eliminate things that system outputs (e.g.,
reports) - Eliminate things that are inputs that you record
information from (e.g., a form)
5Characteristics of Things
- Once list of things finalized, need to define
characteristics of each thing. - Relationships
- Attributes
6Relationships Naturally Occur Between Things
- Naturally occurring association among specific
things - Occur in two directions
- Cardinality/multiplicity
- Types
- Binary
- Unary (recursive),
- Ternary
- n-ary
7Attributes and Values
- Attribute
- One specific piece of information about a thing
- Primary key special type of attribute that
uniquely identifies a specific thing
8Data Entities
- Things the system needs to store data about in
traditional IS approach - Modeled with entity-relationship diagram
- Generally used with relational database
development - Single occurrence of an entity instance
9Simple ERD
Each data entity has a set of attributes,
including primary key (unique identifier)
10Cardinality Symbols of Relationships
11Objects
- Do the work in the system and store information
- Behaviors and attributes
- Class Type of thing
- Object Specific thing
- Methods Behaviors of objects
12Class Diagram
- Classes objects rather than data entities
13Bank Account System Class Diagram
14Aggregation or Whole-Part Relationships
15Data Entities Compared with Objects
16Example Student Enrolls in Course
What data entities would be involved? What are
relationships?