Turn “unlock the door” into behavior you can review.
Follow one feature from its initial request to a concrete handoff. Select sample answers, see which requirements depend on them, and inspect the reasoning before implementation.
One request. Follow the decisions.
Illustrative public demo · sample answers and proposals · no sign-in required
Illustrative decision status
3 unresolved · 0 deferred · 3 proposed requirements depend on these decisions.
Unresolved: offline behavior, confirmation timeout, access revocation.
This teaching view is not a product completeness score. Further engineering questions can remain after every sample answer is selected.
Capture request
Feature request
“Let users unlock the door from the app.”
Operating context
A resident uses a mobile app, an access service and a connected door controller. Connectivity can fail between a request and physical actuation.
SCN-01 · Remote unlock
Trigger: the resident selects Unlock. An authorized resident gains access when the controller reports the lock physically unlocked. Request acceptance alone is not confirmation.
In scope: the app, access service, command dispatch and physical confirmation. Mechanical key access and emergency egress design are outside this example.
Choices stay in this page’s memory. Resetting or reloading restores the sample; nothing is saved to a real project.
Choose a mode for the work you need to do.
This is guidance for project setup. You choose the mode; available steps also depend on enabled modules.
Manage or import existing requirements
Create, edit, review and export specifications, including imported ReqIF content. Upstream definition and AI derivation are not part of Foundation mode.
Define capabilities and requirements
Describe system capabilities and derive proposed requirements from them. Choose Engineering for problem framing, objectives and operational scenarios.
Develop connected system context
Connect problem statements, mission objectives, operational scenarios, capabilities, functions and requirements. Use this mode for work like the remote-unlock example.
Analyze safety-relevant behavior
Extend Engineering with malfunctions, hazards, safety goals and safety requirement derivation. These tools support analysis; they do not establish certification or compliance.
Your first useful result: one requirement with its reason.
Create an account, then set up a project. Bring one real feature request, record an explicit decision, connect a requirement to its source and export the definition for review.
Registration follows the existing account setup flow. This sample is not copied into your project.