Software Processes and Agile Development Flashcards

A set of vocabulary flashcards covering software process models, the waterfall model, prototyping, agile methodologies, and the Scrum framework based on lecture notes.

Software process

A structured set of activities required to develop a software system.

Specification

The software process activity of defining what the system should do.

Design and implementation

The software process activity of defining the organization of the system and implementing the system.

Validation

The software process activity of checking that the system does what the customer wants.

Evolution

The software process activity of changing the system in response to changing customer needs.

Software process model

An abstract representation of a process that presents a description of a process from some particular perspective.

Plan-driven processes

Processes where all the process activities are planned in advance and progress is measured against this plan; also known as the waterfall model.

Agile processes

Processes where planning is incremental and it is easier to change the process to reflect changing customer requirements.

Waterfall model

A model characterized by the inflexible partitioning of the project into distinct stages, requiring each phase to be complete before moving onto the next.

Requirements analysis and definition

The first phase of the waterfall model focused on establishing system requirements.

Operation and maintenance

The final phase of the waterfall model where the system is in practical use and evolving.

Software prototype

An initial version of a system used to demonstrate concepts and try out design options.

Throw-away prototypes

Prototypes discarded after development because they lack documentation, have degraded structures, and are not a good basis for a production system.

Agile methods

Methods based on an iterative approach that focus on the code rather than the design to deliver working software quickly.

Agile Manifesto

A set of values prioritizing individuals and interactions, working software, customer collaboration, and responding to change.

Refactoring

The practice of looking for and making software improvements even when there is no immediate need, to improve understandability and reduce documentation.

Scrum

A general agile method focused on managing iterative development through initial planning, sprint cycles, and project closure.

Sprint cycle

Fixed length development periods, normally $2-4$ weeks, corresponding to the development of a release of the system.

Product backlog

The list of work to be done on a project, used as the starting point for sprint planning.

Scrum master

A facilitator who protects the development team from external distractions, tracks the backlog, and arranges daily meetings.