Untitled Quiz

Combining existing software components to create a new system. These components can be customized for the specific needs of the project.

A linear software development process where each phase is completed sequentially, starting with requirements analysis and ending with operation and maintenance. Changes are difficult to implement once a phase is completed.

The initial phase of the waterfall model, focusing on understanding the needs of the user and documenting them precisely. It's about defining the scope of the project.

This phase involves translating the defined requirements into a functional system design, including architecture, modules, and how they interact.

Software developers write code based on the design. This is the coding and testing stage, where errors and bugs are addressed.

All the software components are brought together and tested as a whole system. This phase ensures all parts work together correctly.

The final stage, where the system is launched and used. Regular maintenance is critical to address bugs, enhance features, and keep the system up-to-date.

A software development approach where the project is broken down into smaller, manageable increments. Each increment adds functionality, allowing for early feedback and flexibility.

Verification and validation (V&V) is a process to ensure a software system meets its specifications and user requirements.

Testing is crucial in V&V as it involves executing the system with specific test cases to check if it meets the requirements.

Software testing is divided into stages: component, system, and customer testing. Component testing checks individual parts, system testing verifies the whole system, and customer testing uses real data to ensure it meets user needs.

Testing phases in a plan-driven process often follow the V-model, where testing activities are linked to each stage of development, like requirements, design, and implementation.

Software needs to evolve as business requirements, technology, and platforms change. It adapts to new needs and improves over time.

System evolution involves modifying an existing software system to meet new requirements, fix bugs, or improve performance.

Change management is critical because changes in software projects are inevitable. It involves managing the impact of changes effectively.

Change costs include the rework needed to update the system, delays caused by changes, and the effort required to manage these changes.

A software process that includes activities to predict potential changes before significant rework is needed.

An early version of a system used to demonstrate ideas and test design choices.

A software process designed to accommodate changes with minimal cost.

A version of a system or part of it, built quickly to verify customer requirements and design feasibility.

Delivering working parts of the system to customers for feedback and experimentation.

Prototyping leads to improved usability, better meeting user needs, higher design quality, enhanced maintainability, and reduced development effort.

Prototypes help identify and address potential issues early in the development process, allowing for adjustments before significant rework is required.

A method of software development that involves building a working model of the system to test and refine design ideas. This model is usually not intended for production use.

A prototype built for early testing and feedback, but discarded after development and not used as the basis for the final product. It's used for exploring ideas and understanding requirements.

Prototype development can lead to systems that don't meet non-functional requirements (like reliability, security), are poorly documented, and may not be able to be improved to meet organizational quality standards.

This approach allows for early user feedback, flexibility in adapting requirements, and ensures each increment is thoroughly tested before integration.

Incremental development is about building in increments, while incremental delivery is about releasing those increments to users. It's about delivering functional parts of the system in each increment rather than waiting for the entire system to be completed.

Incremental delivery offers benefits like early customer value, prototype-driven requirement gathering, reduced project risk, and focused testing on high-priority features.

Challenges include defining common facilities for all increments, potential conflict with procurement models requiring complete specifications upfront, and the continuous evolution of requirements.

A structured approach to enhance software development processes, targeting increased quality, reduced costs, or faster development times.

A process improvement method focusing on refining project management and introducing good software engineering practices, measuring the adoption level of these practices within the organization.

A process improvement approach emphasizing iterative development, rapid delivery of functionality, and responsiveness to changing customer needs.

Agile methods prioritize rapid delivery, flexibility in responding to changing requirements, and close collaboration with customers.

The level of process maturity shows how effectively good technical and management practices are integrated into the organization's software development processes.

The activities involved in creating a software system. They define how development is organized and managed.

Abstract representations of the software processes, showing the steps and their order.

The process of gathering and documenting the needs of the users and stakeholders of a software system.

Checking if the software system meets its specifications and fulfills the users' real needs.

Making changes to an existing software system to adapt to new requirements or address issues.

A framework for assessing the maturity of an organization's software development processes, identifying levels of process control and improvement.

It defines five levels: Initial, Repeatable, Defined, Managed, and Optimizing, each representing increasing levels of process control and improvement.

Agile approaches focus on reducing process overheads and increasing flexibility, while maturity-based approaches emphasize better management and software engineering practices.