Home » Archived » ORMF » Background on Approach to Use Cases
| Background on Approach to Use Cases [message #12072] |
Wed, 06 August 2008 17:01  |
Eclipse User |
|
|
|
In the demos that I was able to access, I saw a different and very
structured approach to Use Cases that I have not previously seen. I was
hoping that there might be some books or articles available that give more
details on your approach to use cases,
I would be most grateful for references - I'd like to work through the
approach in some detail.
|
|
|
| Re: Background on Approach to Use Cases [message #12100 is a reply to message #12072] |
Thu, 07 August 2008 09:35  |
| Eclipse User |
|
|
|
On 2008-08-06 22:01:59 +0100, fballem@ballemco.com (Flavelle Ballem) said:
> In the demos that I was able to access, I saw a different and very
> structured approach to Use Cases that I have not previously seen. I was
> hoping that there might be some books or articles available that give
> more details on your approach to use cases,
>
> I would be most grateful for references - I'd like to work through the
> approach in some detail.
Flavelle, hi.
Thanks for your interest in our use case approach. There are two books
that really inspired us and motivated us to create an automated tool in
the first place:
1) Advanced use case modelling, by Frank Armour and Granville Miller,
Addison Wesley (2001), ISBN:0-201-61592-4
This had a profound impact on the way we perceive use cases and on the
need for deep customisation of the use case approach to suit a
project's specific needs. We also had great conversations with Frank,
one of the two authors, which obviously further enriched the overall
experience.
2) Managing software requirements, by Dean Leffingwell and Don Widrig,
Addison Wesley (2000), ISBN: 0-201-61593-2
This is one of the classics of the science of software requirements. We
really enjoyed it not so much for the specific of use cases, but for
its emphasis on the importance of industrial strenght requirements,
which are captured to be sturdy, traceable and verifiable, but which
are at the same time resilient to change.
Ultimately, the structure we came up for use cases is a distillation of
the knowledge garnered both from books and from real life experience at
formalising requirements as use cases for various organisations, with
varying cultures, sizes and project scopes.
HTH,
B.
--
Barbara Rosi-Schwartz
Etish Limited [http://www.etish.org]
Blog: http://www.brs4etish.blogspot.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
| | |
| Re: Background on Approach to Use Cases [message #564118 is a reply to message #12072] |
Thu, 07 August 2008 09:35 |
| Eclipse User |
|
|
|
On 2008-08-06 22:01:59 +0100, fballem@ballemco.com (Flavelle Ballem) said:
> In the demos that I was able to access, I saw a different and very
> structured approach to Use Cases that I have not previously seen. I was
> hoping that there might be some books or articles available that give
> more details on your approach to use cases,
>
> I would be most grateful for references - I'd like to work through the
> approach in some detail.
Flavelle, hi.
Thanks for your interest in our use case approach. There are two books
that really inspired us and motivated us to create an automated tool in
the first place:
1) Advanced use case modelling, by Frank Armour and Granville Miller,
Addison Wesley (2001), ISBN:0-201-61592-4
This had a profound impact on the way we perceive use cases and on the
need for deep customisation of the use case approach to suit a
project's specific needs. We also had great conversations with Frank,
one of the two authors, which obviously further enriched the overall
experience.
2) Managing software requirements, by Dean Leffingwell and Don Widrig,
Addison Wesley (2000), ISBN: 0-201-61593-2
This is one of the classics of the science of software requirements. We
really enjoyed it not so much for the specific of use cases, but for
its emphasis on the importance of industrial strenght requirements,
which are captured to be sturdy, traceable and verifiable, but which
are at the same time resilient to change.
Ultimately, the structure we came up for use cases is a distillation of
the knowledge garnered both from books and from real life experience at
formalising requirements as use cases for various organisations, with
varying cultures, sizes and project scopes.
HTH,
B.
--
Barbara Rosi-Schwartz
Etish Limited [http://www.etish.org]
Blog: http://www.brs4etish.blogspot.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
| Re: Background on Approach to Use Cases [message #564158 is a reply to message #12100] |
Mon, 08 September 2008 05:02 |
| Eclipse User |
|
|
|
Looks like I'm doing some hunting. I have Leffingwell, but getting Armour
is going to be a challenge. I think it's out of print and isn't on safari
books online.
If someone has a copy that they might like to part with - either
permanently via sale or as a loan (I'm good at returning books!), please
let me know. I'm in Toronto, Canada
Many thanks,
Flavelle
|
|
| |
Goto Forum:
Current Time: Fri May 09 21:59:44 EDT 2025
Powered by FUDForum. Page generated in 0.04765 seconds |
Home