Hello everyone,
I am excited to share an important milestone for the OSLC4Net project - we now have the very first OSLC server published that is implemented using ASP.NET and OSLC4Net.
OSLC server for StrictDoc is a requirements management API server implementing the OSLC RM domain spec. It exposes requirements from the innovative requirements engineering tool called StrictDoc.
StrictDoc aims to provide simple yet rigorous requirements management that is sufficient to conform to standards like DO178C, ISO 26262, IEC 62443 (OT/control system security), EU Cloud Resilience Act, ECSS-E-ST-40C (a product software standard for the European Space Agency), ETSI-303645 (IoT security) and others. The requirements are kept in Git using plain text files with stable IDs and traceability links and the a CLI tool is used to produce a static site that can be used to consume the requirements and to link to them. The generated site offers traceability matrices and other features needed for standards conformance. Git itself serves as a basis for the configuration management.
The OSLC RM server for StrictDoc adds content negotiation to the requirements
URIs and provides OSLC RM output for valid OSLC requests. Features include:
- stable URIs - same URIs as generated by StrictDoc are also valid OSLC resource URIs
- standard root services, service provider catalog, and service provider documents (one SP per StrictDoc document)
- SP capabilities include a query capability and a selection dialog capability.
- Selection dialogs and previews (validated against Jira OSLC Client from Lynxwork)
The server can be run easy using a single dotnet run command or the published OCI/Docker container.
As a reminder, OSLC4Net has a working OSLC Client under .NET 6+ since last year. See the README for an example of how to work with IBM Jazz WorkItem resources (OSLC ChangeRequests).
Happy linking,
Andrew