System Analysis and Design

Download as pdf or txt
Download as pdf or txt
You are on page 1of 3

System Analysis and Design

Systems development is systematic process which includes phases such as planning,


analysis, design, deployment, and maintenance.

Systems Analysis

It is a process of collecting and interpreting facts, identifying the problems, and


decomposition of a system into its components.
System analysis is conducted for the purpose of studying a system or its parts in order
to identify its objectives. It is a problem solving technique that improves the system
and ensures that all the components of the system work efficiently to accomplish
their purpose.
Analysis specifies what the system should do.

Systems Design

It is a process of planning a new business system or replacing an existing system by


defining its components or modules to satisfy the specific requirements. Before
planning, you need to understand the old system thoroughly and determine how
computers can best be used in order to operate efficiently.
System Design focuses on how to accomplish the objective of the system.
System Analysis and Design (SAD) mainly focuses on −
Systems
Processes
Technology

What is a System?

The word System is derived from Greek word Systema, which means an organized
relationship between any set of components to achieve some common cause or
objective.
A system is “an orderly grouping of interdependent components linked together
according to a plan to achieve a specific goal.”
Steps in System life cycle

1. Planning
This is the first phase in the systems development process. It identifies whether or not
there is the need for a new system to achieve a business"s strategic objectives. This is a
preliminary plan (or a feasibility study) for a company"s business initiative to acquire
the resources to build on an infrastructure to modify or improve a service. The
company might be trying to meet or exceed expectations for their employees,
customers and stakeholders too. The purpose of this step is to find out the scope of
the problem and determine solutions. Resources, costs, time, benefits and other items
should be considered at this stage.

2. Systems Analysis and Requirements


The second phase is where businesses will work on the source of their problem or the
need for a change. In the event of a problem, possible solutions are submitted and
analyzed to identify the best fit for the ultimate goal(s) of the project. This is where
teams consider the functional requirements of the project or solution. It is also where
system analysis takes place—or analyzing the needs of the end users to ensure the
new system can meet their expectations. Systems analysis is vital in determining what
a business"s needs are, as well as how they can be met, who will be responsible for
individual pieces of the project, and what sort of timeline should be expected.

There are several tools businesses can use that are specific to the second phase. They
include:

CASE (Computer Aided Systems/Software Engineering)


Requirements gathering
Structured analysis

3. Systems Design
The third phase describes, in detail, the necessary specifications, features and
operations that will satisfy the functional requirements of the proposed system which
will be in place. This is the step for end users to discuss and determine their specific
business information needs for the proposed system. It"s during this phase that they
will consider the essential components (hardware and/or software) structure
(networking capabilities), processing and procedures for the system to accomplish its
objectives.
4. Development
The fourth phase is when the real work begins—in particular, when a programmer,
network engineer and/or database developer are brought on to do the major work on
the project. This work includes using a flow chart to ensure that the process of the
system is properly organized. The development phase marks the end of the initial
section of the process. Additionally, this phase signifies the start of production. The
development stage is also characterized by instillation and change. Focusing on
training can be a huge benefit during this phase.

5. Integration and Testing


The fifth phase involves systems integration and system testing (of programs and
procedures)—normally carried out by a Quality Assurance (QA) professional—to
determine if the proposed design meets the initial set of business goals. Testing may be
repeated, specifically to check for errors, bugs and interoperability. This testing will be
performed until the end user finds it acceptable. Another part of this phase is
verification and validation, both of which will help ensure the program"s successful
completion.

6. Implementation
The sixth phase is when the majority of the code for the program is written.
Additionally, this phase involves the actual installation of the newly-developed system.
This step puts the project into production by moving the data and components from
the old system and placing them in the new system via a direct cutover. While this can
be a risky (and complicated) move, the cutover typically happens during off-peak hours,
thus minimizing the risk. Both system analysts and end-users should now see the
realization of the project that has implemented changes.

7. Operations and Maintenance


The seventh and final phase involves maintenance and regular required updates. This
step is when end users can fine-tune the system, if they wish, to boost performance,
add new capabilities or meet additional user requirements.

https://boisestate.pressbooks.pub/basicguidetopracticalresear
ch/chapter/preparing-your-research-proposal-2/

You might also like