Application-modelling lifecycle

The model emerged through a chain of organisational contributions, permissions and judgements—not from the software alone.

Prepare
1Plan and prioritise
Project manager and modellerScope, priorities and target applications
2Identify owners and capture application data
Application owners and development teamsOwnership, host lists and local application knowledge
3Arrange permission and credentials
Infrastructure owner and discovery teamAuthority and secure login credentials for the relevant hosts
Build
4Scan the infrastructure
Discovery teamWorking access and availability of the target systems
5Set up the modelling silo
Footprint modeller and discovery teamUsable scan results and correctly prepared modelling data
6Create matching rules
Footprint modeller and application teamsTechnical evidence reconciled with business and local knowledge
Assure
7Validate the model
Modeller, application owner and discovery teamJudgement about omissions, false matches and incomplete data
8Accept the model
Application owner and project managerAgreement that the model is credible enough to use
Sustain
9Diagnose faults and refine
Modeller, discovery team and application teamsShared investigation when evidence and expectations disagree
10Archive and report progress
Project manager and modellerReliable shared records, status information and retained context

Delays or ambiguity in any dependency could interrupt the lifecycle or weaken confidence in the resulting application model.