JSEA  Vol.2 No.3 , October 2009
An Exploratory Case Study in Designing and Implementing Tight Versus Loose Frameworks
Abstract: Frameworks provide large scale reuse by providing skeleton structure of similar applications. But the generality, that a framework may have, makes it fairly complex, hard to understand and thus to reuse. Frameworks have been classified according to many criteria. This paper proposes two types of framework (based on the concept of ‘generality’) named as: tight framework and loose framework. A case study is done by developing loose and tight frameworks for the appli-cation sets of Environment for Unit testing (EUT) domain. Based on the experience that we got by during this case study, we tried to find out the benefits of one (tight or loose) framework over the other. This work attempts to provide an initial background for meaningful studies related to the concept of ‘Design and Development of Framework’.
Cite this paper: nullM. GUPTA, R. GUPTA and A. TRIPATHI, "An Exploratory Case Study in Designing and Implementing Tight Versus Loose Frameworks," Journal of Software Engineering and Applications, Vol. 2 No. 3, 2009, pp. 209-220. doi: 10.4236/jsea.2009.23029.

[1]   D. Roberts and R. Johnson, “Evolving frameworks: A pattern language for developing object-oriented frameworks,” in Pat-tern Languages of Program Design 3. Addison-Wesley, Illinois, USA, 1997.

[2]   J. Bosch, P. Molin, M. Mattsson, and P. Bengtsson, Ob-ject-Oriented Frameworks – Problems & Experiences, 1997.

[3]   S. Sparks, K. Benner, C. Faris, and S. Consulting, “Managing object-oriented framework reuse,” IEEE 1996, pp. 52–61, 1996.

[4]   Y. J. Yang, S. Y. Kim, G. J. Choi, E. S. Cho, C. J. Kim, and S. D. Kim, “A UML-based object-oriented framework develop-ment methodology,” Software Engineering Conference, Pro-ceedings. 1998 Asia Pacific, pp. 211–218, 1998.

[5]   IBM, “Building Object-Oriented Frameworks”, http: //

[6]   D. C. Schmidt, “Applying design patterns and frameworks to develop object-oriented communication software,” Handbook of Programming Languages, Volume I, edited by Peter Salus, MacMillan Computer Publishing, 1997.

[7]   M. E. Fayad and D. S. Hamu “Object-oriented enterprise frameworks: Make vs. buy decisions and guidelines for selec-tion,” The Communications of ACM, 1997.

[8]   A. K. Tripathi and M. Gupta, “Risk analysis in reuse-oriented software development,” International Journal of Information Technology and Management, Vol. 5, No. 1, pp. 52–65, 2006.

[9]   P. Jalote, “An integrated approach to software engineering,” ISBN 81-7319-702-4, Narosa. 2005.