federicozipoli / lab-agile-planning

lab-agile-planning

lab-agile-planning's Issues

Need the ability to update a counter to a new value

As a User
I need the ability to update a counter to a new value
So that I can sync with other services and update accordingly

Details and Assumptions

• User knows what is doing.
• Only Users with appropriate authorization can update the counter.
• The counter is an integer value stored in a database.
• Assuming the cloud deployment is up and running: the value is accessible by all the cloud deployments.
• Verify if notification to all the Users is required.

Acceptance Criteria

Given the user is allowed to access the counter
When the user provides a new value for the counter
Then the counter is updated to the new value

Must allow multiple counters

As a [User]
I need [to have multiple counters]
So that [I can keep track of several counts at once]

Details and Assumptions

• [document what you know]

Acceptance Criteria

Given [some context]
When [certain action is taken]
Then [the outcome of action is observed]

Need a service that has a counter

As a User
I need a service that has a counter
So that I can keep track of how many times something was done

Details and Assumptions

• Need a way to increment a counter
• Need a way to get the current value

Acceptance Criteria

Given I have incremented the counter to 2
When I make a call to get the current value
Then it should return 2 as the counter value

Counters can be reset

As a System Administrator
I need the ability to reset the counter
So that I can redo counting from the start

Details and Assumptions

• The System Administrator will trigger this action
• The counter value needs to be updated and stored

Acceptance Criteria

Given I need to start the counting from scratch
When I reset the counter
Then the counter should return 0

Complete Deploy Service to the Cloud

As a Service Provider
I need the service to be deployed to the cloud
So that I can scale capacity with user demand

Details and Assumptions

• Artifacts for Cloud Foundry app have already been created in branch cf-deploy
• [] Database still needs to be provisioned
• [] App needs to be pushed and connected to the database

Acceptance Criteria

Given I have deployed to the cloud
When a customer comes to our URL
Then our service will be available

Must persist counter across restarts

As a [Service Provider]
I need [the service to persist the last known count]
So that [users don’t lose track of their counts after the service is restarted]

Details and Assumptions

• We will use a Redis database
• Counter will be stored as name value pair

Acceptance Criteria

Given I have incremented the counter to 2
When I restart the service
Then the counter should still return 2

Need the ability to remove a counter

As a [System Administrator]
I need [the ability to remove a counter]
So that [it gets deleted when it is not needed]

Details and Assumptions

• [document what you know]

Acceptance Criteria

Given [some context]
When [certain action is taken]
Then [the outcome of action is observed]

Deploy service to the cloud

As a Service Provider
I need the service to be deployed on the cloud
So that I can scaled it up as needed

Details and Assumptions

• The cloud platform being used for deployment is flexible to allows for easy scaling based on demand
• There is a system that monitors the demand and trigger the scaling up process
• The service uses Docker and Kubernetes

Acceptance Criteria

Given the service has been successfully deployed on a cloud platform
When there is an increase in demand for the service
Then the service should automatically scale up to handle the increased load