7.
1 Analysis
Stages of Analysis
• Research current system
• Identify inputs and outputs
• Identify processing
• Find problems
• Gather user requirements
• Gather information requirements
• Identify hardware and software needed
Methods of Research
Method Advantages Disadvantages
Reliable data, inexpensive, sees People may change behavior when
Observation
actual system watched
Detailed answers, flexible Time-consuming, expensive, not
Interview
questions anonymous
Cheap, quick, anonymous, many Low return rate, no follow-up
Questionnaire
responses questions
Existing
Gives detailed system information Time-consuming, expensive
Documents
What the Analyst Finds
• Inputs
• Outputs
• Processing
• Storage needs
• System problems
• User requirements
• Information requirements
User Requirements
• Written in simple language.
• Describe what users need from the new system.
Information Requirements
• What information is needed?
• When is it needed?
System Specification
Hardware
• Input devices (barcode readers, scanners, touch screens)
• Output devices (printers, monitors, speakers)
• Storage devices
Software
• Operating system
• Off-the-shelf software (cheap, quick)
• Bespoke software (custom-made but expensive)
7.2 Design
Design Includes
• File structures
• Data structures
• Input forms
• Output formats
• Validation routines
File Structure
A file contains:
• Records
• Fields
• Primary key (unique field)
Common Data Types
• Text
• Character
• Boolean (Yes/No)
• Integer
• Real/Decimal
• Currency
• Date/Time
Validation Checks
Check Purpose
Range Data between limits
Type Correct data type
Length Correct number of characters
Format Correct pattern (e.g. date)
Presence Field not left empty
Check Digit Detect input errors
Data Capture Forms
Good forms should:
• Have clear headings
• Use text boxes
• Use tick boxes/radio buttons
• Use drop-down menus
• Validate data automatically
Output Design
Should:
• Be clear and readable
• Use suitable fonts and colours
• Make full use of screen/page
• Present information logically
7.3 Development and Testing
Why Test?
To ensure:
• Data structures work
• Files work correctly
• Inputs are accepted correctly
• Outputs are correct
• Validation works
Testing Types
Type Meaning
Normal Valid data
Extreme Boundary values
Abnormal Invalid data
Example
Month field:
• Normal: 6
• Extreme: 1, 12
• Abnormal: 0, 13, July
Test Plan Includes
• Test data
• Expected results
• Actual results
• Any actions required
Modular Testing
1. Test each module separately.
2. Fix errors.
3. Combine modules.
4. Test complete system.
7.4 Implementation
Tasks
• Transfer old data
• Train staff
• Change to new system
Changeover Methods
Method Advantage Disadvantage
Direct Fast, cheap Risky if system fails
Parallel Safe backup Expensive and time-consuming
Pilot Only one area affected if failure occurs Slower rollout
Phased Easier to find problems Very time-consuming
7.5 Documentation
Technical Documentation
For programmers:
• Program code
• Flowcharts
• Hardware/software requirements
• File structures
• Validation rules
• Error messages
User Documentation
For users:
• Installation instructions
• How to use system
• Input/output examples
• Error handling
• Tutorials and FAQs
7.6 Evaluation
Evaluation Checks
• Compare with original requirements
• Identify limitations
• Gather user feedback
• Compare old and new systems
• Measure performance improvements
Possible Outcomes
Hardware updates
• User feedback
• New technology
• Company growth
Software updates
• User feedback
• Business changes
• Legal requirements