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 

Vessela:

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. 

Tony

 

 
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. "...how 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 ?"

and

2. "...how 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.

Cheers,
Agron

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

Community Blog - Latest Posts

Hosted by Deirdre Caren on Agora Insight's Blueprints for Success - The AI Business Analyst I recently had an engaging discussion with Maria Becerra, a passionate advocate for AI and an accomplished business analyst, on the AI Business Analyst. Maria is a respected name in strategy, business analysis and AI. Her path from Colombia to Canada ...
Hosted by Deirdre Caren in Agora Insights' Blueprints for Success I'm thrilled to have Susan Moore join us for episode 9 in our Blueprints for Success. In this session, Susan shares her rich tapestry of experiences that have shaped her career. Her journey into business analysis (ba) is a compelling narrative of exploration and disco...
I recently connected with Fabricio Laguna, aka The Brazilian BA. Fabricio is a passionate and pioneering business analyst from Brazil. During our conversation, we had a thought-provoking discussion on how artificial intelligence stands to shape the field of business analysis in the years ahead. While AI promises to transform many aspects of busines...

 






 

Copyright 2006-2024 by Modern Analyst Media LLC