Prepared by: Hassan Wael ElDessouki

Chapter 7 - System Development Life Cycle (SDLC)

There are six stages followed for SDLC:

1. Analysis: collecting information about the present system & identifying problems
a. Technical Feasibility → Duration for System Development
b. Economic Feasibility → Cost-Benefit Analysis

Technique Description Advantages Disadvantages

Observation The current system is • The analyst can get reliable • Employees may not perform standard
observed to find out information procedures if they are being watched
how it works. • Information will not be biased, as it • Employees may perform differently if
is the analyst’s point of view they know they are being observed
• Inexpensive method (Hawthorne effect)
• All Inputs/Outputs are seen
Interview People using the • Can ask open-ended questions to • It can be a time-consuming process
current system are gauge more feedback • An expensive method, as interviewers
involved in a one-to- • Questions can be changed during and analysts are needed
one question and the interview • The interviewee cannot remain
answer to gauge their • Possible to ask questions relevant to anonymous with this method
feedback. the interviewee • The interviewee can give answers that
• The analyst can watch the facial he thinks the interviewer may want to
expressions of the interviewee hear
Questionnaire Questionnaires are • Questionnaires can reach a large • Questionnaires may not be completed
distributed to audience accurately
employees/ customers • Questions can be answered quickly • May not be all returned
to find out a range of using tick boxes – a cheaper method • Cannot expand or clarify answers to
opinions about the of analyzing questions
current system. • Can be filled at any time • Cannot clarify an answer
• A greater number of people can take • Responses may be exaggerated as it is
part anonymous
• Individuals may be anonymous • It may not be taken seriously
Collecting Existing documents of • Analysts can see how the current • It can be a time-consuming process
Documents the current system are paper system operates • Due to the time required, this is a
analyzed to identify • Can obtain information critical to the costly method
what data is inputted system that couldn’t be seen with
and outputted. the other methods

Data inputed, Requriements of

Problems with
processed and potential new
current system is
outputted is system are
identified
identified identified

Data may be What may be What is the use of

paper based improved? the new system?

Once the analysis stage has been completed, the analysts shall be fully aware of the
current limitations and problems of the current system.

Page 1 of 8
 Then, the analyst has to find out that input and output takes place, processing that is
done, problems of the current system & user and information requirements of the
new system.

A Data Flow Diagram (DFD) is used that visually shows inputs that take place, outputs
produced, processing done and what storage may be needed.
The next step followed is designing the new system and resolving problems of the
current system.

User Requirements is written by the analyst for business managers with very few
technical details to allow the customers to check what the analyst proposes
Information Requirement is the information needed to support the business. It is
made up of what? and when?

The User and Information Requirements are then turned into the requirement
Specification outlining the improvements and expectations of the new system.

System Specifications are input/output devices and software that are identified using
the DFD to run the new system.

2. Design: designing a new system to correct the problems identified in the analysis
Based on the information from the analysis stage, a new system is developed to
resolve the identified issues of the current system.
Users should be able to interact with a system via a data capture form (DCF), making
it easier and quicker to input data.

Page 2 of 8
Data Capture Form example:

a. Design of flowchart & algorithm

i. Algorithm: Step-by-step procedure of the solution theoretically
ii. Flowchart: Step-by-step procedure of the solution diagrammatically

A database should be created before the data input form is created while
considering:
• Type of data captured & inputted
• Different tables are required, and relationships that may be
established
• Different fields (including Key) required
• Data types required for each field
o Text
o Integer (numeric)
o Double
o Boolean (Yes/No)
o OLE Objects (Image)

b. Select the Data Capture Form

i. Paper-based Data Capture Form
ii. Computerized Data Capture Form

Page 3 of 8
c. Design the Data Capture Form
i. Paper-based Data Capture Form
Clear Heading & Instructions
Clear Fonts & Text Styles
1. Heading
2. Subheading
3. Field Names
4. Text Boxes / Checkboxes / Character boxes
5. Required Instructions
ii. Computerized Data Capture Form
1. Heading
2. Subheading
3. Field Names
4. Form Controls
5. Functional Buttons
6. Navigational Buttons
7. Required Instructions

d. Design the Verification and Validation

What is the difference? The source document may contain errors.
Verification only checks that data is copied correctly and does not check if the
data is reasonable/sensible. One example of Validation is the Length Check,
which checks the number of characters. Visual verification is done to compare
the typed data with the original source visually, or Double Data Entry
verification is done where the computer compares two versions of the typed
data. Validation may not pick up that although the data is acceptable, it may
still be incorrect.

i. Verifications- a way of preventing errors when data is copied

Methods of double-checking are used to see if the data is correct
1. Visual Check: Comparing the typed data with the original
data source visually
2. Double Entry: Entering the same data twice & comparing
each other
ii. Validation- Checks whether the data entered fulfill specific criteria
and if it is sensible or not, ensuring the data is valid
1. Presence Check: data entered in Required Field
2. Range Check: 2 boundary values, min & max
3. Limit Check: 1 boundary value, min OR max
4. Length Check: number of characters
5. Consistency Check: related fields that should match each
other
6. Boolean Check: specifies the possibilities
7. Check Digit: extra digit added to a number calculated from
the digits
8. Format/Picture Check: checks data is in a specific format
9. Type/Character Check: checks the input data does not
contain invalid characters
10. Lookup Check: checks whether data entered, exists, and is
stored in a table of data

Page 4 of 8
 e. Design the Testing Plans
