ソフトウェア工学 - Oasis

ソフトウェア工学 - Oasis

OASIS OSLC PROMCODE TC Domain Model Revisited and Use Cases Development Plan of Specifications (Memorandum) Specification Development and Review Team Mikio Aoyama, Kazuhiro Funakoshi, Yoshio Horiuchi, Tsutomu Kamimura, Shigeaki Matsumoto, Arthur Ryman, Masaki Wakao, Kazuo Yabuta, Hiroyuki Yoshida, 1 2014/07/21, 08/05, 08/19, 9/02, 9/16, 9/19, 10/01,11/11, 11/25, 12/10, 12/24, 2015/01/07, 01/21, 02/04,02/18(2/20), 03/04, 04/08, 04/22, 05/13 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Contents Upcoming TC Meeting Schedule Proposed Domain Model Revised Use Cases and Scenarios Resources Associated with the Scenarios Basic Vocabulary TOC of the Draft Specifications Time Line Revised References Related Links: 2 PROMCODE PROMCODE TC TC Wiki: Wiki: https://wiki.oasis-open.org/oslc-promcode/ https://wiki.oasis-open.org/oslc-promcode/ OSLC OSLC Core Core TC Wiki: https://wiki.oasis-open.org/oslc-core/FrontPage All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project

Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Upcoming TC Meeting Schedule Proposed 25 26 27 28 3 Schedule TC Meeting TC Meeting TC Meeting TC Meeting Date/Time [EST] 8:00 p.m., May. 12 8:00 p.m., May. 26 8:00 p.m., Jun. 9 8:00 p.m., Jun. 23 Date/Time [JST] 9:00 a.m., May 13 9:00 a.m., May 27 9:00 a.m., Jun. 10 9:00 a.m., Jun. 24 Note Note: Start of US DST: March 8, 2015 (Sun) All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Specification Development 4 All

All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Action Items Raised TC24(Apr. 22) Introduction Add Add explanation explanation of of project project context, context, i.e. i.e. the the scope of of PROMCODE PROMCODE Terminology Terminology Architecture (Tentative) [New] Explain Explain the holistic view of solution architecture Domain Model Add Add introduction introduction to to the meaning of the model The The model is is about about data data collected collected by by aquirer aquirer (?) (?) Through Through review: Multiplicity Multiplicity of 0 from ManagedItemCollection to Project Service Specification Add Add REST

REST API Ref: Ref: IBM IBM Rational Rational Focal Focal Point Point Linked Linked Data Data and and RDF RDF REST REST API, API, https://j https://j azz.net/wiki/bin/view/LinkedData/FPLinkedData azz.net/wiki/bin/view/LinkedData/FPLinkedData Resource Definitions 5 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 TOC (Rev. 4/22, 5/13) 1. Introduction [Aoyama] <3> 2. Architecture [Aoyama] <2> 3. Domain Model [Yoshida, Aoyama] <10> 4. Service Specification [Wakao, Horiuchi, Ryman] <5> 5. Resource Definitions [Matsumoto, Funakoshi, Ryman] <25> Vocabulary, Vocabulary, Resource Resource Shape Shape 6. Use Case [Matusmoto, Aoyama, Yabuta] <15> 7. Sample Implementation of Use Case [Wakao, Horiuchi, Kamimur a] <10~15> 8. References [Aoyama] <1> References

6 Core Wiki: https://wiki.oasis-open.org/oslc-core/ All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Time Line Revised Milestone TC Launched Start Writing Working Draft Working Draft TC Review Update Draft for Comments Committee Draft Review of Member Section & Core Committee Draft (Due) Committee Draft Public Review Revised(Mar. 3) Mar. 25, 2014 Mar. 05, 2015 Apr. 10, 2015 30 days 14 days May 24, 2015 14 days (2 Weeks) Jun. 7 60 days Aug. 7 14 days Update Spec for Comments => Candidate of OASIS Standard Committee Specification and SoU Due Aug. 21, 2015 Vote 14 days+7 days OASIS Standard Sep. 4, 2015 7 Revised (4/22) May 10 Jun. 24 Jul. 8

Sep. 8 Sep. 22 Oct. 4 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Domain Model Revised 8 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Domain Model v. 2.4 (Revised May 13) 9 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Domain Model v. 2.34 (Revised Feb. 20)

10 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Domain Model v. 2.33 (Revised Feb. 4) Add Risk of same structure of Issue 11 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Domain Model v. 2.32 (Revised Jan. 20) metricOfScopeItemSize State metric 12 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015

