Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Stephen Bear

dblp:15/48 · DBLP profile ↗
← Back
3ranked-venue papers
0as first author
0since 2021 · last 1992
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 2Artificial intelligence and machine learning · 1Databases, data management, data science and information retrieval · 1Human-computer interaction and ubiquitous computing · 1Applied, interdisciplinary, general and emerging computing · 1

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Requirements engineering and software design · 100%

Topics — the 1 heaviest of 2, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › object-oriented analysis and design
object-oriented design
0.011992
Introducing Objectcharts or How to Use Statecharts in Object-Oriented Design · IEEE Trans. Software Eng. 1992

Methods — techniques the papers use, named apart from their topics

statecharts · 0.0formal specification · 0.0
YearPublicationVenuePosition
1992 OASIS: An Object-Oriented Specification Language
Oscar Pastor 0001, Fiona Hayes, Stephen Bear
CAiSE3
1992 Specifying medical software
abstract
The authors have successfully applied formal specification techniques to the construction of medical products. The approach is characterized by concentrating on the use of HP-SL to construct clear and precise specifications of behavior. In a number of collaborative product developments, the effectiveness of the software development process has been improved significantly without getting involved in the 'difficult' formal methods areas of refinement and program proof.>
T. Rush, Stephen Bear
CBMS2
1992 Introducing Objectcharts or How to Use Statecharts in Object-Oriented Design
abstract
A notation called Objectcharts for specifying object classes is introduced. An Objectchart diagram is an extended form of a Statechart, which characterizes the behavior of a class as a state machine. The Objectchart transitions correspond to the state-changing methods that the class provides and those that it requires of other classes. Object attributes and observer methods annotate Objectchart states. Firing and postconditions are used to specify the effect of transitions on class attributes. The Objectchart notions is described through the development of an alarm clock application. How Objectcharts can be used to find subtyping inheritance relationships between classes and a systematic approach for evolving Objectchart specifications are shown.>
Derek Coleman, Fiona Hayes, Stephen Bear
IEEE Trans. Software Eng.3