An Approach to Transformational Reengineering of SSADM Application Specifications to Object-Oriented Specifications

Many organizations are planning for transition to object-oriented software development for savings in development and maintenance costs. Appropriate tools and techniques to support this process of transition will help such organizations in overcoming many problems associated with the transition process. This paper outlines an approach to transformational reengineering of SSADM application specifications to Object-Oriented specifications

Aha\u27 Experiences in Object-Oriented Education: Searching for a Theoretical Foundation

The transition to object-oriented software development can be difficult because it represents a paradigm shift. This paper is based on the assumption that students may need to undergo one or more \u27Aha\u27 experiences in order to successfully make this transition. Literature which is relevant to research in this area is reviewed and a theoretical foundation is presente

Public and Private International Law : German Views on Global Issues

In this paper, a strategy for organisational knowledge evolution is presented. Organisational knowledge is defined as knowledge concerning the management of the artefacts provided by the organisation. The strategy is derived from a theoretical, action-oriented representation of knowledge and uses concrete instruments for iterating between reflection and action. The instruments for reflection are conceptual models and information flow diagrams. The instrument for action is an object oriented information management system, where the models are implemented and tried out in practise. By applying these instruments iteratively, organisational knowledge is generated, both as individual and shared knowledge among the actors, as well as objectified knowledge represented by the models and the implemented information management system. We describe how this strategy has been used at the Ericsson telecommunication company to handle the transition to a new software development model. The transition was complicated by the fact that Ericsson has many designers (more than 10 000) working at local design centres all over the world. Our experience shows that the proposed strategy is a powerful way to quickly acquire, deploy and manifest new organisational knowledg

Object-Oriented Modeling and Design Using DELTA, an Incremental Design Language.

Object-oriented technology has opened the doors for many new ideas in system development. The object-oriented paradigm has produced many new object-oriented programming languages. As with any new methodology, a need for formalism arises to remove ambiguities and inconsistencies and to bring a sense of continuity to software design. Formal languages provide a sound basis for software development throughout the software life cycle. This work presents a set of characteristic features for object-oriented design languages and defines a formal object-oriented design language, DELTA. The rapidly changing face of software has led to an ever increasing need to update out-of-date methods and user interfaces. Software developers want to be able to use the same type of visual interfaces available in application software. The introduction of windowing environments has led to a market for methodologies which incorporate graphical features to supplement textual components of software. The present genre of formal languages must evolve in the same direction to be considered as effective in the design process. DELTA meets this need by providing a modern development environment with graphical features to complement the text that is necessary in any design specification. Researchers and prominent software engineers have provided a litany of object-oriented methodologies. The commonality of these methods is the step-by-step approach to software development. Software engineers agree in theory that the best approach to designing software which will stand the test of time is one which has a sound established discipline. Such a discipline produces a design in incrementations. DELTA supports this theory by providing established levels of incremental design representation. The advent of computer-aided design has led to the evolution of rapid-prototyping. Changes in system requirements, detection of errors, competition in the market, and the ongoing maintenance of software systems can be addressed by the development of system prototypes. DELTA responds to this challenge by establishing a design specification representation which can be easily mapped to an object-oriented programming language. This transition from design to prototype can be enhanced by formal annotations to the chosen implementation language. Annotations have been developed for DELTA software designs prototyped in the object-oriented language Actor

Special Theme of Research in Information Systems Analysis and Design -III Teaching Systems Analysis and Design: A Case for the Object Oriented Approach

Object oriented technologies are widely accepted in software development. A survey of universities run in 2005 found that most schools recognize the need to teach OO languages. However, they continue to teach structured analysis and design. In this article we argue that this approach is a fundamental conceptual mismatch. Further, we contend that a pure OO curriculum involving OO languages and OO analysis and design is advisable in our efforts to equip our students with the knowledge to be successful as software developers. We offer ways to transition to a curriculum that emphasizes the OO philosophy of development

オブジェクト指向モデルからの自動コード生成

