Computer-Aided Systems Engineering Methodology Support and Its Effect on the Output of Structured Analysis

The information systems development literature indicates that there is no conclusive, empirical evidence that CASE improves the quality of system specifications or the resulting information systems. One role of a CASE tool is to serve as a methodology companion—to assist an analyst in the creation of documentation passed to succeeding phases of the life cycle, and to guide the analyst through a particular systems development methodology. A framework for comparing the level of methodology support provided by a CASE tool is proposed and applied to 27 structured analysis methodology rules. The framework contains seven levels of rule enforcement, ranging from real-time enforcement of a rule to the absence of enforcement for a rule. The methodology enforcement framework is then applied to two popular, commercial CASE tools. Each CASE tool was used by eight project teams over a two month period to construct a functional specification for a hotel information system. The goal of the study was to examine the influence on the functional specification of the level of methodology support provided by the CASE tool for each structured analysis methodology rule. Methodology errors in the system specification were noted for each structured analysis methodology rule. An analysis of the frequency of errors indicates that internal consistency rules are easily adhered to regardless of the level of methodology support provided by the CASE tool, while hierarchical consistency rules are adhered to more frequently in the presence of rigorous methodology support.

[1]  Edward Yourdon,et al.  Structured design : fundamentals of a discip!ine of computer proqram and system desiqn , 1979 .

[2]  L. Zucconi Selecting a CASE tool , 1989, SOEN.

[3]  Stuart H. Zweben,et al.  Measuring the quality of structured designs , 1981, J. Syst. Softw..

[4]  Gordon C. Everest,et al.  Assessing user experience with CASE tools: an exploratory analysis , 1992, Proceedings of the Twenty-Fifth Hawaii International Conference on System Sciences.

[5]  Mark Gershon,et al.  The Selection of Computer‐Aided Software Engineering Tools: A Multi‐Criteria Decision Making Approach , 1991 .

[6]  P. N. Robillard,et al.  A project-based software course: the myth of the real world , 1988 .

[7]  Chris F. Kemerer,et al.  Now the learning curve affects CASE tool adoption , 1992, IEEE Software.

[8]  R HerrinWilliam Software maintenance costs , 1985 .

[9]  Patrick Loy,et al.  The method won't save you: (but it can help) , 1993, SOEN.

[10]  Donald L. Day,et al.  User responses to constraints in computerized design tools (extended abstract) , 1996, SOEN.

[11]  Albert S. Dexter,et al.  A Model for estimating Information System Requirements Size: Preliminary Findings , 1988, ICIS.

[12]  Terry Judith Parkins THE CASE AGAINST CASES , 1961 .

[13]  Robert P. Bostrom,et al.  Comparing representations with relational and EER models , 1990, Commun. ACM.

[14]  D. L. Burkhard,et al.  Implementing case tools , 1989 .

[15]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[16]  Jay F. Nunamaker,et al.  Information Technology to Support Electronic Meetings , 1988, MIS Q..

[17]  Chris F. Kemerer,et al.  An agenda for research in the managerial evaluation of computer-aided software engineering (CASE) tool impacts , 1989, [1989] Proceedings of the Twenty-Second Annual Hawaii International Conference on System Sciences. Volume II: Software Track.

[18]  John C. Henderson,et al.  Dimensions of I/S Planning and Design Aids: A Functional Model of CASE Technology , 1990, Inf. Syst. Res..

[19]  Mark S. Silver,et al.  Decision Support Systems: Directed and Nondirected Change , 1990, Inf. Syst. Res..

[20]  Gordon B. Davis,et al.  Strategies for Information Requirements Determination , 1982, IBM Syst. J..

[21]  I. Rozman,et al.  Understandability of the software engineering method as an important factor for selecting a case tool , 1992, SOEN.

[22]  David J. Jankowski The feasibility of CASE structured analysis methodology support , 1994, SOEN.

[23]  Lance A. Miller Programming by Non-Programmers , 1974, Int. J. Man Mach. Stud..

[24]  Victor R. Basili,et al.  Experimentation in software engineering , 1986, IEEE Transactions on Software Engineering.

[25]  Lawrence H. Putnam,et al.  A General Empirical Solution to the Macro Software Sizing and Estimating Problem , 1978, IEEE Transactions on Software Engineering.

[26]  Carma McClure,et al.  Case is Software Automation , 1988 .

[27]  James D. Hollan,et al.  Direct Manipulation Interfaces , 1985, Hum. Comput. Interact..

[28]  B. Adelson,et al.  The Role of Domain Expenence in Software Design , 1985, IEEE Transactions on Software Engineering.

[29]  Donald C. McDermid Software Engineering for Information Systems , 1990 .

[30]  Michael J. Hannafin,et al.  Guidelines for using locus of instructional control in the design of computer-assisted instruction , 1984 .

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

[32]  Claude E. Walston,et al.  A Method of Programming Measurement and Estimation , 1977, IBM Syst. J..

[33]  R. E. Yellen Systems analysts performance using CASE versus manual methods , 1990, Twenty-Third Annual Hawaii International Conference on System Sciences.

[34]  Thomas R. G. Green,et al.  Scope Marking in Computer Conditionals - A Psychological Evaluation , 1977, Int. J. Man Mach. Stud..

[35]  Tom Moher,et al.  Methodology and experimental research in software engineering , 1982 .

[36]  G. Steinberg,et al.  Selection criteria for analysis and design CASE tools , 1989, SOEN.

[37]  James D. McKeen Successful Development Strategies for Business Application Systems , 1983, MIS Q..

[38]  Hausi A. Müller,et al.  Computer Aided Software Engineering , 1996, Springer US.

[39]  Donald F. Shafer,et al.  Establishing a CASE toolbox. 15 steps to selecting CASE tools , 1993 .

[40]  Carol Zagorsky Case Study: Managing the Change to CASE , 1990 .

[41]  John R. Golden,et al.  Software cost estimating: craft or witchcraft , 1981, DATB.

[42]  Claes Wohlin,et al.  Experimentation in Software Engineering , 2000, The Kluwer International Series in Software Engineering.

[43]  Maryam Alavi MAKING CASE AN ORGANIZATIONAL REALITY , 1993 .

[44]  Capers Jones,et al.  Programming Productivity , 1986 .

[45]  Iris Vessey,et al.  Evaluation of vendor products: CASE tools as methodology companions , 1992, CACM.

[46]  Volkmar H. Haase,et al.  Application-Oriented Specifications: Developing the Connection between User and Code: Guest Editors' Introduction , 1982, Computer.

[47]  M. Alavi Making CASE an organizational reality: strategies and new capabilities needed , 1993 .