Hello to one and all.

I am writing a user story and have stumbled upon this problem of avoiding the implementation detail in it. I already have a UI design created for the project.

Say, for example, I am writing a story for the login functionality. The login has two textboxes and a button. As I cannot use the terms textbox & button, as they are HTML implementation details, then how do I write the story.

I have written the following lines:

The Login module should have the following options:

• The module should have an option (textbox) to enter a username
• The module should have an option (textbox) to enter a password
• The module should have an option (textbox) to submit the login details

Also, I am using the term Login Module instead of Login Page as Page is an HTML term

As I come from a development background I find it difficult to wrap my head around the concept of staying away from the implementation detail.

I am also uncomfortable to use the term "should" in my user story, but I have been asked to use it instead of can, will, shall etc.

This is my first project and I am quite nervous. I have read a lot on requirement gather and am quite overwhelmed.

Can someone please guide me with the requirement process for the following:

• Requirement template
• Mapping and tracing requirement with User stories

I hope I was able to convey my problem. Any form of help will be appreciated. Thank you for reading.

Hi Vijit,

Don't stress too much about using solution in a user story. Your acceptance criteria will be hard to write if you do. Are you concerned because the end solution is not decided? 

If your solution includes other channels for login e.g. fingerprint, iris scan; you'll need separate user stories anyway. If not, then you'll need text boxes and buttons and stuff.

Kimbo