Software development/section 1

A several step process to deliver a product to a client

Analysis, design, implementation, testing, documentation, evaluation A Dance In The Dark Everyday

The beginning stage of the design process, the developers and client will define the purpose and requirements of the software

Purpose, functional requirements, assumptions

A paragraph that outlines what the project is for, decided upon by the devcveloper and the client

The program is abstracted into inputs, processes and outputs, these are defined by the developer

Anything that has not been made clear by the client Can include: IT competency, software compatibility etc.

The purpose and functional requirements are considered to create steps that are turned into code in implementation

Structure diagram, flow charts, pseudocode

A visual technique that shows the steps needed to solve a problem Different shapes represent different techniques

A visual design technique that shows the journey of a piece of software Show the process not steps needed (steps needed is structure diagram)

A written design technique not based on any language

Define and refine the main steps, variables are not declared, indentation to show loops and conditionals

To make sure a program runs as intended, you need to test various inputs to make sure they do what is expected

Any data you expect to work

Data at the upper or lower limits of the program, the program should still work as intended

Any data just outsice of the limits, should not be accepted

Syntax errors, logical errors

When the code cannot run because it is not written in the correct form

The code executes, but produces unexpected results Such as using AND instead of OR

A document that contains all analysis, design, implementation and testing

In this stage, the developer will compare the finished product with the analysis and other factors to evaluate whether the product meets expectation

Fitness for purpose, efficiency, robustness, readability