Forums for the Business Analyst

  Modern Analyst Forums  Business and Sy...  Requirements  How to avoid implementation details in a User Story
Previous Previous
Next Next
New Post 4/3/2017 1:20 AM
User is offline Vijit
1 posts
No Ranking

How to avoid implementation details in a User Story 

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.

New Post 4/17/2017 8:05 AM
User is offline Patrick Schmöllerl
3 posts
No Ranking

Re: How to avoid implementation details in a User Story 

Hi Vijit,

I am not a nativ speaker, but the words "textbox" or "Login Module" don't sound like implementation details to me. You obviously don't want to write: "As a user I want to call POST userLogin with the following request-parameters ...". That would be over the top :-)

If you should include details on the implementation in your user-story or strictly avoid it, depends on your project. In my experience it very often depends on the size of the project (how many people are in between your specification and the developer) or your precise role (vgl.

However, there is a a part of a user-story called the"Conversation".This is the best place to add further implementation details (vgl.

New Post 5/10/2017 11:34 PM
User is offline Kimbo
419 posts
5th Level Poster

Re: How to avoid implementation details in a User Story 

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.


Previous Previous
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  How to avoid implementation details in a User Story

Community Blog - Latest Posts

If you are building a reusable Security Product tool to specifically address Security Technical Implementation Guide (STIG)  Findings, should the requirements be considered Non Functional Requirements or Functional Requirements? For example if there are a number of STIGs such as: The minimum password length shall be 15 characters ...
1 Responses
Bert Wagner
Bert Wagner
It’s 4:30 pm on Friday and Mr. Manager comes along to tell you that he needs you to run some important ad-hoc analysis for him. Previously this meant having to stay late at the office, writing cumbersome queries to extract business information from transactional data. Lucky for you, you’ve recently started using Temporal Tables in SQL...
0 Responses
Ronak Sanghavi
Ronak Sanghavi
Current State For many years now, the most commonly used metaphor on Business Analysis has been the “Bridge”. However, in recent past, some in the BA community have started revisiting the metaphor resulting in a debate on how relevant it is. Of course, the value business analysis can provide for an organization does not depend on how i...
2 Responses

Upcoming Live Webinars

Latest Articles

The Goal Is to Solve the Problem
Oct 15, 2017
A requirement is “a condition or capability needed by a user to solve a problem or to achieve an objective” (AKA a goal). Thinking in term...
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC