Java Reference
In-Depth Information
To start any software development project, you need some documented business
requirements. XP employs user stories for documenting requirements. Each user story
describes how the system is going to solve a business problem. Each is a very short
description of the requirement and is often accompanied by acceptance test cases. Thus,
there is a clear traceability from the requirements to the tests. A user story is written on a
story card .
With agile processes, it is not necessary that you have all the requirements in place
before starting a project. To start the first iteration, you need just a few requirements. The
user stories coming after the start of the first iteration are added to the requirements
backlog. A few of them will be picked from the backlog based on their priority for imple-
mentation in a future iteration until the backlog has been cleared. For the OMS in this
chapter, I have picked up three requirements with the highest priority for the first itera-
tion. The priority is set by the customer, and it is used to determine whether a
requirement will be taken up from the backlog for implementation in the next iteration.
The user stories for these requirements are described in the next sections.
Story Card: Sign In Users
The system allows only registered users to sign in with a username and password. In the
case of a sign-in failure, the user will be notified with a generic error message and
prompted to sign in again. On successful sign-in, the user is taken to the home page
with a link to save the order.
Acceptance test set : AT-01
Priority : 1
Story Card: Look Up Services
The system should provide a facility to look up services available to order for authenti-
cated users only. This opens in a new pop-up window. When the user selects a service,
this pop-up closes, supplying the appropriate values to the parent page.
Acceptance test set : AT-02
Priority : 1
Search WWH ::

Custom Search