![]() ![]()
This iterative evolution of the diagrams actually implements the agile iteration of business requirements with no manual action needed. This is the area where the BPMN2 diagrams are composed and uploaded to the repository every time they change. We talked about this in the last post (part 1). These artifacts will be used as dependencies by the BPMN Automation component to read the BPMN2 diagrams inside. The JAR file is uploaded to an artifact repository ( Nexus in our case) with a specific version. The features into each BPMN2 file have a name that will be the name of the JIRA issue grouped in that component. “FUSION” will be the JIRA project name and “TELLER” the name of the JIRA component in that project. Reminder: We’ll use a folder structure related to JIRA items. The set of features will be translated to JIRA issues in each component and project. The first level will be JIRA projects while the second level will be the components in that projects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |