Controllers in computer systems have mainly been explored for automating regulative tasks such as admission control or resource supply control. The majority of IT management tasks, however, relies on discrete management states and coordinated transitions between those states. The paper shows how the concept of a feedback system can also be applied to automate operational management tasks. The paper introduces the concept and a realization of an IT management automation controller, which operates on discrete management states expressed as a pair of models for desired and observed state. Models are represented as a special form of place-transition nets (PTN or Petri nets). Controller logic directly executes PTN in order to achieve and maintain alignment between desired and observed state in a managed domain. In contrast to workflow systems, PTN combine the description of state and actions in one model (graph). Three operational database management tasks have been implemented as a proof of concept in a blade server automation infrastructure using the management automation controller.

Management continues to be a problem for grids. A diversity of systems is in use. Their integration into more comprehensive management solutions that would simplify management, address the scale of grids and enable a higher degree of automation is difficult. This paper presents a management middleware that normalizes management for enterprise grids. Management tasks are rendered as autonomous services following a model-based approach. The paper first introduces the problem domain of managing enterprise grids and then describes the approach to a solution. The concept of a service delivery controller (SDC) is introduced that allows describing management tasks in terms of desired and observed state models, based on which a controller function autonomously performs tasks. The implementation of SDC inform of the SDC toolkit is discussed next. The SDC toolkit is based on the Globus Toolkit GT4. It extends GT4 by the standard for Web services distributed management (WSDM) and SDC-specific capabilities. Finally, a scenario is described where the developed approach and implementation have been applied to management of the Oracle 10g (grid) database system.

Setting up electronic business-to-business relationships is time-consuming and costly. It has been eased to a certain extent by standard such as RosettaNet, which use XML and XML Schema technologies to define standardized syntax messages used in interactions. However, this standardization has necessarily maintained some flexibility to allow companies with different internal processes to comply with the standard. Furthermore, the standard is syntactic, rather than semantic. Semantic constraints on interactions are currently represented informally. In this paper, we describe an application of Semantic Web technology to enhance RosettaNet and further reduce cost and time. Businesses can represent the possible ways they are able to interact as semantic and syntactic constraints. Two businesses can determine if they are able to without altering their business process by sharing constraints, and finding if the overall set is satisfiable. If it is not, they can use the data to determine what changes need to be made to their business processes. They can also use the other business' constraints to verify or generate documents which meet the constraints, and so are usable by the other business. The system integrates with current RosettaNet standards and tools through the use of a translation suite able to transform XML Schema into DAML+OIL and XML into RDF.

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?

A study of leading-edge HP object technology projects was conducted to understand the current state of object-oriented practice, and projects' object-oriented analysis and design method needs. In this paper, we distill general best practices and pitfalls from the lessons learned in these projects. We also consider how the OOA/D methods support what the businesses have set out to accomplish, where they are deficient, and how they are being modified to better support project needs. We draw upon these lessons to point out areas where OOA/D methods and CASE tools require improvement.

article Free Access Share on How do teams shape objects?—How do objects shape teams? Authors: Steven Fraser Bell-Northern Research Ltd., Ottawa, Ontario, Canada Bell-Northern Research Ltd., Ottawa, Ontario, CanadaView Profile , Kent Beck FirstClass Software FirstClass SoftwareView Profile , Grady Booch Rational Booch Rational BoochView Profile , Derek Coleman Hewlett-Packard Laboratories, Palo Alto California Hewlett-Packard Laboratories, Palo Alto CaliforniaView Profile , Jim Coplien AT&T Bell Laboratories AT&T Bell LaboratoriesView Profile , Richard Helm DMR Group., 1200 Mcill College Ave., Montreal. QC H3B 4G7 Canada DMR Group., 1200 Mcill College Ave., Montreal. QC H3B 4G7 CanadaView Profile , Kenny Rubin ParcPlace Systems ParcPlace SystemsView Profile Authors Info & Claims ACM SIGPLAN NoticesVolume 29Issue 10Oct. 1994 pp 468–473https://doi.org/10.1145/191081.191152Online:01 October 1994Publication History 2citation395DownloadsMetricsTotal Citations2Total Downloads395Last 12 Months5Last 6 weeks0 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF

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.>

Article Free Access Share on Formal techniques for OO software development Authors: Pierre America Philips Research Laboratories Philips Research LaboratoriesView Profile , Derek Coleman HP-Lab Bristol HP-Lab BristolView Profile , Roger Duke University of Queensland University of QueenslandView Profile , Doug Lea Syracuse University & SUNY-Oswego Syracuse University & SUNY-OswegoView Profile , Gary Leavens Iowa State University Iowa State UniversityView Profile Authors Info & Claims OOPSLA '91: Conference proceedings on Object-oriented programming systems, languages, and applicationsNovember 1991 Pages 166–170https://doi.org/10.1145/117954.117967Published:01 November 1991Publication History 2citation376DownloadsMetricsTotal Citations2Total Downloads376Last 12 Months13Last 6 weeks1 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF

Article Free Access Share on Coherent models for object-oriented analysis Authors: Fiona Hayes Hewlett Packard Laboratories, Bristol BS12 6QZ, UK Hewlett Packard Laboratories, Bristol BS12 6QZ, UKView Profile , Derek Coleman Hewlett Packard Laboratories, Bristol BS12 6QZ, UK Hewlett Packard Laboratories, Bristol BS12 6QZ, UKView Profile Authors Info & Claims OOPSLA '91: Conference proceedings on Object-oriented programming systems, languages, and applicationsNovember 1991 Pages 171–183https://doi.org/10.1145/117954.117968Online:01 November 1991Publication History 36citation438DownloadsMetricsTotal Citations36Total Downloads438Last 12 Months9Last 6 weeks1 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF

It is shown how design time testing can be used in conjunction with formal specification. Emphasis is placed on the benefits of using an executable specification language OBJ, of having a design controlled by requirements specification, and of adherence to the regularity and uniformity hypotheses in dynamic validation. It is shown that such an approach offers positive benefits by providing early design validation and a controlled, disciplined design process.>

This paper defines the algebraic specification language implemented by the UMIST OBJ system. It also illustrates the use of the language for the definition of abstract, executable specifications of the behaviour of computer programs. The system implements an executable subset of J.A. Goguen's OBJ language, which is based on the algebraic definition of abstract data types. The language permits data type and operations to be defined abstractly, i.e. independently of any particular representation. Moreover, the definitions of an OBJ specification can be treated as an abstract program, by regarding the equations contained in a specification as a set of left-right rewrite rules which may be used to simplify terms. This makes the language useful for formulating and exploring the consequences of abstract designs, and developing relevant parts of the theory of the associated problem domain. The ability to exercise descriptions of the theory of a problem domain is a powerful tool for the programmer. By providing timely feedback on the correctness of design decisions, such use of the language encourages and reinforces the exploration of design possibilities. With these features, UMIST OBJ embodies the foundation of a framework for effective software engineering. It provides an accessible basis for both mechanisable formal notations for program description and semantically motivated support tools.

A method of program design is described which leads naturally to the expression of a program as a pipeline network of simple processes. Starting from the problem statement the valid inputs and outputs are specified by grammars, which can be combined to define the requisite translation. A notation for translation grammars is described informally which allows a translation to take into account semantic as well as syntactic information. Terminal symbols may be attributed by data types and may be qualified by Boolean expressions. The notation is capable of direct compilation but in this paper we show how it may be used to derive a program in a conventional high level language such as Pascal or Cobol. It is shown that more complex problems can be solved by simple pipeline structures of simple translations. Provided that nonbacktracking grammars are used to specify translations, the pipeline structure is well-suited to concurrent execution on a multiprocessor. The method is illustrated by examples from data processing.

Abstract This paper assesses Concurrent Pascal against its design aims. The language is shown to be suitable for writing reliable non‐trivial concurrent applications programs and operating systems. The major weakness of the language is its inability to provide an environment for other Concurrent Pascal programs. A new language construct, group, is proposed to remedy this difficulty.