Mastering the Requirements Process: Getting Requirements …

← Back to document page

E-1E-2E-3E-4BUCGoalsConstraintsBusiness Event ListPUCE-6E-8E-7E-5ConceptionScopingWork InvestigationProduct DeterminationRequirements DefinitionConstructionRequirements OutsourceSupplierExternal Requirements StrategyI-1I-2I-3I-4BUCBusiness Event ListPUCI-5I-6ConceptionScopingWork InvestigationProduct DeterminationRequirements DefinitionConstructionStoriesDeveloperIt erative Requirements StrategyS-1S-2S-3BUCPUCS-4S-5ConceptionS copingWork InvestigationProduct DeterminationRequirements DefinitionConstructionDeveloperRequireme nts GoalsConstraintsBusiness Event ListSequential Requirements StrategyRequirements Strategy MapsDevelopment BacklogRequirementPrioritizedPrioritized FeedbackFeedbackPriorityThe WorkAnalyze Business NeedsDevelop ProductWrite Require-mentsAnalysis Artifactss #ONTEXTs "5#Ss $ATA $ICTIONARYs 3TAKEHOLDERS Business Event List(Analysis Backlog)PrioritizedFeedbackFeedbackWorki ng ProductBusiness NeedsRequirementRequirementRequirementRe quirementIterative Requirements ProcessDesign and DevelopProject BlastoffRequirements Work ScopeDomain KnowledgeStakeholders & ManagementReuse LibraryReusable RequirementsBusinessNeedsProduct Use and EvolutionRisks and CostsReviewed SpecificationStakeholdersWants and NeedsRejectsOwnerMissing RequirementsRequirements TemplateQuali

Design and Develop Project Blastoff Requirements Work Scope Domain Knowledge Stakeholders & Management Reuse Library Reusable Requirements Business Needs Product Use and

  Requirements, Process, Getting, Mastering, Mastering the requirements process