PUT INFATIN ST Integration via agosense.symphony · 2020-02-18 · This product data sheet...
2
1/2 Sparx Enterprise Architect - RM-Tool | 2012-12-01 agosense GmbH Stammheimer Str. 10 70806 Kornwestheim [email protected] fon +49 . 7154 . 99951 . 0 www.agosense.com Follow us on... http://www.facebook.de/agosense http://twitter.com/agosense Integration via agosense.symphony Sparx Enterprise Architect & Requirements-Management-Tool PRODUCT INFORMATION SHEET This product data sheet describes bidirectional integration between the modelling tool Sparx Enterprise Architect (Sparx EA) and another requirements management (RM) tool using the agosense.symphony integration platform. Using the agosense.symphony platform, Sparx EA can be linked to a diverse range of RM tools, such as: • HP Quality Center/ALM • IBM Rational Doors • Jama Contour • Microsoft Team Foundation Server • PTC Integrity • Polarion Requirements Please contact us if you are looking to link other tools. You can find the current list of supported tools on our website at www.agosense.com/english/home > Products > agosense.instruments. Goal To ensure effective collaboration between the users of RM tools (e.g. Requirements Engineers) and Sparx EA users (e.g. System Architects), the tools are linked to the agosense.symphony integration platform using adapters. Using the platform, it is possible to individually configure the synchronisation of requirements from the RM tool to Sparx EA and the use case models from Sparx EA back into the RM tool. All data is available on both sides in close to real time, and is kept constantly updated and available. The Implementation process The synchronisation rules and processes between the tools are defined in a way that is customer specific using the administration interface in agosense.symphony. The data to be transferred between the RM tool and Sparx EA are assigned attribute and/or value levels using the mapping module. This assignment can be defined according to a specific project or department, or various mapping scenarios. In our example, the synchronisation process firstly transfers all the relevant requirements found in the RM tool to Sparx EA, and organises them into a defined requirements package. The hierarchical structure is retained to provide enhanced readability. The goal is to give the architects access to all requirements in Sparx EA, so they may continue working on these requirements without having to leave their own environment. As a result, the Sparx EA user can for example, create mo- dels for use cases. During this process, they may assign use cases or even individual model elements to the relevant requirements, to make it clear how individual require- ments have been factored into the model. The use cases are then integrated into various diagrams within Sparx EA, to maintain a transparent and graphic depiction of the system architecture. The synchronisation process then identifies all relevant objects using the linkage between the requirements and the model elements or use cases. Based on this information, it is determined which diagrams apply to which requirements. The relevant diagrams can then be synchronised into the RM tool (e.g. into a separate area or module). This stage of the process links the diagrams with the relevant requirements within the RM tool. This lets the requirements engineers create a picture of the system architecture without having to change interfaces to look at the details in Sparx EA. The Synchronisation Process The following screenshots reveal a simplified example integration scenario between the tools Sparx EA and IBM Rational Doors. Screenshot No. 1 shows the Doors interface with a list of requirements in an individual hierarchy. Screenshot No. 2 shows the mapping module in the agosense.symphony interface with the translation of attributes between Sparx EA and IBM Rational Doors. Advantages & Uses Automated bidirectional synchronisation of requirements from RM tool to Sparx EA and of use case models from Sparx EA back into the RM tool. Requirements engineers and system ar- chitects continue to work in their own tool while having access to up-to-date automa- ted information. Fig. 1: Schematic integration between a RM tool (e.g. IBM Rational Doors) and Sparx EA using agosense.symphony Sparx Enterprise Architect System Architects create use case models and link them with the synchronised requirements Requirements-Management-Tool Requirements Engineers create requirements in an individual hierarchy in their own tool and can see the resynchronised use case models linked to the requirements. ... and other tools agosense.symphony Modelling of the business process and automated bidi- rectional synchronisation of requirements or use case models
Transcript of PUT INFATIN ST Integration via agosense.symphony · 2020-02-18 · This product data sheet...
1/2Sparx Enterprise Architect - RM-Tool | 2012-12-01
agosense GmbHStammheimer Str. 10 70806 Kornwestheim
[email protected] +49 . 7154 . 99951 . 0www.agosense.com
Follow us on...http://www.facebook.de/agosensehttp://twitter.com/agosense
Integration via agosense.symphonySparx Enterprise Architect & Requirements-Management-Tool
PRODUC T INFORMATION SHEE T
This product data sheet describes bidirectional integration between the modelling tool Sparx Enterprise Architect (Sparx EA) and another requirements management (RM) tool using the agosense.symphony integration platform. Using the agosense.symphony platform, Sparx EA can be linked to a diverse range of RM tools, such as:
• HP Quality Center/ALM• IBM Rational Doors• Jama Contour• Microsoft Team Foundation Server• PTC Integrity• Polarion Requirements
Please contact us if you are looking to link other tools. You can find the current list of supported tools on our website at www.agosense.com/english/home > Products > agosense.instruments.
GoalTo ensure effective collaboration between the users of RM tools (e.g. Requirements Engineers) and Sparx EA users (e.g. System Architects), the tools are linked to the agosense.symphony integration platform using adapters. Using the platform, it is possible to individually configure the synchronisation of requirements from the RM tool to Sparx EA and the use case models from Sparx EA back into the RM tool. All data is available on both sides in close to real time, and is kept constantly updated and available.
The Implementation processThe synchronisation rules and processes between the tools are defined in a way that is customer specific using the administration interface in agosense.symphony. The data to be transferred between the RM tool and Sparx EA are assigned attribute and/or value levels using the mapping module. This assignment can be defined according to a specific project or department, or various mapping scenarios.
In our example, the synchronisation process firstly transfers all the relevant requirements found in the RM tool to Sparx EA, and organises them into a defined requirements package. The hierarchical structure is retained to provide enhanced readability. The goal is to give the architects access to all requirements in Sparx EA, so they may continue working on these requirements without having to leave their own environment.
As a result, the Sparx EA user can for example, create mo-dels for use cases. During this process, they may assign use cases or even individual model elements to the relevant requirements, to make it clear how individual require-ments have been factored into the model. The use cases are then integrated into various diagrams within Sparx EA, to maintain a transparent and graphic depiction of the system architecture.
The synchronisation process then identifies all relevant objects using the linkage between the requirements and the model elements or use cases. Based on this information, it is determined which diagrams apply to which requirements. The relevant diagrams can then be synchronised into the RM tool (e.g. into a separate area or module). This stage of the process links the diagrams with the relevant requirements within the RM tool. This lets the requirements engineers create a picture of the system architecture without having to change interfaces to look at the details in Sparx EA.
The Synchronisation ProcessThe following screenshots reveal a simplified example integration scenario between the tools Sparx EA and IBM Rational Doors.
Screenshot No. 1 shows the Doors interface with a list of requirements in an individual hierarchy.
Screenshot No. 2 shows the mapping module in the agosense.symphony interface with the translation of attributes between Sparx EA and IBM Rational Doors.
Advantages & Uses
Automated bidirectional synchronisation of requirements from RM tool to Sparx EA and of use case models from Sparx EA back into the RM tool.
Requirements engineers and system ar-chitects continue to work in their own tool while having access to up-to-date automa-ted information.
Fig. 1: Schematic integration between a RM tool (e.g. IBM Rational Doors) and Sparx EA using agosense.symphony
Sparx Enterprise Architect
System Architectscreate use case models and link them with the
synchronisedrequirements
Requirements-Management-Tool
Requirements Engineers create requirements in an individual hierarchy in their own tool and can
see the resynchronised use case models linkedto the requirements.
... and other tools
agos
ense
.sym
phon
y
Modelling of the business process and automated bidi-rectional synchronisation of
requirements or use case models
2/2Sparx Enterprise Architect - RM-Tool | 2012-12-01
agosense GmbHStammheimer Str. 10 70806 Kornwestheim
[email protected] +49 . 7154 . 99951 . 0www.agosense.com
Follow us on...http://www.facebook.de/agosensehttp://twitter.com/agosense
Integration via agosense.symphonySparx Enterprise Architect & Requirements-Management-Tool
PRODUC T INFORMATION SHEE T
Screenshot No. 3 demonstrates the synchronised list of requirements ultimately in Sparx EA.
Screenshot No. 4 shows how the system architect can create use case models in Sparx EA and link them to requirements.
Screenshot No. 5 shows the use case models as synchronised from Sparx EA in Doors, each linked with the corresponding requirement.
Screenshot No. 6 shows a synchronised use case model in the Doors interface.
1 2
3 4
65
