Managing domain-specific, product-line development

Macala, R.R.; Stuckey, Lynn D.; Gross, David C.

doi:10.1109/52.493021

Cited by 63 publications

(30 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…DSSA are central to domainspecific reuse, in that they provide a framework for creating assets and constructing systems within a domain. Domain engineering also allows for product-line development, which seeks to achieve reuse across a family of systems [20] [21]. Federated database management systems can be regarded as such a family of systems.…”

Section: Software Product Families and Their Architecturesmentioning

confidence: 99%

Formalization of Federated Schema Architectural Style Variability

Hasselbring¹

2015

JSEA

View full text Add to dashboard Cite

Data integration requires managing heterogeneous schema information. A federated database system integrates heterogeneous, autonomous database systems on the schema level, whereby both local applications and global applications accessing multiple component database systems are supported. Such a federated database system is a complex system of systems which requires a well-designed organization at the system and software architecture level. A specific challenge that federated database systems face is the organization of schemas into a schema architecture. This paper provides a detailed, formal investigation of variability in the family of schema architectures, which are central components in the architecture of federated database systems. It is shown how the variability of specific architectures can be compared to the reference architecture and to each other. To achieve this, we combine the semi-formal object-oriented modeling language UML with the formal object-oriented specification language Object-Z. Appropriate use of inheritance in the formal specification, as enabled by Object-Z, greatly supports specifying and analyzing the variability among the studied schema architectures. The investigation also serves to illustrate the employed specification techniques for analyzing and comparing software architecture specifications.

show abstract

Section: Software Product Families and Their Architecturesmentioning

confidence: 99%

Formalization of Federated Schema Architectural Style Variability

Hasselbring¹

2015

JSEA

View full text Add to dashboard Cite

show abstract

“…describe SPL solutions. The notion of software product line engineering became well established [18], after Parnas' prescient proposal [22] in the 70's.…”

Section: Introductionmentioning

confidence: 99%

Towards a Method for Rigorous Development of Generic Requirements Patterns

Snook

Poppleton

Johnson³

2006

Rigorous Development of Complex Fault-Tolerant Systems

View full text Add to dashboard Cite

Abstract. We present work in progress 3 on a method for the engineering, validation and verification of generic requirements using domain engineering and formal methods. The need to develop a generic requirement set for subsequent system instantiation is complicated by the addition of the high levels of verification demanded by safety-critical domains such as avionics. Our chosen application domain is the failure detection and management function for engine control systems: here generic requirements drive a software product line of target systems. A pilot formal specification and design exercise is undertaken on a small (twosensor) system element. This exercise has a number of aims: to support the domain analysis, to gain a view of appropriate design abstractions, for a B novice to gain experience in the B method and tools, and to evaluate the usability and utility of that method. We also present a prototype method for the production and verification of a generic requirement set in our UML-based formal notation, UML-B, and tooling developed in support. The formal verification both of the structural generic requirement set, and of a particular application, is achieved via translation to the formal specification language, B, using our U2B and ProB tools.

show abstract

“…The notion of software product line (also known as system family) engineering became well established [29], after Parnas' proposal [35] in the 70's of information hiding and modularization as techniques that would support the handling of program families. Product line engineering arises where multiple variants of essentially the same software system are required, to meet a variety of platform, functional, or other requirements.…”

Section: Introductionmentioning

confidence: 99%

Rigorous engineering of product-line requirements: A case study in failure management

Snook

Poppleton

Johnson³

2008

Information and Software Technology

View full text Add to dashboard Cite

We consider the failure detection and management function for engine control systems as an application domain where product line engineering is indicated. The need to develop a generic requirement set -for subsequent system instantiation -is complicated by the addition of the high levels of verification demanded by this safety-critical domain, subject to avionics industry standards. We present our case study experience in this area as a candidate method for the engineering, validation and verification of generic requirements using domain engineering and Formal Methods techniques and tools. For a defined class of systems, the case study produces a generic requirement set in UML and an example system instance. Domain analysis and engineering produce a validated model which is integrated with the formal specification/ verification method B by the use of our UML-B profile. The formal verification both of the generic requirement set, and of a simple system instance, is demonstrated using our U2B, ProB and prototype Requirements Manager tools. This work is a demonstrator for a tool-supported method which will be an output of EU project RODIN 1 . The use of existing and prototype formal verification and support tools is discussed. The method, developed in application to this novel combination of product line, failure management and safety-critical engineering, is evaluated and considered to be applicable to a wide range of domains.

show abstract

Managing domain-specific, product-line development

Cited by 63 publications

References 3 publications

Formalization of Federated Schema Architectural Style Variability

Formalization of Federated Schema Architectural Style Variability

Towards a Method for Rigorous Development of Generic Requirements Patterns

Rigorous engineering of product-line requirements: A case study in failure management

Contact Info

Product

Resources

About