System Life Cycle For IGCSE 2020
System Life Cycle For IGCSE 2020
• Observation: This involves watching the • Interviews: This method involves one to one
personnel using the existing system to find question & answer session between analyst
out how it works. and interviewee
• Advantages:- Reliable date is available, • Advantages- open and honest answers are
inexpensive and overall view of the sys. can received, more feedback and questions can
be received be modified
• Disadvantages:- Some people are • Disadvantages:- time consuming, expensive
uncomfortable when they are watched and and interviewee cant remain anonymous
some employees might work like their usual • -Looking at paper documents: This involves
way the analyst to look at how info. is kept
• -Questionnaires: This method involves manually and helps him to get some ideas for
distributing questionnaires to the workforce the new system
to get their opinions • Advantages:- this can be done by the analyst
• Advantages- this is a quick method, alone
inexpensive, the workforce can remain • Disadvantages:- time consuming and
anonymous and this is allow quick analysis of expensive
data
• Disadvantages:- the return questionnaires
are less, the questions are inflexible and
misunderstood questions cannot be clarified
directly
SYSTEM LIFE CYCLE (design)
• 1. Data capture forms:- This allows date to be input into the system and it has character
boxes and on-screen help boxes
• 2. Screen layouts:- this will have the items that will be available in the systems' menus
• 3. Screen displays and printed reports:- Screen displays are used to show data in very
large forms and printed reports show all output fields
• 4. System flowcharts:- this shows how data flows through a system and also how
decisions are made and they use special symbols
• 5. Validation rules:- these are used to check if the data satisfies certain criteria when
input into a computer
• 6. File structures:- this has to take in account they field length, field name with the use
of a data dictionary and data type
• 7. Testing strategy/plan:- this is done to make sure that the software meets the
requirements and does not crash
SLC (development & testing)
• System development means to build up system. After the analysis and design is
completed, there will be a list of requirements and set of designs that a developer will
have to do in order to make it a working system
• System testing means to test each module and after this is completed, the whole
system is checked again to make sure that the modules did not conflict
• The data used to test:-
• Normal data:- this data is within an acceptable range and has is a valid data
• Extreme data:- This is valid data at the limits of acceptability
• Abnormal data:- invalid data that is outside the acceptable range
• This when the system is being introduced to • 3. Pilot implementation- this involves
the organisation introducing the new system into one branch
• 1. Direct implementation:- this method is of the company
when the old system is stopped immediately • Advantages:- if the system fails only one part
and the new system is introduced is affected and it is faster to train staff and
• Advantages: costs are reduced and less likely less costly
for mistakes as the system is already tested • 4.Phased implementation:- this involves
and the benefits are immediate introducing part by part of the new system
• Disadvantages: if the system fails then all the by checking if it in a satisfactory level to
data is lost move on to the nest level
• 2. Parallel implementation:-this method • Advantages:- failure is not disastrous and it
involves running the old system and new ensures that the system works properly
system together before expanding
• Advantages:- chances of backup is available, • Disadvantages:- it is more time consuming
staff can gradually be trained and expensive
• Disadvantages:- time consuming and
expensive
SLC (documentation)
SYSTEM LIFE CYCLE (evaluation)
• Evaluation looks at the efficiency, ease of use and appropriateness of the solution
and considers the following:-
• 1. comparison of final solution with original task
• 2. identification of any limitations and any improvements
• 3. evaluation of user's responses
• 4. comparison of test results from new system and old system
• 5. observation of users' performing task, including time to do task
THE END