1.10 Principle of Programming

Problem definition, feasibility, analysis, design, build, testing, documentation, maintenance, evaluation

Stakeholders, users, programmers, project managers, systems analysts

Is the first step in a systems lifecycle, This is where the problem is identified, usually by a company commissioning it

Is the second step in a sytems lifecycle, This is where a someone looks to see if the project is possible, can it be completed in the given time, is the price right for the company

Is the third step in a systems lifecycle, this is where project managers will employ someone to find out from the users what they will be requiring in the program, this will be done by questionaries’

The programmers then take the ideas and questionaries’ and design the program to see if it is possible, with flow charts for example

This is where the programs take the Design and actually make it into a workable program

uses white box and black box testing procedures

Is made by the programmers so that other maintenance programmers can look up what different sections of the code actually do

Is carried out throughout the systems lifecycle, and at the begining of its life so that the program can be perfected

Finds out if the program completes its requirements, performance ratings, robustness, cost and usability

Big-Bang Phased Pilot Parallel