Scribd
Upload
12 views5 pages

6_The six stages of the System Development Life Cycle

The document outlines the six stages of the System Development Life Cycle (SDLC), which include Planning, Analysis, Design, Development and Testing, Implementation, and Maintenance and Review. It also discusses various changeover methods for migrating to a new accounting information system, such as direct changeover, parallel running, pilot operation, and phased changeover, each with its own advantages and disadvantages. The importance of end-user participation is emphasized to ensure that the system meets user requirements.

Uploaded by

Kudzai Mupamombe
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
12 views5 pages

6_The six stages of the System Development Life Cycle

The document outlines the six stages of the System Development Life Cycle (SDLC), which include Planning, Analysis, Design, Development and Testing, Implementation, and Maintenance and Review. It also discusses various changeover methods for migrating to a new accounting information system, such as direct changeover, parallel running, pilot operation, and phased changeover, each with its own advantages and disadvantages. The importance of end-user participation is emphasized to ensure that the system meets user requirements.

Uploaded by

Kudzai Mupamombe
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/ 5

The six stages of the System Development Life Cycle (SDLC) (CIMA,

2015), (ISTQB, 2014)

Stage 1 – Planning
The general plan regarding information and user requirements is developed.
Required information is gathered. At this stage the business requirements are
gathered by meeting managers, stakeholders and users. Possible users of
the system are identified and their needs gathered. The nature of the input
and desired output are also taken into consideration. All the gathered data is
documented in the specifications document.
Stage 2 – Analysis
The information gathered in Stage 1 is analyzed. This stage collects
information and attempts to understand the processes and systems currently
in use. The main focus is on identifying key needs and requirements and the
best way to meet them.

Stage 3 – Design
The software is designed using the specifications developed during stage 1.
The design considers both hardware and software requirements of the
system to come up with the system architecture. In most situations the system
is broken up into modules that are coded separately.

Stage 4 – Development and Testing


The designs are developed into systems through performance and
integration testing. It is always important that the system requirements and
objectives are always held during the development of the system.
Development requires writing the necessary code. After the code is
completed, the system is tested against the requirements for which it is being
developed. The testing will show if the system will be able to solve the
problems identified in Stage 1. Different types of tests are carried out
including functional testing as well as non-functional testing.

Page 1 of 5
Stage 5 – Implementation or Deployment
After the testing phase, the system is brought to the users. The new system
is implemented. This involves changing over from the old or existing system
to the new system. There are a number of changeover approaches that the
organisation can use. The arrangements are direct changeover, parallel
running, phased changeover and pilot testing.

Stage 6 – Maintenance ad Review


As the system is used problems may come up that need to be attended to.
The stage involves regular monitoring to see if the system is functioning as
desired. User interactions and feedback remain key. And if any major needs
are identified the cycle is initiated from Stage 1 once again.
Importance of end-user participation

 This ensures that the system meets the requirement of the users not
of the developers.
 The end product will be supported by the end users since they
consider themselves part of the product.

Page 2 of 5
Different AIS Changeover Options
There are different changeover methods that organisations can use when migrating to a
new accounting information system. They can use the direct changeover method, the
parallel changeover method, the pilot testing method or the phased changeover
method.
Direct changeover

This is the complete replacement of the older system by the new system. The old
system will be replaced immediately with the new system. This system avoids
duplicated systems and the possibility of data redundancy and poor data currency
as all data will be up to date. It reduces on the requirements for space as only one
system will be on the computers.
However, this system is not fail safe. If it fails, the organisation is set to suffer
greatly. Since it is new system, there are chances that it may not perform as
required. This works best where system failure does not have big damaging effects.
For the company there could be great damage to the business if the new system
fails and that reverting to the old system would be costly.

Page 3 of 5
Parallel running
This changeover allows for the running of the new system and the old system for
some time (CIMA, 2014).

OLD SYSTEM

NEW SYSTEM

Changeover Period

Advantages
 This changeover has the advantage that it reduces loos of data in the event of
new system failure. Both systems provide back-up for each other.
 This changeover provides the company with a comparator system to provide
confidence that the new system is operating properly.
Disadvantage
 The problem with this changeover is that the two system may be costly to run
during the changeover period since they will be a duplication of the systems.
 It may be time consuming through duplication of transaction input and
processing.

Pilot Operation
When using this changeover, the company will have to test the new system at a
separate site, possibly on the new site. The old system will run at the old site while the
proposed new system runs at a controlled site.
Advantages
 It is much safer than the direct changeover.
 It is less risk as compared to the direct changeover.
Disadvantages

Page 4 of 5
 The changeover cannot be implemented on its own it will devolve into one of the
other changeover systems like direct changeover, parallel running or phased
changeover.

Phased Changeover
The new system is phased in gradually with more and more tasks being carried out on it
while the old system is gradually phased out (UK Essays, 2015).
Advantages
 Gradual phasing in allows staff to learn the new system.
 This has lower staff training costs.
Disadvantages (CIMA, 2014)
 The risk is data loss is greater than that for parallel running.
 It is also expensive to run two systems
 The changeover period is long.

Page 5 of 5

You might also like