Software Engineering Fundamentals: SDLC, Requirement Engineering, PTM, WBS, and UML Modeling

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

1/38

flashcard set

Earn XP

Description and Tags

Vocabulary practice flashcards covering software engineering foundations, SDLC phases, requirement engineering techniques, project time management (PTM), work breakdown structures (WBS), and UML class and use case diagrams.

39 Terms

1
New cards
<p>Association (UML Class Diagram)</p>

Association (UML Class Diagram)

A general connection between classes indicating that they interact or are linked in the system, represented by a solid line without implying an inheritance or whole–part hierarchy.

2
New cards
<p>Aggregation</p>

Aggregation

A weak whole–part relationship between classes where the part can exist independently of the whole, represented by a hollow diamond placed at the whole (container) end.

3
New cards
<p>Composition</p>

Composition

A strong whole–part relationship between classes where the part's lifecycle is tied to and dependent on the whole, represented by a filled diamond placed at the whole end.

4
New cards
<p>Generalization</p>

Generalization

An "is-a" or inheritance relationship showing that one class is a specialized type of a parent class, drawn as a solid line with a hollow triangle pointing to the parent.

5
New cards
<p>Dependency (UML Class Diagram)</p>

Dependency (UML Class Diagram)

A relationship where one class uses another, often temporarily to perform a task, drawn as a dashed arrow pointing to the class being used.

6
New cards

Navigability

An association property, typically indicated with an arrow, showing which class can access or reference the other in the system model.

7
New cards

Class Diagram

A UML structural diagram that models the static view of a system by showing its classes, attributes, methods, and relationships.

8
New cards
<p>Class vs. Object</p>

Class vs. Object

A class is an abstract blueprint or general specification defining data and behaviors, whereas an object is one concrete, specific instance of that class.

9
New cards
<p>Class Compartments (UML)</p>

Class Compartments (UML)

The three standard horizontal divisions of a UML class box: the top compartment contains the class name, the middle lists attributes (data), and the bottom lists methods (operations).

10
New cards

Visibility Modifiers (UML)

Symbols preceding attributes or operations to indicate access level, where ++ denotes public access (accessible from outside) and −- denotes private access (used internally).

11
New cards
<p>Multiplicity</p>

Multiplicity

A numerical notation placed on association ends indicating how many instances of a class can link to one instance of the opposing class, such as 11 (exactly one), 0..∗0..* (zero or many), and 1..∗1..* (one or many).

12
New cards

Project Time Management (PTM)

The management process of analyzing, developing, and controlling a schedule and timeline for project completion, allocating resources, and establishing buffers for unexpected roadblocks.

13
New cards
<p>Triangle of Project Management</p>

Triangle of Project Management

A core project management framework illustrating the interrelated constraints of Cost, Time, and Scope, with Quality positioned at the center.

14
New cards

Time Buffer

A planned margin of reserve time built into a project schedule to absorb delays and critical roadblocks without failing delivery commitments.

15
New cards

Schedule Control

The ongoing management activity of comparing actual project progress against the baseline plan and adjusting activities or resources when variances occur.

16
New cards

Four Basic PTM Techniques

The four sequential techniques for managing project time: 1. Define the Activities, 2. Sequence the Activities, 3. Estimate Activity Resources, and 4. Develop & Control the Schedule.

17
New cards

Software Development Life Cycle (SDLC)

Defined by IEEE as a structured process for planning, creating, testing, and deploying an information system, providing a structured approach to reduce project risks.

18
New cards

SDLC Phases

The sequential stages of software creation: Requirement Analysis, Planning and Analysis, System Design, Implementation, Testing, Deployment, and Maintenance.

19
New cards

Software Maintenance Categories

The four post-deployment maintenance types: Corrective (bug fixing), Adaptive (adapting to environmental changes), Perfective (enhancements and optimizations), and Preventive (preventing future problems).

20
New cards
<p>Requirement Engineering</p>

Requirement Engineering

Defined by IEEE as the process of establishing the services required by the customer and identifying the constraints under which the system operates.

21
New cards

Functional vs. Non-Functional Requirements

Functional requirements define what the system should do, whereas non-functional requirements define how the system should behave, including quality, operational, and performance constraints.

22
New cards
<p>Joint Application Development (JAD)</p>

Joint Application Development (JAD)

A structured requirement elicitation workshop where clients, end users, developers, analysts, and a facilitator collaborate intensively together to resolve issues and agree on requirements rapidly.

23
New cards

Ethnographic Studies (Contextual Inquiry)

A requirement elicitation technique where analysts immerse themselves in the users' real work environment over days or weeks to uncover unspoken needs and hidden pain points.

24
New cards

Reverse Engineering Legacy Systems

An elicitation approach of deconstructing and analyzing older software systems (such as a 20-year-old20\text{-year-old} COBOL system) to extract existing functional requirements.

25
New cards

Storyboarding & Scenario-Based Elicitation

An elicitation method utilizing visual illustrations, user journeys, or scenario mockups to explore system behavior and engage non-technical stakeholders more effectively than text-heavy SRS documents.

26
New cards

Crowdsourcing Requirements

An elicitation method that gathers and prioritizes requirements, feature suggestions, and feedback by engaging a large online user base or community through polls and discussions.

27
New cards
<p>Testing Phase Levels</p>

Testing Phase Levels

The progressive verification stages used to find and fix defects: Unit testing, Integration testing, System testing, and Acceptance testing.

28
New cards

Software (Nature & Characteristics)

A set of programs, procedures, and associated documentation that is logical rather than physical, engineered rather than manufactured, and deteriorates rather than wears out.

29
New cards

Software Engineering (IEEE Standard 610.12-1990)

The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software; that is, the application of engineering to software, and the study of such approaches.

30
New cards

Software Crisis

The historical and operational problem characterized by the inability to develop correct, efficient, and maintainable software within budgeted time and cost estimates.

31
New cards
<p>The Complexity Gap</p>

The Complexity Gap

The widening divergence over time between the exponential growth of software complexity and engineers' ability to manage that complexity.

32
New cards
<p>Distribution of Software Application Types</p>

Distribution of Software Application Types

The breakdown of software applications comprising Web Applications (40%40\%), Mobile Apps (30%30\%), Enterprise Systems (20%20\%), Embedded Systems (5%5\%), and AI/ML Software (5%5\%).

33
New cards
<p>Work Breakdown Structure (WBS)</p>

Work Breakdown Structure (WBS)

A hierarchical decomposition of a project into simpler, manageable, and independent tasks, where the root of the tree is labeled by the project name itself.

34
New cards

Work Package

The lowest-level independent task in a Work Breakdown Structure, representing the simplest deliverable which typically requires less than 2 weeks2\text{ weeks} of work.

35
New cards

Use Case Diagram

A UML behavioral diagram that provides a high-level view of system functionality from the perspective of external actors and systems that interact with it.

36
New cards
<p>Actor (Use Case Diagram)</p>

Actor (Use Case Diagram)

A person or external system positioned outside the system boundary that interacts with the system, representing a role rather than a specific individual.

37
New cards

System Boundary (Use Case Diagram)

A rectangular box enclosing all the use cases belonging to the system, visually defining system scope and separating internal functionality from external actors.

38
New cards
<<include>> Relationship
<> Relationship

A use case relationship indicating that a base use case mandatory requires the behavior of another use case to complete, drawn as a dashed arrow pointing from the base use case to the included use case.

39
New cards
<<extend>> Relationship
<> Relationship

A use case relationship indicating optional or conditional behavior added to a base use case, drawn as a dashed arrow pointing from the extending use case to the base use case.