Navigation:
Documentation
Archive



Page Tree:

Child pages
  • BTP Work Plan - Phase One

This wiki space contains archival documentation of Project Bamboo, April 2008 - March 2013.

Skip to end of metadata
Go to start of metadata

8. Work Plan

We have provided two high-level work plans below; a more detailed plan is provided in Appendix 1. The first view below summarizes major deliverables for each quarter by area of work. The second highlights a smaller number of milestones over the 18-months of the project.


Work Spaces

Corpora Space

Scholarly Services

Services Platform

Shared Services Lifecycle

Collections Interoperability

Q1

Model & design adaptations to base technology

--

Services design; articulate platform support requirements

“Hello World” services; core & utility (support) service design

Evolve toolkit and Lifecycle documents; engage expert review

Refine functional scope & standards adoption criteria

Q2

Implement user interfaces and workflow

Develop functional descriptions for 3-6 proposed Scholarly Applications

Implement first iteration of Scholarly Services

Initial core & utility  service implementation

Incorporate lessons & requirements from Scholarly Services & Platform teams

Develop test protocols for interoperability standards compliance; draft standards profile

Q3

Integrate with Services Platform

Select 2-4 candidates for preliminary proposal development

Initial deployment on Platform; functional and technical testing

Initial production BSP running scholarly services; refine core & utility services

Community review and comment; refine toolkit & Lifecycle documents

Refine standards profile; develop compliance tests

Q4

Refine user interface and experience; documentation

Scholar, technical, feasibility review; select 1-2 candidates for refinement

Refine services, establish adoption / engagement teams

Version 1.0 release. Support Scholarly Service & Work Spaces teams

Support adoption; refine toolkit & Lifecycle documents

Refine standards profile; support profile integration in adoption project roadmaps

Q5

Version 1.0 release

Further refinement; roadmaps for funding proposal

Version 1.0 release; support; select services for Phase II development

Platform refinement; support integrations; distributed-Platform roadmap

Version 0.7 Lifecycle release (final for Phase I). Initial mapping for Phase II evolution

Version 1.0 standards profile release; support profile adoption

Q6

Support pilots

Model and initial design for Phase II implementation

Support adoption / engagement; model Phase II services

Support integrations; design distributed-Platform services

Map and draft/pilot Phase II toolkit & Lifecycle

Support and assess profile adoption; map Phase II evolution

13. Appendix 1: Detailed Work Plan

Work to be Completed in the Planning Phase

We have built a work plan on the accomplishments of the Project Bamboo Planning Phase, supported by a major grant from the Andrew W. Mellon Foundation.  Planning and preparation will continue through the completion of the Planning Phase, in September 2010.  Planning-phase precursors to the work plan are listed as background and context, below:

  • Work Spaces: Develop specification and technology-adaptation roadmaps
  • Corpora Space: Identify scholars for Phase I design activities
  • Scholarly Services: Model Scholarly Services to be deployed in Phase I
  • Services Platform: Articulate technical requirements
  • Services Platform: Assemble, configure, and deploy Platform infrastructure technology (v0.1; cf. Technical Addendum, Appendix 1)
  • Services Platform: Identify and model candidate Core and Utility services (cf. Technical Addendum, Appendix 1)
  • Services Lifecycle: Assemble, configure, and ‘test drive’ an integrated developer environment (IDE)
  • Services Lifecycle: Draft and publish scope and elements of a proposed Bamboo Shared Services Lifecycle
  • Services Lifecycle: Select, deploy, and configure collaborative development tools (e.g., code repository, issue tracker)
  • Collections Interoperability: Draft and publish scope
  • Collections Interoperability: Identify candidate standards, protocols, and specifications

Legend:

In order to fit information in a compressed table, the following acronyms are used in the Work Plan:

