volume_mute

Planned vs. Unplanned Emergent Behavior

publish date: 2026/06/18 05:28:22.071742 UTC

volume_mute

A development team integrates an authentication component with a database update component. They discover that together they enforce a rule that only authorized users can update data - a behavior not present in either component alone. They also discover an unexpected interaction that causes the system to allow duplicate entries in some edge cases. Classify each observed behavior:

drag and drop the selected option to the right place

Correct Answer

(1) Only authorized users can update data - enforced by integration of both components,Planned emergent behavior
(2) Unexpected duplicate entries allowed in edge cases,Unplanned emergent behavior

Explanation

Planned emergent behavior is functionality anticipated by the design that only appears when components are integrated - such as access control arising from combining authentication and database components. Unplanned emergent behavior is unexpected and unwanted - like duplicate entries appearing due to unforeseen component interactions. System tests must check for both.

Reference

Software Engineering, Ian Sommerville, 10th edition

Quizzes you can take where this question appears