Sciweavers

184 search results - page 21 / 37
» Software Requirements Negotiation: Some Lessons Learned
Sort
View
IWPC
1998
IEEE
13 years 11 months ago
Rapid System Understanding: Two COBOL Case Studies
Rapid system understanding is required in the planning, feasibility assessment and cost estimating phases of a system renovation project. In this paper, we apply a number of analy...
Arie van Deursen, Tobias Kuipers
ICSE
1999
IEEE-ACM
13 years 11 months ago
Exploiting ADLs to Specify Architectural Styles Induced by Middleware Infrastructures
Architecture Definition Languages (ADLs) enable the formalization of the architecture of software systems and the execution of preliminary analyses on them. These analyses aim at...
Elisabetta Di Nitto, David S. Rosenblum
SEKE
1993
Springer
13 years 11 months ago
Recovering Conceptual Data Models is Human-Intensive
1 To handle the complexity of modern software systems, a software comprehension strategy pointing out the al abstraction level is necessary. In this context, the role of technology...
Fabio Abbattista, Filippo Lanubile, Giuseppe Visag...
ISESE
2006
IEEE
14 years 1 months ago
Using observational pilot studies to test and improve lab packages
Controlled experiments are a key approach to evaluate and evolve our understanding of software engineering technologies. However, defining and running a controlled experiment is a...
Manoel G. Mendonça, Daniela Cruzes, Josemei...
ICSM
1995
IEEE
13 years 11 months ago
Iterative reengineering to compensate for quick-fix maintenance
A typical approach to software maintenance is analyzing just the source code, applying some patches, releasing the new version, and then updating the documentation. This quick-fix...
Filippo Lanubile, Giuseppe Visaggio