Object-oriented methodologies suggest to create different models of a system indicative of its different aspects. Object Modeling Technique (OMT), an object-oriented methodology, represents the static structure of classes in a system by an ER-style diagram called the object model, and the dynamic behavior of the classes by a set of state transition diagrams called the dynamic model. To speed up the software development process, it has been desired to have CASE tools that can automatically generate code from these models. In the present work, an attempt has been made to find methods to automatically generate executable code from the object-oriented models in general and the dynamic model in particular. An object-oriented approach has been proposed to convert a state diagram representing the behavior of a multi-state class into code. States are treated as classes and transitions as their operations. Inheritance is used to implement state hierarchy and object composition is used to implement concurrent states. It is realized that active objects can well be represented by activity diagrams rather than state diagrams. In the proposed approach, active objects are implemented as Java threads. A system, O-Code, has also been developed that implements the proposed method and automatically generates executable Java code from the specifications of the object and dynamic models. A comparison with Rhapsody shows that the code generated by O-Code is much more compact, efficient and understandable than that of Rhapsody.Thesis (Ph. D. in Engineering)--University of Tsukuba, (A), no. 1966, 1998.7.2

Management implications of moving from a traditional structured systems development methodology to object-orientation

Thesis (M.S.) University of Alaska Fairbanks, 2003As software application systems become larger and more complex, many software employers and managers believe that the key to sustaining its competitive advantage in the computing technology market lies in its software engineering capabilities. Software crisis situation seems to be a common occurrence in the software development environment as systems become larger and more complex. Object Orientation (OO) has been proposed as a viable alternative to traditional approach (i.e., structured techniques), an approach that many hope will solve the current software crisis. 00 is a new paradigm, and it requires new types of knowledge, new specialists, and significant changes in the mindset, an entirely different way of thinking, representing and solving a problem. The transition of moving toward the 00 from the traditional approach may involve a high risk of failure if the managers do not understand the nature of paradigm shifts and do not anticipate the future. The problem of moving to 00 has become very important. An understanding of potential problems from migrating to the new paradigm helps managers make a smoother paradigm shift. The implications and challenges of the 00 paradigm are presented. The study suggests that Object-Oriented System Development (OOSD) requires more discipline, management and training than traditional software development does. Education and experience are keys for the success of any OOSD project

Semantics of ModPascal

A denotational semantics is given for the programming language ModPascal, an object oriented procedural language. It employs concepts of abstract data type theory: heterogenous order algebras with strict operations describe the semantics of types and of a complete program, and the parameterization concept of ModPascal is based on explicit actualization by signature morphisms. This allows to treat standard language objects and user-defined objects in a uniform and sound way. Additionally; the semantic domain structure is able to support equivalence proofs in the transition from applicative languages to ModPascal as it is necessary in software development environments

An Object-oriented methodology for modern user interface development.

