Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
SOFT ENG
Chapter 3
| Question | Answer |
|---|---|
| Effective (rapid and adaptive) response to change | Agility |
| Effective communication among all stakeholders | Agility |
| Is driven by customer descriptions of what is required (scenarios) | Agile Process |
| the art of maximizing the amount of work not done – is essential. | Simplicity |
| is the primary measure of progress | Working software |
| the process molds to the needs of the people and team, not the other way around | Human Factors |
| The most widely used agile process, originally proposed by Kent Beck | Extreme Programming (XP) |
| is used to help define subsequent delivery dates for other increments | project velocity |
| Follows the KIS principle | Extreme Programming (XP) |
| For difficult design problems, suggests the creation of “___________”—a design prototype | spike solutions |
| Encourages “refactoring”—an iterative refinement of the internal program design | Extreme Programming (XP) |
| Encourages “____________”—an iterative refinement of the internal program design | refactoring |
| Recommends the construction of a unit test for a store before coding commences. Encourages “pair programming” | XP Coding |
| All unit tests are executed daily | XP Testing |
| are defined by the customer and excuted to assess customer visible functionality | Acceptance tests |
| Originally proposed by Jim Highsmith. Uses “time-boxing” (See Chapter 24). Explicit consideration of risks. Emphasizes collaboration for requirements gathering. Emphasizes “learning” throughout the process | Adaptive Software Development |
| Promoted by the DSDM Consortium (www.dsdm.org) | Dynamic Systems Development Method |
| Development work is partitioned into “packets”. Testing and documentation are on-going as the product is constructed | Scrum |
| Development work is partitioned into “________”. | packets |
| is a self-organizing interdisciplinary team consisting of a product owner, a Scrum master, and a small (three to six people) development team. | The Scrum team |
| is a prioritized list of product requirements or features that provide business value for the customer | product backlog |
| is the subset of product backlog items selected by the product team to be completed as the code increment during the current active sprint. | sprint backlog |
| is a lean methodology that describes methods for improving any process or workflow. | Kanban method |
| is focused on change management and service delivery. | Kanban method |
| was created by Patrick DeBois [Kim16a] to combine Development and Operations. | DevOps |
| Software deliverables are broken down and developed in multiple sprints with the increments delivered to the quality assurance14 members of the development team for testing | Continuous developme |
| Automated testing tools15 are used to help team members test multiple code increments at the same time to ensure they are free of defects prior to integration. | Continuous testing. |
| The code pieces with new functionality are added to the existing code and to the run-time environment and then checked to ensure there are no errors after deployment. | Continuous integration |
| At this stage the integrated code is deployed (installed) to the production environment, which might include multiple sites globally that need to be prepared to receive the new functionality. | Continuous deployment |
| Operations staff who are members of the development team help to improve software quality by monitoring its performance in the production environment and proactively looking for possible problems before users find them. | Continuous monitoring |
| Proposed by Cockburn and Highsmith. _________—distinguishing features. Actually a family of process models that allow “maneuverability” based on problem characteristics | Crystal |
| a feature “is a client-valued function that can be implemented in two weeks or less.” | features |
| Originally proposed by Scott Ambler | Agile Modeling |
Created by:
cessy_comscie
Popular Computers sets