Security is an important issue that must be considered as a fundamental requirement in information systems development, and particularly in database design. Therefore security, as a further quality property of softwar...
详细信息
Security is an important issue that must be considered as a fundamental requirement in information systems development, and particularly in database design. Therefore security, as a further quality property of software, must be tackled at all stages of the development. The most extended secure database model is the multilevel model, which permits the classification of information according to its confidentiality, and considers mandatory access control. Nevertheless, the problem is that no database design methodologies that consider security (and therefore secure database models) across the entire life cycle, particularly at the earliest stages currently exist. Therefore it is not possible to design secure databases appropriately. Our aim is to solve this problem by proposing a methodology for the design of secure databases. In addition to this methodology, we have defined some models that allow us to include security information in the database model, and a constraintlanguage to define security constraints. As a result, we can specify a fine-grained classification of the information, defining with a high degree of accuracy which properties each user has to own in order to be able to access each piece of information. The methodology consists of four stages: requirements gathering;database analysis;multilevel relational logical design;and specific logical design. The first three stages define activities to analyze and design a secure database, thus producing a general secure database model. The last stage is made up of activities that adapt the general secure data model to one of the most popular secure database management systems: Oracle9i Label Security. This methodology has been used in a genuine case by the Data Processing Center of Provincial Government. In order to support the methodology, we have implemented an extension of Rational Rose, including and managing security information and constraints in the first stages of the methodology. (c) 2004 Elsevier B.V.
A major purpose of analysis is to represent precisely all relevant facts, as they are observed in the external world. A substantial problem in object-oriented analysis is that most modelling languages are more suitabl...
详细信息
The definition of the second major release of the Unified Modelling language, or UML 2.0, has been a long process. But the latest version of the object Management Group (OMG) standard will soon be ready. The large num...
详细信息
The definition of the second major release of the Unified Modelling language, or UML 2.0, has been a long process. But the latest version of the object Management Group (OMG) standard will soon be ready. The large number of changes between UML 1.x and UML 2.0 have raised concerns from users: what is new in UML 2.0? Should I migrate? Is it compatible with existing UML 1.x?
For large-scale software system development, many configuration items will be produced during software life cycle and every configuration item will evolve independently. Therefore, there is a need for adopting a suita...
详细信息
ISBN:
(纸本)0780379527
For large-scale software system development, many configuration items will be produced during software life cycle and every configuration item will evolve independently. Therefore, there is a need for adopting a suitable model to describe the configuration items, the relationship among them, the evolving of a single item and the constraints of the system. By means of UML class diagram, we propose a software configuration meta-model to express configuration items, relationships among the items and the evolvement of each configuration item. The model consists of three kinds of classes: configuration item, port and version. We also defined four relationships: aggregation, generalization, dependency and successor. The notion of port is used to describe the static properties and dynamic behaviors of a configuration item. The constraints of configuration items are defined using the object constraint language (OCL). The model must conform to several constraints: well-formed configuration, behavior equivalence, upward compatibility, and structural conformance. In short, the model can express complex software product structure and describe constraints in a precise way. It provides a strong basis for controlling change and supporting support management and development in the large-scale software system.
The textual object constraint language (OCL) is an official part of the Unified Modeling language (UML). OCL is primarily used to formulate restrictions over UML models, in particular, invariants and operation pre- an...
详细信息
ISBN:
(纸本)1932415211
The textual object constraint language (OCL) is an official part of the Unified Modeling language (UML). OCL is primarily used to formulate restrictions over UML models, in particular, invariants and operation pre- and post-conditions in the context of class diagrams. However OCL is missing means to specify constraints over the dynamic behavior of a UML model. We have therefore developed a temporal extension of OCL that enables modelers to specify behavioral state-oriented constraints. That work provides an alternative to the rather cryptic temporal logic formulae that are commonly used to specify behavioral system properties. This article now illustrates that our OCL extension allows for specifying all kinds of properties that are regarded as relevant in practice. We present according temporal OCL expressions for property specification patterns that have been identified in the area of formal specification.
Activity based costing (ABC) is a method which can solve many limitations of the traditional cost systems in manufacturing management. In this paper, we investigate how to integrate ABC with workflow technology, and ...
详细信息
Activity based costing (ABC) is a method which can solve many limitations of the traditional cost systems in manufacturing management. In this paper, we investigate how to integrate ABC with workflow technology, and build a workflow meta model supporting ABC. Firstly, the concept and concept model of activity based costing (ABC) are introduced. Next, the meta model of P -PROCE (Process, Product, Resource, Organization, and Cost & Evaluation) is presented. Then the cost meta model is defined by adding ABC to P -PROCE model. object constraint language (OCL) is used to express meta model and constraints. Finally, we show an enterprise modeling and simulation tool based on the workflow meta model. We can systematically construct an enterprise model and easily and efficiently conduct simulation. Moreover it enables us to analyze and evaluate business processes and its costs.
This paper is concerned with Quality of Service (QoS) specification in distributed system design. The specification and implementation of QoS is increasingly important in distributed systems due to the need to address...
详细信息
This paper is concerned with Quality of Service (QoS) specification in distributed system design. The specification and implementation of QoS is increasingly important in distributed systems due to the need to address questions of performance, particularly for systems involving multimedia. To ensure correct implementation of QoS requirements, statements of QoS need to be introduced early in the design process, and in terms of design we consider the use of the Unified Modelling language (UML), which has quickly become the de facto standard for object-based designs. The framework we use for distributed system construction is that provided by the open distributed processing reference model, and we focus in particular on its computational viewpoint. The aim of this paper is to construct a UML model of the computational viewpoint focusing on the description of QoS within that viewpoint. To specify the QoS aspects of computational objects in the UML model, we use a real-time logic called QL. In order to express further constraints on the UML model of the computational viewpoint, we use the object constraint language to express invariants that each instance of our model must satisfy. The purpose of our UML model of the computational viewpoint is to act as a template via which specific distributed system designs can be constructed and we illustrate this with the specification of a lip synchronisation mechanism. (C) 2002 Elsevier Science B.V. All rights reserved.
The Unified Modeling language (UML) is a family of design notations that is rapidly becoming a de facto standard software design language. UML provides a variety of useful capabilities to the software designer, includ...
详细信息
The Unified Modeling language (UML) is a family of design notations that is rapidly becoming a de facto standard software design language. UML provides a variety of useful capabilities to the software designer, including multiple, interrelated design views, a semiformal semantics expressed as a UML meta model, and an associated language for expressing formal logic constraints on design elements. The primary goal of this work is an assessment of UMLs expressive power for modeling software architectures in the manner in which a number of existing software architecture description languages (ADLs) model architectures. This paper presents two strategies for supporting architectural concerns within UML. One strategy involves using UML "as is," while the other incorporates useful features of existing ADLs as UML extensions. We discuss the applicability, strengths, and weaknesses of the two strategies. The strategies are applied on three ADLs that, as a whole, represent a broad cross-section of present-day ADL capabilities. One conclusion of our work is that UML currently lacks support for capturing and exploiting certain architectural concerns whose importance has been demonstrated through the research and practice of software architectures. In particulars UML lacks direct support for modeling and exploiting architectural styles, explicit software connectors, and local and global architectural constraints.
The purpose of this paper is to first showcase the concept of an operation schema-a precise form of system-level operation specification-and secondly show how operation schemas enhance development when they are used a...
详细信息
ISBN:
(纸本)354041133X
The purpose of this paper is to first showcase the concept of an operation schema-a precise form of system-level operation specification-and secondly show how operation schemas enhance development when they are used as a supplement to use case descriptions. An operation schema declaratively describes the effects of a system operation by pre- and postconditions using the object constraint language (OCL), as defined by the Unified Modeling language (UML). In particular, the paper highlights techniques to map use cases to operation schemas and discusses the advantages of doing so in terms of clarifying the granularity and purpose of use cases and providing a precise specification of system behavior.
暂无评论