Product Tour
Choose the right Ellygent workflow for each project.
Ellygent adapts from lightweight specification management to full systems engineering and functional safety workflows. Start simple, then add structure as the project requires more context, traceability, and engineering rigor.
Project modes
Fundamental
Lite
Engineering
FuSa
Product Walkthrough
See how Ellygent scales from specifications to full systems engineering.
Choose a project mode first, then follow the workflow steps that become relevant for that level of engineering rigor. Fundamental stays focused on requirements, Lite adds system context, Engineering adds decomposition, and FuSa adds safety analysis.
Modes of operation
Match the workflow rigor to the project maturity.
Ellygent does not force every team into the same process. The project mode defines how much system context must be captured before requirements are authored, reviewed, traced, and exported. This keeps simple projects fast while giving complex and safety-relevant projects the structure they need.
Fundamental mode
A focused specification workspace for teams that need to import, create, edit, review, and export concrete requirements without running a formal system-definition workflow.
When to apply
Use it when the project context already exists elsewhere, when the team is managing imported ReqIF content, or when the immediate need is clean requirements management rather than system decomposition.
Lite mode
A lightweight system-definition flow that captures the minimum engineering rationale needed before requirements are written or refined.
When to apply
Use it for early-stage products, internal tools, customer-facing features, or smaller projects where shared context matters but full decomposition is not yet necessary.
Engineering mode
A complete systems engineering workflow that connects problem context, mission objectives, operational scenarios, capabilities, functions, and requirements.
When to apply
Use it for complex products, embedded systems, multi-team development, platform work, or projects where every requirement must remain traceable to system intent and functional behavior.
FuSa mode
A safety-oriented workflow that extends engineering mode with hazards, malfunctions, and safety goals before deriving the requirements baseline.
When to apply
Use it for safety-relevant systems, regulated environments, embedded control functions, or product areas where unsafe behavior must be analyzed and constrained explicitly.
Workflow steps
One engineering flow, activated progressively by mode.
Step 1
Problem Statement
Clarify why the system needs to exist by capturing the current state, measurable impact, stakeholders, operating context, constraints, and additional considerations.
Step 2
Mission Objectives
Translate the problem into clear mission objectives with measurable targets, success criteria, and expected stakeholder value.
Step 3
Concept of Operations
Define how the system will operate in the real world, including actors, operational environment, system scope, usage scenarios, triggers, and expected outcomes.
Step 4
System Capabilities
Identify what the system must be able to do at a capability level before decomposing behavior into functions or detailed requirements.
Step 5
Functional Decomposition
Break system capabilities down into system functions, behaviors, responsibilities, and logical building blocks that can later drive requirements and architecture.
Step 6
Safety Goals & Hazards
For safety-relevant systems, connect functions, malfunctions, hazards, and safety goals so safety intent remains explicit before requirements are derived.
Step 7
Concrete Requirements
Transform approved system context, capabilities, functions, and safety goals into structured, verifiable requirements ready for review, traceability, and export.
Start simple, then scale the engineering rigor.
Use Fundamental or Lite mode when teams need speed and clarity. Move to Engineering or FuSa mode when the project requires decomposition, safety rationale, and end-to-end traceability.