Welcome

System Analysis and Design

By Eng.Adulahi M. Adan

p://www.mahergelle.com

http://www.mahergelle.com
Chapter One: -
Introduction to
Systems Analysis
and Design
 Introduction
System Analyses and Design

❖ Systems development is systematic process which

includes phases such as
✓ Planning,
✓ Analysis,
✓ Design,
✓ Deployment,
✓ And Maintenance
❖ Here, in this Course, we will primarily focus on:
❑ Systems analysis
❑ Systems design
 Systems Analysis
System Analyses and Design

• It is a process of collecting and interpreting facts,

identifying the problems, and decomposition of a
system into its components.
• System analysis is conducted for the purpose of
studying a system or its parts in order to identify its
objectives.
• It is a problem solving technique that improves the
system and ensures that all the components of the
system work efficiently to accomplish their purpose.
• Analysis specifies what the system should do.
 Systems Analysis
System Analyses and Design

❖ What Is System Analysis About?

•Understanding the goals and strategies of the business.
•Defining the information requirements that support those goals
and strategies.
•It is not about programming.
❖ System Analyst
• A business professional who uses analysis and design
techniques to solve business problems using information
technology.
 Systems Analysis
System Analyses and Design

❖ The Role of a System Analyst

•Investigate, analyze, design, develop, install, evaluate, and
maintain a company’s information systems.
•Business knowledge.
•Business problem solver.
•Help translate business requirements into IT projects.
 Systems Design
System Analyses and Design

• It is a process of planning a new business system or replacing

an existing system by defining its components or modules to
satisfy the specific requirements.
• Before planning, you need to understand the old system
thoroughly and determine how computers can best be used in
order to operate efficiently.
• System Design focuses on how to accomplish the objective
of the system.
• System Analysis and Design (SAD) mainly focuses on:
❖ Systems
❖ Processes
❖ Technology
 System Analysis vs. System Design
System Analyses and Design

System Analysis:
Investigation of the problem and requirement rather than
solution.

System Design:
A conceptual solution that fulfills the requirements, rather than
implementation.
Chapter Two: -
System Development
Life Cycle
❖ Requirement analysis and
Definition
❖ Planning and Feasibility study
❖ Design and Development
❖ Implementation and Testing
 SDLC
Contents A

➢ Communication: -
➢ This is the first step where the user initiates the request for a
desired System product.
➢ The user contacts the service provider and tries to negotiate
the terms, submits the request to the service providing
organization in writing.
➢ Requirement Gathering: -
➢ This step onwards the System development team works to
carry on the project.
➢ The team holds discussions with various stakeholders from
problem domain and tries to bring out as much information as
possible on their requirements.
 SDLC
Contents A

➢ The requirements are contemplated and segregated into User requir

ements, System requirements and Functional requirements.
1. User requirements are the needs and wants of the users of the
System.
They describe what the users need the System to do in order to be
successful. For example, a user requirement for a banking System might
be that it must be able to process transactions securely.
2. System requirements are the technical specifications that the
system must meet in order to fulfill the user requirements.
They describe the hardware, software, and network resources that the
system will need to run on. For example, a system requirement for the
banking system might be that it must be able to run on a Windows
operating system with 4GB of RAM.
 SDLC
Contents A

3. Functional requirements are the specific behaviors that the

system must exhibit in order to fulfill the user requirements.
They describe what the system must do, not how it must do it.
For example, a functional requirement for the banking system
might be that it must be able to allow users to transfer money
between accounts.
➢ The requirements are collected using a number of practic
es as given –
• studying the existing or obsolete system and software,
• conducting interviews of users and developers,
• referring to the database or
• collecting answers from the questionnaires.
 SDLC
Contents A

➢ Feasibility Study
➢ After requirement gathering, the team comes up with a rough
plan of system process.
➢ At this step the team analyzes if a system can be designed to
fulfill all requirements of the user, and if there is any possibility
of system being no more useful.
➢ It is also analyzed if the project is financially, practically, and
technologically feasible for the organization to take up. There
are many algorithms available, which help the developers to
conclude the feasibility of a System project.
 SDLC
Contents A

➢ System Analysis
➢ At this step the developers decide a roadmap of their plan and
try to bring up the best System model suitable for the project.
➢ System analysis includes understanding of system product
limitations, learning system related problems or changes to
be done in existing systems beforehand, identifying and
addressing the impact of project on organization and
personnel etc.
➢ The project team analyzes the scope of the project and plans
the schedule and resources accordingly.
 SDLC