BSP = "Bamboo Services Platform" (a.k.a. "Platform")
BSSL = "Bamboo Shared Services Lifecycle" (a.k.a. "Lifecycle")
CI = "Collections Interoperability"
EoQ = "End of Quarter"
Phase I = first, 18-month phase of implementation described in this Project Bamboo Technology Proposal, Oct 2010 – Mar 2012
Phase II = a second 18-month phase of implementation, continuing Phase I effort, Apr 2012 – Sep 2013
SDK = "Software Development toolKit" – a set of tools to facilitate coding, deployment
UI = "User Interface, i.e., the screens through which a user accesses the functionality of an application, tool, etc.
v#.# = version numbers; v1.0 signifies a full, production release, while lesser numbers signify fractional progress toward production

Project Bamboo Technology Work Plan: Phase I (Oct 2010 – Mar 2012)

Oct-Dec 2010 (Q1)

Jan-Mar 2011 (Q2)

Apr-Jun 2011 (Q3)

Jul-Sep 2011 (Q4)

Oct-Dec 2011 (Q5)

Jan-Mar 2012 (Q6)

1. Scholarly Work Spaces

Formalize Work Spaces and Tool & Service Registry development roadmaps. Model and design adaptations to base technology (e.g., to UI, to research task workflows, to consumption of Platform services). Develop Work Spaces project requirements for scholar/student pilots.

EoQ: Adaptation roadmap, models and design. Requirements for pilots.

Implement UI and research task workflows. Engage scholar community for user experience feedback; identify UI and workflow refinements to be implemented in v1.0 Work Spaces. Model and design Tool & Service Registry data store and services. Solicit proposals for Work Spaces pilots.

EoQ: UI and workflow functionality complete to v0.6. Tool & Service Registry design complete.

Implement service integration with Platform; refine UI & research task workflow functionality based on user experience feedback to-date. Engage scholar community for user experience feedback; identify further refinements to be implemented in v1.0 Work Spaces. Implement and test Tool & Service Registry functionality. Review and select Work Spaces pilots, support development of pilot roadmaps.

EoQ: Service integration functionality complete to v0.6; UI and workflow functionality complete to v0.9. Tool & Service Registry implemented to v0.8. Pilots selected.

Complete Phase I Work Spaces and Tool & Service Registry functionality to release-candidate stage. Engage scholar community for final round of feedback; identify final refinements to be implemented in v1.0. Support evolving pilot roadmaps; document; establish pilot teams.

EoQ: Work Spaces, Tool & Service Registry functionally complete to v1.0-rc.

Complete Phase I Work Spaces and Tool & Service Registry functionality for v1.0 release. Refine documentation. Support pilots, monitoring teams. Continue to solicit feedback from scholarly community, initiate mapping of Work Spaces evolution roadmap.

EoQ: Release v1.0 Scholarly Work Spaces and Tool & Service Registry.

Support pilots; assess applied use of Bamboo standards, services, and processes. Articulate roadmap for evolution of Scholarly Work Spaces and Tool & Service Registry technology in Phase II.

EoQ: Assessment of applied use of Bamboo standards, services, and processes in this area. Roadmap for evolution of Scholarly Work Spaces technology in Phase II

2. Corpora Space

--

Engage scholars in disciplinary clusters to identify broadly useful corpora-centered functionality applicable to humanities scholarship, building on prior efforts.
Recruit 3-6 small groups to compose white papers with functional descriptions of 3-6 potential corpora-centered Applications.

EoQ: 3-6 teams  recruited; broad scope for each white paper defined.

Develop and publish white papers for comment, critique, and technical review. Revise white papers to reflect feedback.

EoQ: 3-6 white papers reviewed by scholars and technologists; revised by writing teams.

Leadership groups to select 2 white papers for further development into preliminary proposals for corpora-centered Applications. Publish proposals for comment, critique, and technical review.
Revise & refine proposals based on initial round of critique and technical review. Publish revised proposals for comment, critique, and technical/feasibility review. Further define and refine as necessary.

EoQ: 2 well-defined feasible, technically sound, corpora-centered Applications proposals of prioritized value to humanist scholarship.

Further define and refine proposals (note: descriptions of work to be included in Dec 2011 funding proposal). Publish evolved proposals for comment, critique, and technical review.

