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

Fabricio Laguna talks Business Analysis and AI
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...
Business Architecture, Ontology and More with Terry Roach
It's been a privilege meeting Terry Roach, a visionary in the field of enterprise architecture and business architecture. Terry's insights into the evolution of business models, the importance of ontology in architecture, and the potential of AI to shape our future were not only thought-provoking but also a reflection of his extensive exper...
Today I had the pleasure of chatting to Jignesh Jamnadas, Chief Operations Officer at Mosaic, about his Blueprints for Success. As a Senior Finance and Operations Executive, Jigs (as he is known to many) has a holistic understanding of all facets of business and a flair for managing both people and processes. Having worked with Jigs, I was struc...

 



Upcoming Live Webinars




 

Copyright 2006-2024 by Modern Analyst Media LLC