i. Normal Test Data: values between a given range
ii. Abnormal Test Data: values outside the range
iii. Extreme Test Data: values of the limits of the range
iv. Live Data: real data with known outcomes

f. Design the File Structure

i. Field Name
ii. Field (data) Type
Data Type Description Examples
Alphanumeric Can store both letters and numbers AB123CD
Character Only one single letter X
Text Stores a string of letters or numbers example_text
Boolean Stores data as Yes/No Y or N
Numeric Integers (whole numbers) 280
Decimal/Real (non-integer values) 45.69
Currency (inclusion of currency symbols) $175.5
Date/Time (inclusion of dates and time in data) 15/04/2023
iii. Field Length
iv. Primary Key

g. Design the Screen layouts & reports

i. Cancel
ii. Ok
iii. Print

3. Development & Testing: developing and testing a new system

Development (creating)
Stages:
a. Creating the Data Capture Form
b. Creating the Validation & Verification
Validation Rules: Checks whether only the correct values may be
entered into the fields.
c. Creating the File Structure
d. Creating the Testing Plans
e. Creating the Screen layouts and Reports
User Interface: Checked to see if User Friendly and different
components work (Navigation Buttons/Save/etc)

Page 5 of 8
Each Development stage is checked to ensure there are no errors in the system.

➢ Finalizing all the hardware & software

➢ Establishing the Network

Testing
Testing takes place, ensuring all components of the
system work correctly before the system is
implemented.

• Software Systems are developed in Modular

Form, which means each part of the system
is developed separately by the programmer.
• This allows each module to be tested
separately once developed.
• If errors are found, modifications are made
to the system to correct (fix) these problems
o Possible Modifications made:
▪ Data/File Structure
▪ Validation Rules
▪ Input Methods
▪ Output Formats

A test plan would include:

• What to test
• Test Data used
• Expected Outcome of the Test
Example: Data Range is 20 to 1000
A) Normal
Normal Data – Data within the range
Example – 21 to 999
B) Abnormal
Abnormal Data – Data outside the range limits
Example – Less than 20 or over 1000
C) Extreme
Extreme Data – Data on the boundaries of the range
Example – 20 OR 1000

Page 6 of 8
 4. Implementation: replacing the old system with the new system
Method Description Advantages Disadvantages
Direct The existing system is stopped and • The entire system would have been • If the new system fails, the old
Implementation replaced by the new system thoroughly tested before its system is not available to fall back
immediately implementation, so there is less to
chance of errors

The data that was inputted into the • Costs are reduced as only one system • There may not be enough time to
existing system is now inputted is being used. Tasks are not duplicated provide training to employees
into the new system
Parallel Running The existing and new systems will • If the new system does not meet the • Tasks will be duplicated as data is
work together until the new requirements, then the old system is inputted into both systems
system is fully mature to take over. still available

Data is inputted into both systems • Employees can be trained gradually on • This will require more employees,
while they are running at the same how to use the new system which will cause more costs
time (paying salaries) for the employers
Phased The new system is gradually • You only introduce an additional part • Time-consuming because every
Implementation introduced. When parts of the new of the system if the current phase module of the system, which is
system are working satisfactorily, works correctly implemented, needs to be
then more elements of the system evaluated
are phased in.
• If a part of the new system does not • Several training sessions would be
meet the requirements, then you can required for employees when
Eventually, the old system will be always go back to the old system, each module of the new system is
phased out over time. which was working introduced
Pilot Running The new system is piloted (trialed) • If the new system does not meet the • It could take a while for the entire
in one part/department of an requirements, then only one system to be implemented across
organization department is affected all departments

If the pilot is successful, then it will • Training can take place in one • If the system fails in one
be implemented across all department at a time, and then department, then modifications
departments employees could be used in other and further training would be
departments to help with training required, resulting in delays

Page 7 of 8
5. Documentation: creating technical & user documentation for the new system
Two documents are made
a. User Documentation (end-users): designed to help users how to use the
software. This may consist of any of the following:
i. how to do a search
ii. how to sort data
iii. how to do printouts
iv. how to add, delete or amend records
v. purpose of the system
vi. limitations of the system
vii. screen layouts
viii. print layouts
ix. hardware/software requirements
x. error handling
xi. faqs (frequently asked questions) / troubleshooting guide
xii. tutorials

b. Technical Documentation: designed to help programmers make

improvements later to the system or repair the system who may need to
edit the system later on. This may comprise of the following:
i. program coding
ii. programming languages used
iii. program flowcharts
iv. purpose of the system
v. limitations of the system
vi. input formats
vii. hardware/software/minimum memory requirements
viii. known ‘bugs’ in the system
ix. file structures
x. sample runs
xi. list of variables used
xii. output formats

6. Evaluation: evaluating whether the new system meets the design requirements
The final stage of the system life cycle is to evaluate the newly implemented system
fully. The purpose of the evaluation is to refer to the requirement specification to see
whether the new system has resolved the issues of the previous system.
a. Compare the solution with the original task requirements
b. Identify any limitations and necessary improvements to the system
c. Evaluate the users responses to the results of testing the system
d. Compare test results from the new system with the old system results

After the evaluation, if there are any problems or limitations with the system from a
technical or user point of view, the system analyst will refer to the design stage of the
system’s life cycle.

Based on the feedback, any necessary changes could be made to improve the overall
efficiency and usability of the new system, either by updating the hardware or
software.

Page 8 of 8