Generative Development Framework
GDF.ai
  • Intro to GDF-FSE
    • Generative AI, Large Language Models, ChatGPT?
    • Knowledge Areas
    • Access a Chat Based LLM
    • Why GDF?
    • Expectations
  • Limitations
  • Prompting
    • Prompt Patterns
    • Prompt Context
    • Prompt Stores
    • Prompt Operators
    • Prompt Chaining
  • Security
    • Protecting Data
    • Protecting Application Security
    • Protecting Intellectual Property
    • Protection Stores
    • AI Security Assessments and Penetration Testing
    • Social Engineering Testing with AI
  • Subject Knowledge Areas
    • Ideation
      • Identifying a Problem Statement
      • Plan and Prioritize Features
      • Develop User Stories
      • Requirement Gathering
      • Ideation Prompting
      • Ideation Template
    • Specification
      • Specifying Languages
      • Specifying Libraries
      • Specifying Project Structures
      • Specify Schemas
      • Specifying Elements
      • Specifying API Specs
    • Generation
      • Generating UI Elements
      • Generating Mock Data
      • Generating Schemas
      • Generating Parsers
      • Generating Databases
      • Generate Functions
      • Generate APIs
      • Generate Diagrams
      • Generating Documentation
    • Transformation
      • Converting Languages
      • Converting Libraries
    • Replacement
      • Replacing Functions
      • Replacing Data Types
    • Integration
      • Connecting UI Components
      • Connecting UI to Backend
      • Connecting Multiple Services Together
      • Connecting Cloud Infrastructure (AWS)
    • Separation
      • Abstraction
      • Model View Controller (MVC)
    • Consolidation
      • Combining UI Elements
      • Deduplicating Code Fragments
    • Templating
      • Layouts
      • Schemas
      • Project Structures
      • Content Management Systems
    • Visualization
      • General Styling
      • Visual Referencing
      • Visual Variations
    • Verification
      • Test Classes
      • Logging and Monitoring
      • Automated Testing
      • Synthetic Monitoring
    • Implementation
      • Infrastructure
      • DevOps / Deployment
    • Optimization
      • General Optimization
      • Performance Monitoring
      • Code Review
  • Guidance
    • Business Process
    • Regulatory Guidance
  • Generative Pipelines
  • Troubleshooting
    • Client Side Troubleshooting
    • Server Side Troubleshooting
    • Troubleshooting with AI
    • Documentation
    • Infrastructure Engineering
  • Terminology
Powered by GitBook
On this page
  • User Story 1: User Registration
  • Acceptance Criteria:
  • User Story 2: Search Bicycles
  • Acceptance Criteria
  • User Story 3: Rent Bicycle
  • Acceptance Criteria
  • User Story 4: Return Bicycle
  • Acceptance Criteria:
  • Summary

Was this helpful?

Export as PDF
  1. Subject Knowledge Areas
  2. Ideation

Develop User Stories

Developing and refining user stories through generative AI

PreviousPlan and Prioritize FeaturesNextRequirement Gathering

Last updated 3 months ago

Was this helpful?

Now that we have features that describe the actions and interactions that users will have with the bicycle rental application, we will create user stories to develop from. User stories should be developed collaboratively with stakeholders and end-users, and should focus on delivering value to the customer.

User stories are defined work items that describe features and functionality that power an end user action.

User stories typically have the following characteristics :

  • Have a description that summarizes the use case the user story is solving

  • Have acceptance criteria that defines when a story is considered complete

  • Represent a single functioning piece of code

  • Assigned to a single developer

  • Moved through phases that track the status of the work item

  • Are reviewed in a QA process

  • Often have subtasks that are pieces of work needed to be completed for the user story to be completed

Given our features from the , let's elaborate on those and create some user stories.

User Story 1: User Registration

As a new user, I want to register for an account so that I can start using the bicycle rental application.

Acceptance Criteria:

  • The user should be able to navigate to the registration page from the login page.

  • The registration form should include fields for name, email, phone number, and password.

  • Upon submitting the registration form, the user's information should be stored securely in the database.

  • The user should be redirected to the login page upon successful registration.

  • If there is any error during the registration process, the user should be notified of the error and asked to correct it.

User Story 2: Search Bicycles

As a user, I want to search for available bicycles based on location and date range so that I can find a suitable bicycle for my needs.

Acceptance Criteria

  • The user should be able to access the search feature from the home page.

  • The search feature should include fields for location, start date, and end date.

  • The application should display a list of available bicycles based on the user's search criteria.

  • The list of available bicycles should include details such as location, type, and price.

  • The user should be able to filter and sort the list of available bicycles based on their preferences.

  • If there are no bicycles available for the given search criteria, the user should be notified accordingly.

User Story 3: Rent Bicycle

As a user, I want to rent a bicycle for a specified duration and complete the payment process so that I can start using the rented bicycle.

Acceptance Criteria

  • The user should be able to select a bicycle from the list of available bicycles.

  • The application should display the details of the selected bicycle, including rental rates and terms.

  • The user should be able to specify the rental duration and see the total rental cost.

  • The application should guide the user through the payment process securely and reliably.

  • Upon successful payment, the user should receive a confirmation email with the rental details and instructions.

  • If there is any error during the rental or payment process, the user should be notified of the error and asked to correct it.

User Story 4: Return Bicycle

As a user, I want to return the rented bicycle to the designated location and receive confirmation of the return.

Acceptance Criteria:

  • The user should be able to see the rental details, including the rental duration and the designated return location.

  • The user should receive reminders about the approaching return deadline via email or push notification.

  • The user should be able to navigate to the designated return location using the application's built-in map or directions feature.

  • Upon returning the bicycle, the user should receive a notification confirming the return and the rental charges should be deducted from their account.

  • If there is any dispute or issue related to the rental or return process, the user should be able to contact customer support through the application.

Summary

User stories will form the basis of our prompts and are a key input to the code knowledge.

Plan and Prioritize Features section
generation