Developing ICT solutions

Mer som dette

CM - Chapter 3 - Why organizations change

Ved Sander van der Kolk

The directors of a property company are looking at whether they shouldconstruct a new office building. The economy is doing well, and the amount ofvacant office space is reducing sharply. As part of their decision they decide to use the 6 Thinking Hats te

Ved Serik Ayazhan

Propaganda Analysis

Ved Erin Graffis

Computational Journalism

Ved Lluis Codina

Developing ICT solutions

Review and maintenance

Perfective maintenance To make the system as efficient as possible by tweaking, may invlove adding extra functions to amke the solution even better

Adaptive maintenance Alter the system to meet the new requirement of the organisation

Corrective maintenance Putting right any reported errors once the system has become operational

This is run when the system is installed and monitored its process, it is a continous, ongoing process. Constantly reviewed.

Testing

Deliverables - Test data and results - Modifed user guide - Client approval to install

Operational testing This test runs in the actual environment in which the solution will be working

User testing The actual users of the system will put it through its paces and offer their comments. It is the final stage of testing before the system goes into operation

System testing This tests the complete, intergrated solution in preparation for user testing

Functional testing This is to test the operation of the system and may pick up errors that were missed at the module/unit testing stage. This is an example of black box testing.

Integration testing When module testing is completed, the modules are combined one at a time at each integration stage and debugged

Module/unit testing This test the individual sections of the software to make sure that each section works as intended. This is an example of white box testing.

Any new system should be thoroughly tested before it goes live.

Constructing the solution

Deliverables - Working system - Documentation of solution - Draft version of user guide

Writing code This gives the designer much more flexibility to produce a solution that fits the client's needs exactly. This takes longer and the likelihood of errors are more than customising a package.

Customising a package A generic or special purpose package which is suitable to be used for producing the solution is probably the cheapest and quickest method. However, it may require compromises as the designer will not have the completely free hand that building. The solutions built this way are probabaly less risky than those coded from scratch and more help and advice is likey to be available.

Installation and conversion

Deliverables - Fully functional solution (signed off by the client) - Full documentation including user guide and techinal documentation

The system is put into its working environment to be used by the client. Also invloes conversion fo any existing system that will be superseded by the new solution and linking to any other systems with which it needs to operate. The system documentation will be presented to teh client at this stage, with operational user guide and technical documnetation.

Design

Deliverables: - Details of file definitions, data structures and processes - Designs of outputs - A test strategy and plan - Detailed time plan for this satge of the project

It will include detailed descriptions of: - The software, tools and techniques to be used, and justification of why they have been chosen - Data capture and validation methods - Desgins for the user interface - Processing - Output - How the solution is to be tested

What is design? The design explains in detail how it is going to do it and how it will produce a solution

Analysis

Deliverables at this stage - Clear and detailed user requirements specification (signed off by end user) - A list of tasks that need to be completed together with a schedule of timings - A Gantt chart for project management - Assessment of the users' current ICT skill level and training requirements - Hardware and software requirements and limitations - Performance indicators or evaluation criteria to measure the success or failure of the project - An outline of the propsed method of solution

Formal Data Analysis Techniques - Data flow diagrams - System flow charts - Data decomposition diagrams

How analysis is carried out? - Interviews with the users - Questionnaire and surveys - Analysis fo existing paperwork - Observation of current system

The aim of analysis - Establish the current system - Strength and weaknesses of the current system - What is required of the new system - Any constraints that my be placed on the new solution

What is analysis? Developed to meet a need or slove a problem