BIT 1160

SYSTEMS ANALYSIS
AND DESIGN
MR LISTONE KAPUTULA
Systems Analysis and Design
Introduction
Project Initiation
Requirements Gathering
Process Modeling
Data Modeling
System Design
System Implementation
Project Management in Systems Development
Agile and Iterative Development
Emerging Trends in SAD
Data Modelling
Overview
Model
An abstraction (simplified representation) of a
real-world object or event
Useful in understanding complexities of the real-
world environment
Data model
A diagram that displays a set of tables and the
relationships between them.
The process includes three main designs:
conceptual, logical, and physical data models.
Data Modelling
Overview
Model
Data Modelling
Data Model
Conceptual Data Model:
Provides a high-level, abstract view of the entire
data environment.
Focuses on entities, attributes, and relationships
between them.
Independent of specific database management
systems (DBMS).
Used to capture business requirements and
concepts.
Data Modelling
Data Model
Logical Data Model:
Translates the conceptual data model into a more
detailed representation.
Aligned with underlying database technology.
Defines the structure of data using tables,
columns, keys, and relationships.
Typically represented using entity-relationship
diagrams or relational data models.
Data Modelling
Data Model
Physical Data Model:
Refines the logical data model by specifying
physical implementation details.
Defines storage structures, indexing mechanisms,
and optimization techniques.
Represents how data will be stored and accessed
in the actual database system.
Considers performance, scalability, and security
aspects.
Data Modelling

Data modeling
Data modeling is a process of creating a visual
representation of data structures required for a
database.
This process helps to articulate the characteristics
of data, business rules, and how information is
organized within the database.
Data modeling includes defining data, relationships
between data, meanings, and limitations.
Identify what data is important
Identify what data should be maintained
Data Modelling

Data modeling
There are various approaches to modeling data
depending on the requirements, complexity, and
nature of the system.
Here are some different approaches to data
modeling:
Entity-relationship modeling*
Relational modeling,
Dimensional modeling,
Object-oriented modeling,
Graph modeling, etc.
Data Modelling

Entity-Relationship (ER) Model

The major activity of this phase is identifying
entities, attributes, and their relationships to
construct model using the Entity Relationship
Diagram.
Entity table
Attribute column
Relationship line
Entity-Relationship Diagrams (ERDs) are graphical
representations used to model the data schema of
a system.
Data Modelling

Entity-Relationship (ER) Model

The
Data Modelling

Entity-Relationship (ER) Model

How to find entities?
Entity:
"...anything (people, places, objects, events,
etc.) about which we store information (e.g.
supplier, machine tool, employee, utility pole,
airline seat, etc.).”
Tangible: customer, product
Intangible: order, accounting receivable
Look for Common nouns, good candidate
BUT a proper noun is not a good candidate….
Data Modelling

Entity-Relationship (ER) Model

How to find attributes?
Attribute:
Attributes are data objects that either identify or
describe entities (properties of an entity).
It is a descriptor whose values are associated
with individual entities of a specific entity type
The process for identifying attributes is
similar except now you want to look for and
extract those names that appear to be
descriptive noun phrases.
Data Modelling

Entity-Relationship (ER) Model

What can you identify?
Data Modelling

Entity-Relationship (ER) Model

Entity instance: a single occurrence of an entity.
we have 6 instances
Data Modelling

Entity-Relationship (ER) Model

How to find relationships?
Relationship:
Relationships are associations between entities.
Typically, a relationship is indicated by a verb
connecting two or more entities.
Employees are assigned to projects
Relationships should be classified in terms of
cardinality.
One-to-one, one-to-many, etc.
Data Modelling

Entity-Relationship (ER) Model

How to find cardinalities?
Cardinality:
The cardinality is the number of occurrences in
one entity which are associated to the number of
occurrences in another.
There are three basic cardinalities (degrees of
relationship).
one-to-one (1:1), one-to-many (1:M), and many-
to-many (M:N)
Data Modelling

Entity-Relationship (ER) Model

Cardinality Constraints
One-to-one (1-to-1). Each entity in E1 is
associated with 0 or one entity in E2, and vice
versa.
Data Modelling

Entity-Relationship (ER) Model

Cardinality Constraints
One-to-many (1-to-m): Each entity in E1 is
associated with zero or more entities in E2, and
each entity in E2 is associated with at most one
entity in E1.
Data Modelling

Entity-Relationship (ER) Model

Cardinality Constraints
Many-to-many (m-to-n). Each entity in E1 is
associated with 0 or more entities in E2, and
vice versa.
Data Modelling

Entity-Relationship (ER) Model

Basic Cardinality Type
Data Modelling

Entity-Relationship (ER) Model

Example model
Data Modelling

Entity-Relationship (ER) Model

Designing ERDs:
Gather requirements: Collect and analyze the
requirements for the system or database.
Identify entities and attributes: Identify the
main entities and their attributes based on the
requirements.
Define relationships: Establish the
relationships between entities based on how
they interact with each other.
Data Modelling

Entity-Relationship (ER) Model

Designing ERDs:
Draw the ERD: Use symbols and notation to
create a graphical representation of the data
model, including entities, attributes, and
relationships.
Validate and refine: Review the ERD to ensure
it accurately reflects the system requirements
and refine as needed.
Data Modelling

Entity-Relationship (ER) Model

Student Enrollment System ERD:
Draw
Data Modelling

UML First Pass

A preliminary or initial stage of using the Unified
Modeling Language (UML) in software development
or system design.
Activities such as:
Requirement Analysis: Gathering and
understanding requirements for the system.
Conceptual Modeling: Creating high-level UML
diagrams to capture the overall structure and
functionality of the system.
Use Case Diagrams: Identifying actors and use
cases to represent system interactions.
Data Modelling

UML First Pass

Class Diagrams: Modeling the static structure of
the system, including classes, attributes, and
relationships.
Sequence Diagrams: Describing the flow of
interactions between objects or components over
time.
Activity Diagrams: Representing workflows or
processes within the system.
State Machine Diagrams: Modeling the behavior
of individual objects or components in response
to different events or states.
Data Modelling

UML First Pass

Use case diagrams
Use case diagrams represent the functionality of
the system from user’s point of view
Data Modelling

UML First Pass

Components of the Use Case Diagrams
Actors: Represent users or external systems interacting
with the system.
Use Cases: Describe specific functionalities or behaviors
provided by the system.
Relationships:
Associations: Show interactions between actors and
Use Cases.
Others: Inclusions and Generalizations
System Boundary: Defines the scope of the system being
modeled, enclosing actors and Use Cases.
Data Modelling

UML First Pass

Class diagrams
Class diagrams represent the structure of the
system
Data Modelling

UML First Pass

Sequence diagram
Represent the behavior of a system as messages
(“interactions”) between different objects
Data Modelling

UML First Pass

Statechart diagrams
Represent behavior of a single object
with interesting dynamic behavior.
Data Modelling

UML First Pass

Activity diagrams
Sequence in which activities are performed and
the conditions or triggers that initiate each activity.
Systems Analysis and Design
Introduction
Project Initiation
Requirements Gathering
Process Modeling
Data Modeling
System Design
System Implementation
Project Management in Systems Development
Agile and Iterative Development
Emerging Trends in SAD