27 terms

Software Development Process

A careful study that looks closely at a thing's parts or elements.
The act of working out the form of something (as by making a sketch or outline or plan).
Putting plans into operation.
The act of subjecting a program to experimental test in order to determine how well something works.
Program listings or technical manuals describing the operation and use of programs.
The act of judging the value or worth of; the result of evaluating; a judgment or appraisal.
The upkeep of industrial facilities and equipment and/or software.
The person who pays for the program to be made.
Systems Analyst
A business professional who uses analysis and design techniques to solve business problems using information technology.
Project Manager
A person responsible for coordinating the activities of several departments on a full-time basis for the completion of a specific project.
The person who designs and writes and tests computer programs.
Independent Test Group
Testing of software by a group of people outwith the development team.
A loosely structured method to describe the logic of a program or outline a system. It uses basic programming techniques but ignores issues of syntax and relies on verbal descriptions.
Graphical Design Notation
A visual representation of the program design such as a Flowchart or Structure Diagram.
Structure Diagram
A diagram that represents the working relationships between the parts of a system or program.
Top-down Design
Also called 'stepwise refinement', it is a software development technique that imposes a hierarchial structure on the design of the program. It starts out by defining the solution at the highest level of functionality and breaking it down further ad further into small routines that can be easily documented and coded.
Stepwise Refinement
The division of major tasks in a program into smaller tasks.
Systematic Testing
Design or sequence tests to rule out competing explanations.
Comprehensive Testing
Testing programs as thoroughly as possible.
Program listings or technical manuals describing the operation and use of programs.
A term used to describe the ability of a program to resist crashing due to incorrect input or incorrect intermediate results.
When a test yields consistent results, as assessed by the consistency of scores on two halves of the test, on alternate forms of the test, or on retesting.
Using resources in such a way as to maximize the production of a program.
Category of requirements that focus on maintaining a product's usefulness over its productive life, and the costs associated with it.
Corrective Maintenance
Changes made to a system to repair flaws in its design, coding or implementation.
Adaptive Maintenance
Making changes to increase system functionality to meet new business requirements.
Perfective Maintenance
Making changes to enhance the system and improve such things as processing performance and usability.