This Article 
 Bibliographic References 
 Add to: 
Managing Requirements Inconsistency with Development Goal Monitors
November/December 1999 (vol. 25 no. 6)
pp. 816-835

Abstract—Managing the development of software requirements can be a complex and difficult task. The environment is often chaotic. As analysts and customers leave the project, they are replaced by others who drive development in new directions. As a result, inconsistencies arise. Newer requirements introduce inconsistencies with older requirements. The introduction of such requirements inconsistencies may violate stated goals of development. In this article, techniques are presented that manage requirements document inconsistency by managing inconsistencies that arise between requirement development goals and requirements development enactment. A specialized development model, called a requirements dialog meta-model, is presented. This meta-model defines a conceptual framework for dialog goal definition, monitoring, and in the case of goal failure, dialog goal reestablishment. The requirements dialog meta-model is supported in an automated multiuser World Wide Web environment, called DealScribe. An exploratory case study of its use is reported. This research supports the conclusions that: 1) an automated tool that supports the dialog meta-model can automate the monitoring and reestablishment of formal development goals, 2) development goal monitoring can be used to determine statements of a development dialog that fail to satisfy development goals, and 3) development goal monitoring can be used to manage inconsistencies in a developing requirements document. The application of DealScribe demonstrates that a dialog meta-model can enable a powerful environment for managing development and document inconsistencies.

