1. Simple Use Case of PROMCODE model June 25th, 2014 T. Kamimura

2. Current model

3. Simple Case User roles –Project manager of acquirer (PM-A) –Project manger of supplier (PM-S) Assumption –A legal contract to bind an acquirer and a supplier is handled separately. –There is no cascading of acquirer-supplier relationships. –Project environment of an acquirer and a supplier are not shared; i.e., project environment of a supplier is not accessible to PM-A and therefore, project information needs to be sent to PM-A for project management by an acquirer. Steps 1.PM-A defines a scopeItems. 2.PM-A requests PM-S to create a plan. 3.PM-S creates workitems and artifacts with the following information. Planned value, its responsible person, planned measure 4.PM-S then sends them to PM-A as a plan. 5.Repeat Steps 1-4, until PM-A and PM-S establish agreement. 6.PM-S updates on regular basis actual values of properties of workitems and of measurements and measures attached to artifacts. This can be done by PM-A requesting a report to PM-S or by PM-S posting a report to an agreed location. 7.PM-S sends an update as a report to PM-A. 8.PM-A reviews updates and takes actions such as Inquire the details of the workItems to appropriate persons responsible for that. Creating, reviewing and closing issues 9.Repeat Steps 6-8 as necessary 10.Conduct acceptance review and close a project

4. Flow of activities Create ScopeItems PM-A Create WorkItems and Artifacts PM-S Request a plan Respond with a plan Reach agreement on a plan Send regular update as report Review report and take actions Repeats as necessary Accept results and close a project Repeats as necessary report

5. Discussions Do we need more resources? Or is a report considered as serialization of a result of a query? plan +date: DateTime +status:(open, agreed, started, closed) ScopeItem Workitem Artifact contains report +date: DateTime