Requirements Gathering with UeXceler
Identify users' needs with use case and user story.
Detail user requirements with user story scenario.
-
Write user stories
In modern software development, requirements capturing is not something you can start and finish at the outset of a project. Instead, new requirements can emerge and previously suggested requirements can change throughout the project. User stories is one of the approach widely adopted by many agile projects to support the continuous capturing and management of ever changing user requirements.
Written by user (or customer team), user stories describe functionality that are needed by and valuable to the users. As an integral part of many agile development processes, user stories offer a quick and handy way in recording user requirements, without having to write any detailed requirement documents, or have any prior consideration of system behaviors.
-
Card layout
View user stories as story cards, which facilitates the arrangement and comparison of stories.
-
Document the conversation
Record in conversation the issues to be resolved, or any details about the user story.
-
Confirmation items that facilitate acceptance test
Record the items to be aware of when working on and when running acceptance tests.
-
Set user story status
Status like pending, working, completed and confirmed can be set to a user story for indicating the progress of development.
-
Prioritizing user stories
Prioritize stories based on their costs and business values, with simple drag and drop.
-
Adding sub-diagrams and references to user story
Visualize behaviors with supplementary sub-diagrams or include related artifacts with references.
-
Linking user story from use case statement
Write use case statements, and then generate user stories from them. Linkage between statements and user stories are preserved.
-
Logged user story changes
Automatically keep history for all the changes made to user stories.
-
Categorize user stories with tag
Group and categorize user stories by adding tags.
-
Manage user stories in use case basis
Get a big picture of system by organizing user goals with use cases. Organizing user stories within use case ensures that the stories are goal-driven and within the system scope. You can also track the progress of supporting a use case by reviewing the status of containing user stories.
-
User story scenario editor
While user story represents user requirements rather than to document any details, a user story scenario provides for customer team to document the preferred way of supporting a requirement, by outlining the interaction between user and system. By reading the steps in a scenario, user can immediately tell whether the function can meet his/her need. Wrong assumption can be corrected without having to wait until any prototype or executables. With risk tackled in early stage of development, a more accurate project planning can be performed.
-
Describe exception with extension
In addition to the main flow, describe the steps that run in exceptional cases.
-
Adding sub-steps
Break-down a step into sub-steps for more detailed description.
-
Collapse and expand sub-steps
Know the high level system flow by hiding the sub-steps.
-
Multiple scenarios per story
Describe the different possible flows of a use case.
-
Reference to model element in step
Reference to related actors, use cases and requirements in steps.
-
Logical operations
Apply if-then-else or looping in describing the steps.
-
Sequence diagram generation
Visualize the flow of events with a UML sequence diagram.
-
Activity diagram generation
Visualize the flow of events with a UML activity diagram.
-
Link scenario to wireframe
If user can see the software before you start the development, you will probably receive a lot of valuable feedback that prevents you from doing something wrong. While is impossible and sounds a bit ridiculously, you can still do as much as you can to simulate user experience and perception. The Flow of Events Editor lists out the steps user will take to achieve a use case and for each step, a wireframe can be associated to show what the screen will look like at that step. These allows users to preview what will the final product look like and how will it behave. They can give suggestions and share their concerns, which help to ensure that the final product will meet with their expectation perfectly.
-
Storyboard in user story
Use storyboards to show what the end user will see and interact with. With the help of storyboards, stakeholders can preview the end product, and to confirm that what you are going to develop actually meets their needs.
-
Playback wireframe to consent to requirements
Let users know how the system will work and how it will benefit them and their organization by presenting to them the system screen flow. You will become a story teller, playing the screens one by one, describing the usage of system, clearly and effectively.
-
Sprint management
Discuss user stories with customer team, and then plan out the next sprint(s). Customer team and development team work collaboratively to select the user stories to be included in the sprint, with a reasonable sprint duration. You can also assign team member responsible for designing, implementing and testing around a user story.
-
Web based requirements management
The web version of UeXceler lets you manage and browse requirements directly on the web (nothing to download or install). Providing you with a more convenient way to record and clarify requirements when meeting remotely with stakeholders. It also ensures the project team will stay up to date with any requirement changes. Stakeholders and project team have access to same and latest set of use cases, user stories and sprints.
-
Identify use cases with Use Case Statements
Use case statements is a technique that helps identify actors and use cases. The user voice form of use case expression begins with <role>, which provides a user-oriented approach to identifying the business objective (i.e. use case) and business value.
|
