A STATE OF THE ART REPORT: SOFTWARE DESIGN METHODS

ion is a means of describing a program function, at an appropriate level of detail. At the highest level of abstraction a solution is stated in the language of the problem environment (requirements analysis). At the lowest level of abstraction, implementation-oriented terminology is used (programming). An abstraction can be compared to a model which incorporates detail only to the extent needed to fulfill its purpose. 2.1.3. Software Architecture While refinement is about the level of detail, architecture is about structure. The architecture of the procedural and data elements of a design represents a software solution for the real-world problem defined by the requirements analysis. It is unlikely that there will be one obvious candidate architecture. 2.1.4. Program Structure The program structure represents the hierarchy of control. Program structure is usually expressed as a simple hierarchy showing super-ordinate and subordinate relationships of modules. 2.1.5. Data Structure Data structure represents the organization, access method, associativity, and processing alternatives for problem-related information. Classic data structures include scalar, sequential, linked-list, n-dimensional, and hierarchical. Data structure, along with program structure, makes up the software architecture.

[1]  W. W. Royce,et al.  Managing the development of large software systems: concepts and techniques , 1987, ICSE '87.

[2]  William W. Agresti,et al.  New Paradigms for Software Development , 1986 .

[3]  Glenford J. Myers,et al.  Composite/structured design , 1978 .

[4]  Daniel H. Fishman.  Object-Oriented Information Systems in the 21st Century , 1997, OOIS.

[5]  Henk Sol,et al.  Information Systems Design Methodologies: A Feature Analysis , 1983 .

[6]  Dallas E. Webster.  Mapping the design information representation terrain , 1988, Computer.

[7]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[8]  Stephen H. Caine,et al.  PDL A tool for software design , 1899 .

[9]  Edward Yourdon,et al.  Object-oriented design , 1991, Yourdon Press Computing Series.

[10]  Douglas T. Ross,et al.  Structured Analysis for Requirements Definition , 1977, IEEE Transactions on Software Engineering.

[11]  Peter A. Ng,et al.  Diagramming techniques in case , 1989 .

[12]  Michael Dyer.  The Cleanroom Approach to Quality Software Development , 1992, Int. CMG Conference.

[13]  Raymond T. Yeh,et al.  An alternative paradigm for software evolution , 1989 .

[14]  James F. Stay.  HIPO and Integrated Program Design , 1976, IBM Syst. J..

[15]  Paul G. Sorenson,et al.  Structured systems analysis using SPSL/SPSA , 1985, Inf. Manag..

[16]  Harlan D. Mills,et al.  Structured programming - theory and practice , 1979, The systems programming series.

[17]  Paul D. Bailor,et al.  Educating knowledge-based software engineers , 1992, Proceedings of the Seventh Knowledge-Based Software Engineering Conference.

[18]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[19]  Laszlo A. Belady.  Leonardo: the MCC software research project , 1989 .

[20]  Lawrence Markosian,et al.  Knowledge-based software engineering using refine , 1989 .

[21]  Robert Balzer,et al.  Operational specification as the basis for rapid prototyping , 1982 .

[22]  David R. Harris,et al.  KBRA: A new paradigm for requirements engineering , 1988, IEEE Expert.

[23]  William H. Roetzheim.  Structured design using HIPO-II , 1990 .

[24]  Wayne P. Stevens.  Software design - concepts and methods , 1991, Practical software engineering series.

[25]  Robert Balzer,et al.  Report on a knowledge-based software assistant , 1986 .

[26]  Michael E. Fagan.  Design and Code Inspections to Reduce Errors in Program Development , 1976, IBM Syst. J..

[27]  Michael Jackson,et al.  Principles of program design , 1975 .

[28]  Tom DeMarco,et al.  Structured Analysis and System Specification , 1978 .

[29]  David W. Payton,et al.  Intelligent real-time control of robotic vehicles , 1991, CACM.

[30]  Antoni Olivé.  Analysis of Conceptual and Logical Models in Information Systems Design Methodologies , 1983, CRIS.

[31]  James Martin,et al.  Diagramming techniques for analysts and programmers , 1984 .

[32]  Grady Booch.  On the concepts of object-oriented design , 1989 .

[33]  Pieter R. Mimno.  Survey of case tools , 1989 .

[34]  T. T. Carey,et al.  Information system prototyping: techniques, tools, and methodologies , 1983 .

[35]  Pankaj Jalote,et al.  An Integrated Approach to Software Engineering , 1991, Springer Compass International.

[36]  Anthony I. Wasserman.  Information system design methodology , 1980, J. Am. Soc. Inf. Sci..