2014-2015 State of Issues Basic set of states (Yabuta-san) Closed In-progress Raised Reference: OSLC CM 3.0 oslc_cm:Closed Completely done, no further fixes or fix verification is needed. oslc_cm:In-progress Active work is occurring. oslc_cm:Fixed oslc_cm:Approved oslc_cm:Reviewed oslc_cm:Verified The resolution or the fix is verified. 13 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Domain Model v. 2.31(Revised Nov. 25) Metric UnitofMeasure 14 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Domain Model v. 2.30(Revised Nov. 11)

15 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Rationale of Proposed Revision to Domain Model [N ov. 11/Nov. 25 ] Changes arising from Use Cases Relationship between Plan and Report should be explicitly specified -> Add association: correspondsTo [reportsOn] Structure of Issue and its Collection Add IssueCollection similar to ManagedItemCollection Relate IssueCollection to Project similar to ManagedIte mCollection: belongsTo Add an attribute, RaisedDate, to Issue 16 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Rationale of Proposed Revision to Domain Model [N ov. 11/Nov. 25 ]: State of Issues State of Issue: Open to users due to its variety in each p roject (OSLC CM, PMBOK) Add a property State defined by URI like UnitType Example: OSLC CM 3.0(http://open-services.net/wiki/change-man agement/Specification-3.0/) Resource State Name: State, Type URI http://open-services.net/ns/cm#State

Range Description oslc_cm:Closed Completely done, no further fixes or fix verification is needed. oslc_cm:In-progress Active work is occurring. oslc_cm:Fixed oslc_cm:Approved oslc_cm:Reviewed 17 oslc_cm:Verified The resolution or the fix is verified. All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Proposed Revision to Domain Model v. 2.26 State <-belongsTo IssueCollection collects <-correspondsTo 18 +raisedDate: DateTime All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management

Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Domain Model v. 2.26(Revised Sep. 25) 19 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Domain Model v. 2.25(Revised Sep. 30/Oct. 1) 20 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Issues and Proposed Changes to Domain Model Discussed at the TC on 9/17 Update of domain model Change Change name: MeasurementCriteria MeasurementCriteria -> Target Consistent Consistent definition of attributes: attributes: Project Project -> -> Add Add properties (identifier, title, description, plannedStartDa

te, te, actualStartDate, actualStartDate, plannedEndDate, plannedEndDate, actualEndDate) actualEndDate) Issue: Issue: Need Need to to discuss discuss whether whether state state should should be be added added Multiplicity: Multiplicity: Refer Refer Properties Properties of of Attributes Attributes in in UML UML Class Class Diagrams Diagrams Default Default value is 1, eliminate * after TypeName O..1 O..1 represents represents possibility possibility of of null null ++ AttributeName AttributeName : TypeName TypeName [*] [*] Metrics Metrics and and MeasureType: MeasureType: Clarify Clarify the the rationale rationale of using using Measure Measure Scenarios 21 Refine Refine the scenarios by adding concrete resources, and show the usage of of domain domain model

model Validating Validating the the domain model All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Reference Properties of Attributes in UML Class Diagrams Multiplicity [Default value is 1] 1 - this attribute has a single value of the specifi ed Type. 0..1 - this attribute can have a value of null. * - this attribute's value is a collection of values. 1..* - this attribute's value is a collection that co ntains at least one value. n .. m - this attribute's value is a collection that c ontains between n and m values. Reference: Properties of Attributes in UML Class Diagrams, http://msdn.microsoft.com/en-us/library/dd323861.aspx 22 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 On Use of Measure and Metrics SWEBOK

Guide to the Software Engineering Body Of Knowledge (SWEBOK), Version 3, 2014 Chapter 8, Software Engineering Management 6. Software Engineering Measurement Key Key terms terms on on software software measures measures and and measurement measurement methods methods have have been been defined defined in in [ISO15939-02] on the basis of the ISO international vocabulary vocabulary of of metrology metrology [ISO93]. [ISO93]. Nevertheless, Nevertheless, readers readers will will encou encou nter nter terminology terminology differences in the literature; for example, the term "metrics" "metrics" is is sometimes sometimes used used in in place place of of "measures. 6.2. Plan the Measurement Process Select Select measures. Candidate Candidate measures measures must must be be selected, selected, with with clear clear links links to to the the information information needs. Measures must then be selected ba sed sed on the the priorities

