Stakeholder needs
Who the system is for, what they need, and the operational scenarios it must support, agreed before design begins.
Systems Engineering platform · In development
Systems Alloysmith
Many parts. One system.
The same guided approach as Product Architect, for complex systems. Systems Alloysmith takes you from stakeholder needs to a verified system: clear requirements, an architecture they are allocated to, interfaces under control, and evidence that every requirement was met. Smitty, its AI coach, helps you write, check and trace the work, and you stay in charge of every decision.
How it will work
From stakeholder need to verified system
- 1
Needs
Capture who the system serves and what they need, with the concept of operations and the constraints it must live within.
- 2
Requirements
Turn needs into system and subsystem requirements, each with a rationale, acceptance criteria and a way to verify it.
- 3
Architecture
Build the functional and physical architecture, allocate requirements to the elements that meet them, and compare options with trade studies.
- 4
Integrate
Define and control the interfaces between elements and teams, and plan how the parts come together into one working system.
- 5
Verify
Verify every requirement by test, analysis, inspection or demonstration, validate with stakeholders, and keep the evidence.
What it will do
Planned capabilities
We're building this platform now. Here's what it's designed to cover; details may change as we work with early users.
Requirements management
System and subsystem requirements with rationale and acceptance criteria, checked for clarity, completeness and testability.
End-to-end traceability
From stakeholder need to requirement, design element and test result and back, so the impact of any change is clear.
Architecture models
Functional and physical architecture, with requirements allocated to the elements that meet them, in a form ready for model-based work.
Interface control
Interface definitions between elements and teams, with owners, agreed versions and change history.
Trade studies
Compare design options against weighted criteria, record the decision and its rationale, and revisit it when facts change.
Verification and validation
A verification plan per requirement (test, analysis, inspection or demonstration), a test matrix, and the evidence that it passed.
Baselines and change control
Freeze baselines at each review, route changes through impact analysis and approval, and keep a full history.
Works with your tools
Link products from Product Architect and programs in Program Forgemaster, and connect delivery work in Jira.
Smitty, your systems engineering coach
An AI coach that helps you write clear, testable requirements, spots gaps and conflicts, suggests allocations and verification methods, and drafts review packages. Drafts are labeled, show their reasoning, and never invent figures.
Built on the standards
Grounded in ISO/IEC/IEEE 15288 for system life cycle processes, ISO/IEC/IEEE 29148 for requirements and ISO/IEC/IEEE 42010 for architecture, following INCOSE practice and ready for SysML v2 models.
One account across the suite
Systems Alloysmith is its own platform with its own plans. One VektorForgeAI login will cover every platform you use, and you can choose one platform, two, or the whole suite.
Systems Alloysmith is in development, and the capabilities above may change as we work with early users. Plans are expected to follow Product Architect's Free, Pro and Team model. INCOSE is a registered trademark of the International Council on Systems Engineering; SysML is a registered trademark of the Object Management Group, Inc. VektorForgeAI is not affiliated with either.
Waitlist
Get early access
Tell us a little about your work and we'll invite you when early access opens. Need help sooner? Our consultants work in this discipline today.