Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275)最新文献_第4页

Abstract object state and version recovery in N-version programming n版本编程中抽象对象状态与版本恢复

Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275) Pub Date : 1999-06-07 DOI: 10.1109/TOOLS.1999.779002

A. Romanovsky

{"title":"Abstract object state and version recovery in N-version programming","authors":"A. Romanovsky","doi":"10.1109/TOOLS.1999.779002","DOIUrl":"https://doi.org/10.1109/TOOLS.1999.779002","url":null,"abstract":"The paper deals with the use of software diversity, specifically, N-version programming (NVP) in object oriented (OO) systems. We formulate the problem of faulty version recovery and show how our NVP scheme, developed recently, can be extended to solve it. Our approach relies on using the abstract version state, which represents a common general description of the states of all correct version objects. The recovery consists in mapping the state of a correct version onto the state of the faulty version via the abstract state. We introduce a formal description of our model and show that many ideas related to object state abstraction can be found in the existing research on OO programming. We discuss extensions of LAYOM and PSL as promising practical approaches for developing recovery features in OO programming. As an alternative solution, we propose a meta-object architecture and a related protocol which can facilitate the solution of the object version recovery problem. The paper finishes with a brief discussion of engineering steps which have to be done for developing recoverable version objects and of some approaches which can improve the reusability of the scheme proposed.","PeriodicalId":434404,"journal":{"name":"Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275)","volume":"29 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-06-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128970938","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 4

Adding visual rules to object-oriented modeling techniques 向面向对象建模技术添加可视规则

Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275) Pub Date : 1999-06-07 DOI: 10.1109/TOOLS.1999.779019

G. Taentzer

{"title":"Adding visual rules to object-oriented modeling techniques","authors":"G. Taentzer","doi":"10.1109/TOOLS.1999.779019","DOIUrl":"https://doi.org/10.1109/TOOLS.1999.779019","url":null,"abstract":"The modeling of behavior in object oriented systems usually relies on control for diagrams and (extended) state automatas. These basic techniques do not support the design in a declarative style very well. This style is useful for modeling integrity constraints, especially active constraints, on the data model, to perform event handling, to derived new attribute values and associations and to model strategies in business and engineering. Rules are added as a declarative modeling technique for behavior. Roughly speaking, a rule consists of a condition and an action. If the condition is true, the action is performed. The concept of rules is integrated into an existing object oriented modeling technique by formulating rules on object diagrams. A rule application may test and change a certain object structure. The application may be triggered automatically by a relevant change of this object structure, periodically or by an event occurring in some behavior diagram. This rule concept has an underlying formal semantics on the basis of graph transformation which may be exploited for analyzing a designed rule set, concerning, e.g. conflicts, dependencies, etc. The graphical notation of the rules follows the UML notations as far as possible.","PeriodicalId":434404,"journal":{"name":"Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275)","volume":"2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-06-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114279447","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 7

Efficiency in C++ c++中的效率

Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275) Pub Date : 1999-06-07 DOI: 10.1109/TOOLS.1999.10009

S. Lippman

引用次数: 0

Dejay: unifying concurrency and distribution to achieve a distributed Java Dejay:统一并发和分布，实现分布式Java

Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275) Pub Date : 1999-06-07 DOI: 10.1109/TOOLS.1999.779020

M. Boger, Frank Wienberg, W. Lamersdorf

引用次数: 10

The requirements/service/interface (RSI) approach to use case analysis (a pattern for structured use case development) 用例分析的需求/服务/接口(RSI)方法(结构化用例开发的模式)

Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275) Pub Date : 1999-06-07 DOI: 10.1109/TOOLS.1999.779010

Mark Collins-Cope

{"title":"The requirements/service/interface (RSI) approach to use case analysis (a pattern for structured use case development)","authors":"Mark Collins-Cope","doi":"10.1109/TOOLS.1999.779010","DOIUrl":"https://doi.org/10.1109/TOOLS.1999.779010","url":null,"abstract":"Use case analysis is a requirements capture technique that is most often used in the early stages of OO and component development projects. When engineers first undertake use case analysis, a number of issues are raised for which easy answers can't be found in the text books, such as: what is the appropriate level of granularity for use cases? If large grained use cases are used, should they decomposed into 'lower level' use cases? If so, at what point should this decomposition stop, and how should these sub-use cases be used? Should user or external system interface functionality be described in use case text? How do dialog descriptions fit in? Where do report layouts go? Should user interface dynamics be included? Should interchange file formats, or interface protocols form part of the documentation? This paper describes the RSI approach to use case analysis. This approach provides a framework for analysing and understanding potential use case deliverables and their interrelationships, with a view to answering the above questions. The RSI approach also aims to assist in maximising software reuse-by partitioning functionality into those aspects which are concerned with 'managing the interface' to an actor and those areas which make up the reusable core of the system.","PeriodicalId":434404,"journal":{"name":"Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275)","volume":"34 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-06-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114527183","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 12

Reflexivity and meta-tools to manage your software real estate 反思性和元工具来管理您的软件资产

Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275) Pub Date : 1999-06-07 DOI: 10.1109/TOOLS.1999.10001

D. Blasband

引用次数: 0

Dependable multiparty interactions: a case study 可靠的多方交互:一个案例研究

Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275) Pub Date : 1999-06-07 DOI: 10.1109/TOOLS.1999.779062

A. Zorzo

引用次数: 6

Towards integration of state machines and object-oriented languages 迈向状态机和面向对象语言的集成

Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275) Pub Date : 1999-06-07 DOI: 10.1109/TOOLS.1999.779018

O. Madsen

引用次数: 16

Measuring OO systems: a critical analysis of the MOOD metrics 度量OO系统:对MOOD度量的关键分析

Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275) Pub Date : 1999-06-07 DOI: 10.1109/TOOLS.1999.779004

Tobias Mayer, T. Hall

{"title":"Measuring OO systems: a critical analysis of the MOOD metrics","authors":"Tobias Mayer, T. Hall","doi":"10.1109/TOOLS.1999.779004","DOIUrl":"https://doi.org/10.1109/TOOLS.1999.779004","url":null,"abstract":"In parallel with the rise to prominence of the OO paradigm has come the acceptance that conventional software metrics are not adequate to measure object oriented systems. This has inspired a number of software practitioners and academics to develop new metrics that are suited to the OO paradigm. Arguably, the most thorough treatment of the subject is that of the MOOD team, under the leadership of Abreau. The MOOD metrics have been subjected to much empirical evaluation, with claims made regarding the usefulness of the metrics to assess external attributes such as quality and maintainability. We evaluate the MOOD metrics on a theoretical level and show that any empirical validation is premature, due to the majority of the MOOD metrics being fundamentally flawed. The metrics either fail to meet the MOOD team's own criteria or are founded on an imprecise, and in certain cases inaccurate, view of the OO paradigm. We propose our own solutions to some of these anomalies and clarify some important aspects of OO design, in particular those aspects that may cause difficulties when attempting to define accurate and meaningful metrics. The suggestions we make are not limited to the MOOD metrics but are intended to have a wider applicability in the field of OO metrics.","PeriodicalId":434404,"journal":{"name":"Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275)","volume":"83 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-06-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122995781","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 36

A design model for object-oriented systems with explicit architecture 具有显式体系结构的面向对象系统的设计模型

Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275) Pub Date : 1999-06-07 DOI: 10.1109/TOOLS.1999.778998

A. Sosio, F. Tisato

引用次数: 1