Structured analysis and object-oriented design are compatible

ABSTRACT

Some form or other of object-oriented design has become common, even standard, for the design of Ada programs. Some form or other of structured analysis is and has long been standard for the specification of software requirements. Recent discussions in the software development community advocate object-oriented analysis as being preferable to structured analysis, especially for Ada software development; such discussions further assert that structured analysis and object-oriented design are incompatible. Others have argued for the effectiveness of combined use of the two methods. The topic has become controversial.It is the thesis of this paper that structured analysis is a desirable way to specify software requirements, and that structured analysis and object-oriented design are compatible and work effectively together.

REFERENCES

• 1: S. C. Bailin, An object-oriented requirements specifications method, Communications of the ACM, v.32 n.5, p.608-623, May 1989 [doi>10.1145/63485.63491]
• 2: BLA90 Blanchard, B. S., and W. J. Fabrycky, Systems Engineering and Analysis, 2nd Edition, Prentice Hall, Englewood Cliffs, New Jersey, 1990.
• 3: G Booch, Object-oriented development, IEEE Transactions on Software Engineering, v.12 n.2, p.211-221, Feb. 1986
• 4: A. L. Brintzenhoff , K. Nielsen , K. Shumate, C2P Ada shadow program: design, prototype development and implementation of command and control software, Proceedings of the Ada-Europe international conference on Ada : experiences and prospects: experiences and prospects, p.56-67, January 1990, Dublin, Ireland
• 5: Peter Pin-Shan Chen, The entity-relationship model—toward a unified view of data, ACM Transactions on Database Systems (TODS), v.1 n.1, p.9-36, March 1976 [doi>10.1145/320434.320440]
• 6: Peter Coad , Edward Yourdon, Object-oriented analysis, Yourdon Press, Upper Saddle River, NJ, 1990
• 7: Alan M. Davis, Software requirements: analysis and specification, Prentice Hall Press, Upper Saddle River, NJ, 1990
• 8: DOA79 Department of the Army, System Engineering, FM 770-78, Washington, D.C., April 1979.
• 9: DSM86 Defense Systems Management College, Systems Engineering Management Guide, Fort Belvoir, Virginia, October 1986.
• 10: ESA89 European Space Agency (ESA), HOOD User Manual, Issue 3.0, WME/89-353/JB, ESA Research and Technology Centre, Noordwijk, The Netherlands.
• 11: H. Gomaa, A software design method for real-time systems, Communications of the ACM, v.27 n.9, p.938-949, Sept. 1984 [doi>10.1145/358234.358262]
• 12: Hassan Gomaa, A software design method for Ada based real time systems, Proceedings of the sixth Washington Ada symposium on Ada, p.273-284, July 1989, McLean, Virginia, United States [doi>10.1145/326490.326592]
• 13: Lewis Gray, Transitioning from structured analysis to object-oriented design, Proceedings of the fifth Washington Ada symposium on Ada, p.151-162, July 1988, Tyson's Corner, Virginia, United States [doi>10.1145/339938.339987]
• 14: Derek J. Hatley , Imtiaz A. Pirbhai, Strategies for real-time system specification, Dorset House Publishing Co., Inc., New York, NY, 1987
• 15: HEI90 Heitz, Maurice., "Practical Issues of Using HOOD," Ada UK Tutorials, Ada UK International Conference, Brighton, England, 23 October 1990.
• 16: KEN88 Kennedy, Allan and Colin Carter, "Real Time Structured Analysis and Ada -- A Pragmatic Object-Oriented Approach," Ada User, December 1988.
• 17: KRE90 Krell, Bruce E., "Ada Software Development Methodology with Case Study," Tutorials of Tri-Ada 1990, Tri-Ada Conference, Baltimore, Maryland, December 3-7, 1990.
• 18: Stephen M. McMenamin , John F. Palmer, Essential systems analysis, Yourdon Press, Upper Saddle River, NJ, 1984
• 19: Kjell Nielsen , Ken Shumate, Designing large real-time systems with Ada, McGraw-Hill, Inc., New York, NY, 1988
• 20: D. L. Parnas, A technique for software module specification with examples, Communications of the ACM, v.15 n.5, p.330-336, May 1972 [doi>10.1145/355602.361309]
• 21: D. L. Parnas, On the criteria to be used in decomposing systems into modules, Communications of the ACM, v.15 n.12, p.1053-1058, Dec. 1972 [doi>10.1145/361598.361623]
• 22: D. L. Parnas , P. C. Clements , D. M. Weiss, Enhancing reusability with information hiding, Software reusability: vol. 1, concepts and models, ACM, New York, NY, 1989 [doi>10.1145/73103.73109]
• 23: David L. Parnas , A. John van Schouwen , Shu Po Kwan, Evaluation of safety-critical software, Communications of the ACM, v.33 n.6, p.636-648, June 1990 [doi>10.1145/78973.78974]
• 24: Ed Seidewitz , Mike Stark, Toward a general object-oriented software development methodology, ACM SIGAda Ada Letters, v.VII n.4, p.54-67, July/Aug. 1987 [doi>10.1145/25314.25315]
• 25: Ken Shumate, Layered virtual machine/object-oriented design, Proceedings of the fifth Washington Ada symposium on Ada, p.177-190, July 1988, Tyson's Corner, Virginia, United States [doi>10.1145/339938.339991]
• 26: SHU90 Shumate, Ken, "Software Specification and Design: Structured Analysis, Object-Oriented Design and the Transition," Addendum to Tutorials of Tri-Ada 1990 -- Software Specification and Design in Ada, Tri-Ada Conference, Baltimore, Maryland, December 3-7, 1990. (Copies available from the author.).
• 27: Paul T. Ward, How to Integrate Object Orientation with Structured Analysis and Design, IEEE Software, v.6 n.2, p.74-82, March 1989 [doi>10.1109/52.23134]

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.10 Design**
            Subjects: Representation**
  D.3 PROGRAMMING LANGUAGES
      D.3.2 Language Classifications

          Nouns: Ada

  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.3 Software Management
          Subjects: Software development

General Terms:
Design, Theory, Verification