ABSTRACT
We were motivated to undertake the research we describe here by a conversation with two practicing software engineers, who described a dilemma they faced at work. They worked for small company that earned revenues by delivering to a large customer a stream of enhancements to a software tool. The engineers' jobs were to estimate the time to make enhancements and to implement selected enhancements. They were good at estimating, but dissatisfied with the system design, believing that it significantly slowed new feature implementation. They had proposed to management to restructure the tool. However, the management, concerned about disrupting the flow of enhancements thus revenues, and having no clear model of likely benefits, declined. The engineers believed that refactoring would increase the velocity of feature delivery, but they had no sense or ability to analyze the situation quantitatively or to frame it in a way that was compelling to business decision-makers. As a result, the engineers were dissatisfied, and the company incurred a possibly significant opportunity cost.
- C. W. Alexander. Notes on the Synthesis of Form. Harvard University Press, 1970.Google Scholar
- W. Ashby. Design for a Brain. John Wiley and Sons, 1952.Google Scholar
- C. Y. Baldwin and K. B. Clark. Design Rules, Vol. 1: The Power of Modularity. The MIT Press, 2000. Google ScholarDigital Library
- F. Brooks. No silver bullet: Essence and accidents of software engineering. IEEE Computer, 20(4):10--19, Apr. 1987. Google ScholarDigital Library
- Y. Cai and K. Sullivan. A value-oriented theory of structure in design, viewed as decision-making activity. In Submitted for publication to ESEC/FSE 05, 2005.Google Scholar
- E. W. Dijkstra. On the role of scientific thought. In Selected Writings on Computing: A Personal Perspective, pages 60--66, Springer-Verlag, 1982.Google ScholarDigital Library
- S. D. Eppinger, Model-based approaches to managing concurrent engineering. Journal of Engineering Design, 2(4):283--290, 1991.Google ScholarCross Ref
- J. M. Favor, K. R. Favor, and P. F. Favor. Value based software reuse investment. In Annals of Software Engineering 5, pages 5--52, 15May 1998. Google ScholarDigital Library
- D. Jackson. Micromodels of software: Lightweight modeling and analysis with alloy. Feb. 2002.Google Scholar
- C. V. Lopes and S. K. Bajracharya. An analysis of modularity in aspect oriented design. 2005.Google Scholar
- D. L. Parnas. On the criteria to be used in decomposing systems into modules. Communications of the ACM, 15(12):1053--8, Dec. 1972. Google ScholarDigital Library
- H. A. Simon. The Sciences of the Artificial. The MIT Press, third edition, 1996. Google ScholarDigital Library
- M. Spivey. The fuzz manual. URL: http://spivey.oriel.ox.ac.uk/~mike/fuzz/.Google Scholar
- W. P. Stevens, G. J. Myers, and L. L. Constantine. Structured design. IBM Systems Journal, 13(2):115--39, 1974.Google ScholarDigital Library
- K. Sullivan, Y. Cai, B. Hallen, and W. G. Griswold. The structure and value of modularity in software design. SIGSOFT Software Engineering Notes, 26(5):99--108, Sept. 2001. Google ScholarDigital Library
- K. J. Sullivan, I. J. Kalet, and D. Notkin. Software design: The options approach. In 2nd International Software Architecture Workshop, Joint Proceedings of the SIGSOFT '96 Workshops, San Francisco, CA, October, 1996., pages 15--18, Aug. 1996. Google ScholarDigital Library
- K. J. Sullivan and J. C. Knight. Building programs from massive components. In Proceedings of the 21st Annual Software Engineering Workshop, Greenbelt, MD, 4-5 Dec. 1996. IEEE.Google Scholar
- A. A. Yassine. An introduction to modeling and analyzing complex product development processes using the design structure matrix (dsm) method. 2004.Google Scholar
Index Terms
- A value-oriented theory of modularity in design
Recommendations
A value-oriented theory of modularity in design
We were motivated to undertake the research we describe here by a conversation with two practicing software engineers, who described a dilemma they faced at work. They worked for small company that earned revenues by delivering to a large customer a ...
The Strategic Value of High-Cost Customers
Many firms today manage their existing customers differentially based on profit potential, providing fewer incentives to less profitable customers and firing unprofitable customers. Although researchers and industry experts advocate this practice, ...
The Retail Value Chain: Linking Employee Perceptions to Employee Performance, Customer Evaluations, and Store Performance
The authors test a value chain model entailing a progression of influence from retail employee job perceptions → retail employee job performances → customer evaluations → customer spending and comparable store sales growth. The authors test the model ...
Comments