System did not meet user requirements/system specification
Feasibility study
An assessment of the practicality of a proposed plan/method
Factors to consider in a feasibility study
Technical - Does technology exist within the organisation?
Legal - Laws to consider
Social - How will current staff be affected?
Economic - How much will the system cost?
Schedule - How long will the software system take to implement?
Benefits of a new system
Greater efficiency
Reduced costs
Standardised way of working
Increased end-user satisfaction
Main factors affecting systems
Time
Cost
User needs
Time
How long will the system take to implement, timing details are essential to arrange training
Cost
A cost estimate must be calculated to determine how much the new system will actually cost. It helps the company determine a budget.
User needs
Does the system meet all user requirements? Will end users need training?
User interface
Allows human users to interact with the computer system and its packages
Software processes
An activity carried out by a computer system. Raw data is processed to become information. Results from one process can be passed onto the next.
Data
Raw facts and figures used in the software processes
Batch processing
Data/Documents are bundled together into a batch and are processed together, overnight. All documents undergo the same level of processing. It is an automatic process and requires no human intervention.
Interactive processing
All transactions are processed immediately. Each transaction directly impacts the next. Each transaction must be fully completed for the next one to begin. Requires a computer system.
Online processing
One transaction takes place at a time, once it is accepted, the database will update. The User Interface must be clear and easy to use. Validation ensures data is correct.
System development life cycle
1. Draw up the system specification
2. Draw up test criteria
3. Conduct a feasibility study
4. Analyse data processing requirements
Responsibilities of a system analyst
Manage and schedule all tasks
Oversee development
Control the budget
Identify risks and report back to the client
Respond to risks
Resources the project manager is responsible for
Hardware
Software
Personnel
Responsibilities of a programmer
1. Write source code
2. Create a test plan and test program code
3. Debug if errors are found
4. Produce technical documentation
Risks in a software development project
Key team member may be unavailable
Task may take too long, causing sub-tasks to begin late, possibly exceeding budget