Working with a use case

After you create a use case, Keldyn drafts an architecture and opens the Architecture Workspace. That is where you review the system, run security analysis, and track progress against the frameworks you assigned. The lifecycle on the workspace header runs Requirements, then Design, then Review.

​

Generate the architecture

Submit a use case and Keldyn builds an architecture model from the requirements and answers. You get a Generating Architecture screen, then an Architecture Preview.

​

The Architecture Workspace

Five tabs. The header is where you change lifecycle status (Draft, Under Review, Approved, Active, Production, Suspended, Retired) or edit the use case.

​

Run security analysis

Keldyn looks at the architecture for threats and weaknesses. Analysis runs after generation. Run it again when the design changes.

• When something needs attention, an alert banner appears at the top of the workspace with actions like Run Analysis, Re-run Analysis, Review Risks, or Review Controls.
• Results populate the Architecture Threats card on the Progress Tracker and the risk table on the Security tab.

​

Track requirements and risks

On the Compliance and Security tabs, each control appears as a row you can expand to see its description, implementation guidance, underlying threat, finding, and evidence. From there you can set a control’s status, assign an owner, or mark it not applicable. For details on working with controls, see Frameworks & controls. On the Security tab, the Architecture CWEs section lists risks from the analysis with their severity and a tracking state (for example Not Reviewed, In Progress, Mitigated, or Accepted) that you can update as you address them.

​

Next steps