Separation of Concerns and Consistent Integration in Requirements Modelling

Chen, Xin; Liu, Zhiming; Mencl, Vladimir

doi:10.1007/978-3-540-69507-3_71

Cited by 18 publications

(8 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The detailed specification of the interactions and functionality provide the full information needed to construct the final model of the structure view. The consistency and integrated semantics of the different views are studied in [6]. In the following, requirements for the POS example are used to illustrate this.…”

Section: Requirements Elicitationmentioning

confidence: 99%

A Refinement Driven Component-Based Design

Chen

Liu

Stolz

et al. 2007

12th IEEE International Conference on Engineering Complex Computer Systems (ICECCS 2007)

Self Cite

View full text Add to dashboard Cite

Modern software applications ranging from enterprise to embedded systems are becoming increasingly complex, and require very high levels of dependability assurance. The most effective means to handle complexity is separation of concerns and incremental development, and assurance of dependability requires formal methods. We report here our experience on these issues in an application of a formal calculus, rCOS, to a component-based design of the point of sale system (POS). We demonstrate the possibility in scaling-up correctness by design and discuss how rCOS may be integrated with current and emerging software engineering tools.

show abstract

Section: Requirements Elicitationmentioning

confidence: 99%

A Refinement Driven Component-Based Design

Chen

Liu

Stolz

et al. 2007

12th IEEE International Conference on Engineering Complex Computer Systems (ICECCS 2007)

Self Cite

View full text Add to dashboard Cite

show abstract

“…In previous work, we investigated the possibility of using Software Engineering-or Model-Driven Development tools like MasterCraft [52,11] or ModelMorf [56,57] to facilitate the rCOS process in existing tools. Clearly, extending an industrialstrength tool is beyond the capabilities of a research project.…”

Section: Tool Supportmentioning

confidence: 99%

“…The combination of the state diagram and the static functionality specification is a guarded design for the contracts [11].…”

Section: Requirements Elicitation and Modellingmentioning

confidence: 99%

Refinement and verification in component-based model-driven design

Chen¹,

Liu²,

Ravn

et al. 2009

Science of Computer Programming

Self Cite

View full text Add to dashboard Cite

a b s t r a c tModern software development is complex as it has to deal with many different and yet related aspects of applications. In practical software engineering this is now handled by a UML-like modelling approach in which different aspects are modelled by different notations. Component-based and object-oriented design techniques are found effective in the support of separation of correctness concerns of different aspects. These techniques are practised in a model-driven development process in which models are constructed in each phase of the development. To ensure the correctness of the software system developed, all models constructed in each phase are verifiable. This requires that the modelling notations are formally defined and related in order to have tool support developed for the integration of sophisticated checkers, generators and transformations. This paper summarises our research on the method of Refinement of Component and Object Systems (rCOS) and illustrates it with experiences from the work on the Common Component Modelling Example (CoCoME). This gives evidence that the formal techniques developed in rCOS can be integrated into a model-driven development process and shows where it may be integrated in computer-aided software engineering (CASE) tools for adding formally supported checking, transformation and generation facilities.

show abstract

“…In the work of [26], the functionality specification of a transition is specified in terms of a design as a pair of pre-/postconditions, and an integrated specification of method m is defined as disjunction of the functionality specifications of all transitions that may react to the invocation of m. The approach integrates state machines with classes and gives complete behavior definitions for the methods. The work of [13] provides full model and code generation for the approach.…”

Section: S_3 Waitqueuementioning

confidence: 99%

Automated transformations from UML behavior models to contracts

Liu

et al. 2014

Sci. China Inf. Sci.

Self Cite

View full text Add to dashboard Cite

In model driven architecture (MDA), system requirements are first captured by UML (unified modeling language) use cases with sequence diagrams to describe their intended use and implemented by classes of objected-oriented languages in the subsequent design stages. It is important that the dynamic behavior specified by the sequence diagrams is in full compliance with the implementation classes. This paper proposes an automatic approach and tool support for generating class contracts, which define a precondition and a postcondition for each operation of the class. The former serves as a guard to ensure invocations of the operations respect the semantics introduced by the sequence diagrams, and the latter places the system in a legal state to facilitate the succeeding operation calls. The contracts can be easily mapped to code of an object-oriented language such as Java. Thus, the approach helps to bridge the gap between the requirements and design stages of system development process. We use our model transformation tool to first generate a UML protocol state machine from the sequence diagrams, and then derive the contracts for a controller class. The transformations take into account the concurrency and critical constructs of the respective UML diagrams.

show abstract

Separation of Concerns and Consistent Integration in Requirements Modelling

Cited by 18 publications

References 8 publications

A Refinement Driven Component-Based Design

A Refinement Driven Component-Based Design

Refinement and verification in component-based model-driven design

Automated transformations from UML behavior models to contracts

Contact Info

Product

Resources

About