Support and investigation
Find the components and rules associated with a reported behaviour, then follow the references into the relevant source.
Application documentation
Give your team documentation they can use
When an application changes hands, people need more than a list of technologies. Harten documents how its processes, business rules, data and interfaces work, using the agreed source and supporting information.
How your team can use the documents
Onboarding and handover
Give incoming engineers and service owners a structured account to read alongside the application, with the unresolved questions still visible.
Preparation for change
Identify current behaviour and dependencies before deciding which requirements a replacement should preserve.
What the documentation covers
The document set covers business capabilities, users and processes, rules and decisions, data, integrations, architecture, security questions and operational concerns. Diagrams explain selected relationships; the surrounding text states what is known and what needs review.
Coverage depends on the material available. A source reference can support how a rule is implemented without establishing whether it remains current policy or is still used in production.
Read a complete example
The PRSD-IWS publication contains 17 documentation chapters and nine supporting views. You can open the same chapter navigation used to present the work, rather than reading another summary of the output.
Current-system overview · Business rules · System-context diagram
Explore the documentationDistinguish existing behaviour from future requirements
Documentation describes the application that was analysed. A specification organises that behaviour into requirements and proposed acceptance checks for review. The customer decides which behaviours remain necessary and which should change.
What happens when the application changes
The original documents remain tied to the source that was reviewed. For a later revision, Harten can scope a refresh around the changed inputs and agree which findings need another review.
Automatic continuous documentation is in development. Retained access and refresh work are separate arrangements, explained under follow-on services.
Arrange documentation for an application
Agree the intended readers, source material and areas that matter to them. The pricing page explains how documentation, specialist review and the other recovery outputs fit within an engagement.
Review the engagement and pricing