Introduction to Software Engineering and Software Process Models

These flashcards cover key definitions, models, methodologies, and principles related to software engineering.

Software Engineering

The systematic application of engineering principles to the development, operation, and maintenance of software systems.

Waterfall Model

A linear, sequential approach to software development with distinct phases such as requirements gathering, design, implementation, testing, and maintenance.

Agile Methodology

A flexible, iterative approach to software development emphasizing collaboration, customer feedback, and rapid delivery.

Modularity

The practice of breaking software into smaller, manageable parts to improve organization and maintenance.

Reusability

The practice of reusing existing components to save time and effort in software development.

Customer Collaboration

Engagement with customers throughout the development process to gather feedback and ensure the software meets their needs.

Dynamic Behavior of Software

Software executes tasks dynamically based on user inputs, configurations, and environmental factors.

Changeability in Software

Software's ability to be easily modified to meet new requirements or fix errors.

Concurrent Development Model

A software development approach where various activities such as communication, development, and testing happen in parallel.

Spiral Model

A risk-driven process model that combines elements of both the Waterfall model and Prototyping model, focusing on iterative development and risk analysis.

Quality Assurance

Activities intended to ensure that software development processes are consistent, reliable, and adhere to established standards.

Documentation-Driven

A characteristic of the Waterfall model where comprehensive documentation is created in each phase.

Feedback Loop

An iterative process in which customer feedback is integrated throughout software development to refine and improve the final product.

User-Centric Design

An approach that keeps user requirements and satisfaction in focus throughout the development process.

Software Crisis

A situation in the late 1960s when software projects frequently failed to meet deadlines, budgets, or quality standards.

Maintainability

The ease with which software can be understood, modified, and updated over time.

Cost and Time Efficiency

The goal of using resources effectively during software development to meet deadlines and budgets.