<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Business Process Modeling</title>
	<link>http://barocks.com/2007/07/26/life-without-use-cases/</link>
	<description>Maria (Murphy) Horrigan talks about Business Analysis, User Centred Design in Requirements Development and Business Process Improvement</description>
	<pubDate>Thu, 28 Aug 2008 08:44:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: Where do we go from here &#8212; making best use of Personas &#171; Matt&#8217;s Musings</title>
		<link>http://barocks.com/2007/07/26/life-without-use-cases/#comment-181</link>
		<author>Where do we go from here &#8212; making best use of Personas &#171; Matt&#8217;s Musings</author>
		<pubDate>Fri, 27 Jun 2008 03:30:04 +0000</pubDate>
		<guid>http://barocks.com/2007/07/26/life-without-use-cases/#comment-181</guid>
		<description>[...] Include these as Actors in use-cases [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Include these as Actors in use-cases [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What&#8217;s my scene &#8212; user roles and needs in social computing &#171; Matt&#8217;s Musings</title>
		<link>http://barocks.com/2007/07/26/life-without-use-cases/#comment-122</link>
		<author>What&#8217;s my scene &#8212; user roles and needs in social computing &#171; Matt&#8217;s Musings</author>
		<pubDate>Thu, 20 Dec 2007 20:22:09 +0000</pubDate>
		<guid>http://barocks.com/2007/07/26/life-without-use-cases/#comment-122</guid>
		<description>[...] sorts of social computing tools you may need to deliver. It will not only help with identifying functional requirements, but also help with creating your marketing strategy for their delivery. For BAs in particular, [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] sorts of social computing tools you may need to deliver. It will not only help with identifying functional requirements, but also help with creating your marketing strategy for their delivery. For BAs in particular, [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Argha</title>
		<link>http://barocks.com/2007/07/26/life-without-use-cases/#comment-33</link>
		<author>Argha</author>
		<pubDate>Thu, 02 Aug 2007 16:57:04 +0000</pubDate>
		<guid>http://barocks.com/2007/07/26/life-without-use-cases/#comment-33</guid>
		<description>Thanks for the post. What kind of techniques and tools did you use for process modeling? (such as Aris, metocube, visio, etc...)</description>
		<content:encoded><![CDATA[<p>Thanks for the post. What kind of techniques and tools did you use for process modeling? (such as Aris, metocube, visio, etc&#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Analysis Manager</title>
		<link>http://barocks.com/2007/07/26/life-without-use-cases/#comment-31</link>
		<author>Analysis Manager</author>
		<pubDate>Thu, 26 Jul 2007 06:31:33 +0000</pubDate>
		<guid>http://barocks.com/2007/07/26/life-without-use-cases/#comment-31</guid>
		<description>This same thing happened to me on a project a couple of years back.  Use cases were banned and process flows were mandated.  However - a use case shows the steps (or process) that an actor employs in order accomplish a goal.

So process vs. use case is just a name.

The reality is that the details of a use case can be documented as a use case document (verbose) or as an activity diagram or process flow.  Many people like process flows because of its visual properties.

The one drawback I found with using activity diagrams or process flows instead of use case specifications is the level of detail.  Most descriptions of activates/steps in a process flows tend to be very brief whereas in a use case more detail is usually added.

Thanks for sharing your experience!

- Adrian</description>
		<content:encoded><![CDATA[<p>This same thing happened to me on a project a couple of years back.  Use cases were banned and process flows were mandated.  However - a use case shows the steps (or process) that an actor employs in order accomplish a goal.</p>
<p>So process vs. use case is just a name.</p>
<p>The reality is that the details of a use case can be documented as a use case document (verbose) or as an activity diagram or process flow.  Many people like process flows because of its visual properties.</p>
<p>The one drawback I found with using activity diagrams or process flows instead of use case specifications is the level of detail.  Most descriptions of activates/steps in a process flows tend to be very brief whereas in a use case more detail is usually added.</p>
<p>Thanks for sharing your experience!</p>
<p>- Adrian</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark A</title>
		<link>http://barocks.com/2007/07/26/life-without-use-cases/#comment-30</link>
		<author>Mark A</author>
		<pubDate>Thu, 26 Jul 2007 05:15:01 +0000</pubDate>
		<guid>http://barocks.com/2007/07/26/life-without-use-cases/#comment-30</guid>
		<description>Hi,
This story points to an oft overlooked element for requirements.  The task is not only about documenting the requirement it is also about communicating it.  And as my wife often reminds me - communication needs 2 people and sometimes we need to be flexible around the vehicles we use to communicate.
I find that too many BA's push the communication vehicle they are comfortable with, rather than ensure that the requirements are accurately communicated.  Sometimes the client have selctive hearing and can only hear the message via the vehicle they are comfortable with.
I applaud your flexibility.</description>
		<content:encoded><![CDATA[<p>Hi,<br />
This story points to an oft overlooked element for requirements.  The task is not only about documenting the requirement it is also about communicating it.  And as my wife often reminds me - communication needs 2 people and sometimes we need to be flexible around the vehicles we use to communicate.<br />
I find that too many BA&#8217;s push the communication vehicle they are comfortable with, rather than ensure that the requirements are accurately communicated.  Sometimes the client have selctive hearing and can only hear the message via the vehicle they are comfortable with.<br />
I applaud your flexibility.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
