Sciweavers

504 search results - page 64 / 101
» Automatically documenting program changes
Sort
View
UML
2001
Springer
15 years 2 months ago
Catalytic Modeling: UML meets XP
: I have always been a strong believer and practitioner of the JFDI approach to development, which yields high morale, early identification of problems in design and of any misunde...
Alan Wills
DIAGRAMS
2006
Springer
15 years 1 months ago
Flow Diagrams: Rise and Fall of the First Software Engineering Notation
Drawings of water are the earliest, least abstract forms of flow diagram. Representations of ideal or generalised sequences for manufacturing or actual paths for materials between ...
Stephen J. Morris, O. C. Z. Gotel
KBSE
2009
IEEE
15 years 4 months ago
ReAssert: Suggesting Repairs for Broken Unit Tests
—Developers often change software in ways that cause tests to fail. When this occurs, developers must determine whether failures are caused by errors in the code under test or in...
Brett Daniel, Vilas Jagannath, Danny Dig, Darko Ma...
OOPSLA
2004
Springer
15 years 3 months ago
Transparent proxies for java futures
A proxy object is a surrogate or placeholder that controls access to another target object. Proxies can be used to support distributed programming, lazy or parallel evaluation, ac...
Polyvios Pratikakis, Jaime Spacco, Michael W. Hick...
SAC
2003
ACM
15 years 3 months ago
Validation of Code-Improving Transformations for Embedded Systems
Programmers of embedded systems often develop software in assembly code due to inadequate support from compilers and the need to meet critical speed and/or space constraints. Many...
Robert van Engelen, David B. Whalley, Xin Yuan