priorities of of the the information needs needs and and other other criteria criteria suc suc h h as cost of of collection, collection, degree degree of of process process disruption disruption during during collecti collecti on, on, ease ease of of analysis, ease of obtaining accurate, consistent data, a nd nd so so on on [ISO15939-02: [ISO15939-02: 5.2.3 5.2.3 and and Appendix Appendix C]. C]. 23 Reference: http://www.computer.org/portal/web/swebok/html/ch8#Ref6 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 On Use of Measure and Metrics ISO 15939:2007 Appendix A.2.3 Base measure A A measure measure defined defined in in terms

terms of of an attribute and the method for quantif ying ying it. it. (A (A measure measure is is aa variable variable to to which which aa value value is is assigned.) assigned.) A A base base measure measure is is functionally independent of other measures. A base meas ure ure captures captures information information about about aa single single attribute. Data collection invol ves ves assigning assigning values values to base measures. Specifying the expected rang ee and/or and/or type of values of a base measure helps to verify the quality o ff the data collected. collected. A.2.3.1.2.2 Unit of measurement A A particular particular quantity, defined defined and adopted by by convention, convention, with with which which other other quantities quantities of the the same same kind kind are are compared compared in in order to express th eir eir magnitude magnitude relative relative to to that

that quantity. quantity. Only Only quantities quantities expressed expressed in in th th ee same same units of measurement are directly comparable. Examples of u nits nits include include the the hour hour and and the the meter. meter. 24 Reference: ISO, ISO/IEC 15939:2007: Systems and Software Engineering Measurement Process, 2007. ISO 9126 Metric ISO 25010 Measure All Rights Reserved, Copyright Next-Generation Project Management Data Exchange Architecture Committee, 2014-2015 All Rights Reserved, Copyright Next-Generation Project Management Data Exchange Architecture Committee, 2014-2015 Add attributes: identifier title description plannedStartDate actualStartDate plannedEndDate actualEndDate Domain Model v. 2.4(Revised Sep. 16) (sizeOfScopeItem) FP Title: login screen actualSize: 10 FP metric State? Change mame: MeasurementCriteria -> Target KLOC

CodeSize 25 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Domain Model Issues Related to EMS in Domain Model Commonality and Difference between EMS and PROMCODE Policy: If PROMCODE use a concept which is defined in EMS, PROM CODE should not define define it, it, but but refer refer it. it. Use of Estimation in PROMCODE: Estimation in EMS is out of scope of PROMCODE. The planned va lue in PROMCODE is a value agreed between an acquirer and an sup plier after estimation estimation Measurement/Measure&Mertics/Measurement Use consistent model Measure of ScopeItem is not defined Associate MeasureType and UnitType to Project Unification of Vocabulary Use the same vocabulary to those of the same meaning metric, unitOfMeasure 26 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015

Domain Model Comparison of EMS and PROMCODE EMS PROMCODE Estimation and Measurement Use Estimation and Measurement i Estimation is out of scope. Planned is a value for agreement between Acquirer and Supplier. Value might be based on estimation, but estimation id not in the included in the activities of project control. Metric metric metric:Sloc (URI) Measure value:Decimal -> MeasureType [refer to] MeasurementCriteria Unit of Measure unitOfMeasure unit:Loc (URI) UnitType <-[referred by] Measure unit ->unitOfMeasure Measurement Measurement -> ScopeItem 27 Measurement numericValue xsd:double Unit of PlannedSize is undefined ->Associate MeasureType and UnitType to Project (A unique measure across the project) All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data

Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Domain Model v. 2.2(Revised Sep. 2) 28 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Domain Model Revisited for v 2.2 on 9/2 Structure around ManagedItem Attributes Attributes of ManagedItem: Add type for classification Add Add ManagedItemCollection ManagedItemCollection as a collection of ManagedItem, whic h h represents represents a collection collection of of status, status, or or snapshot, snapshot, of of the the project project Attributes: Attributes: Add Add identifier identifier and title Add Add Plan Plan and and Report Report as as subclasses subclasses of of ManagedItemCollection: ManagedItemCollection: Plan reflects an order from the acquirer to Supplier when the proj

ect is is started started Report Report reflects reflects aa report report compiled compiled from from the the snapshot in ManagedI temCollection Add Add Project Project as as aa reference reference to to the the project project under under management management The The entity entity Project Project is is only only for for reference, reference, and and is is considered considered as as out out of of ss cope cope of of the the PROMCODE PROMCODE domain model 29 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015

