3.3.1
THIS PRESENTATION COVERS
• A BRIEF LOOK AT THE COMPONENTS THAT MAKE UP THE SYSTEM LIFE
CYCLE.
INTRODUCTION
• LARGE SYSTEM DEVELOPMENT PROJECTS MAY INVOLVE A LOT OF PEOPLE
WORKING OVER SEVERAL MONTHS OR YEARS AND ON DIFFERENT PARTS OF A
PROJECT.
• THIS MEANS THEY CAN’T BE ALLOWED TO WORK IN AN AD-HOC, HAPHAZARD,
FASHION.
• THE GOALS OF A PROJECT MUST BE THOROUGHLY UNDERSTOOD AND FORMAL
PROCEDURES AND METHODS MUST BE APPLIED TO ENSURE PROJECTS ARE
DELIVERED ON TIME AND MEET ALL REQUIREMENTS.
INTRODUCTION
• THERE ARE PROBLEMS WITH WORKING ON A PROJECT IF YOU DON’T HAVE A PLAN:
• HOW CAN YOU PRODUCE A GOOD PROJECT IF YOU AREN’T SURE ABOUT THE PROBLEM?
• HOW CAN A PROJECT BE BUILT IF IT IS NOT DESIGNED?
• HOW CAN IT BE INSTALLED IF IT IS NOT TESTED PROPERLY?
• IF A PROJECT LEADER LEAVES AND SOMEONE TAKES OVER HOW CAN THEY EFFECTIVELY
MANAGE THE PROJECT WITHOUT KNOWING WHAT WORK HAS BEEN DONE AND AT WHAT
STAGE THE PROJECT IS AT?
• HOW CAN CHANGES BE MADE TO A PROJECT IF THE DOCUMENTATION IS INCOMPLETE?
SYSTEM LIFE CYCLE
• THE SYSTEMS LIFE CYCLE ENSURES THAT PEOPLE ARE WORKING IN A
VERY ORGANISED, METHODICAL, MANNER.
• EACH STAGE IS COMPOSED OF CERTAIN WELL-DEFINED ACTIVITIES AND
RESPONSIBILITIES AND EACH STAGE MUST BE COMPLETED BEFORE THEY
NEXT STAGE BEGINS.
• THERE ARE DIFFERENT MODELS OF THE SYSTEM LIFE CYCLE BUT MOST
CONTAIN 5-7 STAGES.
Feasibility
Study
Evaluation &
Maintenance
Analysis
Design
Documentation
Installation
Implementation
Testing
Feasibility
Study
Evaluation &
Maintenance
Analysis
Design
Documentation
Installation
Implementation
Testing
FEASIBILITY STUDY
• THE FEASIBILITY STUDY IS THE FIRST STAGE OF THE SYSTEM’S LIFE CYCLE.
• WHEN A PROBLEM IS RECOGNISED AND IDENTIFIED THE FEASIBILITY
STUDY IS INITIATED.
• THE PURPOSE OF THE FEASIBILITY STUDY IS TO FULLY UNDERSTAND THE
PROBLEM AND TO WORK OUT IF THE PROBLEM IS WORTH FIXING.
FEASIBILITY STUDY
• THERE ARE FIVE MAIN FACTORS TO BE CONSIDERED:
ECHNICAL FEASIBILITY
CONOMIC FEASIBILITY
EGAL FEASIBILITY
PERATIONAL FEASIBILITY
CHEDULE FEASIBILITY
TECHNICAL FEASIBILITY
• THIS INVOLVES LOOKING AT:
• WHETHER THE TECHNOLOGY EXISTS TO IMPLEMENT THE PROPOSED
SYSTEM; OR
• WHETHER THIS IS A PRACTICAL PROPOSITION;
ECONOMIC FEASIBILITY
• THIS INVOLVES ESTABLISHING THE COST-EFFECTIVENESS OF THE
PROPOSED SYSTEM.
• IF THE BENEFITS DO NOT OUTWEIGH THE COST THEN THE PROJECT IS
NOT WORTH GOING AHEAD WITH.
LEGAL FEASIBILITY
• THIS PART OF THE FEASIBILITY STUDY CHECKS TO SEE IF THE
PROPOSED SYSTEM FALLS WITHIN LEGAL GUIDELINES.
• FOR EXAMPLE, WOULD THE NEW SYSTEM CONTRAVENE THE DATA
PROTECTION ACT?
OPERATIONAL FEASIBILITY
• THIS IS CONCERNED WITH WHETHER THE CURRENT WORK PRACTICES
AND PROCEDURES ARE ADEQUATE TO SUPPORT THE NEW SYSTEM.
• IT IS ALSO CONCERNED WITH SOCIAL FACTORS
• HOW THE ORGANISATIONAL CHANGE WILL AFFECT THE WORKING
LIVES OF THOSE AFFECTED BY THE SYSTEM.
SCHEDULE FEASIBILITY
• THIS LOOKS AT HOW LONG THE SYSTEM WILL TAKE TO DEVELOP, OR
WHETHER IT CAN BE DONE IN A DESIRED TIME-FRAME.
FEASIBILITY STUDY
• AT THE END OF THIS STAGE A FEASIBILITY REPORT IS PRODUCED BY A
SYSTEMS ANALYST.
• IF THE REPORT CONCLUDES THAT THE PROJECT SHOULD GO AHEAD,
AND THIS IS AGREED BY THE SENIOR MANAGERS, THEN A DETAILED
REQUIREMENTS ANALYSIS WILL BE PRODUCED.
Feasibility
Study
Evaluation &
Maintenance
Analysis
Design
Documentation
Installation
Implementation
Testing
Feasibility
Study
Evaluation &
Maintenance
Analysis
Design
Documentation
Installation
Implementation
Testing
ANALYSIS
• THIS IS A MORE DETAILED REPORT WHICH FOCUSES ON THE CURRENT
SYSTEM AND THE REQUIREMENTS OF THE NEW PROPOSED SYSTEM.
• IT IS THE SYSTEMS ANALYST’S JOB TO FIND OUT ABOUT CURRENT
METHODS, USER REQUIREMENTS AND TO ASSESS THE FEASIBILITY OF
A PROJECT.
ANALYSIS
• GATHERING DETAILS ABOUT THE CURRENT SYSTEM MIGHT INVOLVE:
• INTERVIEWING STAFF FROM DIFFERENT LEVELS OF THE ORGANISATION
FROM END USERS TO SENIOR MANAGERS.
• EXAMINING CURRENT BUSINESS AND SYSTEMS DOCUMENTS AND OUTPUTS.
• SENDING OUT QUESTIONNAIRES AND ANALYSING RESPONSES.
• OBSERVATIONS OF CURRENT PROCEDURES FROM DIFFERENT DEPARTMENTS.
ANALYSIS
• THE ANALYSIS REPORT WILL:
• EXAMINE HOW DATA AND INFORMATION FLOWS THROUGH AN ORGANISATION.
• EXPLAIN WHAT THE PROPOSED SYSTEM WILL DO (NOT HOW IT WILL DO IT).
• SHOW DETAILED COSTS AND BENEFITS.
• EXPLAIN HOW THE SYSTEM WILL BE IMPLEMENTED.
• EXPLAIN WHO THE END USERS ARE, WHAT INFORMATION THEY WILL GET AND IN
WHAT FORM.
Feasibility
Study
Evaluation &
Maintenance
Analysis
Design
Documentation
Installation
Implementation
Testing
Feasibility
Study
Evaluation &
Maintenance
Analysis
Design
Documentation
Installation
Implementation
Testing
DESIGN
• THE FEASIBILITY AND THE ANALYSIS STAGES ARE ALL ABOUT SOLVING THE
PROBLEM.
• BY THE TIME THESE STAGES ARE COMPLETE THE PEOPLE WORKING ON
THE PROJECT WILL:
• UNDERSTAND THE BUSINESS AND OPERATIONS IN DETAIL
• UNDERSTAND THE PROBLEM AREA IN DETAIL
• HAVE AGREED WITH THE CUSTOMER WHAT THEY WANT THE NEW SYSTEM
TO DO
• HAVE OUTLINED THE SOLUTION
DESIGN
• THE DESIGN STAGE IS ABOUT THE CREATIVE SOLUTION TO THE
PROBLEM.
• THERE MIGHT BE MULTIPLE SOLUTIONS OR JUST ONE.
• IN THE EVENT OF MULTIPLE SOLUTIONS FURTHER ANALYSIS MIGHT BE
REQUIRED TO WORK OUT WHICH WOULD BE THE BEST SOLUTION.
WHAT HAPPENS DURING THE DESIGN
STAGE?
• THERE SHOULD BE A DESCRIPTION OF THE OVERALL DESIGN USING DIAGRAMS
AND COMMENTS.
• THE USER INTERFACE SHOULD BE DESIGNED.
• ALL REPORTS AND SCREENS AND NAVIGATION SYSTEMS SHOULD BE DESIGNED.
• DATA VALIDATION RULES AND VERIFICATION PROCEDURES SHOULD BE SPECIFIED.
WHAT HAPPENS DURING THE DESIGN
STAGE?
• DATA VOLUMES SHOULD BE CALCULATED AND STORAGE AND BACKUP DEFINED.
• FUNCTIONAL DESCRIPTIONS OF ALL PROCEDURES, MODULES,
FUNCTIONS ETC SHOULD BE PRODUCED.
• A COMPLETE TEST PLAN WITH THE DATA TO BE USED AND PREDICTED
OUTPUTS SHOULD BE DONE.
DESIGN
• AN EFFECTIVE DESIGN WOULD ALLOW YOU TO GIVE THE DESIGN
DOCUMENTATION TO ANY PROGRAMMER OR BUILDER OF THE
SYSTEM TO RECREATE IT EXACTLY.
• THE PROGRAMMER/BUILDER SHOULDN’T NEED ANY HELP OTHER
THAN WHAT IS WITHIN THE DESIGN DOCUMENTATION.
Feasibility
Study
Evaluation &
Maintenance
Analysis
Design
Documentation
Installation
Implementation
Testing
Feasibility
Study
Evaluation &
Maintenance
Analysis
Design
Documentation
Installation
Implementation
Testing
IMPLEMENTATION
• DURING THIS PROCESS THE PROJECT DEVELOPMENT TEAM WILL USE THE
DESIGN DOCUMENTATION TO CREATE THE ACTUAL PRODUCT.
• THIS STAGE SHOULD NOT BE CONFUSED WITH THE INSTALLATION OF THE
ACTUAL PRODUCT WHICH INVOLVES TAKING THE FINISHED PRODUCT
AND INSTALLING IT ON THE CUSTOMER’S PREMISES.
• THIS STAGE CAN ONLY BE SUCCESSFUL IF THE DESIGN STAGE WAS
CARRIED OUT PROPERLY.
Feasibility
Study
Evaluation &
Maintenance
Analysis
Design
Documentation
Installation
Implementation
Testing
Feasibility
Study
Evaluation &
Maintenance
Analysis
Design
Documentation
Installation
Implementation
Testing
TESTING
• TESTING SHOULD FOLLOW THE TEST PLAN WHICH WAS LAID OUT IN THE DESIGN
DOCUMENTATION AND SHOULD ALWAYS BE CARRIED OUT.
• THE REASONS:
• A COMPANY NEEDS TO ENSURE THEIR REPUTATION FOR DEVELOPING GOOD SYSTEMS
IS INTACT.
• A GOOD PROGRAM WILL GAIN IN POPULARITY ONLY IF CUSTOMERS SEE IT AS A
GOOD PROGRAM.
• A BAD SYSTEM WILL MEAN THAT SYSTEM WILL BE AVOIDED IN THE FUTURE AND
PERHAPS CUSTOMERS WON’T PAY FOR YOUR SERVICES.
• A SYSTEM THAT CAUSES ACCIDENTS MAY LEAD TO LEGAL PROBLEMS.
Feasibility
Study
Evaluation &
Maintenance
Analysis
Design
Documentation
Installation
Implementation
Testing
Feasibility
Study
Evaluation &
Maintenance
Analysis
Design
Documentation
Installation
Implementation
Testing
INSTALLATION
• ONCE A SYSTEM HAS BEEN BUILT AND TESTED IT NEEDS TO BE INSTALLED
IN A WAY THAT ENSURES MINIMAL DISRUPTION TO THE CUSTOMER.
• THINGS THAT SHOULD BE CONSIDERED:
• STAFF TRAINING – CAN THEY USE THE SYSTEM STRAIGHT AWAY?
• HOW DO YOU GET ALL THE CURRENT DATA ON THE OLD SYSTEM ONTO THE
NEW SYSTEM – HOW LONG WILL IT TAKE? IS IT TRANSFERABLE IN IT’S
CURRENT FORMAT?
• THE HARDWARE/SOFTWARE FOR THE NEW SYSTEM MUST BE IN PLACE. ANY
ADDITIONAL HARDWARE/SOFTWARE REQUIRED FOR THE SYSTEM WILL NEED
TO BE BOUGHT AND STORED SAFELY UNTIL IT IS NEEDED.
INSTALLATION
• THAT ARE FOUR STRATEGIES THAT YOU COULD EMPLOY:
Parallel running
Pilot running
Strategies
Direct changeover
Phased implementation
PARALLEL RUNNING
• IN THIS INSTANCE THE OLD SYSTEM RUNS ALONG SIDE THE NEW SYSTEM.
• THIS ALLOWS THE NEW SYSTEM TO PROVE IT WORKS BEFORE SHUTTING
DOWN THE OLD SYSTEM.
• IT GIVES STAFF AN OPPORTUNITY TO GET USED TO THE NEW SYSTEM BUT
IT MEANS DOUBLING THE WORK LOAD AS YOU HAVE TO INPUT DATA
INTO BOTH SYSTEMS.
• ONCE EVERYTHING CHECKS OUT…THEN THE OLD SYSTEM CAN BE SHUT
DOWN.
PILOT RUNNING
• THIS IS SIMILAR TO PARALLEL RUNNING BUT WITH A DIFFERENCE.
• INSTEAD OF BOTH SYSTEMS RUNNING TOGETHER AT THE SAME TIME, ONLY A PORTION
OF THE NEW SYSTEM WILL BE RUNNING IN PARALLEL. WHEN ONE PORTION CHECKS
OUT OK THEN ANOTHER PORTION OF THE NEW SYSTEM IS PILOTED.
• THE TERM PILOT RUNNING CAN ALSO BE USED WHEN A LARGE ORGANISATION
CHANGES SYSTEMS OVER TIME.
• FOR EXAMPLE, A SUPERMARKET CHAIN MIGHT INSTALL NEW CHECKOUT SYSTEMS IN A FEW
BRANCHES TO MAKE SURE IT WORKS BEFORE INSTALLING THEM IN THE REMAINING
BRANCHES.
DIRECT CHANGEOVER
• THIS IS WHERE YOU SHUT DOWN THE OLD SYSTEM AND START
OPERATING THE NEW SYSTEM STRAIGHT AWAY.
• STAFF TRAINING NEEDS TO TAKE PLACE IN ADVANCED BUT OVERALL
WORKLOAD SHOULDN’T BE AFFECTED.
• THE PROBLEM WITH THIS METHOD IS THAT IF SOMETHING GOES
WRONG THEN THE SYSTEM WILL NEED TO BE FIXED AS SOON AS
POSSIBLE BECAUSE YOU CAN’T FALL BACK ON THE OLD SYSTEM.
PHASED IMPLEMENTATION
• DURING A PHASED IMPLEMENTATION, PARTS OF THE NEW SYSTEM
REPLACE PARTS OF THE OLD SYSTEM.
• PARTS OF THE NEW SYSTEM CAN THEN BE USED FOR STAFF TRAINING
AND CAN PROVE ITSELF BEFORE THE NEXT PART OF THE NEW SYSTEM IS
INSTALLED.
• THIS METHOD TAKES A LONG TIME COMPARED TO DIRECT CHANGEOVER.
Feasibility
Study
Evaluation &
Maintenance
Analysis
Design
Documentation
Installation
Implementation
Testing
Feasibility
Study
Evaluation &
Maintenance
Analysis
Design
Documentation
Installation
Implementation
Testing
DOCUMENTATION
• DURING THIS PROCESS SYSTEM DOCUMENTATION IS CREATED FOR THE END USER.
• THESE DOCUMENTS MIGHT INFORM THE END USER ABOUT:
•
PROGRAM SPECIFICATIONS
•
WHAT TO DO IF THE SYSTEM CRASHES
•
SECURITY DETAILS
•
HOW TO USE THE SYSTEM (USER GUIDE/MANUAL)
• YOU COULD BREAK THIS DOWN INTO TWO TYPES OF DOCUMENTS:
•
USER DOCUMENTATION
•
TECHNICAL DOCUMENTATION
Feasibility
Study
Evaluation &
Maintenance
Analysis
Design
Documentation
Installation
Implementation
Testing
Feasibility
Study
Evaluation &
Maintenance
Analysis
Design
Documentation
Installation
Implementation
Testing
MAINTENANCE
• JUST BECAUSE THE SYSTEM HAS BEEN INSTALLED AND IS BEING USED
DOESN’T MEAN THAT’S THE END OF THE SYSTEM LIFE CYCLE.
• SOME MAINTENANCE MAY BE REQUIRED FOR A RANGE OF DIFFERENT
REASONS.
REASONS FOR MAINTENANCE
• USER HAS DISCOVERED A BUG IN THE SYSTEM.
• THE LAW HAS CHANGED AND THE SYSTEM NO LONGER OPERATES WITHIN THE RULES
OF THE LAW.
• NEW TECHNOLOGY HAS BEEN RELEASED AND THE SYSTEM COULD BENEFIT FROM THE
TECHNOLOGY.
• THE CUSTOMER NEEDS ADDED FUNCTIONALITY WHICH MEANS FURTHER
ENHANCEMENTS ARE REQUIRED.
• THE BUSINESS HAS EXPANDED AND NOW NEEDS TO HANDLE MORE DATA THAN ITS
CURRENT SYSTEM CAN COPE WITH.
EVALUATION
• AFTER THE COMPLETION OF ANY PROJECT IT IS IMPORTANT TO EVALUATE IT.
• THIS SHOULD BE DONE FOR BOTH THE PROJECT DEVELOPMENT TEAM AND ALSO THE CUSTOMER.
• THE PROJECT DEVELOPMENT TEAM NEED TO KNOW IF THEY ESTIMATED COSTS AND TIMINGS
CORRECTLY. THIS WILL HELP THEM GIVE MORE ACCURATE ESTIMATES FOR FUTURE CUSTOMERS.
• THE CUSTOMER WILL WANT TO KNOW IF IT WAS WORTH GOING THROUGH THE PROJECT AND
USE THEIR FINDINGS FOR FUTURE PROJECTS THEY MAY HAVE.
EVALUATION
• THERE ARE VARIOUS QUESTIONS WHICH YOU CAN ASK:
• DOES THE NEW SYSTEM MEET THE SYSTEM REQUIREMENTS?
• DOES THE SYSTEM CONTAIN BUGS?
• DOES IT CRASH?
• IS THE SYSTEM MAKING THE EMPLOYEES MORE EFFICIENT?
• DID THE SELLING PRICE PAY FOR THE WORK THAT WAS DONE?
• ARE EMPLOYEES CONFIDENT IN USING THE NEW SYSTEM?
Feasibility
Study
Evaluation &
Maintenance
Documentation
Analysis
BASIC ANALYSIS
IS IT WORTH GOING AHEAD
WITH THE PROJECT?
Installation
Implementation
Testing
Design
Feasibility
Study
Evaluation &
Maintenance
Documentation
Analysis
DETAILED ANALYSIS
INVESTIGATE REQUIREMENTS,
CURRENT SYSTEM AND FLOW
OF DATA
Installation
Implementation
Testing
Design
Feasibility
Study
Evaluation &
Maintenance
Documentation
Analysis
DESIGN A SOLUTION TO THE
PROBLEM AND PRODUCE A
TEST PLAN
Installation
Implementation
Testing
Design
Feasibility
Study
Evaluation &
Maintenance
Analysis
Design
Documentation
Installation
Implementation
Testing
Feasibility
Study
Evaluation &
Maintenance
Documentation
Analysis
CHECK TO SEE IF THE SYSTEM
WORKS AS EXPECTED
Installation
Implementation
Testing
Design
Feasibility
Study
Evaluation &
Maintenance
Documentation
Analysis
INSTALL THE NEW SYSTEM AT
THE CLIENT’S LOCATION
Installation
Implementation
Testing
Design
Feasibility
Study
Evaluation &
Maintenance
Analysis
Design
Documentation
Installation
Implementation
Testing
Feasibility
Study
Evaluation &
Maintenance
Documentation
Analysis
MAKE CHANGES TO/UPDATE
THE SYSTEM IF NECESSARY
AND EVALUATE IT
Installation
Implementation
Testing
Design