Re: [soa-rm] Use Case 2.0 article

[Ken Laskey <klaskey@mitre.org>]

Luckily, MITRE has a CACM subscription.  

I found the Principles for Use-Case Adoption to be to the point:

1. Keep it simple by telling stories

2. Understand the big picture

3. Focus on value

4. Build the system in slices

5. Deliver the system in increments

6. Adapt to meet the team’s needs.

The titles are good enough even without the associated text.

To the point of user stories vs. use cases, I don’t see how one get a quality use case without the SME or why the SME is more critical the the user story.  I think we’ve all seen the situation where the requirements, in whatever form captured, is a contract deliverable and the staff compiling the requirements has to generate paper from whatever knowledge base they can bring to bear.  If anything, the goal should be to keep the error consequences low so we can remediate when we find the requirements — user stories or use cases/slices — are lacking.

Ken

------------------------------------------------------------------------------
Dr. Kenneth Laskey
MITRE Corporation, M/S F510          phone: 703-983-7934
7515 Colshire Drive                           fax: 703-983-1379
McLean VA 22102-7508

On Mar 3, 2017, at 12:44 AM, Martin Smith <bfc.mclean@gmail.com> wrote:

At this week's TC meeting I mention this article from the May 2016 issue of the Communicatons of the ACM. 

The particular point I mentioned was a conclusion about when to use light-weight (agile) requirements methodologies (using "stories" as the _expression_ of requirements) vs more formal requirements approaches (using "use-cases" to express requirements.) I thought the same consideration might apply to the whole devops/MSA approach vs. more traditional SDLC approaches. Here's what the article said: 

" The question remains: Which technique should you use that is very context dependent, once you go beyond personal preferences? Consider the following factors: how much access is there to the SMEs (subject matter experts); and how severe will requirements errors be if they escape to a live environment.

The sweet spot for user stories is achieved when there is easy access to a SME and the severity of errors is low. Use cases and use-case slices are more suitable when there is no easy access to a SME or when error consequences are high.  "

The full article is pretting interesting, too, but access to it requires an ACM membership or subscription to CACM. Here's the link to the abstract and to the full article  in case you are an ACM member or wish to be one!

http://cacm.acm.org/magazines/2016/5/201604-use-case-2-0/abstract

Regards,

Martin

--

Martin F Smith, Principal

BFC Consulting, LLC

McLean, Va 22102

703 506-0159

703 389-3224 mobile