Term
|
Definition
| a series of steps involving activities, constraints, and resources that produce an intended output of some kind |
|
|
Term
|
Definition
| process that involves the building of some product |
|
|
Term
|
Definition
| describes the life of a software product from its conception to its implementation, delivery, use, and maintenance |
|
|
Term
|
Definition
| the way software should progress |
|
|
Term
|
Definition
| the way software development is done in actuality |
|
|
Term
|
Definition
| stages are depicted as cascading from one to another |
|
|
Term
|
Definition
| partially developed product that enables customers and developers to examine some aspect of the proposed system and decide if it is suitable or appropriate for the finished product |
|
|
Term
|
Definition
| ensures that the system has implemented all of the requirements, so that each system functions can be traced back to a particular requirement in the specification |
|
|
Term
|
Definition
| ensures that each function works correctly |
|
|
Term
|
Definition
| a variation of the waterfall model that demonstrates how the testing activities are related to analysis and design |
|
|
Term
| Operational specification model |
|
Definition
| the system requirements are evaluated or executed in such a way that demonstrates the behavior of the system |
|
|
Term
|
Definition
| applies a series of transformations to change a specification into a deliverable system |
|
|
Term
|
Definition
| time between the required documents were written and the time the system was delivered |
|
|
Term
| Operational (production) system |
|
Definition
| one currently being used by the customer and user |
|
|
Term
|
Definition
| the next version being prepared to replace the current production system |
|
|
Term
|
Definition
| the system as specified in the requirements documents is partitioned into subsystems by functionality |
|
|
Term
|
Definition
| delivers a full system at the very beginning and then changes the functionality of each subsystem with each new release |
|
|
Term
|
Definition
| is a set of techniques for leveraging the creativity of developers and minimizing the amount of administrative overhead |
|
|
Term
|
Definition
| a collection of approaches based on the notion that every project needs a different set of policies, conventions, and methodologies |
|
|
Term
|
Definition
| uses iterative development where each 30-day iteration is called a sprint to implement the product’s backlog of priorities requirements |
|
|
Term
| Adaptive software development |
|
Definition
|
|
Term
|
Definition
| involves the continual interchange between customers and developers |
|
|
Term
|
Definition
| encourages developers to select the simples design or implementation to address the needs of their customers |
|
|
Term
|
Definition
| described by XP creators as commitment to delivering functionality early and often |
|
|
Term
|
Definition
| loops are built into the various activities during the development process |
|
|
Term
|
Definition
| planners generate a map of each release, documenting what the release includes and when it will be delivered |
|
|
Term
|
Definition
| system is designed so that functionality can be delivered as soon as possible |
|
|
Term
|
Definition
| development team agrees on a common vision of how the system will operate |
|
|
Term
|
Definition
| design is kept simple by addressing only current needs |
|
|
Term
|
Definition
| to ensure that the customer’s needs are the driving force behind development, test cases first, as a way of forcing customers to specify requirements that can be tested and verified once the software is built |
|
|
Term
|
Definition
| refers to revisiting the requirements of the design, reformulating them to match new and existing needs |
|
|
Term
|
Definition
| attempts to address the artistic side of software development, acknowledging that the apprentice-master metaphor can be useful in teaching novice software developers how develop the instincts of masters |
|
|
Term
|
Definition
| any developers can make changes to any part of the system as it being developed |
|
|
Term
|
Definition
| delivering functionality quickly means that working systems can be promised to the customer daily and sometimes even hourly |
|
|
Term
|
Definition
| emphasis on people includes acknowledging that fatigue can produce errors |
|
|
Term
|
Definition
| ideally, a customer should be present on-site, working with the developers to determine the requirements and providing feedback about how to test them |
|
|
Term
|
Definition
| standard support other practices such as testing and refactoring |
|
|
Term
|
Definition
| depicts the process, showing that the inputs are transferred to outputs |
|
|
Term
|
Definition
| enacts the process, so the user can see how intermediate and final products are transformed over time |
|
|