Domain Model (Aug. 6) 30 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Domain Model Revisited (2/2) Structure Measure/Measurement Add Add MeasurementCriteria as a criteria criteria of of Measure Measure Add Add attributes attributes of of type type and and title title to to Measure Measure Title: Title: Bug Bug density, Type: NoOfBugsPerKLOC, Unit: 1, Value: 33 Attributes Title Identifier Type 31 Measurement + + + MeasurementCriteria Measure +

+ + NA NA + All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Use Cases and Scenarios 32 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Use Cases and Scenarios Usage Context of Software Supply Chain Project Context Context: Data Interface between Acquirer and Supplier Supply chain is formed by chaining the Acquirer and Su pplier through the PROMCODE interface Scope of time: Assume the plan is completed and the pr oject scope is defined, which implies that scope definiti on including planning is out of scope of PROMCODE Acquirer Organization A 33

Supplier Acquirer Organization Bn * Supplier * Organization Cnm All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Use Cases and Scenarios Deployment Patterns and High-level Scenario Deployment Pattern A Deployment Pattern A is appropriat Supplier Acquirer e for PROMCODE PROMCODE Dashboard PROMCODE Usage Conditions Supplier 1 C P Assumption Assumption The The Acquirer and Suppliers use diff erent erent PM PM tools tools including including Excel Excel of of di fferent fferent schema. schema. Use Use of

of REST REST High-level High-level Scenario Scenario Supplier Supplier pushes pushes aa report report in in PROM CODE CODE resources resources to to a PROMCODE Provider Provider deployed deployed in in aa Web Web server. server. Acquirer Acquirer collects collects the the reports reports from from t he he PROMOCDE PROMOCDE Provider Provider as as aa PRO PRO MCODE MCODE Consumer, Consumer, and and presents presents t he he project project status status on on its its dashboard. dashboard. () () 34 Tool S1 S Push Tool Pull (Tool A) (Web Report Report Service)

P: Provider, C: Consumer Deployment Pattern B Supplier Acquirer Push P/C Deployment Pattern C Supplier P Acquirer Pull C All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Use Cases and Scenarios Use Cases (Top Level) Use vocabulary practically common in project management in contracted delivery Consistent with global standards: PMBOK, ISO 21500:2012 Project Initiation and Planning Project Execution Acquirer Supplier Project Closing 35 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture

Architecture Committee, Committee, 2014-2015 2014-2015 Use Cases and Scenarios Use Cases: Project Execution Use vocabulary practically common in project management in contracted delivery Consistent with global standards: PMBOK, ISO 21500:2012 Project Execution and Control Project Start Status Reporting Acquirer Status Aggregation Supplier Project Closing 36 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Use Cases and Scenarios Use Cases: Project Execution Use vocabulary practically common in project management in contracted delivery Consistent with global standards: PMBOK, ISO 21500:2012 Project Execution Schedule Problem Quality Problem Acquirer Supplier Re-schedule/Re-planning 37 All All Rights Rights Reserved, Reserved, Copyright

Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Use Case Project Start with PROMCODE [Nov. 25] Preconditions Scenario An acquirer registers Project ID, Project plan, and Mappi ng Rules to the PROMCODE Consumer. The acquirer generates a data in the PROMCODE model with the PROMCODE Consumer and stores it to a DB. A supplier registers the Project ID, Project Plan, and Ma pping Rules to the PROMCODE Provider. 38 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Use Case Project Execution with PROMCODE [Nov. 25/Dec. 10] Preconditions The The acquirer and supplier respectively register Project ID, Project pla n, n, and and each each Mapping Mapping Rules Rules to to the the PROMCODE. PROMCODE. The The supplier agreed to push the Report to the PROMCODE Provider on th ee Web Web until

until the the specified specified date date and and time. time. The The acquirer and suppliers agreed to the schema of the Report to be re ported ported from from suppliers to the acquirer. Scenario 39 A A supplier supplier registers registers its Report data to the PM tool S1. The The supplier converts the Report from from the the PM tool S1 to the PROMCOD E E resources. resources. The The supplier pushes pushes the the Report Report in the PROMCODE schema to the PRO MCODE MCODE Provider Provider on on the the Web. Web. The The Acquirer, a PROMCODE Consumer, Consumer, pulls pulls the the collection of Reports Reports from from the the PROMCODE PROMCODE Providers. The The Acquirer converts converts the the collection of the Reports in the PROMCODE resources resources to to the the PM PM tool

