See how your
business connects
Connect business capabilities, applications, data and risks in one architecture model. Give leaders and delivery teams a shared picture for planning change and discussing priorities.
Connect the discussion to the architecture
Give each stakeholder a relevant view of the same underlying information, from business capabilities to applications and risk.
Business and technology context
ContextCapture capabilities, systems, ownership and relationships in your architecture workspace.
One model, consistent views
ConnectionsScapius checks the model and generates focused views from it. Different discussions can use the same definitions and relationships instead of maintaining separate drawings.
Plan business change
PlanningUse capability maps and lifecycle roadmaps to discuss which parts of the business need attention and which systems support them.
Discuss investment priorities
PortfolioBring recorded business value, technology fit and costs into portfolio conversations, with the architecture as context.
Review risk and controls
RiskConnect threats, controls and affected systems. Use risk and compliance views to discuss recorded exposure and the status of controls.
A shared picture for the next decision
When teams work from separate diagrams, it is hard to agree on what depends on what. Bring those connections into one model, with focused views for different conversations.
Exported pictures
landscape_v3_final.pptx
exported 8 months ago
landscape_v3_final_FINAL.pptx
team drive, unclear
context-diagram.png
wiki, author left
Each copy aging separately.
One connected architecture model
workspace.ea
Landscape
currentContainer view
currentThreat model
currentUpdate the model and regenerate consistent views.
For business leaders, architects and delivery teams who need a common view of the organization.
Start with one business area
Map what matters
Choose a business area. Your architecture team records its capabilities, applications, data and dependencies in a connected model.
Check the connections
Scapius checks references and relationship rules, highlighting inconsistencies for the team to resolve. The team remains responsible for keeping the information accurate.
Review with stakeholders
Use focused views to discuss dependencies, priorities and risks. Export diagrams for presentations and regenerate them when the model changes.
Your team maintains the model. Stakeholders see the connections.
Architecture specialists describe the systems and relationships once. Scapius turns that information into diagrams and dashboards, so stakeholders can discuss the architecture without reading its source files.
system core_banking "Core Banking" {description "Ledger and account management"criticality "Mission-Critical"app payment_api "Payment API" {owner "Payments Team"lifecycle { phase "Run" start "2024-01-01" }}}data_object transaction_record "Transaction Record" {classification "Confidential"}payment_api writes transaction_record "Posts entries" {cardinality OneToMany}
What to know before you start
Who is Scapius EA for?
Scapius EA is for architecture teams who need to explain how the business, its systems and its risks connect. Leaders, portfolio owners and delivery teams can use the resulting views in planning and review discussions.
Do business stakeholders need to write code?
No code is needed to read the diagrams, dashboards or exported views. Creating and maintaining the model does require an architecture or technical specialist to work with Scapius source files. This is not a no-code modeling tool.
Which decisions can it support?
Capability maps, portfolio views and lifecycle roadmaps provide context for investment and change discussions. Dependency views help teams understand connections, while risk and compliance views bring recorded threats and controls into reviews. Scapius presents the information your team models; it does not make investment decisions or certify compliance.
How is this different from separate architecture diagrams?
Each view comes from the same connected model. Your team can update a system or relationship once and regenerate the relevant views, rather than maintaining separate drawings. Keeping the model current still depends on the information your team supplies.
Can we use the views in stakeholder presentations?
Yes. Views can be exported as PNG or SVG images for presentations and documents. Exports are snapshots, so regenerate them after the underlying model changes.
What is available today?
Community is available in beta, free and self-hosted, for a single local workspace. Enterprise options for organization-wide use are coming soon. Contact [email protected] to discuss requirements and availability.
Where does our information live?
With Community, the architecture model lives in plain-text files on infrastructure you control. Your team can keep those files in its own Git repository for change history. Enterprise options for your own cloud and Scapius-managed hosting are coming soon.
How should we evaluate it?
Start with one business area and involve someone who maintains its architecture. Map a small set of capabilities, systems and dependencies, then review the resulting views with the stakeholders who use that information.
Start with the decision in front of you
Choose one business area, a change initiative or a risk review. Discuss your needs with us, or ask your architecture team to evaluate Community with a small model.