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

Analyzing User Requirements by the Unified deal and Total Quality care SummaryA successful project demands a correct and gross(a) requirements analysis. This paper proposes a refined requirements workflow, TQM/UP, to analyze requirements systematically. This workflow integrates five concern and statistical analysis tools of Total Quality Management (TQM)Affinity diagram, shoetree diagram, Brainstorming, Pareto analysis and operation Decision Program Chart (PDPC)into the Unified Process (UP) and helps the team to analyze requirements in a more efficient way. The guidelines I provide are based on my own experiences in an IT company, Interlancer, differentiateicular(a) which is briefly introduced at the latter part of this paper. educator & practitioner heavysetI would like to thank all of the people at UL for their financial choke off and input during this project. I give special thanks to my project advisor, Mr. jakes Noonan, for his support and guidance. I would also lik e to thank my girlfriend, for her enduring support over the past several weeks.ContentsSummary 1Educator & practitioner summary 21 Introduction 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 consumption 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 channelise 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 probe the Problem? 144.2.2 How to Understand Stakeholder need? 174.2.3 How to Define the schema? 184.2.4 How to Manage the Scope of the frame? 194.2.5 How to Refine the body Definition? 205 A trustworthy world face Interlancer, Limited 215.1 A brief introduction of Interlancer 215.2 TQM/UP in Interlan cer 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 finis 30Appendix Glossary of Terms 31List of illustrations 32List of tables 32References 331 IntroductionRequirements analysis of a software system is one of the most crucial steps in the software development process. Frederick P. Brooks, Jr. has pointed out that no separate 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 feign of errors in requirements is substantial The resulting software may not satisfy users real needs.