The System Lifecycle

harry.spong
Mind Map by harry.spong, updated more than 1 year ago
harry.spong
Created by harry.spong over 6 years ago
83
3

Description

A-Level ICT (Chapter 1 - The System Lifecycle) Mind Map on The System Lifecycle, created by harry.spong on 10/06/2013.

Resource summary

The System Lifecycle
1 Definition of the problem
1.1 The feasibility of the proposed system is considered.
1.2 This stage is also known as "the feasibility stage"
1.3 An initial look at the existing system to see how it can be improved or meet the needs of the end user
1.4 A feasibility report is produced at the end of this stage
1.5 Main Process Constraints
1.5.1 Time
1.5.2 Budget
1.5.3 Hardware Choice
1.5.4 Software Choice
1.6 Important Questions that should be answered in this stage
1.6.1 Can the need for a new system be justified?
1.6.2 Is it technically feasible and economically desirable to the end users?
1.6.3 Can the solution be designed and implemented within the given constraints of timescale allocated and budget?
1.6.4 Will the solution have a positive impact on the end users and will the new system bring benefits
1.6.5 Will the solution fulfil all the needs and requirements of the end users
2 Design
2.1 The design stage follows a set of objectives (the requirement specification) that have been defined in the investigation and analysis stage
2.2 The methods of data capture that are going to be used have to be considered to make sure that they are compatible with the new system
2.3 The preparation, input, process, output and storage of the data must also be considered
2.3.1 This also covers such activities as the design of the user interface and the screen layout
2.4 The structure of the data must be defined together with the processing and the validation routines that will be used
2.4.1 Development of any user feedback requirements (error messages) should be linked with this
2.5 The design of the queries and reports that have to be identified as requirements during the investigation stage needs to be considered as well
2.6 The main output from this stage is the design specification
3 Doumentation
3.1 The documentation that gets passed to the end user includes
3.1.1 Detailed program specifications
3.1.2 Recovery procedures
3.1.3 Operating procedures
3.1.4 User manuals
3.1.5 Test plans, data and logs
3.1.6 Security details
3.1.7 Version details
3.1.8 Technical details for associated hardware
4 Investigation and Analysis
4.1 This stage uses the feasibility report as its main input
4.2 The full nature of the problem is investigated in this stage
4.3 Methods of investigating the current system
4.3.1 Questionnaires
4.3.2 Interviews
4.3.3 Meetings
4.3.4 Document Analysis
4.3.5 Observations
4.4 The results of the investigation have to be fully analysed to gain a full understanding of the current system
4.4.1 If the investigation is incomplete, the new system may not cover all the issues with the current system
4.4.1.1 Therefore, the new system may not benefit the organisation
4.5 The user requirements have to be defined during this stage
4.5.1 The requirements are agreed with the client and will form the basis for the rest of the system lifecycle
4.5.1.1 The agreed needs/ requirements are the output of this stage (the requirement specification)
4.6 The requirement specification has to be constantly referred to to make sure that the new system meets all of the criteria of this
5 Implementation
5.1 This stage is also known as the development stage
5.2 This stage uses the design specification as its main input
5.3 During this stage, programmers will create the code required for the software solution.
5.3.1 This includes the development of the user interfaces and outputs, which were designed in the design stage
5.3.2 Any macros, processing and queries that are required by the client must be developed as well
5.4 The main output of this stage will be working software code that is ready to be tested
6 Testing
6.1 Two main functions of this stage
6.1.1 If there are any bugs or errors in the code
6.1.2 If the system correctly meets the defined user requirements
6.2 A well-defined and comprehensive test plan must be produced
6.2.1 The test plan must be followed and results must be documented
6.3 This stage can be vey expensive and time consuming but if it carried out correctly and throughly there will be fewer bugs and issues with the new system
7 Evaluation and Maintenance
7.1 This is the final stage of the system lifecycle.
7.1.1 This stage concludes the whole cycle and a report is produced to summarise each stage of the project and all finds, problems encountered.
8 Installation
8.1 Parallel
8.1.1 This type of installation is when the new system is run along the existing system. This allows any persistent bugs with the new system to be corrected without affecting the day to day running of the company. Once all problems have been resolved, the existing system will be withdrawn from operation and the new system will run on its own
8.1.1.1 An example of this type of installation is self service checkouts in supermarkets
8.2 Phased
8.2.1 This type of installation is when a new system is introduced into the company is stages ("phases"). This is done by running the new system in certain departments or areas
8.2.1.1 An example of this is self service checkouts in supermarkets. This is because they were introduced to a few shops to start with to see how consumers reacted to the change and then converting the rest of the stores to the new system
8.2.1.1.1 This is still an ongoing process for some supermarkets because not all of their stores are running the new system. In this case, self service checkout system
8.3 Pilot
8.3.1 This method of installation is done by introducing the system to one department or store to see how it works
8.3.1.1 There is less of a risk involved in this type of installation because if the new system is unsuccessful, it can be withdrawn easily with little disruption
8.4 Direct
8.4.1 This type of installation is done by introducing the new system to the company in one hit. The existing system is removed and the new system is left to run on its own.
8.4.1.1 This is a risky method of installation because the new system may not work due to undiscovered bugs or because users may not be able to adapt fast enough to use the new system

Media attachments

Show full summary Hide full summary

Similar

MICROSOFT WORD 2013 SKILLS FOR WORK
John O'Driscoll
Types and Components of Computer Systems
Jess Peason
Input Devices
Jess Peason
Output Devices
Jess Peason
General ICT Quiz
leahshaw
ICT Revison Flash Cards
Arun Johal
Networks
Will8324
FLAT FILE VS RELATIONAL DATABASE
rosiejones
Online World - Learning Aim A
andysedge
General ICT Quiz
Jade Fantom
Data Types
Jacob Sedore