EoQ: 2 refined proposals for corpora-centered Applications; descriptions included in December funding proposal.

Develop roadmap, model, and initial design for 2 corpora-centered Applications to be implemented in Phase II of Bamboo implementation.

EoQ: Roadmap, model, and design for 2  corpora-centered Applications for which development funding will be requested.

3a. Scholarly Services on Bamboo Services Platform:
 
Scholarly Services

Evaluate candidate services against expected BSP capabilities; finalize selection of Scholarly Services to be deployed on v1.0 BSP; design Scholarly Services; articulate core/utility service support needs. Develop requirements for adoption/engagement projects.

EoQ: Service model and design near-complete for Scholarly Services slated for BSP 1.0 deployment. Requirements for adoption/engagement projects.

Develop Scholarly Services for deployment on BSP; test and refine service interfaces and Collections Interoperability compliance (as necessary); draft service and contract documentation. Solicit proposals for adoption/engagement projects.

EoQ: Service designs complete; service implementations in-progress (~v0.5 on average).

Deploy initial set of Scholarly Services on the BSP; test and refine; confirm Scholarly Services meet functional requirements and core/utility services deliver necessary support; revise service and contract documentation. Review and select adoption/engagement  projects, support development roadmaps.

EoQ: Services deployed (v0.6), refined (v0.7), tested (v0.8). Service documentation up-to-date for v0.8. Adoption/engagement projects selected.

Promote Scholarly Services to adoption/engagement project teams; establish co-development teams (Scholarly Service developers & service consumers); assist adoption/engagement projects as necessary; refine services; monitor and track issues; identify final revisions to v1.0 services.

EoQ: v0.9 services; adoption/engagement project work plans articulated; final revisions mapped for next  (v1.0) release.

Review and make initial selections of candidate services for Phase II BSP deployment. Partner with adoption/engagement teams to effect initial integrations, monitoring teams. Implement and deploy v1.0 services.

EoQ: In-progress adoption/engagement (variable progress). v1.0 service releases.

Finalize initial scholarly services (v1.0.x); finalize documentation; revise and release Scholarly Services as needed (v1.1). Support adoption/engagement projects; assess applied use of Bamboo standards, services, and processes; finalize selection and model Phase II Scholarly Services.

EoQ: Final Phase I releases of Scholarly Services. Assessment of applied use of Bamboo standards, services, and processes in this area. Evaluation of candidate Phase II services against BSP capabilities; Phase II service models.

3b. Scholarly Services on Bamboo Services Platform:
 
Bamboo Services Platform (BSP)

Implement and deploy “Hello World” services on BSP 0.1 stack. Pilot service development & deployment processes: support Scholarly Services partners in deployments of and calls to services on the BSP. Initiate core and utility service design

EoQ: BSP v0.1.

Refine BSP infrastructure, services, and dev/deployment processes. Respond to issues raised by Scholarly Services partners regarding technologies, tuning, and configuration of BSP. Initiate core and utility service implementation.

EoQ: BSP v0.4.

Deploy BSP 0.7 at a single location shared across partner institutions. Implement, test, and deploy core and utility services. Document BSP and support Scholarly Service deployment and consumption.

EoQ: BSP v0.7, initial core & utility service  implementations.

Deploy BSP 1.0 at a single location shared across partner institutions; refine BSP documentation. Operate BSP 1.0 and continue to support Scholarly Service deployment and consumption.

EoQ: BSP v1.0.

Support and analyze platform use and adoption of BSP by Scholarly Service developers and adoption projects. Assist early adopters with technical issues. Initiate exploration of issues to resolve re: distributed BSP deployment.

EoQ: Architecture described for BSP distributed deployment

Support initial Scholarly Service integrations. Initiate design of services to support distributed BSP deployment. Assess BSP 1.0 adoption and use; make adjustments to BSP.

EoQ: Initial service designs to support distributed BSP deployment. Formal assessment of BSP 1.0.

3c. Scholarly Services on Bamboo Services Platform:
 
