Systems Analysis &

Design – Chapter 1
Dr. Shadi Ettantawi
2 What is an
Information
System?

A system is a set of interrelated components that work

together to achieve a specific purpose or goal.

In the context of information technology, a system typically

refers to an information system, which is a collection of
hardware, software, data, procedures, and people that work
together to process and manage information.

The components of a system interact to process inputs,

perform functions, and produce outputs.
3 Key Concepts:

1.Components: Systems consist of various elements that work in

unison to perform a task. In an information system, components
might include software, hardware, databases, and networks.

2.Interrelated: The components of a system are interdependent,

meaning that a change or failure in one part of the system can
impact the entire system.

3.Purpose: Systems are designed with a specific purpose in mind.

For example, a customer management system is designed to track
customer information, transactions, and interactions.
4
5 Computer
Application

Is a software program that executes on a computing device (such

as a desktop, laptop, smartphone, or tablet) to carry out specific
tasks or a set of related tasks.

It is often referred to as an "app," especially when running on

mobile devices or web platforms.
6 Key Concepts:
1.Functionality: A computer application is designed to perform specific
functions for the user. These functions can range from basic tasks like word
processing and web browsing to more complex ones like managing customer
data or running financial simulations.

2.User Interaction: Computer applications are typically interactive, allowing

users to input data, make selections, and receive output.

3.Types of Applications: There are various types of applications, including

desktop applications (e.g., Microsoft Word), web applications (e.g., Google Docs),
and mobile applications (e.g., WhatsApp).

The textbook distinguishes between a computer application and an information

system by noting that the former focuses only on the software program, while
the latter may include additional components such as databases.
7 Systems Analysis

Is the process of studying and understanding the needs and

requirements of a system, and specifying what the new or modified
system must do to achieve its intended goals.

It involves breaking down a system into its component parts to

understand how they interact, and identifying the problems or
improvements needed.
8 Key Concepts:
1.Understanding the Problem: Systems analysis focuses on
understanding the business need or problem that the system must
address. This includes gathering information on what the users
need, the current processes, and any existing system limitations.

2.Specification of Requirements: Systems analysis results in a

detailed specification of what the system should do. This involves
documenting the functions the system must perform, the data it
must handle, and how it interacts with users and other systems.

3.Communication: A crucial part of systems analysis is translating

business requirements into a format that technical teams (such as
programmers) can use to develop the system.
9 Systems design

Is the process of defining the architecture, components, modules,

interfaces, and data for a system to meet the specified
requirements.

It focuses on the "how" aspect, meaning how the system will be

structured and how it will fulfill the requirements identified during
systems analysis.
10 Key Concepts:
1.Solution to the Problem: Systems design is about creating a
detailed blueprint for solving the problem or meeting the business
needs identified in the systems analysis phase. It defines how the
system will function and how its components will interact.

2.Technical Specifications: Systems design provides detailed

technical specifications, including the design of databases, user
interfaces, system architecture, hardware requirements, and
network configurations.
11 Key Concepts:
3.Components of Design:

4.Architectural Design: Defines the overall structure of the

system, including its modules and their interactions.

2.Detailed Design: Specifies the individual components, such as

the design of the user interface, database schema, and
algorithms.

3.Interfaces:Describes how different components of the system

will communicate, both internally and with external systems.

4.Outcome of Systems Design: The outcome is a set of detailed

documents or diagrams (such as class diagrams, database
schemas, and user interface layouts) that guide the development
12 A systems analyst

Is a professional who is responsible for analyzing, designing, and

implementing information systems to meet business needs.

Their primary role is to act as a bridge between the business

stakeholders (such as managers and users) and the technical team
(such as developers and engineers), ensuring that the developed
system meets the specified requirements and solves the business
problems.
13 Key
Responsibilities:
1.Requirement Gathering: Systems analysts work closely with business
stakeholders to gather and document the requirements of a system. This
involves interviews, observations, and analyzing existing systems or workflows.

2.Problem Solving: They identify business problems and propose solutions

through the development or improvement of information systems.

3.Systems Design: They help design the overall structure of the system by
creating specifications for software, databases, and interfaces.

4.Coordination Between Teams: Systems analysts serve as intermediaries,

ensuring that the technical teams (developers, engineers) understand the
business goals and that business stakeholders understand the technical
capabilities and limitations of the system.

