200 likes | 355 Views
PUMA. Fall 2001 EOSP. Dec. 10, 2001. Agenda. Introduction Project Organization & Process Technical Challenges Lesson Learned Next Semester. Who we are. PUMA P ortable U biquitous M iddleware A rchitecture Members Hernan Eguiluz, Venkat Govi,You Jung Kim,
E N D
PUMA Fall 2001 EOSP Dec. 10, 2001
Agenda • Introduction • Project Organization & Process • Technical Challenges • Lesson Learned • Next Semester
Who we are • PUMA Portable Ubiquitous Middleware Architecture • Members Hernan Eguiluz, Venkat Govi,You Jung Kim, Adrian Sia. Katherine Langdon (Technical writer) • Mentors Clifford Huff, Anthony Lattanze • Clients SEI: Scott Hissam, Dan Plakosh
Project goals • Develop a plug-in architecture for mobile devices for the Palm • Develop an application & plug-ins to demonstrate the concept • Deliver an SEI technical note describing the architecture and its rationale • Deliver a programmer’s reference document
Team roles Alterations from TSPi: • Added a role for requirements gathering • Added a role for client liaison
Team process • TSPi processes we used • Cycle planning • Document peer review • Procedures we added • Vision and expectation meetings • Team & client meeting protocol
Current status • Documentation • Developed an initial version of the SOW and the SPMP • Developed a draft of the SRS • Schedule tracking • Will start in next cycle • Education plan • Extended to the winter break
Process challenges • Slow start-up • Steep learning curve • Development & execution of education plan • Timely schedule execution • Development of plan & schedule tracking
The technology problem • Limited computing resources on the Palm platform • Limited interaction between applications • Plug-ins proprietary to a specific application • What if … • we simplify communication between applications on the Palm to easily extend their functionality?
Cool picture! Tony will like it I’d like to email it to him…. Go to mail program.. : Attach the file.. : I give up! The concept - I
PAMD • Plug-in Architecture for Mobile Devices • Provides a specification for application interchange of data and control • Provides common interfaces for applications to access PAMD plug-ins • Provides PAMD plug-in development framework
The concept - II Incredible…. I love PAMD…. I’ll send it to Cliff, Scott, and Dan too!!! Just choose the email plug-ins.. And send it.. Is that all? Wow!!!
Technical challenges • Understanding the Palm technology • Understanding the clients’ needs • Questionnaires lists • Use cases • End to end scenarios • Z-specification
Lessons learned • Stand-up meetings are needed • Deep domain knowledge is needed • Formal plan tracking is needed • Early cycle planning is needed
Next semester • Start the next cycle early • Realign team roles and create transition plan • Perform a mini SRE • Perform plan tracking using earned value • Develop an initial architecture • Develop an initial technical note
For more information, visit the PUMA web site at http://dogbert.mse.cs.cmu.edu/mse2002/projects/PAMD1
Risks • Different cultural background • Vision and expectation meetings • Lack of domain knowledge • Education plan • Time constraints
Use cases Enable Plug-in Use Service List Available Services <<extends>> Register Service Plug-in PAMD User Get Service <<extends>> Register Plug-in Palm OS Install Plug-in Check PAMD availability Application