System Analysis: Kristian Czar Reslin Bscpev
System Analysis: Kristian Czar Reslin Bscpev
System Analysis: Kristian Czar Reslin Bscpev
▪ Analysis Definition
– Analysis focuses on capturing the business requirements for the
system. Analysis identifies the “what” of the system, and it leads
directly into the design phase, during which the “how” of the
system is determined.
Overview of Analysis
▪ Characteristics Of Analysis
– Organization: It implies structure and order. It is the arrangement
of components that helps to achieve objectives.
– Interaction: It refers to the manner in which each component
functions with other components of the system.
– Interdependence: It means that parts of the organization or
computer system depend on one another. They are coordinated
and linked together according to a plan. One subsystem depends
on the output of another subsystem for proper functioning.
– Integration: It refers to the holism of systems. It is concerned with
how a system is tied together.
Overview of Analysis
▪ Characteristics Of Analysis
– Central Objective: A system should have a central objective.
Objectives may be real or stated. Although a stated objective may
be the real objective, it is not uncommon for an organization to
state one objective and operate to achieve another. The important
point is that users must know the central objective of a computer
application early in the analysis for a successful design and
conversion.
Problems of Analysis
▪ Feasibility Studies
– Often the first step involves determining whether the product or
project is worth the time and effort.
– A feasibility study is a document that describes features and
benefits of the product, itemizes costs, resources and staffing then
describes the projects potential profits or value to the
organization.
▪ Interviews
– The details necessary to understand processes or product needs
are usually in the heads of employees and customers.
Tools of the System Analyst
▪ Use Cases
– Short narratives describing how a product will be used, limited to a few
paragraphs, often helps analysts and customers refine product features.
– Refine these narratives throughout the analysis phase. These use cases
can be used throughout the project life cycle, especially during testing.
▪ Requirements Lists
▪ When designing a product, it is helpful to keep a running list of
requirements.
▪ These should be presented as a list or in outline form, organized by
categories.
▪ As the list grows, this list helps the analyst understand the customer’s
needs and helps limit what features are necessary and which are not.
Tools of the System Analyst
▪ Flowcharts
– Flowcharts come in many varieties and under many names, but the basic
concept is to take a process and describe it as a diagram.
– Whether presented as a process flow chart or an Entity/Relation diagram,
the drawing helps the analyst describe a series of steps or decisions in
visual form in a manner that facilitates communication.
▪ Prototypes
– A model or prototype can turn a group of ideas into solid form. Software
engineers often hear the statement “I’ll know what I want when I see it”
and a model or prototype can facilitate these issues.
– By presenting a prototype, the analysts gather features that work and
open discussion on other features and improvements.
System Development Life Cycle
(Structured and Object-Oriented)