[1] M. Alford, “Strengthening the Systems Engineering Process,” Proc. NCOSE, San Jose, Calif., 1991.
[2] A.I. Anton, "Goal-based Requirements Analysis," Proc. 2nd IEEE Int'l Conf. Requirements Engineering, CS Press, Los Alamitos, Calif., Apr. 1996, pp. 136-144.
[3] H. Barki and J. Hartwick, “Rethinking the Concept of User Involvement,” MIS Quarterly, vol. 13, no. 1, pp. 53-56, 1989.
[4] S. Bendifallah and W. Scacchi, “Work Structures and Shifts: An Empirical Analysis of Software Specification Teamwork,” Proc. 11th Int'l Conf. Software Eng., pp. 260-270, IEEE, 1989.
[5] B. Boehm and H. Hoh, Identifying Quality-Requirement Conflicts IEEE Software, pp. 25-36, Mar. 1996.
[6] F.P. Brooks, Jr., The Mythical Man-Month: Essays on Software Engineering, Addison Wesley Longman, Reading, Mass., 1975.
[7] S. Ceri, G. Gottlob, and L. Tanca, "Logic Programming and Databases," Surveys in Computer Science. Springer-Verlag, 1990.
[8] P. Checkland, Systems Thinking, Systems Practice. John Wiley&Sons, 1981.
[9] E.J. Chikofsky and B.L. Rubenstein, “CASE: Reliability Engineering for Information Systems,” Computer Aided Software Eng. (CASE), E. Chikofsky, ed., pp. 147-153, IEEE, 1993.
[10] L. Chung, B. Nixon, and E. Yu, "Using Non-Functional Requirements to Systematically Support Change," Proc. Second Int'l Conf. Requirements Eng., IEEE CS Press, Los Alamitos, Calif., 1995, pp. 132-139.
[11] M. Chen and J. Nunamaker, “The Architecture and Design of a Collaborative Environment for Systems Definition,” Data Base, pp. 22-28, Winter/Spring 1991.
[12] B. Curtis, H. Krasner, and N. Iscoe, "A Field Study of the Software Design Process for Large Systems," Comm. ACM, vol. 31, no. 11, pp. 1,268-1,287, 1988.
[13] A. Dardenne, A. van Lamsweerde, and S. Fickas, "Goal-Directed Requirements Acquisition," Science of Computer Programming, pp. 3-50, vol. 20, Apr. 1993.
[14] C. Davy, “Using CASE to Control a Large Data Analysis Project,” CASE on Trial. K. Spurr and P. Layzell, eds., pp. 7-16, New York: John Wiley&Sons, 1990.
[15] S. Easterbrook, "Domain Modelling with Hierarchies of Alternative Viewpoints," Proc. IEEE Int'l Symp. Requirements Eng., pp. 65-72, 1993.
[16] S. Easterbrook and B. Nuseibeh, “Using ViewPoints for Inconsistency Management,” Software Eng. J., IEE/BCS, 1996.
[17] A. Egyed and B. Boehm, “Analysis of Software Requirements Negotiation Behavior Patterns,” USC-CSE-96-504, Univ. of Southern California, Los Angeles, 1996.
[18] W. Emmerich, A. Finkelstein, C. Montangero, S. Antonelli, S. Armitage, and R. Stevens, “Managing Standards Compliance,” IEEE Trans. Software Eng., Nov./Dec. 1999.
[19] S. Faulk, “Software Requirements: A Tutorial,” Software Requirements Eng., R.H. Thayer and H., Dorfman, eds., pp. 128-149. Los Alamitos, Calif.: IEEE CS Press, 1997.
[20] M.S. Feather, “FLEA : Formal Language for Expressing Assumptions Language Description,” June 1997.
[21] L. Festinger, Conflict, Decision, and Dissonance. London: Tavistock Publications, Ltd., 1964.
[22] S. Fickas and M. Feather, “Requirements Monitoring in Dynamic Environments,” Proc. Int'l Symp. Requirements Eng. (RE'95), pp. 140–147, Mar. 1995.
[23] O. Gotel and A. Finkelstein, Contribution Structures Proc. Second IEEE Int'l Symp. Requirements Eng., 1995.
[24] D.K. Graf and M.M. Misic, “The Changing Roles of the Systems Analyst,” Information Resources Management J., vol. 7, no. 2, pp. 15-23, Spring 1994.
[25] S. Jacobs and S. Kethers, “Improving Communication and Decision Making within Quality Function Deployment,” Proc. First Int'l Conf. Concurrent Eng., Research, and Application, Pittsburgh, Aug. 1994.
[26] M. Jarke, R. Gallersdörfer, M.A. Jeusfeld, and M. Staudt, “ConceptBase : A Deductive Object Base for Meta Data Management,” J. Intelligent Information Systems, vol. 4, no. 2, pp. 167–192, 1995.
[27] M. Jarke, S. Eherer, R. Gallersdorfer, M.A. Jeusfeld, and M. Staudt, “ConceptBase—A Deductive Object Base Manager,” Informatik V, pp. 93-14, 1993.
[28] E. Kim and J. Lee, “An Exploratory Contingency Model of User Participation and MIS Use,” Information and Management, vol. 11, pp. 87-97, 1986.
[29] M. Klein, "Supporting Conflict Resolution in Cooperative Design Systems," IEEE Trans. Systems, Man, and Cybernetics, vol. 21, no. 6, pp. 1,379-1,390, Nov./Dec. 1991.
[30] H. Krasner, B. Curtis, and N. Iscoe, “Communication Breakdowns and Boundary Spanning Activities on Large Programming Projects,” Proc. Empirical Studies of Programmers: Second Workshop, pp. 47-64, Washington, D.C., G.M. Olson, S. Sheppard, and E. Soloway, eds. Norwood, N.J.: Ablex Publishing, Dec. 1987.
[31] J. Lee, SIBYL: A Tool for Managing Group Decision Rationale Proc. Computer Supported Cooperative Work (CSCW '90), 1990.
[32] P. Lempp and L. Rudolf, “What Productivity Increases to Expect from a CASE Environment: Results of a User Survey,” Computer Aided Software Engineering (CASE), Chikofsky, ed., pp. 147-153, IEEE, 1993.
[33] N. Leventhal, “Using Groupware to Automate Joint Application Development,” J. Systems Management, vol. 45, no. 5, pp. 16-22, Sept./Oct. 1995.
[34] Y. Liou and M. Chen, “Using Group Support Systems and Joint Application Development for Requirements Specification,” J. Management Information Systems, vol. 10, no. 3, Winter.
[35] M. Lubars, C. Potts, and C. Richter, "A Review of the State of the Practice in Requirements Modeling," Proc. IEEE Int'l Symp. Requirements Eng., IEEE Computer Soc. Press, Los Alamitos, Calif., 1993, pp. 2-14.
[36] K. Lyytinen and R. Hirschheim, “Information Systems Failures—A Survey and Classification of the Emperical Literature,” Oxford Surveys in Information Technology, vol. 4, pp. 257-309, Oxford Univ. Press, 1987.
[37] S. Magal and K. Snead, “The Role of Causal Attributions in Explaining the Link between User Participation and Information System Success,” Information Resources Management J., vol. 6, no. 3, pp. 19-29, Summer 1993.
[38] N. Maiden, S. Minocha, M. Ryan, K. Hutchings, and K. Manning, “A Co-operative Scenario-Based Approach to the Acquisition and Validation of Systems Requirements,” Proc. Human Error and Systems Development, Glasgow Univ., Scotland, Mar. 1997.
[39] Marconi Systems Tech nology, “Requirements and Traceability Management,” Interactive Development Environments, Inc., San Francisco, 1993.
[40] L. Markus and M. Keil, “If We Build It, They Will Come: Designing Information Systems That People Want to Use,” Sloan Management Review, pp. 11-25, Summer 1994.
[41] C. Mazza et al., Software Engineering Standards, Prentice Hall, Upper Saddle River, N.J., 1994.
[42] J. McKeen and T. Guimaraes, “Successful Strategies for User Participation in Systems Development,” JMIS, vol. 14, no. 2, pp. 133-150, Fall 1997.
[43] P. Mi and W. Scacchi, “Process Integration for CASE Environments,” IEEE Software, vol. 9, no. 2, pp. 45-53, Mar. 1992. reprinted in Computer-Aided Software Eng., second edition, E. Chikovsky, ed., IEEE Computer Society, 1993.
[44] J. Miller, D. Palaniswami, A. Sheth, K. Kochut, and H. Singh, “WebWork: METEOR's Web-Based Workflow Management System,” Technical Report #UGA-CS-TR-97-002, Dept. of Computer Science, Univ. of Georgia, Mar. 1997.
[45] J. Minker, “Logic and Databases: A 20 Year Retrospective,” invited keynote address, Proc. Workshop Logic in Databases, San Miniato, Italy, July 1996.
[46] G. Mullery, "CORE : A Method for Controlled Requirements Expression," Proc. 4th Int'l Conf. Soft. Eng.(ICSE-4), IEEE Comp. Soc. Press, Los Alamitos, Calif., 1979, pp. 126-135.
[47] E. Mumford and M. Wier, Computer Systems in Work Design—The ETHICS Method. London: Assoc. Business Press, 1979.
[48] B. Meyer, “On Formalism in Specifications,” IEEE Software, vol. 2, no. 1, pp. 6-26, Jan. 1986.
[49] J. Mylopoulos, A. Borgida, M. Jarke, and M. Koubarakis, "Telos: Representing Knowledge About Information Systems," ACM Trans. Information Systems, pp. 325-362, vol. 8, Oct. 1990.
[50] R.J. Norman and J.F. Nunamaker Jr., “CASE Productivity Perceptions of Software Engineering Professionals,” Comm. ACM, vol. 32, no. 9, pp. 1,102-1,108, Sept. 1989.
[51] B. Nuseibeh, J. Kramer, and A. Finkelstein, "A Framework for Expressing the Relationships Between Multiple Views in Requirements Specification," IEEE Trans. Software Eng., vol. 20, no. 10, pp. 760-773, Oct. 1994.
[52] L. Osterweil, and S. Sutton, “Using Software Technology to Define Workflow Processes,” National Science Foundation Workshop Workflow&Process Automation, Athens, Georgia, 1996.
[53] C. Potts, K. Takahashi, and A. Anton, "Inquiry-Based Requirements Analysis," IEEE Software, Mar. 1994, pp. 21-32.
[54] QSS Ltd. Dynamic Object Oriented Requirements System, Reference Manual, version 2.1, Oxford.
[55] B. Ramesh and V. Dhar, "Supporting Systems Development by Capturing Deliberations During Requirements Engineering," IEEE Trans. Software Eng., pp. 498-510, vol. 18, June 1992.
[56] B. Ramesh, “Representing and Maintaining Process Knowledge for Large-Scale Systems Development,” IEEE Software, pp. 54-59, Apr. 1994.
[57] B. Ramesh and M. Jarke, “Towards Reference Models for Requirements Traceability,” IEEE, Trans. Software Eng., to appear.
[58] S. Robbins, Organizational Behavior: Concepts, Controversies, and Applications. Inglewood Cliffs, N.J.: Prentice Hall, 1983.
[59] D. Robey, D.L. Farrow, and C.R. Franz, “Group Process and Conflict in Systems Development,” Management Science, The Inst. of Management Sciences, vol. 35, no. 10, pp. 1,172-1,191, Oct. 1989.
[60] W.N. Robinson and S. Volkov, “Conflict-Oriented Requirements Restructuring,” GSU CIS Working Paper 96-15, Georgia State Univ., Atlanta, Sept. 1996.
[61] W.N. Robinson, “Interactive Decision Support for Requirements Negotiation,” Concurrent Engineering: Research&Applications, special issue on Conflict Management in Concurrent Eng., The Inst. of Concurrent Eng., vol. 2, pp. 237-252, 1994.
[62] W.N. Robinson and S. Volkov, “A Meta-Model for Restructuring Stakeholder Requirements,” Proc. 19th Int'l Conf. Software Eng. (ICSE 19), pp. 140–149, May 1997.
[63] W.N. Robinson and S. Volkov, “Supporting the Negotiation Life-Cycle,” Comm. ACM, pp. 95-102, May 1998.
[64] W.N. Robinson and S. Pawloski, “Surfacing Root Requirements Interactions from Inquiry Cycle Requirements Documents,” Proc, Third Int'l Conf. Requirements Eng., ICRE’98, Colorado Springs, Col., IEEE, 1998.
[65] W.N. Robinson, "Negotiation Behavior During Requirement Specification," Proc. Int'l Conf. Software Eng., pp. 268-276, 1990.
[66] A. Sheth, ed., Proc. Workshop Workflow&Process Automation, Nat'l Science Foundation, Athens, Georgia, 1996.
[67] G. Spanoudakis and A. Finkelstein, “Integrating Specifications: A Similarity Reasoning Approach,” Automated Software Eng. J., vol. 2, no. 4, pp. 311-342, 1995.
[68] I. Vessey and A.P. Sravanapudi, “CASE Tools as Collaborative Support Technologies,” Comm. ACM, vol. 38, no. 1, pp. 83-95, Jan. 1995.
[69] A. van Lamsweerde and E. Letier, "Integrating Obstacles in Goal-Driven Requirements Engineering," Proc. ICSE-98: 20th Int'l Conf. Software Eng.,Kyoto, Apr. 1998.
[70] A. van Lamsweerde, R. Darimont, and P. Massonet, "Goal-Directed Elaboration of Requirements for a Meeting Scheduler: Problems and Lessons Learned," Proc. RE'95—Second Int'l Symp. on Requirements Eng.,York, IEEE, 1995.
[71] A. van Lamsweerde, R. Darimont, and P. Massonet, “The Meeting Scheduler System—Preliminary Definition,” internal report, Univ. of Louvain, 1993.
[72] D.B. Walz, J.J. Elam, and B. Curtis, “Inside A Software Design Team: Knowledge Acquisition, Sharing, and Integration,” Comm. ACM, vol. 36, no. 10, pp. 63-77, 1993.
[73] D.B. Walz, J.J. Elam, and H. Krasner, “A Methodology for Studying Software Design Teams: An Investigation of Conflict Behaviors in the Requirements Definition Phase,” Proc. Empirical Studies of Programmers: Second Workshop, G.M. Olson, S. Sheppard, and E. Soloway, eds. pp. 83-99, Washington, D.C., Ablex Publishing, Dec. 1987.
[74] T. Winograd and C.F. Flores, Understanding Computers and Cognition: A New Foundation for Design, Ablex, Norwood, N.J., 1986.
[75] J. Yen and W. Tiao, “A Systematic Tradeoff Analysis for Conflicting Imprecise Requirements,” Proc. Third IEEE Int'l Symp. Requirements Eng., RE’97, Jan. 1997.

Index Terms:
Requirements engineering, inconsistency and conflict management, process modeling and monitoring, meta-modeling, CASE.
William N. Robinson, Suzanne D. Pawlowski, "Managing Requirements Inconsistency with Development Goal Monitors," IEEE Transactions on Software Engineering, vol. 25, no. 6, pp. 816-835, Nov.-Dec. 1999, doi:10.1109/32.824411
Usage of this product signifies your acceptance of the Terms of Use.