Term
|
Definition
The basic concept underlying the democratic programming team. Where every programmer must encourage the other programmers in the team to find faults in his or her code.
Note: 10 egoless programmers constitutes a democratic team |
|
|
Term
|
Definition
| a succession of small, almost trivial, additions to the requirements. |
|
|
Term
|
Definition
| New paradigms characterized by considerably less emphasis on analysis and design than in almost all other life-cycle models and with implementation starting much earlier in the life cycle, because working software is considered more important than detailed documentation. |
|
|
Term
| Software Project Management Plan |
|
Definition
| The plan drawn up after the analysis phase (aka specification phase) describing the proposed software developement in full detail. |
|
|
Term
| Proof of concept prototype |
|
Definition
an engineering prototype, a scale model constructed to test the feasibility of construction.
Note: not to be confused with a raid prototype. A proof of concept prototype is not built for requirements validation. |
|
|
Term
|
Definition
| The final aspect of integration testing. The sofware is delivered to the customer who test it on actual hardware. |
|
|
Term
|
Definition
| a fault inadvertantly introduced into one part of a product as a consequence of making an apparently unrealted change to another part of the product. |
|
|
Term
|
Definition
| a quality of software that can be extended continually (and, if neccesary easily changed) to incorporate the next increment without falling apart. |
|
|
Term
|
Definition
- (actual meaning) the science of methods
- (informal usage) a way of developing a software product. |
|
|
Term
|
Definition
- an implementation of an operation
- the implementation of the operations
of an object |
|
|
Term
|
Definition
| Upon completion of product testing. The first version is supplied to select future clients for testing on site. |
|
|
Term
|
Definition
| consist of the removal of residual faults while leaving the specifications unchanged. |
|
|
Term
|
Definition
a lack of overall design step before the various builds are constructed. The design is modified while the product is being built.
a feature of extreme programming |
|
|
Term
|
Definition
| a component of a software product, such as a specification document, a code module, or a manual. |
|
|
Term
|
Definition
| The corrected alpha release is the beta release. close to the final release |
|
|
Term
|
Definition
| changes made in response to changes in the enviroment in which the product operates, such as new hardware/operating systems or new government regulations. |
|
|
Term
|
Definition
| a problem where while the software is being developed, the requirements change. |
|
|
Term
|
Definition
| Testing done by client after the developers are satisfied that the product functions properly. |
|
|
Term
|
Definition
| Key areas or topics an organization should address to advance to the next SEI maturaty level. |
|
|
Term
|
Definition
| Milestones are date in which the client will get the deliverables of a project. |
|
|
Term
|
Definition
| After a significant change to a project has been made, the project must be retested against previous test cases to ensure the functionality of the rest of the project was not comprimised. |
|
|
Term
|
Definition
Unified modeling language
A tool used to represent the target software.
A picture is worth a thousand words. |
|
|
Term
|
Definition
term used for the software crisis where in software quality is generally unacceptably low and that deadlines and budgets are not being met.
Dubbed depression because of it long duration and grim prognosis. |
|
|
Term
|
Definition
a discipline whose aim is the production of fault-free software, delivered on time and within budget, that satisfies the clients needs.
addendum - the software should be easy to modify |
|
|
