Comments on: Using Wireframes or Prototypes to Elicit, Analyze, and Validate Software Requirements

By: Tools for Prototyping – The Great Facilitator

Tools for Prototyping – The Great Facilitator — Tue, 09 May 2017 17:46:00 +0000

[…] Using wireframes or prototypes to elicit, analyze, and validate software requirements. How the technique can be utilized during the different phases of a business analysis […]

By: Humz

Humz — Fri, 29 Jan 2016 13:32:17 +0000

When we are upgrading a system from A to system b. Because of end of life, the requirement gathering becomes a bit difficult. Can you suggest what questions we should list down to ask HR sme? Basically questions which comes to my mind is how policies will help the it admin later in entering the right data into the system.

By: Using Wireframes or Prototypes to Elicit, Analyze, and Validate Software Requirements |

Mon, 09 Jun 2014 23:48:24 +0000

[…] Within the business analysis community, the debate still reigns about whether how the application will look and how the screens will be laid out is technically part of requirements or design. This debate centers around the wrong question. By Laura Brandenburg at Bridging the Gap. […]

By: A more thorough User eXperience steps breakdown « Code For Thought

A more thorough User eXperience steps breakdown « Code For Thought — Sun, 09 Oct 2011 18:03:29 +0000

[…] Wireframe prototypes 12.3.1 User […]

By: Chelvi

Chelvi — Tue, 20 Sep 2011 20:05:50 +0000

This is a very good article. According to Laura, “wire-framing activities actually come before any sort of user interface specification “. So I am a bit confused regarding this statement. Becasue if the wire-frames are done before the specification/func specs, the what exactly the role of a BA? Because some times the person who does wire-frames will do all the research to what to display on a website. So the BA has to look at the wire-frame and just write a requirement. So how this would be a challenging/interesting job for a BA?