User Story
See also: <Optional link(s) to related information -e.g., links to a functional requirements page.>A user should be able to add an afiiliation for a person instance, linking the person to an Organization. View, edit and delete operations must similarly be supported. There may be multiple instances of affiliations. Users will expect to be able to pivot from a Person to Organizations, and navigate direclty from one to the other.
Related User Stories:
- <link to a related User Story>
- ...
Derived Stories:
These related stories are created or derived from the User Story described on this page. For example, Service Stories describe bits of functionality that a service might need to provide in order for the User Story requirement to be fulfilled. These stories are used to create, plan, and track specific development tasks in JIRA. If development has begun on one of these stories, there should be a link into JIRA describing the story and the related development tasks.
Service Layer Stories
Relation Service Story: Consumer can add new Person-Organization relation.
Relation Service Story: Consumer can view current Person-Organization relations.
Relation Service Story: Consumer can view and update details for a given Person-Organization relation.
Relation Service Story: Consumer can delete a given Person-Organization relation.
Application Layer Stories
Application Story: <Describe a bit of functionality required by the UI layer components as clients.>
Application Story: <Describe a bit of functionality required by the UI layer components as clients.>
UI Layer Stories
UI Story: <Describe a bit of end-user functionality and interaction with UI components.>
UI Story: <Describe a bit of end-user functionality and interaction with UI components.>
Add Comment