JIRA

Overview of UML and SysML stereotypes for a feature-oriented development process for JIRA issues

Overview of UML and SysML stereotypes for a feature-oriented development process for JIRA issues

As used by Dr Darren as IT Consultant and Trainer: Expert Advisor for Science, Engineering, and Education on the SysML Plugin Project for MagicDraw™ UML. Issue stereotypes are linked to JIRA workflow State Machine Diagrams, with many issue types sharing abstract workflows.

Custom 'jRequirement' and 'feature' JIRA issue types represented as UML stereotypes combined with the SysML Requirement approach

Custom 'jRequirement' and 'feature' JIRA issue types represented as UML stereotypes combined with the SysML Requirement approach

It is of importance to this SysML-like process that requirements satisfied by one or more collaborating features are never removed from the system. A JIRA link may be used to represent the SysML «satisfy» stereotype. The SysML «Requirement» Class stereotype is here combined with a custom JIRA «jIssue» stereotype via the hybrid «jRequirement» stereotype, which may be applied to a UML™ Component to afford easier nesting of local tequirements within «feature» components, to reflect JIRA sub-issue groupings directly in a SysML model.

Custom 'recordable' JIRA issue types represented as UML stereotypes

Custom 'recordable' JIRA issue types represented as UML stereotypes

A «recordable» issue is one that should always remain in the system as a development record (and possible JIRA link target for other issues) and need never be resolved or removed. Note how the «recordable» stereotype is related to a «workflow» State Machine. The substereotypes shown have Component as base metaclass, because in this approach the Component is used to model Feature and Requirements (and thus these substereotypes can be applied to Components that graphically and/or physically nest).

UML State Machine Diagram analysis of the workflow of a custom 'recordable' JIRA issue type

UML State Machine Diagram analysis of the workflow of a custom 'recordable' JIRA issue type

A «recordable» issue is one that should always remain in the system as a development record (and possible JIRA link target for other issues) and need never be resolved or removed.

Representation of a feature-oriented software process as UML stereotypes corresponding to JIRA issue types

Representation of a feature-oriented software process as UML stereotypes corresponding to JIRA issue types

Note the complex many-to-many relationship between requirements satisfied by features, and the possibility of many different designs for a given feature. Although a more a accurate representation of the desired process, this proposed stereotype model was not adopted in full, as it proved too fine-grained for the legacy issues on the given project.

Syndicate content
randomness