I. Use Case Description | |
Use Case Name | Index analysis for ETF development |
Use Case Identifier | IND-EFT-DEV |
Source | IND Content Team |
Point of Contact | |
Creation / Revision Date | 7/19/2019 |
Associated Documents | Requirements documentation, traceability matrix if applicable |
...
Use cases proposed by Ashwin via JIRA include the following, which we will flesh out into more complete scenarios:
- Get the value of Index at any point in time. Optionally the user can seek details of the constituents' contribution to the movement of index value from a particular point in time (e.g. previous day's close) - JIRA Issue IND-86
- As a user of the Index service, I need to be able to get all the details of the constituents of the Index including the weightage and other details - JIRA Issue IND-85, IND-81
- To ensure stability of the index, the index constituents are changed at regular interval. Whenever this is done there is a need to "rebalance" the index so that the change in constituents does not change index level abruptly - JIRA Issue IND-83
- There are certain corporate actions of the Index constituents (like stock splits and stock dividends) that require changes to be done to the Index data maintained. Other examples are share issuance and these require adjustments to prevent the value of index from changing. - JIRA Issue IND-84
...
IV. Competency Questions
- What are the constituents of this index as of a given date?
- What is the value (price) of this index on a certain date? What are the prices for the constituents of this index as of this date and how are they weighted?
- What indices have a given equity as a constituent as of a given date?
...
Describe at least one way you expect to use the semantics and/or provenance to propose an answer to the questions. Include an initial description of why the semantics and/or provenance representation and reasoning provides an advantage over other obvious approaches to the problem. (optional – depending on the use case and need for supporting business case).
...
V. Resources
In order to support the capabilities described in this Use Case, a set of resources must be available and/or configured. These resources include the set of actors listed above, with additional detail, and any other ancillary systems, sensors, or services that are relevant to the problem/use case.
...
Data | Type | Characteristics | Description | Owner | Source | Access Policies & Usage |
(dataset or repository name) | (remote, local/in situ, etc.) | e.g. – no cloud cover | Short description of the dataset, possibly including rationale of the usage characteristics |
| Source (possibly a system, or remote site) for discovery and access |
|
|
|
|
|
|
|
|
...
VI. References and Bibliography
List all reference documents – policy documents, regulations, standards, de-facto standards, glossaries, dictionaries and thesauri, taxonomies, and any other reference materials considered relevant to the use case
...
VII. Notes
There is always some piece of information that is required that has no other place to go. This is the place for that information.
...