Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  General   Requirement analysis to design and development using UML approch.
Previous Previous
 
Next Next
New Post 2/28/2008 10:11 PM
User is offline Craig Brown
560 posts
www.betterprojects.net
4th Level Poster




Re: Requirement analysis to design and development using UML approch. 

 adrian wrote

The title may be a bit misleading as it also includes how to solution.  The book advocates using use case models and use case specifications (detailed use case descriptions) do model requirements.

Does the book target develoeprs or analysts or both, or neither specifically?  It (and these agile v BA discussions) made me go back and think about why we work so hard to separate requirements from the solution.

The high level reasons is that we are supposed to define the prpoblem properly before we start wrking on the solution.  This stops us going off half cocked on what can be very expensive solution options that may not be the best fit.  Additionally, requirements elicitaion and analysis are specialist skills, same as coding and designing.  But where the develoepr is doing the analysis, or the analyst is doing the development (eg in a rules engine or in a simple web build) why break them apart?

 
New Post 2/28/2008 10:26 PM
User is offline Adrian M.
765 posts
3rd Level Poster




Re: Requirement analysis to design and development using UML approch. 

 craigwbrown wrote

 adrian wrote

 

The title may be a bit misleading as it also includes how to solution.  The book advocates using use case models and use case specifications (detailed use case descriptions) do model requirements.

 

Does the book target develoeprs or analysts or both, or neither specifically?  It (and these agile v BA discussions) made me go back and think about why we work so hard to separate requirements from the solution.

The high level reasons is that we are supposed to define the prpoblem properly before we start wrking on the solution.  This stops us going off half cocked on what can be very expensive solution options that may not be the best fit.  Additionally, requirements elicitaion and analysis are specialist skills, same as coding and designing.  But where the develoepr is doing the analysis, or the analyst is doing the development (eg in a rules engine or in a simple web build) why break them apart?

The books, in it's own words, targets "IT Business Analysts".  From reading the book, it looks like it's geared more towards "Business Systems Analysts" and "Systems Analysts" and not as much to business case and vision development.

- Adrian


Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
 
New Post 2/29/2008 7:36 AM
User is offline David Wright
141 posts
www.iag.biz
7th Level Poster




Re: Requirement analysis to design and development using UML approch. 

Yes, Use Cases are good for Requirements. My understanding is that Use Cases are not UML artifacts, that they pre-date UML by some time. Its just that they both got popular about the same time and they were used together. My earlier comment about developers saying I should not use UML, I should clarify that they did not include Use Cases in their 'ban', so Use Cases and Data/Concept Models is what I used for Requirements and provided those to the developers for design and build activities.

A parallel issue to this is the position that some people hold that Class Diagrams and ER Data Models are equivalent; you can probably guess that I don't agree, anyone want to know why?

 

Dave W


David Wright
 
New Post 3/1/2008 2:40 PM
User is offline Chris Adams
323 posts
5th Level Poster






Re: Requirement analysis to design and development using UML approch. 
Modified By Chris Adams  on 3/3/2008 5:54:09 PM)

 dwwright99 wrote

Yes, Use Cases are good for Requirements. My understanding is that Use Cases are not UML artifacts, that they pre-date UML by some time. Its just that they both got popular about the same time and they were used together. My earlier comment about developers saying I should not use UML, I should clarify that they did not include Use Cases in their 'ban', so Use Cases and Data/Concept Models is what I used for Requirements and provided those to the developers for design and build activities.

A parallel issue to this is the position that some people hold that Class Diagrams and ER Data Models are equivalent; you can probably guess that I don't agree, anyone want to know why?

 

Dave W

I have my thoughts on this, but yes, please share with us.


Chris Adams
Core Member – ModernAnalyst.com
LinkedIn Profile
 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  General   Requirement analysis to design and development using UML approch.

Community Blog - Latest Posts

Business Impact Analysis(BIA): Assessing the Potential Impact of a Cybersecurity Incident on Business Operations
In today’s highly interconnected society, businesses depend on technology even more than before. While offering opportunities for innovation and creativity, businesses are exposed to various cybersecurity threats that can disrupt operations, damage reputation, and result in substantial financial losses. It is crucial to carry out a comprehens...
In today's ever-evolving market, businesses must adapt swiftly to remain competitive and meet the needs of a fast-paced digital economy. Among the various business strategies available, digital transformation, customer-centricity, and sustainability have emerged as top priorities. Let’s explore why these strategies are critical for busine...
The Cisco Certified Network Associate (CCNA) certification is a pivotal credential for networking professionals, validating your skills in networking fundamentals, security, automation, and programmability. Preparing for the CCNA exam can be challenging, but with the right strategy, resources, and mindset, you can successfully achieve this certific...

 



Upcoming Live Webinars




 

Copyright 2006-2024 by Modern Analyst Media LLC