December 2008
Beginner
320 pages
8h 52m
English
Content preview from Requirements Modelling and Specification for Service Oriented Architecture
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
7.2. Some Problems with the Conventional Approach to Use Cases
Use cases were first introduced as a technique for specifying telephone switching systems at Ericsson and were later recognized as a brilliant and useful idea by the object-oriented methods community. Most methodologists of that generation integrated use cases into their methods and they are a key feature of UML. Use cases offered possibly the first technique within object-oriented development that did not assume that a written system specification existed at the start of object-oriented analysis.
In this section I consider a number of features of the conventional use case approach that militate against its successful use. In the next we will see how these may be overcome. The problems are, in brief, as follows.
Overemphasis on functional decomposition.
Lack of a clear definition and agreed interpretation.
The inappropriate use of controller objects.
Confusion over the relationship of use cases with scenarios.
Lack of a notion of genericity.
Lack of a notion of atomicity.
Too much detail and too many use cases as a result of poor abstraction.
Poor exception handling.
7.2.1. Overemphasis on Functional Decomposition
At first sight, the use case approach appears to have a more functional flavour than an object-oriented practitioner would be comfortable with. Blaha and Premerlani (1998), leading thinkers behind OMT, go so far as to include a treatment of use cases within the dataflow-based Functional Model of that method. This ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.