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 6: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 7: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

I have always loved cooking. I learned from my Grandma June and her kitchen was her sanctuary, a small, warm sunlit space filled with jars of spices, stacks of cookbooks, and the comforting smell of something always on the stove or baking in the oven. Grandma June was as great a cook as she was a teacher to me. She never followed a recipe “to...
Now, I know, I don’t know what kind of new intro BPO may require, but at least I can promise you upfront that I have something different to say about Business Process Outsourcing or simply BPO. What is it? This hasn't been a call center job or a sales job as we all think. It is a mammoth profile, and firms are grappling to ge...
Leveraging Blockchain Technology for Enhanced Data Security in Business Operations
In an age where data breaches and cyberattacks are becoming more frequent and sophisticated, businesses are searching for robust solutions to safeguard their data. Blockchain technology has emerged as a promising tool in this quest, offering a way to secure data with unparalleled reliability. Although initially known for powering cryptocurrencies l...

 






 

Copyright 2006-2025 by Modern Analyst Media LLC