(Enter summary)
Abstract: Designers are often unsuccessful in designing for change
using traditional modularity techniques. A complementary
modularity technique called information transparency can
improve a designer's ability to simplify changes by exposing
the interdependence of dispersed program elements that
must be changed together for correctness. Information transparency
represents modules via similarity and architecture,
rather than locality and abstraction. With these, a programmer
can create locality with a... (Update)
Similar documents based on text: More All
0.3: The Structure and Value of Modularity in Software Design - Sullivan, Cai, Hallen.. (2001)
(Correct)
0.1: Designing For Change: A Modeling And Simulation System Approach - Michael Companion Ph
(Correct)
0.0: Tool Support for Planning the Restructuring of.. - Griswold, Chen.. (1998)
(Correct)
Related documents from co-citation: More All
3: the British Computer Society Human-Computer Interaction Specialist Group (Univer.. (context) - Jones, Winder et al. - 1988
2: Software reflexion models: Bridging the gap between source and high-level models
- Murphy, Notkin et al. - 1995
2: Architectural foundations for real-time performance in intelligent agents (context) - Hayes-Roth - 1990
BibTeX entry: (Update)
W.G. Griswold, Coping with Software Change Using Information Transparency, Tech. Report CS98-585, Dept. of Computer Science and Eng., Univ. of California, San Diego, 1998. http://citeseer.ist.psu.edu/griswold98coping.html More
@inproceedings{ griswold99coping,
author = "William G. Griswold",
title = "Coping With Software Change Using Information Transparency",
booktitle = "Proceedings of the ~21st~ International Conference on Software Engineering",
year = "1999",
url = "citeseer.ist.psu.edu/griswold98coping.html" }
Citations (may not include all citations):
756
Aspect-oriented programming
- Kiczales, Lamping et al. - 1997
427
the criteria to be used in decomposing systems into modules (context) - Parnas - 1972
131
The Mythical Man Month: Essays on Software Engineering (context) - Brooks - 1975
117
Software reflexion models: bridging the gap between source a..
- Murphy, Notkin et al. - 1995
82
An intelligent tool for re-engineering software modularity (context) - Schwanke - 1991
32
The concept assignment problem in program understanding (context) - Biggerstaff, Mitbander et al. - 1993
32
ASTLOG: A language for examining abstract syntax trees
- Crew - 1997
26
The modular structure of complex systems
- Parnas, Clements et al. - 1984
25
Tool support for planning the restructuring of data abstract..
- Griswold, Chen et al. - 1996
21
Automated support for encapsulating abstract data types (context) - Bowdidge, Griswold - 1994
21
Lightweight source model extraction
- Murphy, Notkin - 1995
17
Architectural tradeoffs for a meaning-preserving program res.. (context) - Griswold, Notkin - 1995
17
Principles of Programming Languages: Design (context) - MacLennan - 1987
15
Problem decomposition for reuse
- Jackson, Jackson - 1996
13
Decoupling change from design
- VanHilst, Notkin - 1996
9
Conceptual module querying for software reengineering
- Baniassad, Murphy - 1998
5
Why software jewels are rare (context) - Parnas - 1996
3
Open implementation guidelines (context) - Kiczales, Lamping et al. - 1997
3
Development of an unanticipated member of a program family
- Gray - 1997
3
An introduction to the Standard Template Library (context) - Vilot - 1994
3
Design and specification of the minimal subset of an operati.. (context) - Parnas, Handzel et al. - 1976
1
Code Complete: A Practical Guide of Software Construction (context) - McConnell - 1993
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC