Software Processes and Change Management

<p>The system meets its specification and user needs (B)</p> Signup and view all the answers

<p>It outlines how each system component operates (A)</p> Signup and view all the answers

<p>Incremental development (A)</p> Signup and view all the answers

<p>To define requirements in detail (A)</p> Signup and view all the answers

<p>Models represent processes abstractly (D)</p> Signup and view all the answers

<p>System structure may degrade as new increments are added. (A)</p> Signup and view all the answers

<p>A linear, sequential approach to software development. (A)</p> Signup and view all the answers

<p>An assessment of technical and financial feasibility. (A)</p> Signup and view all the answers

<p>It speeds up the development process by utilizing existing components. (A)</p> Signup and view all the answers

<p>Waterfall model. (D)</p> Signup and view all the answers

<p>Increased difficulty in applying future changes. (D)</p> Signup and view all the answers

<p>Web services developed according to service standards. (A)</p> Signup and view all the answers

<p>Making systematic modifications post-deployment. (D)</p> Signup and view all the answers

<p>Activities are planned in advance with measurable progress. (D)</p> Signup and view all the answers

<p>Financial forecasts relating to the software. (C)</p> Signup and view all the answers

<p>Waterfall model (C)</p> Signup and view all the answers

<p>Interleaving of specification, development, and validation activities. (D)</p> Signup and view all the answers

<p>They incorporate customer feedback in a faster, ongoing manner. (C)</p> Signup and view all the answers

<p>They incorporate elements from various process models. (D)</p> Signup and view all the answers

<p>Roles (A)</p> Signup and view all the answers

<p>Most practical processes include elements of both. (A)</p> Signup and view all the answers

<p>Functional requirements are emphasized over non-functional requirements. (C)</p> Signup and view all the answers

<p>Users may resist using an incomplete system. (B)</p> Signup and view all the answers

<p>Risk management considerations. (C)</p> Signup and view all the answers

<p>They are discarded after the required information is gathered. (C)</p> Signup and view all the answers

<p>Deploying parts of the system for user feedback before the entire system is completed. (C)</p> Signup and view all the answers

<p>Existing users may prefer a completely new system rather than using increments. (D)</p> Signup and view all the answers

<p>Emphasizes iterative development and incremental delivery. (A)</p> Signup and view all the answers

<p>Exploring areas of the product that are poorly understood. (A)</p> Signup and view all the answers

<p>To meet new requirements and remain useful (B)</p> Signup and view all the answers

<p>Rework for requirement re-analysis (D)</p> Signup and view all the answers

<p>System prototyping and incremental delivery (D)</p> Signup and view all the answers

<p>By anticipating potential changes to reduce rework (C)</p> Signup and view all the answers

<p>Adapting to changes at a low-cost, often through incremental development (A)</p> Signup and view all the answers

<p>A phase of a software process (C)</p> Signup and view all the answers

<p>By combining change avoidance with change tolerance (D)</p> Signup and view all the answers

<p>It separates activities from phases (B)</p> Signup and view all the answers

<p>In-phase iteration (D)</p> Signup and view all the answers

<p>It emphasized an iterative and risk-driven development methodology (C)</p> Signup and view all the answers

<p>Incorporating activities to cope with change (B)</p> Signup and view all the answers

<p>Implementation (C)</p> Signup and view all the answers

<p>Project risks are assessed and resolved continuously (B)</p> Signup and view all the answers

Understanding what stakeholders need from a system.

Detailed description of system requirements.

Ensuring requirements are correct and meet needs.

Transforming requirements into a working system.

Building the software based on the design.

Checking if the system meets its design and user needs.

Activities involved in producing a software system.

Adapting a software system over time.

Different ways of organizing tasks to build software, like Waterfall or Agile.

Software processes where all steps are planned ahead of time.

Software processes where planning is flexible, allowing changes during development.

A linear software development process that progresses through distinct phases.

Software development approaches where features/components are built and added incrementally.

Software development where existing components are reused to build a new system.

Specific tasks within a software development process (like designing or testing).

Detailed descriptions of how software is developed, including tasks, ordering, and outcomes.

Adapting existing software to meet changing requirements.

Software projects always need adjustments due to business or tech shifts.

The price of changing software, including rework and new additions.

Methods to anticipate changes and reduce rework efforts.

A software development approach, releasing/building small parts of the project over time.

Software development phases in a sequential order.

Software development in small, manageable parts.

Using existing software components to build new systems.

Web services, object packages, or pre-built systems.

Steps involved in creating, testing, and maintaining software. They are: 'Specification', 'Development', 'Validation' and 'Evolution'

Describing user needs and requirements for a software system.

Sequential phases make changes difficult, not suitable for complex projects.

Changes are challenging, can lead to system degradation over time.

Prototyping helps understand and clarify requirements, especially in areas unclear to stakeholders.

Creating a working model to test and refine features, focusing on what's unclear to stakeholders.

Prototypes discarded after development, used to gain understanding but not part of the final system.

Software is delivered in functional parts called increments, tested and evaluated by users at each step.

Incremental development allows for early feedback, easier adaptation to changing requirements, and reduced risk.

Difficulties arise when delivering increments in software replacements, as full functionality is unavailable early on, reducing user engagement.

A risk-driven software development process model that addresses risk factors at each iteration of the development spiral.

Prototyping clarifies unclear user needs and allows for adjustment of the development process along the way.

A software development process that uses iterative loops with risk assessment in each step.

Identifying, analyzing, and mitigating potential problems in a software project.

Developing software in small steps, repeating phases to improve it with fresh information.

A structured process model for software development.

Inception, elaboration, construction, transition.

Iterative steps within each phase of a process.

Using iterative steps across different phases of the process.

The ability of a process to manage and accommodate changes in requirements and risks.