Prepared by Michael Corry
for Dr. Javed Mostafa
L597 - Spring 1996
Preece, et al. (1994, p. 712) provide two definitions of software design - 1). the process of developing a product, artefact or system, and 2.) a representation (simulation or model) of the product. With the increasing use of the computer in every day l
ife, much time and money are spent on the design of effective, usable, and efficient software throughout the world.
With the increased emphasis on software design has come an increase in strategies to assist designers in their efforts. Baecker, et al. (1995) define three of these areas - principles, guidelines, and methodologies. Principles are defined as collection
s of statements that advise the designer on how to proceed (e.g., know the user). Guidelines are defined as collections of tests that can be applied to an interface to determine if it is satisfactory (e.g., provide an average response time of less than o
ne second). Methodologies are defined as formalized procedures that are believed to guide and structure the process of effective design when followed in sequence (Baecker, et al., 1995, p.74).
The focus of this paper is to provide a broad overview and taxonomy of software design methodologies. Within this area exists many different methodologies. The emphasis of many of the methodological approaches are different; however, as we will see, th
ere is also a great deal of overlap between methodologies. This paper will be broad in nature and will provide only a brief overview of each methodology. The heart of the paper is a table which provides a comparison of the attributes and focus of severa
l methodologies.
Problem
Selected Methodologies
Guidelines for Selection and Classification of Attributes
Classification/Taxonomy Table
Conclusion
Bibliography
Go to the top of this document
Send mail to
mcorry@gwu.edu
Last Updated on November 10, 1997