Professional Documents
Culture Documents
1-System Analysis and Design Part 1
1-System Analysis and Design Part 1
Idea…Theme…Concept..
Design…Drafts…Blueprints….Construct….As
Built…
2
Suppose a company has been using an
existing computer system for a number
of years. They have decided to replace
the current system with a new one. After
a number of years of successful
operation, what would initiate this need to
upgrade?
• The existing computer equipment is now
obsolete (it cannot be repaired anymore).
• Changes to laws or taxes requiring radical
overhaul of software.
• More suitable hardware is now available to
improve efficiency and reliability.
• There is a need to expand the company.
System Analysis and
Design
5
System Analysis and Design
• Step by step process for developing
high-quality information systems.
6
But wait…..
What type/kind of system?
7
Systems
• Within organizations and businesses
• systems of communication, financial systems,
manufacturing systems, etc.
• systems that make the organization or
business work
8
System Analysis
• Review an existing system
• Suggest improvements
9
There are different
methods in analyzing.
10
Methods in Analyzing
• Manual paper-based system
• Computer-based operation that is no longer
regarded as adequate for the task
11
Systems Analyst
• Improve their systems and become
more efficient, and for businesses,
more profitable
12
Stages in System Analysis
Examining current system and identifying
problems
14
Analysis Stage
1. Fact finding/collecting data from the current system
2. Description of the current system – establishing the inputs,
outputs and processing being done
3. Identification of the problems with the current system
4. Agreeing the objectives with the customer
15
Analysis Stage
5. Identifying and agreeing the customer’s
requirements
6. Interpreting the customer’s requirements
7. Producing a cost-benefit analysis
8. Producing a data flow diagram.
16
Analysis Stage
Common methods used in fact finding
1. Observation
– first-hand
– downside to observation?
2. Questionnaires
– quick and simple
– information gathered is limited
3. Interviews
– Key people
– they take a long time
4. Examination of existing documents
– forms get filled in and passed to other offices 17
Analysis Stage
18
Analysis Stage
19
Analysis Stage
20
Analysis Stage
21
Analysis Stage
• identify the data input to the present system,
and the data output.
22
Analysis Stage
Data flow diagram (DFD).
Reservation system when booking a flight
23
Data flow diagram (DFD).
» What inputs take place during the customer enquiry (in this case, a customer
keys in their flight details, such as names of passengers, passport numbers, dates of
flight, and so on)
» What outputs are produced (in this case, on-screen and e-ticket (QR code) sent to
customer’s smartphone)
» What processing is done (check flights, process customer data, allocate flight
reference number and access booking database; customer flight booking has
to be added to database once all processing completed)
» What storage may be needed (a database is needed to store all the flight booking
24
details).
So…what's the whole point
of doing this?
25
Analysis Stage
• The whole point of any system analysis is to
end up with a better system than presently
exists.
26
http://www.igcseict.info/theory/8/analyse/index.html
Design stage
• design the key parts of the recommended
system
• types of hardware are chosen in the design
stage
27
Make sure that…
• Know all important items
• Know the current process step-by-step
29
Verification and Validation
• In terms of Business..
• Verify through sales or market research
30
Verification and Validation
• In terms of Business..
• Validate through sales target, client
feedback..etc
31
Verification and Validation
• Verification
Double entry
• data is entered twice by two different people then
checks if there are differences
Visual check
• comparing entered data on the screen with the data in
the original document
32
Verification and Validation
• Validation
– data is checked to see if it satisfies certain criteria
when input into a computer
Ex: if the data falls within accepted boundaries
33
Validation checks (routines)
• Range
– This checks to see if the data input lies between
an acceptable upper value and an acceptable
lower value
Ex:
Limiting a temperature range from
10 to 50 degrees Celsius
34
Validation checks (routines)
• Type/character
– This checks to see if the data entered is of the
correct type (i.e. letter or number only)
Ex:
A person’s name should not contain numbers
A person’s height should not contain letters
35
Validation checks (routines)
• Length
- This checks to see if the data input contains only the
required number of characters
Ex:
If a password contains eight characters,
then an input with seven characters or
nine characters, for example,
should produce an error message
36
Validation checks (routines)
• Format
- This checks to see if the data input is in the
correct format
Ex:
Ensures the date is entered in a format such as
dd/mm/yyyy (e.g. 10/12/2023)
37
Validation checks (routines)
• Presence
- This checks that data has been entered into a
field and it has not been left empty
Ex:
when using an online form, a
person’s telephone number may be a ‘required
field’; if no data is entered, this should give rise to
an error message
38
Validation checks (routines)
• Check digit
- This is an extra digit added to a number which
has been calculated from the other digits
Ex:
Check digits can identify three types of error:
-1 if two digits have been transposed during
input; for example, 13597 instead of 13579
-2 an incorrect digit has been entered; for
example, 13559 instead of 13579
-3 a digit has been missed out or extra digit added;
for example, 1359 or 135799 instead of 13579 39
40
Development and testing
• Create new system and fully test it
41
Development and testing
• Development stages
– the file structure needs to be finalized at this stage
Ex: In Database (Access)
• type of data stored in each field
• length of each field
• which field will be the key field
• routines have to be fully tested
42
Development and testing
• Development stages
– Hardware are used to interface with the final system
needs to be identified
ex: How the screens (and any other input devices) will be
used to collect the data and the way the output will be
presented
• Necessary to finalize how these devices are used with the
system when it is implemented
43
Development and testing
• Testing
-whole system needs to be tested (i.e. all
modules functioning together)
- there may be data clashes, incompatibility
and memory issues
44
Just like our body
Development and testing
• Testing
-Normal, Extreme or Abnormal Data
• Normal- acceptable/valid and has an
expected (known) outcome
• Extreme- limits of acceptability/validity
End to end
• Abnormal- outside the limits of
acceptability/validity and should be rejected
or cause an error message
47
Development and testing
• Example of Testing
Inputting a date into a database field. The entered
data must take the format dd/mm/yyyy and all
data must be numeric.
Normal –the month can be any whole number in
the range 1 to 12
Extreme –the month can be either of the two end
values . 1 or 12
48
Development and testing
• Example of Testing
Inputting a date into a database field. The entered
data must take the format dd/mm/yyyy and all
data must be numeric.
Abnormal –none of the following values are allowed as
inputs for the month:
– any value less than 1 (for example, 0, −1, −15, etc.)
– any value greater than 12 (for example, 32, 45, etc.)
– letters or other non-numeric data (for example, July, etc.)
– non-integer values (for example, 3.5, 10.75, etc.).
49