task_categories:text-generation task_categories:text2text-generation task_categories:question-answering size_categories:n<1K format:parquet modality:text library:datasets library:pandas library:mlcroissant library:polars library:distilabel region:us synthetic distilabel rlaif datacraft
---
size_categories: n<1K
task_categories:
- text-generation
- text2text-generation
- question-answering
dataset_info:
  features:
  - name: prompt
    dtype: string
  - name: completion
    dtype: string
  - name: system_prompt
    dtype: string
  splits:
  - name: train
    num_bytes: 447115
    num_examples: 100
  download_size: 187715
  dataset_size: 447115
configs:
- config_name: default
  data_files:
  - split: train
    path: data/train-*
tags:
- synthetic
- distilabel
- rlaif
- datacraft
---

<p align="left">
  <a href="https://github.com/argilla-io/distilabel">
    <img src="https://raw.githubusercontent.com/argilla-io/distilabel/main/docs/assets/distilabel-badge-light.png" alt="Built with Distilabel" width="200" height="32"/>
  </a>
</p>

# Dataset Card for User_Story_Generated

This dataset has been created with [distilabel](https://distilabel.argilla.io/).



## Dataset Summary

This dataset contains a `pipeline.yaml` which can be used to reproduce the pipeline that generated it in distilabel using the `distilabel` CLI:

```console
distilabel pipeline run --config "https://huggingface.co/datasets/DerekCho91/User_Story_Generated/raw/main/pipeline.yaml"
```

or explore the configuration:

```console
distilabel pipeline info --config "https://huggingface.co/datasets/DerekCho91/User_Story_Generated/raw/main/pipeline.yaml"
```

## Dataset structure

The examples have the following structure per configuration:


<details><summary> Configuration: default </summary><hr>

```json
{
    "completion": "**Refined User Stories with Additional Details and Acceptance Criteria**\n\n### User Story 1: User Authentication and Profile Management\n\n**Title:** Secure User Authentication with Profile Management\n\n**Description:**\n\nAs a user, I want to be able to create an account and manage my profile information to ensure that I can securely access the system and have a personalized experience.\n\n**Acceptance Criteria:**\n\n* **Create Account:**\n\t+ The user can create an account with a unique username (username should follow the defined format, e.g., alphanumeric characters and 3-20 characters long) and password (password should follow the defined format, e.g., alphanumeric characters and 8-32 characters long).\n\t+ The system checks for existing usernames before allowing registration and provides a unique username suggestion if the entered username is taken.\n* **Edit Profile:**\n\t+ Users can edit and update their email, phone number, and profile picture.\n\t+ The system validates the new email and phone number for accuracy before accepting changes.\n\t+ The system stores the profile picture securely and displays it correctly on the user dashboard.\n* **Secure Authentication:**\n\t+ The system remembers the user\u0027s authentication credentials for future logins using a secure token-based system.\n\t+ Password and salting ensures secure password storage (use a password hashing algorithm like bcrypt or PBKDF2).\n\t+ The system sends a confirmation email with a link to activate the account.\n* **Security Measures:**\n\t+ The system implements a rate limit on login attempts to prevent brute-force attacks.\n\t+ The system logs failed login attempts with the IP address and user agent for security analysis.\n\n### User Story 2: User Data Management\n\n**Title:** User Data Management and Validation\n\n**Description:**\n\nAs a user, I want to be able to view, edit, and delete my personal and contact information to maintain accurate and up-to-date records.\n\n**Acceptance Criteria:**\n\n* **View and Edit Profile:**\n\t+ Users can view their personal and contact information.\n\t+ Users can edit and update their personal and contact information.\n\t+ The system validates field input for data accuracy before accepting changes (e.g., email validation, phone number format).\n* **Delete Profile:**\n\t+ Users can delete their personal and contact information after confirmation.\n\t+ The system prompts users to confirm the deletion of their profile information.\n\t+ The system permanently deletes the user\u0027s data after a specified time period (e.g., 30 days) if no activity is detected.\n\n### User Story 3: Secure Payment Gateway\n\n**Title:** Secure Payment Processing with Trusted Payment Gateway\n\n**Description:**\n\nAs a user, I want to be able to securely process payments through a trusted payment gateway to ensure convenient purchases.\n\n**Acceptance Criteria:**\n\n* **Integration with Payment Gateway:**\n\t+ The system integrates with a trusted payment gateway for secure transactions.\n\t+ The system implements a secure tokenization process for sensitive payment information.\n* **Secure Payment Entry:**\n\t+ Users can securely enter payment information (e.g., credit card number, expiration date, CVV).\n\t+ The system masks sensitive payment information for display.\n* **Payment Processing:**\n\t+ The system processes payments with the selected payment method.\n\t+ Payment confirmations are shown with transaction details.\n* **Security Measures:**\n\t+ The system implements a secure payment tokenization process to minimize sensitive data exposure.\n\t+ The system logs payment transactions with sensitive information redacted for security analysis.\n\n### User Story 4: User Support\n\n**Title:** Responsive User Support\n\n**Description:**\n\nAs a user, I want to be able to contact support for assistance with any issues or concerns to provide a helpful and responsive customer experience.\n\n**Acceptance Criteria:**\n\n* **Submit Support Ticket:**\n\t+ Users can access and submit a support ticket through the system.\n\t+ The system sends a confirmation email with the support ticket details.\n* **Timely Response:**\n\t+ Support staff respond to tickets within a specified time frame (e.g., 24 hours).\n\t+ The system tracks the status of support tickets.\n* **Ticket Status Update:**\n\t+ Users can view and update their support ticket status.\n\n### User Story 5: Data Encryption\n\n**Title:** Secure Data Storage with Encryption\n\n**Description:**\n\nAs a user, I want my sensitive information to be encrypted to maintain confidentiality and security.\n\n**Acceptance Criteria:**\n\n* **Data Encryption:**\n\t+ All user sensitive data is stored encrypted using a recent encryption standard (e.g., AES-256).\n\t+ The system implements key management for secure encryption and decryption.\n* **Secure Key Exchange:**\n\t+ The system securely exchanges encryption keys between users and the system.\n\t+ The system implements secure key storage and management.\n\n### User Story 6: Data Backup\n\n**Title:** Automated Data Backup and Recovery\n\n**Description:**\n\nAs a user, I want my data backed up to prevent loss of important information.\n\n**Acceptance Criteria:**\n\n* **Regular Backup:**\n",
    "prompt": "**User Story 1: User Authentication and Profile Management**\n\nAs a user, I want to be able to create an account and manage my profile information to ensure that I can securely access the system and have a personalized experience.\n\n**Acceptance Criteria:**\n\n* The user can create an account with a unique username and password.\n* The system checks for existing usernames before allowing registration.\n* Users can edit and update their email, phone number, and profile picture.\n* The system remembers the user\u0027s authentication credentials for future logins.\n* Password hashing and salting ensures secure password storage.\n\n**User Story 2: User Data Management**\n\nAs a user, I want to be able to view, edit, and delete my personal and contact information to maintain accurate and up-to-date records.\n\n**Acceptance Criteria:**\n\n* Users can view their personal and contact information.\n* Users can edit and update their personal and contact information.\n* Users can delete their personal and contact information after confirmation.\n* The system validates field input for data accuracy before accepting changes.\n\n**User Story 3: Secure Payment Gateway**\n\nAs a user, I want to be able to securely process payments through a trusted payment gateway to ensure convenient purchases.\n\n**Acceptance Criteria:**\n\n* The system integrates with a trusted payment gateway for secure transactions.\n* Users can securely enter payment information.\n* The system processes payments with the selected payment method.\n* Payment confirmations are shown with transaction details.\n\n**User Story 4: User Support**\n\nAs a user, I want to be able to contact support for assistance with any issues or concerns to provide a helpful and responsive customer experience.\n\n**Acceptance Criteria:**\n\n* Users can access and submit a support ticket through the system.\n* Support staff respond to tickets in a timely manner.\n* Users can view and update their support ticket status.\n\n**User Story 5: Data Encryption**\n\nAs a user, I want my sensitive information to be encrypted to maintain confidentiality and security.\n\n**Acceptance Criteria:**\n\n* All user sensitive data is stored encrypted. \n* The system uses a recent encryption standard and key management.\n\n**User Story 6: Data Backup**\n\nAs a user I want my data backed up regularly to prevent loss of important information.\n\n**Acceptance Criteria:**\n\n* User data is backed up on a regular schedule.\n* Backup is stored securely offsite.",
    "system_prompt": "You are a senior software developer responsible for crafting concise and detailed user stories based on user requirements. Your purpose is to assist in capturing the needs and goals of users, breaking them down into actionable tasks, and defining acceptance criteria for development teams. Provide clear, well-structured user stories that prioritize key features, outline workflows, and ensure seamless integration with other development efforts. Ensure that user stories are easy to understand, testable, and align with overall project goals. User questions are direct and concise."
}
```

This subset can be loaded as:

```python
from datasets import load_dataset

ds = load_dataset("DerekCho91/User_Story_Generated", "default")
```

Or simply as it follows, since there's only one configuration and is named `default`: 

```python
from datasets import load_dataset

ds = load_dataset("DerekCho91/User_Story_Generated")
```


</details>




