Page Comparison

II. Use Case Summary

GoalDescribe briefly the goal the use case is intended to satisfy

Enable equity index selection as the underlying for a new fund

Requirements

State any requirement(s)specific to this use case, including any capabilities from a business architecture or process model that the use case supports, any metrics or other reporting requirements, etc., including any reference identifier for the requirement(s), as applicable

ScopeIdentify any known boundaries and the intended scope of the use case

Coverage is limited to equity indices rather than indices that include credit indices or economic indicators for this initial use case.

Priority

Identify the priority of the use case (with respect to other use cases for the project)

Stakeholders

Identify all known stakeholders for the use case

Description

Summarize the use case, capturing the essential objectives (no longer than a page), including a quick overview, restated goals, and principal actor(s).

User stories, if applicable, and any narrative mapped from those user stories to usage scenarios should be included in the Usage Scenarios section, below.A business analyst/front-office salesperson is interested in selecting one or more equity indices as the basis for developing a new exchange-traded fund (ETF).  This may require understanding the make-up of an index with respect to its composition based on a balance of small, medium, and large cap organizations, overall performance during some prior period, based on a mix of national and international instruments, based on avoiding being overly exposed to a single sector, company, or country, etc. in order to meet the performance goals of the fund.  In general, the goal is either for the fund to track the index or for its performance to exceed that of the index.

Assumptions:  The business analyst has a template for defining the contents of the fund provided by their organization that allows them to vary the index based on desired goals. 

Actors / Interfaces

List actors: people, systems, knowledge bases, repositories, and other data resources, services, sensors, or other “things” outside the system that either act on the system (primary actors) or are acted on by the system (secondary actors). Primary actors are those that invoke the use case and benefit from the result. Identify the primary actor and briefly describe role. 

Any actor that is external to or outside the control of the use case owner should be further described under Resources, below.

Pre-conditions

Identify any assumptions about the state of the system that must be met for the trigger (below) to initiate the use case.  Any assumptions about the state of other related systems can also be stated here.  List all preconditions.

Post-conditions

Provide any conditions that will be true of the state of the system after the use case has been completed.

Triggers

Describe in detail the event or events that initiate the execution of this use case.  Triggers can be external, temporal, or internal.  They can be single events or a complex event that indicates that some set of conditions has been met.

Performance Requirements

List any known performance-specific requirements – timing and sizing (volume, frequency, etc.), maintainability, reusability, other “-ilities”, etc.

Assumptions

Open Issues