INFO 3 C5 - Developing ICT solutions
Success and Failure of an ICT system
Intro
ICT projects are designed to improve an existing system or to create a solution to a problem created by a new technique
Inadequate analysis
A company may have branched out into something new, so an ICT project is implemented to solve problem
Creating a solution leaves open to new problems, companies are well aware of these issues
A project manager is appointed to oversee the IT project and a team of people, either from within or a software house develop the solution
All new projects are at risk of failure, main reason tend to be very complex and use extensive software, by nature it has a greater tendency to fail
Failures of the new NHS system and of the benefits IT system
Air Traffic control system was a success but was out of date by the time it was introduced - system broke down
Lack of management involved in the design
Over-emphasis on the computer system
Concentration on low-level data processing
Lack of management knowledge of ICT systems
Inappropriate/ excessive management demands
Lack of teamwork
Lack of professional standards
Poor testing
Inadequate/inappropriate changeover method
Project managers job to meet the client requirements
Locates any problems that may affect the solution
Analysis of organisation and of the client is fundamental to making a good outcome
Documentation must be produced in a way that is understandable to the client so they can sign it off
Talking to all levels of staff is important as it gives a much clearer picture of the solution
A poor analysis will give a weak foundation for development
very important that the client and users are involved in the design of a system; they will be the ones using it
Companies focusing in on the product itself - new tech, it may not operate as well as a system
Also important for management and users to be on appropriate level of organisation to ensure all reqs are met
Failure due to inadequate attention to the whole system and the lack of knowledge of how the info flows in the system
Must be in line with reqs - not on what the computer can do
Information in the system is not provided with the right level of detail; too much emphasis low-level data processing than high-level info processing
Info to be produced so decisions can be easily made and understandable for managers a right levels
Managers need to have an up-to-date knowledge of the current system and capabilities. They should be able to make informed decisions rather than be blinded from science and jargon
Input is needed from managers about what systems are needed so it benefits the business as a whole
A team must work well together with strong links between them
Cooperation and good strong leadership are essential for a team to work together
Must work to time; and be balanced and effective
Managers with small knowledge of the system may give excessive reqs to project managers
If these demands are not met or fail it must not be used as it does not meet expetation
Important for PM to keep a constant contact with managers and both are willing to compromise on things for system to be a success
Can lead to missed deadlines, which in turn can mean projects extending and costs rising
Without standards, different team members may be unclear of which tasks their colleagues have completed and whether all aspects are covered
They ensure that all team members know what processes and procedures to use during development
When employee leave or is ill team can pick up pieces as if nothing happened
If a test plan is inadequate than errors can slip through and cause problems later on
If project overruns there is tenancy for it to speed up testing process meaning errors go unchecked
Consumer will then typically do testing for the company
Important to have a safe system before it is installed
Many systems that are introduced can be put alongside old system and eventually phased out
Some systems have to be implimented straigh away and are more likey to fail - there is also no effective backup or an old system to return to