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
subjectfact 
requirements analysishas definition The process of deciding on the requirements of a software system2001-08-30 14:57:18.0
determines the responsibilities of a system2001-08-30 14:57:18.0
has risk
  • 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
2001-08-30 14:57:18.0
has typical mistake over-constraint2001-08-30 14:57:18.0
has part modelling2001-08-30 14:57:18.0
has part use case analysis2001-08-30 14:57:18.0
includes defining the problem to be solved and what software will be created to solve it2001-08-30 14:57:18.0
is a subtopic of 4.6 - Some Techniques for Gathering and Analyzing Requirements2001-08-30 14:57:18.0
is part of requirements and specification2001-08-30 14:57:18.0
is performed after domain analysis2001-08-30 14:57:18.0
is a kind of analysis2001-08-30 14:57:18.0
never stops2001-08-30 14:57:18.0
should continue throughout the life of a software system2001-08-30 14:57:18.0
processsee also process^22001-08-30 14:57:05.0