Analyzing User Requirements by the Unified Process and Total Quality Management :: essays research papers

Analyzing User Requirements by the Unified Process and Total Quality Management abbreviationA successful project demands a correct and thorough requirements analytic thinking. This paper proposes a refined requirements workflow, TQM/UP, to analyze requirements systematically. This workflow integrates five management and statistical analysis tools of Total Quality Management (TQM)Affinity diagram, Tree diagram, Brainstorming, Pareto analysis and Process Decision Program graph (PDPC)into the Unified Process (UP) and helps the team to analyze requirements in a much efficient way. The guidelines I provide are based on my own experiences in an IT company, Interlancer, Limited which is briefly introduced at the latter incision of this paper.Educator & practitioner summaryI would like to thank all of the people at UL for their support and input during this project. I give special convey to my project advisor, Mr. John Noonan, for his support and guidance. I would also like to thank my girlfriend, for her enduring support over the past several weeks.ContentsSummary 1Educator & practitioner summary 21 gate 52 What are Requirements? 53 Capturing Requirements by UP 63.1 What is UP? 73.1.1 UP is Use-Case Driven 73.1.2 UP is Architecture-Centric 83.1.3 UP is Iterative and Incremental 83.2 The Life of UP 83.3 The Role of Requirements in the Software Life Cycle 103.4 Requirements Workflow in UP 104 A Refined Requirements Workflow TQM/UP 134.1 Introduction of TQM Tools 134.1.1 Affinity diagram 134.1.2 Tree diagram 134.1.3 Brainstorming 134.1.4 Pareto analysis 144.1.5 Process Decision Program Chart (PDPC) 144.2 TQM/UP 144.2.1 How to Analyze the Problem? 144.2.2 How to Understand Stakeholder Needs? 174.2.3 How to Define the arranging? 184.2.4 How to Manage the chain of the System? 194.2.5 How to Refine the System Definition? 205 A real world case Interlancer, Limited 215.1 A brief instauration of Interlancer 215.2 TQM/UP in Interlancer 225.2.1 Analyze the Problem 225.2 .2 Understand Stakeholder Needs 245.2.3 Define the System 275.2.4 Manage the Scope of the System 275.2.5 Refine the System Definition 286 Conclusion 30Appendix Glossary of Terms 31List of illustrations 32List of tables 32References 331 IntroductionRequirements analysis of a computer software system is one of the most crucial steps in the software development process. Frederick P. Brooks, Jr. has pointed out that no other part of the work so cripples the resulting system if done wrong and no other part is more difficult to rectify later than requirements analysis.The potential impact of errors in requirements is substantial The resulting software may not satisfy users real needs.