OpenFastTracing in Distributed Systems

[ambition-consulting]

Hi,

and thanks for this great product. There is one question though, that I was wondering about.

In a distributed system with independent teams, quite often

1. multiple repositories and
2. multiple deployment plans

exist. To trace requirements end-2-end, I

1. can use git sub-modules to mimic a single file base
2. currently cannot model stepwise deployments, where team B waits for a design implementation dsn˜1 before it can deploy (or maybe even develop/design) their dependant work

So I am wondering, if I was to build an automated report in particular on use cases spanning across both teams, how can the report account for this "legal" state of having pending, not-yet-implemented designs/code? My understanding is, that OFT only knows success or failure in reports, right?

Cheers
John

[ambition-consulting]

Also, I am wondering how to add hyperlinks to Specification Items. It would be really helpful to be able to relate them to the outside world.

[redcatbear]

To answer your first question, the way we do distributed projects is using intermediate exports (currently REQM2 format) and pass those from the specifying org unit to the implementing unit.

I plan to add a native OFT export format as JSON to improve on the shortcomings that OFT inherited from the Requirement Manager that introduced the REQM2 format.

You can mark requirements as DRAFT and filter them out when running a trace if you want to have a planning capacity for future capabilities in your project.

[redcatbear]

Hyperlinks are simply Markdown links. They should be rendered correctly in the reports. If not, that would be a bug.

[redcatbear]

JSON format draft is in #521