Software development process: strategies for handling business rules and requirements

ABSTRACT

A successful project demands a correct and thorough requirements specification. This paper proposes techniques and strategies for handling business rules and requirements. The guidelines we provide are based on our own experiences with the development of large-scale enterprise applications as well as research we have done on best practices for requirements management proposed by other authors. The techniques are based on recursively classifying software requirements into logical coherent classes of requirements so that they improve developers' conception of the requirements and streamline the navigation to the next steps in the process. The techniques proposed in this paper, provide a mechanism for keeping track of requirements and help the development team to test the software in a more efficient way.

REFERENCES

• 1: Bernd Bruegge , Allen A. Dutoit, Object-Oriented Software Engineering; Conquering Complex and Changing Systems, Prentice Hall PTR, Upper Saddle River, NJ, 1999
• 2: Committee on Information Systems Trustworthiness, National Research Council (1999): Trust in Cyberspace, Washington, DC: National Academy Press.
• 3: Dewett T., Jones G. R (2001): The role of information technology in the organization: a review, model, and assessment, Journal of Management 27(2001), pp.313-346.
• 4: Robert B. Grady, Practical software metrics for project management and process improvement, Prentice-Hall, Inc., Upper Saddle River, NJ, 1992
• 5: Stephen Haag , Donald J. McCubbrey , Maeve Cummings, Management and Information Systems for the Information Age,3e, McGraw-Hill Higher Education, 2001
• 6: Ivar Jacobson, Object-oriented software engineering, ACM Press, New York, NY, 1991
• 7: Shari Lawrence Pfleeger, Software Engineering: Theory and Practice, Prentice Hall PTR, Upper Saddle River, NJ, 2001
• 8: Shari Lawrence Pfleeger , Chuck Howell , Les Hatton, Solid Software, Prentice Hall PTR, Upper Saddle River, NJ, 2001
• 9: Craig Larman, Applying UML and patterns: an introduction to object-oriented analysis and design, Prentice-Hall, Inc., Upper Saddle River, NJ, 1997
• 10: Roger S. Pressman, Software Engineering: A Practitioner's Approach, McGraw-Hill Higher Education, 2001
• 11: Siegel S. G (2001): Successful Software Development, Prentice Hall.
• 12: Ian Sommerville, Software engineering (4th ed.), Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1993
• 13: Wainright Martin E., Brown C. V, DeHayes D. W., Hoffer J. A, Perkins W. C (2000): Managing Information Technology, Prentice Hall.
• 14: Scott F. Wilson, Analyzing Requirements and Defining Solution Architectures: MCSD Training Kit: For Exam 70-100 with CD-ROM, Microsoft Press, Redmond, WA, 1999

INDEX TERMS

Keywords:
business rules, domain process, managing software, requirements specification, software engineering, software requirements