tool A. A. The The Acquirer reviews the Report on the PM tool A. A. All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Use Case Project Execution with PROMCODE Review and Actions for Schedule Problems [Dec. 24] Schedule Delay 1. Reviews the difference and raises a concern if the following is obse rved. 1. 1. No No progress progress from from the the previous previous report report 2. 2. Risk Risk of of not meeting a schedule emerges with the current pace of progr ess. ess. May May use use past past data data on on productivity productivity to to project project risk. risk. 2. PM-A interacts with PM-S on further update. 1. 1. Reasons Reasons for for delay

delay 2. 2. Outlook Outlook of of meeting meeting a schedule. schedule. 3. Based on the interaction, PM-A takes one of the following actions. 1. 1. 2. 2. 3. 3. No No formal formal action, action, but with with notice notice on on the the situation situation to to monitor. monitor. Raise Raise an an issue issue on on the the situation and create actions actions Escalate Escalate to to stakeholders for possible possible plan plan change. change. 4. If it is necessary, plan will be changed [See details in Plan Chang e scenario] 40 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee,

Committee, 2014-2015 2014-2015 Use Case Project Execution with PROMCODE Review and Actions for Schedule Problems [Dec. 24] Schedule Delay 1. Reviews the difference and raises a concern if the following is obse rved. 1. 1. No No progress progress from from the the previous previous report report 2. 2. Risk Risk of of not meeting a schedule emerges with the current pace of progr ess. ess. May May use use past past data data on on productivity productivity to to project project risk. risk. 2. PM-A interacts with PM-S on further update. 1. 1. Reasons Reasons for for delay delay 2. 2. Outlook Outlook of of meeting meeting a schedule. schedule. 3. Based on the interaction, PM-A takes one of the following actions. 1. 1. 2. 2. 3. 3.

No No formal formal action, action, but with with notice notice on on the the situation situation to to monitor. monitor. Raise Raise an an issue issue on on the the situation and create actions actions Escalate Escalate to to stakeholders for possible possible plan plan change. change. 4. If it is necessary, plan will be changed [See details in Plan Chang e scenario] 41 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Use Case Project Execution with PROMCODE Review and Actions for Quality Problems [Dec. 10] Quality Concern 1. PM-A compares previous report and current report and highlights t he difference. 2. Reviews the difference and raises a concern if the progress is not sufficient and there is a risk of not meeting quality goal. 3. PM-A interacts with PM-S on further update. 1. 1. 2. 2. 3.

3. Reasons Reasons of of the the current current problem problem Outlook Outlook of of meeting meeting aa goal goal Assess Assess the the impact impact to to the the overall overall project. project. 4. Based on the interaction, PM-A takes one of the following actions. 1. 1. Raise Raise an an issue issue on on the the situation situation and and create create actions actions 2. 2. Escalate Escalate to to stakeholders stakeholders for for possible plan plan change. change. 5. If it is necessary, actions will be taken place [see details in Plan C hange scenario] 42 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange

Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Use Case Project Execution with PROMCODE Review and Actions for Quality Problems [Dec. 10] Quality Concern 1. PM-A compares previous report and current report and highlights t he difference. 2. Reviews the difference and raises a concern if the progress is not sufficient and there is a risk of not meeting quality goal. 3. PM-A interacts with PM-S on further update. 1. 1. 2. 2. 3. 3. Reasons Reasons of of the the current current problem problem Outlook Outlook of of meeting meeting aa goal goal Assess Assess the the impact impact to to the the overall overall project. project. 4. Based on the interaction, PM-A takes one of the following actions. 1. 1. Raise Raise an an issue issue on on the the situation situation and and create create actions actions 2. 2. Escalate Escalate to to stakeholders stakeholders for

for possible plan plan change. change. 5. If it is necessary, actions will be taken place [see details in Plan C hange scenario] 43 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Use Case Project Execution with PROMCODE Plan Change[Dec. 10] About Plan Change: Plan change may change ScopeItem ScopeItem including including PlannedSize, PlannedSize, and and entities entities in in the the ScopeItem ScopeItem WorkItem WorkItem including including PlannedEndDate, PlannedEndDate, and and Artifact Artifact Scenario of Plan Change [Change of ScopeItem] 44

The The Acquirer Acquirer determines to change the ScopeItem The The Acquirer Acquirer notifies the changes of ScopeItem and associated new plan t o o appropriate appropriate Suppliers. Suppliers. The The Supplier Supplier reviews reviews the the new new ScopeItem and and associated associated new new plan, plan, and and not ify ify its its agreement to the Acquirer. The The Acquirer Acquirer and Supplier get agreed. The The Acquirer Acquirer set the the new new plan plan to to the the plan. plan. The The Acquirer Acquirer and Supplier review the ScopeItem revised, and associated WorkItem WorkItem if necessary All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Use Case Publishing Issue(s) with PROMCODE [Nov. 25]

