uportal 3: introduction strategic goals –configuration flexibility rendering mechanisms http...

4
uPortal 3: Introduction Strategic goals configuration flexibility • rendering mechanisms • HTTP parameter generation/processing mechanisms • data layer implementations long-term maintenance • isolated, individually configured groups of components • transparent, sparse coupling Tactical goals JSR168 support SAKAI integration uPortal2 support Complete WSRP integration

Upload: tracey-bailey

Post on 01-Jan-2016

215 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: UPortal 3: Introduction Strategic goals –configuration flexibility rendering mechanisms HTTP parameter generation/processing mechanisms data layer implementations

uPortal 3: Introduction

• Strategic goals– configuration flexibility

• rendering mechanisms• HTTP parameter generation/processing mechanisms• data layer implementations

– long-term maintenance• isolated, individually configured groups of components• transparent, sparse coupling

• Tactical goals– JSR168 support– SAKAI integration– uPortal2 support– Complete WSRP integration

Page 2: UPortal 3: Introduction Strategic goals –configuration flexibility rendering mechanisms HTTP parameter generation/processing mechanisms data layer implementations

uPortal 3: Roadmap

• Sakai Beta – June 2005– Implements minimum Sakai Phase II requirements

• 3.0 Beta: non-2.x users – August 2005– Completes Sakai integration requirements– Completes core features for new uPortal Adopters

• 3.0 Final: Upgrades – September/October2005– Migration tools for existing 2.x users

• IChannel adapter, DB migration• Requirements not finalized at this time

Page 3: UPortal 3: Introduction Strategic goals –configuration flexibility rendering mechanisms HTTP parameter generation/processing mechanisms data layer implementations

uPortal 3: Dependencies

• uPortal– 3.0 resources on 3.0– Support from 2.x resources– Define upgrade/migration tools

• Sakai– Refining SAKAI requirements past June release– Development

• WSRP consumer, deployment testing• alternative (to uP2) skin/structure• OSID Authentication/Authorization

• Testing– Identify resources/institutions– QA and Performance Test

Page 4: UPortal 3: Introduction Strategic goals –configuration flexibility rendering mechanisms HTTP parameter generation/processing mechanisms data layer implementations

uPortal 3: Project Tracking

• JIRA– Tasks– Estimates (Design through Integration Test)– Due Dates– Status

• Confluence– Documentation– Other Collaboration