Design
Professional System Designer
Build a targeted information-system requirements profile and generate a personalised Investigation Atlas report — without entering operational case data.
IdentityContextInformationRequirementsFieldsReport
1. Optional report identity
Use a generic project/system title if appropriate. Do not enter confidential case names or sensitive references.
Used naturally throughout the generated report.
Optional heading or internal reference.
2. Operating context
3. Information architecture
Select the types of information the system may need to manage as structured concepts.
Material types
4. Functional requirements
Protection characteristics
5. Baseline data-dictionary fields
Advanced versions can expose much larger field libraries. These baseline fields demonstrate how CORE, RECOMMENDED and contextual fields can be selected.
Stable non-meaningful identifier.
Lifecycle/status of the record.
Trace where information came from.
System-maintained record history.
Useful for multilingual and translation workflows.
Supports protection and access decisions.
Separates recorded information from later review.
Use carefully for contextual explanation.
Legal & professional positioning: the report identifies matters requiring validation; it does not certify legal compliance. Applicable law, mandate, organisational policy, evidentiary rules, security requirements and professional advice remain controlling.