Searching for authors named "Alexander Egyed" – sorted by Relevance.
-
Dynamic Deployment of Executing and Simulating Software Components
- Physical boundaries have caused software systems to become less monolithic and more distributed. The trend is progressing to a point where software systems will consist of numerous, loosely-coupled, heterogeneous software components. Increased software dynamism will allow these components to be
- Cited by 2 (0 self) – Add To MetaCart
-
Reasoning about Trace Dependencies in a Multi-Dimensional Space
- this paper, we assume the source code to be the commonality between model elements and we assume that scenarios exist that can be tested on its compiled code -- the system. While testing a scenario on a system, it can then be observed what implementation classes, methods, and lines of code it uses.
- Cited by 2 (0 self) – Add To MetaCart
-
Compositional and Relational Reasoning During Class Abstraction
- Class diagrams are among the most widely used object-oriented design techniques. They are effective in modeling the structure of software systems at any stages of the software life cycle. Still, class diagrams can become as complex and overwhelming as the software systems they describe. This pape
- Cited by 3 (0 self) – Add To MetaCart
-
Validating Consistency between Architecture and Design Descriptions
- rgo router, called Port and Warehouse. aPort availableGoods aSurplus aWarehouse aPort availableGoods aWarehouse Port Warehouse aPort aWarehouse abc bc a D #r...f...r#h#v' Srhyv"h#v' D #r...f...r#h#v' Design Architecture Figure 1. Consistency Checking between Architecture and Design Elem
- Cited by 1 (0 self) – Add To MetaCart
-
Semantic Abstraction Rules for Class Diagrams
- When dealing with object-oriented models like class and object diagrams, designers easily get overwhelmed by large amounts of model elements and their interdependencies. To deal with the complexities of large-scale software models, this paper presents rules and methods for automated abstraction. Ou
- Cited by 4 (2 self) – Add To MetaCart
-
Determining the Cost-Quality Trade-Off for Automated Software Traceability
- Major software development standards mandate the establishment of trace links among software artifacts such as requirements, architectural elements, or source code without explicitly stating the required level of detail of these links. However, the level of detail vastly affects the cost and quality
- Cited by 3 (2 self) – Add To MetaCart
-
Scalable Consistency Checking between Diagrams - The VIEWINTEGRA Approach
- The Unified Modeling Language (UML) supports a wide range of diagrams for modeling software development concerns. UML diagrams are independent but connected; their meta-model describes them under a common roof. Despite the advances of UML, we found that the problem of ensuring consistency between UM
- Cited by 30 (1 self) – Add To MetaCart
-
Instant Consistency Checking for the UML
- 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
- Cited by 17 (1 self) – Add To MetaCart
-
A Scenario-Driven Approach to Traceability
- Design traceability has been widely recognized as being an integral aspect of software development. In the past years this fact has been amplified due to the increased use of legacy systems and COTS (commercial-off-the-shelf) components mixed with the growing use of elaborate "upstream" software mod
- Cited by 27 (3 self) – Add To MetaCart
-
Java Beans - the only component architecture for Java?
- > Alexander Egyed, 4/15/99, 6 Alexander Egyed, 4/15/99, 6 Java Java . Object-Oriented . Portable . Network Aware . Common Interfaces but ... . (Graphical) Component Assembly versus Usage . Persistence . Component Interaction (e.g. two applets/applications) 4 USC - Center for Software Engineeri
- Add To MetaCart

