Object Oriented Software Engineering   View all facts   Glossary   Help
subject > process > analysis > requirements analysis
Next analysisroot cause analysis    Upanalysis    Previous analysispost-mortem analysis   

requirements analysis comparison table
Subject include have risk is part of has definition perform after have typical mistake continue throughout stop has part is a subtopic of is a kind of determine
analysis         2.2 - Classes and Objectsprocess 
requirements analysisdefining the problem to be solved and what software will be created to solve it
  • misunderstanding and lack of understanding of the domain or the real problem
  • Requirements can change rapidly, resulting in requirements 'churn'
  • attempting to do too much which occurs when inadequate boundaries have been placed on the problem or the solution, or when those boundaries are not respected
  • It may be hard to reconcile conflicting sets of requirements
  • It is hard to state requirements precisely
requirements and specificationThe process of deciding on the requirements of a software systemdomain analysisover-constraintthe life of a software system use case analysis4.6 - Some Techniques for Gathering and Analyzing Requirementsanalysisthe responsibilities of a system

Next analysisroot cause analysis    Upanalysis    Previous analysispost-mortem analysis