5.Documentation: Analysts produce detailed documentation throughout the

systems development process, which is used by developers to build the system
and by end-users to understand how it operates.
14 Skills :
•Technical Knowledge: A systems analyst needs a strong understanding of
software development, databases, and networking, as well as knowledge of
specific programming languages or development tools.

•Communication Skills: Strong interpersonal and communication skills are

essential for working with different stakeholders to gather requirements and
explain technical details.

•Analytical Thinking: They must be able to break down complex business

processes into manageable parts and define clear, detailed specifications for
solutions.

•Project Management: Systems analysts often oversee the project lifecycle,

from gathering requirements to deploying the system, requiring good planning
and organizational skills.
15
16 Project:

Is a planned, temporary undertaking with a defined beginning and

end, designed to achieve a specific goal or produce a unique
product, service, or result.

It is distinct from ongoing operations because it has a defined

scope, timeline, and resources dedicated to achieving specific
objectives.
17 Key Characteristics
of a Project:

1.Temporary: A project has a defined start and end date. Once the
objectives are met, the project concludes.

2.Unique Outcome: The goal of a project is to create something

that didn't exist before, whether it's a product, service, system, or
improvement.

3.Defined Scope: A project has specific objectives that determine

what it will produce or achieve. The scope outlines what the project
will and will not include.
18 Key Characteristics
of a Project:

4.Planned Effort: Projects require planning to allocate resources

(time, budget, and people) and to sequence the work in a logical
order.

5.Multidisciplinary: Projects often involve people from different

areas of expertise working together to meet the project’s
objectives.

6.Monitoring and Control: Progress must be tracked, and

adjustments made as necessary to ensure the project stays on
course in terms of time, budget, and quality.
19 Systems
Development Life
Cycle (SDLC)

Is a structured process used to develop, maintain, and replace

information systems.

It outlines the various stages involved in creating an information

system from conception to deployment and ongoing maintenance.

The SDLC helps ensure that systems are developed in a disciplined

and efficient manner, meeting the needs of the business and
users.
20 Key Phases of the
SDLC:

1.Planning:

A. Identify the problem or business need.

b. Obtain approval to proceed with the development of a system.

c. Define the project’s scope, goals, and resources.

d. This phase includes feasibility studies and cost-benefit analyses

to ensure that the project is viable and aligns with business
objectives.
21 Key Phases of the
SDLC:

2.Analysis:

a. Discover and understand the details of the problem or need.

b. Gather detailed requirements from stakeholders. (owner,

employees, end users, customers .. Etc)

c. Document the current system (if applicable) and determine

what the new system must do to solve the problem or meet
business needs.
22 Key Phases of the
SDLC:

3.Design:

a. Design the system components that will meet the identified

requirements.

b. Define the architecture, user interfaces, databases, and system

interfaces.

c. Provide detailed specifications for developers and technical

teams to follow.
23 Key Phases of the
SDLC:

3.Design:

a. Design the system components that will meet the identified

requirements.

b. Define the architecture, user interfaces, databases, and system

interfaces.

c. Provide detailed specifications for developers and technical

teams to follow.
24 Key Phases of the
SDLC:
4.Development:

a. Build, test, and integrate the system components.

b. Programmers write the code, develop the database, and create

the interfaces.

c. All the pieces of the system are integrated and tested

individually.
25 Key Phases of the
SDLC:
5.Testing:

a. Perform system-wide tests to ensure that the system meets the

specified requirements.

b. Test components include unit tests, integration tests, system

tests, and user acceptance tests.

c. Bugs or issues are identified and corrected.

26 Key Phases of the
SDLC:
6.Deployment:

a. Deploy the system into a live environment for use by end-

users.

b. This phase often includes user training, data migration from an

old system, and the installation of necessary hardware and
software.

c. The system goes live and is now operational.

27 Key Phases of the
SDLC:
7.Maintenance:

a. The system is maintained to ensure it continues to work

properly after deployment.

b. This includes fixing bugs, updating the system to meet new

requirements, and ensuring it remains secure and efficient.
28 SDLC
Methodologies:

•Waterfall:A linear and sequential approach where each phase

must be completed before moving on to the next.
•Agile: An iterative approach where the system is developed in
small, incremental cycles or "sprints," allowing for more flexibility
and ongoing stakeholder feedback.
29
30