1.5

A study leading to a preliminary report to the end user to be advised on: Technical Practicality, Cost Effectiveness, Time Scale, Budget. To provide information required to support a decision to proceed

• Feasibility Study • Analysis • Design • Implementation • Testing • Changeover • Maintenance

removing layers of complexity to reduce the problem to essential features

Investigation into a problem and how to solve it • identify the main requirements • identify IPSO from system • describe system using DFD • develop ER diagrams • identify constrains • specify hardware/software required

breaking down a problem into smaller sub problems

• Suitable when requiring lots of info from few staff • choose key stakeholders • Gather large amount of information. • Judgements on validity – Body language • Analyst can respond and ask follow-up questions to get detailed responses about key parts • Time consuming and expensive • Need trained interviewer • Difficult to analyse large amount of information • Difficult to analyse large variety of information

• Cheap to produce for large number of people • Distributed worldwide • Completed online • Need to be designed by experts • May be ‘too busy’ to complete • May provide false answers

• Find out current data storage requirements • Can see data flow and document trail throughout, from start to finish

• Shadow emploees • Gather information first hand • Confirm findingings from other modes of investigation

Entering Data (2 Boxes)

Calculation, sort, filter (rounded box)

Provides data to/from a process (box with no right line)

Must be labelled with data, direction of flow of data (arrow)

Design team will create accurate technical documents to instruct the programmers.

Programmers consider: - Level of language - Type of language - Choice of language -IDE - Translation method - Rules for writing/debugging

Testing carried out in house by employees to test functionality and takes placebefore beta testing

When software close to finished product is released to an audience outside of the company and their comments are recorded

Testing performed by the customer in their own environment

• Sudden change to a new system • Simple but dangerous • Used if there is no old system or is it broken/unusable • All new systems liable to have bugs

• System is replaced feture by feature • Projects are often split into modules • Replacing modules of old system with new system • User can get used to new system gradually • Training done in stages • Difficulties managed in one area can be in the next area • Slower to get new system started

• Whole system is replaced departmetn by department • Large organisations tend to have more than one site • Tested on a limited number of sites • Whole system can be fully trialled • Only part of the system is affected by failure • Pilot staff can help train other staff • Difficulties identified by one department can be fixed • Slow • No backup if failure

• Both systems running together for a time • Every action is duplicated on each system • Safe, not catastrophic • New system available to all • IO can be compared • Expensive as needs staff to operate both systems • Confusion having 2 systems

When system functionality is improved/ enhanced EG search time reduced

When the system is changed to run on new hardware or software platform EG switch from windows to linux