Research Project Management Constraints Analysis
The scenario describes a complex universe of research project management within a university setting. Researchers are assigned to specific research groups, and projects are decomposed into work packages led by a research group. Various constraints and rules govern researcher assignments and group changes, ensuring proper service delivery tracking and record-keeping within the research projects.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
The following case describes a universe of research project management. The university has many research groups that belong to different departments. Researchers belong to exactly one research group. Projects are decomposed into Work Packages (WP), and each WP has exactly one research group assigned to it as WP leader. To execute a research project, researchers need to be assigned to Work Packages. Two EDGs are proposed: Consider the two proposed EDGs and the following constraints. Investigate which combination of model and multiple propagation constraints enables you to capture the given constraints in the best way.
A researcher can only be assigned to a WP his/her own research group is leading.
= A researcher can only be assigned to a WP his/her own research group is leading. o Model to the right o MPC teamMember.RGMember.RG = teamMember.WPLeader.RG)
Given the above constraint, when a researcher changes from research group (RG), the assignments s/he did while being in the first group need to be ended first before changing from group
Given the above constraint, when a researcher changes from research group (RG), the assignments s/he did while being in the first group need to be ended first before changing from group o Model to the right o Ending RG_Member requires ending the dependent obj. first = teamMember RG Member TeamMember
A researcher can be assigned to any WP, independent of which RG is leading the WP
A researcher can be assigned to any WP, independent of which RG is leading the WP o Model to the left + model to the right o No constraint
However, service delivery from one group to another needs to be traceable. It should be possible to have an overview of researchers from other groups working on WPs led by a RG. This service delivery implies that whenever a researcher changes research group, the current assignments as team member of a WP are terminated and new ones are created to keep a correct record of the service delivery. Likewise, if WP leadership is re-assigned, team member assignments are re- recorded to ensure correct recording of the service delivery.
RG_Member TeamMember 1 2 However, service delivery from one group to another needs to be traceable. ... whenever a researcher changes research group ... keep a correct record of the (past) service delivery. .... o Model on the left: Life-cycles of RG_Member and TeamMember are unrelated o What happens when RG_Member is ended ? At moment 1, team-membership seems in context of RG1 membership At moment 2, same team-membership seems in context of RG2 membership
However, service delivery from one group to another needs to be traceable. It should be possible to have an overview of researchers from other groups working on WPs led by a RG. This service delivery implies that whenever a researcher changes research group, the current assignments as team member of a WP are terminated and new ones are created to keep a correct record of the service delivery. Likewise, if WP leadership is re-assigned, team member assignments are re-recorded to ensure correct recording of the service delivery. o Model to the right o ending RG_Member and WPLeader requires ending the dependent obj. first = teamMember RG Member TeamMember
