An HTML-formatted group assignment brief instructing student teams to produce a use case scenarios and requirements specification document, including effort estimates, AI use policy, and submission guidance, used by students to understand deliverables and by instructors to distribute the task.
Topics
This module covers 7 topics. Open a topic to see its subtopics.
Module Content
28 items.
-
-
The full module reading combining all six topics on Use Case Scenarios and requirements gathering into one continuous, numbered lesson that learners work through to understand how scenarios bridge the gap between stakeholder intent and what developers build.
-
An introductory lesson page defining Use Case Scenarios as structured narratives of user-system interaction, explaining why they matter for preventing project failure and where they fit in the software development lifecycle; learners read it first to build foundational vocabulary.
-
A lesson on identifying everyone who cares about a system — users, roles, departments, external partners, regulators, and automated actors — and techniques for mapping this stakeholder web before writing any use cases or requirements.
-
A lesson surveying requirements elicitation methods (such as interviews, observation, surveys, and workshops) and explaining how poor elicitation propagates costly errors through later project phases; learners use it to choose appropriate techniques for a project.
-
A lesson on task analysis — systematically studying how users actually perform work, including task sequence, decision points, and underlying rationale — used as the evidence base learners draw on before drafting confident use cases.
-
A practical lesson on the craft of writing use case scenarios, covering step-by-step actor actions, preconditions, and conditional flows, which learners follow as a template when authoring their own scenario documents.
-
A lesson on moving beyond the 'happy path' to enumerate alternate flows, exceptions, unexpected inputs, and edge-case conditions, giving learners strategies for making scenario coverage comprehensive.
-
A closing lesson on organizing, presenting, and maintaining requirements documentation so that different audiences can find and absorb it and so it stays accurate and actionable as the project evolves.
-
This reading introduces use case scenarios as a structured narrative technique for capturing user-system interactions, explaining why they exist, what they contain, and how development teams use them to bridge the gap between stakeholder intent and what is actually built.
-
This reading explains how to identify the full range of stakeholders and users connected to a system — including internal roles, external partners, and regulators — and guides learners through the process of mapping who cares about a system before any requirements or use cases are written.
-
This reading surveys the major requirements elicitation methods — such as interviews, workshops, observation, and surveys — describing how each technique works, when to apply it, and how analysts use them together to discover and articulate what a system must do and the qualities it must possess.
-
This reading covers task analysis as a systematic method for studying how users actually perform their work, including the sequence of steps, decisions, and goals involved, and explains how analysts use this understanding as a foundation for writing accurate use cases and interface designs.
-
This reading provides step-by-step guidance on composing well-formed use case scenarios, covering the roles of actors, the structure of main and alternative flows, preconditions and postconditions, and the craft and discipline required to produce clear, complete scenario documentation.
-
This reading addresses how to move beyond the 'happy path' by systematically identifying alternative usage paths, edge cases, and boundary conditions, and explains techniques designers and analysts use to enumerate and account for unexpected user behavior and real-world variability.
-
This reading explains how to organize, present, and maintain requirements and use case documents for different audiences — including developers, stakeholders, and testers — covering document structure, version control, communication strategies, and keeping documentation accurate as projects evolve.
-
This reading explains how to organize, present, and maintain requirements and use case documents for different audiences — including developers, stakeholders, and testers — covering document structure, version control, communication strategies, and keeping documentation accurate as projects evolve.
-
A foundational reading that defines a use case scenario as a structured account of an actor's step-by-step interaction with a system, covering actors, goals, preconditions, system responses, and success criteria, used by learners as the conceptual starting point before writing their own scenarios.
-
A reading on stakeholder analysis that distinguishes end users from the people who fund, approve, maintain, or regulate a system and shows how to systematically enumerate and prioritize everyone with an interest in it, used by learners to identify whose needs a use case must represent.
-
A reading surveying requirements elicitation methods — interviews, observation, surveys, and related techniques — for drawing out user goals, operating conditions, constraints, and success measures from stakeholders, used by learners to plan how they will collect requirements before designing an interface.
-
A reading on task analysis that explains how to observe or interview users and decompose their work into goals, sub-goals, action sequences, decisions, and information needs to produce a task model, used by learners to ground interface features in what people actually do.
-
A practical reading on drafting use case scenarios, covering how to name the actor, write the step sequence from intention to result, and specify preconditions and postconditions rather than screens or code, used by learners as a template for authoring their own scenarios.
-
A reading that pushes beyond the 'happy path' to enumerate alternate flows and edge cases such as dropped connections, unusual characters in input, language switching, screen-reader use, and other real-world conditions, used by learners to stress-test and expand their scenario coverage.
-
A reading on requirements documentation and communication, addressing where use cases are stored, how they are named, versioned, and traced back to the requirements they satisfy, and how to share them with a project team, used by learners to make their scenarios usable artifacts rather than private notes.
-
A consolidated single-page compilation of all seven module topics, from the introduction to use case scenarios through stakeholder analysis, elicitation techniques, task analysis, scenario writing, edge cases, and documentation, used for continuous reading, review, or printing of the full module.
-
A five-question matching quiz bank covering use case components and their definitions, flow types, sources of ambiguity in use case steps, use case templates and their origins, and writing guidelines for specific use case sections, used to assess learners' understanding of use case terminology and structure.
-
A Markdown-formatted version of the same group assignment asking student teams to develop use case scenarios and a requirements specification, covering the same scope, policies, and expectations as the HTML counterpart, used as a portable or LMS-importable alternative for the same task.
-
An HTML assignment sheet for Phase 2 of the semester group project directing student teams to conduct stakeholder analysis, requirements gathering, and use case development as a continuation of Phase 1, used by students to complete their next project milestone and by instructors to assess progress toward the full system design.