<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>http://groups.google.co.uk/group/volere</id>
  <title type="text">Volere Requirements Google Group</title>
  <subtitle type="text">
  Forum for Requirements Practitioners to discuss, issues, ideas, experiences and questions about Volere requirements techniques. Used world wide from large projects to small enhancements. Volere summary articles at http://www.volere.co.uk Any advertising posted will be deleted
  </subtitle>
  <link href="/group/volere/feed/atom_v1_0_msgs.xml" rel="self" title="Volere Requirements feed"/>
  <updated>2009-11-18T03:23:43Z</updated>
  <generator uri="http://groups.google.co.uk" version="1.99">Google Groups</generator>
  <entry>
  <author>
  <name>Suzanne Robertson</name>
  <email>suza...@systemsguild.net</email>
  </author>
  <updated>2009-11-18T03:23:43Z</updated>
  <id>http://groups.google.co.uk/group/volere/browse_frm/thread/897464b037da1f62/67dc2df49077277e?show_docid=67dc2df49077277e</id>
  <link href="http://groups.google.co.uk/group/volere/browse_frm/thread/897464b037da1f62/67dc2df49077277e?show_docid=67dc2df49077277e"/>
  <title type="text">New Group</title>
  <summary type="html" xml:space="preserve">
  Dear Group Members, &lt;br&gt; &lt;p&gt;This is to let you know that we have started a new Volere Requirements &lt;br&gt; group on LinkedIn. The reason for this is that the medium is more &lt;br&gt; interactive and you will find it easier to have conversations about &lt;br&gt; your use of the Volere techniques. If you would like to join the group
  </summary>
  </entry>
  <entry>
  <author>
  <name>James Robertson</name>
  <email>ja...@systemsguild.net</email>
  </author>
  <updated>2009-09-25T14:52:07Z</updated>
  <id>http://groups.google.co.uk/group/volere/browse_frm/thread/321412c90af7bbce/9bdc3d3afa9831ec?show_docid=9bdc3d3afa9831ec</id>
  <link href="http://groups.google.co.uk/group/volere/browse_frm/thread/321412c90af7bbce/9bdc3d3afa9831ec?show_docid=9bdc3d3afa9831ec"/>
  <title type="text">Re: Business events/BUC/PUC</title>
  <summary type="html" xml:space="preserve">
  Jack, &lt;br&gt; &lt;p&gt;I mean that you consider all of your organisation to be inside the &lt;br&gt; context bubble. Your customer is outside, and any department that is &lt;br&gt; definitely off limits is outside (that is, an adjacent system). &lt;br&gt; Otherwise, the wider the scope of your context the better the business &lt;br&gt; result you get.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Jack</name>
  <email>jack...@yahoo.com</email>
  </author>
  <updated>2009-09-25T02:34:56Z</updated>
  <id>http://groups.google.co.uk/group/volere/browse_frm/thread/321412c90af7bbce/43f3f59e69c5ccb6?show_docid=43f3f59e69c5ccb6</id>
  <link href="http://groups.google.co.uk/group/volere/browse_frm/thread/321412c90af7bbce/43f3f59e69c5ccb6?show_docid=43f3f59e69c5ccb6"/>
  <title type="text">Re: Business events/BUC/PUC</title>
  <summary type="html" xml:space="preserve">
  Thank you so much again. This is giving us far better clarity. &lt;br&gt; &lt;p&gt;I think part of the issue is that we are thinking in terms of process &lt;br&gt; and are breaking down the adjacent systems to much. &lt;br&gt; &lt;p&gt;Regarding the work discussed (applying for an application online) we &lt;br&gt; have several departments (each for processing a part of the
  </summary>
  </entry>
  <entry>
  <author>
  <name>James Robertson</name>
  <email>ja...@systemsguild.net</email>
  </author>
  <updated>2009-09-24T17:48:34Z</updated>
  <id>http://groups.google.co.uk/group/volere/browse_frm/thread/321412c90af7bbce/22ed0ba3dfd76945?show_docid=22ed0ba3dfd76945</id>
  <link href="http://groups.google.co.uk/group/volere/browse_frm/thread/321412c90af7bbce/22ed0ba3dfd76945?show_docid=22ed0ba3dfd76945"/>
  <title type="text">Re: Business events/BUC/PUC</title>
  <summary type="html" xml:space="preserve">
  Jack, &lt;br&gt; &lt;p&gt;the point of the BUC is that it shows *all* that the *business* does &lt;br&gt; in response to a business event. I suggest that you think of the BUC &lt;br&gt; as the combination of what departments A, B and C do whenever the &lt;br&gt; application is submitted from outside the organisation. &lt;br&gt; &lt;p&gt;The reason for this is in your answer -- there is almost always some
  </summary>
  </entry>
  <entry>
  <author>
  <name>Suzanne Robertson</name>
  <email>suza...@systemsguild.net</email>
  </author>
  <updated>2009-09-24T17:53:37Z</updated>
  <id>http://groups.google.co.uk/group/volere/browse_frm/thread/321412c90af7bbce/963fda026d21ad0e?show_docid=963fda026d21ad0e</id>
  <link href="http://groups.google.co.uk/group/volere/browse_frm/thread/321412c90af7bbce/963fda026d21ad0e?show_docid=963fda026d21ad0e"/>
  <title type="text">Re: Business events/BUC/PUC</title>
  <summary type="html" xml:space="preserve">
  Dear Jack, &lt;br&gt; &lt;p&gt;The start of a business event is governed by the work scope that you have &lt;br&gt; declared for your project. A business event takes place in an adjacent &lt;br&gt; system. The response to the business event (the BUC) is everything that &lt;br&gt; happens within the work scope - usually defined using a work context
  </summary>
  </entry>
  <entry>
  <author>
  <name>Jack</name>
  <email>jack...@yahoo.com</email>
  </author>
  <updated>2009-09-23T05:06:05Z</updated>
  <id>http://groups.google.co.uk/group/volere/browse_frm/thread/321412c90af7bbce/a21ef9434b3604b0?show_docid=a21ef9434b3604b0</id>
  <link href="http://groups.google.co.uk/group/volere/browse_frm/thread/321412c90af7bbce/a21ef9434b3604b0?show_docid=a21ef9434b3604b0"/>
  <title type="text">Re: Business events/BUC/PUC</title>
  <summary type="html" xml:space="preserve">
  Firstly, thank you very much for your help. You have confirmed that we &lt;br&gt; are doing things mostly right. &lt;br&gt; &lt;p&gt;I would just like to discuss a couple more points. &lt;br&gt; Continuing with the work in question which is Processing Applications &lt;br&gt; on line. &lt;br&gt; I think what you are saying is that each time an application form gets
  </summary>
  </entry>
  <entry>
  <author>
  <name>George Brooke</name>
  <email>geo...@oaklodgeconsulting.co.uk</email>
  </author>
  <updated>2009-09-17T08:47:03Z</updated>
  <id>http://groups.google.co.uk/group/volere/browse_frm/thread/321412c90af7bbce/ec9619f3cfb728c9?show_docid=ec9619f3cfb728c9</id>
  <link href="http://groups.google.co.uk/group/volere/browse_frm/thread/321412c90af7bbce/ec9619f3cfb728c9?show_docid=ec9619f3cfb728c9"/>
  <title type="text">RE: Business events/BUC/PUC</title>
  <summary type="html" xml:space="preserve">
  Hi Jack, &lt;br&gt; &lt;p&gt;I hope you don&#39;t mind if I give you my take on this. I have copied your &lt;br&gt; questions into my email and attached answers. &lt;br&gt; &lt;p&gt;1. Is there generally only one BUC per Business event? &lt;br&gt; &lt;p&gt;* Generally true, but not necessarily. I could imagine a BUC being &lt;br&gt; joined midway for example, by a higher-level Business Event occurring, so a
  </summary>
  </entry>
  <entry>
  <author>
  <name>Robrecht David</name>
  <email>robrecht.da...@ae.be</email>
  </author>
  <updated>2009-09-17T08:58:50Z</updated>
  <id>http://groups.google.co.uk/group/volere/browse_frm/thread/321412c90af7bbce/a239cc3c6db8e356?show_docid=a239cc3c6db8e356</id>
  <link href="http://groups.google.co.uk/group/volere/browse_frm/thread/321412c90af7bbce/a239cc3c6db8e356?show_docid=a239cc3c6db8e356"/>
  <title type="text">RE: Business events/BUC/PUC</title>
  <summary type="html" xml:space="preserve">
  Jack &lt;br&gt; &lt;p&gt;I think it might be beneficial to make the event a bit more abstract. &lt;br&gt; &amp;quot;person applies for membership&amp;quot; as a first cut scope. Depending on the project goal this can then be refined as &amp;quot;Person applies for membership online&amp;quot;. &lt;br&gt; The first description has the advantage that you can then define the output(s) of the process that has been triggered by this event independent from the way the application was done: at a branch, online, through a call centre,....
  </summary>
  </entry>
  <entry>
  <author>
  <name>Jack</name>
  <email>jack...@yahoo.com</email>
  </author>
  <updated>2009-09-15T23:20:47Z</updated>
  <id>http://groups.google.co.uk/group/volere/browse_frm/thread/321412c90af7bbce/56efee8deb128cee?show_docid=56efee8deb128cee</id>
  <link href="http://groups.google.co.uk/group/volere/browse_frm/thread/321412c90af7bbce/56efee8deb128cee?show_docid=56efee8deb128cee"/>
  <title type="text">Business events/BUC/PUC</title>
  <summary type="html" xml:space="preserve">
  Hi, &lt;br&gt; &lt;p&gt;I was just wondering if we could get some clarity or advice on the &lt;br&gt; relationship between Business Events/Business Use Cases (BUC) and &lt;br&gt; Product Use Cases (PUC). &lt;br&gt; &lt;p&gt;I believe we have a very good understanding here of what each of these &lt;br&gt; is. We are just trying to get a better idea of how many BUCs and PUC&#39;s
  </summary>
  </entry>
  <entry>
  <author>
  <name>Nathan</name>
  <email>n.mor...@xtra.co.nz</email>
  </author>
  <updated>2009-09-10T21:44:44Z</updated>
  <id>http://groups.google.co.uk/group/volere/browse_frm/thread/47deaad41bfb0abb/55c6158ca2fd3e83?show_docid=55c6158ca2fd3e83</id>
  <link href="http://groups.google.co.uk/group/volere/browse_frm/thread/47deaad41bfb0abb/55c6158ca2fd3e83?show_docid=55c6158ca2fd3e83"/>
  <title type="text">Re: Context Diagrams for extremely large projects</title>
  <summary type="html" xml:space="preserve">
  Hello everyone, and Megan in particular. &lt;br&gt; &lt;p&gt;I posted a similar topic a while back and received some useful &lt;br&gt; guidance from both of the Robertsons about discovering the processes. &lt;br&gt; A couple of observations / considerations: &lt;br&gt; &lt;p&gt;1. You or your team will have to know the specific business processes &lt;br&gt; in place at the moment, to be supported by the future product.
  </summary>
  </entry>
  <entry>
  <author>
  <name>kerryP</name>
  <email>ke...@paym8.co.za</email>
  </author>
  <updated>2009-09-09T09:40:29Z</updated>
  <id>http://groups.google.co.uk/group/volere/browse_frm/thread/95bd7983dd407e3a/8a0045011eb17361?show_docid=8a0045011eb17361</id>
  <link href="http://groups.google.co.uk/group/volere/browse_frm/thread/95bd7983dd407e3a/8a0045011eb17361?show_docid=8a0045011eb17361"/>
  <title type="text">Volere &amp; Personify Teamspec</title>
  <summary type="html" xml:space="preserve">
  Teamspec (aka Personify) provides for Requirements described in a Word &lt;br&gt; document to be taken into Microsoft Visual Studio as Work Items. &lt;br&gt; Does anybody have experience of producing Visual Studio Work Items &lt;br&gt; from a Volere Word document?
  </summary>
  </entry>
  <entry>
  <author>
  <name>Rob</name>
  <email>roberts...@gmail.com</email>
  </author>
  <updated>2009-09-03T11:51:09Z</updated>
  <id>http://groups.google.co.uk/group/volere/browse_frm/thread/47deaad41bfb0abb/f26c705de8379b9b?show_docid=f26c705de8379b9b</id>
  <link href="http://groups.google.co.uk/group/volere/browse_frm/thread/47deaad41bfb0abb/f26c705de8379b9b?show_docid=f26c705de8379b9b"/>
  <title type="text">Re: Context Diagrams for extremely large projects</title>
  <summary type="html" xml:space="preserve">
  Megan: &lt;br&gt; &lt;p&gt;A couple of comments on you overall project. &lt;br&gt; &lt;p&gt;It is very hard to &amp;quot;replicate&amp;quot; a &amp;quot;very large&amp;quot; system. You may &lt;br&gt; understand the features (use cases), but it is likely you don&#39;t &lt;br&gt; understand how those features are used (scenarios). Users are often &lt;br&gt; very innovative about using features for &amp;quot;non-intended&amp;quot; purposes. If
  </summary>
  </entry>
  <entry>
  <author>
  <name>Mark Wallace (Los Angeles)</name>
  <email>m...@cox.net</email>
  </author>
  <updated>2009-08-30T20:10:05Z</updated>
  <id>http://groups.google.co.uk/group/volere/browse_frm/thread/47deaad41bfb0abb/e805d2356c9a9254?show_docid=e805d2356c9a9254</id>
  <link href="http://groups.google.co.uk/group/volere/browse_frm/thread/47deaad41bfb0abb/e805d2356c9a9254?show_docid=e805d2356c9a9254"/>
  <title type="text">Re: Context Diagrams for extremely large projects</title>
  <summary type="html" xml:space="preserve">
  The two biggest risks that I can see are: &lt;br&gt; &lt;p&gt;1. A hint of contradiction in the orders coming down from OrgB &lt;br&gt; management. On the one hand, the &amp;quot;mandate is to replicate the system &lt;br&gt; exactly&amp;quot; from OrgA into OrgB. On the other hand, &amp;quot;once OrgA has &lt;br&gt; documented what is required, OrgB may then decide to not do some bits
  </summary>
  </entry>
  <entry>
  <author>
  <name>Rob</name>
  <email>roberts...@gmail.com</email>
  </author>
  <updated>2009-08-29T13:00:52Z</updated>
  <id>http://groups.google.co.uk/group/volere/browse_frm/thread/fb4593e9c134b595/e10213b65fff6eb3?show_docid=e10213b65fff6eb3</id>
  <link href="http://groups.google.co.uk/group/volere/browse_frm/thread/fb4593e9c134b595/e10213b65fff6eb3?show_docid=e10213b65fff6eb3"/>
  <title type="text">Volere for an Undergraduate Class</title>
  <summary type="html" xml:space="preserve">
  I’ve just been assigned to teach a sophomore-level Software &lt;br&gt; Engineering class on Requirements. Our text is Robertson and &lt;br&gt; Roberson, “Mastering the Requirements Process” with Volere. The first &lt;br&gt; class is a week away. &lt;br&gt; Does anyone have resources they would share with me? Examples would &lt;br&gt; be: &lt;br&gt; -Small homework assignments to reinforce lessons from a chapter
  </summary>
  </entry>
  <entry>
  <author>
  <name>Gb2009</name>
  <email>gbridge...@gmail.com</email>
  </author>
  <updated>2009-08-28T14:49:01Z</updated>
  <id>http://groups.google.co.uk/group/volere/browse_frm/thread/47deaad41bfb0abb/989e405d66988054?show_docid=989e405d66988054</id>
  <link href="http://groups.google.co.uk/group/volere/browse_frm/thread/47deaad41bfb0abb/989e405d66988054?show_docid=989e405d66988054"/>
  <title type="text">Re: Context Diagrams for extremely large projects</title>
  <summary type="html" xml:space="preserve">
  Hi Megan, &lt;br&gt; &lt;p&gt;I agree with George Brooke. The context diagram is a good &lt;br&gt; communication tool to help you and the stakeholder understand the &lt;br&gt; system/work boundaries.(scope) &lt;br&gt; &lt;p&gt;George
  </summary>
  </entry>
</feed>