Contents A

➢ System Design
➢ Next step is to bring down whole knowledge of requirements
and analysis on the desk and design the System product.
➢ The inputs from users and information gathered in requireme
nt gathering phase are the inputs of this step.
➢ The output of this step comes in the form of two designs;
➢ logical design, and
➢ physical design.
➢ Engineers produce meta-data and data dictionaries, logical
diagrams, data-flow diagrams.
 SDLC
Contents A

➢ Coding
➢ This step is also known as programming phase. The impleme
ntation of system design starts in terms of writing program
code in the suitable programming language and developing
error-free executable programs efficiently.
➢ Testing
➢ system testing is done while coding by the developers and
thorough testing is conducted by testing experts at various
levels of code such as module testing, program testing,
System testing, and testing the product at user’s end.
➢ Early discovery of errors and their remedy is the key to
reliable system.
 SDLC
Contents A

➢ Integration
➢ System may need to be integrated with the libraries, databases, and
other program(s). This stage of SDLC is involved in the integration of
System with outer world entities.
➢ Implementation
➢ This means installing the software on user machines. At times,
System needs post-installation configurations at user end. System is
tested for portability and adaptability and integration related issues
are solved during implementation.
➢ Operation and Maintenance
➢ This phase confirms the system operation in terms of more efficiency
and less errors. If required, the users are trained on, or aided with
the documentation on how to operate the software and how to keep
the System operational.
 System Development Paradigm
Contents A

➢ The System development paradigm helps a developer to

select a strategy to develop the System.
➢ A System development paradigm has its own set of tools,
methods, and procedures, which are expressed clearly and
defines software development life cycle.
➢ A few of system development paradigms or process models
are defined as follows:
➢ Waterfall Model
➢ Waterfall model is the simplest model of system development
paradigm. All the phases of SDLC will function one after
another in linear manner. That is, when the first phase is finish
ed then only the second phase will start and so on.
System Development Paradigm
 System Development Paradigm
Contents A

➢ Iterative Model
➢ This model leads the system development process in
iterations. It projects the process of development in cyclic
manner repeating every step after every cycle of SDLC
process.
➢ The system is first developed on very small scale and all the
steps are followed which are taken into consideration. Then,
on every next iteration, more features and modules are
designed, coded, tested, and added to the software.
➢ Every cycle produces a software, which is complete in itself
and has more features and capabilities than that of the
previous one.
 System Development Paradigm
Contents A
 System Development Paradigm
Contents A

➢ Spiral Model
➢ Spiral model is a combination of both, iterative model and one
of the SDLC model. It can be seen as if you choose one SDLC
model and combined it with cyclic process (iterative model).
➢ This model considers risk, which often goes un-noticed by mo
st other models. The model starts with determining objectives
and constraints of the software at the start of one iteration. Ne
xt phase is of prototyping the software. This includes risk analy
sis. Then one standard SDLC model is used to build the softw
are. In the fourth phase of the plan of next iteration is prepared
System Development Paradigm
 System Development Paradigm
Contents A

➢ V – model
➢ The major drawback of waterfall model is we move to the next
stage only when the previous one is finished and there was no
chance to go back if something is found wrong in later stages.
➢ V-Model provides means of testing of software at each stage i
n reverse manner.
 System Development Paradigm
Contents A
 System Development Paradigm
Contents A

➢ Big Bang Model

➢ This model is the simplest model in its form.
➢ It requires little planning, lots of programming and lots of fund
➢ This model is conceptualized around the big bang of universe.
➢ As scientists say that after big bang lots of galaxies, planets,
and stars evolved just as an event.
➢ Likewise, if we put together lots of programming and funds,
you may achieve the best software product.
 System Development Paradigm
Contents A
Chapter Three: -
System Design
 Introduction to UML,
UML diagrams and Relationships
System Analyses and Design

• UML stands for unified modeling language.

• UML was created by the object management group (OMG).
• "The Unified Modeling Language (UML) is a graphical languag
e for visualizing, specifying, constructing, and documenting th
e artifacts of a software-intensive system.
• The UML offers a standard way to write a system's blueprints,
including conceptual things such as business processes and s
ystem functions as well as concrete things such as programmi
ng language statements, database schemas, and reusable sof
tware components.“
 Introduction to UML,
