Template for requirements use cases

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Software Requirements Gathering, Analysis, Quality and Testing Problems caused by skipping analysis stage of SDLC Software development life cycle phases, iterations, explained step by step Waterfall versus iterative development misconceptions Differentiating between Functional and Nonfunctional Requirements Writing a software requirements specification (SRS) for a portal app Should QA check changes from outside the requirements document? Software testing metrics for a medium-sized project What should a business analyst's requirements document include? Is a requirements freeze in a software project a bad idea? Requirements elicitation: Workshops vs. apprentice-style analysis Use cases and misuse cases Requirements practices evolving, but organizations still struggle Defining report requirements with use cases How requirements use cases facilitate the SDLC Excelling in the art and science of requirements elicitation Requirements use cases tutorial: Advanced formats, test case comparisons Use cases for software requirements tutorial: Strengths, flaws, formats Writing a software requirements specification (SRS) for a portal app Agile software development tutorial: Agile requirements gathering Pros and cons of requirements-based software testing How to avoid requirements creep Software Requirements Documentation VisibleThread aims to boost IT documentation quality, improve processes When it comes to requirements, what is 'just enough'? How to deliver, implement testable software requirements Blueprint rolls out Requirements Center 2010 Writing a software requirements specification (SRS) for a portal app Should QA check changes from outside the requirements document? Agile software development tutorial: Agile requirements gathering Defining requirements during software project feasibility analysis What should a business analyst's requirements document include? Determining software testing deliverables for a small project

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary use case  (SearchSoftwareQuality.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

I'm not sure I understand this question and therefore doubt that I've answered it satisfactorily. It can be interpreted in several ways, and none of them makes total sense to me. For instance, Google lists jillions of templates for reports on various topics; but I'm pretty sure that's not what the question is about. I'll try to give an answer for each interpretation that occurs to me, and I encourage readers to share their thoughts.

A use case is defined as how an actor interacts with the system. An actor is usually the user but could also be another system or piece of hardware. The system could be a business process but is usually a computer system. The bulk of a use case consists of sets of step-by-step actions involved in the interaction. Each separate way the use case can be carried out is called a path or scenario. The main path (or "happy path") describes the normal or most common success scenario. Alternative paths describe other ways to succeed. Exception paths describe ways that the use case fails to meet its goal.

Interpretation 1: The use case describes how to produce the report.

In general, use cases are good for describing externally observable actions involved in carrying out some task or process, but use cases are not intended or well-suited for describing business rules, quality factors, database manipulations or computer program logic design. Thus, my initial reaction is that I find it hard to think of producing a report in terms of a use case, and I have no idea how a template would fit in. To me, producing reports mainly involves programming logic to access databases, manipulate data formats and apply business rules. Yes, a program carries out these actions step by step, but I believe I'm safe in saying that most use case authorities would not consider description of program logic to be a use case.

Interpretation 2: The use case describes how to identify what the report's contents and format should be.

A Google search revealed two relevant articles on use cases to design a report or template. Geri Schneider Winters says, "If you are going to use a use case to describe a report, what you really want to describe is what job or task a person is doing when he or she creates and views a report" (in "Tips for Business Analysts: Use Cases and Reports").

The Sakai Project, discussing documentation requirements for the OSP Report tool, refers to "use cases to determine report parameters, fields and layouts and allow developers to easily create report templates."

Interpretation 3: The use case describes the process to write requirements for a report.

In this instance, the use case would describe steps such as:

• Meet with users to ascertain what needs the report should meet.
• Identify sources of relevant data.
• Define data manipulation and business rules.
• Design the report layout.
• Review the report layout with the users.
• Create a template for producing the report.
• Prototype the report preparation using the template.
• Adjust the template as necessary.