Precondition Acquirer creates an instance of IssueCollection. Scenario A Supplier registers an Issue(s) to the PROMCODE Pr ovider. The PROMCODE provider notifies the registration of the Issue(s) to the Acquirer. The Acquirer, a PROMCODE Consumer, pulls the publish ed Issue(s) from the PROMCODE Provider. The Acquirer reviews the Issues. 45 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Use Case Project Start Revised [Nov. 11] Preconditions Obsolete Project Project Plan is determined and agreed by both acquirer and supplier. The The size size measure measure and and its its unit unit of of Scope Scope are are respectively respectively defined defined by by Mes Mes ureType ureType and and UnitType , which are specified by the URIs. The The measure measure and and its its unit

unit of of the the Artifact Artifact are are respectively respectively defined defined by by Mes Mes ureType ureType and and UnitType , which are specified by the URIs. Scenario Acquirer Acquirer creates a Project resource, and sets the measure and its unit of project project scope scope to to typeOfMeasure typeOfMeasure and unitOfMeasure of Project. Acquirer Acquirer creates a ScopeItem. Supplier Supplier creates creates an Artifact Artifact and its subclasses to meet the ScopeItem, a nd nd allocates allocates the the Artifacts Artifacts to the ScopeItem. ScopeItem. Supplier Supplier creates creates a set of of WorkItem to to produce produce the the Artifacts, Artifacts, and and allocate allocate ss the the WorkItems to the Artifacts. Supplier Supplier appoints appoints a Person as a representative to the ScopeItem. 46 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project

Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Use Case Project Execution with PROMCODE Simple Use Case User User roles Project Project manager manager of of acquirer acquirer (PM-A) (PM-A) Project Project manger manger of of supplier supplier (PM-S) (PM-S) Pre-condition Pre-condition Obsolete A A legal legal contract contract to to bind bind an an acquirer acquirer and and aa supplier supplier is is handled handled separately. separately. There There is is no no cascading

cascading of of acquirer-supplier acquirer-supplier relationships. relationships. Project Project environment environment of of an an acquirer acquirer and and aa supplier supplier are are not not shared; shared; i.e., i.e., project project environm environm ent ent of of aa supplier supplier is is not not accessible accessible to to PM-A PM-A and and therefore, therefore, project project information information needs needs to to be be sent sent to to PM-A PM-A for for project project management management by by an an acquirer. acquirer. Steps Steps 1. 1. PM-A PM-A and and PM-S PM-S work work together together to to define define ScopeItems,

ScopeItems, WorkItems WorkItems and and artifacts artifacts as as aa plan plan and and establish establish agreement agreement between between them. them. Details Details of of steps steps in in establishing establishing agreement agreement may may vary vary and and we we will will not not specify specify them them further. further. .. 2. 2. PM-S PM-S updates updates on on regular regular basis basis actual actual values values of of properties properties of of WorkItems WorkItems and and of of measur measur ements ements and and measures measures attached attached to to artifacts. artifacts. This This can can be

be done done by by PM-A PM-A requesting requesting aa report report to to PM-S PM-S or or by by PM-S PM-S posting posting aa report report to to an an agre agre ed location. ed location. 3. 3. PM-S PM-S sends sends an an update update as as aa Report Report to to PM-A. PM-A. 4. 4. PM-A PM-A reviews reviews updates updates and and takes takes actions actions such such as as such such as as creating creating and and managing managing Issue Issue s. s. In In particular, particular, 1. 1. Review Review the the possibility possibility of of schedule schedule delay

delay 2. Review Quality 2. Review Quality Details Details of of these these will will be be elaborated elaborated in in the the next next pages. pages. 5. 5. Repeat Repeat Steps Steps 2-4 2-4 as as necessary necessary 6. 6. Conduct Conduct acceptance acceptance review review and and close close aa project project 47 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Resources Associated with the Scenarios 48 All All Rights Rights Reserved,

Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Resources Created before Start Project(1/3)[Nov. 11] Resource Project Attributes 49 Value Identifier Acquirer Title Acquirer Description Acquirer plannedStartDate Acquirer plannedEndDate Acquirer metricOfScopeItemSize Acquirer URI unitOfScopeItemSize Acquirer URI Resource Plan Creator

Attributes Creator Identifier Acquirer Title Acquirer Date Acquirer belongsTo Acquirer collects Acquirer Value All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Resources Created before Start Project(2/3)[Nov. 11] Resource ScopeItem Attributes Identifier Acquirer Title Acquirer Description Acquirer

