volume_mute

Why UML May Not Be Needed

publish date: 2026/06/13 06:39:46.934805 UTC

volume_mute

In which of the following situations would using the UML to document a design NOT be the right approach?

When team members are geographically distributed and need a precise shared design artifact

When developing a system with a plan-driven process where design is done in one organization and implementation in another

When the system requires detailed dependability analysis or must demonstrate conformance to external regulators

When developing using a dynamically typed language like Python, where the design process is agile and design decisions are left to programmers working from informal sketches

Correct Answer

When developing using a dynamically typed language like Python, where the design process is agile and design decisions are left to programmers working from informal sketches

Explanation

Using the UML is less appropriate when: using a dynamically typed language like Python (UML is most useful for statically typed OO languages like Java or C#); using agile methods (which work from informal sketches and leave design decisions to programmers); or configuring an off-the-shelf package (no point designing objects if implementing by configuring a package). UML is most valuable for plan-driven development with geographically distributed teams, detailed documentation requirements, or regulatory compliance.

Reference

Software Engineering, Ian Sommerville, 10th edition

Quizzes you can take where this question appears

Design and Implementation - Review