Sciweavers

287 search results - page 28 / 58
» Automated abstraction of class diagrams
Sort
View
IWPC
2009
IEEE
14 years 2 months ago
Automatically identifying changes that impact code-to-design traceability
An approach is presented that automatically determines if a given source code change impacts the design (i.e., UML class diagram) of the system. This allows code-to-design traceab...
Maen Hammad, Michael L. Collard, Jonathan I. Malet...
FASE
2001
Springer
14 years 1 days ago
A Hoare Calculus for Verifying Java Realizations of OCL-Constrained Design Models
Abstract. The Object Constraint Language OCL offers a formal notation for constraining the modelling elements occurring in UML diagrams. In this paper we apply OCL for developing ...
Bernhard Reus, Martin Wirsing, Rolf Hennicker
CORR
1999
Springer
110views Education» more  CORR 1999»
13 years 7 months ago
Managing Object-Oriented Integration and Regression Testing
Abstract: Systematic testing of object-oriented software turned out to be much more complex than testing conventional software. Especially the highly incremental and iterative deve...
Mario Winter
CBSE
2004
Springer
14 years 29 days ago
Classifying Software Component Interoperability Errors to Support Component Adaption
Abstract. This paper discusses various classifications of component interoperability errors.These classifications aim at supporting the automation of component adaptation. The us...
Steffen Becker, Sven Overhage, Ralf Reussner
UML
2005
Springer
14 years 1 months ago
Specifying Precise Use Cases with Use Case Charts
Use cases are a popular method for capturing and structuring software requirements. The informality of use cases is both a blessing and a curse. It enables easy application and lea...
Jon Whittle