Skip to content

Commit

Permalink
Updated the Actors and made some gramatical edits.
Browse files Browse the repository at this point in the history
  • Loading branch information
bryonbaker committed Apr 5, 2024
1 parent f146979 commit efd08f8
Showing 1 changed file with 22 additions and 18 deletions.
40 changes: 22 additions & 18 deletions docs/user-stories.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,38 +6,42 @@ title: User stories

The intent of these user stories is to provide a north star for this project.

## User stories

- As an enterprise application developer I want to be able to serve (multiple) LLM applications from my platform
## Actors

- As business application owner I want my LLM to be up to date with my systems of record
- Application Developer:

- As a data engineer I need to manage the lifecycle of data surrounding an LLM application including: Ingestion & preparation; building training datasets; Collecting QA data.
- Business application owner:
The Business Application Owner is concerned with the business value the LLM delivers.

- As a data scientist I want to be able to produce an optimised LLM model to support the enterprise use case.
- Data engineer:
The Data Engineer actor is responsible for accessing, importing, and preparing data that is used by the LLM.

- As a data scientist I want ready access to the latest opensource LLM innovations without getting in trouble with security.
- Data scientist:

- As an platform engineer I want to provide a platform enabling self-service for LLM development from experiment to production, while maintaining efficient use of the infrastructure (as a service) investment
- Platform engineer:

- As a security architect I want my LLM development to meet my enterprise wide security policies and controls.
- Security architect:

- As a security architect I want to be able to measure and enforce that software, models and data come from trusted sources.
- Security engineer:

- As a SOC analyst I want sufficient capabilities to detect, investigate and correct security related events as they apply to the LLM platform and workloads
## User stories

## Actors
- As an Application Developer I want to be able to serve (multiple) LLM applications from my platform.

- As Business Application Owner I want my LLM to be up to date with my systems of record.

- Application Developer
- As a Data Engineer I need to manage the lifecycle of data surrounding an LLM application, including: Ingestion & preparation; building training datasets; Collecting QA data.

- Business application owner
- As a Data Scientist I want to be able to produce an optimised LLM model to support the business use case.

- Data engineer
- As a Data Scientist I want ready access to the latest opensource LLM innovations without getting in trouble with security.

- Data scientist
- As a Platform Engineer I want to provide a platform enabling self-service for LLM development from experiment to production, while maintaining efficient use of the infrastructure (as a service) investment

- Platform engineer
- As a Security Architect I want LLM development initiatives to comply with my enterprise-wide security policies and controls.

- Security architect
- As a Security Architect I want to be able to measure and enforce that all software, models, and data come from trusted sources.

- As a SOC analyst I want sufficient capabilities to detect, investigate and correct security related events as they apply to the LLM platform and workloads

- Security engineer

0 comments on commit efd08f8

Please sign in to comment.