The ODMG Standard for object data management system consists of an object Model for modeling applications, an object Definition Language (ODL)for defining database schemas, and an object Query Language (OQL) for writi...
详细信息
ISBN:
(纸本)0769512518
The ODMG Standard for object data management system consists of an object Model for modeling applications, an object Definition Language (ODL)for defining database schemas, and an object Query Language (OQL) for writing queries. Ve present a formal system to specify the data types that can be defined in an ODL database schema and analyze the data types required by OQL queries. We indicate that OQL queries require data types beyond what can be defined in the ODL. With the current specification of the ODMG Standard, no compiler or interpreter could perform type checking for all the valid OQL queries.
The configuration and collaboration of software., components in software architecture are designed to adaptively conform to a set of business requirements that often need to be updated to reflect changing business nee...
详细信息
ISBN:
(纸本)0769512518
The configuration and collaboration of software., components in software architecture are designed to adaptively conform to a set of business requirements that often need to be updated to reflect changing business needs and models. Altering collaboration sequences, business rides and processes within applications often create unacceptable maintenance overhead in a tight delivery window where the constraints of high quality software need to be balanced with (and is sometimes compromised for) rapid time-to-marker. Thus, we identify three major new characteristics that are needed to fulfill the demands of component-based software engineering today and hence-forth;namely, a) dynamic [re-] configuration based on business domain languages, b) component manners to manage collaboration and c) self-description that defines the context and abilities of a component that can be queried without violating encapsulation. We explore how Grammar-orientedobject design (GOOD), facilitates the creation of software enterprise component architectures that realize the three characteristics.
fit soft-ware industrial practice, the high cost of maintenance process of large-scale software has put emphasis on the need to manage the maintainability in earlier phases of a software lifecycle. This paper discusse...
详细信息
ISBN:
(纸本)0769512518
fit soft-ware industrial practice, the high cost of maintenance process of large-scale software has put emphasis on the need to manage the maintainability in earlier phases of a software lifecycle. This paper discusses the applicability of architectural complexity measures to managing the complexity in the maintenance phase and the reliability of the maintenance process. It also discusses the theoretical validity of the architectural complexity measures, as has been established using PVS, a formal verification system.
The industry is nowadays confronted with large-scale monolithic and inflexible object-oriented software. Because of their high business value, these legacy systems must be reengineered. One of the important issues in ...
详细信息
ISBN:
(纸本)0769512518
The industry is nowadays confronted with large-scale monolithic and inflexible object-oriented software. Because of their high business value, these legacy systems must be reengineered. One of the important issues in reengineering is the detection and location of the design flaws, which prevent an efficient maintenance and further development of the system, In this paper we present a metrics-based approach for detecting design problems, and we describe two concrete techniques for the detection of two well-known design flaws found in the literature. We apply our technique on an industrial case-study and discuss the findings. The experiment shows that the proposed technique found indeed real flaws in the system and it suggests that, based on the same approach, further detection techniques for other common design-flaws can be defined.
Business Rules, Constraints, Policies and Workflow and in general, the "manners " or rules governing the behavior of objects and components within object-oriented software architectures need to be managed, d...
详细信息
ISBN:
(纸本)0769512518
Business Rules, Constraints, Policies and Workflow and in general, the "manners " or rules governing the behavior of objects and components within object-oriented software architectures need to be managed, designed and implemented across the software development life-cycle. With such far-reaching influence and impact on software development, it is expected that the process of Rule Management would be honed into a more disciplined set of practices and methods that could be applied uniformly across multiple projects. The expectation to achieve an engineering discipline through the distillation of the industry's body of knowledge pertaining to the way rules are handled has been the motivation of workshops and harvesting of best-practices across multiple projects in various industries over the past six years. This has led to a continuous refinement and update of the Rule Pattern Language (RPL). In this paper, we provide and overview of the patterns and focus on Rule object, Type Rule and Configurable Workflow as three representative patterns in greater detail.
We improve current visual component composition environments by introducing composition patterns as first class objects that can be defined, stored and reused independently of the components. Ve document both componen...
详细信息
ISBN:
(纸本)0769512518
We improve current visual component composition environments by introducing composition patterns as first class objects that can be defined, stored and reused independently of the components. Ve document both components and composition patterns using an extended sequence diagram notation. For a component, typical usage protocols are specified while a composition pattern specifies how a set of roles interact. From this documentation, ive check whether a component can work, as described by a composition pattern using finite state automata theory and we generate glue-code for the composition. In this paper ive present our approach, explain the checking algorithms and glue code generation and discuss the tool support we developed.
Business rules are statements constraining business actions. they are context dependent, and may remain unchanged over a long period of time. The dynamic application of business rules to business actions requires a cl...
详细信息
ISBN:
(纸本)0769512518
Business rules are statements constraining business actions. they are context dependent, and may remain unchanged over a long period of time. The dynamic application of business rules to business actions requires a clear separation of the actions from the rules so that changes to business rules can be done without affecting the actions on which they are applied. In addition, rules can also be applied to a family of implementations of a business action. This paper introduces a formal theoretical business model and a specification language to write business rules. This language, called Business Transaction object-Z (BTOZ), is a conservative extension of the object-Z specification language. The paper also illustrates through a case study how BTOZ can be used to develop a business model.
Many concepts in object-oriented conceptual modelling have complex semantics that are unfortunately not precisely defined. This paper demonstrates that with a few simple and formally defined concepts one can define mo...
详细信息
ISBN:
(纸本)0769510957
Many concepts in object-oriented conceptual modelling have complex semantics that are unfortunately not precisely defined. This paper demonstrates that with a few simple and formally defined concepts one can define more complex concepts such as e.g. aggregation in a precise and formal way. The core concepts offer the possibility of layering modelling concepts;a particular pattern of simple lower level concepts can be used to represent a single high level concept. The advantage is that the high level concept is defined in terms of the lower level concepts. Because of their simplicity the lower level concepts are much easier to define formally. The high-level concept benefits from this formal definition: its own formal definition can be inferred from the formal definition of its constituent lower level concepts. This layered approach can also be followed on a project by project basis by defining high-level concepts only applicable in the context of one particular project.
Quality of Service (QoS) becomes an important issue as systems are more open, therefore less predictable. In such contexts it is difficult to ensure via static approaches that a system will provide the expected QoS. I...
详细信息
ISBN:
(纸本)0769512518
Quality of Service (QoS) becomes an important issue as systems are more open, therefore less predictable. In such contexts it is difficult to ensure via static approaches that a system will provide the expected QoS. In dynamic approaches, sen,ices are adapted to provide the best QoS according to the execution context. This article describes an object-based framework, to deal with QoS in domains in which temporal faults is a major QoS criterion. The QoS optimization policy influences most of the architectural design decisions. The implementation is based on metaobjects that collectively manage the QoS and form a two decision-levels framework: at global level, objects share the same decision policy aiming to reduce timing faults, while at object level any specific QoS criteria may be applied. QoS description is made using UML extension mechanisms. Finally, the main phases of QoS management are detailed: prediction, establishment and operational, including observation and negotiation.
The middleware technology used as the foundation of Internet-enabled enterprise information systems is becoming increasingly complex. In addition, the various technologies offer a number of standard components archite...
详细信息
ISBN:
(纸本)0769510957
The middleware technology used as the foundation of Internet-enabled enterprise information systems is becoming increasingly complex. In addition, the various technologies offer a number of standard components architectures that can be used by designers as templates to build applications. However, there is little understanding in the software industry on the strengths and weaknesses of competing technologies, and the different trade-offs that various component architectures impose. This paper describes the approach being taken in CSIRO's Middleware technology Evaluation (MTE) project to attempt to alleviate some of these problems. Specifically, this paper focuses on the scalability of transactional CORBA applications using the Visibroker Integrated Transaction Service v1.2. It discusses the methodology that has been developed, the application and environment used, and presents some performance results regarding the scalability of the Visibroker ITS.
暂无评论