Skip to content
CS Exit Ethiopia
All courses

Software Engineering

Open the unified study guide and question reading lookup

Computer Science Exit Exam Study Guide · 278 questions

Read the question first. Select the eye beside the reading hint, study the cited module section, then reveal the answer. Each eye controls only its own block. All hints and answers start closed whenever this page opens.

Read the linked study-guide sections before revealing the answer. PDF page references count from the first page of the document.

278 of 278 questions

Question 1

A company delivers registration first, then adds payments and reporting, each as a usable delivery. Which model specifically names this addition-of-functionality strategy, independent of whether earlier features are also refined?

  • A. Waterfall
  • B. Incremental
  • C. Spiral
  • D. Evolutionary

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE04 · Iteration, increments and early delivery

SE06 · Spiral development and risk

Study-guide references

Correct answer: B — Incremental

The delivery strategy adds usable capabilities in stages so that end users receive a valuable subset before the complete product is ready. Incremental development names that addition of functionality. Evolutionary development broadly emphasizes refinement and can overlap with increments, but does not specifically name the stated delivery distinction. Spiral is organized around risk-reduction cycles, and classical waterfall normally delays usable delivery until its planned development phases are complete.

Evidence in the complete study note

Choose incremental delivery when prioritized partial capability must reach users early. Smaller changes can be easier to debug and permit feedback, though architecture and integration still require planning. Iteration need not rebuild the whole system every time, and increments need not be perfectly independent modules. Broad descriptions of early working software can fit prototypes, iterative or Agile processes; identify the purpose of that early version.SE04
Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06

Choice by choice

A · incorrect — Classical waterfall organizes sequential phases rather than prioritizing staged usable subsets.

B · correct — Incremental development adds usable capability in successive deliveries.

C · incorrect — Spiral names risk-driven cycles; those may contain increments without defining this delivery strategy.

D · incorrect — Evolutionary refinement can overlap with increments, but the question asks the specific name for adding usable functionality.

Question 2

If you want to test individual sub-systems of software, which phase of software testing is appropriate?

  • A. Integration testing
  • B. Unit testing
  • C. System testing
  • D. Acceptance testing

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE35 · Testing levels and acceptance

Study-guide references

Correct answer: B — Unit testing

Unit testing tests isolated building blocks, including objects and subsystems; integration begins when individually tested components are combined.

Evidence in the complete study note

Acceptance testing supports the customer/user’s acceptance decision against agreed needs and criteria. Alpha typically happens in a controlled developer setting with selected users; beta uses external users in their environments. None of these levels is universally the longest. Unit is a level, while white-box is a technique; a unit can be tested using black-box cases too.SE35

Choice by choice

A · incorrect — Combines components rather than isolating a subsystem. See PDF p. 148, 144.

B · correct — Directly tests an individual object or subsystem. See PDF p. 148, 144.

C · incorrect — Tests components together as one system. See PDF p. 148, 144.

D · incorrect — Checks the delivered system against the client agreement. See PDF p. 148, 144.

Question 3

Which characteristic of requirements specifies that the requirement should be phrased so that there is one and only one interpretation for it?

  • A. Unambiguous
  • B. Correct
  • C. Feasible
  • D. Verifiable

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE11 · Validate requirements and maintain traceability

Study-guide references

Correct answer: A — Unambiguous

A single interpretation is the unambiguous property. Correctness, feasibility and verifiability answer different questions.

Evidence in the complete study note

Correct requirements reflect actual stakeholder needs. Complete requirements address the agreed scope, normal and exceptional behavior. Consistency excludes contradictions. Clarity/unambiguity gives one intended interpretation; feasibility/realism means achievable within constraints. Verifiability means objective evidence can check fulfillment. Replace “fast for most users” with a defined metric, workload and threshold.SE11

Choice by choice

A · correct — Rules out two or more interpretations. See PDF p. 68, 70.

B · incorrect — Accuracy to the client's view does not guarantee a unique reading. See PDF p. 68, 70.

C · incorrect — Realism concerns implementation within constraints. See PDF p. 68, 70.

D · incorrect — Requires a repeatable test, not a unique interpretation alone. See PDF p. 68, 70.

Question 4

Which option most completely summarizes the listed observable behaviors that functional requirements may specify?

  • A. specifies the tasks the program must complete
  • B. Specifies observable tasks the program must not perform
  • C. Specifies required observable responses to invalid input
  • D. All of the mentioned

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE09 · Functional requirements include prohibited behavior

Study-guide references

Correct answer: D — All of the mentioned

Functional requirements describe observable services and behavior, including what must happen, what is prohibited and how the system responds to errors. Each individual choice gives one of these forms. The all-of-the-mentioned option is therefore the complete summary. Selecting only A, B or C would omit other valid functional obligations; negative wording alone does not make a requirement nonfunctional.

Evidence in the complete study note

A functional requirement states an observable service or behavior, including reactions to inputs, errors and forbidden actions. “When the sensor detects intrusion, send an alert” is functional. “Only a manager may approve refunds” also specifies permitted/prohibited behavior. A negative statement is not automatically nonfunctional.SE09

Choice by choice

A · incorrect — Required tasks are functional, but A alone omits the other listed forms.

B · incorrect — Prohibited tasks can be functional, but B alone is incomplete.

C · incorrect — Required error responses are functional, but C alone is incomplete.

D · correct — All three listed observable behavior forms can be functional requirements.

Question 5

A team has little experience with a project’s unfamiliar technology. Major feasibility risks must be evaluated before each further commitment, and experienced risk-analysis support is available. Which lifecycle is selected specifically by that risk-driven criterion?

  • A. Iterative Enhancement Model
  • B. RAD
  • C. Spiral
  • D. Waterfall

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE02 · Lifecycle phases and model selection

SE06 · Spiral development and risk

Study-guide references

Correct answer: C — Spiral

Spiral organizes each cycle around objectives, alternatives, risk assessment and reduction before further commitment. That directly addresses the specified major feasibility risks and supported risk-analysis capability. Iterative enhancement can aid learning but does not make risk assessment its defining organizer; RAD needs rapid construction and skilled support. Classical waterfall fits stable requirements and familiar technology, which the scenario does not supply.

Evidence in the complete study note

Select a process using requirement stability, technical risk, delivery urgency, stakeholder availability, team skills and assurance needs. “Team has little experience” alone does not uniquely identify a process. A risk-driven cycle, prototype or carefully planned staged process may each help, depending on the actual uncertainty. No process eliminates the need for testing or documentation.SE02
Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06

Choice by choice

A · incorrect — Iteration supports feedback but is not defined by risk-driven commitments.

B · incorrect — RAD emphasizes rapid construction rather than the specified risk cycle.

C · correct — Spiral explicitly organizes commitment around major risk reduction.

D · incorrect — Unfamiliar technology and unresolved risks do not fit the stated classical waterfall rationale.

Question 6

In which step of SDLC actual programming of software code is done?

  • A. Development and Documentation
  • B. Maintenance and Evaluation
  • C. Design
  • D. Analysis

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE02 · Lifecycle phases and model selection

Study-guide references

Correct answer: A — Development and Documentation

Programming translates the design into source code in implementation. A corresponds to the development stage of implementation and unit testing.

Evidence in the complete study note

A common lifecycle names requirements, design, implementation, testing, deployment and maintenance. Analysis clarifies the problem; system design chooses architecture; object/detail design specifies interfaces and algorithms; implementation writes code; testing evaluates behavior; deployment puts it into service. These activities may overlap and repeat.SE02

Choice by choice

A · correct — Development is the option corresponding to producing source code; documentation accompanies the process. See PDF p. 18, 18, 19.

B · incorrect — Maintenance modifies an operational product. See PDF p. 18, 18, 19.

C · incorrect — Design derives implementation structure rather than source code. See PDF p. 18, 18, 19.

D · incorrect — Analysis establishes and organizes requirements. See PDF p. 18, 18, 19.

Question 7

Which offered requirement is nonfunctional, specifying a measurable quality rather than required or prohibited observable tasks?

  • A. specifies the tasks the program must complete
  • B. Specifies observable tasks the program must not perform
  • C. Specifies the required error response to invalid input
  • D. Search shall respond within two seconds under 100 concurrent users.

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE09 · Functional requirements include prohibited behavior

SE10 · Nonfunctional qualities and measurable constraints

Study-guide references

Correct answer: D — Search shall respond within two seconds under 100 concurrent users.

The response-time limit under a defined concurrent-user workload is a measurable performance requirement, a nonfunctional quality constraint. Required services, prohibited actions and specified error responses are all forms of observable functional behavior. Their positive or negative wording does not determine the category. D instead constrains how well the search service must perform, making it the unique nonfunctional example.

Evidence in the complete study note

A functional requirement states an observable service or behavior, including reactions to inputs, errors and forbidden actions. “When the sensor detects intrusion, send an alert” is functional. “Only a manager may approve refunds” also specifies permitted/prohibited behavior. A negative statement is not automatically nonfunctional.SE09
“Search responds within two seconds under 100 concurrent users” is measurable performance. “New users finish checkout within one minute without help” is usability. “Use Java” is a technology/pseudo-requirement, often separately classified as a system constraint. Dependability includes reliability, safety and robustness; portability is not its usual central category. Performance degradation at peak load primarily concerns performance, not automatically reliability.SE10

Choice by choice

A · incorrect — Required observable tasks are functional.

B · incorrect — Prohibited observable tasks can be functional.

C · incorrect — An observable error response specifies functional behavior.

D · correct — The time threshold and workload constrain performance quality.

Question 8

Which of the following is the understanding of software product limitations, learning system related problems or changes to be done in existing systems beforehand, identifying and addressing the impact of project on organization and personnel etc.?

  • A. Software Design
  • B. Feasibility Study
  • C. Requirement Gathering
  • D. System Analysis

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE08 · Feasibility and levels of requirements

Study-guide references

Correct answer: B — Feasibility study.

SE08 asks whether a proposal is worth doing and deliverable, considering existing limitations, impacts on organization and personnel, benefits, costs, skills and integration risk. That matches the stem’s preliminary impact and constraint investigation. System analysis studies the detailed problem and behavior and informs feasibility, but the broad early viability assessment is the more specific match here.

Evidence in the complete study note

Feasibility asks whether a proposal is worth doing and can be delivered within technical, economic, operational and schedule constraints. Examine existing limitations, organizational impacts, benefits, cost, available skills and integration risk. System analysis studies the problem and needed behavior in more detail; the activities inform each other.SE08

Choice by choice

A · incorrect — Design chooses solution structures rather than primarily assessing preliminary viability and organizational impacts.

B · correct — Feasibility investigates existing limitations, impacts and whether the proposal is worthwhile and deliverable.

C · incorrect — Gathering needs is useful input but does not by itself cover the full viability assessment.

D · incorrect — System analysis examines detailed problem behavior; feasibility is the more specific preliminary impact/viability activity.

Question 9

For a software product developed to meet a client’s requirements, which choice most completely describes its scope?

  • A. Software product refers any software created to meet the client's requirements.
  • B. Software product includes design and test documentation.
  • C. Software product includes requirement specifications, and user manuals.
  • D. All of the above

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE01 · Software engineering, processes and work products

Study-guide references

Correct answer: D — All of the above

SE01 explicitly includes executable code plus requirements, designs, test assets, configuration and user documentation in a software product. A describes the implemented software, while B and C name relevant accompanying artifacts. All three descriptions are therefore compatible; none limits the product to code alone. D is the inclusive answer among these options.

Evidence in the complete study note

Software engineering applies systematic methods to development, operation and maintenance. A software product includes executable code and relevant requirements, designs, test assets, configuration and user documentation. A process defines activities, ordering, roles, products and entry/exit conditions. Its four broad activities are specification, design/implementation, validation and evolution.SE01

Choice by choice

A · incorrect — True as one component, but incomplete as the requested full selection. Software built to meet client requirements forms part of the product.

B · incorrect — True as one component, but incomplete as the requested full selection. Relevant design and testing documentation are included product artifacts.

C · incorrect — True as one component, but incomplete as the requested full selection. Requirements specifications and user manuals are relevant product documentation.

D · correct — All three descriptions are compatible with the complete software-product scope.

Question 10

One of the followings is type of requirements associated with quality features of a software.

  • A. Business requirements
  • B. Functional requirements requirements
  • C. Non-functional
  • D. User requirements

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE10 · Nonfunctional qualities and measurable constraints

Study-guide references

Correct answer: C — Non-functional

Quality and user-visible constraints beyond functional behavior are nonfunctional requirements; user and business are viewpoints rather than this quality classification.

Evidence in the complete study note

Nonfunctional requirements include quality attributes and constraints. Performance concerns response time, throughput and resource use; reliability concerns failure-free service; availability concerns being ready for use; usability concerns task success and ease of learning. Security concerns protection; compatibility concerns cooperating environments; portability concerns moving environments; maintainability/supportability concern change, diagnosis and evolution.SE10

Choice by choice

A · incorrect — Business objectives do not identify the stated quality category. See PDF p. 66, 78.

B · incorrect — Specifies provided interactions and services. See PDF p. 66, 78.

C · correct — Matches nonfunctional quality constraints. See PDF p. 66, 78.

D · incorrect — User requirements can contain several types, so this is broader than quality features. See PDF p. 66, 78.

Question 11

A type of requirement that describes why the software project is needed and used to define the objective of the software is .

  • A. Business requirements
  • B. Functional requirements
  • C. Non-functional requirements
  • D. User requirements

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE08 · Feasibility and levels of requirements

Study-guide references

Correct answer: A — Business requirements.

SE08 distinguishes the business reason and objectives of a project from user needs and detailed system obligations. The question asks why the project is needed and what objectives it serves, so business requirements match directly. Functional requirements describe behavior, while nonfunctional requirements describe qualities or constraints; neither primarily states the project's business justification.

Evidence in the complete study note

Business requirements explain why the project exists and its goals. User requirements describe stakeholder needs at a useful high level; system requirements specify detailed services and constraints. The Software Requirements Specification (SRS) organizes the agreed requirements. A natural-language specification communicates with clients while analysis models formalize it for technical discussion; real specifications can also contain diagrams.SE08

Choice by choice

A · correct — Business requirements state the project's purpose, justification and intended organizational goals.

B · incorrect — Functional requirements specify observable system services rather than the overall business reason for the project.

C · incorrect — Nonfunctional requirements specify qualities or constraints rather than why the project exists.

D · incorrect — User requirements describe stakeholder needs at a high level rather than the project's business justification.

Question 12

Which of the following is used to model the functionality of software?

  • A. Use case diagram
  • B. Class diagram
  • C. E-R diagram
  • D. Deployment diagram

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE14 · Actors, use cases and scope

SE-S03 · Modeling categories and data diagrams

SE24 · Architecture styles and integration boundaries

Study-guide references

Correct answer: A — Use case diagram

Use-case diagrams model external roles and their goals or interactions with the system. This is the functional view requested. Class diagrams instead emphasize static classes, features and relationships. Entity–relationship diagrams organize entity types, attributes and data relationships. Deployment diagrams map software artifacts to execution nodes. Each can contribute to understanding a system, but only the use-case view directly presents the actor-goal functionality in this comparison.

Evidence in the complete study note

Draw actors outside the system boundary rectangle and use-case ovals inside. Name a goal with a verb and noun. The diagram shows roles, goals and relationships, not the full detailed algorithm or UI layout. Being an internal component is different from being an external actor; the chosen boundary determines which role applies.SE14
An entity–relationship diagram models entity types, their attributes and the relationships between them, commonly for data design. Its focus differs from a use-case diagram of external roles and goals, a class diagram of classes and their features, or a deployment diagram mapping artifacts to execution nodes.SE-S03
A component diagram shows components/interfaces/dependencies; a deployment diagram places software artifacts on nodes.SE24

Choice by choice

A · correct — Use-case diagrams show external actors and the system goals they use.

B · incorrect — Class diagrams describe static types and their relationships.

C · incorrect — ER diagrams describe entity types, attributes and data relationships.

D · incorrect — Deployment diagrams map software artifacts onto execution nodes.

Question 13

Which of the following refers to the deployment platform? i

  • A. Use case
  • B. Tier
  • C. Layer
  • D. Component

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE23 · Layers, tiers and architecture views

Study-guide references

Correct answer: B — Tier.

SE23 explicitly separates logical abstraction from deployment separation. A layer organizes responsibilities logically, whereas a tier describes their deployment separation or platform arrangement. A use case models an actor goal, and a component is a software building block. Neither is the term for the deployment distinction asked for here.

Evidence in the complete study note

A layer is a logical abstraction level; a tier is a deployment separation. A closed layered architecture permits calls only to the immediately lower layer; an open one permits approved skipping. For top-to-bottom A,B,C,D, A→B obeys closed layering, A→C skips, and lower-to-upper calls violate the simple dependency rule unless explicitly mediated by a defined mechanism.SE23

Choice by choice

A · incorrect — A use case models a goal or interaction rather than the deployment platform separation.

B · correct — A tier identifies deployment separation, contrasting with logical layering.

C · incorrect — A layer is a logical abstraction level and need not occupy a distinct deployment platform.

D · incorrect — A component is a software element and does not itself denote a deployment tier.

Question 14

When requirements will change substantially and frequent early feedback is needed, which classical process organization is least accommodating among these choices?

  • A. Waterfall
  • B. Scrum
  • C. RAD
  • D. Agile

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE03 · Waterfall and the V-model

SE05 · Agile values, stories and Scrum

SE07 · Prototypes, RAD and reuse-oriented development

Study-guide references

Correct answer: A — Waterfall

Classical waterfall commits to planned phases and reviewed deliverables, making late feedback and changed requirements costly. Agile and Scrum plan and inspect work incrementally, allowing later content to adapt. RAD also uses rapid construction and user participation to obtain feedback. The comparison therefore favors waterfall as the least accommodating under the stated conditions, without claiming that a waterfall project is physically unable to authorize any change.

Evidence in the complete study note

Classical waterfall separates planned phases with reviewed deliverables. It fits well-understood, stable requirements and familiar technology; late feedback makes changes costly. It does not make change physically impossible: real projects revisit work under control, and modified waterfall explicitly includes feedback. Rigidity offers milestone visibility but can freeze incorrect assumptions.SE03
Agile favors people collaborating, useful working results, customer participation and adaptation over rigid adherence to procedures, exhaustive documents, contracts or fixed plans. The latter still have value. Agile does not mean no planning or no documentation. A user story states a small user need and value, supported by acceptance criteria; an epic groups broader work.SE05
A prototype explores requirements, usability or technical feasibility. A throwaway prototype is discarded after learning; an evolutionary prototype is deliberately refined toward production. A quick prototype may omit robustness, security or architecture, so do not deploy it unchanged without evaluation. Coding may occur during prototyping even if a diagram labels that activity construction rather than coding.SE07

Choice by choice

A · correct — Late feedback and phase commitments make major requirement changes costly in classical waterfall.

B · incorrect — Scrum inspects usable increments and adapts later work within its planning framework.

C · incorrect — RAD uses rapid construction and user participation to obtain feedback.

D · incorrect — Agile explicitly values responding to changing needs.

Question 15

Which of the following aims to find errors?

  • A. Requirement Analysis
  • B. Design
  • C. Testing
  • D. None of the above

Distinguish process assurance from product evaluation, and compare specified obligations with actual stakeholder needs.

Study-guide sections

SE34 · Quality assurance, verification and validation

Study-guide references

Correct answer: C — Testing

Testing systematically attempts to expose errors in the implementation; the other named activities primarily construct specifications and designs.

Evidence in the complete study note

A fault/defect is an underlying problem; an error may be an incorrect internal state; a failure is an externally observed departure from required service. Reliability is a product quality attribute; low cost or short development time are project outcomes. Tests increase confidence and reveal defects but cannot generally guarantee correctness over every possible input.SE34

Choice by choice

A · incorrect — Structures requirements, although validation may reveal requirement defects. See PDF p. 140, 100, 18.

B · incorrect — Constructs the solution design. See PDF p. 140, 100, 18.

C · correct — Explicit planned fault detection activity. See PDF p. 140, 100, 18.

D · incorrect — Testing is present, so none is false. See PDF p. 140, 100, 18.

Question 16

Which among the following focuses on the way the elements interact with each other at runtime during architectural design?

  • A. All choices are correct
  • B. Component-and-connector (C&C) structures
  • C. Allocation structures
  • D. Module decomposition structure

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE23 · Layers, tiers and architecture views

Study-guide references

Correct answer: B — Component-and-connector structures.

The runtime interaction of software elements is the subject of component-and-connector structures in SE23. Module structures instead organize the code, while allocation structures relate software to hardware, teams or environments. These are different architectural views, so the inclusive choice fails: only the C&C option specifically answers the runtime-interaction focus.

Evidence in the complete study note

A structure is the elements/relations themselves; a view represents selected aspects. Module structures show code organization, component-and-connector structures runtime interaction, and allocation structures map software to hardware, teams or environment. Processes/threads belong in concurrency views. Evaluate architectures against quality attributes and scenarios; processor allocation, decomposition and style selection can all be architectural concerns.SE23

Choice by choice

A · incorrect — The alternatives address different architectural concerns, so not every choice focuses on runtime interaction.

B · correct — C&C structures show runtime elements and the connectors through which they interact.

C · incorrect — Allocation structures map software to hardware, teams or environments rather than primarily describing runtime exchanges.

D · incorrect — Module decomposition shows code organization rather than the runtime interactions emphasized by the stem.

Question 17

Which option combines both explicitly specified testability mechanisms among A, C and D? Treat refactoring alone as behavior-preserving restructuring with no stated testability improvement.

  • A. Sand box
  • B. A and D
  • C. Refactoring
  • D. Limiting structural complexity

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE27 · Patterns, variability and testability

SE22 · Cohesion, coupling, modularity and refactoring

Study-guide references

Correct answer: B — A and D

A sandbox can isolate execution, giving control over the test environment. Limiting structural complexity also supports testability by making behavior easier to control and observe. Refactoring preserves behavior while changing structure, but without a stated improvement it does not automatically supply either testability effect. The combination A and D therefore includes both explicitly supported mechanisms; the individual choices each give only one.

Evidence in the complete study note

Variability can use selectable features, omission/inclusion and extension points; overloading supplies alternate signatures in code but is not every variability mechanism. Testability improves with controllable inputs, observable outputs, replaceable dependencies and limited structural complexity. A sandbox can isolate execution. Assess each design claim independently before evaluating a combined statement.SE27
Logical cohesion groups similar-category operations, often selected by a flag; temporal cohesion groups operations done at the same time; functional cohesion focuses on one task. Splitting an unrelated three-purpose component improves modularity. If behavior is preserved, the restructuring is refactoring; the words are not mutually exclusive answers. Smaller modules can aid understanding, independent work, reuse and maintenance, but too many interfaces also create complexity.SE22

Choice by choice

A · incorrect — Sandbox isolation is valid but only one of the two mechanisms.

B · correct — A and D include both explicitly supported mechanisms.

C · incorrect — Unspecified refactoring need not improve testability.

D · incorrect — Limited structural complexity is valid but only one of the two mechanisms.

Question 18

Which choices explicitly provide architectural variability through selectable elements or defined extension interfaces? Select all that apply. Treat overloading as alternate code signatures only.

  • A. Overloading
  • B. Omission or inclusion of elements
  • C. Extension point
  • D. All of the above

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE27 · Patterns, variability and testability

Study-guide references

Correct answers (select all): B, C — Omission or inclusion of elements; Extension point

Omitting or including selected elements permits configured architectural variation, and extension points define places where additional behavior can be supplied. Overloading by itself supplies alternate code signatures and does not establish either architectural mechanism. Thus B and C meet the specified architectural scope. The all-of-the-above choice includes that insufficient code-level case and therefore cannot be selected as a correct aggregate.

Evidence in the complete study note

Variability can use selectable features, omission/inclusion and extension points; overloading supplies alternate signatures in code but is not every variability mechanism. Testability improves with controllable inputs, observable outputs, replaceable dependencies and limited structural complexity. A sandbox can isolate execution. Assess each design claim independently before evaluating a combined statement.SE27

Choice by choice

A · incorrect — Alternate signatures alone do not define the specified architectural variability.

B · correct — Selectable omission or inclusion changes architectural configuration.

C · correct — Extension points explicitly support variation at defined boundaries.

D · incorrect — It incorrectly includes overloading alone as an architectural mechanism.

Question 19

Which choice most completely describes the stated advantages of the Factory Method pattern?

  • A. Allows the sub-classes to choose the type of objects to create
  • B. Promotes loose coupling
  • C. A and B
  • D. None of the above

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE27 · Patterns, variability and testability

Study-guide references

Correct answer: C — A and B

SE27 describes Factory Method as letting subclasses choose a concrete product through a creation operation, reducing dependence on concrete constructors. Those are exactly the two benefits in A and B, so C is the inclusive answer. The reference is to Factory Method; a simple factory is related but does not necessarily delegate product choice to subclasses.

Evidence in the complete study note

Factory Method lets subclasses choose a concrete product through a creation operation, reducing coupling to concrete constructors. A simple factory centralizes creation but is not identical to Factory Method. Singleton controls access to one instance; Observer notifies subscribers; Memento stores/restores state while hiding representation; Iterator traverses; Decorator adds behavior through wrapping. The pattern name is Memento, not Momento.SE27

Choice by choice

A · incorrect — True as one component, but incomplete as the requested full selection. Factory Method lets subclasses select the concrete product through the creation operation.

B · incorrect — True as one component, but incomplete as the requested full selection. Depending on the creation abstraction reduces coupling to concrete product constructors.

C · correct — Both listed benefits hold for Factory Method, making this the inclusive answer.

D · incorrect — The note explicitly supports both benefits, so none is false.

Question 20

Which statements correctly distinguish architectural structures and views? Select all that apply.

  • A. B and D only
  • B. Views design structures whereas architects document the structures.
  • C. A structure is the set of elements and their relations as they exist in software or hardware.
  • D. A view is a representation of a structure

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE23 · Layers, tiers and architecture views

Study-guide references

Correct answers (select all): C, D — A structure is the set of elements and their relations as they exist in software or hardware.; A view is a representation of a structure

An architectural structure consists of elements and their relations in the modeled software or hardware. A view represents selected aspects of a structure for a particular purpose. Both C and D therefore express compatible definitions. Views are representations, not agents that design structures, so B is false. The aggregate A includes that false statement and incorrectly excludes the true structure definition.

Evidence in the complete study note

A structure is the elements/relations themselves; a view represents selected aspects. Module structures show code organization, component-and-connector structures runtime interaction, and allocation structures map software to hardware, teams or environment. Processes/threads belong in concurrency views. Evaluate architectures against quality attributes and scenarios; processor allocation, decomposition and style selection can all be architectural concerns.SE23

Choice by choice

A · incorrect — The B-and-D-only combination includes false B and excludes true C.

B · incorrect — Views represent structures rather than acting as their designers.

C · correct — A structure is the underlying set of elements and relations.

D · correct — A view represents selected aspects of a structure.

Question 21

Which testing level isolates one function or class, using stubs or mocks for called dependencies, so its internal branches can be tested directly?

  • A. System testing
  • B. Integration testing
  • C. System and integration testing together
  • D. Unit testing

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE35 · Testing levels and acceptance

SE36 · Test types, regression and exploratory work

Study-guide references

Correct answer: D — Unit testing

Unit testing isolates a function, class or small component and may replace dependencies with stubs or mocks. That matches the stated test scope. White-box cases can then target its internal branches, but white-box is a technique rather than a testing level. Integration and system tests cover combined interactions or the full system, so neither matches the isolation specified here.

Evidence in the complete study note

Unit testing isolates a function, class or small component, often replacing dependencies with stubs/mocks; a driver invokes the unit and a stub substitutes a called dependency. Integration testing exercises interfaces and interactions among combined parts. System testing checks the complete integrated system against functional and nonfunctional requirements in a representative environment.SE35
Functional tests check required behavior against the SRS and acceptance criteria. Performance tests assess speed, throughput and resources under a specified workload; load uses expected demands and stress exceeds normal limits. Usability, security, compatibility and reliability tests target their respective qualities. “Normal operating conditions” alone does not distinguish functional from performance testing.SE36

Choice by choice

A · incorrect — System testing evaluates the complete integrated system.

B · incorrect — Integration testing targets interactions among combined parts.

C · incorrect — Combining system and integration levels does not give isolated unit scope.

D · correct — Unit testing isolates the function or class with replaceable dependencies.

Question 22

Which offered UML diagram models external behavioral goals and actor interactions at a high level, rather than detailed message timing or state evolution?

  • A. Component diagram
  • B. Use case diagram
  • C. Deployment diagram
  • D. Class Diagram

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE20 · Activity, state and data-flow models

SE14 · Actors, use cases and scope

Study-guide references

Correct answer: B — Use case diagram

A use-case diagram presents external roles, their goals and relationships within a chosen system boundary. It therefore matches the specified high-level behavioral scope. Component, deployment and class diagrams describe structural organization, allocation or static types. Sequence, activity and state diagrams would be appropriate for detailed interactions, workflows or state changes, but those finer-grained dynamic questions are explicitly outside this stem.

Evidence in the complete study note

An activity diagram models workflow: filled circle start, rounded actions, guarded decision diamond, thick fork/join bars and partitions/swimlanes for responsibility. A diamond can also merge alternative flows; a join synchronizes concurrent flows. A state machine models states and transitions triggered by events, often with guards/actions, for one object’s lifecycle.SE20
Draw actors outside the system boundary rectangle and use-case ovals inside. Name a goal with a verb and noun. The diagram shows roles, goals and relationships, not the full detailed algorithm or UI layout. Being an internal component is different from being an external actor; the chosen boundary determines which role applies.SE14

Choice by choice

A · incorrect — Component diagrams describe components and interfaces.

B · correct — Use-case diagrams show actor roles and high-level goals.

C · incorrect — Deployment diagrams allocate artifacts to nodes.

D · incorrect — Class diagrams show static types and relationships.

Question 23

Which choice most completely identifies the listed reasons requirements elicitation can be difficult?

  • A. All choices are correct
  • B. Problem of scope
  • C. Problem of understanding
  • D. Problem of volatility

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE11 · Validate requirements and maintain traceability

SE-S01 · Scope, understanding and changing requirements

Study-guide references

Correct answer: A — All choices are correct

SE11 identifies scope, understanding and volatility as distinct elicitation difficulties. Scope concerns agreeing what belongs in the system; understanding concerns discovering and interpreting actual needs; volatility concerns needs changing as the project progresses. Since all three listed problems are valid, the inclusive answer is appropriate rather than choosing just one source of difficulty.

Evidence in the complete study note

Correct requirements reflect actual stakeholder needs. Complete requirements address the agreed scope, normal and exceptional behavior. Consistency excludes contradictions. Clarity/unambiguity gives one intended interpretation; feasibility/realism means achievable within constraints. Verifiability means objective evidence can check fulfillment. Replace “fast for most users” with a defined metric, workload and threshold.SE11
Trace each requirement backward to its source/rationale and forward to design, code and tests. Record dependencies among requirements. A traceability matrix links these artifacts and helps impact analysis; it is not just a cost/schedule ledger. Stakeholders must negotiate conflicting requirements rather than independently approving incompatible demands. Scope, understanding and volatility are distinct elicitation difficulties.SE11
Elicitation difficulties have several distinct sources. Scope problems concern agreeing on system boundaries and the appropriate level of detail. Understanding problems arise when stakeholders and analysts have different domain knowledge, omit tacit needs or communicate conflicting interpretations. Volatility means that requirements change as circumstances and understanding develop.SE-S01
These difficulties call for repeated communication, explicit boundaries, negotiated meanings and controlled revision. They can occur together; resolving one does not automatically remove the others.SE-S01

Choice by choice

A · correct — All three listed difficulties are explicitly recognized in the complete note.

B · incorrect — True as one component, but incomplete as the requested full selection. Unclear system boundaries make agreeing on included and excluded requirements difficult.

C · incorrect — True as one component, but incomplete as the requested full selection. Different interpretations and tacit stakeholder needs complicate accurate understanding.

D · incorrect — True as one component, but incomplete as the requested full selection. Changing needs make elicitation an ongoing activity rather than a one-time capture.

Question 24

Which development activity primarily recognizes and clarifies the problem, required behavior and related constraints before choosing the solution architecture or algorithms?

  • A. Implementation
  • B. Testing
  • C. Analysis
  • D. Design

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE02 · Lifecycle phases and model selection

Study-guide references

Correct answer: C — Analysis

Analysis clarifies the problem, required behavior and constraints. Design then chooses architecture, interfaces and algorithms for a solution; implementation writes it, and testing evaluates its behavior. The revised scope keeps these responsibilities distinct instead of mixing problem recognition with selecting methods to overcome it. Creativity can occur in several activities, so the activity’s purpose, rather than that adjective, determines the answer.

Evidence in the complete study note

A common lifecycle names requirements, design, implementation, testing, deployment and maintenance. Analysis clarifies the problem; system design chooses architecture; object/detail design specifies interfaces and algorithms; implementation writes code; testing evaluates behavior; deployment puts it into service. These activities may overlap and repeat.SE02

Choice by choice

A · incorrect — Implementation writes the selected solution.

B · incorrect — Testing evaluates behavior.

C · correct — Analysis clarifies the problem and constraints.

D · incorrect — Design selects the solution architecture and mechanisms.

Question 25

_______ is a set of notations and conventions used to describe and model an application.

  • A. All choices are correct
  • B. Unified approach (UA)
  • C. Unified modeling language (UML)
  • D. Jacobson's use case

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE17 · Class diagrams, visibility and multiplicity

Study-guide references

Correct answer: C — Unified modeling language (UML)

UML provides modeling notations and conventions; it is distinct from a development methodology.

Evidence in the complete study note

A class box lists name, attributes and operations; + public, - private, # protected and ~ package indicate visibility. A class diagram shows static types and relationships, while an object diagram shows particular instances/links. UML is maintained and standardized by OMG; it is a modeling language, not a lifecycle process. Structural things describe conceptual or physical structural elements.SE17

Choice by choice

A · incorrect — UA and use cases are not both equivalent to the language. See PDF p. 32.

B · incorrect — UA specifies steps for development. See PDF p. 32.

C · correct — The exact defined modeling notation language. See PDF p. 32.

D · incorrect — A use case is an interaction model inside the approach. See PDF p. 32.

Question 26

Which structural risk can arise when repeated software changes are made without coherent design or refactoring?

  • A. Reduced user engagement
  • B. Increased software complexity
  • C. Increased automation
  • D. Elimination of maintenance costs

Classify the motive for the change before its implementation: repair, environment, useful capability or reduced future risk.

Study-guide sections

SE01 · Software engineering, processes and work products

SE40 · Maintenance and software evolution

SE22 · Cohesion, coupling, modularity and refactoring

SE43 · Design choices, evidence and economical improvement

Study-guide references

Correct answer: B — Increased software complexity

Repeated changes without coherent boundaries can accumulate dependencies and make the evolving system harder to understand. Refactoring and good subsystem design help control that structural complexity while maintenance still requires impact analysis and regression checks. User engagement is a product-use outcome rather than the structural risk asked for. Automation is an execution technique, not itself structural deterioration, and ongoing evolution does not eliminate maintenance costs.

Evidence in the complete study note

Software engineering applies systematic methods to development, operation and maintenance. A software product includes executable code and relevant requirements, designs, test assets, configuration and user documentation. A process defines activities, ordering, roles, products and entry/exit conditions. Its four broad activities are specification, design/implementation, validation and evolution.SE01
Corrective maintenance fixes faults; adaptive maintenance responds to environment changes; perfective maintenance improves useful capability/performance; preventive maintenance reduces future risk, such as restructuring fragile code. Motive determines category; refactoring can support preventive or perfective work. Maintenance often lasts years and includes understanding legacy code and regression effort, so it may dominate lifecycle cost.SE40
Cohesion measures how well elements inside a module serve a related purpose; coupling measures dependency between modules. Seek high cohesion and low coupling. Shared mutable data and knowledge of another module’s internal representation increase coupling. Information hiding exposes stable operations while concealing changeable decisions.SE22
poor object design can still be complex.SE01
Refactor to preserve behavior while improving structure; optimize only against measured needs; record rationale and update traceability and regression evidence after change.SE43

Choice by choice

A · incorrect — Engagement concerns user behavior rather than the internal structural deterioration asked for.

B · correct — Accumulated poorly coordinated changes can increase structural complexity.

C · incorrect — Automation does not itself describe deterioration of responsibilities or dependency structure.

D · incorrect — Changing software still requires maintenance and regression work.

Question 27

Which of the following best describes the difference between CPM and PERT?

  • A. CPM focuses on minimizing cost, while PERT focuses on minimizing time.
  • B. CPM is used for projects with uncertain activity durations, while PERT is used for projects with known activity durations.
  • C. PERT is used for projects with uncertain activity durations, while CPM is used for projects with known activity durations.
  • D. PERT is deterministic, whereas CPM is probabilistic.

Write out the supplied quantities and dependency constraints. Compute and compare values under the stated metric, finish condition and assumptions.

Study-guide sections

SE30 · Slack assumptions and PERT calculations

Study-guide references

Correct answer: C — PERT models uncertain durations; traditional CPM uses point durations.

SE30 gives traditional CPM point estimates and PERT optimistic, most-likely and pessimistic duration estimates. PERT therefore represents duration uncertainty, whereas the traditional CPM calculation uses known or fixed activity durations. The cost-versus-time contrast is not the defining distinction here, and the other two choices reverse the described treatment of uncertainty.

Evidence in the complete study note

Traditional CPM uses point durations; PERT models uncertainty with optimistic a, most-likely m and pessimistic b. The classic estimate is TE=(a+4m+b)/6 and variance=((b-a)/6)^2. For 3,6,15 days, TE=42/6=7 days and variance=4 days². Do not replace the weighted estimate by a simple average. These formulas are approximations, not guaranteed actual completion times.SE30

Choice by choice

A · incorrect — The note's defining contrast concerns duration uncertainty rather than assigning cost exclusively to CPM.

B · incorrect — This reverses the models: PERT explicitly represents uncertain activity durations.

C · correct — PERT uses uncertain three-point estimates, while traditional CPM uses fixed point durations.

D · incorrect — The probabilistic/deterministic characterization is reversed relative to the note.

Question 28

A key benefit of using a project management tool in software development is:

  • A. Automatic bug detection and fixing.
  • B. Replacing the need for human project managers.
  • C. Improved communication and collaboration within the team.
  • D. Increased coding efficiency for developers.

Distinguish the planning or organization goal from the tool or structure used to support it. Apply the stated project conditions.

Study-guide sections

SE28 · Planning, WBS, estimation and tools

Study-guide references

Correct answer: C — Improved team communication and collaboration.

SE28 says planning tools coordinate ownership, dependencies and progress while leaving judgment to people. That coordination supports communication and collaboration. The tool does not automatically detect and repair code faults, replace project managers or directly guarantee faster coding. Those benefits would require other capabilities and evidence beyond project-management tooling itself.

Evidence in the complete study note

Planning is continuous: identify scope/deliverables, decompose work, estimate effort/duration/cost, assign resources, sequence dependencies and revise as evidence changes. A WBS is hierarchical and covers project scope without adding unrelated work. Tools help coordinate ownership, dependencies and progress; they do not replace judgment or automatically fix bugs.SE28

Choice by choice

A · incorrect — Project-management tools do not automatically detect and repair software defects.

B · incorrect — They support planning and coordination while human managers still supply judgment.

C · correct — Shared ownership, dependency and progress information helps the team communicate and collaborate.

D · incorrect — A direct increase in coding efficiency is not the general coordination benefit established here.

Question 29

A software development team is setting up a configuration management process. They need to identify the configuration items (CIs) for their project. Which of the following would not typically be considered a configuration item?

  • A. Internet browsers used by the development team
  • B. Source code files
  • C. User manuals
  • D. Test plans

Separate artifact history and controlled changes from scheduling, collaboration benefits and automated execution.

Study-guide sections

SE33 · Configuration, change control and version control

Study-guide references

Correct answer: A — Ordinary browsers used by the team are usually tools, not product configuration items.

Controlled configuration items include source files, requirements, manuals and test plans. A team's ordinary browser is normally just a tool. A particular browser version can become an environment CI if the project deliberately controls it for reproducible testing, but the word typically makes A the appropriate exception in the stated scenario.

Evidence in the complete study note

Configuration management identifies controlled items, versions/baselines, change procedures, status and audits. Items may include source code, requirements, manuals, test plans, environments and build configurations. A team’s ordinary browser is usually a tool rather than product CI, but a controlled test-browser version may be an environment CI.SE33

Choice by choice

A · correct — An ordinary team browser is usually a tool; a deliberately controlled test-browser version would be an exception.

B · incorrect — Source code files are standard controlled product configuration items.

C · incorrect — User manuals can be versioned and baselined alongside the software product.

D · incorrect — Test plans are controlled project artifacts whose versions must match the tested configuration.

Question 30

Which of the following is NOT a characteristic of a well-defined Work Breakdown Structure (WBS)?

  • A. It can be used to assign ownership and track the progress of project tasks.
  • B. It clearly defines deliverables for each level of the breakdown.
  • C. It includes activities that are outside the project scope.
  • D. It is organized in a hierarchical manner, with the overall project at the top and smaller tasks at the bottom.

Distinguish the planning or organization goal from the tool or structure used to support it. Apply the stated project conditions.

Study-guide sections

SE28 · Planning, WBS, estimation and tools

Study-guide references

Correct answer: C — It includes activities that are outside the project scope.

Planning breaks down the work needed to complete this project. Work outside project scope is therefore not part of its WBS; hierarchy and assignable tasks are consistent with decomposition.

Evidence in the complete study note

Planning is continuous: identify scope/deliverables, decompose work, estimate effort/duration/cost, assign resources, sequence dependencies and revise as evidence changes. A WBS is hierarchical and covers project scope without adding unrelated work. Tools help coordinate ownership, dependencies and progress; they do not replace judgment or automatically fix bugs.SE28

Choice by choice

A · incorrect — Task assignment and tracking serve project management. See PDF p. 90, 95.

B · incorrect — Deliverables constrain and clarify project work. See PDF p. 90, 95.

C · correct — Outside-scope activities do not belong to the work needed to complete the defined project. See PDF p. 90, 95.

D · incorrect — Breaking large tasks into smaller activities supports the hierarchy described. See PDF p. 90, 95.

Question 31

A project team is working on a software project with multiple developers. They decided to implement a version control system (VCS). Which of the following scenarios best describes the use case for a distributed VCS like Git?

  • A. The team prefers to avoid merge conflicts by locking files so only one developer can work on a file at a time.
  • B. The team is large, geographically distributed, and each developer needs to work on features independently and merge changes later.
  • C. The team is small, and all developers work in the same physical location on a single branch.
  • D. The project requires strict control over who can make changes, and all changes must be approved by a central authority before being committed.

Separate artifact history and controlled changes from scheduling, collaboration benefits and automated execution.

Study-guide sections

SE33 · Configuration, change control and version control

Study-guide references

Correct answer: B — Independent distributed development followed by merging.

SE33 says a distributed Git clone contains local history and allows independent branches that can later be merged. B matches that working arrangement directly. Git does not require everyone to lock files, use one local branch or obtain central permission before every local commit. Additional review policies can be imposed, but they do not define distributed version control.

Evidence in the complete study note

Change management handles request, impact assessment, decision/prioritization, implementation and validation; configuration management keeps all affected versions consistent. Distributed Git gives each clone local history and supports independent branches followed by merging; it does not eliminate merge conflicts or approvals. Plan test configuration management early and apply it throughout testing, not at just one exclusive phase.SE33

Choice by choice

A · incorrect — Exclusive file locking is not the defining distributed Git collaboration model.

B · correct — Local histories and independent branches support geographically distributed work followed by merging.

C · incorrect — A colocated team can use Git, but this scenario does not express its independent distributed-work benefit.

D · incorrect — Central approval policies can exist, but they do not define or require distributed local commits.

Question 32

The given statement describes which type of requirement? "A heat sensor detects an intrusion and alerts the system."

  • A. Known Requirement
  • B. None of the given options
  • C. Functional
  • D. Non-Functional

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE09 · Functional requirements include prohibited behavior

Study-guide references

Correct answer: C — Functional

Detection followed by an alert specifies an externally observable service, not a timing or quality constraint.

Evidence in the complete study note

A functional requirement states an observable service or behavior, including reactions to inputs, errors and forbidden actions. “When the sensor detects intrusion, send an alert” is functional. “Only a manager may approve refunds” also specifies permitted/prohibited behavior. A negative statement is not automatically nonfunctional.SE09

Choice by choice

A · incorrect — Known requirement is not the module's classification for this behavior. See PDF p. 65, 66.

B · incorrect — A functional option is present. See PDF p. 65, 66.

C · correct — Describes the system's required interaction with the intrusion sensor and alert recipient. See PDF p. 65, 66.

D · incorrect — No performance or other quality bound is stated. See PDF p. 65, 66.

Question 33

In the ordinary software lifecycle terminology used here, which document organizes the agreed user and detailed system requirements?

  • A. Software Design Description
  • B. Software Requirement Specification
  • C. Capability Development Document
  • D. Domain-Driven Design

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE08 · Feasibility and levels of requirements

SE21 · Design and subsystem decomposition

SE-S06 · Distinguish a requirements specification from neighboring terms

Study-guide references

Correct answer: B — Software Requirement Specification

The SRS records the agreed software services and constraints, including user-level and detailed system requirements. A Software Design Description explains how the solution is organized rather than being the requirements agreement. A Capability Development Document is a specialized defense capability-requirements artifact. Domain-driven design is an approach to organizing software models around business concepts. Thus the ordinary software requirements document requested is the SRS.

Evidence in the complete study note

User requirements describe stakeholder needs at a useful high level; system requirements specify detailed services and constraints. The Software Requirements Specification (SRS) organizes the agreed requirements.SE08
System design turns the analysis model into architecture: design goals, subsystem responsibilities, dependencies, hardware mapping, data management, access control, control flow and startup/shutdown/error policies.SE21
A Software Requirements Specification records agreed software services and constraints. A Capability Development Document is a defense capability-requirements artifact describing needed capability characteristics and performance parameters; its specialized acquisition context differs from the ordinary software SRS. Domain-driven design is an approach that organizes software models around the business domain, not the name of an agreed requirements specification.SE-S06

Choice by choice

A · incorrect — A design description records the solution structure rather than the agreed requirements specification.

B · correct — The SRS organizes agreed user and system services and constraints.

C · incorrect — A Capability Development Document belongs to a specialized defense capability-acquisition context.

D · incorrect — Domain-driven design is a modeling/design approach, not the name of the requirements document.

Question 34

Which listed statements describe supported advantages or uses of incremental delivery? Select all that apply. Interpret easier testing/debugging as a potential benefit of smaller changes, not a guarantee.

  • A. Easier to test and debug
  • B. Easier to test and debug & It is used when there is a need to get a product to the market early
  • C. Customer can respond to each increment
  • D. It is used when there is a need to get a product to the market early

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE04 · Iteration, increments and early delivery

Study-guide references

Correct answers (select all): A, B, C, D — Easier to test and debug; Easier to test and debug & It is used when there is a need to get a product to the market early; Customer can respond to each increment; It is used when there is a need to get a product to the market early

Incremental delivery adds usable capability in stages. Smaller changes can be easier to test and debug, users can provide feedback after increments, and prioritized partial capability can reach the market early. Thus A, C and D each describe a supported benefit, and B is also true because it combines two true points. These benefits still require architecture, integration and testing effort.

Evidence in the complete study note

Choose incremental delivery when prioritized partial capability must reach users early. Smaller changes can be easier to debug and permit feedback, though architecture and integration still require planning. Iteration need not rebuild the whole system every time, and increments need not be perfectly independent modules. Broad descriptions of early working software can fit prototypes, iterative or Agile processes; identify the purpose of that early version.SE04

Choice by choice

A · correct — Smaller increments can be easier to test and debug.

B · correct — Both the smaller-change and early-delivery points are supported.

C · correct — Users can respond to each usable increment.

D · correct — Early delivery of prioritized capability is a supported use.

Question 35

Use a process diagram whose named stages are requirements gathering, quick design, prototype construction, prototype refinement and engineering the production product. Which offered activity is not a separately named stage, although it can occur within prototype construction?

  • A. Coding
  • B. Prototype Refinement
  • C. Engineer Product
  • D. Quick Design

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE07 · Prototypes, RAD and reuse-oriented development

Study-guide references

Correct answer: A — Coding

Coding can be part of building an executable prototype even if the process diagram labels that work construction. It is therefore the offered activity that is not a separately named stage in the stated convention. Quick design, refinement and production engineering are named stages there. This answer concerns the diagram’s labels and does not claim that prototyping excludes coding or always follows one universal phase taxonomy.

Evidence in the complete study note

A prototype explores requirements, usability or technical feasibility. A throwaway prototype is discarded after learning; an evolutionary prototype is deliberately refined toward production. A quick prototype may omit robustness, security or architecture, so do not deploy it unchanged without evaluation. Coding may occur during prototyping even if a diagram labels that activity construction rather than coding.SE07

Choice by choice

A · correct — Coding can occur inside construction without a separate stage label.

B · incorrect — Prototype refinement is a named stage.

C · incorrect — Engineering the production product is a named stage.

D · incorrect — Quick design is a named stage.

Question 36

What is the major drawback of using the RAD Model?

  • A. Increases reusability of components, Highly specialized & skilled developers/designers are required
  • B. Increases reusability of components
  • C. Highly specialized & skilled developers/designers are required
  • D. Encourages customer/client feedback

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE07 · Prototypes, RAD and reuse-oriented development

Study-guide references

Correct answer: C — The need for highly skilled developers and designers.

SE07 describes RAD as rapid construction using timeboxes, user participation and often reusable components, but requiring skilled designers and developers. That staffing prerequisite is the listed drawback. Reuse and customer feedback are useful features. A combines the genuine prerequisite with a benefit, so C states the drawback accurately without misclassifying reuse.

Evidence in the complete study note

RAD uses rapid construction, timeboxing, user participation and often reusable components; it requires available users and skilled designers/developers. Reuse-oriented development searches components, evaluates fit, may adjust requirements, designs around interfaces and builds missing parts. Product-line assets may include requirements, architecture, components and tests; all are potentially reusable.SE07

Choice by choice

A · incorrect — It bundles a genuine staffing drawback with component reuse, which is generally a benefit.

B · incorrect — Component reuse helps rapid construction and is not the drawback asked for.

C · correct — RAD depends on skilled designers and developers, which can constrain staffing and feasibility.

D · incorrect — Customer feedback supports learning and fit rather than being the stated RAD disadvantage.

Question 37

Which requirements are the foundation from which quality is measured?

  • A. None of the mentioned
  • B. Hardware
  • C. Software
  • D. Programmers

Distinguish process assurance from product evaluation, and compare specified obligations with actual stakeholder needs.

Study-guide sections

SE34 · Quality assurance, verification and validation

Study-guide references

Correct answer: C — Software

Conformance is evaluated against software behavior specifications, making software requirements the foundation for the quality comparison here.

Evidence in the complete study note

Quality assurance establishes and checks processes/standards; quality control evaluates work products. An SQA plan identifies standards, responsibilities, evaluations, reviews, audits and assurance records. Quality of conformance means following the design/specification; a product can conform to a poor specification. Verification asks whether specified obligations are implemented correctly; validation asks whether the product meets intended stakeholder needs. Both can use reviews, analysis or execution, so “human-only versus computer-only” is false.SE34

Choice by choice

A · incorrect — A software requirements option is present. See PDF p. 140, 26.

B · incorrect — Hardware alone does not specify expected software behavior. See PDF p. 140, 26.

C · correct — Defines the behavior against which reliability and failure are judged. See PDF p. 140, 26.

D · incorrect — Programmer preferences are not the behavior specification. See PDF p. 140, 26.

Question 38

Which of the following is not a SQA plan for a project?

  • A. Documents to be produced by the SQA group
  • B. Evaluations to be performed
  • C. Audits and reviews to be performed
  • D. Amount of technical work

Distinguish process assurance from product evaluation, and compare specified obligations with actual stakeholder needs.

Study-guide sections

SE34 · Quality assurance, verification and validation

Study-guide references

Correct answer: D — Amount of general technical development work.

SE34 identifies assurance responsibilities, evaluations, reviews, audits and assurance records as SQA-plan contents. The documents produced by SQA are assurance records; evaluations, audits and reviews are assurance activities. The amount of general technical development work belongs primarily to project scope and effort planning rather than defining the SQA activities listed here.

Evidence in the complete study note

Quality assurance establishes and checks processes/standards; quality control evaluates work products. An SQA plan identifies standards, responsibilities, evaluations, reviews, audits and assurance records. Quality of conformance means following the design/specification; a product can conform to a poor specification. Verification asks whether specified obligations are implemented correctly; validation asks whether the product meets intended stakeholder needs. Both can use reviews, analysis or execution, so “human-only versus computer-only” is false.SE34

Choice by choice

A · incorrect — Assurance documents and records are legitimate SQA-plan deliverables.

B · incorrect — Planned evaluations are explicitly part of an SQA plan.

C · incorrect — Reviews and audits are explicitly listed assurance-plan activities.

D · correct — General technical-work quantity is a project scope/effort concern rather than the listed assurance-plan content.

Question 39

Which of the below is not a part of the Test Plan?

  • A. Schedule
  • B. Incident reports
  • C. Entry and exit criteria
  • D. Risk

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE39 · Test process, plans and defect reports

Study-guide references

Correct answer: B — Incident reports are execution outputs, rather than the test plan itself.

SE39 places objectives, scope, resources, schedule, risks and entry/exit criteria in test planning. Incident reports document observed problems during execution and are normally outputs of that work. They may be referenced by later plans, but that does not make actual incident reports an intrinsic part of the prospective test plan.

Evidence in the complete study note

A test plan describes intended work; incident/defect reports are normally execution outputs. A defect report should identify build/environment, steps, expected versus actual behavior, evidence and severity. Anyone finding a fault should record it; testers often coordinate reporting, but it is not their exclusive permission. Configuration control makes the tested version reproducible.SE39

Choice by choice

A · incorrect — The test schedule is planned work and belongs in a test plan.

B · correct — Incident reports normally record execution findings rather than describing the planned testing work.

C · incorrect — Entry and exit criteria define when testing can start or finish and belong in planning.

D · incorrect — Testing risks influence scope and priorities and are legitimate test-plan content.

Question 40

Exploratory testing is a -----?

  • A. Experience-based Test Design Technique
  • B. Black Box Test Design Technique
  • C. White Box Test Design Technique
  • D. Grey Box Test Design Technique

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE36 · Test types, regression and exploratory work

Study-guide references

Correct answer: A — Experience-based testing.

SE36 explicitly classifies exploratory testing as experience based because learning, test design and execution occur together. It may use knowledge of specifications or internals, but black-box, white-box and grey-box describe different bases of test derivation. None of them replaces the defining experience-based classification asked for in this question.

Evidence in the complete study note

Black-box techniques derive cases from specified behavior; white-box techniques derive them from internal structure; grey-box uses partial internal knowledge. Regression testing checks for unintended effects after change; confirmation testing checks the particular defect repair. Exploratory testing combines learning, design and execution and is experience based. Manual/automated describe execution support, not a compulsory black-/white-box classification.SE36

Choice by choice

A · correct — Exploratory testing uses experience while learning, designing and executing tests together.

B · incorrect — It may use external behavior, but black-box alone is not its defining classification.

C · incorrect — Exploratory testing does not require test cases to be derived from internal code structure.

D · incorrect — Partial internal knowledge can help exploration, but it does not define the technique.

Question 41

Non-conformance to software requirements is known as

  • A. Software reliability
  • B. Software availability
  • C. None of the mentioned
  • D. Software failure

Distinguish process assurance from product evaluation, and compare specified obligations with actual stakeholder needs.

Study-guide sections

SE34 · Quality assurance, verification and validation

Study-guide references

Correct answer: D — Software failure

Failure is the deviation of observed behavior from its specified behavior; reliability measures conformance rather than the non-conformance event.

Evidence in the complete study note

A fault/defect is an underlying problem; an error may be an incorrect internal state; a failure is an externally observed departure from required service. Reliability is a product quality attribute; low cost or short development time are project outcomes. Tests increase confidence and reveal defects but cannot generally guarantee correctness over every possible input.SE34

Choice by choice

A · incorrect — Probability or measure of success, not the deviation itself. See PDF p. 140.

B · incorrect — Availability is not defined as non-conformance. See PDF p. 140.

C · incorrect — The failure option supplies the defined term. See PDF p. 140.

D · correct — Matches deviation from specified behavior. See PDF p. 140.

Question 42

When comparing internal subsystem-grouping criteria with an external user perspective, which option names the external perspective rather than an internal structural or responsibility criterion?

  • A. Coupling
  • B. System's functionality
  • C. Cohesion
  • D. Users thinking

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE21 · Design and subsystem decomposition

SE22 · Cohesion, coupling, modularity and refactoring

Study-guide references

Correct answer: D — Users thinking

Coupling measures dependencies across subsystem boundaries, cohesion measures relatedness within a subsystem, and functionality helps assign responsibilities. These are internal structural grouping criteria. A user’s perspective describes externally needed tasks and behavior, so it is the different kind of information requested. User workflows can still inform architecture; the distinction does not claim users have no influence on design or that internal boundaries should ignore their needs.

Evidence in the complete study note

Group closely related objects and functionality, minimize associations crossing boundaries, and isolate communication infrastructure where useful. User workflows inform decomposition but do not alone dictate the internal structure. Analysis describes domain needs; subsystem decomposition is principally a design result. Architecture documentation supports communication and records major decisions, not every source-level execution step.SE21
Cohesion measures how well elements inside a module serve a related purpose; coupling measures dependency between modules. Seek high cohesion and low coupling. Shared mutable data and knowledge of another module’s internal representation increase coupling. Information hiding exposes stable operations while concealing changeable decisions.SE22

Choice by choice

A · incorrect — Coupling directly measures inter-subsystem dependency.

B · incorrect — Functionality guides internal responsibility grouping.

C · incorrect — Cohesion measures how well elements grouped inside a subsystem serve a related purpose.

D · correct — This names the external user perspective rather than an internal structural measure or responsibility criterion.

Question 43

The functional model is represented graphically with ——

  • A. Use case diagram
  • B. State transition diagram
  • C. Class diagram
  • D. Object diagram

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE13 · From scenarios to analysis objects

Study-guide references

Correct answer: A — Use case diagram

Use case diagrams represent the functional model; different diagrams represent the dynamic and object models.

Evidence in the complete study note

A scenario is one concrete execution; a use case abstracts the related successful and alternative scenarios. Analysis integrates functional (use cases/scenarios), structural/object (classes) and dynamic (states/interactions) models. Entity objects represent domain information such as Incident; boundary objects mediate interaction, such as ReportForm; control objects coordinate a use case. A UI form is normally boundary, not entity.SE13

Choice by choice

A · correct — Explicit graphical form of the functional model. See PDF p. 101.

B · incorrect — Models dynamic state transitions. See PDF p. 101.

C · incorrect — Models object structure. See PDF p. 101.

D · incorrect — Models object instances, not the functional model. See PDF p. 101.

Question 44

Under the course’s distinction between problem analysis and solution design, which statement is false?

  • A. System Analysis Focuses on the user's view of the system
  • B. Design focuses on the developer point of view.
  • C. Result of system analysis is a model that includes a subsystem decomposition
  • D. Requirements elicitation establishes externally visible stakeholder needs and constraints before internal solution design.

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE02 · Lifecycle phases and model selection

SE21 · Design and subsystem decomposition

SE08 · Feasibility and levels of requirements

Study-guide references

Correct answer: C — Result of system analysis is a model that includes a subsystem decomposition

Analysis clarifies the domain and externally required behavior; system design chooses the solution architecture and subsystem responsibilities. Attributing subsystem decomposition to the principal analysis result therefore confuses these stages. Requirements elicitation establishes stakeholder needs and constraints before the internal solution is selected. The revised elicitation option avoids the stronger claim that only one user’s viewpoint matters, while retaining the intended external-needs versus internal-design distinction.

Evidence in the complete study note

Analysis clarifies the problem; system design chooses architecture; object/detail design specifies interfaces and algorithms; implementation writes code; testing evaluates behavior; deployment puts it into service.SE02
User workflows inform decomposition but do not alone dictate the internal structure. Analysis describes domain needs; subsystem decomposition is principally a design result.SE21
User requirements describe stakeholder needs at a useful high level; system requirements specify detailed services and constraints.SE08

Choice by choice

A · incorrect — Analysis clarifies the user/domain view of required behavior.

B · incorrect — Design develops the solution structure and implementation-facing decisions.

C · correct — Subsystem decomposition is principally a system-design result, so attributing it to analysis is the false claim.

D · incorrect — Elicitation establishes externally visible stakeholder needs and constraints before choosing internal design.

Question 45

Which of the following heuristics is not used to identify Entity objects

  • A. Real-world entities
  • B. Real-world activities
  • C. Forms
  • D. Data sources

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE13 · From scenarios to analysis objects

Study-guide references

Correct answer: C — Forms normally identify boundary objects.

SE13 defines entity objects as domain information and gives ReportForm as a boundary mediating interaction. Thus forms normally suggest boundary objects rather than entity objects. Real-world things, domain activities represented as information and relevant stored data can suggest entity candidates; those are heuristics, not mechanical rules guaranteeing a class for every noun or activity.

Evidence in the complete study note

Use nouns as candidate objects, possessive descriptions as candidate attributes, and verbs such as manages/reports-to as candidate associations. These are heuristics, not automatic parsing rules. CRC means Class, Responsibilities, Collaborators. A control per use case or participating actor can be a useful starting point, not a mandatory UML rule or fixed object lifetime.SE13
A UI form is normally boundary, not entity.SE13

Choice by choice

A · incorrect — Real-world domain entities are natural candidates for entity objects.

B · incorrect — A domain activity represented as persistent domain information can suggest an entity candidate.

C · correct — A user-interface form normally mediates interaction and is modeled as a boundary object.

D · incorrect — Relevant domain data sources can suggest information-holding entities, subject to analysis rather than automatic conversion.

Question 46

"Consider a system where, a heat sensor detects an intrusion and alerts the security company." What kind of a requirement the system is providing?

  • A. Functional Requirement
  • B. Non-Functional
  • C. Constraints
  • D. Known Requirement

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE09 · Functional requirements include prohibited behavior

Study-guide references

Correct answer: A — Functional Requirement

Detecting an intrusion and notifying the security company is a required interaction/service independent of implementation.

Evidence in the complete study note

Write one clear obligation with an actor/trigger, action and observable result. “The system shall generate a PDF report” is functional. “The system shall not reveal another customer’s balance” can be a security-related functional rule. Security as a broad quality goal and the functions implementing it must be distinguished. Words such as must, should and not work do not by themselves determine a requirement’s classification.SE09

Choice by choice

A · correct — Specifies the system's required behavior. See PDF p. 65.

B · incorrect — No response-time, reliability or quality limit is stated. See PDF p. 65.

C · incorrect — No implementation or resource restriction is stated. See PDF p. 65.

D · incorrect — Known Requirement is not the behavioral category defined here. See PDF p. 65.

Question 47

which one of the following is used to Identifying Actors

  • A. What kind of dependencies are exist among use cases.
  • B. What information does the actor access?
  • C. Which user groups execute the system's main functions?
  • D. What are the tasks that the actor wants the system to perform?

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE14 · Actors, use cases and scope

Study-guide references

Correct answer: C — Which user groups execute the system's main functions?

Identifying user groups that execute the main functions identifies actors; questions about information and tasks identify scenarios.

Evidence in the complete study note

An actor is an external role interacting with the system; it can be a person, device or another system. A person may play several roles, and several people may play one role. A primary actor seeks a goal; a supporting actor provides a service. Ask which user groups perform main functions, administer or maintain the system, and which external systems exchange information.SE14

Choice by choice

A · incorrect — Concerns use-case relationships rather than identifying external entities. See PDF p. 71, 73.

B · incorrect — Listed as a scenario-identification question. See PDF p. 71, 73.

C · correct — Exact actor-identification heuristic. See PDF p. 71, 73.

D · incorrect — Listed as a scenario-identification question. See PDF p. 71, 73.

Question 48

_______________is requirement elicitation techniques that is used to gather the requirements using day-to-day working observation and notes made of the actual tasks.

  • A. Use case
  • B. Ethnography
  • C. Scenario
  • D. Interview

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE12 · Elicitation techniques, FAST and QFD

Study-guide references

Correct answer: B — Ethnography.

The stem describes observing people's actual daily tasks and recording what they do. SE12 names that observation-based elicitation approach ethnography. Interviews ask stakeholders questions, while scenarios and use cases describe executions or goals; those can complement observation but do not name the day-to-day fieldwork technique itself.

Evidence in the complete study note

Interviews ask stakeholders about needs; document analysis examines manuals, contracts and current records; observation/ethnography studies actual daily work. Prototypes reveal tacit expectations. Workshops/JAD bring users, managers and developers together with a facilitator and recorder to build consensus. Use several sources and check assumptions against observed work.SE12

Choice by choice

A · incorrect — A use case describes goal-oriented interactions rather than naming observational fieldwork.

B · correct — Ethnography gathers understanding by observing actual day-to-day work and recording it.

C · incorrect — A scenario is one concrete execution, not the observation-based elicitation technique itself.

D · incorrect — An interview asks people questions rather than primarily observing their daily tasks.

Question 49

Which one of the following is more related to effective management of software complexity?

  • A. Modularity
  • B. Reusability
  • C. Extensibility
  • D. All

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE21 · Design and subsystem decomposition

Study-guide references

Correct answer: A — Modularity

Decomposition into simpler, manageable subsystems controls complexity. Reuse and extensibility can benefit designs, but do not substitute for this direct mechanism.

Evidence in the complete study note

System design turns the analysis model into architecture: design goals, subsystem responsibilities, dependencies, hardware mapping, data management, access control, control flow and startup/shutdown/error policies. Detail/object design refines APIs, parameter/return types, exceptions, component choices and algorithms. A subsystem is a manageable logical collection with services and an interface; it need not be a physical replaceable artifact.SE21

Choice by choice

A · correct — Divides the solution domain into manageable simpler parts. See PDF p. 118, 32.

B · incorrect — Reusability is an additional benefit of object-oriented modules. See PDF p. 118, 32.

C · incorrect — Extensibility concerns future additions rather than directly partitioning complexity. See PDF p. 118, 32.

D · incorrect — The text directly establishes modularity; it does not identify all three as equivalent complexity mechanisms. See PDF p. 118, 32.

Question 50

Which one of the following testing required knowledge about internal structure, design and implementation of the system?

  • A. Black box Testing
  • B. White box testing
  • C. Alpha testing
  • D. Beta testing

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE36 · Test types, regression and exploratory work

Study-guide references

Correct answer: B — White box testing

Path testing requires source code and data-structure knowledge; black-box equivalence testing instead groups observable inputs.

Evidence in the complete study note

Black-box techniques derive cases from specified behavior; white-box techniques derive them from internal structure; grey-box uses partial internal knowledge. Regression testing checks for unintended effects after change; confirmation testing checks the particular defect repair. Exploratory testing combines learning, design and execution and is experience based. Manual/automated describe execution support, not a compulsory black-/white-box classification.SE36

Choice by choice

A · incorrect — Does not require internal paths. See PDF p. 149, 149.

B · correct — Matches the source-knowledge requirement. See PDF p. 149, 149.

C · incorrect — Alpha denotes development-team system testing, not an internal-knowledge technique. See PDF p. 149, 149.

D · incorrect — Beta denotes testing by customers, not an internal-knowledge technique. See PDF p. 149, 149.

Question 51

Which team organization shares development decisions among team members rather than centralizing technical coordination in a chief programmer?

  • A. Functional
  • B. Project
  • C. Democratic
  • D. Chief programmer

Distinguish the planning or organization goal from the tool or structure used to support it. Apply the stated project conditions.

Study-guide sections

SE32 · Team organization, development and maturity

Study-guide references

Correct answer: C — Democratic

Democratic teams share decisions, whereas chief-programmer teams centralize technical coordination. Functional and project organizations classify how people are grouped, not how authority is distributed. Asking about shared decision-making therefore makes democratic the unique answer. It does not require every individual to perform every lifecycle task; a democratic team can still divide work by expertise and responsibilities.

Evidence in the complete study note

Functional organizations group specialists by discipline; project organizations group people around projects. Functional specialization helps staffing and knowledge continuity but may create handoff barriers. Democratic teams share decisions; chief-programmer teams centralize technical coordination. These are different classification dimensions. Tuckman’s sequence is forming→storming→norming→performing→adjourning: orientation, conflict, norms, effective work and closure.SE32

Choice by choice

A · incorrect — Functional organization groups specialists by discipline.

B · incorrect — Project organization groups people by project rather than defining shared authority.

C · correct — Democratic teams share decisions.

D · incorrect — Chief-programmer teams centralize technical coordination.

Question 52

Which capability maturity model level an organization must master the requirements management software quality assurance, and software project planning

  • A. Repeatable level
  • B. Initial level
  • C. Defined level
  • D. Managed level

Distinguish the planning or organization goal from the tool or structure used to support it. Apply the stated project conditions.

Study-guide sections

SE32 · Team organization, development and maturity

Study-guide references

Correct answer: A — Historical CMM Level 2: Repeatable.

SE32 explicitly assigns requirements management, software project planning, quality assurance and configuration management to historical Software CMM Level 2. Its name is Repeatable, rather than the later CMMI label Managed. The other named choices correspond to levels 1, 3 and 4 in this historical model, so A matches both practices and terminology.

Evidence in the complete study note

Historical Software CMM levels are 1 Initial, 2 Repeatable, 3 Defined, 4 Managed, 5 Optimizing. Level2 establishes basic project discipline including requirements management, project planning, quality assurance and configuration management. These historical labels must not be silently replaced by modern CMMI terminology. A maturity model concerns process capability, not a guarantee that every product is defect free.SE32

Choice by choice

A · correct — Repeatable is historical Software CMM Level 2, which establishes the listed basic project practices.

B · incorrect — Initial is historical Level 1, before the repeatable project discipline specified here.

C · incorrect — Defined is historical Level 3, not the level associated with this basic practice list.

D · incorrect — Managed is historical Software CMM Level 4; modern CMMI terminology must not be substituted.

Question 53

All are the advantages of functional format structure, except

  • A. Ease of staffing
  • B. Production of good quality documents
  • C. No need job specialization
  • D. Efficient handling manpower turnover

Distinguish the planning or organization goal from the tool or structure used to support it. Apply the stated project conditions.

Study-guide sections

SE32 · Team organization, development and maturity

Study-guide references

Correct answer: C — No need for job specialization is false of a functional organization.

SE32 defines functional organizations as grouping specialists by discipline. Claiming that specialization is unnecessary contradicts that organizing principle. Ease of staffing and knowledge continuity are benefits of specialization; continuity can help with turnover. Specialist expertise can also support documentation quality, although no organizational form guarantees good documents. C is the clear exception.

Evidence in the complete study note

Functional organizations group specialists by discipline; project organizations group people around projects. Functional specialization helps staffing and knowledge continuity but may create handoff barriers. Democratic teams share decisions; chief-programmer teams centralize technical coordination. These are different classification dimensions. Tuckman’s sequence is forming→storming→norming→performing→adjourning: orientation, conflict, norms, effective work and closure.SE32

Choice by choice

A · incorrect — Grouping specialists supports staffing within established disciplines, so this is a plausible benefit.

B · incorrect — Specialist expertise can support good documentation; this is not the direct contradiction of functional grouping.

C · correct — This contradicts the defining use of specialist disciplines in a functional organization.

D · incorrect — Knowledge continuity within a functional group can help absorb staff turnover.

Question 54

Which testing should focus on testing the functionality of objects or methods?

  • A. Integration testing
  • B. White box testing
  • C. Black box testing
  • D. Unit testing

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE35 · Testing levels and acceptance

Study-guide references

Correct answer: D — Unit testing

Unit testing isolates the building blocks, including objects; a method is part of such an individual component's behavior.

Evidence in the complete study note

Acceptance testing supports the customer/user’s acceptance decision against agreed needs and criteria. Alpha typically happens in a controlled developer setting with selected users; beta uses external users in their environments. None of these levels is universally the longest. Unit is a level, while white-box is a technique; a unit can be tested using black-box cases too.SE35

Choice by choice

A · incorrect — Tests components together. See PDF p. 148, 144.

B · incorrect — A technique based on internal paths, not the requested component level. See PDF p. 148, 144.

C · incorrect — A technique based on external behavior, not a component level. See PDF p. 148, 144.

D · correct — Tests isolated objects or subsystems and their functionality. See PDF p. 148, 144.

Question 55

Which of the following views represents the interaction of the user with the software but tells nothing about the internal working of the software?

  • A. Use case diagram
  • B. Activity diagram
  • C. Class diagram
  • D. Sequence diagram

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE14 · Actors, use cases and scope

Study-guide references

Correct answer: A — Use case diagram

A use case describes external behavior from an actor's point of view without prescribing the internal realization.

Evidence in the complete study note

Draw actors outside the system boundary rectangle and use-case ovals inside. Name a goal with a verb and noun. The diagram shows roles, goals and relationships, not the full detailed algorithm or UI layout. Being an internal component is different from being an external actor; the chosen boundary determines which role applies.SE14

Choice by choice

A · correct — Directly models actor-visible interaction. See PDF p. 47, 54, 51.

B · incorrect — Models action/control flow and may include internal work. See PDF p. 47, 54, 51.

C · incorrect — Describes classes and their structure. See PDF p. 47, 54, 51.

D · incorrect — Distributes interaction among participating objects, revealing internal collaboration. See PDF p. 47, 54, 51.

Question 56

Requirements and technical feasibility are unclear. The immediate goal is to build an exploratory version for user feedback and feasibility learning, then discard it rather than deliver it as production software. Which model best names that immediate activity?

  • A. Incremental model
  • B. Prototype model
  • C. Spiral model
  • D. Waterfall model

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE07 · Prototypes, RAD and reuse-oriented development

SE06 · Spiral development and risk

Study-guide references

Correct answer: B — Prototype model

A throwaway prototype explores requirements, usability or technical feasibility and is discarded after learning. That exactly matches the immediate purpose specified. Incremental delivery would provide usable production capability; spiral would organize broader commitments around risk-driven cycles and might use a prototype within them. Classical waterfall favors understood requirements and familiar technology. The specific learning-and-discard goal therefore identifies the prototype model.

Evidence in the complete study note

A prototype explores requirements, usability or technical feasibility. A throwaway prototype is discarded after learning; an evolutionary prototype is deliberately refined toward production. A quick prototype may omit robustness, security or architecture, so do not deploy it unchanged without evaluation. Coding may occur during prototyping even if a diagram labels that activity construction rather than coding.SE07
Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06

Choice by choice

A · incorrect — Incremental delivery targets usable capability rather than a discarded exploratory artifact.

B · correct — A throwaway prototype explores needs and feasibility before being discarded.

C · incorrect — Spiral may use a prototype, but names the broader risk-driven process.

D · incorrect — The stated uncertainty lacks classical waterfall’s stable, familiar conditions.

Question 57

What is the purpose of a sequence diagram?

  • A. To show the interactions between actors and a system
  • B. To show the behavior of objects in a system
  • C. To show the flow of activities in a system
  • D. To show the order and timing of interactions between objects

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE19 · Sequence diagrams and the emergency-report example

Study-guide references

Correct answer: D — To show the order and timing of interactions between objects

The vertical axis is time and arrows are messages among participating objects; this directly supports order and timing.

Evidence in the complete study note

Sequence diagrams show interactions across lifelines, with order/time generally downward. Messages cross between participants; activation rectangles show execution. A creation message starts a lifeline; an X marks modeled destruction, not a guarantee about when a garbage collector runs. Synchronous calls wait for completion; asynchronous messages permit the sender to proceed.SE19

Choice by choice

A · incorrect — Actor interaction is part of some sequences but is less precise than object-message order. See PDF p. 54.

B · incorrect — Broadly describes behavior without identifying temporal interaction. See PDF p. 54.

C · incorrect — Activity flow is represented by activity diagrams. See PDF p. 54.

D · correct — Matches time-ordered messages and activations. See PDF p. 54.

Question 58

Which of the following diagram types is used to represent the static structure of a system?

  • A. Use case documentation
  • B. Sequence diagram
  • C. Class diagram
  • D. Activity diagram

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE17 · Class diagrams, visibility and multiplicity

Study-guide references

Correct answer: C — Class diagram

Class diagrams describe system structure in classes, attributes, operations and relationships; sequence and activity models describe behavior.

Evidence in the complete study note

A class box lists name, attributes and operations; + public, - private, # protected and ~ package indicate visibility. A class diagram shows static types and relationships, while an object diagram shows particular instances/links. UML is maintained and standardized by OMG; it is a modeling language, not a lifecycle process. Structural things describe conceptual or physical structural elements.SE17

Choice by choice

A · incorrect — Documents functions from actors' viewpoints. See PDF p. 51, 101.

B · incorrect — Represents interactions over time. See PDF p. 51, 101.

C · correct — Explicit structural description of classes and objects. See PDF p. 51, 101.

D · incorrect — Models activities and control flow. See PDF p. 51, 101.

Question 59

Which is the following is the most important feature of the spiral model?

  • A. Efficiency management
  • B. Time management
  • C. Quality management
  • D. Risk management

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE06 · Spiral development and risk

Study-guide references

Correct answer: D — Risk management.

SE06 makes risk the organizing principle of spiral development. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops an appropriate next result and plans further commitment. Time, efficiency and quality still matter, but they do not distinguish spiral from other processes as directly as its explicit risk-driven cycles.

Evidence in the complete study note

Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06

Choice by choice

A · incorrect — Efficiency is useful, but it is not the defining organizing feature of spiral cycles.

B · incorrect — Time management matters in many processes and does not distinguish spiral.

C · incorrect — Quality management is important generally, but the defining spiral emphasis is risk.

D · correct — Each spiral cycle explicitly evaluates and reduces the most important risks.

Question 60

_______ is the process of writing down the user and system requirements in a requirements document.

  • A. Feasibility study
  • B. Requirements elicitation and analysis.
  • C. Requirements specification
  • D. Requirements validation

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE08 · Feasibility and levels of requirements

Study-guide references

Correct answer: C — Requirements specification

Specification translates analyzed information into a document containing user requirements and detailed system requirements.

Evidence in the complete study note

Business requirements explain why the project exists and its goals. User requirements describe stakeholder needs at a useful high level; system requirements specify detailed services and constraints. The Software Requirements Specification (SRS) organizes the agreed requirements. A natural-language specification communicates with clients while analysis models formalize it for technical discussion; real specifications can also contain diagrams.SE08

Choice by choice

A · incorrect — Decides viability before detailed analysis. See PDF p. 26, 25, 26.

B · incorrect — Derives requirements rather than being the document-writing step. See PDF p. 26, 25, 26.

C · correct — Directly names translation into the requirements document. See PDF p. 26, 25, 26.

D · incorrect — Checks realism, consistency and completeness of the document. See PDF p. 26, 25, 26.

Question 61

Incremental model of software development is

  • A. A reasonable mode when requirements are well define
  • B. Good model when a working core product is required quickly
  • C. Good model for the projects with large development teams
  • D. Good model when user requirements are not complete

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE04 · Iteration, increments and early delivery

Study-guide references

Correct answer: B — Good model when a working core product is required quickly

Early increments are usable stripped-down products; early working capability is the clearest fit among these options.

Evidence in the complete study note

Choose incremental delivery when prioritized partial capability must reach users early. Smaller changes can be easier to debug and permit feedback, though architecture and integration still require planning. Iteration need not rebuild the whole system every time, and increments need not be perfectly independent modules. Broad descriptions of early working software can fit prototypes, iterative or Agile processes; identify the purpose of that early version.SE04

Choice by choice

A · incorrect — Well-defined requirements can be useful, but are not the distinctive advantage asked. See PDF p. 22, 22.

B · correct — Directly supported by early working software. See PDF p. 22, 22.

C · incorrect — The module specifically notes fewer staff can implement early increments. See PDF p. 22, 22.

D · incorrect — Feedback can refine requirements, but the module also calls for sufficient overall definition to partition them. See PDF p. 22, 22.

Question 62

Which relationship are used when you have one use case that is similar to another, but does something slightly differently or something more.

  • A. Generalization
  • B. Aggregation
  • C. Composition
  • D. Association

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE16 · Include, extend, generalization and abstract use cases

Study-guide references

Correct answer: A — Generalization

Use-case generalization specializes a general use case by adding detail or varying its realization, as in password versus smart-card authentication.

Evidence in the complete study note

Generalization relates a specialized actor/use case to a more general one, with a hollow triangle toward the general element. An abstract use case specifies behavior for specialization and is not directly instantiated as a complete use case. It is not defined merely by reuse or lack of a direct actor line. Included behavior is incorporated where the inclusion is reached; do not infer every conditional branch in the base always executes.SE16

Choice by choice

A · correct — Direct specialization mechanism described by the module. See PDF p. 51.

B · incorrect — Whole-part relationship, not use-case specialization. See PDF p. 51.

C · incorrect — Whole-part lifecycle ownership, not use-case specialization. See PDF p. 51.

D · incorrect — Communication/linkage alone does not express the stated specialized behavior. See PDF p. 51.

Question 63

______a software product is necessary to rectify the bugs observed while the system is in use.

  • A. Adaptive maintenance
  • B. Corrective maintenance
  • C. Perfective maintenance
  • D. Preventive maintenance

Classify the motive for the change before its implementation: repair, environment, useful capability or reduced future risk.

Study-guide sections

SE40 · Maintenance and software evolution

Study-guide references

Correct answer: B — Corrective maintenance

The purpose of the change determines the maintenance category. Corrective maintenance repairs faults observed during use. Adaptive maintenance handles environmental changes, perfective maintenance improves useful capability or performance, and preventive maintenance reduces future risk before a corresponding failure occurs. Because the scenario starts with observed bugs that need repair, corrective maintenance is the direct category rather than one of the other three motives.

Evidence in the complete study note

Corrective maintenance fixes faults; adaptive maintenance responds to environment changes; perfective maintenance improves useful capability/performance; preventive maintenance reduces future risk, such as restructuring fragile code. Motive determines category; refactoring can support preventive or perfective work. Maintenance often lasts years and includes understanding legacy code and regression effort, so it may dominate lifecycle cost.SE40

Choice by choice

A · incorrect — Adaptive maintenance responds to a changed environment.

B · correct — Corrective maintenance repairs observed defects.

C · incorrect — Perfective maintenance improves useful capability or performance.

D · incorrect — Preventive maintenance reduces future risk rather than primarily fixing the stated observed bugs.

Question 64

Criteria that should not be considered when evaluating or assessing requirement analysis?

  • A. Correctness
  • B. Need assessment
  • C. Consistency
  • D. Speed

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE11 · Validate requirements and maintain traceability

Study-guide references

Correct answer: D — Speed

Validation checks correctness, consistency and realism against stakeholder needs. Speed is a property of the future system's performance, not a general criterion for whether the analysis is valid.

Evidence in the complete study note

Correct requirements reflect actual stakeholder needs. Complete requirements address the agreed scope, normal and exceptional behavior. Consistency excludes contradictions. Clarity/unambiguity gives one intended interpretation; feasibility/realism means achievable within constraints. Verifiability means objective evidence can check fulfillment. Replace “fast for most users” with a defined metric, workload and threshold.SE11

Choice by choice

A · incorrect — Explicit requirements-validation property. See PDF p. 68, 79.

B · incorrect — Assessing actual needs supports faithful requirements. See PDF p. 68, 79.

C · incorrect — Explicit absence-of-contradiction property. See PDF p. 68, 79.

D · correct — System response speed is a nonfunctional requirement, not an analysis quality criterion itself. See PDF p. 68, 79.

Question 65

A measurement that defines the level of inter-dependability among modules of a programis__.

  • A. Cohesive
  • B. Coupling
  • C. Design
  • D. Testing

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE22 · Cohesion, coupling, modularity and refactoring

Study-guide references

Correct answer: B — Coupling

Coupling measures dependency between subsystems; coherence/cohesion concerns dependency within one subsystem.

Evidence in the complete study note

Cohesion measures how well elements inside a module serve a related purpose; coupling measures dependency between modules. Seek high cohesion and low coupling. Shared mutable data and knowledge of another module’s internal representation increase coupling. Information hiding exposes stable operations while concealing changeable decisions.SE22

Choice by choice

A · incorrect — Internal relatedness, not inter-module dependency. See PDF p. 120, 120.

B · correct — Exact strength-of-dependencies measure between subsystems. See PDF p. 120, 120.

C · incorrect — An activity that chooses structures, not this measurement. See PDF p. 120, 120.

D · incorrect — An error-detection activity, not this measurement. See PDF p. 120, 120.

Question 66

Which are supported modularization benefits? Select all that apply. Read D as a claim that modularization alone guarantees security.

  • A. Smaller components are difficult to maintain
  • B. Components with high cohesion can be re-used again
  • C. Program can be divided based on functional aspects
  • D. Modularization alone guarantees security.

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE22 · Cohesion, coupling, modularity and refactoring

Study-guide references

Correct answers (select all): B, C — Components with high cohesion can be re-used again; Program can be divided based on functional aspects

Cohesive components with clear interfaces can be reused, and functional decomposition divides responsibilities into manageable modules. Smaller modules can also improve understanding and maintenance, so A reverses the ordinary benefit. Security requires appropriate protection and boundary enforcement; simply dividing code into modules does not guarantee it. Thus B and C are supported structural benefits without the unconditional security promise.

Evidence in the complete study note

Logical cohesion groups similar-category operations, often selected by a flag; temporal cohesion groups operations done at the same time; functional cohesion focuses on one task. Splitting an unrelated three-purpose component improves modularity. If behavior is preserved, the restructuring is refactoring; the words are not mutually exclusive answers. Smaller modules can aid understanding, independent work, reuse and maintenance, but too many interfaces also create complexity.SE22

Choice by choice

A · incorrect — This reverses the ordinary maintenance benefit of manageable cohesive modules.

B · correct — Cohesive components can be reused in suitable contexts.

C · correct — Functional decomposition separates related responsibilities into modules.

D · incorrect — Module boundaries alone do not guarantee security.

Question 67

Which of the following is not element of Requirement Engineering Process?

  • A. Software Requirement Specification
  • B. Feasibility Steady
  • C. Software Requirement Design
  • D. Requirement Gathering

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE08 · Feasibility and levels of requirements

Study-guide references

Correct answer: C — Software Requirement Design

The four listed requirements-engineering activities are feasibility, elicitation/analysis, specification and validation. Software requirement design is not one of them.

Evidence in the complete study note

Business requirements explain why the project exists and its goals. User requirements describe stakeholder needs at a useful high level; system requirements specify detailed services and constraints. The Software Requirements Specification (SRS) organizes the agreed requirements. A natural-language specification communicates with clients while analysis models formalize it for technical discussion; real specifications can also contain diagrams.SE08

Choice by choice

A · incorrect — Specification is explicitly included. See PDF p. 25, 26, 26.

B · incorrect — Feasibility study is explicitly included, despite the typo Steady. See PDF p. 25, 26, 26.

C · correct — Designing the solution is separate from the listed requirements-engineering activities. See PDF p. 25, 26, 26.

D · incorrect — Gathering is part of elicitation/analysis. See PDF p. 25, 26, 26.

Question 68

Which type of test determine if the system meets the entire requirements (functional and nonfunctional)

  • A. Unit Test
  • B. Integration test
  • C. System test
  • D. Acceptance test

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE35 · Testing levels and acceptance

Study-guide references

Correct answer: C — System test

System testing examines the complete system's functional and nonfunctional requirements. Acceptance is a client decision against the agreement, which may also cover requirements but is a more specific acceptance purpose.

Evidence in the complete study note

Acceptance testing supports the customer/user’s acceptance decision against agreed needs and criteria. Alpha typically happens in a controlled developer setting with selected users; beta uses external users in their environments. None of these levels is universally the longest. Unit is a level, while white-box is a technique; a unit can be tested using black-box cases too.SE35

Choice by choice

A · incorrect — Isolates objects/components. See PDF p. 144, 147, 145.

B · incorrect — Finds faults among combined components. See PDF p. 144, 147, 145.

C · correct — Explicit complete-system functional/nonfunctional scope. See PDF p. 144, 147, 145.

D · incorrect — Client agreement testing, rather than the general full-system test scope asked. See PDF p. 144, 147, 145.

Question 69

All of the following are required to develop an effective test except:

  • A. Detailed understanding of the system
  • B. Application and solution domain knowledge
  • C. Knowledge of the testing techniques
  • D. Skill to specific programming language

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE36 · Test types, regression and exploratory work

Study-guide references

Correct answer: D — Skill to specific programming language

Black-box equivalence tests can be derived from inputs and expected behavior without writing in a particular implementation language. Domain/system knowledge and testing methods remain relevant.

Evidence in the complete study note

Functional tests check required behavior against the SRS and acceptance criteria. Performance tests assess speed, throughput and resources under a specified workload; load uses expected demands and stress exceeds normal limits. Usability, security, compatibility and reliability tests target their respective qualities. “Normal operating conditions” alone does not distinguish functional from performance testing.SE36

Choice by choice

A · incorrect — Needed to choose meaningful cases and expected results. See PDF p. 149, 149.

B · incorrect — Needed to interpret required behavior. See PDF p. 149, 149.

C · incorrect — Needed to partition inputs or choose boundaries/paths appropriately. See PDF p. 149, 149.

D · correct — Not universally necessary for behavior-based test design; source-language knowledge applies particularly to white-box work. See PDF p. 149, 149.

Question 70

Use case description commonly contain:

  • A. Trigger, associations, guarantee.
  • B. Precondition, generalizations, main scenario.
  • C. Precondition, main scenario, alternative scenarios
  • D. None of the above

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE15 · Write a complete use case with alternatives

Study-guide references

Correct answer: C — Precondition, main scenario, alternative scenarios

A use-case description includes entry conditions, the numbered normal flow and exceptional cases.

Evidence in the complete study note

Example: Submit Incident. Precondition: officer authenticated. 1 Officer supplies location and description. 2 System validates details. 3 System records the incident. 4 System returns its ID. Alternative 2a: location missing → report the problem and request correction; save nothing. Success postcondition: incident and ID persist; failure guarantee: no partial record. An alternate flow is a conditional variation; an exception flow handles a failure. Preconditions hold before entry, while a trigger starts the use case.SE15

Choice by choice

A · incorrect — Trigger/associations/guarantee are not its stated three-part summary. See PDF p. 48.

B · incorrect — Generalization is a relationship, not one of these template fields. See PDF p. 48.

C · correct — Matches preconditions and normal/exceptional flow content. See PDF p. 48.

D · incorrect — A supported summary is offered. See PDF p. 48.

Question 71

Aggregation, composition, generalization. Which document is created by a system analyst after the requirements are collected from different stakeholders?

  • A. Requirement gathering
  • B. Software Requirement specification
  • C. Software Requirement testing
  • D. Software Requirement validation

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE08 · Feasibility and levels of requirements

Study-guide references

Correct answer: B — Software Requirement specification

After collection, requirements are organized into the SRS. The opening aggregation/composition/generalization fragment does not alter the requested document.

Evidence in the complete study note

Business requirements explain why the project exists and its goals. User requirements describe stakeholder needs at a useful high level; system requirements specify detailed services and constraints. The Software Requirements Specification (SRS) organizes the agreed requirements. A natural-language specification communicates with clients while analysis models formalize it for technical discussion; real specifications can also contain diagrams.SE08

Choice by choice

A · incorrect — A gathering activity, not the resulting specification document. See PDF p. 26, 83.

B · correct — The defined organized requirements document. See PDF p. 26, 83.

C · incorrect — Testing is an activity rather than this document. See PDF p. 26, 83.

D · incorrect — Validation checks a specification rather than naming its document. See PDF p. 26, 83.

Question 72

________is a process which translate system specification into a formal or semi formal model.

  • A. Implementation
  • B. Elicitation
  • C. Analysis
  • D. Design

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE13 · From scenarios to analysis objects

Study-guide references

Correct answer: C — Analysis

Analysis structures and formalizes the natural-language system specification into a formal or semiformal analysis model.

Evidence in the complete study note

A scenario is one concrete execution; a use case abstracts the related successful and alternative scenarios. Analysis integrates functional (use cases/scenarios), structural/object (classes) and dynamic (states/interactions) models. Entity objects represent domain information such as Incident; boundary objects mediate interaction, such as ReportForm; control objects coordinate a use case. A UI form is normally boundary, not entity.SE13

Choice by choice

A · incorrect — Converts design to executable code. See PDF p. 100, 62.

B · incorrect — Produces the initial specification with stakeholders. See PDF p. 100, 62.

C · correct — Exact formalization activity described. See PDF p. 100, 62.

D · incorrect — Derives internal solution structure after analysis. See PDF p. 100, 62.

Question 73

Which maintenance risk can arise from poorly designed objects with complex or poorly separated responsibilities?

  • A. Easier maintenance
  • B. Objects may be understood as stand-alone entities
  • C. Objects are potentially reusable components
  • D. Poorly designed objects can be difficult to maintain.

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE22 · Cohesion, coupling, modularity and refactoring

SE01 · Software engineering, processes and work products

Study-guide references

Correct answer: D — Poorly designed objects can be difficult to maintain.

Encapsulation and reuse can ease maintenance when objects have clear responsibilities and interfaces. Poor object design can still be complex, so its objects may become difficult to maintain. That conditional risk is D. The other choices describe potential advantages of well-designed objects rather than disadvantages arising from the stated poor design. Object orientation alone does not guarantee either maintenance outcome.

Evidence in the complete study note

Cohesion measures how well elements inside a module serve a related purpose; coupling measures dependency between modules. Seek high cohesion and low coupling. Shared mutable data and knowledge of another module’s internal representation increase coupling. Information hiding exposes stable operations while concealing changeable decisions.SE22
Procedural decomposition organizes functions; object oriented decomposition organizes objects with state and behavior. Either can use iterative or sequential development. OOP does not automatically shorten every project. Reuse, encapsulation and consistent models can reduce duplication and ease change; poor object design can still be complex. Functional programming emphasizes function evaluation and controlled side effects; event-driven programs react to events.SE01
Splitting an unrelated three-purpose component improves modularity. If behavior is preserved, the restructuring is refactoring; the words are not mutually exclusive answers.SE22

Choice by choice

A · incorrect — Easier maintenance is a potential benefit, not this risk.

B · incorrect — Understanding encapsulated objects through their interfaces is a potential benefit.

C · incorrect — Potential reuse is an advantage of suitable design.

D · correct — Poorly designed complex objects can be difficult to maintain.

Question 74

In a class diagram, a filled diamond is at Car’s end of its Engine association. In this model an Engine remains owned by its Car for its entire lifetime, with no detachment or transfer. What does the relationship imply?

  • A. Car uses Engine temporarily
  • B. Engine can exist independently of the Car
  • C. Engine is part of Car and cannot exist independently under the stated lifetime policy.
  • D. Car inherits from Engine

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE18 · Association, aggregation, composition and generalization

Study-guide references

Correct answer: C — Engine is part of Car and cannot exist independently under the stated lifetime policy.

The filled diamond at Car denotes composition: Car is the whole and Engine is its strongly owned part. Composition destroys parts that remain owned when the whole is destroyed. Because this model forbids detachment or transfer, the Engine’s lifetime cannot continue independently of its Car. Temporary use would be a dependency, and inheritance would use a hollow generalization triangle instead.

Evidence in the complete study note

Composition uses a filled diamond at the whole end and strong ownership: a part is in at most one composite at a time, and parts still owned are destroyed with that composite. Parts may be detached/transferred under a defined model. Thus “cannot ever exist independently” is an oversimplification. For Car composing Engine, the diamond belongs beside Car; saying it points to Engine is imprecise. The Car–Engine example describes composition.SE18

Choice by choice

A · incorrect — Temporary use is a dependency, not composition.

B · incorrect — The stipulated permanent ownership excludes an independent Engine lifetime.

C · correct — Engine is the owned part and cannot outlive Car under the stated policy.

D · incorrect — Inheritance uses a hollow triangle rather than a filled diamond.

Question 75

From the following statement which one is disadvantage of waterfall model?

  • A. model is simple and easy to understand and use
  • B. It is easy manage due to the rigidity of the model
  • C. . Not suitable for projects where requirements are at a moderate to high risk of changing
  • D. In this model phases are processed and completed one at a time

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE03 · Waterfall and the V-model

Study-guide references

Correct answer: C — . Not suitable for projects where requirements are at a moderate to high risk of changing

Waterfall requires early stable requirements and has difficulty responding to change, so moderate-to-high change risk is its documented disadvantage.

Evidence in the complete study note

Classical waterfall separates planned phases with reviewed deliverables. It fits well-understood, stable requirements and familiar technology; late feedback makes changes costly. It does not make change physically impossible: real projects revisit work under control, and modified waterfall explicitly includes feedback. Rigidity offers milestone visibility but can freeze incorrect assumptions.SE03

Choice by choice

A · incorrect — Listed as an advantage. See PDF p. 20.

B · incorrect — Listed as an advantage from distinct deliverables/reviews. See PDF p. 20.

C · correct — Directly matches the disadvantage on PDF p.21. See PDF p. 20.

D · incorrect — Sequential non-overlap is a structural feature, not the stated change-risk disadvantage. See PDF p. 20.

Question 76

Which statement specifically constrains response-time performance under a stated workload?

  • A. The system allow user to generate PDF report.
  • B. The system respond to user's request within 2 second under normal load
  • C. . The system allow user to store data on relational database
  • D. The system allow user to submit emergency report

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE10 · Nonfunctional qualities and measurable constraints

Study-guide references

Correct answer: B — The system respond to user's request within 2 second under normal load

The two-second response obligation bounds the speed of a service under the stated load, so it is a performance requirement. Generating a PDF and submitting an emergency report describe services the system provides. The database clause describes storage behavior together with an implementation choice; it does not impose a response-time threshold. The explicit performance scope removes the broader taxonomy overlap between nonfunctional requirements and technology constraints.

Evidence in the complete study note

Nonfunctional requirements include quality attributes and constraints. Performance concerns response time, throughput and resource use; reliability concerns failure-free service; availability concerns being ready for use; usability concerns task success and ease of learning. Security concerns protection; compatibility concerns cooperating environments; portability concerns moving environments; maintainability/supportability concern change, diagnosis and evolution.SE10
“Search responds within two seconds under 100 concurrent users” is measurable performance. “New users finish checkout within one minute without help” is usability. “Use Java” is a technology/pseudo-requirement, often separately classified as a system constraint. Dependability includes reliability, safety and robustness; portability is not its usual central category. Performance degradation at peak load primarily concerns performance, not automatically reliability.SE10

Choice by choice

A · incorrect — Report generation specifies a service, not its response-time limit.

B · correct — A two-second response bound under normal load is a quantitative speed target.

C · incorrect — This specifies storage behavior and a database technology, without a timing bound.

D · incorrect — Submitting an emergency report specifies a function rather than its speed.

Question 77

In object design, what does the contract typically includes?

  • A. The class diagram and sequence diagram
  • B. Project budget and timeline
  • C. Invariants, preconditions, post conditions
  • D. The use case names and actors role

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE25 · Design principles and operation contracts

Study-guide references

Correct answer: C — Invariants, preconditions, post conditions

Contracts establish class-wide invariants and caller/callee obligations before and after an operation.

Evidence in the complete study note

A contract states preconditions, postconditions and invariants. For withdraw(amount): require amount>0 and amount<=balance; ensure balance=oldBalance-amount; preserve balance>=0. Validation checks inputs; implementation enforces the transition. A complete feature needs both UI/API and persisted behavior, not only a diagram.SE25

Choice by choice

A · incorrect — Diagrams can document a design but are not the contract constraint categories. See PDF p. 136.

B · incorrect — Project planning terms, not class contracts. See PDF p. 136.

C · correct — Exactly the three contract constraint types. See PDF p. 136.

D · incorrect — Use-case identifiers and roles do not specify class invariants and operation obligations. See PDF p. 136.

Question 78

Which one of the following UML building block that defines the static part of the model and represents physical and conceptual elements?

  • A. Structural things
  • B. Behavioral things
  • C. ¢. An notational things
  • D. Grouping things

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE17 · Class diagrams, visibility and multiplicity

SE-S03 · Modeling categories and data diagrams

Study-guide references

Correct answer: A — Structural things

Structural things explicitly define the static model and physical/conceptual elements.

Evidence in the complete study note

A class box lists name, attributes and operations; + public, - private, # protected and ~ package indicate visibility. A class diagram shows static types and relationships, while an object diagram shows particular instances/links. UML is maintained and standardized by OMG; it is a modeling language, not a lifecycle process. Structural things describe conceptual or physical structural elements.SE17
In the course’s UML building-block terminology, structural things describe static conceptual or physical elements. Behavioral things describe dynamic interactions and state behavior. Grouping things organize model elements into packages. Annotational things attach explanatory remarks or constraints, usually as notes.SE-S03

Choice by choice

A · correct — Matches the module verbatim. See PDF p. 45, 45, 46.

B · incorrect — Behavioral things are dynamic. See PDF p. 45, 45, 46.

C · incorrect — Annotational things capture notes and remarks. See PDF p. 45, 45, 46.

D · incorrect — Grouping things organize elements into packages. See PDF p. 45, 45, 46.

Question 79

After deploying a new software system, users reports that the system slows during peak hour. Which software quality attribute primarily affected?

  • A. Maintainability
  • B. Performance
  • C. Reliability
  • D. Usability

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE10 · Nonfunctional qualities and measurable constraints

Study-guide references

Correct answer: B — Performance

Slow response at peak load concerns responsiveness and concurrency/load constraints, hence performance.

Evidence in the complete study note

“Search responds within two seconds under 100 concurrent users” is measurable performance. “New users finish checkout within one minute without help” is usability. “Use Java” is a technology/pseudo-requirement, often separately classified as a system constraint. Dependability includes reliability, safety and robustness; portability is not its usual central category. Performance degradation at peak load primarily concerns performance, not automatically reliability.SE10

Choice by choice

A · incorrect — Concerns cost/ease of modifying the system. See PDF p. 79, 66.

B · correct — Directly affected response-speed/load quality. See PDF p. 79, 66.

C · incorrect — Reliability concerns conformance/failures; slow service could violate requirements, but performance is the specific attribute. See PDF p. 79, 66.

D · incorrect — Usability concerns ease of learning/using rather than primarily load-dependent response speed. See PDF p. 79, 66.

Question 80

Which choice most completely lists candidate heuristics for grouping objects into subsystems? Treat them as starting guidance, not mandatory boundaries.

  • A. Assign objects identified in one use case into the same subsystem.
  • B. Create a dedicated subsystem for objects used for moving data among subsystems.
  • C. Minimize the number of associations crossing subsystem boundaries.
  • D. All of the above

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE21 · Design and subsystem decomposition

Study-guide references

Correct answer: D — All of the above

SE21 recommends grouping related functionality, minimizing cross-subsystem associations and isolating communication infrastructure where useful. Grouping objects serving one use case can be a starting heuristic, though workflows do not dictate every boundary. B and C directly support isolation and low coupling. Since the question asks what can be a heuristic, the inclusive option is appropriate.

Evidence in the complete study note

System design turns the analysis model into architecture: design goals, subsystem responsibilities, dependencies, hardware mapping, data management, access control, control flow and startup/shutdown/error policies. Detail/object design refines APIs, parameter/return types, exceptions, component choices and algorithms. A subsystem is a manageable logical collection with services and an interface; it need not be a physical replaceable artifact.SE21
Group closely related objects and functionality, minimize associations crossing boundaries, and isolate communication infrastructure where useful.SE21

Choice by choice

A · incorrect — True as one component, but incomplete as the requested full selection. Objects collaborating on one use case can be grouped as a starting heuristic, subject to other design constraints.

B · incorrect — True as one component, but incomplete as the requested full selection. Communication infrastructure can be isolated in a dedicated subsystem when useful.

C · incorrect — True as one component, but incomplete as the requested full selection. Reducing cross-boundary associations reduces coupling between subsystems.

D · correct — All three can guide decomposition, provided use-case grouping is not treated as an absolute rule.

Question 81

Which statement is false about a logical software subsystem? Interpret complexity reduction as managing solution-design complexity, not changing the inherent application domain.

  • A. A physical and replaceable part of the system.
  • B. It helps manage the complexity of the solution design.
  • C. Decompose a system into simpler parts.
  • D. Well-defined interfaces that encapsulate the state and behavior of its contained classes.

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE21 · Design and subsystem decomposition

Study-guide references

Correct answer: A — A physical and replaceable part of the system.

A subsystem is a manageable logical collection of responsibilities with services and an interface. It need not be a physical replaceable artifact, so A is false as a definition. Decomposing the designed solution into simpler groups helps manage complexity, and defined interfaces can encapsulate implementation state and behavior. These design benefits concern the solution organization rather than reducing the inherent complexity of its problem domain.

Evidence in the complete study note

Group closely related objects and functionality, minimize associations crossing boundaries, and isolate communication infrastructure where useful. User workflows inform decomposition but do not alone dictate the internal structure. Analysis describes domain needs; subsystem decomposition is principally a design result. Architecture documentation supports communication and records major decisions, not every source-level execution step.SE21
A subsystem is a manageable logical collection with services and an interface; it need not be a physical replaceable artifact.SE21

Choice by choice

A · correct — A logical subsystem need not be physical or independently replaceable.

B · incorrect — Managing solution-design complexity is a supported decomposition benefit.

C · incorrect — Decomposition groups the system into simpler responsibilities.

D · incorrect — Defined interfaces encapsulate contained implementation details.

Question 82

Which of the following is an example of Usability requirements?

  • A. A new user shall complete the main interface task within one minute without help.
  • B. Robustness
  • C. Mean time to failure
  • D. Adaptability

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE10 · Nonfunctional qualities and measurable constraints

SE-S07 · Scalability and robustness are different qualities

Study-guide references

Correct answer: A — A new user shall complete the main interface task within one minute without help.

A usability requirement states an observable target for successful and learnable use. Requiring a new user to finish a main interface task without help within one minute gives a task, user context, success condition and threshold. Robustness concerns dependable behavior under adverse conditions, mean time to failure is a reliability measure, and adaptability concerns change. Merely naming a user interface would not itself specify an obligation, so the option supplies a genuine requirement.

Evidence in the complete study note

Performance concerns response time, throughput and resource use; reliability concerns failure-free service; availability concerns being ready for use; usability concerns task success and ease of learning.SE10
“New users finish checkout within one minute without help” is usability.SE10
Robustness concerns reliable operation across varied or difficult operating conditions and controlled failure outside the supported range. It is different from usability, which concerns people successfully learning and carrying out tasks. Improving an interface’s task success does not by itself establish robustness under adverse conditions.SE-S07

Choice by choice

A · correct — The task-success and unaided-learning target is a measurable usability obligation.

B · incorrect — Robustness concerns dependable behavior under adverse conditions rather than ease of learning a task.

C · incorrect — Mean time to failure measures reliability rather than user task ease.

D · incorrect — Adaptability concerns accommodating change rather than the stated user task target.

Question 83

Which one of the following is a Nonfunctional requirement?

  • A. Admin can upload photos
  • B. Admin can search book
  • C. Librarian can delete student
  • D. The system delivers the search items within 2 seconds

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE10 · Nonfunctional qualities and measurable constraints

Study-guide references

Correct answer: D — The system delivers the search items within 2 seconds

The two-second limit constrains how quickly the search service responds; the others specify permitted operations.

Evidence in the complete study note

Nonfunctional requirements include quality attributes and constraints. Performance concerns response time, throughput and resource use; reliability concerns failure-free service; availability concerns being ready for use; usability concerns task success and ease of learning. Security concerns protection; compatibility concerns cooperating environments; portability concerns moving environments; maintainability/supportability concern change, diagnosis and evolution.SE10

Choice by choice

A · incorrect — Uploading is a service. See PDF p. 65, 66.

B · incorrect — Searching is a service. See PDF p. 65, 66.

C · incorrect — Deletion is a service. See PDF p. 65, 66.

D · correct — Quantitative response-time requirement. See PDF p. 65, 66.

Question 84

Which of the following is false about functional requirement?

  • A. Requirements should complete
  • B. Requirement should be accurate as possible.
  • C. Each requirement should state a clear, independently verifiable obligation.
  • D. A requirement can be interpreted in many exclusive ways.

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE11 · Validate requirements and maintain traceability

SE09 · Functional requirements include prohibited behavior

Study-guide references

Correct answer: D — A requirement can be interpreted in many exclusive ways.

Requirements should accurately reflect stakeholder needs, cover the agreed scope and express clear, verifiable obligations. Unambiguity requires one intended interpretation; mutually exclusive readings violate that property. The revised third option states the useful single-obligation writing rule without claiming that duplicate requirements can never be consolidated. Thus the multiple-interpretation option is the single false quality claim, while completeness, accuracy and clarity remain valid goals.

Evidence in the complete study note

Correct requirements reflect actual stakeholder needs. Complete requirements address the agreed scope, normal and exceptional behavior. Consistency excludes contradictions. Clarity/unambiguity gives one intended interpretation; feasibility/realism means achievable within constraints. Verifiability means objective evidence can check fulfillment. Replace “fast for most users” with a defined metric, workload and threshold.SE11
Write one clear obligation with an actor/trigger, action and observable result.SE09

Choice by choice

A · incorrect — Completeness requires coverage of the agreed behavior and exceptional cases.

B · incorrect — Accuracy requires requirements to reflect the actual stakeholder needs.

C · incorrect — A clear independently verifiable obligation supports precise specification.

D · correct — Mutually exclusive readings violate the unambiguity requirement.

Question 85

Which of the following is not true about requirement elicitation?

  • A. Errors introduced during requirements elicitation are expensive to correct.
  • B. Define the purpose of the system by collaboration of the client and developers.
  • C. Requirements elicitation is less challenging than Analysis.
  • D. Requirements specification is the result of requirement elicitation.

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE11 · Validate requirements and maintain traceability

Study-guide references

Correct answer: C — Requirements elicitation is less challenging than Analysis.

Elicitation requires stakeholder agreement and accurate problem understanding; analysis formalizes it. Elicitation is not inherently less challenging, and postponed decisions can be costly.

Evidence in the complete study note

Correct requirements reflect actual stakeholder needs. Complete requirements address the agreed scope, normal and exceptional behavior. Consistency excludes contradictions. Clarity/unambiguity gives one intended interpretation; feasibility/realism means achievable within constraints. Verifiability means objective evidence can check fulfillment. Replace “fast for most users” with a defined metric, workload and threshold.SE11

Choice by choice

A · incorrect — Late correction raises cost, consistent with identifying issues early. See PDF p. 62, 100.

B · incorrect — Matches collaborative purpose definition. See PDF p. 62, 100.

C · correct — The claimed easier-than-analysis ranking is unsupported and contrary to the described difficulty. See PDF p. 62, 100.

D · incorrect — The system specification is its explicit output. See PDF p. 62, 100.

Question 86

Which named approach develops an experimental version specifically to explore unclear requirements or feasibility, and can therefore serve both as a development approach and an elicitation technique?

  • A. Spiral process model
  • B. Waterfall process model
  • C. Prototype process model
  • D. Agile process model

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE07 · Prototypes, RAD and reuse-oriented development

SE06 · Spiral development and risk

Study-guide references

Correct answer: C — Prototype process model

Prototyping uses an early experimental representation or working version to discover requirements, usability needs or technical feasibility. It can be organized as a development approach and also used within elicitation. Spiral may contain a prototype to reduce risk, but risk-driven cycles define spiral itself. Waterfall names phased development, while Agile names a broader adaptive approach. The question asks the named experimentation technique that directly serves both purposes.

Evidence in the complete study note

A prototype explores requirements, usability or technical feasibility. A throwaway prototype is discarded after learning; an evolutionary prototype is deliberately refined toward production. A quick prototype may omit robustness, security or architecture, so do not deploy it unchanged without evaluation. Coding may occur during prototyping even if a diagram labels that activity construction rather than coding.SE07
Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06

Choice by choice

A · incorrect — Spiral may employ prototypes but is itself defined by risk-driven cycles.

B · incorrect — Waterfall is a phased lifecycle rather than the experimentation technique described.

C · correct — Prototyping directly explores requirements or feasibility using an experimental version.

D · incorrect — Agile is a broad adaptive approach and can use several elicitation techniques.

Question 87

What is the base for functional testing?

  • A. We have to refer to the system design document
  • B. We have to refer to the system requirement specification document
  • C. We have to refer to user manual if any exists
  • D. A and B

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE36 · Test types, regression and exploratory work

Study-guide references

Correct answer: B — We have to refer to the system requirement specification document

Functional testing tests requirements from the RAD and, if available, the user manual. Of the options, the requirements specification is the primary basis; the user manual is supplementary.

Evidence in the complete study note

Black-box techniques derive cases from specified behavior; white-box techniques derive them from internal structure; grey-box uses partial internal knowledge. Regression testing checks for unintended effects after change; confirmation testing checks the particular defect repair. Exploratory testing combines learning, design and execution and is experience based. Manual/automated describe execution support, not a compulsory black-/white-box classification.SE36

Choice by choice

A · incorrect — Design goals support performance tests and architecture supports integration, rather than being the primary functional oracle. See PDF p. 144, 83, 130.

B · correct — The requirement document defines what behavior to test. See PDF p. 144, 83, 130.

C · incorrect — A manual can supplement functional requirements, but is not the primary complete basis. See PDF p. 144, 83, 130.

D · incorrect — Adding design as an equal required functional basis overstates the cited rule. See PDF p. 144, 83, 130.

Question 88

Evaluate statements A–C about subsystem decomposition. Which is false? Select D if none is false.

  • A. In designing the desirable effect is low coupling and high cohesion in sub system decomposition
  • B. Cohesion refers to the dependency of classes with in subsystem
  • C. Coupling refers to the dependency between sub systems
  • D. None of statements A–C is false.

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE22 · Cohesion, coupling, modularity and refactoring

Study-guide references

Correct answer: D — None of statements A–C is false.

Low coupling limits dependencies between subsystems, while high cohesion keeps related responsibilities together inside each subsystem. The first statement recommends this combination, the second identifies cohesion within the subsystem, and the third identifies coupling across subsystems. All three substantive statements are therefore true. The final alternative is explicitly the response for finding no false statement among those three, rather than a self-referential assertion about all choices.

Evidence in the complete study note

Cohesion measures how well elements inside a module serve a related purpose; coupling measures dependency between modules. Seek high cohesion and low coupling. Shared mutable data and knowledge of another module’s internal representation increase coupling. Information hiding exposes stable operations while concealing changeable decisions.SE22

Choice by choice

A · incorrect — Low coupling and high cohesion are the stated decomposition goals.

B · incorrect — Cohesion concerns relatedness and dependencies among elements within a subsystem.

C · incorrect — Coupling concerns dependencies between subsystems.

D · correct — None of the substantive statements A–C is false, so this is the required response.

Question 89

Which offered asset is inherently excluded from reuse in a software product line?

  • A. Test cases
  • B. Requirement
  • C. Architecture
  • D. None of A–C; all three can be reusable product-line assets.

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE07 · Prototypes, RAD and reuse-oriented development

Study-guide references

Correct answer: D — None of A–C; all three can be reusable product-line assets.

Product-line assets can include requirements, architecture, components and tests. Consequently test cases, requirements and architecture are all potentially reusable, although each must be evaluated for fit in a particular product. None of A–C is inherently excluded by its asset type. Option D expresses this conclusion directly rather than contradicting the negative stem with an undefined all-choices assertion.

Evidence in the complete study note

RAD uses rapid construction, timeboxing, user participation and often reusable components; it requires available users and skilled designers/developers. Reuse-oriented development searches components, evaluates fit, may adjust requirements, designs around interfaces and builds missing parts. Product-line assets may include requirements, architecture, components and tests; all are potentially reusable.SE07

Choice by choice

A · incorrect — Test cases can be reusable product-line assets.

B · incorrect — Requirements can be shared across related products.

C · incorrect — Architecture can be a reusable product-line asset.

D · correct — None of A–C is inherently excluded; all can be reused.

Question 90

A software design model states exact withdraw preconditions and balance equations but omits physical implementation detail. Compare it with an informal mathematical sketch that leaves those constraints unspecified and a fully detailed engine drawing. Which statement is FALSE for these particular models?

  • A. This software model is less precise than the specified mathematical sketch.
  • B. This software model is more abstract than the fully detailed engine drawing.
  • C. A main role of this model is to represent the software designer’s ideas.
  • D. None of A–C is false.

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE43 · Design choices, evidence and economical improvement

SE25 · Design principles and operation contracts

SE23 · Layers, tiers and architecture views

Study-guide references

Correct answer: A — This software model is less precise than the specified mathematical sketch.

The software model states exact preconditions and balance equations, whereas the informal mathematical sketch omits those constraints. It is therefore not less precise in the stated comparison, making A false. Omitting implementation detail makes it more abstract than the specified detailed engine drawing, and representing design ideas remains a legitimate purpose. These are scenario-specific judgments rather than universal rankings of all software and mathematical models.

Evidence in the complete study note

Choose designs by their effect on stated goals. Fine-grained self-contained components, separation of producers/consumers and limited shared mutable data often improve maintainability. Trade-offs remain: interfaces can add latency, isolation can complicate transactions, and global state can simplify one operation while coupling many others. Prefer measurable quality scenarios to counting components alone.SE43
A contract states preconditions, postconditions and invariants. For withdraw(amount): require amount>0 and amount<=balance; ensure balance=oldBalance-amount; preserve balance>=0. Validation checks inputs; implementation enforces the transition. A complete feature needs both UI/API and persisted behavior, not only a diagram.SE25
A layer is a logical abstraction level; a tier is a deployment separation. A closed layered architecture permits calls only to the immediately lower layer; an open one permits approved skipping. For top-to-bottom A,B,C,D, A→B obeys closed layering, A→C skips, and lower-to-upper calls violate the simple dependency rule unless explicitly mediated by a defined mechanism.SE23
A structure is the elements/relations themselves; a view represents selected aspects.SE23

Choice by choice

A · correct — Its exact constraints make the stated less-precise comparison false.

B · incorrect — The software model omits implementation detail retained in the detailed drawing.

C · incorrect — A design model can represent the designer’s ideas and decisions.

D · incorrect — A is false, so the no-false-statements alternative is wrong.

Question 91

Which among the following designing models show sequence functional transformation done on inputs into outputs?

  • A. ER diagrams
  • B. DFD diagrams
  • C. Component diagrams
  • D. None of the choices are correct

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE20 · Activity, state and data-flow models

SE-S03 · Modeling categories and data diagrams

Study-guide references

Correct answer: B — Data-flow diagrams.

SE20 defines a DFD through data flows, stores and transformations from inputs to outputs. That matches the functional-transformation focus in the stem. An ER diagram focuses on domain data relationships, while a component diagram describes software components and dependencies. A DFD need not show detailed control timing merely because it depicts connected transformations.

Evidence in the complete study note

Choose a sequence diagram for message order between participants, a state machine for event-dependent state changes, and activity for workflow. Both sequence and state diagrams describe behavior over time. State machines are useful for objects with significant states, whether entity or control. A DFD shows data stores/flows and transformations from inputs to outputs; it is not a UML diagram.SE20
An entity–relationship diagram models entity types, their attributes and the relationships between them, commonly for data design. Its focus differs from a use-case diagram of external roles and goals, a class diagram of classes and their features, or a deployment diagram mapping artifacts to execution nodes.SE-S03

Choice by choice

A · incorrect — ER diagrams describe entities and relationships rather than transformations of input data into outputs.

B · correct — DFDs depict data flows and the processes that transform inputs into outputs.

C · incorrect — Component diagrams describe component interfaces and dependencies rather than this data-transformation view.

D · incorrect — DFD is listed and directly matches the functional-transformation description.

Question 92

Which of the following is step in software development life cycle that tell us if developing a software makes sense for the current company situation or not.

  • A. Requirement analysis
  • B. Feasibility analysis
  • C. Designing phase
  • D. Requirement elicitation

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE08 · Feasibility and levels of requirements

Study-guide references

Correct answer: B — Feasibility analysis

Feasibility assesses technological practicality, budget and business cost-effectiveness before deciding to proceed with detailed analysis.

Evidence in the complete study note

Feasibility asks whether a proposal is worth doing and can be delivered within technical, economic, operational and schedule constraints. Examine existing limitations, organizational impacts, benefits, cost, available skills and integration risk. System analysis studies the problem and needed behavior in more detail; the activities inform each other.SE08

Choice by choice

A · incorrect — Further analysis follows a feasibility decision. See PDF p. 25, 26.

B · correct — Direct viability/go-ahead decision. See PDF p. 25, 26.

C · incorrect — Derives a solution after requirements are understood. See PDF p. 25, 26.

D · incorrect — Collects stakeholder needs rather than deciding whether the investment is viable. See PDF p. 25, 26.

Question 93

Which choice gives the most complete supported comparison of object-oriented model continuity and transitions between different development models?

  • A. Object-oriented development can use a consistent vocabulary of objects and classes across analysis and design.
  • B. Reuse and consistent models in object-oriented development can reduce development effort and duration on suitable projects.
  • C. Moving between different representations in a traditional phased approach can add translation complexity and errors.
  • D. All statements A–C are correct.

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE01 · Software engineering, processes and work products

SE-S02 · Objects, shared models and specialization

Study-guide references

Correct answer: D — All statements A–C are correct.

A consistent object vocabulary across development stages can reduce errors from translating between unrelated models. Reuse and continuity can also reduce effort on suitable projects, while transitions between different representations can add complexity. These are potential benefits and risks, not guarantees that every OO project is shorter or every traditional project is worse. With those qualifications, all three substantive statements are supported, making their aggregate the most complete answer.

Evidence in the complete study note

Software engineering applies systematic methods to development, operation and maintenance. A software product includes executable code and relevant requirements, designs, test assets, configuration and user documentation. A process defines activities, ordering, roles, products and entry/exit conditions. Its four broad activities are specification, design/implementation, validation and evolution.SE01
Procedural decomposition organizes functions; object oriented decomposition organizes objects with state and behavior. Either can use iterative or sequential development. OOP does not automatically shorten every project. Reuse, encapsulation and consistent models can reduce duplication and ease change; poor object design can still be complex. Functional programming emphasizes function evaluation and controlled side effects; event-driven programs react to events.SE01
An object-oriented approach can use a consistent vocabulary of objects, classes and relationships across analysis, design and implementation. Models are refined for different purposes rather than being identical artifacts. This continuity can reduce translation errors and effort; reusable classes can shorten suitable projects, but neither shorter duration nor good design is guaranteed.SE-S02

Choice by choice

A · incorrect — True but incomplete alone: a consistent object/class vocabulary can connect analysis and design.

B · incorrect — True but incomplete alone: reuse and model continuity can reduce effort, without guaranteeing it.

C · incorrect — True but incomplete alone: translation between different representations can add complexity or errors.

D · correct — All three qualified statements hold, so the aggregate is the complete selection.

Question 94

Which of the following process model is concerned with how changes are incorporated in software?

  • A. Configuration management process
  • B. Change management process
  • C. Inspection management process
  • D. Project management process

Separate artifact history and controlled changes from scheduling, collaboration benefits and automated execution.

Study-guide sections

SE33 · Configuration, change control and version control

Study-guide references

Correct answer: B — Change management process.

SE33 assigns handling change requests, impact assessment, decisions, implementation and validation to change management. Configuration management coordinates versions and baselines of affected artifacts, which supports that work but is a different focus. Inspection and general project management also contribute, yet B specifically names how proposed software changes are evaluated and incorporated.

Evidence in the complete study note

Change management handles request, impact assessment, decision/prioritization, implementation and validation; configuration management keeps all affected versions consistent. Distributed Git gives each clone local history and supports independent branches followed by merging; it does not eliminate merge conflicts or approvals. Plan test configuration management early and apply it throughout testing, not at just one exclusive phase.SE33

Choice by choice

A · incorrect — Configuration management maintains controlled versions and baselines rather than primarily deciding and incorporating requested changes.

B · correct — Change management evaluates, approves/prioritizes, implements and validates proposed changes.

C · incorrect — Inspection evaluates artifacts rather than defining the complete change-handling process.

D · incorrect — Project management is broader than the specific process for handling software change requests.

Question 95

After a maintenance change request has been received, which is the earliest listed technical activity before release planning and implementation?

  • A. Release planning
  • B. Change management
  • C. Impact analysis
  • D. Testing

Classify the motive for the change before its implementation: repair, environment, useful capability or reduced future risk.

Study-guide sections

SE40 · Maintenance and software evolution

Study-guide references

Correct answer: C — Impact analysis

A typical evolution sequence is change request, impact analysis, release planning, implementation/testing and release. Once the request has arrived, impact analysis is the earliest listed technical step, assessing consequences before scheduling and implementation. Change management names the broader handling process rather than that next step. Release planning and testing occur later, so neither starts the specified post-request technical sequence.

Evidence in the complete study note

A typical evolution sequence is change request→impact analysis→release planning→implementation/testing→release. Among a list lacking the request step, impact analysis may be the earliest listed technical activity. Major restructuring is reengineering; if the architecture itself changes, architectural transformation is the more specific description. Markets, technology, stakeholders and funding can all change scope or priorities.SE40

Choice by choice

A · incorrect — Release planning follows impact analysis.

B · incorrect — Change management is the overarching process.

C · correct — Impact analysis is the first listed technical activity after the request.

D · incorrect — Testing follows analysis, planning and implementation.

Question 96

A takes 5 days. B takes 3 days and C takes 4 days; both depend only on A and may run in parallel with sufficient resources. The project finishes when all three complete. What is its earliest duration?

  • A. 3 days
  • B. 4 days
  • C. 5 days
  • D. 9 days

Write out the supplied quantities and dependency constraints. Compute and compare values under the stated metric, finish condition and assumptions.

Study-guide sections

SE29 · Critical path: forward and backward passes

Study-guide references

Correct answer: D — 9 days

A completes at day five. B and C then start together, finishing at days eight and nine respectively. The project must wait for both required tasks, so its earliest finish is 5+max(3,4)=9 days. Adding all durations would ignore the permitted parallelism, while using eight days would count only the shorter A–B path and leave C incomplete.

Evidence in the complete study note

If A takes 5 days and B=3,C=4 both follow A, project duration is 5+max(3,4)=9 days. B finishes at 8, but the project waits for C at 9. If paths B5+C6 and D8+E3 share a zero-duration start/end, both total 11; there are two critical paths, not one.SE29

Choice by choice

A · incorrect — Three counts B alone and omits its predecessor.

B · incorrect — Four counts C alone and omits A.

C · incorrect — Five stops after A, before both successors.

D · correct — A followed by the longer parallel branch takes nine days.

Question 97

A project starts at day 0 and must finish at day 9. It consists of exactly two parallel paths, A → B and C → D. A and C have no predecessors, B depends only on A, D depends only on C, and the project finishes when both B and D are complete. Activity durations and early times are: A: duration 4 days, ES=0, EF=4; B: duration 5 days, ES=4, EF=9; C: duration 3 days, ES=0, EF=3; D: duration 6 days, ES=3, EF=9. What is the total slack (float) of Activity C?

  • A. 0 days
  • B. 1 day
  • C. 3 days
  • D. 6 days

Write out the supplied quantities and dependency constraints. Compute and compare values under the stated metric, finish condition and assumptions.

Study-guide sections

SE30 · Slack assumptions and PERT calculations

Study-guide references

Correct answer: A — 0 days.

Each complete path takes 9 days: A→B is 4+5 and C→D is 3+6. Working backward from day 9, D must start by day 3. Therefore C must finish by day 3 and start by day 0. C has LS=0 and ES=0, so total slack = LS−ES = 0 days (equivalently LF−EF = 3−3). A is correct. Delaying C would delay its successor D and the required project finish.

Evidence in the complete study note

Early start/finish values alone do not determine slack without successor relationships and the project completion constraint. If C3→D6 is a complete path parallel to A4→B5 and both finish at day9, C has zero float. That network cannot be silently inferred from four unrelated ES/EF rows.SE30
Traditional CPM uses point durations; PERT models uncertainty with optimistic a, most-likely m and pessimistic b. The classic estimate is TE=(a+4m+b)/6 and variance=((b-a)/6)^2. For 3,6,15 days, TE=42/6=7 days and variance=4 days². Do not replace the weighted estimate by a simple average. These formulas are approximations, not guaranteed actual completion times.SE30

Choice by choice

A · correct — C has latest start 0 and earliest start 0, giving zero total slack.

B · incorrect — A one-day delay would make the C→D path finish on day 10, beyond the day-9 finish.

C · incorrect — C’s three-day duration is not its slack; a three-day delay would finish this path on day 12.

D · incorrect — D’s six-day duration is not C’s slack; a six-day delay to C would finish the path on day 15.

Question 98

PERT considers which of the following time estimates for each activity?

  • A. Ideal time only
  • B. Worst-case time only
  • C. Three-point estimates (optimistic, most likely, pessimistic)
  • D. Average of historical data (if available) statement.

Write out the supplied quantities and dependency constraints. Compute and compare values under the stated metric, finish condition and assumptions.

Study-guide sections

SE30 · Slack assumptions and PERT calculations

Study-guide references

Correct answer: C — Optimistic, most likely and pessimistic estimates.

SE30 defines the classic PERT inputs as optimistic a, most-likely m and pessimistic b. These feed the weighted expected time (a+4m+b)/6 and an uncertainty estimate. Neither a single ideal or worst-case time nor an unqualified historical average supplies the three-point representation of uncertainty described by PERT.

Evidence in the complete study note

Traditional CPM uses point durations; PERT models uncertainty with optimistic a, most-likely m and pessimistic b. The classic estimate is TE=(a+4m+b)/6 and variance=((b-a)/6)^2. For 3,6,15 days, TE=42/6=7 days and variance=4 days². Do not replace the weighted estimate by a simple average. These formulas are approximations, not guaranteed actual completion times.SE30

Choice by choice

A · incorrect — An ideal estimate alone omits the most-likely and pessimistic values needed by classic PERT.

B · incorrect — A worst-case estimate alone omits the optimistic and most-likely possibilities.

C · correct — Classic PERT uses optimistic, most-likely and pessimistic duration estimates.

D · incorrect — Historical data may inform estimates, but an average alone is not the PERT three-point input model.

Question 99

__________diagram is not supported by UML considering Data-driven modeling.

  • A. Activity
  • B. Data Flow Diagram (DFD)
  • C. State Chart
  • D. Component

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE20 · Activity, state and data-flow models

Study-guide references

Correct answer: B — Data Flow Diagram (DFD)

The traditional nine UML diagram types include activity, statechart and component diagrams; DFD is not a UML diagram type. Thus DFD is the offered non-UML notation.

Evidence in the complete study note

Choose a sequence diagram for message order between participants, a state machine for event-dependent state changes, and activity for workflow. Both sequence and state diagrams describe behavior over time. State machines are useful for objects with significant states, whether entity or control. A DFD shows data stores/flows and transformations from inputs to outputs; it is not a UML diagram.SE20

Choice by choice

A · incorrect — Listed UML activity diagram. See PDF p. 101, 56, 55.

B · correct — Not included among the module's nine UML diagrams on PDF p.47. See PDF p. 101, 56, 55.

C · incorrect — Listed UML statechart diagram. See PDF p. 101, 56, 55.

D · incorrect — Listed UML component diagram on PDF p.47. See PDF p. 101, 56, 55.

Question 100

What defining intention distinguishes a throwaway prototype from an evolutionary prototype?

  • A. It involves successive steps
  • B. It involves just one task
  • C. The prototype is built with the idea that it will eventually be converted into final system
  • D. It is intended to be discarded after learning, rather than refined into the production system.

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE07 · Prototypes, RAD and reuse-oriented development

Study-guide references

Correct answer: D — It is intended to be discarded after learning, rather than refined into the production system.

A throwaway prototype is built to learn about requirements, usability or feasibility and is discarded after serving that purpose. An evolutionary prototype is deliberately refined toward production. Either may involve successive steps, multiple tasks and varying development time, so those features do not define the difference. The artifact’s intended future, rather than how quickly it was built, distinguishes the approaches.

Evidence in the complete study note

A prototype explores requirements, usability or technical feasibility. A throwaway prototype is discarded after learning; an evolutionary prototype is deliberately refined toward production. A quick prototype may omit robustness, security or architecture, so do not deploy it unchanged without evaluation. Coding may occur during prototyping even if a diagram labels that activity construction rather than coding.SE07

Choice by choice

A · incorrect — Either kind may involve successive steps.

B · incorrect — Either kind can explore more than one task.

C · incorrect — Intended refinement into the final system describes evolutionary prototyping.

D · correct — Discard after learning is the defining throwaway intention.

Question 101

Which factors can cause requirements, scope or priorities to evolve during a project? Select all that apply.

  • A. Changing needs of stakeholders
  • B. Advances in technology
  • C. Market dynamics
  • D. Lack of project funding

Classify the motive for the change before its implementation: repair, environment, useful capability or reduced future risk.

Study-guide sections

SE11 · Validate requirements and maintain traceability

SE40 · Maintenance and software evolution

Study-guide references

Correct answers (select all): A, B, C, D — Changing needs of stakeholders; Advances in technology; Market dynamics; Lack of project funding

Stakeholder needs can change the services required, technology can introduce new constraints or opportunities, and market dynamics can alter business priorities. A funding shortfall can also reduce scope or force reprioritization. The note explicitly includes all four sources of change. Their effects depend on the project, but each can cause evolution, so none is an unconditional exception.

Evidence in the complete study note

Trace each requirement backward to its source/rationale and forward to design, code and tests. Record dependencies among requirements. A traceability matrix links these artifacts and helps impact analysis; it is not just a cost/schedule ledger. Stakeholders must negotiate conflicting requirements rather than independently approving incompatible demands. Scope, understanding and volatility are distinct elicitation difficulties.SE11
Corrective maintenance fixes faults; adaptive maintenance responds to environment changes; perfective maintenance improves useful capability/performance; preventive maintenance reduces future risk, such as restructuring fragile code. Motive determines category; refactoring can support preventive or perfective work. Maintenance often lasts years and includes understanding legacy code and regression effort, so it may dominate lifecycle cost.SE40
Markets, technology, stakeholders and funding can all change scope or priorities.SE40

Choice by choice

A · correct — Changed stakeholder needs can revise required behavior.

B · correct — Technology changes can alter constraints or opportunities.

C · correct — Market changes can alter goals and priorities.

D · correct — Funding limits can reduce scope or reorder requirements.

Question 102

Used when a large amount of testing is needed and the changes, while small, can affect many parts of the system

  • A. Preventive testing
  • B. Unit Testing
  • C. Regression Testing
  • D. Acceptance Testing

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE36 · Test types, regression and exploratory work

Study-guide references

Correct answer: C — Regression testing.

The concern is that small changes may disturb other previously working parts of the software. Regression testing means checking unintended effects after change, rather than only confirming the defect. Such testing can span multiple levels and a large scope; the question describes its purpose, not the size of a unit or an acceptance decision.

Evidence in the complete study note

Black-box techniques derive cases from specified behavior; white-box techniques derive them from internal structure; grey-box uses partial internal knowledge. Regression testing checks for unintended effects after change; confirmation testing checks the particular defect repair. Exploratory testing combines learning, design and execution and is experience based. Manual/automated describe execution support, not a compulsory black-/white-box classification.SE36

Choice by choice

A · incorrect — Preventive testing is not the defined technique for detecting unintended effects of a specific software change.

B · incorrect — Unit testing isolates a small component and does not by itself define the cross-system change-impact purpose.

C · correct — Regression tests check whether changes unintentionally damage previously working behavior elsewhere.

D · incorrect — Acceptance testing supports a user acceptance decision rather than specifically checking unintended change effects.

Question 103

The Decision table testing is a ----------?

  • A. White box Test Design Technique
  • B. Black Box Test Design Technique
  • C. Experience-based Test Design Technique
  • D. Grey Box Test Design Technique

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE37 · Equivalence, boundaries and decision tables

Study-guide references

Correct answer: B — Black-box, specification-based testing.

SE37 derives decision-table cases from combinations of specified conditions and resulting actions. This is specification-based rather than code-structure-based testing. It therefore belongs to black-box techniques. Experience or partial internal knowledge may help a tester, but they do not define the decision-table method or change its condition/action test basis.

Evidence in the complete study note

A decision table lists condition combinations and resulting actions. For validCard and enoughFunds, enumerate TT,TF,FT,FF; specify dispense only for TT and the proper rejection for others. Cover feasible rules rather than blindly using every impossible combination. These are specification-based techniques. Test requirements can also define state-transition cases, such as rejecting dispatch from an already closed incident.SE37

Choice by choice

A · incorrect — White-box techniques derive tests from internal implementation structure rather than specified condition/action rules.

B · correct — Decision tables derive cases from specified conditions and expected actions, making them black-box.

C · incorrect — The technique has an explicit specification-based structure rather than being defined by tester experience.

D · incorrect — Partial knowledge of internals is not required to derive decision-table test cases.

Question 104

Which of the following testing is related to the boundary value analysis?

  • A. White & black box testing
  • B. White-box testing
  • C. Black box testing
  • D. None of the above

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE37 · Equivalence, boundaries and decision tables

Study-guide references

Correct answer: C — Black box testing

Boundary testing is a special case of equivalence testing, a black-box testing technique.

Evidence in the complete study note

Equivalence partitioning groups inputs expected to behave alike, then samples valid and invalid groups. For allowed age18..60, useful partitions are below18,18..60,above60. Boundary tests target edges and neighbors, such as 17,18,19,59,60,61, with the exact set chosen under the stated coverage scheme.SE37

Choice by choice

A · incorrect — The cited classification does not require both white and black knowledge. See PDF p. 149, 149.

B · incorrect — Internal path knowledge is not required by input-class edges. See PDF p. 149, 149.

C · correct — Follows by boundary being a special case of black-box equivalence testing. See PDF p. 149, 149.

D · incorrect — The black-box option is supported. See PDF p. 149, 149.

Question 105

During initial design, a component with three unrelated responsibilities is split into three cohesive components. Which concept most specifically names the resulting decomposition into responsibility-based modules, rather than a general restructuring activity?

  • A. Refactoring
  • B. Modularization
  • C. Information hiding
  • D. Refinement

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE22 · Cohesion, coupling, modularity and refactoring

Study-guide references

Correct answer: B — Modularization

Separating unrelated responsibilities into cohesive components is modularization: the design is divided into modules with focused purposes. Refactoring can describe behavior-preserving restructuring of an existing solution, but that broader activity is not the specific decomposition concept requested. Information hiding concerns concealed decisions behind interfaces, while refinement is a general elaboration concept. The stated split primarily establishes better module responsibility boundaries.

Evidence in the complete study note

Logical cohesion groups similar-category operations, often selected by a flag; temporal cohesion groups operations done at the same time; functional cohesion focuses on one task. Splitting an unrelated three-purpose component improves modularity. If behavior is preserved, the restructuring is refactoring; the words are not mutually exclusive answers. Smaller modules can aid understanding, independent work, reuse and maintenance, but too many interfaces also create complexity.SE22

Choice by choice

A · incorrect — Refactoring names behavior-preserving restructuring rather than the specific module decomposition principle.

B · correct — Modularization separates responsibilities into cohesive components.

C · incorrect — No particular hidden implementation decision defines the stated split.

D · incorrect — Refinement is broader than the specified module-boundary decomposition.

Question 106

Which design approach characteristically starts with available reusable components and assembles them into a larger system, rather than starting from high-level decomposition?

  • A. Both can be used
  • B. Top down
  • C. Bottom up
  • D. None of the choices are correct

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE25 · Design principles and operation contracts

Study-guide references

Correct answer: C — Bottom up

Bottom-up design begins with existing components and assembles them into a larger solution. Top-down design instead starts with high-level structure and refines it, although it can still reuse components later. A hybrid combines the two directions, but the question asks which approach characteristically begins with the parts. Reuse by itself would not distinguish them; the explicit starting direction does.

Evidence in the complete study note

Use abstraction and decomposition to manage complexity; preserve consistency, traceability and clear responsibilities. Top-down design refines high-level structure; bottom-up design assembles existing components. A hybrid combines both. SOLID includes Single Responsibility, Open–Closed, Liskov substitution, Interface Segregation and Dependency Inversion. Depend on abstractions; add compatible extensions; avoid forcing unused operations. DRY limits duplicated knowledge, KISS avoids unnecessary complexity, and YAGNI avoids speculative work.SE25

Choice by choice

A · incorrect — A hybrid may use both directions but does not name the specifically described starting approach.

B · incorrect — Top-down begins with high-level structure.

C · correct — Bottom-up assembles existing components into the larger system.

D · incorrect — Bottom-up directly matches, so none is false.

Question 107

Processes and threads are element types we find in ____________ software structure.

  • A. Service software structure
  • B. Use software structure
  • C. Layer software structure
  • D. Concurrent software structure

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE23 · Layers, tiers and architecture views

Study-guide references

Correct answer: D — Concurrent software structure.

SE23 explicitly puts processes and threads in concurrency views because they represent independently scheduled execution. Layer structure instead describes logical abstraction levels, while uses and service relations describe different dependencies or interfaces. Thus the concurrent structure is the offered category that directly matches these runtime execution elements.

Evidence in the complete study note

A structure is the elements/relations themselves; a view represents selected aspects. Module structures show code organization, component-and-connector structures runtime interaction, and allocation structures map software to hardware, teams or environment. Processes/threads belong in concurrency views. Evaluate architectures against quality attributes and scenarios; processor allocation, decomposition and style selection can all be architectural concerns.SE23

Choice by choice

A · incorrect — Service structure emphasizes provided behavior or interfaces rather than processes and threads as execution elements.

B · incorrect — Uses structure emphasizes dependencies rather than the concurrency entities named in the stem.

C · incorrect — Layers organize logical abstraction levels rather than identifying independently scheduled execution units.

D · correct — Concurrent structure models execution elements such as processes and threads.

Question 108

Which statements correctly describe verification and validation? Select all that apply.

  • A. Verification consists of checking of documents/files and is performed by human where as validation consists of execution of program and is performed by computer.
  • B. All choices are correct
  • C. Validation assesses whether the built software meets intended stakeholder needs.
  • D. Verification refers to the set of activities that ensure software correctly implements the specific function.

Distinguish process assurance from product evaluation, and compare specified obligations with actual stakeholder needs.

Study-guide sections

SE34 · Quality assurance, verification and validation

Study-guide references

Correct answers (select all): C, D — Validation assesses whether the built software meets intended stakeholder needs.; Verification refers to the set of activities that ensure software correctly implements the specific function.

Verification checks whether specified functions and obligations have been implemented correctly. Validation checks whether the built product meets intended stakeholder needs. Both can use reviews, analysis and execution, so the claimed human-only versus computer-only split is false. Traceability can support these activities but does not alone establish satisfaction. If C states that validation checks whether software meets intended stakeholder needs, C and D are correct.

Evidence in the complete study note

Quality assurance establishes and checks processes/standards; quality control evaluates work products. An SQA plan identifies standards, responsibilities, evaluations, reviews, audits and assurance records. Quality of conformance means following the design/specification; a product can conform to a poor specification. Verification asks whether specified obligations are implemented correctly; validation asks whether the product meets intended stakeholder needs. Both can use reviews, analysis or execution, so “human-only versus computer-only” is false.SE34

Choice by choice

A · incorrect — Both activities can use human reviews and execution; the exclusive split is false.

B · incorrect — A is false, so all choices are not correct.

C · correct — Validation assesses whether the product meets intended stakeholder needs.

D · correct — Verification assesses correct implementation of specified obligations.

Question 109

Which architectural style is more suitable for if a system has to have successive transformation of streams of data?

  • A. Pipe and filter
  • B. Layered architecture
  • C. Client server architecture
  • D. All choices are correct

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE24 · Architecture styles and integration boundaries

Study-guide references

Correct answer: A — Pipe and filter

Pipe-and-filter architecture explicitly applies transformations to streams without user intervention.

Evidence in the complete study note

Repository style shares central data, simplifying common access but creating bottleneck/schema dependencies. MVC separates domain model, display view and interaction controller. Client–server separates requesters from service providers; peer-to-peer permits both roles. Pipe-and-filter applies successive transformations to data streams. Three-tier separates presentation, application logic and storage; some four-tier variants split presentation client/server.SE24

Choice by choice

A · correct — Direct match to successive stream transformations. See PDF p. 126, 127, 124.

B · incorrect — Layers organize levels, but the module does not identify them as the stream transformation style. See PDF p. 126, 127, 124.

C · incorrect — Client/server organizes requests/services, not the requested transformation pipeline. See PDF p. 126, 127, 124.

D · incorrect — Client/server is not equally established for the specific stream criterion. See PDF p. 126, 127, 124.

Question 110

Which of the following is quality measure for software?

  • A. Reliability
  • B. Low cost
  • C. Productivity
  • D. Low development time

Distinguish process assurance from product evaluation, and compare specified obligations with actual stakeholder needs.

Study-guide sections

SE34 · Quality assurance, verification and validation

Study-guide references

Correct answer: A — Reliability

Reliability is a software quality attribute characterized by behavior conformance and failure probability.

Evidence in the complete study note

A fault/defect is an underlying problem; an error may be an incorrect internal state; a failure is an externally observed departure from required service. Reliability is a product quality attribute; low cost or short development time are project outcomes. Tests increase confidence and reveal defects but cannot generally guarantee correctness over every possible input.SE34

Choice by choice

A · correct — Explicit quality metric. See PDF p. 91, 140.

B · incorrect — A project cost consideration rather than the offered software-behavior quality metric. See PDF p. 91, 140.

C · incorrect — An output/effort process measure, not the specific product quality attribute. See PDF p. 91, 140.

D · incorrect — A schedule measure rather than product reliability. See PDF p. 91, 140.

Question 111

A project manager is using PERT to estimate the duration of a project activity. The optimistic time (a) is 3 days, the most likely time (m) is 6 days, and the pessimistic time (b) is 15 days. What is the expected time (TE) for the activity?

  • A. 8 days
  • B. 10 days
  • C. 7 days
  • D. 9 days

Write out the supplied quantities and dependency constraints. Compute and compare values under the stated metric, finish condition and assumptions.

Study-guide sections

SE30 · Slack assumptions and PERT calculations

Study-guide references

Correct answer: C — 7 days.

Use TE=(a+4m+b)/6 from SE30 with a=3, m=6 and b=15. The numerator is 3+24+15=42, so TE=42/6=7 days. A simple average would give 8, but that discards the fourfold weighting of the most-likely estimate. The expected duration is an estimate, not a guaranteed actual completion time.

Evidence in the complete study note

Traditional CPM uses point durations; PERT models uncertainty with optimistic a, most-likely m and pessimistic b. The classic estimate is TE=(a+4m+b)/6 and variance=((b-a)/6)^2. For 3,6,15 days, TE=42/6=7 days and variance=4 days². Do not replace the weighted estimate by a simple average. These formulas are approximations, not guaranteed actual completion times.SE30

Choice by choice

A · incorrect — Eight is the simple mean of 3, 6 and 15, not the weighted PERT estimate.

B · incorrect — Ten does not result from substituting the three given values into the PERT formula.

C · correct — The weighted sum is 42 and dividing by six gives 7 days.

D · incorrect — Nine does not equal the PERT weighted expected time for these estimates.

Question 112

Which of the following is NOT a characteristic of a critical path in a CPM network diagram for software development?

  • A. Any delay in tasks on this path delays the entire project.
  • B. It identifies tasks with strict dependencies.
  • C. It represents the longest sequence of tasks.
  • D. It has the most slack (buffer time) compared to other paths.

Write out the supplied quantities and dependency constraints. Compute and compare values under the stated metric, finish condition and assumptions.

Study-guide sections

SE29 · Critical path: forward and backward passes

Study-guide references

Correct answer: D — It has the most slack (buffer time) compared to other paths.

The critical path is the chain determining project duration. The maximum-slack claim contradicts this: freely postponable tasks would not determine the earliest completion under a fixed network.

Evidence in the complete study note

In a dependency network, ES=max predecessor EF and EF=ES+duration; start tasks have ES=0 unless another constraint applies. Project earliest finish is the maximum terminal EF. Backward, LF=min successor LS and LS=LF-duration, starting from the required finish. Total float/slack=LS-ES=LF-EF. A critical path has the longest total duration and normally zero float in an unconstrained schedule.SE29

Choice by choice

A · incorrect — Delaying a controlling chain delays completion. See PDF p. 95.

B · incorrect — Dependency order constrains the chain, though noncritical tasks can also have strict dependencies. See PDF p. 95.

C · incorrect — The duration-determining chain is the longest required chain in the fixed-duration network. See PDF p. 95.

D · correct — Maximum slack is inconsistent with a path that controls completion; no resource constraints are assumed. See PDF p. 95.

Question 113

A zero-duration start A leads to parallel paths B(5)→C(6) and D(8)→E(3), both ending at a zero-duration finish. Which critical-path statements are true? Select all that apply. Multiple critical paths are allowed.

  • A. A→B→C is a critical path with total duration 11 days.
  • B. A→D→E is a critical path with total duration 11 days.
  • C. A→D→E is a critical path with total duration 14 days.
  • D. A→B→C is a critical path with total duration 14 days.

Write out the supplied quantities and dependency constraints. Compute and compare values under the stated metric, finish condition and assumptions.

Study-guide sections

SE29 · Critical path: forward and backward passes

Study-guide references

Correct answers (select all): A, B — A→B→C is a critical path with total duration 11 days.; A→D→E is a critical path with total duration 11 days.

The B–C branch totals 5+6=11 days and the D–E branch totals 8+3=11 days. With zero-duration start and finish, both are equally longest complete paths, so both are critical and the project duration is eleven days. There is no rule requiring a unique critical path. The alternatives using fourteen days miscalculate the corresponding branch totals.

Evidence in the complete study note

In a dependency network, ES=max predecessor EF and EF=ES+duration; start tasks have ES=0 unless another constraint applies. Project earliest finish is the maximum terminal EF. Backward, LF=min successor LS and LS=LF-duration, starting from the required finish. Total float/slack=LS-ES=LF-EF. A critical path has the longest total duration and normally zero float in an unconstrained schedule.SE29
If A takes 5 days and B=3,C=4 both follow A, project duration is 5+max(3,4)=9 days. B finishes at 8, but the project waits for C at 9. If paths B5+C6 and D8+E3 share a zero-duration start/end, both total 11; there are two critical paths, not one.SE29

Choice by choice

A · correct — The B–C branch totals eleven and is critical.

B · correct — The D–E branch also totals eleven and is critical.

C · incorrect — Eight plus three is eleven, not fourteen.

D · incorrect — Five plus six is eleven, not fourteen.

Question 114

How can market dynamics influence the evolution of requirements?

  • A. By introducing new competitors with innovative products
  • B. By stabilizing existing market conditions
  • C. By reducing the need for frequent updates
  • D. By minimizing consumer demands

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE11 · Validate requirements and maintain traceability

Study-guide references

Correct answer: A — By introducing new competitors with innovative products

Product competition is a business risk. A competitor introducing a product can alter customer needs and thus motivate evolution.

Evidence in the complete study note

Correct requirements reflect actual stakeholder needs. Complete requirements address the agreed scope, normal and exceptional behavior. Consistency excludes contradictions. Clarity/unambiguity gives one intended interpretation; feasibility/realism means achievable within constraints. Verifiability means objective evidence can check fulfillment. Replace “fast for most users” with a defined metric, workload and threshold.SE11

Choice by choice

A · correct — Direct concrete competitive stimulus consistent with the risk table on PDF p.97. See PDF p. 96, 41.

B · incorrect — Stabilization does not supply the change stimulus described. See PDF p. 96, 41.

C · incorrect — Reduced updates does not explain new competitive requirements. See PDF p. 96, 41.

D · incorrect — Minimizing demands is not the described competitive pressure. See PDF p. 96, 41.

Question 115

The static nature of the system is represented by which model?

  • A. Context Model
  • B. Data Model
  • C. Structural Model
  • D. Behavioral Model

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE17 · Class diagrams, visibility and multiplicity

Study-guide references

Correct answer: C — Structural Model

The class/object model describes structure rather than temporal behavior; structural model is the offered general category.

Evidence in the complete study note

A class box lists name, attributes and operations; + public, - private, # protected and ~ package indicate visibility. A class diagram shows static types and relationships, while an object diagram shows particular instances/links. UML is maintained and standardized by OMG; it is a modeling language, not a lifecycle process. Structural things describe conceptual or physical structural elements.SE17

Choice by choice

A · incorrect — Context concerns system boundaries, not all internal static structure. See PDF p. 51, 101.

B · incorrect — Data is one aspect of structure but narrower than the overall static model. See PDF p. 51, 101.

C · correct — Best matches the system's static classes/relationships. See PDF p. 51, 101.

D · incorrect — Behavioral models describe interactions and changes over time. See PDF p. 51, 101.

Question 116

How does backward traceability help in requirements management?

  • A. By identifying redundant requirements
  • B. By mapping requirements to design documents
  • C. By ensuring that each requirement can be traced back to its source
  • D. By linking requirements to future project phases

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE11 · Validate requirements and maintain traceability

Study-guide references

Correct answer: C — Trace each requirement back to its source and rationale.

SE11 directs requirements backward to their source or rationale and forward to design, code and tests. Backward traceability therefore establishes why a requirement exists and where it came from. It can assist reviews, but redundancy detection is not its definition. Design mappings and future phases primarily describe the forward direction.

Evidence in the complete study note

Trace each requirement backward to its source/rationale and forward to design, code and tests. Record dependencies among requirements. A traceability matrix links these artifacts and helps impact analysis; it is not just a cost/schedule ledger. Stakeholders must negotiate conflicting requirements rather than independently approving incompatible demands. Scope, understanding and volatility are distinct elicitation difficulties.SE11

Choice by choice

A · incorrect — Redundancy detection can benefit from traceability, but it is not the definition of backward tracing.

B · incorrect — Mapping toward design documents is forward traceability from the requirement.

C · correct — Backward tracing establishes the source or rationale from which each requirement originated.

D · incorrect — Links toward later project artifacts describe forward rather than backward traceability.

Question 117

Which artifact primarily serves project budgeting rather than specifying, planning or tracing tests?

  • A. Test strategy
  • B. Test Case
  • C. Project-wide cost estimate
  • D. Requirements Traceability Matrix [RTM]

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE39 · Test process, plans and defect reports

SE11 · Validate requirements and maintain traceability

SE28 · Planning, WBS, estimation and tools

Study-guide references

Correct answer: C — Project-wide cost estimate

A test strategy describes how testing will be approached, a test case supplies actions or inputs with expected results, and an RTM links requirements to tests to support coverage and impact analysis. A project-wide cost estimate instead budgets the broader project. It may include testing costs and inform a test plan, but its primary purpose is project planning rather than specifying or tracing tests. The distractor uses that explicit distinction.

Evidence in the complete study note

Plan objectives, scope, resources, schedule, risks and entry/exit criteria. Analyze the test basis for testable features and defects; design cases/expected results; implement data, scripts and environment; execute and compare; report defects; evaluate completion.SE39
Trace each requirement backward to its source/rationale and forward to design, code and tests. Record dependencies among requirements. A traceability matrix links these artifacts and helps impact analysis; it is not just a cost/schedule ledger.SE11
Planning is continuous: identify scope/deliverables, decompose work, estimate effort/duration/cost, assign resources, sequence dependencies and revise as evidence changes.SE28

Choice by choice

A · incorrect — A test strategy defines the intended testing approach.

B · incorrect — A test case specifies inputs or actions and expected results.

C · correct — A project-wide cost estimate is a budgeting artifact, not primarily a testing specification or trace.

D · incorrect — An RTM links requirements to tests and supports test coverage.

Question 118

Degree to which design specifications are followed in manufacturing the product is called

  • A. Quality Control
  • B. None of the mentioned
  • C. Quality of conformance
  • D. Quality Assurance

Distinguish process assurance from product evaluation, and compare specified obligations with actual stakeholder needs.

Study-guide sections

SE34 · Quality assurance, verification and validation

Study-guide references

Correct answer: C — Quality of conformance.

SE34 defines quality of conformance as following the design or specification. That is exactly the degree asked for in the stem. Quality control evaluates work products and quality assurance establishes and checks processes, but neither is the name of this conformance property. A conforming product may still follow an inadequate specification.

Evidence in the complete study note

Quality assurance establishes and checks processes/standards; quality control evaluates work products. An SQA plan identifies standards, responsibilities, evaluations, reviews, audits and assurance records. Quality of conformance means following the design/specification; a product can conform to a poor specification. Verification asks whether specified obligations are implemented correctly; validation asks whether the product meets intended stakeholder needs. Both can use reviews, analysis or execution, so “human-only versus computer-only” is false.SE34

Choice by choice

A · incorrect — Quality control evaluates products rather than naming their degree of adherence to the design.

B · incorrect — The exact property is offered as quality of conformance.

C · correct — Conformance measures how faithfully the product follows its design or specification.

D · incorrect — Quality assurance concerns processes and standards rather than the named degree of product conformance.

Question 119

Which of the below testing is related to Non-functional testing?

  • A. Performance Testing
  • B. Unit Testing
  • C. Black-box Testing
  • D. None of the choices are correct

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE36 · Test types, regression and exploratory work

Study-guide references

Correct answer: A — Performance Testing

Performance testing explicitly checks nonfunctional requirements and additional design goals.

Evidence in the complete study note

Black-box techniques derive cases from specified behavior; white-box techniques derive them from internal structure; grey-box uses partial internal knowledge. Regression testing checks for unintended effects after change; confirmation testing checks the particular defect repair. Exploratory testing combines learning, design and execution and is experience based. Manual/automated describe execution support, not a compulsory black-/white-box classification.SE36

Choice by choice

A · correct — Directly tests nonfunctional qualities. See PDF p. 144.

B · incorrect — A test level that can use several techniques and requirement types. See PDF p. 144.

C · incorrect — A knowledge-based technique category, not specifically nonfunctional scope. See PDF p. 144.

D · incorrect — The performance option is supported. See PDF p. 144.

Question 120

First design the very high level structure of the system. Then gradually work down to detailed decisions about low-level constructs. Which design approach follows the given strategy?

  • A. Bottom-up
  • B. System design
  • C. Top-down
  • D. Hybrid

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE25 · Design principles and operation contracts

Study-guide references

Correct answer: C — Top-down design.

The described direction starts with high-level structure and refines it into lower-level decisions. SE25 explicitly calls that top-down design. Bottom-up starts from existing components and assembles them; a hybrid combines directions. System design names a design activity or level, not the specific refinement direction requested by the question.

Evidence in the complete study note

Use abstraction and decomposition to manage complexity; preserve consistency, traceability and clear responsibilities. Top-down design refines high-level structure; bottom-up design assembles existing components. A hybrid combines both. SOLID includes Single Responsibility, Open–Closed, Liskov substitution, Interface Segregation and Dependency Inversion. Depend on abstractions; add compatible extensions; avoid forcing unused operations. DRY limits duplicated knowledge, KISS avoids unnecessary complexity, and YAGNI avoids speculative work.SE25

Choice by choice

A · incorrect — Bottom-up proceeds from components toward a larger structure, reversing the described direction.

B · incorrect — System design names an architectural activity rather than the specific high-to-low refinement approach.

C · correct — Top-down begins with high-level structure and progressively refines implementation details.

D · incorrect — A hybrid combines both directions; the stem describes only top-down refinement.

Question 121

If you plan a software test to be done by clients to demonstrate that the system satisfies their requirements, which phase of software testing is appropriate?

  • A. Acceptance testing
  • B. Integration testing
  • C. System testing
  • D. Unit testing

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE35 · Testing levels and acceptance

Study-guide references

Correct answer: A — Acceptance testing

Acceptance testing checks requirements against the project agreement and is performed by the client, matching both actor and purpose in the stem.

Evidence in the complete study note

Acceptance testing supports the customer/user’s acceptance decision against agreed needs and criteria. Alpha typically happens in a controlled developer setting with selected users; beta uses external users in their environments. None of these levels is universally the longest. Unit is a level, while white-box is a technique; a unit can be tested using black-box cases too.SE35

Choice by choice

A · correct — Direct client agreement/acceptance check. See PDF p. 145, 144.

B · incorrect — Combines individually tested components. See PDF p. 145, 144.

C · incorrect — Tests the complete system, but the specified client acceptance purpose identifies the narrower level. See PDF p. 145, 144.

D · incorrect — Isolates building blocks, not client acceptance. See PDF p. 145, 144.

Question 122

Assume you make modification to your software. Then you want to make sure that the modification has not introduced new errors. Which software testing level is required?

  • A. Regression testing
  • B. Static testing
  • C. Beta testing
  • D. Dynamic testing

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE36 · Test types, regression and exploratory work

Study-guide references

Correct answer: A — Regression testing.

Regression testing means checking for unintended effects after a software change. That matches the stated goal of finding newly introduced errors. Static and dynamic describe execution-related approaches rather than this change-focused purpose; beta describes an external-user test setting. Although the stem says level, regression is more accurately a testing purpose/type.

Evidence in the complete study note

Black-box techniques derive cases from specified behavior; white-box techniques derive them from internal structure; grey-box uses partial internal knowledge. Regression testing checks for unintended effects after change; confirmation testing checks the particular defect repair. Exploratory testing combines learning, design and execution and is experience based. Manual/automated describe execution support, not a compulsory black-/white-box classification.SE36

Choice by choice

A · correct — Regression testing checks whether a modification damages behavior that previously worked.

B · incorrect — Static testing examines artifacts without execution and does not specifically define the change-impact purpose.

C · incorrect — Beta testing involves external users in their environments rather than specifically checking every change's unintended effects.

D · incorrect — Dynamic testing means executing software; it is broader than the regression purpose described.

Question 123

After deep analysis if your software requires major change to the architecture of the system, which strategy of software change should be applied?

  • A. Preventative maintenance
  • B. Architectural transformation
  • C. Software reengineering
  • D. Software maintenance

Classify the motive for the change before its implementation: repair, environment, useful capability or reduced future risk.

Study-guide sections

SE40 · Maintenance and software evolution

Study-guide references

Correct answer: B — Architectural transformation.

SE40 names major restructuring reengineering and identifies architectural transformation as the more specific term when the architecture itself changes. The stem expressly requires major architecture change, making B the best match. Maintenance and reengineering are broader categories, while preventive maintenance describes a motive and need not involve architectural restructuring.

Evidence in the complete study note

A typical evolution sequence is change request→impact analysis→release planning→implementation/testing→release. Among a list lacking the request step, impact analysis may be the earliest listed technical activity. Major restructuring is reengineering; if the architecture itself changes, architectural transformation is the more specific description. Markets, technology, stakeholders and funding can all change scope or priorities.SE40

Choice by choice

A · incorrect — Preventive maintenance reduces future risk but does not specifically denote a major architectural change.

B · correct — Architectural transformation directly names the major architecture change required by the scenario.

C · incorrect — Reengineering is a broader restructuring category; architectural transformation is more specific here.

D · incorrect — Maintenance is the broad activity family rather than the particular architecture-change strategy.

Question 124

Which one of the following does NOT show a non-functional requirement of software systems?

  • A. Response time
  • B. Memory requirement
  • C. Reliability
  • D. Displaying information

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE09 · Functional requirements include prohibited behavior

Study-guide references

Correct answer: D — Displaying information

Response time, memory constraints and reliability are nonfunctional qualities. Displaying information specifies a service rather than a quality bound.

Evidence in the complete study note

A functional requirement states an observable service or behavior, including reactions to inputs, errors and forbidden actions. “When the sensor detects intrusion, send an alert” is functional. “Only a manager may approve refunds” also specifies permitted/prohibited behavior. A negative statement is not automatically nonfunctional.SE09

Choice by choice

A · incorrect — Quantitative speed constraint. See PDF p. 65, 66, 127.

B · incorrect — Space/resource constraint. See PDF p. 65, 66, 127.

C · incorrect — Dependability quality. See PDF p. 65, 66, 127.

D · correct — Observable function of presenting information. See PDF p. 65, 66, 127.

Question 125

Which one of the following is false about project planning stage?

  • A. Risk analysis is done during project planning
  • B. Preparing time schedule is done during project planning
  • C. Cost estimation is done during project planning
  • D. Project planning is a one-time task in software development life cycle

Distinguish the planning or organization goal from the tool or structure used to support it. Apply the stated project conditions.

Study-guide sections

SE28 · Planning, WBS, estimation and tools

Study-guide references

Correct answer: D — Project planning is a one-time task in software development life cycle

Planning is explicitly continuous from initial concept through delivery and revised as information changes. Therefore the one-time statement is false.

Evidence in the complete study note

Planning is continuous: identify scope/deliverables, decompose work, estimate effort/duration/cost, assign resources, sequence dependencies and revise as evidence changes. A WBS is hierarchical and covers project scope without adding unrelated work. Tools help coordinate ownership, dependencies and progress; they do not replace judgment or automatically fix bugs.SE28

Choice by choice

A · incorrect — Risk analysis is in the plan structure. See PDF p. 90.

B · incorrect — Schedule is in the project plan. See PDF p. 90.

C · incorrect — Plans concern schedule and budget, so cost estimation belongs in planning. See PDF p. 90.

D · correct — Direct contradiction of continuous revision. See PDF p. 90.

Question 126

Which phase of software development process refers to modification of software to reflect changing customer and market requirements?

  • A. Validation
  • B. Evolution
  • C. Development
  • D. Specification

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE01 · Software engineering, processes and work products

Study-guide references

Correct answer: B — Evolution

Changing existing software to meet new requirements is software evolution.

Evidence in the complete study note

Software engineering applies systematic methods to development, operation and maintenance. A software product includes executable code and relevant requirements, designs, test assets, configuration and user documentation. A process defines activities, ordering, roles, products and entry/exit conditions. Its four broad activities are specification, design/implementation, validation and evolution.SE01

Choice by choice

A · incorrect — Checks conformance and customer expectations. See PDF p. 41.

B · correct — Exact ongoing change activity. See PDF p. 41.

C · incorrect — Produces a software implementation. See PDF p. 41.

D · incorrect — Defines required services and constraints. See PDF p. 41.

Question 127

When is it appropriate to use the Spiral model?

  • A. Where business modeling is clearly understood and in use
  • B. When it is too risky to develop the overall system as one block
  • C. When requirements are understood early but can change during the project's life cycle
  • D. When requirements are unstable and constantly changing

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE06 · Spiral development and risk

Study-guide references

Correct answer: B — When major risks make one-block development unsafe.

SE06 uses explicit risk assessment and reduction to distinguish spiral development from other iterative approaches. B directly states that risk makes a single overall commitment inappropriate. Changing or unstable requirements can occur in several processes and do not alone identify spiral; clear business modeling likewise does not supply the distinctive risk-based reason.

Evidence in the complete study note

Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06
Use risk emphasis to distinguish spiral from a generic changing-requirements scenario.SE06

Choice by choice

A · incorrect — Understanding business modeling alone does not identify the need for risk-driven spiral cycles.

B · correct — Important risks justify staged investigation and commitment rather than building the entire system in one block.

C · incorrect — Possible requirement changes fit multiple processes and omit spiral's distinguishing explicit risk emphasis.

D · incorrect — Unstable requirements alone do not uniquely select spiral over other adaptive approaches.

Question 128

A module is said to have logical cohesion if:

  • A. All the functions of the module are executed within the same time span
  • B. All elements of the module depend on their interface complexity
  • C. It performs a set of tasks that relate to each other very loosely
  • D. All elements of the module perform similar operations

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE22 · Cohesion, coupling, modularity and refactoring

Study-guide references

Correct answer: D — The module groups similar-category operations.

SE22 defines logical cohesion as grouping operations in a similar category, often selected through a flag. D matches that shared logical category. A instead describes temporal cohesion, where operations occur at the same time. Interface complexity concerns dependencies, and a loose collection of unrelated tasks does not state the defining category-based relationship.

Evidence in the complete study note

Logical cohesion groups similar-category operations, often selected by a flag; temporal cohesion groups operations done at the same time; functional cohesion focuses on one task. Splitting an unrelated three-purpose component improves modularity. If behavior is preserved, the restructuring is refactoring; the words are not mutually exclusive answers. Smaller modules can aid understanding, independent work, reuse and maintenance, but too many interfaces also create complexity.SE22

Choice by choice

A · incorrect — Grouping operations because they occur at the same time is temporal cohesion.

B · incorrect — Interface complexity concerns dependencies and does not define logical cohesion inside a module.

C · incorrect — Loose task relatedness alone does not establish the shared operation category defining logical cohesion.

D · correct — Grouping similar-category operations is the defining feature of logical cohesion.

Question 129

Which software engineering principles are used to help reduce programming complexity?

  • A. Structured and unstructured
  • B. Object Oriented Design
  • C. Abstraction and Decomposition
  • D. Functional and Non-functional

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE22 · Cohesion, coupling, modularity and refactoring

Study-guide references

Correct answer: C — Abstraction and Decomposition

Abstraction lets developers reason about objects at a higher level while decomposition divides a complex system into simpler subsystems; both directly control complexity.

Evidence in the complete study note

Cohesion measures how well elements inside a module serve a related purpose; coupling measures dependency between modules. Seek high cohesion and low coupling. Shared mutable data and knowledge of another module’s internal representation increase coupling. Information hiding exposes stable operations while concealing changeable decisions.SE22

Choice by choice

A · incorrect — Structured/unstructured names do not identify the paired techniques. See PDF p. 31, 118.

B · incorrect — OO design employs these mechanisms but is the broader methodology. See PDF p. 31, 118.

C · correct — Combines the two explicit complexity-management mechanisms. See PDF p. 31, 118.

D · incorrect — These classify requirements, not techniques for decomposing a program. See PDF p. 31, 118.

Question 130

Which listed model organizes repeated cycles around risk assessment and can select prototyping, incremental or sequential activities as appropriate within those cycles?

  • A. Spiral model
  • B. Prototyping model
  • C. Classical Waterfall model
  • D. Iterative Waterfall model

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE03 · Waterfall and the V-model

SE06 · Spiral development and risk

Study-guide references

Correct answer: A — Spiral model

Spiral development repeatedly identifies objectives, assesses and reduces risks, develops an appropriate result and plans further commitment. Its cycles can incorporate prototyping, incremental work or sequential activities according to the risks. The other listed models name particular exploratory or staged organizations rather than this risk-driven choice framework. This explains the conventional general-model reading without claiming that every process is formally a specialization of spiral.

Evidence in the complete study note

Classical waterfall separates planned phases with reviewed deliverables. It fits well-understood, stable requirements and familiar technology; late feedback makes changes costly. It does not make change physically impossible: real projects revisit work under control, and modified waterfall explicitly includes feedback. Rigidity offers milestone visibility but can freeze incorrect assumptions.SE03
Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06

Choice by choice

A · correct — Spiral selects cycle work through risk assessment.

B · incorrect — Prototyping is one learning activity that a spiral cycle may use.

C · incorrect — Classical waterfall is a planned sequential organization.

D · incorrect — Iterative waterfall adds feedback without defining the risk-driven cycle.

Question 131

Which system requirement specification includes human-computer interface issues from the system?

  • A. Functional requirements of the system
  • B. Non-functional requirements of the system
  • C. Goals of implementation
  • D. System Testing

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE10 · Nonfunctional qualities and measurable constraints

Study-guide references

Correct answer: B — Non-functional requirements of the system

User-interface look/feel and user expertise are explicitly nonfunctional concerns, under user interface and human factors. Particular interaction services can still be functional; the question is read as interface quality issues.

Evidence in the complete study note

Nonfunctional requirements include quality attributes and constraints. Performance concerns response time, throughput and resource use; reliability concerns failure-free service; availability concerns being ready for use; usability concerns task success and ease of learning. Security concerns protection; compatibility concerns cooperating environments; portability concerns moving environments; maintainability/supportability concern change, diagnosis and evolution.SE10

Choice by choice

A · incorrect — Specific interface functions can be functional, but this is not the broad human-factor quality category. See PDF p. 78, 66.

B · correct — Explicitly includes user interface and human factors. See PDF p. 78, 66.

C · incorrect — Implementation goals are not the stated requirement category. See PDF p. 78, 66.

D · incorrect — Testing is an activity, not a requirement category. See PDF p. 78, 66.

Question 132

In a classical waterfall model, which phase precedes the design phase?

  • A. Requirements analysis and specification
  • B. Maintenance
  • C. Feasibility study
  • D. Coding and unit testing

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE03 · Waterfall and the V-model

Study-guide references

Correct answer: A — Requirements analysis and specification

The sequential waterfall establishes the requirements specification before deriving the software design from the SRS.

Evidence in the complete study note

Classical waterfall separates planned phases with reviewed deliverables. It fits well-understood, stable requirements and familiar technology; late feedback makes changes costly. It does not make change physically impossible: real projects revisit work under control, and modified waterfall explicitly includes feedback. Rigidity offers milestone visibility but can freeze incorrect assumptions.SE03

Choice by choice

A · correct — The immediate input and preceding phase. See PDF p. 15, 18, 26.

B · incorrect — Occurs after delivery and operation. See PDF p. 15, 18, 26.

C · incorrect — A prior viability activity, not the immediate specification input to design. See PDF p. 15, 18, 26.

D · incorrect — Implements a design after it has been produced. See PDF p. 15, 18, 26.

Question 133

When to use the Spiral Model?

  • A. Where business modeling is clearly understood and in use.
  • B. When it is too risky to develop the overall system as one block.
  • C. When requirements are understood in the early stages but can change during the project's life cycle.
  • D. When requirements are unstable and constantly changing.

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE06 · Spiral development and risk

Study-guide references

Correct answer: B — When major risks make whole-system development in one block unsafe.

A spiral cycle identifies objectives, assesses and reduces important risks, develops an appropriate result and plans further commitment. B directly supplies the risk-based reason for choosing that process. Clear business understanding, potentially changing requirements and continuously unstable requirements do not alone distinguish spiral from other staged or adaptive models. The explicit risk is the decisive feature.

Evidence in the complete study note

Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06

Choice by choice

A · incorrect — Clear business modeling does not by itself create a reason for risk-driven spiral development.

B · correct — Risk makes staged assessment and commitment preferable to building the whole system in one block.

C · incorrect — Requirements that may change fit several processes and do not specifically identify spiral.

D · incorrect — Unstable requirements alone do not distinguish spiral without its explicit risk-analysis need.

Question 134

The process that generates activities such as project schedule, cost estimations and work breakdown structures is described as:

  • A. Project Executing
  • B. Project Initiating
  • C. Project Closing
  • D. Project Planning

Distinguish the planning or organization goal from the tool or structure used to support it. Apply the stated project conditions.

Study-guide sections

SE28 · Planning, WBS, estimation and tools

Study-guide references

Correct answer: D — Project Planning

The project plan explicitly sets out resources, work breakdown and schedule and concerns budget; these are outputs of project planning.

Evidence in the complete study note

Planning is continuous: identify scope/deliverables, decompose work, estimate effort/duration/cost, assign resources, sequence dependencies and revise as evidence changes. A WBS is hierarchical and covers project scope without adding unrelated work. Tools help coordinate ownership, dependencies and progress; they do not replace judgment or automatically fix bugs.SE28

Choice by choice

A · incorrect — Execution carries out planned tasks. See PDF p. 90, 95.

B · incorrect — Initiation frames a project but does not best identify this full planning output set. See PDF p. 90, 95.

C · incorrect — Closing concerns completion/acceptance, not scheduling future work. See PDF p. 90, 95.

D · correct — Directly corresponds to the listed plan contents. See PDF p. 90, 95.

Question 135

Which slogan is against the agile method philosophy?

  • A. Working software over comprehensive documentation
  • B. Following a plan over responding to changes
  • C. Individuals and interactions over processes and tools
  • D. Customer collaboration over contract negotiation

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE05 · Agile values, stories and Scrum

Study-guide references

Correct answer: B — Following a plan over responding to changes

Agile values working software, people interacting, customer collaboration and responsiveness to change over the respective items on the other side of each comparison. It still recognizes value in documentation, tools, contracts and plans. The reversed preference for following a plan over responding to changes conflicts with this ordering. The other three alternatives retain the Agile ordering and therefore are not slogans against its philosophy.

Evidence in the complete study note

Agile favors people collaborating, useful working results, customer participation and adaptation over rigid adherence to procedures, exhaustive documents, contracts or fixed plans. The latter still have value. Agile does not mean no planning or no documentation. A user story states a small user need and value, supported by acceptance criteria; an epic groups broader work.SE05

Choice by choice

A · incorrect — This preserves the Agile preference for working software while still valuing documentation.

B · correct — This reverses Agile’s preference for responding to change over following a plan.

C · incorrect — This preserves the preference for individuals and interactions.

D · incorrect — This preserves the preference for customer collaboration.

Question 136

What would be the most likely consequence if every software stakeholder were rushing to be approved for their requirements without discussing with other stakeholders?

  • A. Results in excess requirement
  • B. Attains the project schedule
  • C. Requirements become unambiguous
  • D. Leads to conflicting requirement

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE11 · Validate requirements and maintain traceability

Study-guide references

Correct answer: D — Leads to conflicting requirement

JAD brings stakeholders together to negotiate a mutually acceptable specification; without discussion, incompatible local demands can remain unresolved.

Evidence in the complete study note

Correct requirements reflect actual stakeholder needs. Complete requirements address the agreed scope, normal and exceptional behavior. Consistency excludes contradictions. Clarity/unambiguity gives one intended interpretation; feasibility/realism means achievable within constraints. Verifiability means objective evidence can check fulfillment. Replace “fast for most users” with a defined metric, workload and threshold.SE11

Choice by choice

A · incorrect — Excess scope is possible but not the most direct consequence of unnegotiated differences. See PDF p. 81, 68.

B · incorrect — Rushing approvals does not prove the schedule is met. See PDF p. 81, 68.

C · incorrect — Clarity is not obtained automatically by separate approvals. See PDF p. 81, 68.

D · correct — Competing viewpoints can yield contradictions, precisely what consensus and consistency checks address. See PDF p. 81, 68.

Question 137

If the estimate for total discounted benefits for a project is Birr 120,000 and total discounted cost is Birr 100,000, what is the estimated return on investment (ROI) percentage?

  • A. 30%
  • B. 12%
  • C. 10%
  • D. 20%

Write out the supplied quantities and dependency constraints. Compute and compare values under the stated metric, finish condition and assumptions.

Study-guide sections

SE31 · Business value, risks and resource optimization

Study-guide references

Correct answer: D — 20%.

The benefits and costs are already discounted to a common date, so use SE31 directly: ROI=(120000−100000)/100000×100%. Net benefit is Birr 20000, and dividing by Birr 100000 gives 0.20, or 20%. Dividing total benefits by costs would report a benefit-cost ratio, not the net return percentage requested.

Evidence in the complete study note

With benefits and costs already discounted to a common date, ROI=(benefits-costs)/costs*100%. Birr120000 benefits and Birr100000 costs give 20%, not 120%. Identify project risks to resources/schedule, product risks to quality, and business risks to the organization. Analyze likelihood and impact, plan responses and monitor.SE31

Choice by choice

A · incorrect — Thirty percent does not follow from the given net benefit and cost.

B · incorrect — Twelve percent is not 20000 divided by 100000 as a percentage.

C · incorrect — Ten percent understates the calculated net return of twenty percent.

D · correct — Net benefit is Birr 20000, which is 20% of the Birr 100000 cost.

Question 138

In a closed layered architecture with A,B,C,D from top to bottom, a pair (X,Y) means X directly calls Y. Calls may go only to the immediately lower layer. Which pair obeys this policy?

Diagram supplied with question 138
  • A. (A,C)
  • B. (D,A)
  • C. (A,B)
  • D. (C,B)

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE23 · Layers, tiers and architecture views

Study-guide references

Correct answer: C — (A,B)

Closed layering permits a layer to call only the immediately lower layer. A→B follows that adjacency and direction, so C is valid. A→C skips B and violates the closed policy even though it would be possible in a suitably open architecture. D→A and C→B point upward, which the stipulated dependency policy also forbids. The ordered pair is interpreted as caller then callee.

Evidence in the complete study note

A layer is a logical abstraction level; a tier is a deployment separation. A closed layered architecture permits calls only to the immediately lower layer; an open one permits approved skipping. For top-to-bottom A,B,C,D, A→B obeys closed layering, A→C skips, and lower-to-upper calls violate the simple dependency rule unless explicitly mediated by a defined mechanism.SE23

Choice by choice

A · incorrect — A→C skips B.

B · incorrect — D→A points upward.

C · correct — A→B calls the immediately lower layer.

D · incorrect — C→B points upward.

Question 139

Which listed roles should document a fault if they discover it during development? Select all that apply.

  • A. Tester
  • B. Requirement engineer
  • C. Developer
  • D. Scrum master

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE39 · Test process, plans and defect reports

Study-guide references

Correct answers (select all): A, B, C, D — Tester; Requirement engineer; Developer; Scrum master

Anyone discovering a fault should record it with enough evidence to reproduce and assess it. Testers often coordinate reporting, but requirements engineers, developers and Scrum masters should also document faults they discover. The report should identify the relevant environment, steps and expected versus actual behavior. Therefore all four roles meet the stated discoverer-based responsibility rather than only the dedicated tester.

Evidence in the complete study note

Plan objectives, scope, resources, schedule, risks and entry/exit criteria. Analyze the test basis for testable features and defects; design cases/expected results; implement data, scripts and environment; execute and compare; report defects; evaluate completion. Analysis asks what to test and assesses testability; design asks how. Monitoring/control run across these activities.SE39
Anyone finding a fault should record it; testers often coordinate reporting, but it is not their exclusive permission.SE39

Choice by choice

A · correct — A tester discovering a fault should record it.

B · correct — A requirements engineer discovering a fault should record it.

C · correct — A developer discovering a fault should record it.

D · correct — A Scrum master discovering a fault should record it.

Question 140

Select the one that is not correct related to generalization in system modeling.

  • A. Ingeneralization, the attributes and operations associated with higher-level classes are also associated with the lower-level classes
  • B. Facilitate easy modification of data
  • C. The higher-level classes are more specific than the lower-level classes by adding specific attributes and operations
  • D. Common information will be maintained in one place

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE18 · Association, aggregation, composition and generalization

SE-S02 · Objects, shared models and specialization

Study-guide references

Correct answer: C — The higher-level classes are more specific than the lower-level classes by adding specific attributes and operations

Generalization puts common features in more general superclasses; subclasses add or override details and are more specialized. C reverses the direction.

Evidence in the complete study note

Association connects related instances. A dashed dependency arrow means a client uses a supplier. Generalization uses a solid line and hollow triangle pointing to the superclass/general element. Shared aggregation uses a hollow diamond at the whole end and weak whole-part meaning; it does not by itself define a detailed lifecycle policy.SE18
Generalization places common concepts in a more general superclass and specialized concepts in subclasses. Available inherited attributes and operations are shared by subclasses, which may extend or override behavior. Defining common features once can reduce duplicated maintenance. The top of the hierarchy is more general, not more specialized.SE-S02

Choice by choice

A · incorrect — Inherited attributes and methods are available on subclasses. See PDF p. 104.

B · incorrect — Common definitions can reduce duplicated modification; the wording is broad. See PDF p. 104.

C · correct — Higher-level classes are more general, not more specific. See PDF p. 104.

D · incorrect — Consolidating common features in a superclass removes redundancy. See PDF p. 104.

Question 141

Which statement accurately describes the main evidential goal of software testing within quality assurance?

  • A. To achieve project timelines and deadlines.
  • B. To monitor the entire SDLC.
  • C. To generate software requirement and design documentation.
  • D. To assess conformance to specified requirements, reveal defects and increase confidence through evidence.

Distinguish process assurance from product evaluation, and compare specified obligations with actual stakeholder needs.

Study-guide sections

SE34 · Quality assurance, verification and validation

Study-guide references

Correct answer: D — To assess conformance to specified requirements, reveal defects and increase confidence through evidence.

Testing evaluates behavior against required results, revealing failures and increasing confidence in conformance. It does not generally guarantee correctness over every possible input or environment. Meeting schedules and monitoring the whole lifecycle are broader management or assurance activities, while requirements and design documentation usually form part of the test basis. Option D states the supported evidential purpose without promising certainty.

Evidence in the complete study note

Quality assurance establishes and checks processes/standards; quality control evaluates work products. An SQA plan identifies standards, responsibilities, evaluations, reviews, audits and assurance records. Quality of conformance means following the design/specification; a product can conform to a poor specification. Verification asks whether specified obligations are implemented correctly; validation asks whether the product meets intended stakeholder needs. Both can use reviews, analysis or execution, so “human-only versus computer-only” is false.SE34
Tests increase confidence and reveal defects but cannot generally guarantee correctness over every possible input.SE34

Choice by choice

A · incorrect — Timelines are a project-management goal rather than the test evidence goal.

B · incorrect — Whole-lifecycle monitoring is broader assurance/control work.

C · incorrect — Requirements and design documents are typically inputs to testing.

D · correct — Tests assess conformance, reveal defects and increase confidence.

Question 142

What component hides the distinction or boundaries between various microservices from end-client application?

  • A. Alayered system
  • B. API gateway
  • C. API logging
  • D. API proxy

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE24 · Architecture styles and integration boundaries

Study-guide references

Correct answer: B — API gateway.

SE24 defines an API gateway as one entry point that routes or combines service calls and hides service boundaries from clients. That directly matches the stated role. Logging records activity and a layered system describes broader organization; a generic proxy label alone does not establish the multi-service routing and composition role given in the note.

Evidence in the complete study note

An API gateway presents one entry point and routes/combines calls to services, hiding service boundaries from clients. It can centralize policies but also become a bottleneck. A component diagram shows components/interfaces/dependencies; a deployment diagram places software artifacts on nodes. Choose the style for the required interactions and qualities rather than selecting a universally best architecture.SE24

Choice by choice

A · incorrect — Layering organizes abstraction levels rather than naming this single microservice-facing entry component.

B · correct — An API gateway hides service boundaries behind a unified entry point and routes or combines requests.

C · incorrect — API logging records activity rather than routing clients across hidden service boundaries.

D · incorrect — A generic proxy forwards requests; the note names the broader multi-service entry-point role an API gateway.

Question 143

Which question is outside the architectural abstraction level and instead asks for every source-level execution detail?

  • A. Which architectural organization is best for delivering the functional requirements?
  • B. How the system will be distributed across a number of cores or processors
  • C. Which variable is assigned at every individual source-code execution step?
  • D. Which architectural patterns or styles to use

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE23 · Layers, tiers and architecture views

SE21 · Design and subsystem decomposition

Study-guide references

Correct answer: C — Which variable is assigned at every individual source-code execution step?

Architecture addresses major organization, responsibilities, allocation and style decisions. Selecting an arrangement for required behavior, mapping work to processors and choosing patterns are therefore valid architectural concerns. Enumerating every source-level assignment on every execution step is implementation-level tracing, beyond the abstraction of architecture documentation. Option C supplies that genuine exception while preserving the question’s comparison of architectural and detailed concerns.

Evidence in the complete study note

A structure is the elements/relations themselves; a view represents selected aspects. Module structures show code organization, component-and-connector structures runtime interaction, and allocation structures map software to hardware, teams or environment. Processes/threads belong in concurrency views. Evaluate architectures against quality attributes and scenarios; processor allocation, decomposition and style selection can all be architectural concerns.SE23
System design turns the analysis model into architecture: design goals, subsystem responsibilities, dependencies, hardware mapping, data management, access control, control flow and startup/shutdown/error policies. Detail/object design refines APIs, parameter/return types, exceptions, component choices and algorithms. A subsystem is a manageable logical collection with services and an interface; it need not be a physical replaceable artifact.SE21
Architecture documentation supports communication and records major decisions, not every source-level execution step.SE21

Choice by choice

A · incorrect — Organization supporting required behavior is architectural.

B · incorrect — Processor allocation is an architectural concern.

C · correct — Every source-level execution step exceeds the architectural abstraction.

D · incorrect — Style and pattern selection is architectural.

Question 144

Select the one that is not related with the purpose of properly documenting software architectures

  • A. to Know how the system is organized and interoperate
  • B. For Stakeholder communication
  • C. For critical system design decisions
  • D. To easily figure out the source code flow

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE21 · Design and subsystem decomposition

Study-guide references

Correct answer: D — To easily figure out the source code flow

The SDD documents goals, subsystem organization, mapping and interfaces to support teams and architecture decisions. Detailed source-code control flow is a lower-level implementation concern than the document's architectural control-flow mechanisms.

Evidence in the complete study note

System design turns the analysis model into architecture: design goals, subsystem responsibilities, dependencies, hardware mapping, data management, access control, control flow and startup/shutdown/error policies. Detail/object design refines APIs, parameter/return types, exceptions, component choices and algorithms. A subsystem is a manageable logical collection with services and an interface; it need not be a physical replaceable artifact.SE21

Choice by choice

A · incorrect — Subsystem decomposition and interfaces expose organization/interoperation. See PDF p. 130.

B · incorrect — Defines interfaces between development teams and supports communication. See PDF p. 130.

C · incorrect — Serves as reference when architecture-level decisions are revisited. See PDF p. 130.

D · correct — Detailed source-level flow is not the purpose of an architecture description; global control mechanisms may still be documented. See PDF p. 130.

Question 145

Given the following fragment of code, how many tests are required for 100% decision coverage? if width > length then biggest_dimension = width if height > width then biggest_dimension = height end_if else biggest_dimension = length if height > length then biggest_dimension = height end_if end_if

  • A. ona. 4
  • B. 6
  • C. Ole 2
  • D. 3

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE38 · Statement, decision and branch coverage

Study-guide references

Correct answer: A — Four tests for 100% decision coverage.

There are three decisions: width>length and one separate height comparison inside each outer branch. Covering both inner outcomes requires two tests with outer true and two with outer false. For example (w,l,h)=(3,2,4),(3,2,1),(2,3,4),(2,3,1) covers all outcomes. One execution cannot visit both outer branches, so two or three tests cannot suffice; six are unnecessary.

Evidence in the complete study note

Statement coverage is the number of distinct executable statements exercised divided by the total executable statements in the declared test scope. Unreachable statements can prevent100%; any justified exclusions must be documented with the adjusted scope. Decision coverage counts decision outcomes; branch coverage counts control-flow edges, including unconditional edges under the stated convention. Testing both true and false of each decision may need more than two overall test cases when branches nest. Coverage is evidence of exercised structure, not proof of all behavior.SE38
In the width/length/height program, the outer if has separate inner decisions in each branch. Need outer true with inner true and false, and outer false with its inner true and false: four tests, for example (w,l,h)=(3,2,4),(3,2,1),(2,3,4),(2,3,1). One run cannot exercise both outer branches. All paths may be infeasible or infinite with loops; specify the chosen coverage target.SE38

Choice by choice

A · correct — Four tests cover true/false of the inner decision on each of the two outer branches.

B · incorrect — Six can cover the decisions, but four suffice; it is not the required minimum.

C · incorrect — Two cover the outer decision but cannot cover both outcomes of both separate inner decisions.

D · incorrect — Three leave at least one inner decision outcome uncovered because each outer branch needs two tests.

Question 146

Using classical up-front waterfall planning, usable incremental additions and timeboxed adaptive Agile, which lifecycle statements are NOT true? Select all that apply.

  • A. Ina waterfall life cycle, the project scope, time, and cost are determined in the early phases of the life cycle
  • B. Inagile life cycle the project scope is generally determined early in the project life cycle, but time and cost estimates are routinely modified
  • C. Inanincremental life cycle, the deliverable is produced through a series of iterations that successively add functionality within a predetermined time frame
  • D. Inagile life cycles, the project scope cannot be outlined and agreed before the start of iteration.

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE05 · Agile values, stories and Scrum

Study-guide references

Correct answers (select all): B, D — Inagile life cycle the project scope is generally determined early in the project life cycle, but time and cost estimates are routinely modified; Inagile life cycles, the project scope cannot be outlined and agreed before the start of iteration.

Classical waterfall establishes planned baselines early, and incremental work adds functionality in successive deliveries. Agile instead adapts content while its timeboxes tend to remain fixed, so B misstates the general organizing pattern. D is also false because Agile permits outlining and agreeing scope before an iteration; planning continues as evidence changes. Adaptation does not mean that scope discussion or early agreement is prohibited.

Evidence in the complete study note

Scrum uses timeboxed Sprints of at most one month, with a Sprint Goal, selected work and a usable Increment meeting a Definition of Done. Scope is discussed before and during planning; it is not forbidden to agree scope. Timeboxes tend to stay fixed while content is adapted without endangering the goal. Agile can be combined with required assurance/documentation; safety-critical context alone cannot prove it is unsuitable.SE05

Choice by choice

A · incorrect — Early planned baselines fit classical waterfall.

B · correct — The claim reverses the timeboxed/adaptive-content characterization.

C · incorrect — Successive additions of usable functionality fit incremental delivery.

D · correct — Agile permits scope discussion and agreement before an iteration.

Question 147

Which design pattern is used to restore the state of an object to its previous state?

  • A. Iterator pattern
  • B. Observer pattern
  • C. Momento pattern
  • D. Visitor pattern

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE27 · Patterns, variability and testability

Study-guide references

Correct answer: C — Memento, printed as Momento.

SE27 explicitly identifies Memento as storing and restoring state while hiding representation, and notes that Momento in this question bank is a spelling error for Memento. That makes C the intended pattern name. Iterator traverses a collection and Observer notifies subscribers; neither supplies the state-snapshot restoration responsibility asked for here.

Evidence in the complete study note

Factory Method lets subclasses choose a concrete product through a creation operation, reducing coupling to concrete constructors. A simple factory centralizes creation but is not identical to Factory Method. Singleton controls access to one instance; Observer notifies subscribers; Memento stores/restores state while hiding representation; Iterator traverses; Decorator adds behavior through wrapping. The pattern name is Memento, not Momento.SE27
Variability can use selectable features, omission/inclusion and extension points; overloading supplies alternate signatures in code but is not every variability mechanism. Testability improves with controllable inputs, observable outputs, replaceable dependencies and limited structural complexity. A sandbox can isolate execution. Assess each design claim independently before evaluating a combined statement.SE27

Choice by choice

A · incorrect — Iterator traverses elements rather than storing a restorable snapshot of object state.

B · incorrect — Observer notifies subscribers about changes rather than restoring an earlier object state.

C · correct — Momento refers here to Memento, the state capture-and-restoration pattern.

D · incorrect — Visitor is not the state-snapshot restoration pattern; the note assigns that role to Memento.

Question 148

Which of the following shows the five stages in Tuckman's model of team development, in sequential order?

  • A. forming, storming, performing, norming, and adjourning
  • B. norming, forming, storming, performing, and adjourning
  • C. storming, forming, norming, performing, and adjourning
  • D. forming, storming, norming, performing, and adjourning

Distinguish the planning or organization goal from the tool or structure used to support it. Apply the stated project conditions.

Study-guide sections

SE32 · Team organization, development and maturity

Study-guide references

Correct answer: D — Forming → storming → norming → performing → adjourning.

SE32 lists orientation first, then conflict, development of norms, effective performance and closure. Their stage names are forming, storming, norming, performing and adjourning. D preserves that order. The other alternatives either put performance before norms or move orientation after later stages, contradicting the taught sequence.

Evidence in the complete study note

Functional organizations group specialists by discipline; project organizations group people around projects. Functional specialization helps staffing and knowledge continuity but may create handoff barriers. Democratic teams share decisions; chief-programmer teams centralize technical coordination. These are different classification dimensions. Tuckman’s sequence is forming→storming→norming→performing→adjourning: orientation, conflict, norms, effective work and closure.SE32

Choice by choice

A · incorrect — It places performing before norming, reversing the stated development sequence.

B · incorrect — It starts with norming before the initial forming and storming stages.

C · incorrect — It places storming before the initial forming stage.

D · correct — It matches the taught progression from orientation through conflict, norms, performance and closure.

Question 149

Which one of the following is not among the purposes of software testing?

  • A. Requesting more design and implementation time
  • B. Identifying shortcomings
  • C. Improving product acceptance
  • D. Enhancing reliability

Distinguish process assurance from product evaluation, and compare specified obligations with actual stakeholder needs.

Study-guide sections

SE34 · Quality assurance, verification and validation

Study-guide references

Correct answer: A — Requesting more design and implementation time

Testing detects faults, supports client acceptance and enables corrections that improve reliability. Requesting more implementation time is a possible project consequence, not a testing purpose.

Evidence in the complete study note

A fault/defect is an underlying problem; an error may be an incorrect internal state; a failure is an externally observed departure from required service. Reliability is a product quality attribute; low cost or short development time are project outcomes. Tests increase confidence and reveal defects but cannot generally guarantee correctness over every possible input.SE34

Choice by choice

A · correct — A request for time is not the fault-detection or confidence purpose. See PDF p. 140, 140, 145.

B · incorrect — Identifying faults/shortcomings is the explicit goal. See PDF p. 140, 140, 145.

C · incorrect — Client acceptance is checked through acceptance tests. See PDF p. 140, 140, 145.

D · incorrect — Fault discovery permits corrections and increased reliability. See PDF p. 140, 140, 145.

Question 150

During which listed activity should the test plan define configuration-management procedures alongside objectives, resources and schedule, before those procedures are applied during execution?

  • A. During test execution
  • B. During test planning
  • C. During test closing
  • D. During test initiation

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE33 · Configuration, change control and version control

SE39 · Test process, plans and defect reports

Study-guide references

Correct answer: B — During test planning

Test planning specifies intended work, objectives, resources and schedule; configuration-management procedures should be defined early as part of that preparation. They then apply throughout testing to preserve reproducible builds, data and environments. Execution and closing use those procedures rather than being their exclusive establishment point. Initiation may set context, but the question specifically asks for the activity that defines them in the test plan.

Evidence in the complete study note

Configuration management identifies controlled items, versions/baselines, change procedures, status and audits. Items may include source code, requirements, manuals, test plans, environments and build configurations. A team’s ordinary browser is usually a tool rather than product CI, but a controlled test-browser version may be an environment CI.SE33
A test plan describes intended work; incident/defect reports are normally execution outputs. A defect report should identify build/environment, steps, expected versus actual behavior, evidence and severity. Anyone finding a fault should record it; testers often coordinate reporting, but it is not their exclusive permission. Configuration control makes the tested version reproducible.SE39
Plan test configuration management early and apply it throughout testing, not at just one exclusive phase.SE33
Analysis asks what to test and assesses testability; design asks how.SE39

Choice by choice

A · incorrect — Execution applies the planned procedures to tested versions.

B · correct — Test planning defines procedures with the other planned work.

C · incorrect — Closing preserves final artifacts under established control.

D · incorrect — Initiation sets context rather than the specified test-plan definition activity.

Question 151

"The system architecture should be designed using fine-grain, self-contained components. Producers of data should be separated from consumers and shared data structures should be avoided". For which requirement this architecture description applies?

  • A. Performance
  • B. Availability
  • C. Maintainability
  • D. Security

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE43 · Design choices, evidence and economical improvement

Study-guide references

Correct answer: C — Maintainability

Independent self-contained subsystems and avoiding shared attribute data reduce coupling, limiting the impact of future changes. That directly serves maintainability.

Evidence in the complete study note

Choose designs by their effect on stated goals. Fine-grained self-contained components, separation of producers/consumers and limited shared mutable data often improve maintainability. Trade-offs remain: interfaces can add latency, isolation can complicate transactions, and global state can simplify one operation while coupling many others. Prefer measurable quality scenarios to counting components alone.SE43

Choice by choice

A · incorrect — Fine-grained separation can carry overhead and is not primarily the stated speed optimization. See PDF p. 120, 118.

B · incorrect — Availability requires continuity/failure treatment beyond component separation alone. See PDF p. 120, 118.

C · correct — Matches minimizing change impact through low coupling. See PDF p. 120, 118.

D · incorrect — Security needs explicit access-control policy; independence alone does not establish it. See PDF p. 120, 118.

Question 152

Which of the following is a process of selecting program paths in such a manner that certain branches (i.e., outgoing edges of nodes) of a control flow graph are covered by the execution of those paths?

  • A. Branch boundary
  • B. Branch coverage
  • C. Branch control
  • D. Branch expansion

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE38 · Statement, decision and branch coverage

Study-guide references

Correct answer: B — Branch coverage.

The stem explicitly defines branches as outgoing control-flow edges. SE38 identifies branch coverage as counting exercised control-flow edges under the declared convention. This differs from merely counting executed statements or evaluating decision outcomes. Branch boundary, branch control and branch expansion are not the coverage criterion described by selecting paths that exercise graph edges.

Evidence in the complete study note

Statement coverage is the number of distinct executable statements exercised divided by the total executable statements in the declared test scope. Unreachable statements can prevent100%; any justified exclusions must be documented with the adjusted scope. Decision coverage counts decision outcomes; branch coverage counts control-flow edges, including unconditional edges under the stated convention. Testing both true and false of each decision may need more than two overall test cases when branches nest. Coverage is evidence of exercised structure, not proof of all behavior.SE38

Choice by choice

A · incorrect — Branch boundary is not the defined edge-coverage criterion in the note.

B · correct — Branch coverage measures whether control-flow edges are exercised by the selected test paths.

C · incorrect — Branch control is not the name of the specified structural coverage measure.

D · incorrect — Branch expansion does not name the outgoing-edge coverage criterion described.

Question 153

Which of the following is the correct sequence that will be followed during software evolution process?

  • A. Change request, release planning, change implementation, impact analysis, system release
  • B. Change request, impact analysis, release planning, change implementation, system release
  • C. Impact analysis, Change request, change implementation, release planning, system release
  • D. Change request, impact analysis, change implementation, release planning, system release

Classify the motive for the change before its implementation: repair, environment, useful capability or reduced future risk.

Study-guide sections

SE40 · Maintenance and software evolution

Study-guide references

Correct answer: B — Change request → impact analysis → release planning → implementation → release.

SE40 gives the sequence directly. A requested change is analyzed before commitment to a release, then planned, implemented and tested, and finally released. B preserves those dependencies. The alternatives analyze consequences too late, begin analysis before a request exists, or implement before release planning. Implementation here includes the testing work omitted from the abbreviated options.

Evidence in the complete study note

A typical evolution sequence is change request→impact analysis→release planning→implementation/testing→release. Among a list lacking the request step, impact analysis may be the earliest listed technical activity. Major restructuring is reengineering; if the architecture itself changes, architectural transformation is the more specific description. Markets, technology, stakeholders and funding can all change scope or priorities.SE40

Choice by choice

A · incorrect — It postpones impact analysis until after implementation, too late to guide planning and commitment.

B · correct — It preserves request, analysis, planning, implementation/testing and release in the taught order.

C · incorrect — It begins impact analysis before identifying a change request and implements before release planning.

D · incorrect — It places implementation before release planning instead of planning the analyzed change first.

Question 154

Which of the following UML element is wrongly applied?

  • A. Use case diagram represents an interaction with the system
  • B. Sequence diagram shows the sequence of interactions required to complete some operation
  • C. An activity diagram primarily specifies the persistent lifecycle states of one object and the event-triggered transitions between those states.
  • D. Class diagram shows the object classes in a system and their relation

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE20 · Activity, state and data-flow models

SE19 · Sequence diagrams and the emergency-report example

SE17 · Class diagrams, visibility and multiplicity

Study-guide references

Correct answer: C — An activity diagram primarily specifies the persistent lifecycle states of one object and the event-triggered transitions between those states.

Use-case diagrams summarize actor goals, sequence diagrams order interactions across participants, and class diagrams describe static types and relationships. An activity diagram models workflow and action/control flow. Persistent lifecycle states and event-triggered transitions of a particular object instead call for a state machine. The revised third statement makes that mismatch explicit; the original generic event wording was too broad because activities can also respond to events.

Evidence in the complete study note

An activity diagram models workflow: filled circle start, rounded actions, guarded decision diamond, thick fork/join bars and partitions/swimlanes for responsibility. A diamond can also merge alternative flows; a join synchronizes concurrent flows. A state machine models states and transitions triggered by events, often with guards/actions, for one object’s lifecycle.SE20
Sequence diagrams show interactions across lifelines, with order/time generally downward. Messages cross between participants; activation rectangles show execution. A creation message starts a lifeline; an X marks modeled destruction, not a guarantee about when a garbage collector runs. Synchronous calls wait for completion; asynchronous messages permit the sender to proceed.SE19
A class box lists name, attributes and operations; + public, - private, # protected and ~ package indicate visibility. A class diagram shows static types and relationships, while an object diagram shows particular instances/links.SE17

Choice by choice

A · incorrect — Use-case diagrams summarize external roles and system goals/interactions.

B · incorrect — Sequence diagrams show ordered participant interactions.

C · correct — The specified lifecycle-state behavior belongs to a state machine rather than an activity workflow.

D · incorrect — Class diagrams describe static classes and their relationships.

Question 155

Select the wrong statement regarding traceability in software development projects.

  • A. Traceability shows the dependency among two or more requirements if any
  • B. Requirements should be linked to the respective stakeholder who generated them
  • D. Every design element(component) should be linked back to the requirement
  • G. Traceability traces the overall cost and schedule of every activity in the requirement

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE11 · Validate requirements and maintain traceability

Study-guide references

Correct answer: G — Traceability traces the overall cost and schedule of every activity in the requirement

Traceability records where requirements came from, how requirements depend on one another, and how each requirement is realized and checked in design, code and tests. Source links support rationale, and forward or backward links support change-impact analysis. A cost-and-schedule ledger instead belongs to project planning and control. It can reference requirements, but recording every activity’s cost and schedule is not the definition of requirements traceability.

Evidence in the complete study note

Trace each requirement backward to its source/rationale and forward to design, code and tests. Record dependencies among requirements. A traceability matrix links these artifacts and helps impact analysis; it is not just a cost/schedule ledger. Stakeholders must negotiate conflicting requirements rather than independently approving incompatible demands. Scope, understanding and volatility are distinct elicitation difficulties.SE11

Choice by choice

A · incorrect — Dependency links among requirements are a valid traceability relation.

B · incorrect — Source or stakeholder links record a requirement’s provenance.

D · incorrect — Design-to-requirement links support realization and impact analysis.

G · correct — An overall activity cost-and-schedule ledger is project control, not the defining traceability relation.

Question 156

Which named prioritization heuristic suggests that a small subset of causes may account for much of the observed impact, often summarized as 80/20?

  • A. Pareto principle
  • B. Pairwise principle
  • C. Partition principle
  • D. Parametric principle

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE43 · Design choices, evidence and economical improvement

Study-guide references

Correct answer: A — Pareto principle

Pareto’s 80/20 idea is a prioritization heuristic: a relatively small set of causes may account for a large share of observed impact. It encourages examining evidence to focus improvement effort. It does not promise that exactly one fifth of the effort fixes exactly four fifths of all defects. The revised question asks for this named heuristic, so the other principle names do not identify the rule described.

Evidence in the complete study note

Pareto’s 80/20 rule is a prioritization heuristic: a small subset of causes may account for much of the observed impact. It does not guarantee 80% of defects can be fixed with exactly 20% effort. Refactor to preserve behavior while improving structure; optimize only against measured needs; record rationale and update traceability and regression evidence after change.SE43

Choice by choice

A · correct — Pareto names the small-subset/large-impact heuristic often expressed as 80/20.

B · incorrect — This is not the name of the described 80/20 prioritization heuristic.

C · incorrect — Partitioning does not name the described concentration-of-impact heuristic.

D · incorrect — Parametric reasoning does not name the described concentration-of-impact heuristic.

Question 157

A business expects changing requirements and organizes development around repeated customer collaboration and incremental replanning; risk-analysis cycles are not its organizing priority. Which offered approach most directly matches these priorities?

  • A. Code and run
  • B. Spiral model
  • C. Agile development method
  • D. Water fall model

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE05 · Agile values, stories and Scrum

SE06 · Spiral development and risk

Study-guide references

Correct answer: C — Agile development method

The scenario’s organizing emphasis is repeated customer collaboration and adaptive planning as needs change, which identifies Agile. Spiral can also accommodate change, but organizes its cycles around explicit risk assessment and reduction. Classical waterfall relies more heavily on stable requirements and planned phase commitments. Code-and-run lacks the described disciplined planning and feedback organization. Changing requirements alone would not uniquely determine a process, so the added priorities matter.

Evidence in the complete study note

Agile favors people collaborating, useful working results, customer participation and adaptation over rigid adherence to procedures, exhaustive documents, contracts or fixed plans. The latter still have value. Agile does not mean no planning or no documentation. A user story states a small user need and value, supported by acceptance criteria; an epic groups broader work.SE05
Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06

Choice by choice

A · incorrect — Code-and-run does not supply the disciplined adaptive planning and feedback organization stated.

B · incorrect — Spiral is specifically organized around risk assessment and reduction rather than the stated primary emphasis.

C · correct — Agile makes customer collaboration and adaptation central to planning.

D · incorrect — Classical waterfall is a poorer fit for repeated replanning of evolving needs.

Question 158

Which statement is correct about the differences between functional and non-functional requirements?

  • A. Functional requirements are the services the system provide while non-functional requirements are constraints on the services or functions offered by the system
  • B. Functional requirements are decided by the customer while non-functional requirements are decided by developers
  • C. Both are the same most of the time and only vary under certain contexts
  • D. Unlike functional requirement, nonfunctional requirements are stable

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE10 · Nonfunctional qualities and measurable constraints

Study-guide references

Correct answer: A — Functional requirements are the services the system provide while non-functional requirements are constraints on the services or functions offered by the system

Required interactions are distinct from user-visible quality constraints such as response time and accuracy; users and clients participate in defining both.

Evidence in the complete study note

Nonfunctional requirements include quality attributes and constraints. Performance concerns response time, throughput and resource use; reliability concerns failure-free service; availability concerns being ready for use; usability concerns task success and ease of learning. Security concerns protection; compatibility concerns cooperating environments; portability concerns moving environments; maintainability/supportability concern change, diagnosis and evolution.SE10

Choice by choice

A · correct — Correct service-versus-constraint distinction. See PDF p. 65, 66, 78.

B · incorrect — Both types involve users/clients and developers; they are not separated by who decides. See PDF p. 65, 66, 78.

C · incorrect — The module explicitly distinguishes their subject matter. See PDF p. 65, 66, 78.

D · incorrect — No immunity to changing stakeholder needs is stated for nonfunctional requirements. See PDF p. 65, 66, 78.

Question 159

Which paired activity assesses requirements/system testability and then designs test cases and expected results?

  • A. Test analysis and requirements
  • B. Test analysis and design
  • C. Test analysis and planning
  • D. Test analysis and Implementation

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE39 · Test process, plans and defect reports

Study-guide references

Correct answer: B — Test analysis and design

Test analysis examines the test basis, identifies what can be tested and evaluates testability. Test design then specifies how to test it through cases and expected results. The analysis-and-design pair therefore covers both responsibilities. Requirements work, planning and implementation are relevant elsewhere, but do not replace case design: planning addresses resources and scope, while implementation prepares data, scripts and the environment.

Evidence in the complete study note

A test plan describes intended work; incident/defect reports are normally execution outputs. A defect report should identify build/environment, steps, expected versus actual behavior, evidence and severity. Anyone finding a fault should record it; testers often coordinate reporting, but it is not their exclusive permission. Configuration control makes the tested version reproducible.SE39
Analysis asks what to test and assesses testability; design asks how.SE39

Choice by choice

A · incorrect — Requirements work does not supply the requested case-design half.

B · correct — Analysis assesses testability and design specifies cases and expected results.

C · incorrect — Planning addresses intended work, resources and schedule rather than case design.

D · incorrect — Implementation prepares scripts, data and environment rather than being the design half.

Question 160

Which parameter is used to assess and evaluate software architectures?

  • A. Number of components in the architecture
  • B. Durability of the architecture
  • C. Responsiveness of the architectures
  • D. Architectural quality attributes

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE23 · Layers, tiers and architecture views

Study-guide references

Correct answer: D — Architectural quality attributes

Design goals are qualities derived from nonfunctional requirements; choices are evaluated consistently against performance, dependability, maintenance, cost and end-user criteria.

Evidence in the complete study note

A layer is a logical abstraction level; a tier is a deployment separation. A closed layered architecture permits calls only to the immediately lower layer; an open one permits approved skipping. For top-to-bottom A,B,C,D, A→B obeys closed layering, A→C skips, and lower-to-upper calls violate the simple dependency rule unless explicitly mediated by a defined mechanism.SE23

Choice by choice

A · incorrect — Component count alone does not establish architecture quality. See PDF p. 127, 116.

B · incorrect — Durability alone does not span the taught criteria. See PDF p. 127, 116.

C · incorrect — Responsiveness is only one performance criterion. See PDF p. 127, 116.

D · correct — Covers the full set of quality criteria used to judge architectural decisions. See PDF p. 127, 116.

Question 161

In software risk management, accepting risk happening but don not do anything is known as:

  • A. Risk transfer
  • B. Risk Retention
  • C. Risk Reduction
  • D. Risk avoidance

Write out the supplied quantities and dependency constraints. Compute and compare values under the stated metric, finish condition and assumptions.

Study-guide sections

SE31 · Business value, risks and resource optimization

Study-guide references

Correct answer: B — Risk retention, specifically passive acceptance.

SE31 distinguishes removing a risk, reducing it, transferring consequences and retaining or accepting it. It explicitly says passive acceptance may take no action. The stem describes recognizing the risk and allowing it to remain without action, so retention matches. The other responses all involve a deliberate change to the risk or its consequences.

Evidence in the complete study note

Avoidance changes the plan to remove a risk, mitigation reduces likelihood/impact, transfer assigns consequences contractually, and retention/acceptance keeps the risk; passive acceptance may take no action. Resource leveling adjusts dates to respect resource availability and can change project finish; smoothing uses available float within schedule constraints. Neither magically creates extra staff.SE31

Choice by choice

A · incorrect — Transfer assigns consequences contractually rather than simply keeping the risk without action.

B · correct — Retention or passive acceptance keeps the risk and may involve no immediate action.

C · incorrect — Reduction actively lowers likelihood or impact instead of merely accepting exposure.

D · incorrect — Avoidance changes the plan to remove the risk rather than allowing it to remain.

Question 162

Which software process model will you use if you want to deliver different functionalities (modules) of the software product that have different priority at different time?

  • A. Waterfall model
  • B. Spiral model
  • C. Incremental model
  • D. Linear model

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE04 · Iteration, increments and early delivery

SE06 · Spiral development and risk

Study-guide references

Correct answer: C — Incremental model

Incremental development delivers prioritized functionality in usable stages. Earlier increments provide value while later increments add further capability. This is a delivery organization, distinct from a strict single-pass waterfall sequence. Spiral cycles are organized around risks and may use increments, but risk-driven development is not the specific name of the stated delivery strategy. A generic linear sequence also does not describe prioritized usable subsets.

Evidence in the complete study note

Choose incremental delivery when prioritized partial capability must reach users early. Smaller changes can be easier to debug and permit feedback, though architecture and integration still require planning. Iteration need not rebuild the whole system every time, and increments need not be perfectly independent modules. Broad descriptions of early working software can fit prototypes, iterative or Agile processes; identify the purpose of that early version.SE04
Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06

Choice by choice

A · incorrect — Classical waterfall organizes phases before the principal usable delivery.

B · incorrect — Spiral is defined by risk-driven cycles, even when an increment is produced.

C · correct — Incremental development names the successive delivery of usable functionality.

D · incorrect — A linear model does not name prioritized delivery of separate usable subsets.

Question 163

Which of the following is a resource optimization techniques in which start and finish dates are adjusted based on resource constraints with the goal of balancing the demand for resources with the available supply?

  • A. Resource smoothing
  • B. Responsibility assignment matrix
  • C. Resource leveling
  • D. Resource grouping

Write out the supplied quantities and dependency constraints. Compute and compare values under the stated metric, finish condition and assumptions.

Study-guide sections

SE31 · Business value, risks and resource optimization

Study-guide references

Correct answer: C — Resource leveling.

SE31 defines resource leveling as adjusting dates to respect resource availability, potentially changing the project finish. That matches balancing resource demand against supply by moving starts and finishes. Smoothing instead works within available float and schedule constraints. A responsibility matrix assigns ownership, and resource grouping is not the defined date-adjustment technique.

Evidence in the complete study note

Avoidance changes the plan to remove a risk, mitigation reduces likelihood/impact, transfer assigns consequences contractually, and retention/acceptance keeps the risk; passive acceptance may take no action. Resource leveling adjusts dates to respect resource availability and can change project finish; smoothing uses available float within schedule constraints. Neither magically creates extra staff.SE31

Choice by choice

A · incorrect — Smoothing uses available float while retaining schedule constraints rather than generally leveling against availability.

B · incorrect — A responsibility assignment matrix maps work to owners rather than adjusting task dates for resource capacity.

C · correct — Resource leveling changes dates to balance required resources against available supply.

D · incorrect — Resource grouping is not the defined schedule-adjustment method described by the stem.

Question 164

Identify the design principle that does not apply to software systems

  • A. design should be structured to accommodate change
  • B. design should exhibit uniformity and integration
  • C. design should be reinventing the wheel from scratch
  • D. design should be traceable to the analysis model

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE25 · Design principles and operation contracts

Study-guide references

Correct answer: C — design should be reinventing the wheel from scratch

Reusable classes, controlled change and traceability to requirements support software engineering. Recreating existing solutions from scratch contradicts its reuse rationale.

Evidence in the complete study note

Use abstraction and decomposition to manage complexity; preserve consistency, traceability and clear responsibilities. Top-down design refines high-level structure; bottom-up design assembles existing components. A hybrid combines both. SOLID includes Single Responsibility, Open–Closed, Liskov substitution, Interface Segregation and Dependency Inversion. Depend on abstractions; add compatible extensions; avoid forcing unused operations. DRY limits duplicated knowledge, KISS avoids unnecessary complexity, and YAGNI avoids speculative work.SE25

Choice by choice

A · incorrect — Low coupling explicitly limits future change impact. See PDF p. 32, 120, 70.

B · incorrect — Consistent interfaces and integrated structures support the system, though this exact slogan is not quoted. See PDF p. 32, 120, 70.

C · correct — Contradicts the documented promotion of reuse and component selection. See PDF p. 32, 120, 70.

D · incorrect — Traceability explicitly supports validating design against requirements. See PDF p. 32, 120, 70.

Question 165

Which phase of the software development life cycle is responsible for gathering and analyzing user requirements?

  • A. Analysis
  • B. Design
  • C. Development
  • D. Testing

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE08 · Feasibility and levels of requirements

Study-guide references

Correct answer: A — Analysis

Requirements elicitation and analysis establish the system's purpose with users and formalize their needs; design and implementation follow.

Evidence in the complete study note

Business requirements explain why the project exists and its goals. User requirements describe stakeholder needs at a useful high level; system requirements specify detailed services and constraints. The Software Requirements Specification (SRS) organizes the agreed requirements. A natural-language specification communicates with clients while analysis models formalize it for technical discussion; real specifications can also contain diagrams.SE08

Choice by choice

A · correct — The offered phase covering gathering and analysis. See PDF p. 62, 100.

B · incorrect — Derives internal structure from requirements. See PDF p. 62, 100.

C · incorrect — Produces executable code. See PDF p. 62, 100.

D · incorrect — Detects faults in implemented behavior. See PDF p. 62, 100.

Question 166

Which design principle suggests that software components should have a single, well-defined responsibility?

  • A. DRY (Don't Repeat Yourself) principle
  • B. SOLID principle
  • C. KISS (Keep It Simple, Stupid) principle
  • D. YAGNI (You Ain't Gonna Need It) principle

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE25 · Design principles and operation contracts

Study-guide references

Correct answer: B — Single Responsibility, within SOLID.

SE25 includes Single Responsibility among the SOLID principles. That principle assigns a component one well-defined responsibility. DRY limits duplicated knowledge, KISS avoids unnecessary complexity and YAGNI avoids speculative work. Those can complement focused responsibilities, but none is the named principle directly described by the question.

Evidence in the complete study note

Use abstraction and decomposition to manage complexity; preserve consistency, traceability and clear responsibilities. Top-down design refines high-level structure; bottom-up design assembles existing components. A hybrid combines both. SOLID includes Single Responsibility, Open–Closed, Liskov substitution, Interface Segregation and Dependency Inversion. Depend on abstractions; add compatible extensions; avoid forcing unused operations. DRY limits duplicated knowledge, KISS avoids unnecessary complexity, and YAGNI avoids speculative work.SE25

Choice by choice

A · incorrect — DRY limits duplication of knowledge rather than specifically assigning one responsibility per component.

B · correct — SOLID includes the Single Responsibility principle that the stem describes.

C · incorrect — KISS favors simplicity, a different design concern from the specific single-responsibility rule.

D · incorrect — YAGNI avoids speculative work rather than defining responsibility boundaries.

Question 167

Which of the following is an agile development methodology?

  • A. Waterfall model
  • B. Scrum
  • C. V-model
  • D. Spiral model

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE05 · Agile values, stories and Scrum

Study-guide references

Correct answer: B — Scrum.

SE05 presents Scrum through timeboxed Sprints, a Sprint Goal and a usable Increment, in the Agile context. Waterfall and the V-model organize planned stages and corresponding tests, while spiral is defined by risk-driven cycles. Therefore Scrum is the specifically Agile approach among the listed alternatives; iteration alone does not make every process Scrum.

Evidence in the complete study note

Scrum uses timeboxed Sprints of at most one month, with a Sprint Goal, selected work and a usable Increment meeting a Definition of Done. Scope is discussed before and during planning; it is not forbidden to agree scope. Timeboxes tend to stay fixed while content is adapted without endangering the goal. Agile can be combined with required assurance/documentation; safety-critical context alone cannot prove it is unsuitable.SE05

Choice by choice

A · incorrect — Classical waterfall organizes planned phases rather than the Agile Scrum approach described.

B · correct — Scrum is the Agile framework using Sprints and usable Increments.

C · incorrect — The V-model pairs development stages with test levels rather than being the listed Agile framework.

D · incorrect — Spiral is risk driven and is not the specifically Agile methodology named among these choices.

Question 168

A team delivers small usable capabilities, replans the next work with customers and treats adaptation as a central value rather than organizing cycles around risk analysis. Which broad approach best fits?

  • A. Waterfall model
  • B. Agile methodology
  • C. Prototype model
  • D. Spiral model

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE04 · Iteration, increments and early delivery

SE06 · Spiral development and risk

SE05 · Agile values, stories and Scrum

Study-guide references

Correct answer: B — Agile methodology

The team adds small usable capabilities and repeatedly replans with customers. Agile makes this combination of working results, customer participation and adaptation central. A prototype’s immediate purpose is learning about requirements or feasibility; a spiral cycle is organized around risk reduction. Classical waterfall instead emphasizes planned phase commitments. Increments by themselves can occur in several processes, so the collaboration and planning priorities establish the intended comparison.

Evidence in the complete study note

Iteration revisits and improves a solution; an increment adds usable functionality. A process may do both. Delivering registration first, then payments, then reporting is incremental; revising a registration prototype after feedback is iterative. Each increment still needs design, implementation and testing.SE04
Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06
Agile favors people collaborating, useful working results, customer participation and adaptation over rigid adherence to procedures, exhaustive documents, contracts or fixed plans. The latter still have value. Agile does not mean no planning or no documentation. A user story states a small user need and value, supported by acceptance criteria; an epic groups broader work.SE05

Choice by choice

A · incorrect — Classical waterfall does not make repeated adaptive replanning its organizing emphasis.

B · correct — Agile combines working increments with ongoing customer collaboration and adaptation.

C · incorrect — Prototyping primarily explores uncertainty rather than naming this ongoing delivery-and-planning organization.

D · incorrect — Spiral’s defining emphasis is risk analysis and reduction.

Question 169

Which software testing technique focuses on finding defects by executing the software without knowledge of its internal structure?

  • A. White-box testing
  • B. Black-box testing
  • C. Integration testing
  • D. System testing

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE36 · Test types, regression and exploratory work

Study-guide references

Correct answer: B — Black-box testing

Black-box equivalence testing chooses input classes based on expected behavior without tracing internal paths; white-box paths require source knowledge.

Evidence in the complete study note

Black-box techniques derive cases from specified behavior; white-box techniques derive them from internal structure; grey-box uses partial internal knowledge. Regression testing checks for unintended effects after change; confirmation testing checks the particular defect repair. Exploratory testing combines learning, design and execution and is experience based. Manual/automated describe execution support, not a compulsory black-/white-box classification.SE36

Choice by choice

A · incorrect — Requires code/data-structure knowledge for path selection. See PDF p. 149, 149.

B · correct — Matches behavior testing without internal-structure knowledge. See PDF p. 149, 149.

C · incorrect — A test level that can combine techniques. See PDF p. 149, 149.

D · incorrect — A complete-system scope rather than the knowledge-based distinction. See PDF p. 149, 149.

Question 170

Which diagrams describe detailed behavioral evolution over time through either ordered participant interactions or event-triggered state changes? Select all that apply.

  • A. Use case diagrams
  • B. Class diagrams
  • C. Sequence diagrams
  • D. State machine diagrams

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE20 · Activity, state and data-flow models

Study-guide references

Correct answers (select all): C, D — Sequence diagrams; State machine diagrams

Sequence diagrams show ordered messages across participant lifelines, while state machines show event-triggered transitions through an object’s lifecycle states. Both therefore describe behavioral evolution over time under the stated scope. A use-case diagram summarizes external roles and goals without that detailed temporal evolution, and a class diagram describes static types and relationships. Neither replaces the two detailed dynamic views requested.

Evidence in the complete study note

Choose a sequence diagram for message order between participants, a state machine for event-dependent state changes, and activity for workflow. Both sequence and state diagrams describe behavior over time. State machines are useful for objects with significant states, whether entity or control. A DFD shows data stores/flows and transformations from inputs to outputs; it is not a UML diagram.SE20

Choice by choice

A · incorrect — Use-case diagrams summarize roles/goals rather than detailed temporal evolution.

B · incorrect — Class diagrams are static.

C · correct — Sequence diagrams show ordered participant interactions.

D · correct — State machines show event-triggered lifecycle changes.

Question 171

Which software development methodology promotes adaptive planning, evolutionary development, and continuous improvement?

  • A. Waterfall model
  • B. Agile methodology
  • C. V-model
  • D. Spiral model

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE05 · Agile values, stories and Scrum

SE03 · Waterfall and the V-model

SE06 · Spiral development and risk

Study-guide references

Correct answer: B — Agile methodology

Adaptive planning, evolutionary improvement and responsiveness to customer feedback characterize Agile as a broad development approach. Waterfall emphasizes planned phase progression; the V-model pairs development stages with corresponding test levels. Spiral can evolve a product as well, but its defining organization is repeated risk assessment and reduction. The question asks for the approach whose core emphasis matches the stated planning and collaboration values.

Evidence in the complete study note

Agile favors people collaborating, useful working results, customer participation and adaptation over rigid adherence to procedures, exhaustive documents, contracts or fixed plans. The latter still have value. Agile does not mean no planning or no documentation. A user story states a small user need and value, supported by acceptance criteria; an epic groups broader work.SE05
Classical waterfall separates planned phases with reviewed deliverables. It fits well-understood, stable requirements and familiar technology; late feedback makes changes costly. It does not make change physically impossible: real projects revisit work under control, and modified waterfall explicitly includes feedback. Rigidity offers milestone visibility but can freeze incorrect assumptions.SE03
Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06

Choice by choice

A · incorrect — Waterfall emphasizes planned phase progression rather than adaptive planning.

B · correct — Agile places adaptive planning and ongoing improvement at the center.

C · incorrect — The V-model emphasizes correspondence between development and test stages.

D · incorrect — Spiral is organized primarily around risk reduction, even when development is evolutionary.

Question 172

Which technique is used to represent the flow of activities and decisions in a software system?

  • A. Use case modeling
  • B. Activity diagrams
  • C. State machine diagrams
  • D. Component diagrams

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE20 · Activity, state and data-flow models

Study-guide references

Correct answer: B — Activity diagrams

Activity diagrams interpret actions and transitions as control flow; decision diamonds branch that flow based on conditions.

Evidence in the complete study note

An activity diagram models workflow: filled circle start, rounded actions, guarded decision diamond, thick fork/join bars and partitions/swimlanes for responsibility. A diamond can also merge alternative flows; a join synchronizes concurrent flows. A state machine models states and transitions triggered by events, often with guards/actions, for one object’s lifecycle.SE20

Choice by choice

A · incorrect — Captures external functions, not detailed action flow. See PDF p. 56, 57.

B · correct — Explicit action/control-flow notation with decisions. See PDF p. 56, 57.

C · incorrect — Shows states responding to events rather than primarily the activity sequence. See PDF p. 56, 57.

D · incorrect — Represents component organization rather than activity decisions. See PDF p. 56, 57.

Question 173

Developers build a quick interface version solely to discover how users perform an unfamiliar task; it is not a production release. Which named approach describes the immediate purpose of that version?

  • A. Waterfall model
  • B. Agile methodology
  • C. Prototype model
  • D. Spiral model

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE07 · Prototypes, RAD and reuse-oriented development

SE06 · Spiral development and risk

Study-guide references

Correct answer: C — Prototype model

The early version is built to learn how users understand and carry out a task, not to deliver a production increment. That exploratory purpose identifies a prototype. Agile can use prototypes but its broader definition centers on collaboration and adaptation. Spiral may prototype to reduce a risk, but risk cycles are not the specific technique requested. Classical waterfall does not itself name early experimental versions. The purpose of the artifact distinguishes these overlapping practices.

Evidence in the complete study note

A prototype explores requirements, usability or technical feasibility. A throwaway prototype is discarded after learning; an evolutionary prototype is deliberately refined toward production. A quick prototype may omit robustness, security or architecture, so do not deploy it unchanged without evaluation. Coding may occur during prototyping even if a diagram labels that activity construction rather than coding.SE07
Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06

Choice by choice

A · incorrect — Waterfall is a phased lifecycle rather than the named exploratory artifact technique.

B · incorrect — Agile may use prototypes but does not specifically name the described usability experiment.

C · correct — Prototyping uses an experimental version to discover requirements or usability needs.

D · incorrect — Spiral may employ a prototype, but its defining method is organizing cycles around risk reduction.

Question 174

Which testing technique focuses on testing the interaction between different components or modules of a software system?

  • A. Unit testing
  • B. Integration testing
  • C. System testing
  • D. Regression testing

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE35 · Testing levels and acceptance

SE36 · Test types, regression and exploratory work

Study-guide references

Correct answer: B — Integration testing

Integration testing targets interfaces and interactions among components that have been combined. Unit testing isolates a smaller function or component, while system testing evaluates the complete integrated product against its requirements. Regression testing is triggered by a change and looks for unintended effects; it can be performed at several levels. The scenario is categorized by its interaction scope, so integration is the specific level requested.

Evidence in the complete study note

Unit testing isolates a function, class or small component, often replacing dependencies with stubs/mocks; a driver invokes the unit and a stub substitutes a called dependency. Integration testing exercises interfaces and interactions among combined parts. System testing checks the complete integrated system against functional and nonfunctional requirements in a representative environment.SE35
Functional tests check required behavior against the SRS and acceptance criteria. Performance tests assess speed, throughput and resources under a specified workload; load uses expected demands and stress exceeds normal limits. Usability, security, compatibility and reliability tests target their respective qualities. “Normal operating conditions” alone does not distinguish functional from performance testing.SE36

Choice by choice

A · incorrect — Unit testing isolates a function or small component.

B · correct — Integration testing exercises interactions among combined components.

C · incorrect — System testing evaluates the complete product rather than specifically the component interfaces.

D · incorrect — Regression names the after-change purpose, not a particular component-combination level.

Question 175

Which design principle suggests that software entities should depend on abstractions, not on concrete implementations?

  • A. DRY (Don't Repeat Yourself) principle
  • B. SOLID principle
  • C. KISS (Keep It Simple, Stupid) principle
  • D. YAGNI (You Ain't Gonna Need It) principle

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE25 · Design principles and operation contracts

Study-guide references

Correct answer: B — Dependency Inversion, within SOLID.

SE25 lists Dependency Inversion within SOLID and explicitly directs designs to depend on abstractions. That reduces dependence on concrete implementation details and matches the stem. DRY, KISS and YAGNI address duplication, simplicity and speculative functionality respectively; none is the principle defining the abstraction-based dependency relationship.

Evidence in the complete study note

Use abstraction and decomposition to manage complexity; preserve consistency, traceability and clear responsibilities. Top-down design refines high-level structure; bottom-up design assembles existing components. A hybrid combines both. SOLID includes Single Responsibility, Open–Closed, Liskov substitution, Interface Segregation and Dependency Inversion. Depend on abstractions; add compatible extensions; avoid forcing unused operations. DRY limits duplicated knowledge, KISS avoids unnecessary complexity, and YAGNI avoids speculative work.SE25

Choice by choice

A · incorrect — DRY addresses duplicated knowledge rather than the direction and target of dependencies.

B · correct — SOLID includes Dependency Inversion, which directs dependencies toward abstractions.

C · incorrect — KISS addresses unnecessary complexity rather than specifying abstraction-based dependencies.

D · incorrect — YAGNI limits speculative work rather than defining dependency direction.

Question 176

Which software development approach follows a linear, sequential flow from requirements gathering to testing and maintenance?

  • A. Waterfall model
  • B. Agile methodology
  • C. Prototype model
  • D. Spiral model

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE03 · Waterfall and the V-model

SE06 · Spiral development and risk

Study-guide references

Correct answer: A — Waterfall model

Classical waterfall organizes development as planned sequential phases such as requirements, design, implementation and testing. Agile instead adapts work through feedback, prototyping uses experimental versions to learn, and spiral cycles organize work around risk reduction. Real waterfall projects can revisit work under change control, but the idealized linear organization described by the question is its characteristic model rather than one of the feedback-centered alternatives.

Evidence in the complete study note

Classical waterfall separates planned phases with reviewed deliverables. It fits well-understood, stable requirements and familiar technology; late feedback makes changes costly. It does not make change physically impossible: real projects revisit work under control, and modified waterfall explicitly includes feedback. Rigidity offers milestone visibility but can freeze incorrect assumptions.SE03
Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06

Choice by choice

A · correct — The idealized waterfall model follows the stated planned phase sequence.

B · incorrect — Agile emphasizes adaptation and incremental planning.

C · incorrect — Prototyping learns through experimental versions and feedback.

D · incorrect — Spiral organizes repeated cycles around risk assessment and reduction.

Question 177

Which technique is used to estimate the size and complexity of a software project?

  • A. Use case modeling
  • B. Storyboarding
  • C. Function point analysis
  • D. Pair programming

Distinguish the planning or organization goal from the tool or structure used to support it. Apply the stated project conditions.

Study-guide sections

SE28 · Planning, WBS, estimation and tools

Study-guide references

Correct answer: C — Function point analysis

Function-point analysis counts system externals, assigns complexity weights and aggregates them to estimate software size independent of implementation language.

Evidence in the complete study note

Function points estimate functional size using inputs, outputs, inquiries, internal logical files and external interface files, weighted under the chosen method. They are not just lines of code and are not a direct exact measure of complexity. Git tracks versions; issue trackers such as Jira track work/defects; CI tools such as Jenkins automate checks; Docker packages application/runtime dependencies into containers.SE28

Choice by choice

A · incorrect — Captures functionality but is not the stated weighted size-estimation method. See PDF p. 93, 91.

B · incorrect — A user-experience representation, not the module's quantitative size method. See PDF p. 93, 91.

C · correct — Directly taught size/complexity weighting technique. See PDF p. 93, 91.

D · incorrect — A development collaboration practice, not this sizing method. See PDF p. 93, 91.

Question 178

Which tool is used to track and manage software issues, bugs, and tasks throughout the development process?

  • A. Git
  • B. Jira
  • C. Jenkins
  • D. Docker

Distinguish the planning or organization goal from the tool or structure used to support it. Apply the stated project conditions.

Study-guide sections

SE28 · Planning, WBS, estimation and tools

Study-guide references

Correct answer: B — Jira.

SE28 distinguishes version tracking, issue tracking, automated checks and container packaging. It names Jira as an issue tracker for work and defects, matching bugs and tasks across development. Git records versions, Jenkins automates checks and Docker packages runtime dependencies; those tools may integrate with issue tracking but have different primary roles.

Evidence in the complete study note

Function points estimate functional size using inputs, outputs, inquiries, internal logical files and external interface files, weighted under the chosen method. They are not just lines of code and are not a direct exact measure of complexity. Git tracks versions; issue trackers such as Jira track work/defects; CI tools such as Jenkins automate checks; Docker packages application/runtime dependencies into containers.SE28

Choice by choice

A · incorrect — Git tracks source versions and history rather than serving as the named issue/task tracker.

B · correct — Jira tracks work items, defects and tasks through their development workflow.

C · incorrect — Jenkins automates checks and integration work rather than primarily managing issue records.

D · incorrect — Docker packages runtime dependencies into containers rather than tracking bugs and tasks.

Question 179

Which design principle suggests that software entities should be open for extension but closed for modification?

  • A. DRY (Don't Repeat Yourself) principle
  • B. SOLID principle
  • C. KISS (Keep It Simple, Stupid) principle
  • D. YAGNI (You Ain't Gonna Need It) principle

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE25 · Design principles and operation contracts

Study-guide references

Correct answer: B — Open–Closed, within SOLID.

SE25 lists Open–Closed within SOLID and recommends adding compatible extensions. The stem quotes that principle's central idea: support extension while keeping established code stable. DRY, KISS and YAGNI address other concerns. Open–Closed is a design goal achieved through suitable abstractions, rather than a claim that software can never need modification.

Evidence in the complete study note

Use abstraction and decomposition to manage complexity; preserve consistency, traceability and clear responsibilities. Top-down design refines high-level structure; bottom-up design assembles existing components. A hybrid combines both. SOLID includes Single Responsibility, Open–Closed, Liskov substitution, Interface Segregation and Dependency Inversion. Depend on abstractions; add compatible extensions; avoid forcing unused operations. DRY limits duplicated knowledge, KISS avoids unnecessary complexity, and YAGNI avoids speculative work.SE25

Choice by choice

A · incorrect — DRY limits duplicated knowledge rather than defining openness for extension.

B · correct — SOLID includes the Open–Closed principle explicitly described by the stem.

C · incorrect — KISS favors simple solutions rather than the specific extension-versus-modification relationship.

D · incorrect — YAGNI avoids speculative functionality rather than defining the Open–Closed design goal.

Question 180

Which technique is used to represent the static structure of a software system, including classes, relationships, and attributes?

  • A. Use case diagrams
  • B. Class diagrams
  • C. Sequence diagrams
  • D. State machine diagrams

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE17 · Class diagrams, visibility and multiplicity

Study-guide references

Correct answer: B — Class diagrams

Class diagrams explicitly depict classes with attributes and operations and their associations/generalizations.

Evidence in the complete study note

A class box lists name, attributes and operations; + public, - private, # protected and ~ package indicate visibility. A class diagram shows static types and relationships, while an object diagram shows particular instances/links. UML is maintained and standardized by OMG; it is a modeling language, not a lifecycle process. Structural things describe conceptual or physical structural elements.SE17

Choice by choice

A · incorrect — External functions and actors. See PDF p. 51.

B · correct — Exact structural modeling notation. See PDF p. 51.

C · incorrect — Time-ordered messages among objects. See PDF p. 51.

D · incorrect — State evolution rather than static attributes/relationships. See PDF p. 51.

Question 181

Customer representatives stay in close contact with developers and use feedback to reshape the next timeboxed work. Which methodology makes this collaboration and adaptation a foundational priority?

  • A. Waterfall model
  • B. Agile methodology
  • C. V-model
  • D. Spiral model

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE05 · Agile values, stories and Scrum

SE03 · Waterfall and the V-model

SE06 · Spiral development and risk

Study-guide references

Correct answer: B — Agile methodology

Frequent stakeholder communication alone is possible in several lifecycles. The scenario additionally gives customer representatives ongoing access to the team and lets feedback reshape the next timeboxed body of work, matching Agile’s collaboration and adaptation values. Waterfall and the V-model primarily organize planned stages, while spiral organizes commitments around risk reduction. The combination of priorities, rather than communication frequency by itself, identifies the intended methodology.

Evidence in the complete study note

Agile favors people collaborating, useful working results, customer participation and adaptation over rigid adherence to procedures, exhaustive documents, contracts or fixed plans. The latter still have value. Agile does not mean no planning or no documentation. A user story states a small user need and value, supported by acceptance criteria; an epic groups broader work.SE05
Classical waterfall separates planned phases with reviewed deliverables. It fits well-understood, stable requirements and familiar technology; late feedback makes changes costly. It does not make change physically impossible: real projects revisit work under control, and modified waterfall explicitly includes feedback. Rigidity offers milestone visibility but can freeze incorrect assumptions.SE03
Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06

Choice by choice

A · incorrect — Waterfall is defined by planned phase progression, not the stated adaptive collaboration priority.

B · correct — Agile explicitly prioritizes customer collaboration and responding to change.

C · incorrect — The V-model is defined by linked development and testing stages.

D · incorrect — Spiral’s organizing priority is risk assessment and reduction, though stakeholders can participate.

Question 182

Which technique documents an actor’s goal with preconditions, a main success flow, alternative flows and postconditions?

  • A. Use case modeling
  • B. Storyboarding
  • C. Wireframing
  • D. Pair programming

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE14 · Actors, use cases and scope

SE-S05 · Exploration artifacts and collaborative implementation

Study-guide references

Correct answer: A — Use case modeling

A use-case description captures an actor’s goal together with preconditions, main flow, alternatives and postconditions. This provides the structured behavioral requirements record in the scenario. Storyboards illustrate moments in an interaction and wireframes sketch interface structure; either can help discovery without supplying that full behavioral contract. Pair programming organizes two people’s implementation work. It is therefore use-case modeling that directly names the requested requirements representation.

Evidence in the complete study note

An actor is an external role interacting with the system; it can be a person, device or another system. A person may play several roles, and several people may play one role. A primary actor seeks a goal; a supporting actor provides a service. Ask which user groups perform main functions, administer or maintain the system, and which external systems exchange information.SE14
A storyboard sketches a sequence of moments in a proposed interaction, helping people explore how a concept would be used. A wireframe sketches interface structure and the arrangement of content or controls. Both can inform requirements, but neither automatically supplies a complete use-case description with actors, preconditions, flows and postconditions.SE-S05
Pair programming is a way for two programmers to work together on the same implementation task, commonly sharing a workstation with complementary writing and reviewing roles. It is an implementation collaboration practice rather than a replacement for modeling a user goal.SE-S05

Choice by choice

A · correct — Use-case modeling records actors, goals and structured successful and alternative flows.

B · incorrect — Storyboarding sketches interaction moments rather than necessarily supplying the full goal-and-flow description.

C · incorrect — Wireframing sketches interface structure and layout.

D · incorrect — Pair programming is collaborative implementation work.

Question 183

Which testing technique focuses on retesting modified or affected parts of the software to ensure that changes do not introduce new defects?

  • A. Unit testing
  • B. Integration testing
  • C. Regression testing
  • D. System testing

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE36 · Test types, regression and exploratory work

Study-guide references

Correct answer: C — Regression testing.

SE36 defines regression testing by the purpose of detecting unintended effects after change. That includes retesting changed and affected areas to find newly introduced faults. Unit, integration and system testing describe levels or scope; regression tests can be run at any of them, so the change-driven purpose uniquely identifies C.

Evidence in the complete study note

Black-box techniques derive cases from specified behavior; white-box techniques derive them from internal structure; grey-box uses partial internal knowledge. Regression testing checks for unintended effects after change; confirmation testing checks the particular defect repair. Exploratory testing combines learning, design and execution and is experience based. Manual/automated describe execution support, not a compulsory black-/white-box classification.SE36

Choice by choice

A · incorrect — Unit testing defines a small-component scope rather than the purpose of checking change-induced defects.

B · incorrect — Integration testing focuses on interfaces and interactions, which may be regression-tested but do not define regression.

C · correct — Regression testing retests previously working behavior to detect unintended effects of modifications.

D · incorrect — System testing addresses the complete integrated system rather than specifically the after-change purpose.

Question 184

Which tool is used to package an application and its dependencies into a container for easy deployment and scalability?

  • A. Git
  • B. Jira
  • C. Jenkins
  • D. Docker

Distinguish the planning or organization goal from the tool or structure used to support it. Apply the stated project conditions.

Study-guide sections

SE28 · Planning, WBS, estimation and tools

Study-guide references

Correct answer: D — Docker.

SE28 explicitly says Docker packages an application and its runtime dependencies into containers. That matches the deployment packaging task in the question. Git tracks versions, Jira tracks issues and Jenkins automates checks; they can participate in a deployment pipeline, but none replaces Docker's specified container packaging responsibility.

Evidence in the complete study note

Function points estimate functional size using inputs, outputs, inquiries, internal logical files and external interface files, weighted under the chosen method. They are not just lines of code and are not a direct exact measure of complexity. Git tracks versions; issue trackers such as Jira track work/defects; CI tools such as Jenkins automate checks; Docker packages application/runtime dependencies into containers.SE28

Choice by choice

A · incorrect — Git manages version history rather than packaging the runtime into a container.

B · incorrect — Jira manages work and defects rather than building application containers.

C · incorrect — Jenkins automates checks and pipelines but is not the named container-packaging tool.

D · correct — Docker packages the application and runtime dependencies into a deployable container.

Question 185

Which phase of the software development life cycle (SDLC) focuses on gathering and understanding user requirements?

  • A. Analysis
  • B. Design
  • C. Implementation
  • D. Testing

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE08 · Feasibility and levels of requirements

Study-guide references

Correct answer: A — Analysis

Elicitation and analysis establish user needs before internal design and implementation.

Evidence in the complete study note

Business requirements explain why the project exists and its goals. User requirements describe stakeholder needs at a useful high level; system requirements specify detailed services and constraints. The Software Requirements Specification (SRS) organizes the agreed requirements. A natural-language specification communicates with clients while analysis models formalize it for technical discussion; real specifications can also contain diagrams.SE08

Choice by choice

A · correct — Corresponds to gathering and structuring requirements. See PDF p. 62, 100.

B · incorrect — Plans the internal realization. See PDF p. 62, 100.

C · incorrect — Realizes the software design in code. See PDF p. 62, 100.

D · incorrect — Tries to expose faults in implemented software. See PDF p. 62, 100.

Question 186

What is the primary goal of software design?

  • A. To create a visually appealing user interface
  • B. To optimize the performance of the software system
  • C. To translate user requirements into a detailed plan
  • D. To develop and test individual software components

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE21 · Design and subsystem decomposition

Study-guide references

Correct answer: C — To translate user requirements into a detailed plan

Design transforms the SRS into a structure suitable for implementation and identifies internal architecture and responsibilities.

Evidence in the complete study note

System design turns the analysis model into architecture: design goals, subsystem responsibilities, dependencies, hardware mapping, data management, access control, control flow and startup/shutdown/error policies. Detail/object design refines APIs, parameter/return types, exceptions, component choices and algorithms. A subsystem is a manageable logical collection with services and an interface; it need not be a physical replaceable artifact.SE21

Choice by choice

A · incorrect — UI appearance is one design concern, not the whole goal. See PDF p. 18, 116.

B · incorrect — Performance optimization is a design goal, not the full transformation purpose. See PDF p. 18, 116.

C · correct — Matches transforming requirements into an implementable design. See PDF p. 18, 116.

D · incorrect — Coding/testing occur after or alongside design refinement, not its primary deliverable. See PDF p. 18, 116.

Question 187

Which broad approach explicitly centers its values on collaboration, working results and responding to change, using frequent feedback to improve later work?

  • A. Waterfall model
  • B. Agile methodology
  • C. Spiral model
  • D. V-model

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE05 · Agile values, stories and Scrum

SE03 · Waterfall and the V-model

SE06 · Spiral development and risk

Study-guide references

Correct answer: B — Agile methodology

The stated priorities combine short feedback cycles, collaboration and adaptation as central development values. Agile names that broad approach. Waterfall and the V-model emphasize planned stages, with the V-model additionally relating stages to test levels. Spiral can also iterate and consult stakeholders, but its defining cycle is risk-driven. Distinguishing the core emphasis avoids incorrectly claiming that only Agile can communicate or revisit work.

Evidence in the complete study note

Agile favors people collaborating, useful working results, customer participation and adaptation over rigid adherence to procedures, exhaustive documents, contracts or fixed plans. The latter still have value. Agile does not mean no planning or no documentation. A user story states a small user need and value, supported by acceptance criteria; an epic groups broader work.SE05
Classical waterfall separates planned phases with reviewed deliverables. It fits well-understood, stable requirements and familiar technology; late feedback makes changes costly. It does not make change physically impossible: real projects revisit work under control, and modified waterfall explicitly includes feedback. Rigidity offers milestone visibility but can freeze incorrect assumptions.SE03
Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06

Choice by choice

A · incorrect — Classical waterfall emphasizes planned phase commitments.

B · correct — Agile makes collaboration and responsiveness to change central values.

C · incorrect — Spiral is defined by explicit risk-reduction cycles rather than this value-based emphasis.

D · incorrect — The V-model is defined by development–test correspondences.

Question 188

A team separates a reusable reporting component behind a stable interface so other applications can use it and its implementation can change without rewriting clients. Which benefit most directly captures both goals?

  • A. To improve the readability of the code
  • B. To ensure efficient memory management
  • C. To facilitate code reuse and maintenance
  • D. To minimize the number of software defects

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE22 · Cohesion, coupling, modularity and refactoring

Study-guide references

Correct answer: C — To facilitate code reuse and maintenance

A module with a stable interface can be reused in another application, and hiding its implementation allows localized changes without rewriting its clients. Those are reuse and maintenance benefits. Readability may improve as well, but it does not fully describe the two goals stated in the scenario. Modularization does not automatically optimize memory use or eliminate defects; good boundaries and verification still matter.

Evidence in the complete study note

Logical cohesion groups similar-category operations, often selected by a flag; temporal cohesion groups operations done at the same time; functional cohesion focuses on one task. Splitting an unrelated three-purpose component improves modularity. If behavior is preserved, the restructuring is refactoring; the words are not mutually exclusive answers. Smaller modules can aid understanding, independent work, reuse and maintenance, but too many interfaces also create complexity.SE22

Choice by choice

A · incorrect — Readability may improve, but it does not fully describe reuse across applications and localized change.

B · incorrect — Memory efficiency is not guaranteed by separating modules.

C · correct — Reuse and maintenance directly match the two stated goals.

D · incorrect — Reducing defects can be a benefit, but it does not name the stated reuse-and-change objective.

Question 189

Which type of testing aims to uncover defects in the interaction between different components of a software system?

  • A. Unit testing
  • B. Integration testing
  • C. System testing
  • D. Regression testing

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE35 · Testing levels and acceptance

SE36 · Test types, regression and exploratory work

Study-guide references

Correct answer: B — Integration testing

The defects sought are in communication or interfaces among combined components, so the applicable level is integration testing. Unit tests concentrate on isolated units and system tests assess the complete product. Regression testing instead describes checking for unintended effects after a change, and can include unit, integration or system tests. The distinction is between the scope of combination and the purpose that triggers a test run.

Evidence in the complete study note

Unit testing isolates a function, class or small component, often replacing dependencies with stubs/mocks; a driver invokes the unit and a stub substitutes a called dependency. Integration testing exercises interfaces and interactions among combined parts. System testing checks the complete integrated system against functional and nonfunctional requirements in a representative environment.SE35
Functional tests check required behavior against the SRS and acceptance criteria. Performance tests assess speed, throughput and resources under a specified workload; load uses expected demands and stress exceeds normal limits. Usability, security, compatibility and reliability tests target their respective qualities. “Normal operating conditions” alone does not distinguish functional from performance testing.SE36

Choice by choice

A · incorrect — Unit testing concentrates on an isolated function or small component.

B · correct — Integration testing targets interactions among combined parts.

C · incorrect — System testing checks the whole integrated system against requirements.

D · incorrect — Regression is an after-change objective that can occur at several testing levels.

Question 190

Which programming paradigm is based on the concept of objects and their interactions?

  • A. Functional programming
  • B. Procedural programming
  • C. Object-oriented programming
  • D. Event-driven programming

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE01 · Software engineering, processes and work products

Study-guide references

Correct answer: C — Object-oriented programming

Object-oriented programming organizes a system around objects that combine state and behavior and interact through operations. Procedural programming decomposes work into functions or procedures that manipulate data. Functional programming emphasizes function evaluation and controlled side effects, while event-driven programming organizes reactions to events. An object-oriented program may also use events or functions, but the question asks which paradigm is defined by objects and their interactions.

Evidence in the complete study note

Procedural decomposition organizes functions; object oriented decomposition organizes objects with state and behavior. Either can use iterative or sequential development. OOP does not automatically shorten every project. Reuse, encapsulation and consistent models can reduce duplication and ease change; poor object design can still be complex. Functional programming emphasizes function evaluation and controlled side effects; event-driven programs react to events.SE01

Choice by choice

A · incorrect — Functional programming emphasizes evaluation of functions and controlled side effects.

B · incorrect — Procedural programming emphasizes functions or procedures operating on data.

C · correct — Object-oriented programming centers on objects with state and behavior.

D · incorrect — Event-driven programming centers on reactions to events, independent of object-based decomposition.

Question 191

What is the defining artifact-management function of version control, distinguishing it from collaboration benefits and CI services?

  • A. To manage project schedules and milestones
  • B. To facilitate collaboration among team members
  • C. To track and control changes to source code and files
  • D. To automate the testing and deployment processes

Separate artifact history and controlled changes from scheduling, collaboration benefits and automated execution.

Study-guide sections

SE33 · Configuration, change control and version control

SE28 · Planning, WBS, estimation and tools

Study-guide references

Correct answer: C — To track and control changes to source code and files

Version control records artifact versions and their history, making it possible to inspect changes, maintain branches and combine compatible work. Collaboration is an important benefit, but it is broader than the defining version-history function. Scheduling belongs to project planning, while automated testing and deployment belong to CI or delivery tooling that can use version-control events. These roles can be integrated without becoming the same activity.

Evidence in the complete study note

Configuration management identifies controlled items, versions/baselines, change procedures, status and audits. Items may include source code, requirements, manuals, test plans, environments and build configurations. A team’s ordinary browser is usually a tool rather than product CI, but a controlled test-browser version may be an environment CI.SE33
Git tracks versions; issue trackers such as Jira track work/defects; CI tools such as Jenkins automate checks; Docker packages application/runtime dependencies into containers.SE28

Choice by choice

A · incorrect — Scheduling and milestones belong to project planning and tracking.

B · incorrect — Collaboration is a benefit enabled by shared versions and merging, rather than the defining artifact-history function.

C · correct — Tracking and controlling file changes is the direct version-control function.

D · incorrect — Testing and deployment automation is CI/delivery work that may integrate with version control.

Question 192

Which conventional lifecycle is described by a simple linear requirements→design→implementation→testing sequence with reviewed phase completion, without the V-model’s explicit development-to-test pairing?

  • A. Waterfall model
  • B. Agile methodology
  • C. Spiral model
  • D. V-model

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE03 · Waterfall and the V-model

Study-guide references

Correct answer: A — Waterfall model

Classical waterfall organizes work as separated planned phases with reviewed deliverables, matching the stated linear sequence. The V-model additionally pairs development artifacts with later test levels, which this question excludes. Agile emphasizes adaptation and feedback, while spiral organizes repeated risk-driven cycles. Explicitly distinguishing the test-pairing structure removes the overlap between two staged processes without denying their relationship.

Evidence in the complete study note

The V-model pairs specification/design stages with later test levels. Requirements inform acceptance tests; system design informs system tests; component/detail design informs integration/unit tests. Coding lies at the bottom. Test planning starts early. Stable requirements and strong assurance may favor this organization, but neither a V shape nor waterfall guarantees safety or correctness.SE03
Classical waterfall separates planned phases with reviewed deliverables. It fits well-understood, stable requirements and familiar technology; late feedback makes changes costly.SE03

Choice by choice

A · correct — Classical waterfall matches the specified simple linear organization.

B · incorrect — Agile emphasizes adaptive content and feedback.

C · incorrect — Spiral uses risk-driven cycles.

D · incorrect — The V-model adds explicit development-to-test pairing excluded here.

Question 193

What is the primary purpose of software documentation?

  • A. To serve as a record of code authorship
  • B. To provide instructions for end-users
  • C. To assist in software maintenance and understanding
  • D. To ensure compliance with coding standards

Distinguish process assurance from product evaluation, and compare specified obligations with actual stakeholder needs.

Study-guide sections

SE34 · Quality assurance, verification and validation

Study-guide references

Correct answer: C — To assist in software maintenance and understanding

Documentation records requirements and architecture so developers can understand decisions, revisit designs and coordinate later change. A user manual is one audience-specific part of this broader purpose.

Evidence in the complete study note

Quality assurance establishes and checks processes/standards; quality control evaluates work products. An SQA plan identifies standards, responsibilities, evaluations, reviews, audits and assurance records. Quality of conformance means following the design/specification; a product can conform to a poor specification. Verification asks whether specified obligations are implemented correctly; validation asks whether the product meets intended stakeholder needs. Both can use reviews, analysis or execution, so “human-only versus computer-only” is false.SE34

Choice by choice

A · incorrect — Authorship alone does not capture system decisions or behavior. See PDF p. 130, 83, 32.

B · incorrect — End-user instructions are a valid subset, not the overall technical purpose. See PDF p. 130, 83, 32.

C · correct — Matches understanding, revisiting and maintaining documented structures. See PDF p. 130, 83, 32.

D · incorrect — Coding-standard compliance is narrower than the general understanding purpose. See PDF p. 130, 83, 32.

Question 194

After each short usable release, customers reorder the remaining work and the team adapts the next release’s content while keeping its timebox. Which broad approach most directly fits this planning behavior?

  • A. Waterfall model
  • B. Agile methodology
  • C. Spiral model
  • D. V-model

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE04 · Iteration, increments and early delivery

SE03 · Waterfall and the V-model

SE06 · Spiral development and risk

SE05 · Agile values, stories and Scrum

Study-guide references

Correct answer: B — Agile methodology

A fixed short timebox with usable results and customer-driven adaptation of later content fits Agile planning. Classical waterfall and the V-model organize planned development stages, with the latter pairing stages to tests. Spiral cycles organize commitments around risk assessment and reduction. All can incorporate some staged work, so the stated treatment of feedback and later scope is what makes the Agile option the most direct match.

Evidence in the complete study note

Choose incremental delivery when prioritized partial capability must reach users early. Smaller changes can be easier to debug and permit feedback, though architecture and integration still require planning. Iteration need not rebuild the whole system every time, and increments need not be perfectly independent modules. Broad descriptions of early working software can fit prototypes, iterative or Agile processes; identify the purpose of that early version.SE04
Classical waterfall separates planned phases with reviewed deliverables. It fits well-understood, stable requirements and familiar technology; late feedback makes changes costly. It does not make change physically impossible: real projects revisit work under control, and modified waterfall explicitly includes feedback. Rigidity offers milestone visibility but can freeze incorrect assumptions.SE03
Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06
Scrum uses timeboxed Sprints of at most one month, with a Sprint Goal, selected work and a usable Increment meeting a Definition of Done. Scope is discussed before and during planning; it is not forbidden to agree scope. Timeboxes tend to stay fixed while content is adapted without endangering the goal. Agile can be combined with required assurance/documentation; safety-critical context alone cannot prove it is unsuitable.SE05

Choice by choice

A · incorrect — Classical waterfall emphasizes planned phases and later delivery feedback.

B · correct — Agile adapts later work from customer feedback while producing usable increments.

C · incorrect — Spiral is specifically organized around risk reduction, not the stated timeboxed adaptation rule.

D · incorrect — The V-model is defined by paired development and test stages.

Question 195

Which design principle advocates for designing software components that have a single responsibility?

  • A. Encapsulation
  • B. Inheritance
  • C. Polymorphism
  • D. Single Responsibility Principle

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE25 · Design principles and operation contracts

SE-S02 · Objects, shared models and specialization

Study-guide references

Correct answer: D — Single Responsibility Principle.

SE25 identifies Single Responsibility among the core design principles. The question asks directly for one responsibility per component, so D is the exact named rule. Encapsulation protects internal decisions, inheritance creates subtype relations, and polymorphism supports varying implementations through a common interface. Those can help a design but do not themselves define a single responsibility.

Evidence in the complete study note

SOLID includes Single Responsibility, Open–Closed, Liskov substitution, Interface Segregation and Dependency Inversion.SE25
Generalization places common concepts in a more general superclass and specialized concepts in subclasses. Available inherited attributes and operations are shared by subclasses, which may extend or override behavior.SE-S02
Encapsulation groups state with operations and hides representation behind an interface. Polymorphism permits different object types to respond differently through a common operation or interface. Abstraction exposes the relevant contract while omitting unnecessary detail. Reusability means using suitable existing classes or components in new contexts rather than writing them again. These ideas support each other but name different properties.SE-S02

Choice by choice

A · incorrect — Encapsulation hides implementation details rather than requiring one responsibility per component.

B · incorrect — Inheritance establishes superclass/subclass reuse rather than the focused-responsibility rule.

C · incorrect — Polymorphism supports compatible varying implementations rather than defining responsibility count.

D · correct — Single Responsibility explicitly calls for one focused responsibility in a software component.

Question 196

Which design pattern is used to ensure that only one instance of a class is created throughout the system?

  • A. Singleton pattern
  • B. Factory pattern
  • C. Observer pattern
  • D. Decorator pattern

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE27 · Patterns, variability and testability

Study-guide references

Correct answer: A — Singleton.

SE27 describes Singleton as controlling access to one instance. That is the pattern requested by the one-instance condition. Factory patterns address how concrete objects are created, Observer notifies subscribers and Decorator adds behavior by wrapping. None of those other pattern responsibilities guarantees a single shared instance by itself.

Evidence in the complete study note

Factory Method lets subclasses choose a concrete product through a creation operation, reducing coupling to concrete constructors. A simple factory centralizes creation but is not identical to Factory Method. Singleton controls access to one instance; Observer notifies subscribers; Memento stores/restores state while hiding representation; Iterator traverses; Decorator adds behavior through wrapping. The pattern name is Memento, not Momento.SE27

Choice by choice

A · correct — Singleton controls creation and access so that the intended class has one shared instance.

B · incorrect — A factory selects or constructs products rather than inherently limiting a class to one instance.

C · incorrect — Observer distributes notifications to subscribers rather than restricting object instance count.

D · incorrect — Decorator adds behavior through wrapping rather than enforcing a single instance.

Question 197

Which test type checks that specified services produce the required outputs under normal operating conditions, without measuring speed/resources or user task ease?

  • A. Stress testing
  • B. Performance testing
  • C. Functional testing
  • D. Usability testing

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE36 · Test types, regression and exploratory work

Study-guide references

Correct answer: C — Functional testing

Functional tests compare observable services and outputs with the SRS and acceptance criteria. That is the stated objective, so C applies. Performance testing measures speed, throughput or resources, and usability evaluates user task success or ease; neither is requested here. Stress testing exceeds normal limits. Normal operating conditions alone would not distinguish these types, but the explicit behavioral objective does.

Evidence in the complete study note

Functional tests check required behavior against the SRS and acceptance criteria. Performance tests assess speed, throughput and resources under a specified workload; load uses expected demands and stress exceeds normal limits. Usability, security, compatibility and reliability tests target their respective qualities. “Normal operating conditions” alone does not distinguish functional from performance testing.SE36

Choice by choice

A · incorrect — Stress testing exceeds normal operating limits.

B · incorrect — Performance testing measures speed, throughput or resources.

C · correct — Functional testing checks specified services and outputs.

D · incorrect — Usability testing evaluates user task ease or success.

Question 198

Which programming paradigm promotes the use of data and avoids side effects?

  • A. Functional programming
  • B. Procedural programming
  • C. Object-oriented programming
  • D. Event-driven programming

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE01 · Software engineering, processes and work products

Study-guide references

Correct answer: A — Functional programming, for the side-effect emphasis.

The phrase promotes the use of data is not distinctive because all these paradigms use data. The discriminating part is avoiding or controlling side effects. SE01 explicitly assigns function evaluation and controlled side effects to functional programming. Procedural, object-oriented and event-driven styles organize behavior differently and do not inherently impose that emphasis.

Evidence in the complete study note

Procedural decomposition organizes functions; object oriented decomposition organizes objects with state and behavior. Either can use iterative or sequential development. OOP does not automatically shorten every project. Reuse, encapsulation and consistent models can reduce duplication and ease change; poor object design can still be complex. Functional programming emphasizes function evaluation and controlled side effects; event-driven programs react to events.SE01

Choice by choice

A · correct — Functional programming emphasizes evaluating functions and controlling side effects.

B · incorrect — Procedural decomposition organizes functions or procedures without inherently avoiding state-changing effects.

C · incorrect — Object-oriented decomposition combines state and behavior and does not inherently exclude side effects.

D · incorrect — Event-driven programs react to events; that does not itself require avoiding side effects.

Question 199

Which type of software maintenance involves making changes to a software system to adapt it to new environments or technologies?

  • A. Corrective maintenance
  • B. Adaptive maintenance
  • C. Perfective maintenance
  • D. Preventive maintenance

Classify the motive for the change before its implementation: repair, environment, useful capability or reduced future risk.

Study-guide sections

SE40 · Maintenance and software evolution

Study-guide references

Correct answer: B — Adaptive maintenance.

SE40 defines adaptive maintenance as responding to changes in the environment. New platforms or technologies therefore create an adaptive-maintenance need even when the original software is not faulty. Corrective maintenance fixes faults, perfective work improves useful capability or performance, and preventive work reduces future risk. The stated environmental motive makes B the appropriate category.

Evidence in the complete study note

Corrective maintenance fixes faults; adaptive maintenance responds to environment changes; perfective maintenance improves useful capability/performance; preventive maintenance reduces future risk, such as restructuring fragile code. Motive determines category; refactoring can support preventive or perfective work. Maintenance often lasts years and includes understanding legacy code and regression effort, so it may dominate lifecycle cost.SE40

Choice by choice

A · incorrect — Corrective work fixes faults rather than primarily accommodating changed environments or technology.

B · correct — Adaptive maintenance changes software so it continues working in a new environment or technology context.

C · incorrect — Perfective work improves capability or performance rather than specifically responding to an environmental change.

D · incorrect — Preventive work reduces future maintenance risk rather than defining adaptation to a new environment.

Question 200

What is the purpose of usability testing in software development?

  • A. To evaluate the performance of the software system under stress conditions
  • B. To assess the user-friendliness and ease of use of the software system
  • C. To verify the compliance of the software system with specified requirements
  • D. To identify and fix defects or issues in the software system

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE36 · Test types, regression and exploratory work

Study-guide references

Correct answer: B — To assess the user-friendliness and ease of use of the software system

Usability testing examines ease of learning, task completion and user errors, with the goal of identifying and improving usability problems.

Evidence in the complete study note

Functional tests check required behavior against the SRS and acceptance criteria. Performance tests assess speed, throughput and resources under a specified workload; load uses expected demands and stress exceeds normal limits. Usability, security, compatibility and reliability tests target their respective qualities. “Normal operating conditions” alone does not distinguish functional from performance testing.SE36

Choice by choice

A · incorrect — Stress performance is not the ease-of-use focus. See PDF p. 82.

B · correct — Directly matches ease of use and learning. See PDF p. 82.

C · incorrect — General requirements conformance is broader than this specific user-focused test. See PDF p. 82.

D · incorrect — General fault fixing is broader; the test identifies user interaction difficulties rather than implementing all repairs. See PDF p. 82.

Question 201

Which software development methodology involves iterative development cycles called sprints?

  • A. Waterfall model
  • B. Agile methodology
  • C. Spiral model
  • D. V-model

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE05 · Agile values, stories and Scrum

Study-guide references

Correct answer: B — Agile methodology, specifically Scrum.

SE05 places Sprints in Scrum, an Agile framework. B is therefore the available category that contains the specific process described. Agile as a whole does not require every method to call its iterations Sprints. Waterfall, spiral and the V-model have other organizing principles, so none is the named Sprint-based method.

Evidence in the complete study note

Scrum uses timeboxed Sprints of at most one month, with a Sprint Goal, selected work and a usable Increment meeting a Definition of Done. Scope is discussed before and during planning; it is not forbidden to agree scope. Timeboxes tend to stay fixed while content is adapted without endangering the goal. Agile can be combined with required assurance/documentation; safety-critical context alone cannot prove it is unsuitable.SE05

Choice by choice

A · incorrect — Classical waterfall uses planned phases rather than Scrum Sprints.

B · correct — Scrum is an Agile framework whose iterative delivery cycles are called Sprints.

C · incorrect — Spiral uses risk-driven cycles rather than specifically the Scrum Sprint mechanism.

D · incorrect — The V-model pairs development stages with tests rather than organizing work into Sprints.

Question 202

What is the primary purpose of code refactoring?

  • A. To add new features to the software system
  • B. To optimize the performance of the software system
  • C. To improve the readability and maintainability of the code
  • D. To fix defects or issues in the software system

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE43 · Design choices, evidence and economical improvement

Study-guide references

Correct answer: C — To improve the readability and maintainability of the code

Restructuring explicitly addresses maintainability, readability and understandability, while optimization separately addresses speed and memory. C matches refactoring’s purpose of improving internal structure and maintainability.

Evidence in the complete study note

Pareto’s 80/20 rule is a prioritization heuristic: a small subset of causes may account for much of the observed impact. It does not guarantee 80% of defects can be fixed with exactly 20% effort. Refactor to preserve behavior while improving structure; optimize only against measured needs; record rationale and update traceability and regression evidence after change.SE43

Choice by choice

A · incorrect — Adds behavior, whereas restructuring reorganizes existing design elements. See PDF p. 133.

B · incorrect — Optimization is separately classified by performance goals. See PDF p. 133.

C · correct — Direct match to the documented restructuring goals. See PDF p. 133.

D · incorrect — Repairing a fault is correction; restructuring need not fix a behavioral defect. See PDF p. 133.

Question 203

Which approach treats customer participation in reviewing working results and reprioritizing future work as a foundational value, rather than merely a practice a project may choose?

  • A. Waterfall model
  • B. Agile methodology
  • C. Spiral model
  • D. V-model

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE05 · Agile values, stories and Scrum

SE03 · Waterfall and the V-model

SE06 · Spiral development and risk

Study-guide references

Correct answer: B — Agile methodology

The project treats customer participation in reviewing results and reprioritizing future work as a foundational development value. This directly matches Agile’s customer collaboration and responsiveness to change. Waterfall and the V-model primarily define phase and test-stage organization. Spiral also includes stakeholder review, but risk assessment and reduction define its cycle. Participation alone is not exclusive; the explicit priority given to continual adaptive collaboration identifies the answer.

Evidence in the complete study note

Agile favors people collaborating, useful working results, customer participation and adaptation over rigid adherence to procedures, exhaustive documents, contracts or fixed plans. The latter still have value. Agile does not mean no planning or no documentation. A user story states a small user need and value, supported by acceptance criteria; an epic groups broader work.SE05
Classical waterfall separates planned phases with reviewed deliverables. It fits well-understood, stable requirements and familiar technology; late feedback makes changes costly. It does not make change physically impossible: real projects revisit work under control, and modified waterfall explicitly includes feedback. Rigidity offers milestone visibility but can freeze incorrect assumptions.SE03
Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06

Choice by choice

A · incorrect — Classical waterfall’s defining organization is planned phase progression.

B · correct — Agile explicitly prioritizes customer collaboration and adapting to feedback.

C · incorrect — Spiral includes review but is defined by risk-driven cycles.

D · incorrect — The V-model organizes linked development and test stages, rather than naming the stated collaboration values.

Question 204

Which type of testing involves running the entire software system in an environment that closely resembles the production environment?

  • A. Unit testing
  • B. Integration testing
  • C. System testing
  • D. Regression testing

Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

Study-guide sections

SE35 · Testing levels and acceptance

SE36 · Test types, regression and exploratory work

Study-guide references

Correct answer: C — System testing

System testing evaluates the complete integrated software against its functional and nonfunctional requirements in a representative environment. Unit testing isolates a smaller element and integration testing concentrates on interfaces among combined parts. Regression testing instead checks for unintended consequences after change and is not restricted to any one level or environment. The question specifies the complete-product scope, making system testing the direct classification.

Evidence in the complete study note

Unit testing isolates a function, class or small component, often replacing dependencies with stubs/mocks; a driver invokes the unit and a stub substitutes a called dependency. Integration testing exercises interfaces and interactions among combined parts. System testing checks the complete integrated system against functional and nonfunctional requirements in a representative environment.SE35
Functional tests check required behavior against the SRS and acceptance criteria. Performance tests assess speed, throughput and resources under a specified workload; load uses expected demands and stress exceeds normal limits. Usability, security, compatibility and reliability tests target their respective qualities. “Normal operating conditions” alone does not distinguish functional from performance testing.SE36

Choice by choice

A · incorrect — Unit testing isolates a function, class or small component.

B · incorrect — Integration testing focuses on interfaces and interactions among combined parts.

C · correct — System testing evaluates the complete integrated product in a representative environment.

D · incorrect — Regression names an after-change checking purpose and can run at multiple levels.

Question 205

What is a use case in use case modeling?

  • A. A description of a specific user interface design
  • B. A step-by-step procedure for software installation
  • C. A sequence of activities performed by a user or system
  • D. A diagram that represents the relationships between software components

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE14 · Actors, use cases and scope

Study-guide references

Correct answer: C — A sequence of activities performed by a user or system

A use case describes a system-provided function as a flow of events producing an actor-visible result. C is acceptable when understood as goal-related interactions, not any arbitrary sequence of activities.

Evidence in the complete study note

Draw actors outside the system boundary rectangle and use-case ovals inside. Name a goal with a verb and noun. The diagram shows roles, goals and relationships, not the full detailed algorithm or UI layout. Being an internal component is different from being an external actor; the chosen boundary determines which role applies.SE14

Choice by choice

A · incorrect — UI layout is an implementation/interface design artifact. See PDF p. 47, 48.

B · incorrect — Installation instructions are one possible documented procedure, not the general use-case definition. See PDF p. 47, 48.

C · correct — Best matches the goal-oriented flow of events involving actors and the system. See PDF p. 47, 48.

D · incorrect — Component relationships describe internal structure rather than actor-visible behavior. See PDF p. 47, 48.

Question 206

What is an actor in use-case modeling when the system boundary is fixed?

  • A. A component that performs specific actions in a software system
  • B. An external interacting role played by a person, device or another system.
  • C. A diagram that represents the flow of activities in a use case
  • D. A particular individual user account rather than a role.

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE14 · Actors, use cases and scope

Study-guide references

Correct answer: B — An external interacting role played by a person, device or another system.

An actor is an external role that interacts across the chosen system boundary. A person, device or another system may play that role. It is not an internal component, a diagram, or merely one individual user account. Because actors model roles rather than particular people, one person can play multiple actors and multiple people can fulfill the same actor role.

Evidence in the complete study note

Draw actors outside the system boundary rectangle and use-case ovals inside. Name a goal with a verb and noun. The diagram shows roles, goals and relationships, not the full detailed algorithm or UI layout. Being an internal component is different from being an external actor; the chosen boundary determines which role applies.SE14
An actor is an external role interacting with the system; it can be a person, device or another system. A person may play several roles, and several people may play one role.SE14

Choice by choice

A · incorrect — An internal component is not an external actor merely because it acts.

B · correct — The external interacting role is the actor.

C · incorrect — An activity-flow diagram is a model artifact rather than an actor.

D · incorrect — An individual account is not the role abstraction.

Question 207

What is the purpose of an include relationship between use cases?

  • A. To represent the reuse of common steps between use cases
  • B. To represent optional steps within a use case
  • C. To represent the extension of a use case with additional steps
  • D. To represent the relationship between actors and use cases

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE16 · Include, extend, generalization and abstract use cases

Study-guide references

Correct answer: A — To represent the reuse of common steps between use cases

Factoring common functionality into one included use case eliminates redundant descriptions, as in shared HelpDispatcher behavior.

Evidence in the complete study note

Include factors required reused behavior: Submit Order includes Validate Order, with the dashed arrow from the including/base use case to the included one. Extend adds conditional behavior at extension points: Apply Discount extends Checkout, with the arrow from the extension to the base. The base is meaningful independently. For an extension, draw the arrow from the extending use case to the base use case.SE16

Choice by choice

A · correct — Direct reuse/commonality mechanism. See PDF p. 50, 50.

B · incorrect — Optional exceptional behavior is more directly represented by extend. See PDF p. 50, 50.

C · incorrect — Adds events under conditions through extend rather than reuse via include. See PDF p. 50, 50.

D · incorrect — Actor/use-case communication uses associations, not include. See PDF p. 50, 50.

Question 208

Which statements describe extend between use cases? Select all that apply. Read optional as conditional behavior at an extension point.

  • A. To factor required reused steps into an included use case.
  • B. To represent optional steps within a use case
  • C. To represent the extension of a use case with additional steps
  • D. To represent the relationship between actors and use cases

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE16 · Include, extend, generalization and abstract use cases

Study-guide references

Correct answers (select all): B, C — To represent optional steps within a use case; To represent the extension of a use case with additional steps

Extend adds conditional behavior at extension points in an independently meaningful base use case. It therefore represents optional additional behavior and extends the base with added steps, making both B and C true. Factoring required reused behavior is the include relationship. Associations between actors and use cases are separate from the extend relationship linking use cases to one another.

Evidence in the complete study note

Include factors required reused behavior: Submit Order includes Validate Order, with the dashed arrow from the including/base use case to the included one. Extend adds conditional behavior at extension points: Apply Discount extends Checkout, with the arrow from the extension to the base. The base is meaningful independently. For an extension, draw the arrow from the extending use case to the base use case.SE16

Choice by choice

A · incorrect — Required reused behavior is factored with include.

B · correct — Conditional additional behavior need not occur in every base execution.

C · correct — Extend adds steps to an independently meaningful base.

D · incorrect — Actor association is a different relationship.

Question 209

Which diagram is commonly used to visualize the relationships between actors and use cases in use case modeling?

  • A. Class diagram
  • B. Use case diagram
  • C. Activity diagram
  • D. Sequence diagram

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE14 · Actors, use cases and scope

Study-guide references

Correct answer: B — Use case diagram

Use-case diagrams depict actors and use cases with communication associations; these are the requested external interaction relationships.

Evidence in the complete study note

Draw actors outside the system boundary rectangle and use-case ovals inside. Name a goal with a verb and noun. The diagram shows roles, goals and relationships, not the full detailed algorithm or UI layout. Being an internal component is different from being an external actor; the chosen boundary determines which role applies.SE14

Choice by choice

A · incorrect — Describes class structure. See PDF p. 47, 48.

B · correct — Direct actor/use-case representation. See PDF p. 47, 48.

C · incorrect — Describes action/control flow. See PDF p. 47, 48.

D · incorrect — Describes time-ordered object interactions, not the high-level actor/function map. See PDF p. 47, 48.

Question 210

What defines an abstract use case, rather than optionality, unfinished documentation or reuse alone?

  • A. To represent a use case that is not yet fully defined
  • B. To represent a use case that is optional in the system
  • C. It specifies behavior for specialization and is not directly instantiated as a complete use case.
  • D. To represent a use case that is reused by other use cases

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE16 · Include, extend, generalization and abstract use cases

Study-guide references

Correct answer: C — It specifies behavior for specialization and is not directly instantiated as a complete use case.

An abstract use case specifies behavior for specialization and is not directly instantiated as a complete use case. That is different from being unfinished, optional or reused. Concrete behavior can be included for reuse, and extend can express conditional additions. Nor does the absence of a direct actor line by itself establish abstraction. Option C states the actual defining criterion.

Evidence in the complete study note

Generalization relates a specialized actor/use case to a more general one, with a hollow triangle toward the general element. An abstract use case specifies behavior for specialization and is not directly instantiated as a complete use case. It is not defined merely by reuse or lack of a direct actor line. Included behavior is incorporated where the inclusion is reached; do not infer every conditional branch in the base always executes.SE16

Choice by choice

A · incorrect — An incomplete description is not the abstraction criterion.

B · incorrect — Optional behavior is not the abstraction criterion.

C · correct — Specialization without direct complete instantiation defines this abstraction.

D · incorrect — Reuse alone can also involve concrete use cases.

Question 211

Which option states the most specific defining purpose of an exception flow, distinguishing it from a generic alternative flow?

  • A. To represent an error or exceptional situation in the use case
  • B. To represent an alternative path within the use case
  • C. To represent the termination of the use case
  • D. To represent the relationship between primary and secondary actors

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE15 · Write a complete use case with alternatives

Study-guide references

Correct answer: A — To represent an error or exceptional situation in the use case

An exception flow handles an error or failure encountered in the use case. Such a path is also an alternative to the main success flow in a broad sense, but B alone does not distinguish exceptional handling from normal conditional variations. An exception may allow correction and recovery instead of terminating the use case. Actor relationships do not define its failure-handling purpose.

Evidence in the complete study note

Example: Submit Incident. Precondition: officer authenticated. 1 Officer supplies location and description. 2 System validates details. 3 System records the incident. 4 System returns its ID. Alternative 2a: location missing → report the problem and request correction; save nothing. Success postcondition: incident and ID persist; failure guarantee: no partial record. An alternate flow is a conditional variation; an exception flow handles a failure. Preconditions hold before entry, while a trigger starts the use case.SE15

Choice by choice

A · correct — Error or exceptional handling is the specific defining purpose.

B · incorrect — Alternative path is broader and does not identify the exceptional nature.

C · incorrect — Exceptions need not terminate the entire use case.

D · incorrect — Actor relationships do not describe failure handling.

Question 212

What is the primary goal of use case modeling?

  • A. To define the software architecture of the system
  • B. To identify and document user requirements
  • C. To design the user interface of the system
  • D. To implement the functionality of the system

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE14 · Actors, use cases and scope

Study-guide references

Correct answer: B — To identify and document user requirements

Use cases capture externally visible functionality and let developers validate requirements with users, rather than defining internal architecture or implementation.

Evidence in the complete study note

An actor is an external role interacting with the system; it can be a person, device or another system. A person may play several roles, and several people may play one role. A primary actor seeks a goal; a supporting actor provides a service. Ask which user groups perform main functions, administer or maintain the system, and which external systems exchange information.SE14

Choice by choice

A · incorrect — System design defines architecture after the external analysis model. See PDF p. 47, 62.

B · correct — Directly captures actor-visible functional requirements. See PDF p. 47, 62.

C · incorrect — UI layout can be explored alongside use cases but is not their primary purpose. See PDF p. 47, 62.

D · incorrect — Implementation realizes the requirements instead of documenting them. See PDF p. 47, 62.

Question 213

What is an alternative flow in a use case?

  • A. A flowchart representation of the use case steps
  • B. A flow of activities that occurs in parallel with the main flow
  • C. A different sequence of steps based on specific conditions
  • D. A representation of the relationship between use cases

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE15 · Write a complete use case with alternatives

Study-guide references

Correct answer: C — A different sequence of steps based on specific conditions

A flow of events describes interactions; exceptional conditions introduce alternative event sequences. This is a different path under a condition, rather than necessarily concurrency or inter-use-case structure.

Evidence in the complete study note

Example: Submit Incident. Precondition: officer authenticated. 1 Officer supplies location and description. 2 System validates details. 3 System records the incident. 4 System returns its ID. Alternative 2a: location missing → report the problem and request correction; save nothing. Success postcondition: incident and ID persist; failure guarantee: no partial record. An alternate flow is a conditional variation; an exception flow handles a failure. Preconditions hold before entry, while a trigger starts the use case.SE15

Choice by choice

A · incorrect — A flowchart is a representation format, not the alternative sequence itself. See PDF p. 48, 50.

B · incorrect — Parallel execution is not required by an alternative branch. See PDF p. 48, 50.

C · correct — Directly describes a condition-dependent event sequence. See PDF p. 48, 50.

D · incorrect — Include/extend/generalization describe relationships, not the definition of every alternative flow. See PDF p. 48, 50.

Question 214

What is the purpose of a use case diagram?

  • A. To describe the behavior of a use case in detail
  • B. To represent the internal structure of a use case
  • C. To visualize the relationships between actors and use cases
  • D. To represent the flow of activities within a use case

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE14 · Actors, use cases and scope

Study-guide references

Correct answer: C — To visualize the relationships between actors and use cases

The diagram shows actors, functions and communication links; the separate textual template contains detailed event sequences and conditions.

Evidence in the complete study note

Draw actors outside the system boundary rectangle and use-case ovals inside. Name a goal with a verb and noun. The diagram shows roles, goals and relationships, not the full detailed algorithm or UI layout. Being an internal component is different from being an external actor; the chosen boundary determines which role applies.SE14

Choice by choice

A · incorrect — Detailed flow belongs in the use-case description/template. See PDF p. 47, 48.

B · incorrect — Internal structure is modeled with classes/components. See PDF p. 47, 48.

C · correct — Direct high-level actor/function interaction view. See PDF p. 47, 48.

D · incorrect — Activity diagrams or textual flows express detailed action sequences. See PDF p. 47, 48.

Question 215

Identifying and describing the fundamental software system abstractions and their relationships. Establishing the overall system architecture — in which phase are these activities done?

  • A. System design
  • B. Requirement analysis and definition
  • C. System testing
  • D. Implementation

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE21 · Design and subsystem decomposition

Study-guide references

Correct answer: A — System design

System and software design establish the overall architecture and identify software abstractions and relationships.

Evidence in the complete study note

System design turns the analysis model into architecture: design goals, subsystem responsibilities, dependencies, hardware mapping, data management, access control, control flow and startup/shutdown/error policies. Detail/object design refines APIs, parameter/return types, exceptions, component choices and algorithms. A subsystem is a manageable logical collection with services and an interface; it need not be a physical replaceable artifact.SE21

Choice by choice

A · correct — Direct match to the described design tasks. See PDF p. 18, 116.

B · incorrect — Establishes required services, constraints and goals. See PDF p. 18, 116.

C · incorrect — Checks complete-system behavior. See PDF p. 18, 116.

D · incorrect — Translates a design into code. See PDF p. 18, 116.

Question 216

Instead of delivering the system as a single delivery, development and delivery is broken down into phases with each phase delivering part of the required functionality. What type of development model is this?

  • A. Incremental
  • B. Waterfall
  • C. Spiral
  • D. Evolutionary

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE04 · Iteration, increments and early delivery

SE06 · Spiral development and risk

Study-guide references

Correct answer: A — Incremental

Successive deliveries that each add part of the required usable functionality define incremental development. The product gains capability across these deliveries rather than waiting for a single completed-system handoff. Waterfall and a generic linear model organize phase sequence. Spiral is organized around risk assessment, and evolutionary development broadly describes refinement. Those can overlap with staged delivery, but incremental is the specific name for the delivery organization stated.

Evidence in the complete study note

Choose incremental delivery when prioritized partial capability must reach users early. Smaller changes can be easier to debug and permit feedback, though architecture and integration still require planning. Iteration need not rebuild the whole system every time, and increments need not be perfectly independent modules. Broad descriptions of early working software can fit prototypes, iterative or Agile processes; identify the purpose of that early version.SE04
Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06

Choice by choice

A · correct — Incremental development adds usable required functionality in successive deliveries.

B · incorrect — Waterfall names planned phase progression, not this particular staged-capability strategy.

C · incorrect — Spiral names risk-driven cycles, even when increments are produced.

D · incorrect — Evolutionary refinement is broader than the specific addition-of-functionality strategy described.

Question 217

We should NOT use the Waterfall software development process model in situations like:

  • A. Plenty of resources with required expertise are available freely
  • B. There are no ambiguous requirements
  • C. The project is short
  • D. Software requirements change quickly

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE03 · Waterfall and the V-model

Study-guide references

Correct answer: D — Software requirements change quickly

Waterfall should be used only when requirements are well understood and unlikely to change radically. Rapid requirement change violates this selection condition.

Evidence in the complete study note

Classical waterfall separates planned phases with reviewed deliverables. It fits well-understood, stable requirements and familiar technology; late feedback makes changes costly. It does not make change physically impossible: real projects revisit work under control, and modified waterfall explicitly includes feedback. Rigidity offers milestone visibility but can freeze incorrect assumptions.SE03

Choice by choice

A · incorrect — Available expertise is not the documented contraindication. See PDF p. 20.

B · incorrect — Unambiguous stable requirements support, rather than undermine, the model. See PDF p. 20.

C · incorrect — The module says waterfall works well for smaller projects with well-understood requirements. See PDF p. 20.

D · correct — Directly violates the stability assumption and creates costly rework. See PDF p. 20.

Question 218

Which one of the following is false about divide and conquer or modularization process?

  • A. Separate people can work on each sub-divided part
  • B. Opportunities arise for making the component reusable
  • C. Each individual component is smaller, and therefore easier to understand
  • D. Replacing or changing a component is difficult because it affects other parts extremely

Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

Study-guide sections

SE22 · Cohesion, coupling, modularity and refactoring

Study-guide references

Correct answer: D — Replacing or changing a component is difficult because it affects other parts extremely

Subsystems can be assigned to separate teams, reused and changed with reduced impact when coupled loosely. D contradicts the change-isolation goal of good modularization.

Evidence in the complete study note

Logical cohesion groups similar-category operations, often selected by a flag; temporal cohesion groups operations done at the same time; functional cohesion focuses on one task. Splitting an unrelated three-purpose component improves modularity. If behavior is preserved, the restructuring is refactoring; the words are not mutually exclusive answers. Smaller modules can aid understanding, independent work, reuse and maintenance, but too many interfaces also create complexity.SE22

Choice by choice

A · incorrect — Independent teams can realize different manageable subsystems. See PDF p. 118, 116, 32, 120.

B · incorrect — Reusable self-contained modules are an explicit OO benefit. See PDF p. 118, 116, 32, 120.

C · incorrect — Decomposition produces simpler manageable units. See PDF p. 118, 116, 32, 120.

D · correct — Strong propagation of every change describes undesirable tight coupling, not good modularization. See PDF p. 118, 116, 32, 120.

Question 219

For this project, planned testing effort in hours is setup + (cases × hours per case). The estimates (setup,cases,hours/case) are Unit=(4,80,0.1), Acceptance=(3,10,1), System=(6,20,0.5), Integration=(4,20,0.5). Which level has the greatest planned effort?

  • A. Unit testing
  • B. Acceptance testing
  • C. System testing
  • D. Integration testing

Use the effort formula given in the question separately for every level, then compare all computed totals.

Study-guide sections

SE35 · Testing levels and acceptance

SE28 · Planning, WBS, estimation and tools

Study-guide references

Correct answer: C — System testing

The estimates give unit effort 4+80×0.1=12 hours, acceptance 3+10×1=13, system 6+20×0.5=16, and integration 4+20×0.5=14. System testing therefore has the greatest planned effort for this project. The note does not make any test level universally longest; the explicit workload and setup assumptions are what justify this particular ranking.

Evidence in the complete study note

Unit testing isolates a function, class or small component, often replacing dependencies with stubs/mocks; a driver invokes the unit and a stub substitutes a called dependency. Integration testing exercises interfaces and interactions among combined parts. System testing checks the complete integrated system against functional and nonfunctional requirements in a representative environment.SE35
None of these levels is universally the longest.SE35
Planning is continuous: identify scope/deliverables, decompose work, estimate effort/duration/cost, assign resources, sequence dependencies and revise as evidence changes.SE28

Choice by choice

A · incorrect — Unit totals twelve hours, below the maximum.

B · incorrect — Acceptance totals thirteen hours, below the maximum.

C · correct — System totals sixteen hours, the largest estimate.

D · incorrect — Integration totals fourteen hours, below system testing.

Question 220

A filled composition diamond is at Car’s end of its Engine association. In this model Engine remains owned for its entire lifetime and cannot be detached or transferred. What does this imply?

  • A. Car uses Engine temporarily
  • B. Engine can exist independently of the Car
  • C. Engine is part of Car and cannot exist independently under the stated lifetime policy.
  • D. Car inherits from Engine

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE18 · Association, aggregation, composition and generalization

Study-guide references

Correct answer: C — Engine is part of Car and cannot exist independently under the stated lifetime policy.

Composition makes Engine a strongly owned part of Car, with the filled diamond beside the whole. Parts still owned are destroyed when their composite is destroyed. Since this model does not permit Engine to detach or transfer, it cannot continue an independent lifetime without Car. Temporary use would be a dependency, and inheritance would be shown by a hollow triangle.

Evidence in the complete study note

Composition uses a filled diamond at the whole end and strong ownership: a part is in at most one composite at a time, and parts still owned are destroyed with that composite. Parts may be detached/transferred under a defined model. Thus “cannot ever exist independently” is an oversimplification. For Car composing Engine, the diamond belongs beside Car; saying it points to Engine is imprecise. The Car–Engine example describes composition.SE18

Choice by choice

A · incorrect — Temporary use is a dependency rather than composition.

B · incorrect — The no-detachment policy excludes an independent Engine lifetime.

C · correct — Engine is Car’s owned part and cannot outlive it under this policy.

D · incorrect — Inheritance uses a hollow triangle.

Question 221

From the following statement which one is disadvantage of waterfall model?

  • A. model is simple and easy to understand and use
  • B. It is easy manage due to the rigidity of the model
  • C. Not suitable for projects where requirements are at a moderate to high risk of changing
  • D. In this model phases are processed and completed one at a time

Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

Study-guide sections

SE03 · Waterfall and the V-model

Study-guide references

Correct answer: C — Poor suitability when requirements have substantial change risk.

SE03 says waterfall fits stable understood requirements and familiar technology. Late feedback can make changes costly, so moderate-to-high requirement-change risk is a direct disadvantage. Simplicity and milestone visibility are advantages. Sequential phase organization characterizes the classical model; it can contribute to rigidity, but C explicitly identifies the adverse scenario asked for.

Evidence in the complete study note

Classical waterfall separates planned phases with reviewed deliverables. It fits well-understood, stable requirements and familiar technology; late feedback makes changes costly. It does not make change physically impossible: real projects revisit work under control, and modified waterfall explicitly includes feedback. Rigidity offers milestone visibility but can freeze incorrect assumptions.SE03

Choice by choice

A · incorrect — Simplicity and ease of understanding are presented as advantages rather than the adverse scenario.

B · incorrect — Manageable milestones can be an advantage of planned rigidity, despite its trade-offs.

C · correct — Likely requirement changes make late feedback and rigid commitments costly.

D · incorrect — Sequential phases describe the model; C more directly states the requested disadvantage.

Question 222

For a search service whose functions and database technology are already specified, which requirement adds a quantitative service-speed target?

  • A. The system allow user to generate PDF report.
  • B. The system respond to user’s request within 2 second under normal load
  • C. The system allow user to store data on relational database
  • D. The system allow user to submit emergency report

Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

Study-guide sections

SE10 · Nonfunctional qualities and measurable constraints

Study-guide references

Correct answer: B — The system respond to user’s request within 2 second under normal load

The two-second response obligation bounds the speed of a service under the stated load, so it is a performance requirement. Generating a PDF and submitting an emergency report describe services the system provides. The database clause describes storage behavior together with an implementation choice; it does not impose a response-time threshold. The explicit performance scope removes the broader taxonomy overlap between nonfunctional requirements and technology constraints.

Evidence in the complete study note

Nonfunctional requirements include quality attributes and constraints. Performance concerns response time, throughput and resource use; reliability concerns failure-free service; availability concerns being ready for use; usability concerns task success and ease of learning. Security concerns protection; compatibility concerns cooperating environments; portability concerns moving environments; maintainability/supportability concern change, diagnosis and evolution.SE10
“Search responds within two seconds under 100 concurrent users” is measurable performance. “New users finish checkout within one minute without help” is usability. “Use Java” is a technology/pseudo-requirement, often separately classified as a system constraint. Dependability includes reliability, safety and robustness; portability is not its usual central category. Performance degradation at peak load primarily concerns performance, not automatically reliability.SE10

Choice by choice

A · incorrect — Report generation specifies a service, not its response-time limit.

B · correct — A two-second response bound under normal load is a quantitative speed target.

C · incorrect — This specifies storage behavior and a database technology, without a timing bound.

D · incorrect — Submitting an emergency report specifies a function rather than its speed.

Question 223

Which one of the following UML building block that defines the static part of the model and represents physical and conceptual elements?

  • A. Structural things
  • B. Behavioral things
  • C. An notational things
  • D. Grouping things

Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

Study-guide sections

SE17 · Class diagrams, visibility and multiplicity

SE-S03 · Modeling categories and data diagrams

Study-guide references

Correct answer: A — Structural things.

SE17 explicitly describes structural things as conceptual or physical structural elements. They make up the static model in contrast with behavior over time. Behavioral things cover dynamic aspects, grouping organizes elements and annotations add explanatory information rather than being the static elements themselves. Thus A directly matches both parts of the definition.

Evidence in the complete study note

A class box lists name, attributes and operations; + public, - private, # protected and ~ package indicate visibility. A class diagram shows static types and relationships, while an object diagram shows particular instances/links. UML is maintained and standardized by OMG; it is a modeling language, not a lifecycle process. Structural things describe conceptual or physical structural elements.SE17
In the course’s UML building-block terminology, structural things describe static conceptual or physical elements. Behavioral things describe dynamic interactions and state behavior. Grouping things organize model elements into packages. Annotational things attach explanatory remarks or constraints, usually as notes.SE-S03

Choice by choice

A · correct — Structural things are the static conceptual or physical building blocks described.

B · incorrect — Behavioral things concern dynamic behavior rather than the static structural elements.

C · incorrect — Annotations add explanatory information rather than defining the static structural building blocks.

D · incorrect — Grouping organizes model elements rather than being the stated conceptual/physical structural category.

Question 224

What is the difference between functional and non-functional requirements? Give an example of each.

    Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

    Study-guide sections

    SE09 · Functional requirements include prohibited behavior

    SE10 · Nonfunctional qualities and measurable constraints

    Study-guide references

    Answer: Functional requirements specify observable behavior; nonfunctional requirements specify qualities or constraints. Example: generate a PDF report versus respond within two seconds under a stated load.

    SE09 includes required and prohibited services, so generating a PDF report is functional. SE10 specifies qualities such as performance, usability and availability; a response-time threshold under defined load is nonfunctional. Security mechanisms can implement functional behavior as well as support quality goals, so a negative or security-related statement is not automatically nonfunctional.

    Evidence in the complete study note

    A functional requirement states an observable service or behavior, including reactions to inputs, errors and forbidden actions. “When the sensor detects intrusion, send an alert” is functional.SE09
    “The system shall generate a PDF report” is functional. “The system shall not reveal another customer’s balance” can be a security-related functional rule. Security as a broad quality goal and the functions implementing it must be distinguished.SE09
    Nonfunctional requirements include quality attributes and constraints. Performance concerns response time, throughput and resource use; reliability concerns failure-free service; availability concerns being ready for use; usability concerns task success and ease of learning.SE10
    “Search responds within two seconds under 100 concurrent users” is measurable performance. “New users finish checkout within one minute without help” is usability.SE10

    Question 225

    Why is low coupling considered good in software design?

      Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

      Study-guide sections

      SE22 · Cohesion, coupling, modularity and refactoring

      Study-guide references

      Answer: Low coupling limits dependencies, so changes remain local and modules are easier to understand, replace, test and maintain.

      SE22 measures coupling through dependencies between modules and recommends low coupling with high cohesion. Shared mutable data and knowledge of another module’s representation increase the chance that one change affects others. Stable interfaces and information hiding constrain that impact. More interfaces can add complexity, so minimizing harmful dependencies matters more than simply maximizing the number of modules.

      Evidence in the complete study note

      Cohesion measures how well elements inside a module serve a related purpose; coupling measures dependency between modules. Seek high cohesion and low coupling. Shared mutable data and knowledge of another module’s internal representation increase coupling. Information hiding exposes stable operations while concealing changeable decisions.SE22

      Question 226

      What is the difference between Waterfall and Agile methodologies?

        Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

        Study-guide sections

        SE03 · Waterfall and the V-model

        SE05 · Agile values, stories and Scrum

        Study-guide references

        Answer: Waterfall uses planned, reviewed stages and suits stable requirements; Agile emphasizes collaboration, working results, feedback and adaptation.

        SE03 describes planned phases with costly late feedback, useful for stable requirements and familiar technology. SE05 values customer participation and adaptation with useful working increments. Agile still plans and documents; waterfall can revisit work under control. The practical difference is feedback and commitment organization, not a claim that one process forbids change or the other forbids documentation.

        Evidence in the complete study note

        Classical waterfall separates planned phases with reviewed deliverables. It fits well-understood, stable requirements and familiar technology; late feedback makes changes costly. It does not make change physically impossible: real projects revisit work under control, and modified waterfall explicitly includes feedback. Rigidity offers milestone visibility but can freeze incorrect assumptions.SE03
        Agile favors people collaborating, useful working results, customer participation and adaptation over rigid adherence to procedures, exhaustive documents, contracts or fixed plans. The latter still have value. Agile does not mean no planning or no documentation. A user story states a small user need and value, supported by acceptance criteria; an epic groups broader work.SE05

        Question 227

        What is the difference between <<include>> and <<extend>> in use case diagrams?

          Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

          Study-guide sections

          SE16 · Include, extend, generalization and abstract use cases

          Study-guide references

          Answer: Include factors required reused behavior, with base→included; extend adds conditional behavior, with extension→base.

          SE16 uses include for reused required behavior incorporated when the inclusion point is reached. Extend adds behavior at extension points under a condition, and the base remains meaningful independently. The dashed arrows have different directions: including use case toward included, and extending use case toward base. Neither relation should be confused with actor association or specialization generalization.

          Evidence in the complete study note

          Include factors required reused behavior: Submit Order includes Validate Order, with the dashed arrow from the including/base use case to the included one. Extend adds conditional behavior at extension points: Apply Discount extends Checkout, with the arrow from the extension to the base. The base is meaningful independently. For an extension, draw the arrow from the extending use case to the base use case.SE16
          Generalization relates a specialized actor/use case to a more general one, with a hollow triangle toward the general element. An abstract use case specifies behavior for specialization and is not directly instantiated as a complete use case. It is not defined merely by reuse or lack of a direct actor line. Included behavior is incorporated where the inclusion is reached; do not infer every conditional branch in the base always executes.SE16

          Question 228

          Why is maintenance often the most expensive phase of the SDLC?

            Classify the motive for the change before its implementation: repair, environment, useful capability or reduced future risk.

            Study-guide sections

            SE40 · Maintenance and software evolution

            Study-guide references

            Answer: Maintenance can dominate cost because it lasts years and repeatedly requires legacy understanding, changes, regression testing and release work.

            SE40 says maintenance often spans years and includes understanding existing code plus regression effort. Work is not limited to bug fixes: environments, useful capabilities and future risks also change. Repeated impact analysis, implementation and testing accumulate across the operational lifetime, so maintenance may dominate lifecycle cost. This is a common outcome, not a guarantee for every project.

            Evidence in the complete study note

            Corrective maintenance fixes faults; adaptive maintenance responds to environment changes; perfective maintenance improves useful capability/performance; preventive maintenance reduces future risk, such as restructuring fragile code. Motive determines category; refactoring can support preventive or perfective work. Maintenance often lasts years and includes understanding legacy code and regression effort, so it may dominate lifecycle cost.SE40
            A typical evolution sequence is change request→impact analysis→release planning→implementation/testing→release. Among a list lacking the request step, impact analysis may be the earliest listed technical activity. Major restructuring is reengineering; if the architecture itself changes, architectural transformation is the more specific description. Markets, technology, stakeholders and funding can all change scope or priorities.SE40

            Question 229

            Which software development approach emphasizes breaking systems into functions or procedures that manipulate isolated data?

            • A. Object-Oriented Approach
            • B. Traditional Approach
            • C. Agile Approach
            • D. Iterative Approach

            Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

            Study-guide sections

            SE01 · Software engineering, processes and work products

            Study-guide references

            Correct answer: B — Traditional/procedural decomposition.

            SE01 contrasts procedural decomposition organized around functions with object-oriented decomposition organized around objects combining state and behavior. B is the available traditional/procedural label for functions operating on data. Agile and iterative describe lifecycle organization rather than this decomposition paradigm, and either can be used with procedural or object-oriented programming.

            Evidence in the complete study note

            Procedural decomposition organizes functions; object oriented decomposition organizes objects with state and behavior. Either can use iterative or sequential development. OOP does not automatically shorten every project. Reuse, encapsulation and consistent models can reduce duplication and ease change; poor object design can still be complex. Functional programming emphasizes function evaluation and controlled side effects; event-driven programs react to events.SE01

            Choice by choice

            A · incorrect — Object orientation combines state and behavior in objects rather than organizing primarily around separate procedures.

            B · correct — Traditional/procedural decomposition organizes functions and procedures acting on data.

            C · incorrect — Agile concerns process adaptation rather than requiring function-based decomposition.

            D · incorrect — Iteration describes revisiting development work and does not determine procedural versus object decomposition.

            Question 230

            In the Object-Oriented Approach, which property allows classes to be used in different parts of the system or other projects without rewriting them?

            • A. Encapsulation
            • B. Polymorphism
            • C. Reusability
            • D. Abstraction

            Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

            Study-guide sections

            SE-S02 · Objects, shared models and specialization

            Study-guide references

            Correct answer: C — Reusability.

            The stem explicitly asks about using existing classes elsewhere without rewriting them, which is reuse. SE01 lists reuse alongside encapsulation and consistent models as ways to reduce duplication and ease change. Encapsulation and abstraction can make reuse safer, while polymorphism supports compatible varying implementations, but those are enabling concepts rather than the name of the capability described.

            Evidence in the complete study note

            Encapsulation groups state with operations and hides representation behind an interface. Polymorphism permits different object types to respond differently through a common operation or interface. Abstraction exposes the relevant contract while omitting unnecessary detail. Reusability means using suitable existing classes or components in new contexts rather than writing them again. These ideas support each other but name different properties.SE-S02

            Choice by choice

            A · incorrect — Encapsulation hides implementation and can enable reuse, but it is not the capability's name.

            B · incorrect — Polymorphism supports differing implementations through compatible interfaces rather than directly naming reuse.

            C · correct — Reusability means using suitable existing classes or components in other contexts without rewriting them.

            D · incorrect — Abstraction exposes relevant contracts and can assist reuse, but the requested property is reusability.

            Question 231

            Which of the four fundamental software process activities involves making updates to meet changing customer needs after deployment?

            • A. Software Specification
            • B. Software Design and Implementation
            • C. Software Validation
            • D. Software Evolution

            Classify the motive for the change before its implementation: repair, environment, useful capability or reduced future risk.

            Study-guide sections

            SE40 · Maintenance and software evolution

            Study-guide references

            Correct answer: D — Software evolution.

            SE40 describes maintenance and evolution through change requests, impact analysis, planning, implementation/testing and release. Updating a deployed product to meet changing customer needs belongs to evolution among the four broad process activities. Specification, implementation and validation still occur within that work, but D names the lifecycle-wide change activity asked for rather than one constituent task.

            Evidence in the complete study note

            Corrective maintenance fixes faults; adaptive maintenance responds to environment changes; perfective maintenance improves useful capability/performance; preventive maintenance reduces future risk, such as restructuring fragile code. Motive determines category; refactoring can support preventive or perfective work. Maintenance often lasts years and includes understanding legacy code and regression effort, so it may dominate lifecycle cost.SE40
            A typical evolution sequence is change request→impact analysis→release planning→implementation/testing→release.SE40

            Choice by choice

            A · incorrect — Specification captures needs but does not name the overall postdeployment change activity.

            B · incorrect — Design/implementation is part of making a change rather than the broad evolution activity.

            C · incorrect — Validation checks the changed product against needs rather than naming ongoing adaptation itself.

            D · correct — Evolution updates existing software as stakeholder needs and operating conditions change.

            Question 232

            A software process that plans all activities in advance and measures progress against that plan is classified as:

            • A. Agile Process
            • B. Plan-Driven Process
            • C. Incremental Process
            • D. Evolutionary Process

            Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

            Study-guide sections

            SE-S04 · Plan-driven and adaptive planning

            Study-guide references

            Correct answer: B — Plan-driven process.

            The stem defines up-front planning and measurement against that plan. B names the plan-driven organization, illustrated by SE03’s planned phases and reviewed deliverables. Incremental delivery and evolution describe how results grow or change and can coexist with planning. Agile also plans, but it emphasizes adaptation rather than defining all activity commitments in advance as stated here.

            Evidence in the complete study note

            In a plan-driven process, activities are planned in advance and progress is assessed against that plan. Agile planning is incremental and adapts to changing needs. This distinction concerns planning strategy; a process can combine advance planning with staged deliveries and feedback.SE-S04

            Choice by choice

            A · incorrect — Agile uses planning but adapts content as feedback arrives rather than defining this fixed up-front emphasis.

            B · correct — Plan-driven explicitly organizes activities and progress measurement around an advance plan.

            C · incorrect — Incremental describes staged capability delivery and does not alone specify up-front planning commitments.

            D · incorrect — Evolutionary describes progressive change rather than necessarily advance planning of all activities.

            Question 233

            In requirement elicitation, the document created to describe what the system should do — agreed upon by clients and developers — is called:

            • A. Analysis Model
            • B. Use Case Diagram
            • C. Requirements Specification
            • D. Design Document

            Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

            Study-guide sections

            SE08 · Feasibility and levels of requirements

            Study-guide references

            Correct answer: C — Requirements Specification.

            SE08 states that the Software Requirements Specification organizes agreed requirements. That is the artifact describing what the system should do for client/developer agreement. Analysis models support technical discussion, a use-case diagram captures only selected goals/relationships and a design document describes solution decisions. None replaces the overall agreed requirements specification.

            Evidence in the complete study note

            Business requirements explain why the project exists and its goals. User requirements describe stakeholder needs at a useful high level; system requirements specify detailed services and constraints. The Software Requirements Specification (SRS) organizes the agreed requirements. A natural-language specification communicates with clients while analysis models formalize it for technical discussion; real specifications can also contain diagrams.SE08

            Choice by choice

            A · incorrect — Analysis models formalize selected aspects for discussion rather than replacing the full agreed requirements document.

            B · incorrect — A use-case diagram shows goals and roles but not the complete requirements specification.

            C · correct — The requirements specification organizes the agreed services and constraints the system must satisfy.

            D · incorrect — A design document describes how the solution is organized rather than the complete statement of required behavior.

            Question 234

            What is the key distinction between a Requirements Specification and an Analysis Model?

            • A. The specification uses diagrams; the model uses natural language
            • B. The specification uses natural language; the model uses symbols and diagrams
            • C. Both use the same representation but serve different purposes
            • D. The analysis model is only for developers; specification is for testing

            Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

            Study-guide sections

            SE08 · Feasibility and levels of requirements

            Study-guide references

            Correct answer: B — In the taught convention, natural-language client specification versus symbolic/diagrammatic analysis models.

            SE08 explicitly describes natural-language specification for clients and analysis models that formalize it for technical discussion. B matches that teaching convention. This is not a universal ban on diagrams in an SRS: the note immediately allows them in real specifications. The other choices reverse the convention or impose unsupported exclusive audiences and purposes.

            Evidence in the complete study note

            Business requirements explain why the project exists and its goals. User requirements describe stakeholder needs at a useful high level; system requirements specify detailed services and constraints. The Software Requirements Specification (SRS) organizes the agreed requirements. A natural-language specification communicates with clients while analysis models formalize it for technical discussion; real specifications can also contain diagrams.SE08

            Choice by choice

            A · incorrect — It reverses the natural-language specification versus formalized-model convention taught in the note.

            B · correct — This matches the taught convention, while real requirements specifications can also include diagrams.

            C · incorrect — The taught distinction does use different representation emphases rather than identical forms.

            D · incorrect — Neither artifact has the exclusive audience or testing-only purpose asserted here.

            Question 235

            In use case modeling, actors can be defined as:

            • A. Only human users who interact with the system
            • B. People, machines, or external systems that interact with the system
            • C. Only primary users who need system assistance
            • D. Software components within the system boundary

            Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

            Study-guide sections

            SE14 · Actors, use cases and scope

            Study-guide references

            Correct answer: B — External interacting roles played by people, devices or other systems.

            SE14 explicitly permits a person, device or other system to play an external actor role. B is the only option including those categories. Actors are not restricted to primary users or humans, and internal components are inside the chosen system boundary rather than external roles. One person may play several actors, so actor instances should not be confused with individual people.

            Evidence in the complete study note

            Draw actors outside the system boundary rectangle and use-case ovals inside. Name a goal with a verb and noun. The diagram shows roles, goals and relationships, not the full detailed algorithm or UI layout. Being an internal component is different from being an external actor; the chosen boundary determines which role applies.SE14
            An actor is an external role interacting with the system; it can be a person, device or another system.SE14

            Choice by choice

            A · incorrect — Actors can be devices or external systems as well as human users.

            B · correct — People, devices and external systems can play roles interacting across the system boundary.

            C · incorrect — Supporting and administrative external roles can be actors, not only primary goal-seeking users.

            D · incorrect — Internal components are not external actor roles under the chosen system boundary.

            Question 236

            Which type of requirement specifies that 'the system must respond within 1 second'?

            • A. Functional Requirement
            • B. System Constraint
            • C. Non-Functional Requirement
            • D. Domain Requirement

            Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

            Study-guide sections

            SE10 · Nonfunctional qualities and measurable constraints

            Study-guide references

            Correct answer: C — Nonfunctional performance requirement.

            SE10 identifies response time as a performance quality. A one-second threshold constrains how well a service responds rather than naming the service itself, so C is the appropriate category. A complete measurable requirement should also define the operation, load and timing conditions. Those omissions affect test precision, not the underlying classification of the stated response-time target.

            Evidence in the complete study note

            Nonfunctional requirements include quality attributes and constraints. Performance concerns response time, throughput and resource use; reliability concerns failure-free service; availability concerns being ready for use; usability concerns task success and ease of learning. Security concerns protection; compatibility concerns cooperating environments; portability concerns moving environments; maintainability/supportability concern change, diagnosis and evolution.SE10

            Choice by choice

            A · incorrect — The statement constrains response speed rather than specifying which service is performed.

            B · incorrect — The specific quality is performance; this is not primarily a technology or implementation constraint.

            C · correct — The one-second limit is a nonfunctional response-time/performance target.

            D · incorrect — No domain-specific business rule is stated; the obligation concerns a general performance quality.

            Question 237

            When technology constraints are separated from quality attributes, what is the most specific category for “the system must be built using Java”?

            • A. Functional Requirement
            • B. Non-Functional Requirement
            • C. System/Constraint Requirement
            • D. Quality Requirement

            Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

            Study-guide sections

            SE10 · Nonfunctional qualities and measurable constraints

            Study-guide references

            Correct answer: C — System/Constraint Requirement

            The statement prescribes an implementation technology rather than an externally observable service or a measurable product quality. In the course’s explicit separation of quality attributes from technology constraints, the specific category is a system or constraint requirement. A broad requirements taxonomy can place constraints under nonfunctional requirements, but the question asks for the more specific category. No performance, reliability or usability threshold is supplied by merely naming Java.

            Evidence in the complete study note

            “Search responds within two seconds under 100 concurrent users” is measurable performance. “New users finish checkout within one minute without help” is usability. “Use Java” is a technology/pseudo-requirement, often separately classified as a system constraint. Dependability includes reliability, safety and robustness; portability is not its usual central category. Performance degradation at peak load primarily concerns performance, not automatically reliability.SE10

            Choice by choice

            A · incorrect — The statement prescribes technology rather than an observable service.

            B · incorrect — This is a broader umbrella in some taxonomies; it is incomplete when the specific constraint category is offered.

            C · correct — A required implementation language is a technology or system constraint.

            D · incorrect — No measurable quality attribute is specified merely by requiring Java.

            Question 238

            Which nonfunctional requirement category addresses the ability of the system to work across different web browsers and devices?

            • A. Reliability
            • B. Scalability
            • C. Usability
            • D. Compatibility

            Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

            Study-guide sections

            SE10 · Nonfunctional qualities and measurable constraints

            SE-S07 · Scalability and robustness are different qualities

            Study-guide references

            Correct answer: D — Compatibility.

            SE10 distinguishes compatibility, which concerns cooperating environments, from portability, which concerns moving environments. Supporting different browsers and devices in the question is the offered compatibility category. Reliability concerns failure-free service, scalability concerns growth and usability concerns task success/ease of learning. None of those names the stated cross-environment cooperation requirement as directly.

            Evidence in the complete study note

            Nonfunctional requirements include quality attributes and constraints. Performance concerns response time, throughput and resource use; reliability concerns failure-free service; availability concerns being ready for use; usability concerns task success and ease of learning. Security concerns protection; compatibility concerns cooperating environments; portability concerns moving environments; maintainability/supportability concern change, diagnosis and evolution.SE10
            Scalability is the ability to accommodate additional workload while maintaining the required service, often by increasing available resources. It concerns growth in demand. Compatibility concerns supported cooperating environments, such as browsers and devices; usability concerns successful and learnable user tasks.SE-S07

            Choice by choice

            A · incorrect — Reliability concerns failure-free service rather than which browsers and devices can cooperate with the system.

            B · incorrect — Scalability concerns handling increased workload rather than cross-browser/device compatibility.

            C · incorrect — Usability concerns ease of learning and successful tasks, not the supported environment set itself.

            D · correct — Compatibility addresses operating/cooperating across the specified browsers and device environments.

            Question 239

            Dependability in software engineering is a broader concept that includes all of the following EXCEPT:

            • A. Reliability
            • B. Robustness
            • C. Safety
            • D. Portability

            Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

            Study-guide sections

            SE10 · Nonfunctional qualities and measurable constraints

            SE-S07 · Scalability and robustness are different qualities

            Study-guide references

            Correct answer: D — Portability is the exception to the usual central dependability categories.

            SE10 explicitly includes reliability, safety and robustness in dependability and says portability is not its usual central category. Portability instead concerns moving environments. Thus D is the listed exception. The distinction does not imply portability never affects practical service outcomes, only that it is a different quality category from the taught dependability grouping.

            Evidence in the complete study note

            Dependability includes reliability, safety and robustness; portability is not its usual central category.SE10
            Security concerns protection; compatibility concerns cooperating environments; portability concerns moving environments; maintainability/supportability concern change, diagnosis and evolution.SE10
            Robustness concerns reliable operation across varied or difficult operating conditions and controlled failure outside the supported range.SE-S07

            Choice by choice

            A · incorrect — Reliability is explicitly included in the taught dependability grouping.

            B · incorrect — Robustness is explicitly included in the broader dependability concept.

            C · incorrect — Safety is explicitly included among dependability concerns.

            D · correct — Portability concerns moving environments rather than the usual central dependability categories.

            Question 240

            In requirements elicitation activities, which step involves formalizing scenarios into structured descriptions of system interactions?

            • A. Identifying Actors
            • B. Identifying Use Cases
            • C. Identifying Scenarios
            • D. Refining Use Cases

            Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

            Study-guide sections

            SE13 · From scenarios to analysis objects

            Study-guide references

            Correct answer: B — Identifying use cases by abstracting concrete scenarios.

            SE13 calls a scenario one concrete execution and a use case an abstraction of related success and alternative scenarios. Formalizing those interactions into the more general use-case description therefore identifies use cases. Identifying actors establishes external roles, identifying scenarios captures individual executions and later refinement adds detail to an already identified use case.

            Evidence in the complete study note

            A scenario is one concrete execution; a use case abstracts the related successful and alternative scenarios. Analysis integrates functional (use cases/scenarios), structural/object (classes) and dynamic (states/interactions) models. Entity objects represent domain information such as Incident; boundary objects mediate interaction, such as ReportForm; control objects coordinate a use case. A UI form is normally boundary, not entity.SE13

            Choice by choice

            A · incorrect — Actor identification establishes external roles rather than generalizing scenario executions into interaction descriptions.

            B · correct — Use cases abstract related concrete scenarios into structured goal-oriented interaction descriptions.

            C · incorrect — Scenario identification captures concrete executions rather than their use-case abstraction.

            D · incorrect — Refinement elaborates an existing use case; the scenario-to-use-case abstraction is the identification step asked here.

            Question 241

            According to the Simple Use Case Writing Guide, which of the following is CORRECT practice?

            • A. Use passive voice so responsibility is unclear
            • B. Describe user interface elements in detail
            • C. Document exceptions separately from the main flow
            • D. Combine multiple tasks into one use case for brevity

            Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

            Study-guide sections

            SE15 · Write a complete use case with alternatives

            Study-guide references

            Correct answer: C — Document exceptions separately from the main success flow.

            SE15 instructs writers to use active subject–verb steps and separate errors from normal flow. C follows that rule directly. Passive voice hides responsibility, detailed UI design distracts from goal-level behavior, and combining unrelated tasks does not produce a clear use case. The distinction concerns organizing scenarios rather than omitting exception handling.

            Evidence in the complete study note

            Example: Submit Incident. Precondition: officer authenticated. 1 Officer supplies location and description. 2 System validates details. 3 System records the incident. 4 System returns its ID. Alternative 2a: location missing → report the problem and request correction; save nothing. Success postcondition: incident and ID persist; failure guarantee: no partial record. An alternate flow is a conditional variation; an exception flow handles a failure. Preconditions hold before entry, while a trigger starts the use case.SE15
            Use active subject–verb steps at one abstraction level; separate errors from the normal flow.SE15

            Choice by choice

            A · incorrect — Passive voice makes responsibility less clear, contrary to the active subject–verb guideline.

            B · incorrect — Detailed UI elements are not the goal-level behavior and flow structure emphasized by the guide.

            C · correct — Separating exception behavior keeps the main success flow clear while still documenting failures.

            D · incorrect — Combining multiple unrelated tasks sacrifices a coherent goal and consistent abstraction level.

            Question 242

            In the FAST (Facilitated Application Specification Technique), participants are initially asked to individually create lists of three item categories. Which is NOT one of them?

            • A. Things that are part of the environment surrounding the system
            • B. Things the system produces or outputs
            • C. Technical risks and constraints
            • D. Things the system uses or takes as inputs

            Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

            Study-guide sections

            SE12 · Elicitation techniques, FAST and QFD

            Study-guide references

            Correct answer: C — Technical risks and constraints are not one of the three initial FAST lists.

            SE12 explicitly lists environment elements, outputs and inputs as the initial participant categories. A, B and D match them. Technical risks and constraints can matter elsewhere in engineering, but they are not one of those three named initial FAST lists. The negative question asks about that procedure, not whether risk information is ever useful.

            Evidence in the complete study note

            In the taught FAST technique, participants list environment elements, outputs and inputs, consolidate lists and develop smaller specifications. QFD prioritizes customer value: normal needs are explicitly stated, expected needs are assumed, and exciting needs provide unanticipated benefit. Brainstorm first to generate ideas, then evaluate and prioritize; do not confuse that with letting every idea become a committed requirement.SE12

            Choice by choice

            A · incorrect — Environment elements are explicitly one of the initial FAST categories.

            B · incorrect — System outputs are explicitly included in the three initial lists.

            C · correct — Risks and constraints are not one of the specified environment/output/input categories.

            D · incorrect — Inputs and things the system uses are part of the stated initial categories.

            Question 243

            In Quality Function Deployment (QFD), which category of requirements represents features that go beyond customer expectations and provide great satisfaction?

            • A. Normal Requirements
            • B. Expected Requirements
            • C. Exciting Requirements
            • D. Implicit Requirements

            Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

            Study-guide sections

            SE12 · Elicitation techniques, FAST and QFD

            Study-guide references

            Correct answer: C — Exciting requirements.

            SE12 distinguishes explicitly stated normal needs, assumed expected needs and exciting needs that bring unanticipated benefit. Features exceeding expectations and producing additional satisfaction match the exciting category. Calling them merely implicit would confuse customer assumptions with unexpected added value rather than identify the QFD term.

            Evidence in the complete study note

            In the taught FAST technique, participants list environment elements, outputs and inputs, consolidate lists and develop smaller specifications. QFD prioritizes customer value: normal needs are explicitly stated, expected needs are assumed, and exciting needs provide unanticipated benefit. Brainstorm first to generate ideas, then evaluate and prioritize; do not confuse that with letting every idea become a committed requirement.SE12

            Choice by choice

            A · incorrect — Normal requirements are explicitly stated needs rather than unexpected extra benefits.

            B · incorrect — Expected requirements are assumed by customers and do not denote surprising added satisfaction.

            C · correct — Exciting requirements deliver unanticipated benefit beyond the customer’s expectations.

            D · incorrect — Implicit describes assumed needs more generally, not the QFD category for unanticipated benefits.

            Question 244

            Which validation property ensures that the requirements specification does not contain contradictory statements?

            • A. Completeness
            • B. Consistency
            • C. Clarity
            • D. Correctness

            Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

            Study-guide sections

            SE11 · Validate requirements and maintain traceability

            Study-guide references

            Correct answer: B — Consistency.

            SE11 directly defines consistency as excluding contradictions. Completeness covers agreed scope, clarity gives one intended interpretation, and correctness reflects stakeholder needs. A specification can be complete yet inconsistent, or clear yet wrong, so these properties cannot substitute for the precise no-contradictions condition.

            Evidence in the complete study note

            Correct requirements reflect actual stakeholder needs. Complete requirements address the agreed scope, normal and exceptional behavior. Consistency excludes contradictions. Clarity/unambiguity gives one intended interpretation; feasibility/realism means achievable within constraints. Verifiability means objective evidence can check fulfillment. Replace “fast for most users” with a defined metric, workload and threshold.SE11

            Choice by choice

            A · incorrect — Completeness concerns covering scope and behavior, not whether requirements contradict each other.

            B · correct — Consistency requires the specification’s statements to coexist without contradiction.

            C · incorrect — Clarity addresses interpretive ambiguity rather than logical compatibility between requirements.

            D · incorrect — Correctness concerns actual stakeholder needs, a different validation property.

            Question 245

            The Waterfall model is MOST appropriate when:

            • A. Requirements are expected to change frequently during development
            • B. The project is large and complex with evolving needs
            • C. Requirements are constant, the project is short, and technology is stable
            • D. The team needs to deliver working software in small increments

            Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

            Study-guide sections

            SE03 · Waterfall and the V-model

            Study-guide references

            Correct answer: C — Stable requirements and familiar, stable technology.

            SE03 says classical waterfall fits well-understood stable requirements and familiar technology, directly supporting C among these alternatives. Frequent change, evolving needs and early small deliveries call for feedback or incremental capability rather than waterfall’s late feedback. Short duration alone is not a proof, but C also supplies the decisive stability conditions stated in the note.

            Evidence in the complete study note

            Classical waterfall separates planned phases with reviewed deliverables. It fits well-understood, stable requirements and familiar technology; late feedback makes changes costly. It does not make change physically impossible: real projects revisit work under control, and modified waterfall explicitly includes feedback. Rigidity offers milestone visibility but can freeze incorrect assumptions.SE03

            Choice by choice

            A · incorrect — Frequent requirement changes make late-feedback sequential planning a poor fit.

            B · incorrect — Large evolving needs do not establish the stable requirements that favor classical waterfall.

            C · correct — Constant requirements and stable technology match the note’s stated waterfall selection conditions.

            D · incorrect — Prioritized usable small deliveries are the rationale for incremental delivery rather than a single sequential release.

            Question 246

            Which is a characteristic drawback of classical waterfall compared with approaches that seek repeated early feedback?

            • A. Requires skilled developers
            • B. Late feedback can make requirement changes costly through rework of earlier phase deliverables.
            • C. No clear project milestones
            • D. Does not support documentation

            Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

            Study-guide sections

            SE03 · Waterfall and the V-model

            Study-guide references

            Correct answer: B — Late feedback can make requirement changes costly through rework of earlier phase deliverables.

            Classical waterfall separates planned phases and may receive important feedback late. Correcting earlier assumptions can then require costly rework across completed deliverables, which is its characteristic drawback here. Changes are still possible under control. Skilled developers are needed across approaches, and waterfall provides milestone visibility and documentation, so the other alternatives do not identify the stated comparative disadvantage.

            Evidence in the complete study note

            Classical waterfall separates planned phases with reviewed deliverables. It fits well-understood, stable requirements and familiar technology; late feedback makes changes costly. It does not make change physically impossible: real projects revisit work under control, and modified waterfall explicitly includes feedback. Rigidity offers milestone visibility but can freeze incorrect assumptions.SE03

            Choice by choice

            A · incorrect — Skill requirements are not unique to waterfall.

            B · correct — Late feedback can make requirement changes costly after earlier phases.

            C · incorrect — Waterfall provides clear reviewed milestones.

            D · incorrect — Waterfall supports planned documentation.

            Question 247

            What is the key conceptual distinction between iteration and incremental delivery, even when a process combines both?

            • A. Iterative adds new features each cycle; Incremental refines the same set repeatedly
            • B. Iteration revisits and improves a solution; an increment adds usable functionality.
            • C. They are identical; the terms are interchangeable
            • D. Incremental involves risk analysis; Iterative does not

            Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

            Study-guide sections

            SE04 · Iteration, increments and early delivery

            Study-guide references

            Correct answer: B — Iteration revisits and improves a solution; an increment adds usable functionality.

            Iteration revisits and improves a solution, while an increment adds usable functionality. A process can refine existing capability and add new capability in the same cycle, so the concepts are compatible but not identical. Neither requires rebuilding the entire system or making every increment completely independent. Risk analysis is a separate concern rather than the structural distinction defining these two terms.

            Evidence in the complete study note

            Choose incremental delivery when prioritized partial capability must reach users early. Smaller changes can be easier to debug and permit feedback, though architecture and integration still require planning. Iteration need not rebuild the whole system every time, and increments need not be perfectly independent modules. Broad descriptions of early working software can fit prototypes, iterative or Agile processes; identify the purpose of that early version.SE04
            Iteration revisits and improves a solution; an increment adds usable functionality. A process may do both.SE04

            Choice by choice

            A · incorrect — This reverses refinement and added functionality.

            B · correct — Iteration refines; increments add usable capability.

            C · incorrect — The terms differ even when combined in one process.

            D · incorrect — Risk analysis does not define their distinction.

            Question 248

            A large application already has its core capabilities. The main development goal is to revisit and improve that existing solution repeatedly as feedback and future changes arrive, rather than primarily add new capability in each delivery. Which concept most directly names that emphasis?

            • A. Waterfall Model
            • B. V-Model
            • C. Iterative Model
            • D. Incremental Model

            Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

            Study-guide sections

            SE04 · Iteration, increments and early delivery

            SE02 · Lifecycle phases and model selection

            Study-guide references

            Correct answer: C — Iterative Model

            The stated emphasis is iterative: revisiting and improving an existing solution in response to feedback. Incremental development names the addition of usable functionality, which is not the primary goal specified, although both can coexist. Classical waterfall’s stable staged planning and the V-model’s paired assurance structure do not directly name this refinement emphasis. Large size and anticipated change alone would not have selected a unique model.

            Evidence in the complete study note

            Choose incremental delivery when prioritized partial capability must reach users early. Smaller changes can be easier to debug and permit feedback, though architecture and integration still require planning. Iteration need not rebuild the whole system every time, and increments need not be perfectly independent modules. Broad descriptions of early working software can fit prototypes, iterative or Agile processes; identify the purpose of that early version.SE04
            A common lifecycle names requirements, design, implementation, testing, deployment and maintenance. Analysis clarifies the problem; system design chooses architecture; object/detail design specifies interfaces and algorithms; implementation writes code; testing evaluates behavior; deployment puts it into service. These activities may overlap and repeat.SE02
            Iteration revisits and improves a solution; an increment adds usable functionality. A process may do both.SE04

            Choice by choice

            A · incorrect — Classical waterfall does not directly name repeated refinement as the organizing emphasis.

            B · incorrect — The V-model emphasizes paired development and tests.

            C · correct — Iteration directly names revisiting and improving the existing solution.

            D · incorrect — Incremental describes added functionality rather than the specified primary emphasis.

            Question 249

            In the Agile SDLC, small units of functionality that the software needs to deliver are called:

            • A. Sprints
            • B. Iterations
            • C. User Stories
            • D. Epics

            Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

            Study-guide sections

            SE05 · Agile values, stories and Scrum

            Study-guide references

            Correct answer: C — User stories.

            SE05 defines a user story as a small user need and value supported by acceptance criteria. Sprints and iterations name cycles or timeboxes, not the need itself. An epic groups broader work. C therefore names the small functional work unit intended here, without claiming that Agile requirements consist only of story text.

            Evidence in the complete study note

            Scrum uses timeboxed Sprints of at most one month, with a Sprint Goal, selected work and a usable Increment meeting a Definition of Done. Scope is discussed before and during planning; it is not forbidden to agree scope. Timeboxes tend to stay fixed while content is adapted without endangering the goal. Agile can be combined with required assurance/documentation; safety-critical context alone cannot prove it is unsuitable.SE05
            A user story states a small user need and value, supported by acceptance criteria; an epic groups broader work.SE05

            Choice by choice

            A · incorrect — A Sprint is a timeboxed development interval rather than the individual user need.

            B · incorrect — An iteration is a cycle of work or refinement, not a small functional requirement.

            C · correct — A user story states a small user need and its value with acceptance criteria.

            D · incorrect — An epic groups broader work rather than naming the smaller story-sized need.

            Question 250

            The Spiral Model distinguishes itself from other models primarily through its emphasis on:

            • A. Sequential phase completion
            • B. Risk Analysis at every cycle
            • C. Customer delivery at the end of the project
            • D. Strict adherence to initial requirements

            Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

            Study-guide sections

            SE06 · Spiral development and risk

            Study-guide references

            Correct answer: B — Risk analysis and reduction in every spiral cycle.

            SE06 defines spiral development as risk driven, with each cycle identifying objectives and alternatives, assessing and reducing risks, producing a result and planning commitment. That emphasis distinguishes it from merely repeating phases or delivering only at the end. It can adapt requirements and combine other activities rather than enforcing an unchangeable initial specification.

            Evidence in the complete study note

            Spiral development is risk driven. Each cycle identifies objectives and alternatives, assesses and reduces important risks, develops/verifies an appropriate next result, and plans further commitment. A prototype may test a risky technology before a large investment. The amount and type of work depend on the risks.SE06

            Choice by choice

            A · incorrect — A spiral can contain staged work, but sequential completion is not its defining driver.

            B · correct — Risk assessment and reduction guide each cycle’s work and further commitment.

            C · incorrect — Only delivering at the end is not the distinguishing spiral principle.

            D · incorrect — A risk-driven cycle can revise plans and requirements rather than rigidly freeze them.

            Question 251

            The V-Model derives its name from its shape. What does the BOTTOM of the 'V' represent?

            • A. Requirements Gathering
            • B. Deployment
            • C. Coding/Implementation
            • D. Maintenance

            Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

            Study-guide sections

            SE03 · Waterfall and the V-model

            Study-guide references

            Correct answer: C — Coding/implementation.

            SE03 explicitly places coding at the bottom of the V while specification and design stages correspond to later testing levels. Requirements therefore begin the development side rather than occupy the bottom; deployment and maintenance are not that connecting implementation activity. This is a model-diagram convention, not a claim that all real work follows a perfect geometric sequence.

            Evidence in the complete study note

            The V-model pairs specification/design stages with later test levels. Requirements inform acceptance tests; system design informs system tests; component/detail design informs integration/unit tests. Coding lies at the bottom. Test planning starts early. Stable requirements and strong assurance may favor this organization, but neither a V shape nor waterfall guarantees safety or correctness.SE03

            Choice by choice

            A · incorrect — Requirements occur on the specification side, not at the coding bottom of the V.

            B · incorrect — Deployment is not the implementation activity joining the V-model’s sides.

            C · correct — The note explicitly identifies coding as the bottom of the V.

            D · incorrect — Maintenance occurs in lifecycle evolution rather than at this implementation point.

            Question 252

            Which organization standardizes and maintains UML as a modeling language?

            • A. IEEE
            • B. ISO
            • C. Object Management Group (OMG)
            • D. W3C

            Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

            Study-guide sections

            SE17 · Class diagrams, visibility and multiplicity

            Study-guide references

            Correct answer: C — Object Management Group (OMG)

            The note identifies the Object Management Group as UML’s standardizing and maintaining organization. UML is a modeling language rather than a software lifecycle process. This stewardship question does not claim that the organization originally invented every contributing notation. IEEE, ISO and W3C are not the organization to which the supplied note attributes this particular standardization and maintenance role.

            Evidence in the complete study note

            A class box lists name, attributes and operations; + public, - private, # protected and ~ package indicate visibility. A class diagram shows static types and relationships, while an object diagram shows particular instances/links. UML is maintained and standardized by OMG; it is a modeling language, not a lifecycle process. Structural things describe conceptual or physical structural elements.SE17

            Choice by choice

            A · incorrect — IEEE is not the attributed UML steward.

            B · incorrect — ISO is not the organization attributed this role in the note.

            C · correct — OMG is the stated standardizing and maintaining organization.

            D · incorrect — W3C is not the attributed UML steward.

            Question 253

            In a UML Use Case Diagram, the rectangle enclosing all use cases is called:

            • A. System Context
            • B. System Boundary Box
            • C. Package Container
            • D. Module Frame

            Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

            Study-guide sections

            SE14 · Actors, use cases and scope

            Study-guide references

            Correct answer: B — The system boundary box.

            SE14 says actors are outside the system-boundary rectangle and use-case ovals are inside. The enclosing rectangle therefore marks the modeled system’s boundary. A context may be communicated by the diagram, but it is not the specific box name requested; packages and modules serve different grouping roles rather than defining this external actor boundary.

            Evidence in the complete study note

            Draw actors outside the system boundary rectangle and use-case ovals inside. Name a goal with a verb and noun. The diagram shows roles, goals and relationships, not the full detailed algorithm or UI layout. Being an internal component is different from being an external actor; the chosen boundary determines which role applies.SE14

            Choice by choice

            A · incorrect — System context is broader information, not the specific name of this enclosing boundary rectangle.

            B · correct — The rectangle separates the modeled system’s use cases from external actor roles.

            C · incorrect — A package groups modeling elements but is not the stated system/actor boundary.

            D · incorrect — Module frame is not the use-case system-boundary term defined in SE14.

            Question 254

            When execution reaches an include relationship’s inclusion point in a base use case, what does include require?

            • A. Optional behavior that may be added to the base use case
            • B. The included behavior is required whenever execution reaches the inclusion point.
            • C. An inheritance relationship between two use cases
            • D. A timing constraint between two use cases

            Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

            Study-guide sections

            SE16 · Include, extend, generalization and abstract use cases

            Study-guide references

            Correct answer: B — The included behavior is required whenever execution reaches the inclusion point.

            Include factors required reused behavior into another use case. When the base reaches the inclusion point, the included behavior is incorporated and performed as specified. This does not imply that every possible conditional branch of the base reaches that point. Optional conditional additions correspond to extend, specialization to generalization, and timing constraints are separate from the inclusion relationship.

            Evidence in the complete study note

            Generalization relates a specialized actor/use case to a more general one, with a hollow triangle toward the general element. An abstract use case specifies behavior for specialization and is not directly instantiated as a complete use case. It is not defined merely by reuse or lack of a direct actor line. Included behavior is incorporated where the inclusion is reached; do not infer every conditional branch in the base always executes.SE16
            Include factors required reused behavior: Submit Order includes Validate Order, with the dashed arrow from the including/base use case to the included one.SE16

            Choice by choice

            A · incorrect — Conditional optional added behavior describes extend.

            B · correct — The included behavior is required when its inclusion point is reached.

            C · incorrect — Specialization is generalization rather than include.

            D · incorrect — Include is not a timing constraint.

            Question 255

            In a UML class diagram, visibility marked with '#' indicates:

            • A. Public access
            • B. Private access
            • C. Protected access
            • D. Package-level access

            Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

            Study-guide sections

            SE17 · Class diagrams, visibility and multiplicity

            Study-guide references

            Correct answer: C — Protected visibility.

            SE17 lists + public, - private, # protected and ~ package. The requested hash marker therefore means protected access. These symbols indicate visibility of a class member; they do not express object multiplicity, inheritance direction or class ownership, and the other choices correspond to different explicit markers.

            Evidence in the complete study note

            A class box lists name, attributes and operations; + public, - private, # protected and ~ package indicate visibility. A class diagram shows static types and relationships, while an object diagram shows particular instances/links. UML is maintained and standardized by OMG; it is a modeling language, not a lifecycle process. Structural things describe conceptual or physical structural elements.SE17

            Choice by choice

            A · incorrect — Public visibility is marked with + rather than #.

            B · incorrect — Private visibility is marked with - rather than #.

            C · correct — The note explicitly assigns # to protected visibility.

            D · incorrect — Package visibility uses ~ rather than the protected # marker.

            Question 256

            In UML, which relationship is represented by a HOLLOW diamond shape pointing toward the 'whole' class?

            • A. Composition
            • B. Dependency
            • C. Aggregation
            • D. Generalization

            Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

            Study-guide sections

            SE18 · Association, aggregation, composition and generalization

            Study-guide references

            Correct answer: C — Shared aggregation.

            SE18 defines shared aggregation with a hollow diamond at the whole end. Composition instead uses a filled diamond; dependency is a dashed arrow and generalization uses a hollow triangle. The question’s whole-end description is consistent with the notation, so the hollow shape uniquely identifies aggregation among these alternatives.

            Evidence in the complete study note

            Composition uses a filled diamond at the whole end and strong ownership: a part is in at most one composite at a time, and parts still owned are destroyed with that composite. Parts may be detached/transferred under a defined model. Thus “cannot ever exist independently” is an oversimplification. For Car composing Engine, the diamond belongs beside Car; saying it points to Engine is imprecise. The Car–Engine example describes composition.SE18
            Shared aggregation uses a hollow diamond at the whole end and weak whole-part meaning;SE18

            Choice by choice

            A · incorrect — Composition uses a filled diamond, not the specified hollow diamond.

            B · incorrect — Dependency is represented by a dashed arrow rather than a whole-part diamond.

            C · correct — Shared aggregation uses a hollow diamond placed at the whole end.

            D · incorrect — Generalization uses a hollow triangle toward the general element rather than a diamond.

            Question 257

            Which statement accurately distinguishes UML composition from shared aggregation while allowing model-defined detachment or transfer?

            • A. Aggregation is for classes; Composition is for interfaces
            • B. Composition has exclusive composite ownership at a time and destroys still-owned parts with the whole; shared aggregation gives weaker whole-part meaning.
            • C. Aggregation implies inheritance; Composition does not
            • D. They are synonymous in modern UML

            Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

            Study-guide sections

            SE18 · Association, aggregation, composition and generalization

            Study-guide references

            Correct answer: B — Composition has exclusive composite ownership at a time and destroys still-owned parts with the whole; shared aggregation gives weaker whole-part meaning.

            Composition gives strong ownership: a part is in at most one composite at a time, and still-owned parts are destroyed with that composite. Shared aggregation indicates weaker whole-part meaning without that detailed lifecycle policy. A model can permit detachment or transfer, so permanent inability to exist independently is too strong. Neither relationship is inheritance, and composition is not restricted to interfaces.

            Evidence in the complete study note

            Composition uses a filled diamond at the whole end and strong ownership: a part is in at most one composite at a time, and parts still owned are destroyed with that composite. Parts may be detached/transferred under a defined model. Thus “cannot ever exist independently” is an oversimplification. For Car composing Engine, the diamond belongs beside Car; saying it points to Engine is imprecise. The Car–Engine example describes composition.SE18

            Choice by choice

            A · incorrect — Composition is not restricted to interfaces.

            B · correct — This states strong ownership and destruction of still-owned parts, unlike weak shared aggregation.

            C · incorrect — Aggregation is not inheritance; generalization is separate.

            D · incorrect — The ownership meanings differ, so they are not synonyms.

            Question 258

            Under the course’s sequence-diagram layout heuristic—rather than a mandatory UML column rule—which participant belongs in the second column?

            • A. The control object managing the use case
            • B. The actor who initiated the use case
            • C. A boundary object the actor used to start the use case
            • D. An entity object central to the use case

            Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

            Study-guide sections

            SE19 · Sequence diagrams and the emergency-report example

            Study-guide references

            Correct answer: C — A boundary object the actor used to start the use case

            The course’s heuristic places the initiating actor first, the boundary object second, the control object third and entity objects afterward. The boundary used by the actor therefore occupies the second column under that convention. UML itself does not mandate this column order; lifeline semantics come from the modeled participants and messages rather than their horizontal position alone.

            Evidence in the complete study note

            One interaction-diagram layout heuristic puts the initiating actor first, boundary second, control third, then entities. This is not a required UML column order. In ReportEmergency, FieldOfficer activates ReportEmergencyButton, enters details through EmergencyReportForm, and later sees AcknowledgmentNotice; DispatcherStation belongs to the dispatcher side. Choose the button for initiating this particular scenario.SE19

            Choice by choice

            A · incorrect — The heuristic places control third.

            B · incorrect — The initiating actor is first.

            C · correct — The actor-facing boundary is second under the specified heuristic.

            D · incorrect — Entities follow the boundary and control in this heuristic.

            Question 259

            In a UML Activity Diagram, a diamond shape is used to represent:

            • A. Initial State
            • B. Final State
            • C. Action Box
            • D. Decision Box

            Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

            Study-guide sections

            SE20 · Activity, state and data-flow models

            Study-guide references

            Correct answer: D — A decision node, also usable as a merge node in the appropriate flow.

            SE20 names the guarded decision diamond and separately notes that the same shape can merge alternative flows. D is therefore a correct use of the shape, without claiming decision is its only role. Initial nodes are filled circles, actions are rounded, and final-state notation is not the diamond described.

            Evidence in the complete study note

            An activity diagram models workflow: filled circle start, rounded actions, guarded decision diamond, thick fork/join bars and partitions/swimlanes for responsibility. A diamond can also merge alternative flows; a join synchronizes concurrent flows. A state machine models states and transitions triggered by events, often with guards/actions, for one object’s lifecycle.SE20

            Choice by choice

            A · incorrect — The initial node is a filled circle rather than a diamond.

            B · incorrect — The diamond is not the standard final-state marker in the described notation.

            C · incorrect — Actions are rounded nodes rather than guarded-flow diamonds.

            D · correct — A diamond can represent a guarded decision; it can also merge alternative flows.

            Question 260

            In system design, 'coupling' between subsystems refers to:

            • A. How well objects within a subsystem work toward a common goal
            • B. The number of operations a subsystem exposes
            • C. The degree of dependency between two subsystems
            • D. The architectural pattern chosen for the system

            Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

            Study-guide sections

            SE22 · Cohesion, coupling, modularity and refactoring

            Study-guide references

            Correct answer: C — The degree of dependency between subsystems.

            SE22 explicitly distinguishes cohesion within a module from coupling between modules. A describes cohesion; C describes coupling. Interface operation count can affect design complexity but is not the definition of dependence, and an architectural pattern may influence coupling without being the relationship measure itself. The goal is usually low coupling with high cohesion.

            Evidence in the complete study note

            Cohesion measures how well elements inside a module serve a related purpose; coupling measures dependency between modules. Seek high cohesion and low coupling. Shared mutable data and knowledge of another module’s internal representation increase coupling. Information hiding exposes stable operations while concealing changeable decisions.SE22

            Choice by choice

            A · incorrect — Related purpose inside a subsystem defines cohesion rather than between-subsystem coupling.

            B · incorrect — Operation count alone does not measure the actual dependencies between subsystems.

            C · correct — Coupling is the degree of dependency between modules or subsystems.

            D · incorrect — An architectural style can affect coupling but is not its definition.

            Question 261

            In architectural design, a 'closed architecture' in a layered system means:

            • A. No external access to any layer is allowed
            • B. A layer can access any layer at deeper levels freely
            • C. A layer can only call the layer immediately below it
            • D. All layers communicate through a central repository

            Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

            Study-guide sections

            SE23 · Layers, tiers and architecture views

            Study-guide references

            Correct answer: C — Calls are restricted to the immediately lower layer.

            SE23 defines a closed layered architecture as allowing calls only to the immediately lower layer. Open layering may permit approved skipping, so B describes a different policy. Closed does not mean no external access or a shared repository; it concerns permitted dependencies between layers rather than the system’s exposure or storage organization.

            Evidence in the complete study note

            A layer is a logical abstraction level; a tier is a deployment separation. A closed layered architecture permits calls only to the immediately lower layer; an open one permits approved skipping. For top-to-bottom A,B,C,D, A→B obeys closed layering, A→C skips, and lower-to-upper calls violate the simple dependency rule unless explicitly mediated by a defined mechanism.SE23

            Choice by choice

            A · incorrect — Closed layering restricts interlayer calls, not every form of external access.

            B · incorrect — Skipping freely to deeper layers contradicts the immediate-lower-layer restriction.

            C · correct — A layer calls only the immediately lower layer in the defined closed architecture.

            D · incorrect — A central repository is another architectural arrangement and does not define closed layering.

            Question 262

            Which architectural style divides subsystems into Model, View, and Controller components?

            • A. Repository Style
            • B. Client/Server Style
            • C. Peer-to-Peer Style
            • D. Model-View-Controller Style

            Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

            Study-guide sections

            SE24 · Architecture styles and integration boundaries

            Study-guide references

            Correct answer: D — Model–View–Controller.

            SE24 explicitly defines MVC as separating a domain model, display view and interaction controller. D names that exact style. Repository, client–server and peer-to-peer organize central data or interacting roles differently; any may be combined with MVC, but none is the name of this particular three-responsibility separation.

            Evidence in the complete study note

            Repository style shares central data, simplifying common access but creating bottleneck/schema dependencies. MVC separates domain model, display view and interaction controller. Client–server separates requesters from service providers; peer-to-peer permits both roles. Pipe-and-filter applies successive transformations to data streams. Three-tier separates presentation, application logic and storage; some four-tier variants split presentation client/server.SE24

            Choice by choice

            A · incorrect — Repository style centers shared data rather than the specific model/view/controller separation.

            B · incorrect — Client–server separates requesters and service providers, not these three presentation-interaction responsibilities.

            C · incorrect — Peer-to-peer allows participants to play requester and provider roles rather than defining MVC components.

            D · correct — Model–View–Controller explicitly names the three responsibilities in the question.

            Question 263

            In the Three-Tier architectural style, which layer handles 'storing, retrieving, and querying persistent data'?

            • A. Interface Layer
            • B. Application Logic Layer
            • C. Storage Layer
            • D. Presentation Layer

            Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

            Study-guide sections

            SE24 · Architecture styles and integration boundaries

            SE23 · Layers, tiers and architecture views

            Study-guide references

            Correct answer: C — The storage layer/tier.

            SE24 separates three-tier presentation, application logic and storage. Persistent data storage and retrieval belong to the storage responsibility, whereas presentation handles interaction and application logic coordinates domain behavior. The question uses layer for a tier-style role; that terminology does not change which responsibility owns persistence.

            Evidence in the complete study note

            Repository style shares central data, simplifying common access but creating bottleneck/schema dependencies. MVC separates domain model, display view and interaction controller. Client–server separates requesters from service providers; peer-to-peer permits both roles. Pipe-and-filter applies successive transformations to data streams. Three-tier separates presentation, application logic and storage; some four-tier variants split presentation client/server.SE24
            A layer is a logical abstraction level; a tier is a deployment separation. A closed layered architecture permits calls only to the immediately lower layer; an open one permits approved skipping. For top-to-bottom A,B,C,D, A→B obeys closed layering, A→C skips, and lower-to-upper calls violate the simple dependency rule unless explicitly mediated by a defined mechanism.SE23

            Choice by choice

            A · incorrect — The interface responsibility handles interaction rather than persistent storage and querying.

            B · incorrect — Application logic coordinates domain operations but delegates persistence to the storage responsibility.

            C · correct — The storage role handles persistent data, including retrieval and queries.

            D · incorrect — Presentation formats user interaction and output rather than owning persistent data storage.

            Question 264

            In the analysis model, which type of object represents the bridges between the system and the actors?

            • A. Entity Objects
            • B. Control Objects
            • C. Boundary Objects
            • D. Interface Objects

            Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

            Study-guide sections

            SE13 · From scenarios to analysis objects

            Study-guide references

            Correct answer: C — Boundary objects.

            SE13 defines boundary objects as mediating interaction, with ReportForm as an example. That is the bridge between external actors and the system. Entity objects hold domain information, while controls coordinate use cases. Interface objects is a generic descriptive phrase, but boundary is the explicitly defined analysis-category name requested among these choices.

            Evidence in the complete study note

            A scenario is one concrete execution; a use case abstracts the related successful and alternative scenarios. Analysis integrates functional (use cases/scenarios), structural/object (classes) and dynamic (states/interactions) models. Entity objects represent domain information such as Incident; boundary objects mediate interaction, such as ReportForm; control objects coordinate a use case. A UI form is normally boundary, not entity.SE13

            Choice by choice

            A · incorrect — Entity objects represent domain information rather than the actor-facing interaction bridge.

            B · incorrect — Control objects coordinate use-case behavior rather than primarily mediate actor interaction.

            C · correct — Boundary objects are explicitly defined as mediating system–actor interaction.

            D · incorrect — Interface objects is not the named entity/boundary/control category specified here’s analysis model.

            Question 265

            Which heuristic rule states that there should be 'one control object per actor' in a use case?

            • A. CRC Card Heuristic
            • B. Control Object Identification Heuristic
            • C. Boundary Object Heuristic
            • D. Sequence Diagram Column Rule

            Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

            Study-guide sections

            SE13 · From scenarios to analysis objects

            Study-guide references

            Correct answer: B — The control-object identification heuristic.

            SE13 permits one control per use case or participating actor as a useful starting point, while denying a mandatory UML rule. The stem already asks for a heuristic, so B correctly identifies the control-object selection guideline. CRC, boundary identification and column layout concern different tasks; none makes the count a required lifetime or architecture constraint.

            Evidence in the complete study note

            Use nouns as candidate objects, possessive descriptions as candidate attributes, and verbs such as manages/reports-to as candidate associations. These are heuristics, not automatic parsing rules. CRC means Class, Responsibilities, Collaborators. A control per use case or participating actor can be a useful starting point, not a mandatory UML rule or fixed object lifetime.SE13

            Choice by choice

            A · incorrect — CRC records class responsibilities and collaborators rather than prescribing this candidate-control count.

            B · correct — This is the heuristic for identifying candidate use-case control objects, not a universal UML constraint.

            C · incorrect — Boundary heuristics identify interaction-facing objects rather than coordinating controls.

            D · incorrect — Sequence-column layout orders participants visually and does not define candidate control-object counts.

            Question 266

            CRC cards stand for:

            • A. Class, Requirements, Conditions
            • B. Component, Relationship, Constraints
            • C. Class, Responsibilities, Collaborators
            • D. Control, Reuse, Composition

            Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

            Study-guide sections

            SE13 · From scenarios to analysis objects

            Study-guide references

            Correct answer: C — Class, Responsibilities, Collaborators.

            SE13 expands CRC directly as Class, Responsibilities, Collaborators. The card identifies the class, what it must do or know, and which other objects help fulfill those responsibilities. The distractors replace these terms with requirements, components or unrelated design concepts and therefore do not preserve the stated expansion.

            Evidence in the complete study note

            Use nouns as candidate objects, possessive descriptions as candidate attributes, and verbs such as manages/reports-to as candidate associations. These are heuristics, not automatic parsing rules. CRC means Class, Responsibilities, Collaborators. A control per use case or participating actor can be a useful starting point, not a mandatory UML rule or fixed object lifetime.SE13

            Choice by choice

            A · incorrect — Requirements and Conditions are not the R and final C in the stated expansion.

            B · incorrect — Component, Relationship and Constraints do not match the class-card terminology.

            C · correct — This is the exact CRC expansion supplied in SE13.

            D · incorrect — Control, Reuse and Composition are different concepts rather than the CRC card fields.

            Question 267

            In UML association multiplicity, what does '0..*' mean?

            • A. Exactly one instance
            • B. Zero or exactly one instance
            • C. Zero or more instances
            • D. One or more instances

            Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

            Study-guide sections

            SE17 · Class diagrams, visibility and multiplicity

            Study-guide references

            Correct answer: C — Zero or more instances.

            SE17 defines 0..* as any nonnegative number. Zero is allowed and the star places no finite upper bound, so C fits. The alternatives correspond to 1, 0..1 and 1..* respectively. Multiplicity at one end is interpreted relative to one object at the opposite end, not as a whole-system object count.

            Evidence in the complete study note

            Multiplicity at one end counts how many objects there may correspond to one object at the opposite end: 1 exactly one, 0..1 optional, 0..* any nonnegative number, 1..* at least one. A one-to-many association does not automatically mean composition. Read each end separately before choosing cardinality.SE17

            Choice by choice

            A · incorrect — Exactly one corresponds to multiplicity 1 rather than 0..*.

            B · incorrect — Optional single-valued multiplicity is 0..1, not an unbounded star.

            C · correct — Zero is permitted and the upper star allows any number of related instances.

            D · incorrect — One or more requires lower bound 1, written 1..*.

            Question 268

            In Abbott's heuristics for identifying associations, which phrase pattern most directly suggests a relationship between classes?

            • A. Look for adjective phrases describing class properties
            • B. Examine verb phrases like 'has', 'is part of', 'manages', 'reports to'
            • C. Find all nouns that appear more than twice
            • D. Identify all user interface terms

            Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

            Study-guide sections

            SE13 · From scenarios to analysis objects

            Study-guide references

            Correct answer: B — Verb phrases expressing relationships, such as manages or reports to.

            SE13 recommends nouns as candidate objects and verbs such as manages/reports-to as candidate associations. B is the relationship-phrase option. Adjectives generally describe properties, repeated nouns do not automatically imply an association, and UI terms suggest boundary concerns. These are candidate-identification heuristics rather than a proof that every verb must become a modeled link.

            Evidence in the complete study note

            Use nouns as candidate objects, possessive descriptions as candidate attributes, and verbs such as manages/reports-to as candidate associations. These are heuristics, not automatic parsing rules. CRC means Class, Responsibilities, Collaborators. A control per use case or participating actor can be a useful starting point, not a mandatory UML rule or fixed object lifetime.SE13

            Choice by choice

            A · incorrect — Property descriptions suggest attributes rather than directly identifying links between classes.

            B · correct — Relationship verbs are the note’s direct heuristic for candidate associations.

            C · incorrect — Noun frequency is not the stated association-identification rule; nouns instead suggest candidate objects.

            D · incorrect — UI terminology may suggest boundaries but does not directly establish an association between domain classes.

            Question 269

            In software testing, which type of testing evaluates the software's behavior WITHOUT knowledge of its internal code structure?

            • A. White Box Testing
            • B. Grey Box Testing
            • C. Black Box Testing
            • D. Structural Testing

            Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

            Study-guide sections

            SE36 · Test types, regression and exploratory work

            Study-guide references

            Correct answer: C — Black-box testing.

            SE36 contrasts black-box cases derived from required behavior with white-box cases derived from implementation structure. Grey-box uses partial internal knowledge. The question excludes internal-code knowledge, so black-box is the appropriate technique. Structural testing instead refers to the very internal paths or statements that this scenario does not inspect.

            Evidence in the complete study note

            Black-box techniques derive cases from specified behavior; white-box techniques derive them from internal structure; grey-box uses partial internal knowledge. Regression testing checks for unintended effects after change; confirmation testing checks the particular defect repair. Exploratory testing combines learning, design and execution and is experience based. Manual/automated describe execution support, not a compulsory black-/white-box classification.SE36

            Choice by choice

            A · incorrect — White-box testing explicitly uses internal implementation structure to derive cases.

            B · incorrect — Grey-box testing uses partial internal knowledge rather than excluding it.

            C · correct — Black-box testing derives cases from externally specified behavior without needing code structure.

            D · incorrect — Structural testing is based on internal control or code structure, contrary to the stem.

            Question 270

            Which type of functional testing verifies that individual components work correctly in ISOLATION?

            • A. System Testing
            • B. Integration Testing
            • C. Regression Testing
            • D. Unit Testing

            Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

            Study-guide sections

            SE35 · Testing levels and acceptance

            Study-guide references

            Correct answer: D — Unit testing.

            SE35 defines unit testing as isolating a function, class or small component, often replacing dependencies with stubs or mocks. Integration checks combined interactions and system testing evaluates the whole system. Regression describes testing after changes and can occur at different levels, so it is not the isolation level named by the question.

            Evidence in the complete study note

            Unit testing isolates a function, class or small component, often replacing dependencies with stubs/mocks; a driver invokes the unit and a stub substitutes a called dependency. Integration testing exercises interfaces and interactions among combined parts. System testing checks the complete integrated system against functional and nonfunctional requirements in a representative environment.SE35

            Choice by choice

            A · incorrect — System testing evaluates the complete integrated system rather than an isolated component.

            B · incorrect — Integration testing focuses on interactions among combined parts, not isolation.

            C · incorrect — Regression checks unintended effects after change and is not inherently a component-isolation level.

            D · correct — Unit testing evaluates a small component in isolation, with dependencies replaceable by test doubles.

            Question 271

            Non-functional testing that evaluates how the system behaves under expected workloads and measures response speed is called:

            • A. Usability Testing
            • B. Reliability Testing
            • C. Performance Testing
            • D. Compatibility Testing

            Separate testing scope, technique and purpose. Use the stated workload, observable result or coverage target rather than a universal ranking.

            Study-guide sections

            SE36 · Test types, regression and exploratory work

            Study-guide references

            Correct answer: C — Performance testing, specifically load-oriented testing under expected demand.

            SE36 defines performance tests as assessing speed, throughput and resource use under a specified workload and distinguishes expected load from stress beyond normal limits. The stem explicitly adds workload and response speed, so it supports performance testing rather than merely a vague normal-condition test. Usability, reliability and compatibility target different quality questions.

            Evidence in the complete study note

            Functional tests check required behavior against the SRS and acceptance criteria. Performance tests assess speed, throughput and resources under a specified workload; load uses expected demands and stress exceeds normal limits. Usability, security, compatibility and reliability tests target their respective qualities. “Normal operating conditions” alone does not distinguish functional from performance testing.SE36

            Choice by choice

            A · incorrect — Usability focuses on task success and ease of use rather than response-speed measurements under load.

            B · incorrect — Reliability concerns failure-free service, not primarily the stated response-time criterion.

            C · correct — Speed under an expected workload is performance/load testing as defined in SE36.

            D · incorrect — Compatibility examines cooperating environments rather than the specified speed-under-load behavior.

            Question 272

            In the analysis phase, which model type uses use cases and scenarios to describe what the software should do?

            • A. Dynamic Model
            • B. Analysis Object Model
            • C. Functional Model
            • D. Structural Model

            Distinguish observable services, measurable qualities and implementation constraints. Check scope, stakeholder meaning and the requested level of specificity.

            Study-guide sections

            SE13 · From scenarios to analysis objects

            Study-guide references

            Correct answer: C — The functional model.

            SE13 explicitly associates use cases and scenarios with functional modeling, classes with structural/object modeling, and states/interactions with dynamic modeling. Thus C names the requested description of what the system should do. The alternatives describe state-dependent behavior or static object structure rather than this user-goal and scenario view.

            Evidence in the complete study note

            A scenario is one concrete execution; a use case abstracts the related successful and alternative scenarios. Analysis integrates functional (use cases/scenarios), structural/object (classes) and dynamic (states/interactions) models. Entity objects represent domain information such as Incident; boundary objects mediate interaction, such as ReportForm; control objects coordinate a use case. A UI form is normally boundary, not entity.SE13

            Choice by choice

            A · incorrect — Dynamic models emphasize states and interactions rather than the named use-case/scenario category.

            B · incorrect — The analysis object model captures classes and relationships rather than the functional use-case view.

            C · correct — Use cases and scenarios are explicitly the functional analysis model.

            D · incorrect — Structural modeling describes static classes and links rather than required user-goal flows.

            Question 273

            In an analysis model, an object coordinates a use case and moves among Idle, WaitingForReply and Completing states as events arrive. Domain entities are passive records and the form has no persistent modes in this scenario. Which object category is the direct state-machine target described?

            • A. Entity Objects
            • B. Boundary Objects
            • C. Control Objects
            • D. All objects equally

            Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

            Study-guide sections

            SE20 · Activity, state and data-flow models

            SE13 · From scenarios to analysis objects

            Study-guide references

            Correct answer: C — Control Objects

            A control object coordinates a use case, and the described coordinator has significant event-dependent states. A state machine is therefore directly useful for that control object in this scenario. Entities and boundaries can also have meaningful lifecycles in other systems, but here their stated behavior does not supply the modeled states. Suitability follows from responsibilities and lifecycle behavior, not equal need across all objects.

            Evidence in the complete study note

            Choose a sequence diagram for message order between participants, a state machine for event-dependent state changes, and activity for workflow. Both sequence and state diagrams describe behavior over time. State machines are useful for objects with significant states, whether entity or control. A DFD shows data stores/flows and transformations from inputs to outputs; it is not a UML diagram.SE20
            A scenario is one concrete execution; a use case abstracts the related successful and alternative scenarios. Analysis integrates functional (use cases/scenarios), structural/object (classes) and dynamic (states/interactions) models. Entity objects represent domain information such as Incident; boundary objects mediate interaction, such as ReportForm; control objects coordinate a use case. A UI form is normally boundary, not entity.SE13

            Choice by choice

            A · incorrect — The scenario’s entities are passive records rather than the stated coordinator.

            B · incorrect — The form has no persistent modes and is not the use-case coordinator.

            C · correct — The stateful coordinator is a control object.

            D · incorrect — The need depends on significant state behavior, not equality across every object.

            Question 274

            In the ReportEmergency use case example, which boundary object allows the FieldOfficer to initiate the reporting process?

            • A. EmergencyReportForm
            • B. AcknowledgmentNotice
            • C. ReportEmergencyButton
            • D. DispatcherStation

            Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

            Study-guide sections

            SE19 · Sequence diagrams and the emergency-report example

            Study-guide references

            Correct answer: C — ReportEmergencyButton.

            SE19 explicitly says FieldOfficer activates ReportEmergencyButton, supplies details through EmergencyReportForm and later sees AcknowledgmentNotice. DispatcherStation belongs to the dispatcher side. Therefore the button initiates this particular scenario; the form handles later input and the notice reports completion. This is grounded in the named example rather than a generic rule that every use case starts with a button.

            Evidence in the complete study note

            One interaction-diagram layout heuristic puts the initiating actor first, boundary second, control third, then entities. This is not a required UML column order. In ReportEmergency, FieldOfficer activates ReportEmergencyButton, enters details through EmergencyReportForm, and later sees AcknowledgmentNotice; DispatcherStation belongs to the dispatcher side. Choose the button for initiating this particular scenario.SE19

            Choice by choice

            A · incorrect — The form receives incident details after initiation rather than starting the documented scenario.

            B · incorrect — The acknowledgment is seen later as feedback, not used to initiate reporting.

            C · correct — The note explicitly identifies this button as the FieldOfficer’s initiating boundary object.

            D · incorrect — DispatcherStation is on the dispatcher side rather than the FieldOfficer’s initiation interface.

            Question 275

            Generalization in UML modeling is best described as:

            • A. Dividing a class into multiple subclasses with no shared properties
            • B. Identifying a general concept where other concepts are more specific versions of it
            • C. Creating interfaces for external system communication
            • D. Grouping unrelated classes into a package for organization

            Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

            Study-guide sections

            SE18 · Association, aggregation, composition and generalization

            SE16 · Include, extend, generalization and abstract use cases

            Study-guide references

            Correct answer: B — A general concept with more-specific specializations.

            SE16 relates a specialized actor or use case to a more general one; SE18 gives the corresponding class generalization toward a superclass. B expresses that abstraction/specialization relationship. It does not merely package unrelated classes, create an external interface or split classes while denying shared general properties.

            Evidence in the complete study note

            Association connects related instances. A dashed dependency arrow means a client uses a supplier. Generalization uses a solid line and hollow triangle pointing to the superclass/general element. Shared aggregation uses a hollow diamond at the whole end and weak whole-part meaning; it does not by itself define a detailed lifecycle policy.SE18
            Generalization relates a specialized actor/use case to a more general one, with a hollow triangle toward the general element. An abstract use case specifies behavior for specialization and is not directly instantiated as a complete use case. It is not defined merely by reuse or lack of a direct actor line. Included behavior is incorporated where the inclusion is reached; do not infer every conditional branch in the base always executes.SE16

            Choice by choice

            A · incorrect — Specialization is related through a general concept rather than requiring no shared properties.

            B · correct — Generalization identifies the common general element of which other concepts are more specific versions.

            C · incorrect — External communication interfaces do not by themselves define a generalization relationship.

            D · incorrect — Packaging unrelated classes is organizational grouping rather than specialization of a shared general concept.

            Question 276

            The 'high cohesion, low coupling' principle in subsystem design means:

            • A. Subsystems should be tightly interconnected for maximum communication efficiency
            • B. Objects within a subsystem should be closely related, while subsystems themselves should be mostly independent
            • C. Each subsystem should have minimal internal functionality to reduce complexity
            • D. All subsystems should share a single central data repository

            Separate responsibilities inside a component from dependencies across boundaries. Evaluate the stated structure, change and reuse goals without assuming guaranteed benefits.

            Study-guide sections

            SE22 · Cohesion, coupling, modularity and refactoring

            Study-guide references

            Correct answer: B — Related responsibilities within a subsystem, limited dependencies between subsystems.

            SE22 defines cohesion as related purpose within a module and coupling as dependency across modules, then recommends high cohesion and low coupling. B states both dimensions. It does not require minimal functionality, tight cross-connections or one shared repository; those choices can undermine coherent responsibilities or increase dependency rather than establish the principle.

            Evidence in the complete study note

            Cohesion measures how well elements inside a module serve a related purpose; coupling measures dependency between modules. Seek high cohesion and low coupling. Shared mutable data and knowledge of another module’s internal representation increase coupling. Information hiding exposes stable operations while concealing changeable decisions.SE22

            Choice by choice

            A · incorrect — Tight interconnection increases coupling rather than meeting the low-coupling goal.

            B · correct — Closely related internal responsibilities and limited external dependencies express both parts of the principle.

            C · incorrect — Cohesion concerns related purpose, not simply having as little functionality as possible.

            D · incorrect — A shared repository is a style choice and can create dependencies; it does not define cohesion or coupling.

            Question 277

            A safety-critical contract requires traceable assurance records and reviewed verification before release. Waterfall, V-model and spiral proposals include those obligations; the proposed lightweight Agile variant supplies working code but omits the required assurance records. Which proposal is least appropriate as specified?

            • A. Waterfall Model
            • B. V-Model
            • C. Agile Model
            • D. Spiral Model

            Identify whether the scenario prioritizes delivery, learning, adaptation or risk reduction. Several processes can share individual practices, so compare their defining emphasis.

            Study-guide sections

            SE05 · Agile values, stories and Scrum

            SE03 · Waterfall and the V-model

            Study-guide references

            Correct answer: C — Agile Model

            The specified Agile proposal omits mandatory assurance records, so it cannot satisfy the stated contract without modification. The other proposals include those obligations and are not excluded on that ground. This is a judgment about the supplied lightweight variant, not Agile in general: the note explicitly allows Agile to incorporate required documentation and assurance. Stable requirements alone would not establish a universal ranking.

            Evidence in the complete study note

            Scrum uses timeboxed Sprints of at most one month, with a Sprint Goal, selected work and a usable Increment meeting a Definition of Done. Scope is discussed before and during planning; it is not forbidden to agree scope. Timeboxes tend to stay fixed while content is adapted without endangering the goal. Agile can be combined with required assurance/documentation; safety-critical context alone cannot prove it is unsuitable.SE05
            The V-model pairs specification/design stages with later test levels. Requirements inform acceptance tests; system design informs system tests; component/detail design informs integration/unit tests. Coding lies at the bottom. Test planning starts early. Stable requirements and strong assurance may favor this organization, but neither a V shape nor waterfall guarantees safety or correctness.SE03
            Classical waterfall separates planned phases with reviewed deliverables. It fits well-understood, stable requirements and familiar technology; late feedback makes changes costly.SE03

            Choice by choice

            A · incorrect — This proposal includes the required reviewed deliverables.

            B · incorrect — This proposal includes the required assurance obligations.

            C · correct — The specified lightweight variant omits mandatory records and is therefore least suitable as proposed.

            D · incorrect — This proposal includes the stated assurance obligations.

            Question 278

            In a sequence diagram, what does an 'X' (cross) at the end of a lifeline dashed line indicate?

            • A. The object is temporarily inactive
            • B. The object is waiting for a message
            • C. The object ceases to exist at that point
            • D. The object is calling itself recursively

            Match the information to be represented with each model’s purpose. Read relationship direction, boundary and ownership conditions before classifying it.

            Study-guide sections

            SE19 · Sequence diagrams and the emergency-report example

            Study-guide references

            Correct answer: C — Modeled destruction of the object at that point.

            SE19 explicitly identifies X as modeled destruction, so C is correct in UML diagram semantics. Temporary inactivity and waiting do not end an object’s modeled existence, and a recursive message is represented by an interaction rather than destruction. The marker does not guarantee the runtime moment at which a garbage collector reclaims memory.

            Evidence in the complete study note

            Sequence diagrams show interactions across lifelines, with order/time generally downward. Messages cross between participants; activation rectangles show execution. A creation message starts a lifeline; an X marks modeled destruction, not a guarantee about when a garbage collector runs. Synchronous calls wait for completion; asynchronous messages permit the sender to proceed.SE19

            Choice by choice

            A · incorrect — Temporary inactivity does not terminate the object’s lifeline.

            B · incorrect — Waiting for a message does not mean the modeled object has been destroyed.

            C · correct — X marks the object’s modeled destruction at that point, not necessarily immediate memory reclamation.

            D · incorrect — A recursive call is an interaction message and does not use the destruction marker.