Scribd
Upload
5 views

Intro-to-SAD

Systems analysis and design is a systematic approach to developing high-quality information systems, involving the integration of technology, people, and data. The process includes various methodologies such as the Systems Development Life Cycle (SDLC), Waterfall, V-Model, Prototyping, Spiral, Iterative, and Agile Development, each with distinct phases and focuses. A systems analyst plays a crucial role in this process by investigating, designing, and maintaining information systems that meet business requirements.

Uploaded by

Tantan Bartolomew
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
5 views

Intro-to-SAD

Systems analysis and design is a systematic approach to developing high-quality information systems, involving the integration of technology, people, and data. The process includes various methodologies such as the Systems Development Life Cycle (SDLC), Waterfall, V-Model, Prototyping, Spiral, Iterative, and Agile Development, each with distinct phases and focuses. A systems analyst plays a crucial role in this process by investigating, designing, and maintaining information systems that meet business requirements.

Uploaded by

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

Systems Analysis

and Design
LESSON 1: Introduction to Systems Analysis and Design

Systems analysis and design is a


step-by-step process for developing
high-quality information systems.
LESSON 1: Introduction to Systems Analysis and Design

Information system is the


combination of:
• Technology
• People
• Data
IT department develops and maintains
information systems
The Systems Analyst

A systems analyst
investigates, analyzes, designs,
develops, installs, evaluates,
and maintains a company’s
information systems.
plans the periodicity for evaluation helps develop IT systems that
after it has been used for some support business requirements.
time, and modify the system as
needed. 8 1
translates complex
implements the logical technical issues into
design of system which words and images that
7 2
must be modular. nontechnical people can
grasp
Systems Analyst
suggests many flexible builds a series of
alternative solutions, pick 6 3
models, diagrams, and
the best solution, and decision tables and
quantify cost and benefits. uses other descriptive
gathers facts or information 5 4 tools and techniques
and acquires the opinions of
users. act as translators
Attributes of a System Analyst:

Interpersonal
Technical Skills
Skills

Skills of System Analyst

Management
Analytical Skills Skills
Information System

A system is a set of
related components
that produces specific
results.
Information System
Internet Business Strategies
Three trends that shaped business today:

• Rapidly increasing globalization


• Technology integration
• Rapid growth of cloud-based computing and software
Internet Model
• Business-to-Consumer
• Business-to-Business
• Business-to-Business-to-Consumer
SYSTEM DEVELOPMENT METHODOLOGIES

The systems development life cycle


(SDLC) is a common methodology for
systems development in many
organizations; it features several
phases that mark the progress of the
systems analysis and design effort.
A methodology is a
formalized approach in
implementing the SDLC
(i.e., it is a list of steps
and deliverables).
• The purpose is evaluate an IT-related
business opportunity or problem.
• Usually begins with a formal request to the IT
department, called a systems request
• To determine whether to perform preliminary
investigation
• Feasibility study
• The purpose is to build a
logical model of the new
system.
• To build business models,
data and process models,
and object models.
• The deliverable for the
systems analysis phase is
the system requirements
document or system
requirement specification
(SRS).
• The purpose is to create a physical model that
will satisfy all documented requirements for
the system.
• The user interface is designed, and necessary
outputs, inputs, and processes are identified
• As well internal and external controls are
designed
• The new system is constructed.
• programs are written, tested, and
documented, and the system is installed
• To deliver a completely functioning and
documented information system.
• Includes systems evaluation
• The IT staff maintains,
enhances, and protects the
system
Waterfall Development

With Waterfall Development-based


Methodologies, the analysts and users
proceed in sequence from one phase to the
next.

This methodology is referred to as waterfall


development because it moves forward from
phase to phase in the same manner.
V-Model

The V-model is a type of SDLC model where


process executes in a sequential manner in V-
shape

• Verification and Validation model


• based on the association of a testing phase
for each corresponding development stage.
• Development of each step directly associated
with the testing phase.
Prototyping Model

• Prototyping model is a software development


model in which prototype is built, tested, and
reworked until an acceptable prototype is
achieved.

• It also creates base to produce the final


system or software
Prototyping Approaches

• Rapid Throwaway Prototypes


• Evolutionary Prototype
• Incremental Prototype
• Extreme Prototype
Spiral Model

• Every phase starts with a design goal


and ends with the client reviewing the
progress.
Spiral Model
Iterative Model

Uses an iterative, which overcomes the


weakness of the waterfall model.
Agile Development

• Based on the Agile Manifesto and a set


of principles.
• The emphasis of the manifesto is to
focus the developers on the working
conditions of the developers, the
working software, the customers, and
addressing the changing requirements.
These principles include the following:

Satisfy the customer through delivery of working


1 software.

Embrace change, even if introduced late in


2 development.

Continue to deliver functioning software


3 incrementally and frequently.

Encourage customers and analysts to work together


4 daily.
5 Trust motivated individuals to get the job done.

6 Promote face-to-face conversation.

7 Concentrate on getting software to work.

Encourage continuous, regular, and sustainable


8 development.
9 Adopt agility with attention to mindful design.

10 Support self-organizing teams..

11 Provide rapid feedback.

12 Encourage quality.
13 Review and adjust behavior occasionally

14 Adopt simplicity.
Scrum Methodology
Extreme Programming Methodology
SOURCES OF SOFTWARE

Sources of Application Software


Off-The-Shelf Software

Ease of Installation Cost


8 1

Response Time Functionality


7 2

Off-The-Shelf
Software Criteria
6 3
Vendor Support
Documentation

5 4
Flexibility Viability of Vendor
Thank you!

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy