Can someone please help me with a Domain Model and a DesignClass Diagram for the attached task?
Background In the F2 system there is an organizational structure consisting of (among others) units and persons. A person can be associated with a unit and the units can be set up in a hierarchy. People and units, in this regard, are called: Parties. The F2 system supports communication (mails) at both unit- and person level. To facilitate the sending there a concept named Distribution lists. A simple user story describing the use of a distribution list could be: As a case manager who needs to send an e-mail, I can choose a distribution list so that avoid selecting more single parties. A distribution list can be set up by all users of the system and the user must decide on the parties to be included in the distribution list and how each party should be handled in the tribution list. An administrator in F2 can create global distribution lists that can be used by all users, a case manager can only create private distribution lists that can only be used by the user himself. Figurforklaring FRED F2 cong Com One can imagine a hierarchy as depicted in Figure 1. Here you could need to make a distribution list so that you sent to all persons in the unit F2 R&D and its sub-units. This could be named “F2 R&D stakeholders” and the user would expect that a mail sent to this distribution list would hit Aske, Gisli, Gert, David, Thomas, Alan and … In the same hierarchy you could imagine another distribution list that was relevant to the managers of F2 R&D as well as the unit mailboxes in the underlying units. This could be named “F2 R&D general information”, and the user who sent an email to this list would expect to hit Thomas, Alan and the devices Core, F2X, and… The Task Create a mockup of a dialog for the end user to make it easy to understand how the individual parties are set up in the distribution list. These user stories must be able to be fulfilled by the user interface. 1. As a case manager, I can add a person to a distribution list so that I can send to the person later. 2. As a case manager, I can add a unit to a distribution list so that I can later send to the people in the unit. 3. As a case manager, I can add a unit to a distribution list so that I can send to the unit mailbox later. 4. As a case manager, I can configure a selected unit in a distribution list so that I can choose whether to send to the sub-units unit mailbox or sub-unit users. 5. As a case manager, I can add multiple parties to a distribution list so that I can have many parties on my list. 6. As a case manager, I can remove parties from a distribution list so that I can maintain my distribution list. 7. As a case manager, I can name a distribution list so I can see the difference between the distribution lists. 8. As an administrator, I can also create my own distribution lists so that I can get the same benefits as a case manager by having a private distribution list. 9. As an administrator, I can specify that a distribution list is visible to everyone, so that in the organization you can have global distribution lists. Show transcribed image text Background In the F2 system there is an organizational structure consisting of (among others) units and persons. A person can be associated with a unit and the units can be set up in a hierarchy. People and units, in this regard, are called: Parties. The F2 system supports communication (mails) at both unit- and person level. To facilitate the sending there a concept named Distribution lists. A simple user story describing the use of a distribution list could be: As a case manager who needs to send an e-mail, I can choose a distribution list so that avoid selecting more single parties. A distribution list can be set up by all users of the system and the user must decide on the parties to be included in the distribution list and how each party should be handled in the tribution list. An administrator in F2 can create global distribution lists that can be used by all users, a case manager can only create private distribution lists that can only be used by the user himself. Figurforklaring FRED F2 cong Com One can imagine a hierarchy as depicted in Figure 1. Here you could need to make a distribution list so that you sent to all persons in the unit F2 R&D and its sub-units. This could be named “F2 R&D stakeholders” and the user would expect that a mail sent to this distribution list would hit Aske, Gisli, Gert, David, Thomas, Alan and … In the same hierarchy you could imagine another distribution list that was relevant to the managers of F2 R&D as well as the unit mailboxes in the underlying units. This could be named “F2 R&D general information”, and the user who sent an email to this list would expect to hit Thomas, Alan and the devices Core, F2X, and… The Task Create a mockup of a dialog for the end user to make it easy to understand how the individual parties are set up in the distribution list. These user stories must be able to be fulfilled by the user interface. 1. As a case manager, I can add a person to a distribution list so that I can send to the person later. 2. As a case manager, I can add a unit to a distribution list so that I can later send to the people in the unit. 3. As a case manager, I can add a unit to a distribution list so that I can send to the unit mailbox later. 4. As a case manager, I can configure a selected unit in a distribution list so that I can choose whether to send to the sub-units unit mailbox or sub-unit users. 5. As a case manager, I can add multiple parties to a distribution list so that I can have many parties on my list. 6. As a case manager, I can remove parties from a distribution list so that I can maintain my distribution list. 7. As a case manager, I can name a distribution list so I can see the difference between the distribution lists. 8. As an administrator, I can also create my own distribution lists so that I can get the same benefits as a case manager by having a private distribution list. 9. As an administrator, I can specify that a distribution list is visible to everyone, so that in the organization you can have global distribution lists.
Expert Answer
Answer to Can someone please help me with a Domain Model and a Design Class Diagram for the attached task?…