...
II. Use Case Summary | |
Goal | Enable development of a new fund whose performance can be compared to a benchmark |
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 |
Scope | Coverage is limited to equity indices rather than indices that include credit indices or economic indicators for this 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). A business analyst/front-office salesperson is interested in selecting one or more equity indices as the basis for predicting/comparing the performance of a new exchange-traded fund (ETF). This may require understanding the make-up of a benchmark 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, which will be covered under the CIV FCT, not herehowever the goal of this use case is for limited comparison. In other words, we will not necessarily create a number of sector classification schemes for this use case. In general, the goal is either for the fund to track the index or for its performance to exceed that of the index. This means being able to describe 10- 15 benchmarks that are commonly used, without detailed sector classification, but sufficient to distinguish one major index from another. This initial use case involves limiting the scope to equities only. We will create a subsequent use case to cover bond/debt indicies. We will only use content that is published about each of the indexes, and avoid classification issues assumptions about classification schemes (at least, in depth classification) for the purposes of this use case. 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 |
|
...