Learn how use cases and activity diagrams make system goals clearer and easier to discuss. Use cases describe user interactions and desired outcomes, while activity diagrams map the flow of work. Together, they help teams spot gaps and dependencies early—and keep requirements tied to real user needs.

Multiple Choice

What are two effective approaches to detail and refine specified goals in system development?

The correct answer emphasizes the effective use of use cases and activity diagrams to specify and refine goals in system development. Use cases provide a clear description of how users will interact with the system, highlighting the user requirements and desired outcomes. They help ensure that the goals are aligned with user needs and can be easily understood by both technical and non-technical stakeholders. Activity diagrams complement this by illustrating the flow of activities and interactions involved in achieving the specified goals. By mapping out these processes visually, stakeholders can identify any gaps, overlaps, or dependencies, leading to a more nuanced understanding of the goals and how they can be achieved effectively. This approach not only clarifies requirements but also enhances communication among team members, making it easier to address potential challenges early in the development process. By using these tools together, developers can create a comprehensive roadmap for system functionalities, ensuring that all stated goals are achievable and well-defined. Other approaches may lack the clarity and structured methodology of use cases and activity diagrams, making them less effective in refining goals for system development.

A system goal can sound clear until a team tries to build around it. “Make order handling faster,” for example, feels specific enough in a meeting. But faster for whom? Which steps should change? How will anyone know the result is better? In system development, refining goals means turning broad intentions into descriptions that people can understand, discuss, and connect to real system behavior.

Two useful approaches are to describe goals through use cases and activity diagrams, and to break broad goals into smaller ones with a goal tree. They serve different purposes. One shows how people and a system work together; the other clarifies what the goal itself contains. Used side by side, they help teams move from a high-level ambition to a more concrete picture of what needs to happen.

Start with the people and their goals

A use case describes how an actor—often a user, but sometimes another system—interacts with a system to achieve an outcome. It usually sets out a goal, the conditions before the interaction begins, the main steps, and possible exceptions.

Suppose a company wants to reduce the time needed to process a customer return. A use case might describe how a service agent finds an order, checks whether it qualifies for return, records the item, and starts a refund. The goal is no longer just “make returns faster.” The team can see who needs to do what, what information is involved, and where the system should help.

That shift matters because goals can hide assumptions. Does the agent need to find an order by number, email address, or both? Can a customer begin a return without speaking to an agent? What happens if the item is outside the return period? A well-framed use case brings these details into view without turning the conversation into a long list of technical features.

Use cases also create a shared reference point. A product manager might focus on customer experience, while a developer thinks about data and system behavior. A support lead may notice that an exception happens every day, not once in a blue moon. When everyone can follow the same scenario, those different perspectives have somewhere to meet.

Give the story a shape with an activity diagram

A written use case is useful, but long descriptions can be hard to scan. An activity diagram adds a visual view of the steps, decisions, and paths involved in reaching a goal. It can show where work begins, which actions follow, and what happens when the process branches.

For a return, the diagram might show an agent entering an order number, the system checking the purchase date, and a decision point: is the item eligible? If yes, the refund process continues. If not, the agent receives a clear reason and may offer another route. The diagram makes the process visible at a glance.

This is more than a tidy picture for a document. It helps a team spot gaps and awkward handoffs. If the diagram shows a decision but no next step for one outcome, something is missing. If three different paths all lead to the same action, the team may be able to simplify the flow. And if a task moves between departments, the diagram can reveal a dependency that had been buried in prose.

Use cases and activity diagrams work well together because they answer related but distinct questions. The use case explains the interaction and the outcome from an actor’s point of view. The activity diagram shows the flow of work that supports it. One tells the story; the other lays out the route.

Still, diagrams should clarify, not decorate. A crowded chart with every minor detail can be as hard to read as a dense paragraph. Teams should show the decisions and actions that matter to the goal, then add more detail when a particular area needs closer attention.

Break a big goal into smaller ones

A second approach is to use a goal tree. The tree starts with a broad goal and divides it into more concrete subgoals. These smaller goals describe the conditions or outcomes needed to achieve the larger one.

Take “reduce the time needed to process a customer return.” A team might divide it into goals such as:

  • Help an agent find the right order quickly.

  • Make return eligibility clear.

  • Reduce repeated entry of customer and item details.

  • Ensure the refund reaches the correct payment method.

Each subgoal can then be examined on its own. “Help an agent find the right order quickly” may lead to more precise goals, such as searching by order number or customer email. “Make return eligibility clear” may require the system to show the relevant policy and explain why an item qualifies or does not qualify.

This breakdown is valuable because broad goals often combine several concerns. A single statement may mix speed, accuracy, customer satisfaction, and staff workload. A goal tree helps separate those concerns so a team can see what success depends on. It also makes it easier to notice missing pieces: a process might be fast but still fail if it sends a refund to the wrong place.

The tree is not a feature list, though it can help shape one later. A feature says what a system can do; a goal says what people need to achieve. Keeping that distinction clear helps teams avoid jumping straight from a vague ambition to a favorite solution.

These tools complement each other

Goal trees and use cases are not rivals. They look at refinement from different angles. A goal tree asks, “What smaller outcomes must support this larger one?” A use case asks, “How does an actor interact with the system to reach an outcome?” An activity diagram then shows how the interaction flows.

For example, a goal tree may reveal that a return process needs faster order lookup and clearer eligibility decisions. Use cases can show how agents and customers carry out those tasks. Activity diagrams can map the steps and decision points, including what happens when a search fails or a return is not eligible.

This combination also helps people discuss feasibility. A goal should not be replaced simply because it is difficult. First, the team needs to understand what the goal means and what supports it. If a requirement cannot be met as stated, that is a reason to revisit the constraints and discuss alternatives—not to quietly invent a different goal. Clear refinement gives stakeholders a solid basis for that conversation.

Keep the goal connected to its purpose

Refinement can go too far. A team may produce diagrams and subgoals that are precise but no longer connected to the reason the work began. To avoid that, keep the broader goal visible as details are added. Ask whether each subgoal supports it, and whether the described system behavior genuinely helps an actor reach the intended outcome.

It also helps to review goals with people who know the work firsthand. A service agent may point out that the “usual” return process changes during busy periods. A customer may care less about saving one minute than about knowing when a refund will arrive. Those details can reshape both the use case and the goal tree—and make them more realistic.

In the end, refining goals is a way to turn a shared intention into something a team can reason about. Use cases and activity diagrams make interactions and flows clearer. Goal trees make broad ambitions more concrete by showing the outcomes beneath them. Together, they provide a practical bridge from “what we hope to achieve” to “what the system and its users need to do.”