UML diagrams and Relationships
System Analyses and Design

• UML diagrams represent two different views of a system model:

• Static (or structural) view: This view emphasizes the static
structure of the system using objects, attributes, operations,
and relationships.
• Ex: Class diagram, Composite Structure diagram.
• Dynamic (or behavioral) view: This view emphasizes the
dynamic behavior of the system by showing collaborations
among objects and changes to the internal states of objects.
• Ex: Sequence diagram, Activity diagram, State Machine
diagram.
 Static (or structural) view
System Analyses and Design

1. Class diagram
2. Composite Structure diagram.
3. Object Diagram
4. Profile Diagram
5. Deployment Diagram
6. Package Diagram
7. Component Diagram
 Dynamic (or behavioral) view:
System Analyses and Design

1. Activity Diagram
2. Use case Diagram
3. Interaction Diagram
4. State Machine Diagram
5. Sequence Diagram
6. Communication Diagram
7. Interaction Overview Diagram
8. Timing Diagram
 Introduction
System Analyses and Design

❖ a
System Analyses and Design

Use case Diagram

 Use case Diagram
System Analyses and Design

• In the Unified Modeling Language (UML), a use case diagram

can summarize the details of your system's users (also known
as actors) and their interactions with the system.
• To build one, you'll use a set of specialized symbols and
connectors. An effective use case diagram can help your team
discuss and represent:
• Scenarios in which your system or application interacts with
people, organizations, or external systems
• Goals that your system or application helps those entities
(known as actors) achieve
 Use case diagram components
System Analyses and Design

• Actors: The users that interact with a system. An actor can be

a person, an organization, or an outside system that interacts
with your application or system. They must be external objects
that produce or consume data.
• Use case: It describes set of actions performed by a system
for a specific goal.
• System: A specific sequence of actions and interactions
between actors and the system. A system may also be referre
d to as a scenario.
• Goals: The end result of most use cases. A successful
diagram should describe the activities and variants used to
reach the goal.
 Use Case Diagram
System Analyses and Design

Use Case Model

The Use Case Model captures the requirements of a system.
Use cases are a means of communicating with users and other
stakeholders about what the system is intended to do.
Actor
 Use Case Diagram
System Analyses and Design

• Actors can generalize other actors as detailed in the following

diagram:
 Use Case Diagram
System Analyses and Design

• Use Cases: A use case is a single unit of meaningful work.

• It provides a high-level view of behavior observable to someon
e or something outside the system.
• The notation for a use case is an ellipse.
 Use Case Diagram
System Analyses and Design

• The notation for using a use case is a connecting line with

an optional arrowhead showing the direction of control.
• The following diagram indicates that the actor Customer uses
the Withdraw use case.
Use case diagram Examples

Hotel
 Activity Diagram
Contents A

❖ Activity diagram is another important diagram in UML to

describe the dynamic aspects of the system.
❖ 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.
❖ The control flow is drawn from one operation to another.
❖ This flow can be sequential, branched, or concurrent.
❖ It describes a flowchart to represent the flow from one activity
to another activity.
❖ Activity means as an operation of the system.
 Activity Diagram
Contents A

❖ The purpose of an activity diagram can be described as −

➢ Draw the activity flow of a system.
➢ Describe the sequence from one activity to another.
➢ Describe the parallel, branched and concurrent flow
of the system.
➢ It can be represented as follows.
 Activity Diagram
Contents A

➢ Control Flow
➢ A control flow shows the flow of control from one action to the
next . Its notation is a line with an arrowhead.
 Activity Diagram
Contents A

➢ Initial Node
➢ An initial or start node is depicted by a large black spot , as
depicted below.
 Activity Diagram
Contents A

➢ Final Node
➢ There are two types of final node:
➢ ACTIVITY FINAL NODE ➢ FLOW FINAL NODE
➢ The activity final node is ➢ The flow final node is depicted
depicted as a circle with a as a circle with a cross inside.
dot inside.

➢ The difference between the two node types is that the

➢ flow final node denotes the end of a single control flow;
➢ activity final node denotes the end of all control flows within the activity
Activity Diagram Example
Activity Diagram Example
Thank you
@Eng.Abdulahi Mohamed