1. ANALYSIS
1.1. COLLECTION OF DATA
1.2. DESCRIPTION OF CURRENT STATUS
1.3. RECOGNISE AND RESULT OUT PROBLEM WITH THE SYSTEM TO THE CLIENT
1.4. CUSTOMER REQUIREMENTS
1.5. COST-BENEFIT ANALYSIS
1.6. DATA FLOW DIAGRAM
2. DESIGN
2.1. DESIGNING INPUT FORMS
2.2. DESIGNING SCREEN LAYOUTS
2.3. DESIGNING OUTPUT FORMS
2.4. PRODUCING PSEUDO CODE
2.5. DESIGNING REQUIRED VALIDATION RULES
2.5.1. RANGE CHECK
2.5.2. LENGTH CHECK
2.5.3. CHARACTER/TYPE CHECK
2.5.4. FORMAT /PICTURE CHECK
2.5.5. LIMIT CHECK
2.5.6. PRESENCE CHECK
2.5.7. CONSISTENCY CHECK
2.5.8. DIGIT CHECK
2.6. SELECTING APPROPRIATE DATA VERIFICATION METHODS
2.6.1. DOUBLE ENTRY
2.6.2. VISUAL CHECK
2.7. DESIGNING AND AGREEING TO FILE STRUCTURES AND TABLES.
2.8. DESIGNING REQUIRED HARDWARE AND SOFTWARE
2.9. PRODUCING ALGORITHMS / FLOWCHART
2.10. TESTING PLAN DESIGNING
3. DEVELOPMENT AND TESTING
3.1. TESTING STRATEGIES
3.1.1. ABNORMAL
3.1.2. NORMAL
3.1.3. EXTREME
4. IMPLEMENTATION
4.1. TRAIN STAFF ON NEW SYSTEM
4.2. TRANSFER OF PAPER/ELECTRONIC FILES TO NEW SYSTEM
4.2.1. DOCUMENT SCANNING
4.2.2. KEYING IN DATA
4.2.3. DOWNLOADING FILES TO NEW DATABASE
4.3. CHANGEOVER TO NEW SYSTEM
4.3.1. DIRECT CHANGEOVER
4.3.2. PARALLEL RUNNING
4.3.3. PILOT IMPLEMENTATION
4.3.4. PHASED IMPLEMENTATION
5. DOCUMENTATION
5.1. USER DOCUMENTATION
5.2. TECHNICAL DOCUMENTATION
6. EVALUATION AND REVIEW
6.1. TO EVALUATE THE SYSTEM, THE ANALYST WILL:
6.1.1. COMPARE FINAL SOLUTION WITH ORIGINAL REQUIREMENT
6.1.2. IDENTIFY LIMITATIONS IN THE SYSTEM
6.1.3. IDENTIFY NECESSARY IMPROVEMENTS NEED TO MADE IN THE SYSTEM
6.1.4. EVALUATE USER'S RESPONSE TO NEW SYSTEM
6.1.5. COMPARE TEST RESULTS FROM NEW SYSTEM WITH THAT OF OLD SYSTEM
6.1.6. COMPARE PERFORMANCE OF NEW SYSTEM WITH OLD SYSTEM
6.1.7. OBSERVING USER'S PERFORMING SET TASKS, COMPARING OLD ONE WITH NEW
6.1.8. COMPARE TIME TAKEN TO COMPLETE TASKS
6.1.9. SURVEY USERS TO GATHER INFO ON THE WORKING OF NEW SYSTEM
6.2. HARDWARE NEED TO UPDATED WHEN:
6.2.1. FEEDBACK FROM END USERS
6.2.2. NEW HARDWARE COMES ON MARKET MAKING CHANGES NECESSARY
6.2.3. CHANGES WITHIN THE COMPANY WHICH REQUIRE NEW DEVICES TO BE ADDED/UPDATED
6.3. SOFTWARE NEEDS TO UPDATED WHEN:
6.3.1. FEEDBACK FROM END USERS
6.3.2. CHANGES TO COMPANY STRUCTURE/MODIFICATION IN HOW THE COMPANY WORKS FOR SOFTWARE
6.3.3. CHANGES IN LEGISLATION NEED MODIFICATIONS IN SOFTWARE