Track the Status of a Set of Pages Shared by Different Users and/or Teams

Different Kuali Teams may share interest in a set of specifications (e.g. Use Cases are generated and maintained by the Use Case team but are reviewed and assessed by the Application Design Team) and they may internally divide up pieces of a specification. The following is an example of using wiki labels and the "reporting" macro to dynamically generate a cross-reference matrix reflecting the various labels on wiki pages that may come from different teams or reflect various milestones. The example below simulates the review of Use Cases  that have been labeled as having been created by the Use Case team (labeled "uc"), completed by the Use Case team (labeled "uc-completed"), in review by the Application Design team (labeled "app-design-ip"),  review completed by the Application Design team (labeled "app-design-completed") and revisions completed by the Use Case team.  The Matrix below is completely dynamic based on the labels used by the wiki pages so that the appropriate users simply have to update the wiki page labels to update the status matrix.

Questions: Should there be A) a single status label so the "furthest" progress is the only thing that is noted (as in UC Proposer submits proposal for review), or B) multiple status labels that indicate the extent of the progress (as in UC Staff member searches for a Course)?

Status of Create Course Lifecycle

Name	Use Case In Progress	Completed Use Case	In Review by App Design	Review completed by App Design Team	Use Case Revisions Completed
UC Collaborate on Course Proposal
UC Create Course Proposal
UC Proposer submits proposal for review
UC Staff member searches for a Course

Track the Usage of a Component Referred to by Different Teams

Kuali Teams will need the ability to easily track the use of specifications, particularly those that are re-used in different contexts. The following is an example using outgoing links to track the "path" of Use Cases in the  Create a Course "Melange" from the high level Use Cases through to their implementation in application code.  The result should allow Kuali team members to see where various components are used (and re-used).  In the static example below, the Create a Course Melange is linked to the "UC Collaborate on Course Proposal" Use Case which has been converted into the "FS Collaborate" Functional Specification which refers to a Service "SVC Find Person" and a UI component "UI Select Person to Collaborate with".

 The following is a dynamic rendering of all of the outgoing links from every component through to the end of the chain. 

• Create a Course Melange —
  • UC Collaborate on Course Proposal —
    • FS Collaborate —
      • SVC Find Person —
        Service Operation Find Person
      • UI Select Person to Collaborate with — User Interface to Select Person
  • UC Create Course Proposal —
    • FS Create Course
  • UC Proposer submits proposal for review —
    • FS submit course proposal for review —
      • SVC submit course proposal for review
      • UI submit course proposal for review
  • UC Staff member searches for a Course —
    • FS Search for Course —
      • SVC Search for Course
      • UI Search for Course

Test Pages referenced in these examples

Code Find Person (Sandbox) Labels: code, completed, ks-test

Create a Course Melange (Sandbox) — {outgoing-links:excerpt=true} Labels: uc, melange, scenario, ks-test

FS Collaborate (Sandbox) — {outgoing-links:excerpt=true} Labels: fs, melange-create-course, completed, ks-test

FS Create Course (Sandbox) Labels: ks-test

FS Search for Course (Sandbox) — {outgoing-links:excerpt=true} Labels: fs, melange-create-course, completed, ks-test

FS submit course proposal for review (Sandbox) — {outgoing-links:excerpt=true} Labels: fs, melange-create-course, completed, ks-test

FS User Chooses Course (Sandbox) Labels: ks-test

Kuali Project Tracking and Progress Tools (Sandbox) Labels: ks-test

SVC Find Person (Sandbox) — Service Operation Find Person Labels: melange-create-course, svc, completed, ks-test

UC Collaborate on Course Proposal (Sandbox) — {outgoing-links:excerpt=true} Labels: melange-create-course, uc, completed, ks-test, uc-ip

UC Create Course Proposal (Sandbox) — {outgoing-links} Labels: uc, melange-create-course, ks-test, uc-ip

UC Proposer submits proposal for review (Sandbox) — {outgoing-links:excerpt=true}{outgoing-links} Labels: melange-create-course, uc, ks-test, uc-revised

UC Staff member searches for a Course (Sandbox) — {outgoing-links:excerpt=true}{outgoing-links} Labels: ks-test, uc, melange-create-course, completed, app-design-completed, uc-revised, app-design-ip, uc-ip

UI Select Person to Collaborate with (Sandbox) — User Interface to Select Person Labels: ks-test, ui

Use Case Status (Sandbox) Labels: ks-test

The Use Cases (listed below) have the following labels: Use Case 1: uc; Use Case 2: uc, app-design-ip; Use Case 3: uc,uc-completed, app-design-ip, app-design-completed; Use Case 4: uc; Use Case 5: uc, uc-completed.  The matrix above is generated dynamically based on these labels alone.