Scribd
Upload
31 views6 pages

System Analysis & Design Summary

The document outlines the Systems Development Life Cycle (SDLC) and the role of a systems analyst in developing information systems, emphasizing phases such as planning, analysis, design, and implementation. It details the responsibilities of various analysts, project selection methodologies, and the importance of project management and coordination. Additionally, it highlights the significance of feasibility analysis and business process management in ensuring successful project outcomes.

Uploaded by

Mariam Nasr
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
31 views6 pages

System Analysis & Design Summary

The document outlines the Systems Development Life Cycle (SDLC) and the role of a systems analyst in developing information systems, emphasizing phases such as planning, analysis, design, and implementation. It details the responsibilities of various analysts, project selection methodologies, and the importance of project management and coordination. Additionally, it highlights the significance of feasibility analysis and business process management in ensuring successful project outcomes.

Uploaded by

Mariam Nasr
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

System Analysis & Design

Chapter 1 : Systems Analyst and Information


Systems Development Lifecycle

1. Introduction to SDLC

The Systems Development Life Cycle (SDLC) is a structured approach


to developing information systems, involving planning, analysis, design,
and implementation. The systems analyst plays a crucial role in
identifying business needs, designing solutions, and implementing
improvements.

2. Role of a Systems Analyst

A systems analyst ensures that information systems meet business needs


effectively. Key skills include:

Technical (understanding IT solutions),


Business (applying IT to solve business problems),
Analytical (problem-solving),
Interpersonal (communication),
Management (project oversight),
Ethical (ensuring fairness and honesty).

3. Systems Analyst Roles

Business Analyst – Focuses on business requirements. / Focuses on the


business issues surrounding the system
Systems Analyst – Deals with IT solutions. / Focuses on the information
system issues surrounding the system

Infrastructure Analyst – Manages technical components. / Focuses on the


technical issues
Change Management Analyst – Handles organizational adoption. /
Focuses on the people and management issues surrounding the system
installation
Project Manager – Oversees timelines and budgets and ensures that the
system deliver the expected value to the organization.

NOTE
The difference between Business Analyst and System Analyst
Business Analyst: provides an input information for the system analyst,
gathers and documents the requirements.
System Analyst: writes technical requirements from the business
requirements

4. Systems Development Life Cycle (SDLC) Phases

Planning – Defines project goals and business value.


Analysis – Determines system requirements and user needs.
Design – Specifies system architecture, user interfaces, and databases.
Implementation – Develops, tests, and deploys the system.

1. Planning
Answers the questions => why an information system should be built,
and determining how the project team will go about building it

Planning phase has two steps:


1- project initiation: system’s business value to the organization is
identified => lower cost or increase revenue

2- project management: the project manager creates a work plan,


staffs the project, and puts techniques in place to help the project
team control and direct the project through the entire SDLC
2. Analysis
Answers the questions => who will use the system, what the system
will do, where and when it will be used
project team investigates any current system(s), identifies
improvement opportunities, and develops a concept for the new
system.

Analysis has three steps:


1. Analysis Strategy – Evaluates the current system, identifies issues,
and plans improvements.
2. Requirements Gathering – Collects data to define system needs and
develop models.
3. System Proposal – Presents the proposed solution to decision-makers
for approval.

3. Design
Answers the questions => how the system will operate

The design phase has four steps:

1. Design Strategy – Determines if development will be in-house or


outsourced.
2. Architecture Design – Defines hardware, software, and network
setup.
3. Database & File Specifications – Specifies data storage details.
4. Program Design – Outlines required programs and their functions.

4. Implementation
involves developing or purchasing the system and installing it.

It is the longest and most expensive phase and includes three steps:

1. System Construction – Building and testing the system.


2. Installation – Replacing the old system with the new one.
3. Support Plan – Reviewing performance and planning for future
updates.

SDLC Phase Outcome Purpose


Document
1. Planning System Justifies the need for the system and evaluates
Request & feasibility.
Feasibility
Study
2. Analysis System Summarizes business requirements and the proposed
Proposal solution.
3. Design System Defines system architecture, databases, and program
Specification design.
Document
4. Test Reports, Confirms system functionality, prepares users, and
Implementa Training finalizes deployment.
tion Manuals, &
Deployment
Plan

5. Project Identification & Initiation

Projects start when a business identifies the need for an information system.

Project initiation follow 6 steps:

1. Business case (why the project is necessary)


2. Feasibility study (research the reason for the project)
3. Project charter (how the project will be built)
4. Team
5. Project office
6. Review
Business Process Management (BPM) is a methodology used by
organizations to continuously improve end-to-end business processes.
BPM plays a role in improving workflows through:
BPA (Automation of manual processes),
BPI (Improving workflows),
BPR (Radical process changes, changing the fundamental way in which the
organization operate “Reengineering”).

6. Project sponsor

Someone who has interest in the project success


Project sponsor responsibilities:
1- Providing requirements
2- Maintaining ongoing communication
3- Reviewing deliverables
4- Monitoring the progress and budget
5- Managing risks
7. System Request & Feasibility Analysis

Business requirements: capabilities that the system will need to have.


Business value: describe the benefits that the organization should expect
from the system.
A System Request outlines business needs and expected value.
Feasibility Analysis evaluates project risks and determine whether to
proceed with a project in three areas:
Technical Feasibility – Can we build it?
Economic Feasibility – Is it cost-effective?
Organizational Feasibility – Will users accept it?
Ways to assess the organizational feasibility:
- Understand how well the goals align with the organization objectives
and strategies
- Conduct stakeholder analysis

Chapter 2: Project Selection and Management


1. Project Selection

 CIOs must choose projects that maximize IT investment returns.


 Project Portfolio Management (PPM) helps organizations select
projects that align with business goals.
 Projects are classified based on cost, benefits, risks, and
intangibles like employee perception.

2. Project Methodologies

Different approaches to System Development Life Cycle (SDLC) include:

 Waterfall Model – Sequential, structured, but slow.


 Parallel Development – Splits work into smaller parts for efficiency.
 V-Model – Focuses on testing after each phase.
 Rapid Application Development (RAD) – Uses prototyping for
faster development.
 Agile Development – Iterative, user-focused (e.g., Scrum, XP).

3. Project Planning & Management

 Work Plan Development – Uses tools like Microsoft Project and


Oracle Primavera P6.
 Staffing – A structured team with clear roles ensures efficiency.
 Motivation & Conflict Handling – Uses intrinsic rewards
(recognition, responsibility) and conflict resolution strategies.

4. Project Coordination & Control

 CASE Tools – Automate parts of SDLC (Upper CASE, Lower CASE).


 Managing Scope – Avoid scope creep, where uncontrolled feature
additions delay projects.
 Timeboxing – Setting fixed deadlines and adjusting functionality if
needed.
 Risk Management – Identifies potential issues and plans mitigation
strategies.

You might also like