DFP5043

SOFTWARE
REQUIREMENT & DESIGN
CHAPTER 3.1
SOFTWARE MANAGEMENT & DEVELOPMENT:
UNDERSTAND SYSTEM DEVELOPMENT MODEL

LAILATUL AIMI
The real of project management
• https://www.youtube.com/watch?v=7IC6k88Redo
• miss understand requirements
• https://www.youtube.com/watch?v=0YBMfTorE6A
CONTENTS
• 3.2 Understanding System Development Models
• 3.2.1 Explain the importance of Software development
models
• 3.2.2 Discuss different types of models based on
fundamentals software modeling perspectives of context,
interaction, structure and behavior
• a. context models
• b. Interaction Models
• c. Structural Models
• d. Behaviour Models
Important of software development modelling
software modeling
perspectives of

context,
interaction,
structure and
behaviour
Structure diagrams
Structure diagrams show the static structure of the system and its parts on different
abstraction and implementation levels and how they are related to each other. The elements
in a structure diagram represent the meaningful concepts of a system, and may include
abstract, real world and implementation concepts, there are seven types of structure
diagram as
• Class Diagram
• Component Diagram
• Deployment Diagram
• Object Diagram
• Package Diagram
• Composite Structure Diagram
• Profile Diagram
Behaviour diagrams
• Behavior diagrams show the dynamic behavior of the objects in a system,
which can be described as a series of changes to the system over time, there
are seven types of behavior diagrams as follows:
• Use Case Diagram
• Activity Diagram
• State Machine Diagram
• Sequence Diagram
• Communication Diagram
• Interaction Overview Diagram
• Timing Diagram
• Testing team : funny video https://
www.youtube.com/watch?v=mSZp5qrehus

• Developer tic toc: https://www.youtube.com/watch?v=yQdwCiSbLyY

 Class diagram
• Classes: A template for creating objects and implementing
behavior in a system. In UML, a class represents an object
or a set of objects that share a common structure and
behavior. They're represented by a rectangle that includes
rows of the class name, its attributes, and its operations. 
• Name: The first row in a class shape.
• Attributes: The second row in a class shape. Each attribute
of the class is displayed on a separate line.
• Methods: The third row in a class shape. Also known as
operations, methods are displayed in list format with each
operation on its own line.
Class diagram
• Basic components of a class diagram
• The standard class diagram is composed of three sections:
• Upper section: Contains the name of the class. This section is always
required, whether you are talking about the classifier or an object.
• Middle section: Contains the attributes of the class. Use this section
to describe the qualities of the class. This is only required when
describing a specific instance of a class.
• Bottom section: Includes class operations (methods). Displayed in
list format, each operation takes up its own line. The operations
describe how a class interacts with data.
Class diagram for an ATM system

• ATMs are deceptively simple:

although customers only need to
press a few buttons to receive
cash, there are many layers of
security that a safe and effective
ATM must pass through to
prevent fraud and provide value
for banking customers. The
various human and inanimate
parts of an ATM system are
illustrated by this easy-to-read
diagram—every class has its
title, and the attributes are listed
beneath.
Class diagram for a hotel management
system
Benefits of class diagrams
Class diagrams offer a number of benefits for any organization. Use UML class
diagrams to:

• Illustrate data models for information systems, no matter how simple or

complex.
• Better understand the general overview of the schematics of an application.
• Visually express any specific needs of a system and disseminate that
information throughout the business.
• Create detailed charts that highlight any specific code needed to be
programmed and implemented to the described structure.
• Provide an implementation-independent description of types used in a
system that are later passed between its components.
 Discuss different types of models
https://slideplayer.com/slide/4802047/

extra notes: https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-uml/

a. Context models
b. Interaction Models
c. Structural Models
d. Behaviour Models
Context Model
Interaction model
Interaction models
A sequence diagram is a type of interaction diagram because
it describes how—and in what order—a group of objects works together.
How to draw sequence diagram
• https://www.youtube.com/watch?v=XIQKt5Bs7II

• How to draw sequence diagram for ATM situation.

https://www.youtube.com/watch?v=A9FgSncMXz0
Structure Model
Structure models
Behaviour models
Behaviour models
Activity diagram
• Activity diagram is
basically a flowchart to
represent the flow from
one activity to another
activity. The activity can
be described as an
operation of the
system.
events

State machine diagrams can also be used to express the usage protocol of part of a system.
 State machine models
"A state is an abstraction of the attribute values and links of an
object. Sets of values are grouped together into a state according
to properties that affect the gross behaviour of the object."

•A state machine diagram

describes all events (and states
and transitions for a single
object)

•A sequence diagram describes

the events for a single
interaction across all objects
involved
• Funny about development project: https://
www.youtube.com/watch?v=LIy_Y-4V2w0

• FAIL YOUR WAY TO SUCCESS - Motivational Video

on Never Giving Up
• https://www.youtube.com/watch?v=_uL6NP38hbk