ISO/IEC/IEEE 12207
Software lifecycle processes.
SOFTWARE PRODUCTION SYSTEM
From requirements
to working software.
In one system.
Fornax Forge is a software production system. It manages the full lifecycle, from requirements through architecture, interface and code to testing and maintenance, and carries it out without developers.
FORNAX FORGEILLUSTRATIVE WORKFLOW
Customer portalConnected delivery / Release 0.8
One requirement. Every stage that follows from it.
One shared modelSelect a record to trace it
RequirementsArchitecture & databaseUser interfaceSource codeTestingDefect resolutionFurther development
01 / THE LIFECYCLE
Seven stages.
One software production system.
Fornax Forge takes a project through every stage and versions every key sub-stage. Each change stays linked to the requirement it comes from.
Follow one requirement through all seven stages.
01 / 07
01 / SPECIFY
Start with a requirement everyone can build on.
Requirements and the processes the software runs are written, approved and versioned. Every later stage builds on the approved version.
- Business, user, system and software requirements
- Versioned statements with a clear rationale
- Impact visible before a change is approved
CUSTOMER PORTAL
Session timeout
The system shall end an inactive user session after 15 minutes.
Rationale
Limit access from unattended workstations.
↗ ADR-008↗ PR-042↗ TST-026
Example record · Conceptual interface
02 / USE CASES
New project, existing code,
or migration.
Fornax Forge, the software production system, supports three starting points.
New projects. Fornax Forge builds software from requirements to release.
Taking over existing code. The system takes over and develops existing code, including code with no formal requirements.
Migration. Fornax Forge moves source code to a different technology or programming language.
EXISTING CODE EXAMPLE
What needs to change if we shorten the session timeout?
Fornax Forge starts from REQ-014, updates the session design and the service, and reruns the linked timeout tests.
REQ-014ADR-008PR-042TST-026
Every change keeps its reasoning.
Illustrative example, not a live system response.
03 / STANDARDS
A production system
built to standards.
As a software production system, Fornax Forge carries out every process in line with applicable standards and recommendations, including:
04 / BUILT AROUND YOUR ORGANISATION
Your tools.
Your knowledge.
Define how Fornax Forge fits your organisation: the tools to connect, access requirements and control over project data. Set the scope for each as part of the pilot.
Tool integration.
Agree which repositories, build pipelines, issue trackers and modelling tools the pilot needs to connect.
Access and deployment.
Define who needs access to each specification, how users sign in, and the hosting and region requirements for the pilot.
Data ownership and export.
Agree how project information will be imported, stored and exported, including the formats your team needs.
05 / A PATH TO ADOPTION
Start with a focused pilot.
Choose one project and agree how to evaluate it. Then, use the pilot findings to decide the next step.
- 01
Discovery
Define the project, source material and tools for a focused pilot. Agree the evaluation criteria.
- 02
Pilot
Pick one project – new, existing or due for migration – and test Fornax Forge on your own code.
- 03
Verification
Assess one change or release against the agreed criteria and record the findings.
- 04
Rollout
Use the pilot findings to plan integrations, responsibilities and wider adoption.
About Fornax Systems
For software that lasts.
Fornax Systems Sp. z o.o. develops Fornax Forge, a software production system that runs the entire software lifecycle, from requirements to maintenance and further development.
Key Fornax Forge technologies are patent-pending in the United States.
QUESTIONS AND ANSWERS
Software production system:
questions and answers.
Short answers about Fornax Forge.
What is a software production system?
It is a system that carries out the whole software lifecycle itself. Fornax Forge, for example, manages requirements, architecture, the database, the user interface, source code, testing and maintenance; therefore, no developers are involved.
How does the software production system work without developers?
First, the requirements and the processes the software runs are written and approved. Then Fornax Forge designs, produces and tests the software. In addition, every key sub-stage is versioned, so each change stays traceable.
Can the production system take over existing software?
Yes. Fornax Forge takes over and develops existing code, even code with no formal requirements. Therefore, the starting point can be a system that is already running.
Which languages does the software production system support?
Fornax Forge produces source code in almost any programming language. Moreover, it can migrate existing code to a different technology or programming language.
How do we start with the software production system?
Start with a focused pilot on one project: new, existing or due for migration. After that, use the pilot findings to plan integrations and wider adoption.
LET’S CONNECT THE DOTS
Discuss a pilot
for your project.
Tell us whether it is a new project, existing code, or a migration. We will discuss a pilot focused on your needs.
fornax@fornaxsystems.eu