Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
15 Cards in this Set
- Front
- Back
- 3rd side (hint)
|
Agile manifesto |
1. Individuals & interactions/processes and tools IPT 2. Working software/comprehensive documentation WCD 3. Customer collaboration/contract negotiation CCN 4. Responding to change/following a plan FAP |
Interpret woes customization rechap |
|
|
Agile Principle |
Civil idle press breach maincity |
|
|
|
Customer involvement |
Customers should be closely involved throughout the development process.
Their role is; -provide & prioritize new system requirements -to evaluate the iterations of the system |
Closely invoked |
|
|
Incremental delivery |
The software is developed in increments with the customer specifying the requirements to be included in each increment. |
Specify requirements |
|
|
People not process |
The skills of the development team should be recognized & exploited.
Team members should be left to develop their own ways of working without prescriptive processes. |
Recognized & exploited |
|
|
Embrace changes |
Expect the system requirements to change and so design the system to accommodate these changes. |
Accommodate changes |
|
|
Maintain simplicity |
Focus on simplicity in both the software being developed & in the development process.
Wherever possible, actively work to eliminate complexity from the system. |
Focus on simplicity |
|
|
Maintain simplicity |
Focus on simplicity in both the software being developed & in the development process.
Wherever possible, actively work to eliminate complexity from the system. |
Focus on simplicity |
|
|
XP Principle |
Implement smaller seed for airing |
|
|
|
Incremental planning |
Requirements are recorded on Story Cards & the Stories to be included in a release are determined by the time available & their relative priority.
The developers break these Stories into development ‘Tasks’. |
Story cards |
|
|
Small release |
The minimal useful set of functionality that provides business value is developed first.
Releases of the system are frequent & incrementally add functionality to the first release. |
Minimal useful set |
|
|
Simple design |
Enough design is carried out to meet the current requirements and no more. |
Enough design |
|
|
Pair programming |
Developers work in pairs, checking each other’s work & providing the support to always do a good job. |
Provide support |
|
|
Waterfall model |
1. Requirements definition RED 2. System & software design SSD 3. Implementation & unit testing UNIT 4. Integration & system setting ISS 5. Operation & maintenance OP
1-5 fall the stairs 5-1 touch one by one and return
|
red ssd unit is op 1to5 fall 5to1 touch |
|
|
Evolutionary development model |
1. Define system requirements DRS 2. Assess existing system ASEX 3. Propose system changes PROS 4. Modify systems MOD 5. New system NEWT 6. Existing systems EXIST
1-4 go thru 4 go to 1 4 go to 5 5 go to 2 6 go to 2 |
DRS ASEX PROS MOD NEWT EXIST |
