Software development process: strategies for handling business rules and requirements

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.

[1]  Gareth R. Jones,et al.  The role of information technology in the organization: a review, model, and assessment , 2001 .

[2]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[3]  Carol V. Brown,et al.  Managing Information Technology , 1991 .

[4]  Scott F. Wilson.  Analyzing Requirements and Defining Solution Architectures: MCSD Training Kit: For Exam 70-100 with CD-ROM , 1999 .

[5]  Samuel L. Grier,et al.  A tool that detects plagiarism in Pascal programs , 1981, SIGCSE '81.

[6]  S. K. Robinson,et al.  An empirical approach for detecting program similarity and plagiarism within a university programming environment , 1987 .

[7]  Ian Sommerville,et al.  Software engineering (4th ed.) , 1993 .

[8]  G. Whale.  Indentification of Program Similarity in Large Populations , 1990, Comput. J..

[9]  Craig Larman,et al.  Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition) , 1997 .

[10]  Ivar Jacobson,et al.  Object-Oriented Software Engineering , 1991, TOOLS.

[11]  Carolyn Wong.  A Successful Software Development , 1984, IEEE Transactions on Software Engineering.

[12]  Shari Lawrence Pfleeger,et al.  Solid Software , 2001 .

[13]  정인기,et al.  [서평]「Applying UML and Patterns - An Introduction to Object-Oriented Analysis and Design」 , 1998 .

[14]  Bernd Bruegge,et al.  Object Oriented Software Engineering, Conquering Complex and Changing Systems , 2002 .

[15]  David A. Wilson.  Managing Information , 1997 .

[16]  K. J. Ottenstein.  An algorithmic approach to the detection and prevention of plagiarism , 1976, SGCS.

[17]  Robert B. Grady,et al.  Practical Software Metrics for Project Management and Process Improvement , 1992 .

[18]  Donald J. McCubbrey,et al.  Management Information Systems for the Information Age , 1997 .

[19]  Scott E. Donaldson,et al.  Successful Software Development , 2001 .