ACM Home Page
Please provide us with feedback. Feedback
Digital Library logoTake a look at the new version of this page: [ beta version ]. Tell us what you think.
Managing software design complexity: facade vs role-based design
Full text PdfPdf (277 KB)
Source
ACM SIGSOFT Software Engineering Notes archive
Volume 34 ,  Issue 1  (January 2009) table of contents
SECTION: Article abstracts with full text online table of contents
Pages: 1-4  
Year of Publication: 2009
ISSN:0163-5948
Author
R. K. Pandey  University Institute of Computer Science and Applications (UICSA) R. D. University, Jabalpur (M.P.) India
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 8,   Downloads (12 Months): 169,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1457516.1457526
What is a DOI?

ABSTRACT

Good software design practice calls for minimizing coupling and maximizing cohesiveness. The use of roles in CBSE has been shown to help in achieving the abovementioned design goal. The idea of role-based component design is that the public interface is split into smaller interfaces that model the different roles a component can take in a system. In addition, we have the design pattern facade which is just opposite to what role-based design philosophy advocates. Yet both design approaches claim to reduce the overall complexity of the system. In this paper we make an investigation into these two design approaches in order to understand how these two contradictory design principles can help the designer in managing complexity.