In software design process the software structure is translated into an executable program

The customer should be available part time for the use of the XP team and is responsible for bringing system requirements to the team for implementation

The phases of sprint cycle are: Select – Develop – Review – Assess

Scrum Velocity is an estimate of how much product backlog effort that a team can cover in a single sprint

In plan-driven processes, planning is incremental and it is easier to change the process to reflect changing customer requirements

Process improvement cycle consists of measurement, design and change

If the development team is distributed or if part of the development is being outsourced, then you may need Agile development methods

Agile method approach is used If the development team is distributed or if part of the development is being outsourced

In Scrum, the starting point for planning is the product backlog, which is the list of work to be done on the project

In XP, the customer chooses the stories for inclusion in the next release based on their size

In SCRUM, the initial phase is an outline planning phase where you establish the general objectives for the project and design the software architecture

Consistent requirements are requirements that may be interpreted in different ways by developers and users

Unambiguous requirements are those that have no conflicts or contradictions in their descriptions

Requirements documentation is the process of writing down the user and system requirements in a requirements document

In writing requirements use “should” for mandatory requirements, and “shall” for desirable requirements

Requirements engineering is a generic process that does not vary from one software project to another

Use-case actors are always people, never system devices

Design patterns are not applicable to the design of object-oriented software?

Software designs are refactored to allow the creation of software that is easier to integrate, easier to test, and easier to maintain

Software dependability includes responsiveness, processing time, memory utilization, etc.

Prototyping focus on non-functional rather than functional requirements such as reliability and security

User Stories are structured forms of Scenarios

Requirements management is the process of managing changing requirements during the requirements engineering process and system development

A sequence diagram shows the sequence of interactions that take place during a particular use case

Waterfall model is mostly used for large systems engineering projects

The phases of sprint cycle are: Select – Develop – Assess – Review, respectively

The initial phase in SCRUM is an outline planning phase where you establish the general objectives for the project and design the software architecture

If the software system is subject to external regulation, then you will probably be required to use plan-driven method to produce detailed documentation

Agility is nothing more than the ability of a project team to respond rapidly to change

In agile software processes the highest priorities is to satisfy the customer through early and continuous delivery of valuable software

In agile development it is more important to build software that meets the customers' needs today than worry about features that might be needed in the future

In requirements validation the requirements model is reviewed to ensure its technical feasibility

Since modularity is an important design goal it is not possible to have too many modules in a proposed design

The architectural representations can be an enabler for communication among project stakeholders

Software processes can be constructed out of pre-existing software patterns to best meet the needs of a software projec

In agile development it is more important to build software that meets the customers' needs today than worry about features that might be needed in the future

A stakeholder is anyone who will purchase the completed software system under development

Since project estimates are not completely reliable, they can be ignored once a software development project begins

Outsourcing always provides a simple means of acquiring software at lower cost than onsite development of the same product

Design and architecture are often referred to as the “what" of the system and requirements as the “how".

Efficiency includes a range of characteristics including reliability, security and safety

In Plan-Driven processes it is easier to change the process to reflect changing customer requirements

Software specification is the process of establishing what services are required and the constraints on the system’s operation and development

Verification and validation (V & V) is intended to show that a system conforms to its specification and meets the requirements of the system customer