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

Click on the image below to view it full size in an image viewer !
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.

randomness