by Lam Siu Hong.Thesis (M.Phil.)--Chinese University of Hong Kong, 1991.Includes bibliographical references.Chapter Chapter1 --- Introduction --- p.1Chapter 1.1 --- Software Development Crisis of User Interface --- p.1Chapter 1.2 --- Objectives and Scope of Interests --- p.1Chapter 1.3 --- Overview of the Thesis --- p.2Chapter Chapter2 --- Background and Problems --- p.4Chapter 2.1 --- Categories of User Interfaces --- p.4Chapter 2.2 --- Trends of User Interfaces --- p.6Chapter 2.3 --- Some other Desirable Features and Problems of UI Development --- p.7Chapter 2.3.1 --- Separating UI from Application --- p.7Chapter 2.3.1.1 --- Benefits of Separable UIs and Applications --- p.7Chapter 2.3.1.2 --- Requirements of Complete Separation --- p.10Chapter 2.3.2 --- Instant Continuous Feedback --- p.12Chapter 2.3.2.1 --- Problems of Linguistic Model on World Model Type UIs --- p.12Chapter 2.3.3 --- Undo and Recovery --- p.15Chapter 2.3.4 --- Iterative Design through Rapid Protyping --- p.16Chapter Chapter3 --- An Object-Oriented Model for Model World User Interfaces Development --- p.18Chapter 3.1 --- Features of UIs to be supported by the Model --- p.18Chapter 3.2 --- A Linkage Model for Separating UI from Application --- p.19Chapter 3.2.1 --- Communication Messages Modeled using an Object Oriented Approach --- p.20Chapter 3.2.2 --- A Sample Message --- p.22Chapter 3.2.3 --- Linkage in a Distributed Heterogenous Environment --- p.24Chapter 3.2.4 --- Comparing the Linkage Model with the Application Interface Model in Seeheim's UI Model --- p.25Chapter 3.3 --- An Object-Oriented Model for Supporting Multiple Feedbacks and Multi-thread dialogue --- p.26Chapter 3.3.1 --- An Overview of the Model --- p.27Chapter 3.3.2 --- Objects on the Lexical Layer --- p.28Chapter 3.3.3 --- Roles of Presentation Objects --- p.29Chapter 3.3.4 --- Syntactic Objects --- p.31Chapter 3.3.5 --- Interaction Objects --- p.32Chapter 3.3.6 --- Interaction between objetcs and Linkage Component --- p.33Chapter 3.3.7 --- Multiple U-tubes Ladder for Supporting Multiple Feedbacks --- p.33Chapter 3.3.8 --- Recovery through a Generic UNDO stack --- p.35Chapter 3.3.9 --- Dialogue Control in an Object --- p.37Chapter 3.3.10 --- Interactive Objects --- p.39Chapter 3.3.11 --- An Architecture for Supporting Multi-thread Dialogue --- p.40Chapter 3.4 --- Basic Object Structure --- p.42Chapter 3.4.1 --- An Event Model for Dialogue Control --- p.43Chapter 3.4.2 --- Maintain Consistency through ε-rules --- p.45Chapter 3.4.3 --- An Example of an Inner Object Specification --- p.47Chapter 3.4.4 --- Pre and Post Condition of Action --- p.49Chapter 3.4.5 --- Automatic Message Routing --- p.49Chapter 3.5 --- Systematic Approach to UI Specification --- p.50Chapter Chapter4 --- User Interface Framework Design --- p.52Chapter 4.1 --- A Framework for UI Development --- p.52Chapter 4.1.1 --- Abstract Base Class for Each Object Type --- p.54Chapter 4.1.2 --- A Kernel for Message Routing --- p.60Chapter 4.1.3 --- Interaction Knowledge Base --- p.63Chapter 4.1.4 --- A Dynamic View of UI Objects --- p.64Chapter 4.1.5 --- Switch Box Mechanism for Dialogue Switching --- p.66Chapter 4.1.6 --- Software IC Construction --- p.68Chapter 4.2 --- Summaries of Object-Object UI Model and UI Framework --- p.70Chapter 4.2.1 --- A New Approach to User Interface Development 、 --- p.70Chapter 4.2.2 --- Feautures of UI Development provided by the Object-Object UI Model and UI Framework --- p.71Chapter Chapter5 --- Implementation --- p.73Chapter 5.1 --- Implementation of Framework in Microsoft Window Environment --- p.73Chapter 5.1.1 --- Implementation of automatic message routing through dynamic binding --- p.73Chapter 5.1.2 --- A generic message structure --- p.75Chapter 5.1.3 --- A meta class for object communication --- p.76Chapter 5.1.4 --- Software component of UI framework in Microsoft Window environment --- p.76Chapter 5.2 --- A Simple Stock Market Decision Support System (SSMDSS) --- p.77Chapter 5.2.1 --- UI Specification --- p.81Chapter 5.2.2 --- UI features supported by SSMDSS --- p.87Chapter Chapter6 --- Results --- p.89Chapter 6.1 --- Facts discovered --- p.89Chapter 6.1.1 --- Asynchronous and synchronous communication among objects --- p.89Chapter 6.1.2 --- Flexibility of the C+ + language --- p.90Chapter 6.2 --- Technical Problems Encountered --- p.91Chapter 6.2.1 --- Problems from Implementation Platform --- p.91Chapter 6.2.2 --- Problems due to Object Decomposition in an Interactive Object in SSMDSS --- p.92Chapter 6.3 --- Objectives accomplished by the Object-Oriented UI Model indicated by SSMDSS --- p.93Chapter Chapter7 --- Conclusion --- p.95Chapter 7.1 --- Thesis Summary --- p.95Chapter 7.2 --- Merits and Demerit of the Object-Oriented UI Model --- p.96Chapter 7.3 --- Cost of the Object-Oriented UI Model --- p.96Chapter 7.4 --- Future work --- p.97AppendixChapter A1 --- An Alogrithm for Converting Transition Network Diagram to Event Response Language --- p.A1Chapter A2 --- An Object-Oriented Software Development --- p.A4Chapter A2.1 --- Traditional Non Object-Oriented Software Development --- p.A4Chapter A2.2 --- An Object-Oriented Software Development --- p.A6Chapter A3 --- Vienna Development Method (VDM) --- p.A8Chapter A3.1 --- An Overview of VDM --- p.A8Chapter A3.2 --- Apply VDM to Object-Oriented UI model --- p.A10Chapter A4 --- Glossaries and Terms --- p.A12Referenc