View User Story

User Story: As a user I should be able to delete a project. The system shall ask me if I am sure and tell me how many items within this project will also be deleted.

Acceptance Criteria

Criteria	Actions
No acceptance criteria found.

Add Acceptance Criteria

Add Relationship

Select Related Requirement: The system shall use a mySQL databaseAs an administrator, I need the database to make sense and be relational so that it is easier to manageAs a BA, I need to enter my requirements into the database with an easy to use form so that I can use the system easily and be productive.As a BA, I need to link my requirements to each other, so that I can see how they work togetherAs a BA, I need to link Acceptance Criteria to user storiesSystem should allow for a sort order for modulesSystem should allow for a sort order for requirementsSystem should allow for a sort order for user storiesModule and requirements table need a sort orderNeed to change the enum values for parent/child to be 'parent of' and maybe 'child of:The system shall show all requirements within the project when linking two requirements together As a BA, I need to enter user stories into the system to record how and why users need to use the system.The system shall allow Sebastian to learn the Great lakes using mnemonic devices.As a user, I should be able to add a new projectAs a user, I should be able to sort my projects on the project index screenAs a user I shall be able to rename a projectThe project shall be the highest level artifact in the project hierarchy. When a project is deleted, all of the modules, requirements, user stories, and their relationships shall be deletedAs a user, I want to use my finger or thumb to push an arrow to move an item higher or lower in the listAs a user I want to use my finger to push an arrow to move an item left or right in the list to indent it, thus indicating a parent/child relationship between the two.The system will indent a child requirement underneath its parent requirement. Similar to an ordered list.The system shall maintain a numbered list of requirements and user stories. If a requirement number is 3, then its children will start with 3.1,3.2 etcThe numbered list shall be for each section, one for requirements within a module and one for user stories within a module.as a user, I shall be able to add a new moduleAs a user, I shall be able to delete a module. The system shall ask me if I am sure and tell me how many items within this module will also be deleted.As a user, I shall be able to rename a moduleAs a user, I shall be able to reorder the modules as they appear on the index screenThe system shall display requirement/user story details in a pop up window with an 'X' to close in the upper rightThe system will use buttons for options that take an action (add, update, delete)When viewing the requirement/user story details window, there should be an 'update' button that will take you to a screen to perform the update Relationship Type: Parent/Child Satisfies Contains Relates

Back to Module Details