Script to generate requirements from actors and acitvities

[Hurra]

Hello!

I use NAFv4 and have modelled Operational Views with the following:

«OperationalPerformer» --- IsCapableToPerform --> «OperationalActivity»

From this I create stakeholder requirements with the following syntax:

The system shall enable «OperationalPerformer» to «OperationalActivity».

I know seems like a waste, but it's a government agency 😇 "it has to be textual requirements"

🤔I just wanted to know if someone have any ideas of how I can keep track of which performers and acitvities which have requirements. My thought is to be able to generate these requirements when there are changes in the Operational Views. E.g. a new performer, or added activities to an existing performer.

💡One idea that pops up is to create a connector (maybe «trace»?) between the requirement to the performer and activity. And before creating a requirement, check if there is a corresponding requirement for the performer and activity in focus. If there is a requirement, just update the requirement text.

❓Any thoughts of how I can implement such a thing, and is the connector approach any good? Is there another way?

Thank you!

[Sunshine]

Govt Agency - you and me both.

I just wanted to know if someone have any ideas of how I can keep track of which performers and acitvities which have requirements. My thought is to be able to generate these requirements when there are changes in the Operational Views. E.g. a new performer, or added activities to an existing performer.

You could you a matrix of performers vs activities.
You could also baseline and compare to see any differences periodically.

💡One idea that pops up is to create a connector (maybe «trace»?) between the requirement to the performer and activity. And before creating a requirement, check if there is a corresponding requirement for the performer and activity in focus. If there is a requirement, just update the requirement text.

mmh? that sounds like extra work and in a large project likely to become unsustainable.
Rather than create a requirement element why not just generate the requirement via document generation. You've already modelled «OperationalPerformer» --- IsCapableToPerform --> «OperationalActivity»
so it shouldn't be too hard to create a MS Word document that transposes that into
The system shall enable «OperationalPerformer» to «OperationalActivity».
You may need to create a document fragment to achieve that with some SQL behind the scenes.

❓Any thoughts of how I can implement such a thing, and is the connector approach any good? Is there another way?

Interesting to see NAFv4 https://www.nato.int/cps/en/natohq/topics_157575.htm Looking at those documents I see they are using Sparx Enterprise Architect. 

[Hurra]

💡One idea that pops up is to create a connector (maybe «trace»?) between the requirement to the performer and activity. And before creating a requirement, check if there is a corresponding requirement for the performer and activity in focus. If there is a requirement, just update the requirement text.

mmh? that sounds like extra work and in a large project likely to become unsustainable.
Rather than create a requirement element why not just generate the requirement via document generation. You've already modelled «OperationalPerformer» --- IsCapableToPerform --> «OperationalActivity»
so it shouldn't be too hard to create a MS Word document that transposes that into
The system shall enable «OperationalPerformer» to «OperationalActivity».
You may need to create a document fragment to achieve that with some SQL behind the scenes.

Well, we need a status of the requirement, approved/implemented/verified/validated etc and also an ID. Therefore I don't think it's enough to only generate the requirement in the document. With a seperate object for the specific requirement based on OperationalPerformer and OperationalActivity we can do that easily.

I don't see we can do that with only generating text in the document. How would we keep track of status and ID?

What I do atm is to wait with generating the requirements as long as possible, then handle the changes and new stuff manually.

Thanks for your input.