Sciweavers

1925 search results - page 153 / 385
» Documenting software systems with views
Sort
View
IWPC
2009
IEEE
16 years 27 days 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...
IWPSE
2007
IEEE
16 years 16 days ago
Talking tests: an empirical assessment of the role of fit acceptance tests in clarifying requirements
The starting point for software evolution is usually a change request, expressing the new or updated requirements on the delivered system. The requirements specified in a change ...
Filippo Ricca, Marco Torchiano, Mariano Ceccato, P...
ICSM
2007
IEEE
16 years 17 days ago
Design recovery and maintenance of build systems
The build system forms an indispensable part of any software project. It needs to evolve in parallel with the source code in order to build, test and install the software. Unfortu...
Bram Adams, Herman Tromp, Kris De Schutter, Wolfga...
IWPC
2003
IEEE
15 years 11 months ago
Scaling an Object-Oriented System Execution Visualizer through Sampling
Increasingly, applications are being built by combining existing software components. For the most part, a software developer can treat components as black-boxes. However, for som...
Andrew Chan, Reid Holmes, Gail C. Murphy, Annie T....
OOIS
1994
Springer
15 years 10 months ago
Problems, Descriptions and Objects
The business of software development is solving problems. Following Polya, we can increase our ability to solve problems by focusing directly on problems themselves, on their part...
Michael Jackson