John Artim

dblp:93/3388 · DBLP profile ↗
← Back
2ranked-venue papers
1as first author
0since 2021 · last 1998
0000-0001-5295-6803ORCID · verified

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

Software engineering, systems software and programming languages · 2 · 1 first-author

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
2 papers
Requirements engineering and software design · 70% Empirical software engineering · 30%

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

TopicWeightPapersLastEvidence papers
Empirical software engineering › developer studies
developer collaboration
0.011998
Object-Oriented Practice in 1998: Does it help or hinder collaboration? (Panel) · OOPSLA 1998
Requirements engineering and software design
software design notation
0.011997
UML: The Language of Blueprints for Software? (Panel) · OOPSLA 1997
Requirements engineering and software design › model-driven engineering
UML
0.011997
UML: The Language of Blueprints for Software? (Panel) · OOPSLA 1997
Requirements engineering and software design
object-oriented development
0.011998
Object-Oriented Practice in 1998: Does it help or hinder collaboration? (Panel) · OOPSLA 1998
Requirements engineering and software design
object-oriented analysis and design
0.011997
UML: The Language of Blueprints for Software? (Panel) · OOPSLA 1997
YearPublicationVenuePosition
1998 Object-Oriented Practice in 1998: Does it help or hinder collaboration? (Panel)
abstract
Groups of people working in concert perform most commercial, industrial or in-house software development. These groups are often quite diverse. This panel brings together object-oriented consultants and developers as well as practitioners and researchers interested in human factors and user-centered design, project management and technical writing. The panel will address the question, "To successfully complete today's projects, does object-oriented development as practiced today do an adequate job of supporting ALL of the participants who must collaborate?"
John Artim, Charlie Bridgeford, Lillian Christman, James Coplien, Mary Beth Rosson, Stanley Taylor, Rebecca Wirfs-Brock
OOPSLA1
1997 UML: The Language of Blueprints for Software? (Panel)
abstract
The Unified Method was launched by Grady Booch and Jim Rumbaugh at an OOPSLA'95 Conference Fringe meeting organised by Rational Software Corporation. In 1996 Unified Method was re-scoped to a notation, and renamed Unified Modeling Language (UML).Earlier this year, UML was submitted to Object Management Group for standardisation and has been endorsed by Microsoft, IBM, HP, Platinum Technologies, ObjectTime and many other corporations. No wonder UML is leading contender as de facto standard notation for object-oriented analysis and design.The panel will take a sanity check, and will go beyond hype and newsgroup flames and attempt to form an objective view of UML and its prospects.The members of panel have been working closely with UhL in many different roles, including that of UML language designer, end-user, consultant, CASE tool expert, and object-oriented methodologist. The discussion will focus on how LJML matches up in practice against one of its original. raisons d'etre as the language of blueprints for software.Specific issues to be addressed include:• What is advantage of UML over existing OOA/D notations?• Can UML be used on real projects today?• Is language sufficiently simple, and well-enough defined, to become de facto standard?• Will UML lead to improved OOA/D methods and CASE tools?• What is importance of meta-model in UML?
Derek Coleman, John Artim, Victor Ohnjec, Erick Rivas, James E. Rumbaugh, Rebecca Wirfs-Brock
OOPSLA2