Scaling step-wise refinement

Batory, Don; Sarvela, Jacob Neal; Rauschmayer, Axel

doi:10.1109/icse.2003.1201199

Cited by 325 publications

(633 citation statements)

References 19 publications

Supporting

Mentioning

625

Contrasting

Unclassified

Order By: Relevance

“…The application of refinement approaches to PLE to date has been modest, e.g. [6,30], and has, in our view, much potential. An obvious unit for modelling variabilities is the feature.…”

Section: Resultsmentioning

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 application of refinement approaches to PLE to date has been modest, e.g. [6,30], and has, in our view, much potential. An obvious unit for modelling variabilities is the feature.…”

Section: Resultsmentioning

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

show abstract

“…AHEAD Tool Suite is a set of stand alone and language-extensible tools [3] which implement Feature Oriented Programming (FOP), a technology that studies feature modularity in program synthesis for product lines [13]. We performed our study in the AspectJ implementation of five core tools of ATS [30].…”

Section: Case Studiesmentioning

confidence: 99%

Measuring and Characterizing Crosscutting in Aspect-Based Programs: Basic Metrics and Case Studies

Lopez-Herrejon

Apel

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

Abstract. Aspects are defined as well-modularized crosscutting concerns. Despite being a core tenet of Aspect Oriented Programming, little research has been done in characterizing and measuring crosscutting concerns. Some of the issues that have not been fully explored are: What kinds of crosscutting concerns exist? What language constructs do they use? And what is the impact of crosscutting in actual Aspect Oriented programs? In this paper we present basic code metrics that categorize crosscutting according to the number of classes crosscut and the language constructs used. We applied the metrics to four non-trivial open source programs implemented in AspectJ. We found that for these systems, the number of classes crosscut by advice per crosscutting is small in relation to the number of classes in the program. We argue why we believe this result is not atypical for Aspect Oriented programs and draw a relation to other non-AOP techniques that provide crosscutting.

show abstract

“…Briefly we describe the key implementation techniques that are based on reflective engineering [12]. Reflective engineering includes a variety of techniques -Meta Programming, Table Driven Programming, Generative Programming [3], Aspect Oriented Software Development [12], Multi Dimensions of Concern [12] and Feature Oriented Programming [18]. Each if these approaches programmatically compose code fragments to produce the resulting program instance.…”

Section: Reflective Engineering For Building Domain Classesmentioning

confidence: 99%

“…We argue that there is an intrinsic difference between technology frameworks and product lines and business frameworks. This difference means that business frameworks need to be constructed with a reflective engineering [12] [3] [18] approach rather than by using concrete classes and classical analysis.…”

Section: Business Classes -A Little Reflectionmentioning

confidence: 99%

The Elusive Search for Business Frameworks.

Thomas¹

2004

JOT

View full text Add to dashboard Cite

Scaling step-wise refinement

Cited by 325 publications

References 19 publications

Towards a Method for Rigorous Development of Generic Requirements Patterns

Towards a Method for Rigorous Development of Generic Requirements Patterns

Measuring and Characterizing Crosscutting in Aspect-Based Programs: Basic Metrics and Case Studies

The Elusive Search for Business Frameworks.

Contact Info

Product

Resources

About