plannedSize Acquirer isPartOf Acquirer Resource WorkItem 50 Creator Attributes Creator Identifier Acquirer Title Acquirer Description Acquirer plannedStartDate Acquirer plannedEndDate Acquirer isPartOf Acquirer requiredBy Acquirer representedBy Supplier Value Value All

All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Resources Created before Start Project(3/3)[Nov. 11] Resource Artifact Attributes Identifier Acquirer Title Acquirer Description Acquirer isPartOf Acquirer producedBy Acquirer Resource Target Attributes 51 Creator Identifier Acquirer Title Acquirer determines

Acquirer designedFor Acquirer Resource Measure Creator Attributes Creator Identifier Acquirer Title Acquirer Value Acquirer typeOfMeasure Acquirer unitOfMeasure Acquirer Value Value Value All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Resources Created/Changed in Status Reporting(1/2)[Nov. 11]

Resource Report Attributes Identifier Acquirer Title Supplier Date Supplier correspondsTo Supplier belongsTo Supplier collects Supplier Resource WorkItem Attributes Supplier actualEndDate Supplier Attributes Date Resource Measure 52 Creator actualStartDate Resource Measurement Creator Value

Value Supplier Attributes Value Creator Value Creator Value Supplier All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Resources Created/Changed in Status Reporting(2/2)[Nov. 11] Resource Attributes IssueCollection Identifier Acquirer Title Supplier Date Supplier collects Supplier Resource Issue

53 Creator Attributes Creator Identifier Acquirer/ Supplier Title Acquirer/ Supplier raisedDate Acquirer/ Supplier Description Acquirer/ Supplier Value Value All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Resources Created/Changed in Project Closing[Nov. 11] Resource Project Resource ScopeItem 54

Attributes actualEndDate Attributes actualSize Creator Value Supplier Creator Value Supplier All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Basic Vocabulary 55 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Vocabulary [2014/12/23] acquirer: acquirer: stakeholder stakeholder that acquires acquires or or procures procures aa product product or

