Scribd
Upload
46 views

System Analisis

This document summarizes the FAST methodology for system analysis. It describes system analysis as the study of a system and its components prior to system design. The key tasks of system analysis include understanding user and stakeholder needs, documenting existing systems and processes, identifying problems and opportunities for improvement, and defining requirements for the new system. Common system analysis approaches include structured analysis using models and prototypes, with key outputs being requirements documents, models, and plans.

Uploaded by

Maszuza Syahlevi
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
46 views

System Analisis

This document summarizes the FAST methodology for system analysis. It describes system analysis as the study of a system and its components prior to system design. The key tasks of system analysis include understanding user and stakeholder needs, documenting existing systems and processes, identifying problems and opportunities for improvement, and defining requirements for the new system. Common system analysis approaches include structured analysis using models and prototypes, with key outputs being requirements documents, models, and plans.

Uploaded by

Maszuza Syahlevi
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/ 25

System Analysis

Masrul Indrayana
FAST Methodology
The Context System Analysis
• Systems analysis is the study of a system and
its components, prerequisite to Systems
Design
• System analysis driven by SO and SU
• It adresses the knowledge, process and
communications from SO and SU perspectives
• SA serves as facilitators
• The documentation produced by SA tasks are
typically stored in a repository
Repository Implemented
• A network directory of word processing,
spreadsheet, and other computer generated
files that contain project correspondence,
reports and data
• One or more CASE (computer-assisted systems
engineering) tool
• Printed documentatiton
• An internet web site interface for useful
communication
System Analysis Approaches
• Model-Driven Analysis Approaches; uses pictures
(ex: flowcharts, organization charts) to communicate
business problems, requirements and solution.
structured analysis, information engineering, object-
oriented analysis
• Accelerated Systems Analysis Approaches;
construction of prototypes to more rapidly identify
business and user requirements. Common in the
rapid application development (RAD)
Discovery prototyping (simple tools), rapid architected
analysis (reverse engineering technology)
Structured Anaylsis
• One of traditional approaches to analyze or
define business requirements
• Focuses on the flow of data through business and
software process (process centered)
• One of the key tools used to model processes is
the data flow diagram
• DFD depicts the processes in a system along with
their inputs, outputs and data
• Process models serve as blueprints for business
process to be implemented and software to be
purchased or constructed
A Simple Process Model (DFD)
The
models
show the
flow of
data
between
and
through
process
and show
the places
where data
is stored
A Simple Data Model (ERD)
Focuses on
the structure
of stored
data rather
than on
processes
An Object Model
Requirements Discovery Approaches
• Fact-finding Techniques
– Sampling of existing documentation, reports, forms, files,
databases and memos
– Research of relevant literature, bencahmarking, site visits
– Obeservatioan of the current system and the work
environment
– Questionnaires and surveys
– Interviews of managers, users, and technical staff
• Joint Requiremnet Planning; analyst as facilitator for a
workshop will typically run from three to five full
working days
The Scope Definition Phase
• Is this project worth looking at?
• Concerned primarily with the SO’ of the existing
system and the problems or opportuinities that
triggered the interest
• The task!:
– Identify baseline problem and opportunites
– Negotiate baseline scope
– Asses baseline project worthines
– Develop baseline sechedule and budget
– Communicate the project plan
Problem Analysis Phase
• Are the problems really worth solving?
• The task!:
– Understand the problem domain
– Analyze problems and opportunities (causes-effects
analysis)
– Analyze business processes (redesign?)
– Establish system improvemnet objectives (criteria?)
– Update or refine the project plan
– Communicate findings and recommendations
The Requirements Analysis Phase
• Defines the business requiremnets for a new
system
• The task!:
– Identify and express system requirements
– Prioritize system requirements (mandatory-
desirable)
– Update or refine the project plan
– Communicate the requirements statement
The Logical Design Phase
• The task!:
– Structure functional requirements (data
attributes, business rules, policies, atl)
– Prototype functional requirements (alternative)
– Validate functional requirements
– Define acceptance test cases
The Decision Analysis Phase
• Identify candidate solutions, analyze those candidate
solutions and recommended a target system that will
be designed, constructed and implemented
• The task!:
– Identify candidate solutions
– Analyze candidate solutions (technical feasibility,
operational feasibility, economic feasibility, schedule
feasibility)
– Compare candidate solutions
– Update the project plan
– Recommend a system solution

You might also like