Forums for the Business Analyst

  Modern Analyst Forums  Business and Sy...  Usability and U...  Requirements elicitation for user interface vs application
Previous Previous
Next Next
New Post 4/10/2010 7:56 AM
User is offline Tony Markos
493 posts
5th Level Poster

Re: Requirements elicitation for user interface vs application 


The BABOK is based on what is popular - not upon what makes sense.   Take Business Requirements vs Functional Requirements.   What the BABOK says is that if a requirement is high level and non-implementation specific, it is essentially different than a requirement that is not as high level and is implementation specific (i.e,  implemented within a specific system).  (Do not be confused by goals, objectives, and needs vs functions and processes;   a high level goal, need, or objective can easily be restated to be a high level essential function/process.  It is just a small matter of changing some wording around.)

Such thinking, especially for larger scale efforts, is very problematic as it retards the analysts ability to integrate all essential functional requirements into a comprehensive, integrated whole.   Data flow diagrams are proof that all essential goals, objectives, needs, functions, and process - high level, detail level, non-implementation specific and implementation specific - can all be tied together into a single comprehensive, integrated whole. 



New Post 4/27/2010 8:02 AM
User is offline Agron
1 posts
No Ranking

Re: Requirements elicitation for user interface vs application 

Hi Priyanka,

My understanding is that you are asking two questions here:

1. " are the requirements for the user interface different from the requirements for the whole application. User interface is a part of the application design, right ?"


2. " the use case design different for User interface than the one designed for a partular functionality?"

My answers to above:

1. I presume by "requirements" you mean "Functional Requirements". Yes, UI FR are part of the application design.

2. Yes, Use Case can not be different for UI and for the Application, the use case represents a particular function (or part of it) that the application must provide in order to meet the particular Business Requirement(s).

Hope this helps.


Previous Previous
Next Next
  Modern Analyst Forums  Business and Sy...  Usability and U...  Requirements elicitation for user interface vs application

Community Blog - Latest Posts

My Certification Journey – Avoiding a CBAPtism by Fire. Industry Certification has always been one of my career goals. Ever since being first introduced to Business Analysis, the discussion of being certified by the most recognized industry body in this field, the IIBA, has been a consistent topic. This was only reinforced when I was first in...
BPMN 2.0 is a modelling standard that has been around for 10 years now and although it has its foibles it has been recognised as the best for capturing the business logic behind real-life scenarios.  What most people don’t realise is that the standard itself is supported by an XML definition of its objects. What does this mean? Essent...
Different procedures are utilized for legitimate administration of IT administrations, yet ITIL is viewed as the best arrangement of practices for even administration of IT administrations. ITIL is the contraction for Information Technology Infrastructure Library.  In easier words, ITIL is many rules and arrangements for the effective admin...

Upcoming Live Webinars


Copyright 2006-2021 by Modern Analyst Media LLC