or service service from from aa supplier supplier [ISO/IEC [ISO/IEC 15288:2002] 15288:2002] measure measure (noun): (noun): variable variable to which a value value is assigned as the result of of measuremen measuremen t.t. [ISO/IEC 15939: 2007] 2007] NOTE: NOTE: The The plural plural form form measures measures is is used used to to refer refer collectively collectively to to base base measures, measures, derived derived measures measures aa nd nd indicators. indicators. measure measure (verb): (verb): make a measurement. [ISO/IEC 14598-1:1999] measurement: measurement: set of operations having the object of determining a value of a meas ure. ure. [ISO/IEC [ISO/IEC 15939: 2007] NOTE NOTE Adapted Adapted from from the the International International Vocabulary Vocabulary of of Basic Basic and and General

General Terms Terms in in Metrology, Metrology, 1993. 1993. project: project: aa temporary endeavor endeavor undertaken undertaken to to create create aa unique unique product, product, service, service, or or re re sult. sult. [PMBOK [PMBOK V5] V5] quality quality measure: measure: measure that is defined as a measurement function function of of two two or mor ee values values of of quality measure measure elements elements [ISO/IEC [ISO/IEC 25010: 25010: 2011] 2011] scope: scope: The The sum sum of of the the products, products, services services and and results results to to be be provided provided as as aa project. project. S S ee ee also also project project scope and product scope.[PMBOK V5, 2013] supplier: supplier: organization

organization or or individual that that enters enters into into an an agreement agreement with with the the acquirer acquirer ff or or the the supply supply of of a product product or or service. service. [ISO/IEC [ISO/IEC 15939: 15939: 2007] 2007] 56 NOTE NOTE 1: 1: Other Other terms terms commonly commonly used used for for supplier supplier are are contractor, contractor, producer, producer, seller seller and and vendor. vendor. NOTE 2: acquirer and supplier be of organization. NOTE 2: The The acquirer and the the supplier may may be part part of the

the same same organization. All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 Vocabulary References [2014/12/23] [ 1] P. Bourque and R.E. Fairley (eds.), Guide to the Software Engineering Body of Knowledge, Version 3.0, IEEE Computer Society, 2014, http://www.swebok.org. [ 2] ISO/IEC 14598-1:1999, Information technology - Software product evaluation - Part 1: General overview. [ 3] ISO/IEC 15288:2002, Systems engineering - System life cycle processes. [ 4] ISO/IEC 15939:2007, Systems and software engineering - Measurement process. [ 5] ISO/IEC 25010:2011, Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - System and software quality models. [ 6] ISO, International Vocabulary of Basic and General Terms in Metrology, 1993. [ 7] PMI, A Guide to Project Management of Body Of Knowledge (PMBOK Guide), Fifth Edition, 2013. 57 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015 References [ 1] R. Cyganiak, et al. (eds.), RDF 1.1 Concepts and Abstract Syntax, W3C Recommendation, 25 February 2014, http://www.w3.org/TR/2014/REC-rdf11-concepts20140225/#dfn-iri [ 2] R. Cyganiak, An RDF Design Pattern: Inverse Property Labels, Jun. 2006, http://richard.cyganiak.de/blog/2006/06/an-rdf-design-pattern-inverse-property-labels/. [ 3] A. G. Ryman, et al., OSLC Resource Shape: A Language for Defining Constraints on Linked Data, Proc. of the WWW2013 Workshop on Linked Data on the Web (LDOW 2013), May 2013, 5 pages,

http://events.linkeddata.org/ldow2013/papers/ldow2013-paper-02.pdf. [ 4] A. G. Ryman, Vocabulary Annotation Vocabulary, Sep. 2013, http://open-services.net/wiki/core/Vocabulary-Annotation-Vocabulary/. [ 5] A. G. Ryman, Resource Shape 2.0, W3C Member Submission, Feb. 2014, http://www.w3.org/Submission/2014/SUBM-shapes-20140211/. [ 6] Open Services for Lifecycle Collaboration Change Management Specification, Version 3.0, http://open-services.net/wiki/change-management/Specification-3.0/ 58 All All Rights Rights Reserved, Reserved, Copyright Copyright Next-Generation Next-Generation Project Project Management Management Data Data Exchange Exchange Architecture Architecture Committee, Committee, 2014-2015 2014-2015

Recently Viewed Presentations

  • Chapter 13 - The Age of Exploration

    Chapter 13 - The Age of Exploration

    Gold. They brought back spices used to preserve & flavor food, and precious metals. Made a lot of money through trade of these goods. Glory. They wanted the glory of discovering new lands, new products and going on exciting adventures....
  • Sample Problem 5.1 Radiation Particles Identify and write

    Sample Problem 5.1 Radiation Particles Identify and write

    Identify and write the symbol for the type of radiation that has a mass number of zero and a 1+ charge. Answer. A positron, , has a mass number of 0 and a 1+ charge. ... Step 4 Set up...
  • WEDNESDAY APRIL 19TH, 2017 Learning Target; I can

    WEDNESDAY APRIL 19TH, 2017 Learning Target; I can

    The North Atlantic Treaty Organization consisting of the US, Canada, and Western Europe becomes the first peace-time alliance in US history. ... I can explain what led to the Red Scare and how McCarthyism affected Americans. Bomb Shelter. Air system...
  • Inequality Measures - iprcc.org.cn

    Inequality Measures - iprcc.org.cn

    Inequality Measures Celia M. Reyes Introduction to Poverty Analysis NAI, Beijing, China Nov. 1-8, 2005 Chapter 6 Inequality Measures Celia M. Reyes July 6, 2004 Definition of Inequality Poverty measures previously discussed depend on the average level of income or...
  • Memory - McMurray VMC

    Memory - McMurray VMC

    mcmurray. website. Journal Entry: After watching the 2 Ted Talks, reflect on the one you liked the most and why. What have you learned that can be applied to your life. Be specific. Two Types of Stress. ... Carla McMurray...
  • IB PHYSICS DATA BOOKLET REVIEW CORE ELECTRICTY Topic

    IB PHYSICS DATA BOOKLET REVIEW CORE ELECTRICTY Topic

    charge comes in two forms + and - charge. is a scalar quantity charge. is quantized charge . is conserved in a closed system charging
  • Inclusive Assessment - Ahead

    Inclusive Assessment - Ahead

    (Disability Act, 2005) Inclusive Assessment Disabled Students All Students Contingency Approach "special arrangements" such as extra time, own room, etc.) which is essentially a form of assimilation into an existing system Alternative Approach (e.g., a viva voce instead of a...
  • Inflammatory Bowel Disease

    Inflammatory Bowel Disease

    Granny = Granulomatous (non caseating) Skipping - Skip lesions; Often with RECTAL SPARING. Cobblestone appearance - ulcers seperated by areas of normal tissue. ... Uveitis. Clubbing. Get into 2 groups. Complete first 3 boxes on form based on what we...