0

I'm trying to represent some Jira the following business rules:

  • A project has defined issue status and issues types.
  • Same issue status and types can be defined across multiple projects.
  • Each issue has a status and a issue type of the project it belongs to.
  • Each issue is associated to a project, and a project has many issues.
  • Only issues with status = "closed" and issueType = "task" have the customField1.

So far I have this representation for the 4 rules :

enter image description here

Would like some feedback on the representation and any sugestion on the last rule.

qwerty_so
  • 35,448
  • 8
  • 62
  • 86
xdw dae
  • 51
  • 5

1 Answers1

0

Looks ok so far. For the last bullet point you can add a constraint attached to Issue which reads

{ Only issues with status = "closed" and issueType = "task" have the customField1 }

and you should probably add the attribute customField1 to Issue.

It's a bit strange, though, since attributes can normally not added dynamically. So probably it should be more like "can access" instead of "have".

qwerty_so
  • 35,448
  • 8
  • 62
  • 86
  • Thanks for your suggestion. Never used a constraint before but for what I found it is normally attached to a note, like in option A). Do you think any of the other options is correct? (options : https://i.stack.imgur.com/JNjIB.png) Notice also added connection between field and project like in issueType. – xdw dae Aug 07 '18 at 21:38
  • Edit : http://www.agiledata.org/images/admInitialDomainModel.gif (http://www.agiledata.org/essays/agileDataModeling.html#InitialDomainModel) found this image. That gave me this idea (only looking at issueType) : https://i.stack.imgur.com/VheZZ.png. Don't know if by now i should make a new question but any feedback appreciatted. – xdw dae Aug 07 '18 at 22:12
  • Ambler's picture shows an association class and no constraint at all. – qwerty_so Aug 08 '18 at 07:14