Services Lifecycle

Revise initial draft of Bamboo Shared Service Lifecycle (BSSL) documentation; publish second draft; refine candidate Software Developer Kit (SDK); engage experts to review lifecycle vision; identify and draft service contract requirements. Iterate SDK as necessary.

EoQ: Lifecycle docs v0.2 published for review. Fully functional SDK.

Incorporate service lifecycle requirements from Scholarly Services, Collections Interoperability, and BSP; revise lifecycle documentation; publish third draft for community review. Stabilize SDK for Phase I use.

EoQ: Lifecycle docs v0.3 out for review. Stable SDK.

Revise Lifecycle docs to v0.4; shepherd through community review and comment; cycle docs to v0.5; promote adoption of v0.5 for Bamboo service development, deployment, and maintenance. Refine SDK as necessary, and document.

EoQ: Lifecycle docs v0.5. Refined SDK, SDK documentation.

Revise Lifecycle docs to v0.6. Support adoption of BSSL 0.6 across adoption projects during adoption planning phase, establish co-development teams; monitor lifecycle adoption and track issues; suggest revisions to BSSL 0.6. Support adoption of SDK, monitor issues, enrich documentation.

EoQ: Lifecycle docs v0.6 & suggested revisions. Enriched SDK documentation.

Assess Lifecycle v0.6 & SDK adoption and evaluate effectiveness; revise, and release Lifecycle v0.7 docs. Support uptake and monitor issues with Lifecycle v0.7, track changes for Phase II revisions. Update SDK as necessary.

EoQ: Lifecycle docs v0.7 (final for Phase I). Updated SDK and documentation.

Continue to support uptake and monitor issues with Lifecycle docs and SDK during adoption work. Track and fully document proposed changes for Phase II Lifecycle and SDK additions and revisions.

EoQ: Roadmap for evolution of Lifecycle and SDK during Phase II.

4. Collections Inter-operability (CI)
 

Review initial functional scope against user stories & initial BSP and Scholarly Services roadmap; refine functional scope; develop criteria and protocols for standards adoption; propose testing protocols for service contracts and integrations. Develop requirements for adoption projects.

EoQ: Complete identification & selection of key standards; gap analysis.

Initiate development of tests for CI contracts and integrations against stub or initial Scholarly Services; create draft CI profile of standards and specifications for initially scoped degree of collections interoperability; publish draft for review.  Solicit proposals for adoption projects.

EoQ: CI profile v05. Initial compliance levels definitions.

Further testing and refinement of CI; develop content store compliance tests and conformance requirements for the CI profile; revise CI profile and publish for review. Review and select adoption projects, support development of adoption roadmaps.

EoQ: CI profile v0.8; adoption projects selected; initial demonstrations of what levels of compliance mean.

Support integration of CI 0.8 in adoption project roadmaps, establish co-development teams (CI partners & adoption project teams); monitor CI profile adoption and track issues; evaluate compliance and conformance requirements against declared adoptions; iterate to CI v0.9 and map revisions to CI v1.0.

EoQ: CI profile v0.9; mapped revisions for v1.0 (release); begin work on bi-directional content interoperability.

Assess CI profile adoption and evaluate its effectiveness as a Bamboo interoperability profile. Iterate to CI profile v1.0 compliance and conformance specification; support adoption of CI 1.0 in adoption projects, monitoring teams.

EoQ: CI profile v1.0. Assessment of CI profile adoption; REST based tools to partially validate level of compliance (e.g., conformance to a supported metadata application profile).

Continue to support uptake and monitor issues with CI in adoption project work. Track and fully document proposed changes for Phase II CI additions and revisions. Support adoption projects; assess applied use of Bamboo standards, services, and processes.

EoQ: Assessment of applied use of Bamboo standards, services, and processes in this area. Roadmap for CI Phase II.


This right-side column is an artifact of "old-style" navigation. Please remove sections, columns, and content of the right-side column when this page is next edited. Cf. the Wiki navigation changes - July 2011 page for a 'how-to' on removing old-style page markup.