Software Engineering: SDLC, Agile, CMMI, CI/CD, Quality & Testing, and UML Design

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/43

flashcard set

Earn XP

Description and Tags

Comprehensive vocabulary flashcards covering the Software Development Lifecycle, CMMI maturity levels, CI/CD and DevOps practices, software testing methods, and UML architectural diagrams.

44 Terms

1
New cards

Adaptive Maintenance

Software maintenance performed to update the software so that it works in new or changing operating environments.

2
New cards

Corrective Maintenance

Software maintenance focused on fixing bugs and defects as they are discovered.

3
New cards

Perfective Maintenance

Software maintenance carried out to enhance existing functionality to meet changing user needs.

4
New cards

Waterfall Model

A linear, sequential software process model where progress flows steadily downwards through distinct phases that must each be completed before the next begins.

5
New cards

Prototyping Model

A process model starting with initial requirement gathering and a quick design, after which a prototype is iteratively built and refined based on user feedback.

6
New cards

Spiral Model

A software development model combining elements of prototyping and the Waterfall model with extensive risk analysis, suitable for large, expensive, and complicated projects.

7
New cards

Product Owner

The Scrum role responsible for managing the product backlog and ensuring the value of the work performed by the development team.

8
New cards

Scrum Master

The Scrum role responsible for ensuring that the development team adheres to Agile practices and principles.

9
New cards

Work in Progress (WIP) Limits

A Kanban practice of restricting the maximum number of active tasks permitted in a given workflow stage to prevent bottlenecks and encourage completion.

10
New cards

Commitment Point (Kanban)

The specific point in the Kanban workflow when a work item is selected and moved onto the board.

11
New cards

Delivery Point (Kanban)

The end of the Kanban workflow representing the point at which products or completed items are delivered.

12
New cards

Capability Maturity Model Integration (CMMI)

A framework of best practices designed to provide organizations with essential process elements to improve performance and key capabilities in service, product, and software development.

13
New cards

Ad Hoc Processes

Processes characterized by a lack of formal enforcement, high dependency on individual practitioner skills, limited project visibility, and reactive management.

14
New cards

Institutionalized Processes

Processes that are well-established, embedded within organizational culture, actively nurtured by management, and remain effective beyond the tenure of their creators.

15
New cards

Initial (CMMI Level 1)

The CMMI maturity level in which organizational processes are unpredictable, poorly controlled, and reactive.

16
New cards

Managed (CMMI Level 2)

The CMMI maturity level where processes are characterized at the project level and often remain reactive.

17
New cards

Defined (CMMI Level 3)

The CMMI maturity level where processes are standardized and characterized for the entire organization and are proactive.

18
New cards

Quantitatively Managed (CMMI Level 4)

The CMMI maturity level where processes are quantitatively measured and controlled.

19
New cards

Optimizing (CMMI Level 5)

The highest CMMI maturity level, focusing on continuous process improvement through innovative technologies and optimization techniques.

20
New cards

Casual Analysis and Resolution

A CMMI Support process area dedicated to identifying and preventing the root causes of defects and problems.

21
New cards

Configuration Management (CMMI)

A CMMI Support process area focused on managing product integrity through detailed configuration protocols.

22
New cards

Continuous Integration (CI)

A software development practice where developers frequently integrate code changes into a shared central repository, triggering automated builds and testing.

23
New cards

Continuous Delivery (CD)

An extension of Continuous Integration ensuring that software is automatically tested and verified such that it can be released to production at any time.

24
New cards

Continuous Deployment

An extension of Continuous Delivery where every mainline commit that passes the automated test suite is deployed directly and automatically to production.

25
New cards

Infrastructure as Code (IaC)

The practice of managing and provisioning computing infrastructure (machines, devices, operating systems) through code rather than manual processes.

26
New cards

DevOps

A software engineering culture and practice aimed at unifying software development (Dev) and operations (Ops) to shorten the development lifecycle and deliver features frequently.

27
New cards

Verification

The quality process evaluating whether a software system conforms to its specified technical requirements ("building the product right").

28
New cards

Validation

The quality process ensuring that a software system meets the actual operational needs and expectations of its users ("building the right product").

29
New cards

Static Verification

Verification that examines non-executable artifacts of an application, such as documents and source code, using techniques like code reviews and inspections.

30
New cards

Dynamic Verification

Verification involving the execution of the application code under various conditions to observe runtime behaviors (e.g., unit and system testing).

31
New cards

Equivalence Partitioning

A black-box testing technique that divides the program's input domain into partitions of data assumed to behave identically, testing a single representative value from each set.

32
New cards

Boundary Value Analysis

A black-box testing strategy that complements equivalence partitioning by focusing test cases on values at the extreme edges or boundaries of input partitions.

33
New cards

Statement Coverage

A white-box testing metric measuring whether every individual code statement has been executed at least once.

34
New cards

Decision Coverage

A white-box testing metric requiring that every statement is executed and every decision branch takes on all possible outcomes at least once.

35
New cards

Path Coverage

A white-box testing metric requiring that each statement is executed and all possible combinations of condition outcomes in each decision occur at least once.

36
New cards

Test-Driven Development (TDD)

A development practice where automated tests are written before functional code; development proceeds in a cycle of failing test, minimal passing code, and refactoring.

37
New cards

4+1 View Model

An architectural model framework designed to capture multiple stakeholder perspectives using five concurrent views: Logical, Process, Implementation, Deployment, and Use Case Views.

38
New cards

Aggregation (UML)

A flexible whole-part class relationship in UML where parts can exist independently of the whole object (e.g., books in a library).

39
New cards

Composition (UML)

A strong form of aggregation implying ownership, where the lifecycle of the parts depends on the whole; if the whole is destroyed, the parts are destroyed as well.

40
New cards

Sequence Diagram

A UML interaction diagram that models the chronological order of message flow between objects over time for specific use cases.

41
New cards

Communication Diagram

A UML diagram that emphasizes structural organization and links between objects within a network of message exchanges.

42
New cards

Boundary Classes (B-C-E)

Classes in Boundary-Control-Entity modeling that manage the system's interactions with external entities, handling input/output interface operations.

43
New cards

Control Classes (B-C-E)

Classes in Boundary-Control-Entity modeling that encapsulate operational application logic and mediate workflow between boundary classes and entity classes.

44
New cards

Entity Classes (B-C-E)

Classes in Boundary-Control-Entity modeling that represent core business objects, containing persistent data and behaviors typically mapped to database tables.