ACM Home Page
Please provide us with feedback. Feedback
Sotware modularization using requirements attributes
Full text PdfPdf (396 KB)
Source ACM Southeast Regional Conference archive
Proceedings of the 42nd annual Southeast regional conference table of contents
Huntsville, Alabama
SESSION: Software engineering #1 table of contents
Pages: 104 - 109  
Year of Publication: 2004
ISBN:1-58113-870-9
Authors
Turky N. Al-Otaiby  Florida Institute of Technology, Melbourne, Florida
Walter P. Bond  Florida Institute of Technology, Melbourne, Florida
Mohsen AlSherif  Florida Institute of Technology, Melbourne, Florida
Sponsor
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 6,   Downloads (12 Months): 43,   Citation Count: 2
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues   peer to peer  

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

ABSTRACT

Due to the increasing complexity of today's software applications, design methodologies are of great concern to the software community. The design phase of the software lifecycle is a major factor to the success of a software system. Some studies have shown that the majority of errors detected during the testing phase are related to design. Therefore, it is very critical to assess the quality of the design. The correct top-level modularization of the software is critical to the design quality.Software modularity is not a new concept in the software engineering field; it has been a design issue since the earliest days of software development. Because the software designer cannot be expected to conceptualize a complex software application as a whole, it is usual to create a top-level design which has been decomposed into a set of modules. The degree of modularization is a subjective concept that is difficult to measure; however, coupling and cohesion are two well-known concepts that are used to characterize software modularization.In this paper we will illustrate how requirements scenarios can be clustered based on attributes identified in the scenarios. The technique uses heuristic clustering methods that cluster scenarios so that those scenarios within a cluster have a strong functional relationship with one another and weak relationships to the scenarios in other clusters. Hence, cohesion within clusters is maximized while coupling between clusters is minimized. Consequently, software modularization based on these clusters should provide a good initial design.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
 
3
 
4
 
5
 
6
 
7
 
8
Nico Lassing; Daan Rijsenbrij; and Hans Vliet. Using UML in Architecture-Level Modifiability Analysis. 2001.
 
9
10
 
11
Alexander, C. (1964). Notes on the synthesis of form, Harvard Press 1964.
 
12
 
13
 
14


Collaborative Colleagues:
Turky N. Al-Otaiby: colleagues
Walter P. Bond: colleagues
Mohsen AlSherif: colleagues

Peer to Peer - Readers of this Article have also read: