Analysis
Looks in to detail of the current system or requirements, this person is called a system analyst who also investigates new requirements.
Analysis will involve:
- Understanding of the existing system.
- Understanding the proposed system if there is no existing system.
- Gathering and analysing the user requirements.
- Producing a logical specification.
Design/Specification of Solution
The system analyst will need to produce a design and specification that will enable the system to actually be built in the next phase.
Design will involve:
- Designing the system in line with the user requirements.
- Creating the design specification, for hardware, software , telecommunications, databases, personnel and procedures that will enable the usable system to be built.
Building The Solution
This is the stage where the system is actually built according to the design.
Building will involve:
- Staff using the physical design produced in the last stage to produce a working system.
- Programmers writing any programming code needed for the working solution.
- Using software tools to produce the working version.
producing working system to user requirements.
Testing the Solution
Most ICT projects involve lots of different people working on a different aspects of the system.
Testing will involve:
- Test at very detailed levels.
- Testing at a higher level.
- Testing the system with real life data.
Different Type of Tests
Functional Testing - Checks system meets business requirements.
System Testing - Is tested to see the whole system works with hardware , users and environment.
Operational Testing – Is performed by end user on software which is being used in its normal operating environmental.
User Testing – Allows the team of users to test the software or system.
Installation and Conversion
This is the stage where the completed and fully tested system is installed on operational equipment for real life use.
Implementation will involve:
- Installing hardware.
- Installing software.
- Conversion if previous data.
- Training of all users.
- Production of documentation and training guides to hep people understand the system.
Review and Maintenance
After installation and conversion stage as it is only then that users will find problems and shortcomings.
Review will involve:
- Checking that user requirements are still meet.
- Assessment of how happy the user is of the new system.
- Setting up a system review to make sure that user requirements is been meet.
- Setting a help desk facility to help others who have problems.
Maintenance will involve:
- Altercations in the system , adding extra functions.
- Any systems crashes to be investigated to find out the reasons for their occurrence.
Reasons why systematic formal methods are needed.
After the analysis is completed the developer needs to draw up a specification of what the new system will require this information will be attained from the manager, then the use of the systems development life cycle would be implemented as the use of formal methods produce better systems.
Project management
Project manager has overall responsibility for the development of the project, they are in charge of the development team. The project manager has tools and techniques to ensure success of the project , firstly a a project plan that contains a budget, the project will only be considered a success if it matches all user requirements, completed on time and within budget.
Success of project dependent on:
Clear Time scales – Time is allocated to small tasks to build up whole time-scale.
Milestones – Where tasks are set to finish on certain dates.
Agreed Deliverables – deliverables are small task that together build up the project , they are agreements which state when they are to be completed and who who are are to complete what then a meeting is held were deliverables are signed off.
Approval to Proceed - In order to proceed with a project a feasibility study that looks at cost and benefits will need to be presented which is a formal document outlining the results and conclusions of the study.
The steps involved in project management:
-Creation of the specification of the project.
- Context of the new systematic interface needed
- Time scales
- Resources
-Breaking down work
-Allocating Tasks.
-Estimating time to complete whole project .
-Regularly checking project and establishing controls.
-Planning for errors.
Linear Method
Waterfall Method – Is where one stage is perfected before you move onto another stage, so everything is done separately.
- Too rigid and hard too achieve in practise.
- Method assumes that no problems will be found later on or something may need to be changed after finding something out in a later stage.
- In some projects will want to see a rough working of a working version in order to make comments or adjustments.
- Offers simple, disciplined approach to developing system.
- Each task is completed fully so problems are dealt with at the time, so no need to go back.
- Bugs found early in software so costs are low to correct than if it was later into the development.
Iterative Methodologies
This is when the project is broken into different stages and undergoes a cyclic development process., this is when each stage is evaluated, until it is improved to meet developer and user requirements, this is then taken into account when completing other stages.
- Each time a step is completed the project improves as it highlights the value learning.
- It allows user involvement resulting in better solution.
- User involvement causes problems with their day to day work.
- Increased user involvement may increase features which will effect costs and timing.
Linear method is appropriate when:
- Where the project is large.
- Pressure doesn’t exist.
- Has clear objectives and solutions.
- Inexperienced.
Iterative method is appropriate:
- Project is based online.
- Requirements are made unclear.
- Experienced team.
- Pressure is on the team.
