May 10, 2001An Overview of the Princeton University Web - DEMAND 1 uPortal and DEMAND  History - uPortal consortium started 12/99 as part of JA- SIG. Mission is to build an open architecture framework for a free university portal. - Demand (DEpartmental MANagers portal) is a prototype uPortal that will address that one constituency

May 10, 2001An Overview of the Princeton University Web - DEMAND 2 Elements of a Portal  Adaptive, Secure Framework  Customization  Personalization  Desktop Replacement

May 10, 2001An Overview of the Princeton University Web - DEMAND 3 Portal Choices  Free (with strings)  Buy a tool  Build our own  Use a vertical (or verticals)  Consortium

May 10, 2001An Overview of the Princeton University Web - DEMAND 4 uPortal and DEMAND  Rationale for method –Open architecture, no vendor lock-in, no purchased code. –Follow J2EE specs to insure scalability, platform independence –Write in java

May 10, 2001An Overview of the Princeton University Web - DEMAND 5 uPortal and DEMAND  Initial implementation –Currently at version 1.5 –1 ½ years

May 10, 2001An Overview of the Princeton University Web - DEMAND 6 uPortal and DEMAND  Resources for uPortal –About 10 schools –one hired consulting group –total FTEs are approx. 5-6  Resources for Demand - One customer, one technical person

May 10, 2001An Overview of the Princeton University Web - DEMAND 7 uPortal and DEMAND uPortal and DEMAND  uPortal Project management –Technical project mgr and a ½ time project leader. Managed outside of Princeton. Group meets approx 1/mo.  Volunteers for roles through JA-SIG  Demand Project management –Follows P2k methodology. Customer lead and one programmer.

May 10, 2001An Overview of the Princeton University Web - DEMAND 8 uPortal and DEMAND uPortal and DEMAND  Project maintenance – uPortal –Coordinated through JA-SIG –Source code at Univ. of Delaware  Project maintenance – Demand –framework will be maintained by ASIG –content?

May 10, 2001An Overview of the Princeton University Web - DEMAND 9 uPortal and DEMAND  Project success - Not yet met all our goals - Have made considerable progress - Have made considerable progress - Believe prototype (due in Aug) will be successful. - Believe prototype (due in Aug) will be successful.

May 10, 2001An Overview of the Princeton University Web - DEMAND 10 uPortal and DEMAND  Futures –We are forming a steering committee of departmental mgrs to define needs. This should be done for every constituency serviced by a university portal. –We need university policy regarding vendor specific vertical portals (such as PeopleSoft) vs a horizontal portal.

May 10, 2001An Overview of the Princeton University Web - DEMAND 11DEMAND