states a condition that any valid object of the class should satisfy at all times from its creation onwards.
invariant
1 of 12
Reusable part of architecture and code
framework
2 of 12
When partitioning a system into individual classes you want the coupling between them to be loose so you have the flexibility to vary them independently.
Observer pattern
3 of 12
a development phase, no longer than a month, that has as a deliverable a useable working increment
the sprint
4 of 12
lasts no more than eight hours
sprint planning meeting
5 of 12
a daily meeting, no longer than 15 minutes, looking at what has been done and planning the work for the next 24 hours.
the daily scrum
6 of 12
geared to better communication and collaboration among developers.
agile practices
7 of 12
traditional, more prescriptive approaches to software development
plan driven development
8 of 12
no code is written without first devising and writing an automated test case for each code increment.
test driven development
9 of 12
Splits user interface interaction into three distinct roles: the model of the domain, the view representing that domain, and the controller of changes to the domain.
model view controller pattern
10 of 12
a more detailed description of the functionality to be provided.’
software requirement
11 of 12
A particular way of viewing a complex problem to arrive at some useful decomposition of that problem.
abstraction
12 of 12
Other cards in this set
Card 2
Front
Reusable part of architecture and code
Back
framework
Card 3
Front
When partitioning a system into individual classes you want the coupling between them to be loose so you have the flexibility to vary them independently.
Back
Card 4
Front
a development phase, no longer than a month, that has as a deliverable a useable working increment
Comments
No comments have yet been made