Results 1 - 10
of
239
A Framework for Expressing the Relationships Between Multiple Views in Requirements Specification
- IEEE TRANSACTIONS ON SOFTWARE ENGINEERING
, 1994
"... Composite systems are generally comprised of heterogeneous components whose specifications are developed by many development participants. The requirements of such systems are invariably elicited from multiple perspectives which overlap, complement and contradict each other. Furthermore, these requi ..."
Abstract
-
Cited by 356 (38 self)
- Add to MetaCart
Composite systems are generally comprised of heterogeneous components whose specifications are developed by many development participants. The requirements of such systems are invariably elicited from multiple perspectives which overlap, complement and contradict each other. Furthermore, these requirements are generally developed and specified using multiple methods and notations respectively. It is therefore necessary to express and check the relationships between the resultant specification fragments. In this paper we deploy multiple "ViewPoints" that hold partial requirements specifications, described and developed using different representation schemes and development strategies. We discuss the notion of interViewPoint communication in the context of this ViewPoints framework, and propose a general model for ViewPoint interaction and integration. We elaborate on some of the requirements for expressing and enacting inter-ViewPoint relationships - the vehicles for consistency che...
xlinkit: A Consistency Checking and Smart Link Generation Service
, 2000
"... ... In this paper we show how consistency constraints can be expressed and checked. We describe a novel semantics for first order logic that produces links instead of truth values and give an account of our content management strategy. We present the architecture of our service and the results of tw ..."
Abstract
-
Cited by 141 (15 self)
- Add to MetaCart
... In this paper we show how consistency constraints can be expressed and checked. We describe a novel semantics for first order logic that produces links instead of truth values and give an account of our content management strategy. We present the architecture of our service and the results of two substantial case studies that use xlinkit for checking course syllabus information and for validating UML models supplied by industrial partners.
Using ViewPoints for Inconsistency Management
- SOFTWARE ENGINEERING JOURNAL
, 1996
"... Large-scale software development is an evolutionary process. In an evolving specification, multiple development participants often hold multiple, inconsistent views on the system being developed, and considerable effort is spent handling recurrent inconsistencies. Detecting and resolving inconsisten ..."
Abstract
-
Cited by 113 (24 self)
- Add to MetaCart
Large-scale software development is an evolutionary process. In an evolving specification, multiple development participants often hold multiple, inconsistent views on the system being developed, and considerable effort is spent handling recurrent inconsistencies. Detecting and resolving inconsistencies is only part of the problem: a resolved inconsistency might not stay resolved as a specification evolves. Frameworks in which inconsistency is tolerated help by allowing resolution to be delayed. However, the evolution of a specification may affect both resolved and unresolved inconsistencies. We present and elaborate a framework in which software development knowledge is partitioned into multiple views called "ViewPoints". Inconsistencies between ViewPoints are managed by explicitly representing relationships between them, and recording both resolved and unresolved inconsistencies. We assume that ViewPoints will often be inconsistent with one another, and we ensure that a complete wor...
A Framework for Multi-Valued Reasoning over Inconsistent Viewpoints
, 2001
"... In requirements elicitation, different stakeholders often hold different views of how a proposed system should behave, resulting in inconsistencies between their descriptions. Consensus may not be needed for every detail, but it can be hard to determine whether a particular disagreement affects the ..."
Abstract
-
Cited by 86 (27 self)
- Add to MetaCart
(Show Context)
In requirements elicitation, different stakeholders often hold different views of how a proposed system should behave, resulting in inconsistencies between their descriptions. Consensus may not be needed for every detail, but it can be hard to determine whether a particular disagreement affects the critical properties of the system. In this paper, we describe the # bel framework for merging and reasoning about multiple, inconsistent state machine models. # bel permits the analyst to choose how to combine information from the multiple viewpoints, where each viewpoint is described using an underlying multi-valued logic. The different values of our logics typically represent different levels of agreement. Our multi-valued model checker, # chek, allows us to check the merged model against properties expressed in a temporal logic. The resulting framework can be used as an exploration tool to support requirements negotiation, by determining what properties are preserved for various combinations of inconsistent viewpoints.
Managing Inconsistent Specifications: Reasoning, Analysis, and Action
- ACM Transactions on Software Engineering and Methodology
, 1995
"... This article is a revised and extended version of our earlier work which appeared in Proceedings of the 3rd International Symposium on Requirements Engineering (1997), pages 78 -- 86; Authors' addresses: A. Hunter, Department of Computer Science, University College London, Gower Street, London ..."
Abstract
-
Cited by 86 (22 self)
- Add to MetaCart
This article is a revised and extended version of our earlier work which appeared in Proceedings of the 3rd International Symposium on Requirements Engineering (1997), pages 78 -- 86; Authors' addresses: A. Hunter, Department of Computer Science, University College London, Gower Street, London WC1E 6BT, UK; email: A.Hunter@cs.ucl.ac.uk; B. Nuseibeh, Department of Computing, Imperial College, 180 Queen's Gate, London, SW7 2BZ, UK; email: ban@doc.ic.ac.uk.
Instant consistency checking for the UML
- In Proc. 28th International Conference on Software Engineering (ICSE
, 2006
"... ABSTRACT Inconsistencies in design models should be detected immediately to save the engineer from unnecessary rework. Yet, tools are not capable of keeping up with the engineers' rate of model changes. This paper presents an approach for quickly, correctly, and automatically deciding what con ..."
Abstract
-
Cited by 75 (9 self)
- Add to MetaCart
(Show Context)
ABSTRACT Inconsistencies in design models should be detected immediately to save the engineer from unnecessary rework. Yet, tools are not capable of keeping up with the engineers' rate of model changes. This paper presents an approach for quickly, correctly, and automatically deciding what consistency rules to evaluate when a model changes. The approach does not require consistency rules with special annotations. Instead, it treats consistency rules as black-box entities and observes their behavior during their evaluation to identify what model elements they access. The UML/Analyzer tool, integrated with IBM Rational Rose™, fully implements this approach. It was used to evaluate 29 models with tens-of-thousands of model elements, evaluated on 24 types of consistency rules over 140,000 times. We found that the approach provided design feedback correctly and required, in average, less than 9ms evaluation time per model change with a worst case of less than 2 seconds at the expense of a linearly increasing memory need. This is a significant improvement over the state-of-the-art.
Inconsistency Management for Multiple-View Software Development Environments
- IEEE Transactions on Software Engineering
, 1998
"... Abstract—Developers need tool support to help manage the wide range of inconsistencies that occur during software development. Such tools need to provide developers with ways to define, detect, record, present, interact with, monitor and resolve complex inconsistencies between different views of sof ..."
Abstract
-
Cited by 65 (12 self)
- Add to MetaCart
(Show Context)
Abstract—Developers need tool support to help manage the wide range of inconsistencies that occur during software development. Such tools need to provide developers with ways to define, detect, record, present, interact with, monitor and resolve complex inconsistencies between different views of software artifacts, different developers and different phases of software development. This paper describes our experience with building complex multiple-view software development tools that support diverse inconsistency management facilities. We describe software architectures we have developed, user interface techniques used in our multiple-view development tools, and discuss the effectiveness of our approaches compared to other architectural and HCI techniques. Index Terms—Inconsistency management, multiple views, integrated software development environments, collaborative software development. 1
Experiences Using Lightweight Formal Methods for Requirements Modeling
- IEEE Transactions on Software Engineering
, 1998
"... Additional information is available from the NASA Software IV&V Facility on the ..."
Abstract
-
Cited by 64 (8 self)
- Add to MetaCart
Additional information is available from the NASA Software IV&V Facility on the
Inconsistency management in software engineering: Survey and open research issues
- in Handbook of Software Engineering and Knowledge Engineering
, 2001
"... The development of complex software systems is a complex and lengthy activity that involves the participation and collaboration of many stakeholders (e.g. customers, users, analysts, designers, and developers). This results in many partial models of the developing system. These models can be inconsi ..."
Abstract
-
Cited by 61 (4 self)
- Add to MetaCart
The development of complex software systems is a complex and lengthy activity that involves the participation and collaboration of many stakeholders (e.g. customers, users, analysts, designers, and developers). This results in many partial models of the developing system. These models can be inconsistent with each other since they describe the system from different perspectives and reflect the views of the stakeholders involved in their construction. Inconsistent software models can have negative and positive effects in the software development life-cycle. On the negative side, inconsistencies can delay and increase the cost of system development; do not guarantee some properties of the system, such as safety and reliability; and generate difficulties on system maintenance. On the positive side, inconsistencies can facilitate identification of some aspects of the system that need further analysis, assist with the specification of alternatives for the development of the system, and support elicitation of information about it. The software engineering community has proposed many techniques and methods to support the management of inconsistencies in various software models. In this paper, we present a survey of these techniques and methods. The survey is organized according to a conceptual framework which views inconsistency management as a process composed of six activities. These activities are the detection of overlaps, detection of inconsistencies, diagnosis of inconsistencies, handling of inconsistencies, tracking of inconsistencies, and specification and application of a management policy for inconsistencies. This paper also presents the main contributions of the research work that has been conducted to support each of the above activities and identifies the issues which are still open to further research. 1.
Co-ordinating Distributed ViewPoints: the anatomy of a consistency check
- CONCURRENT ENGINEERING: RESEARCH AND APPLICATIONS
, 1994
"... ..."
(Show Context)