Fall 2001 EOSP
description
Transcript of Fall 2001 EOSP
Dec. 10, 2001
Fall 2001 EOSPFall 2001 EOSPFall 2001 EOSPFall 2001 EOSPPUMAPUMA
2PUMPUMAA
AgendaAgenda
Introduction Project Organization & Process Technical Challenges Lesson Learned Next Semester
3PUMPUMAA
Who we areWho 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
4PUMPUMAA
Project goalsProject 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
5PUMPUMAA
Team rolesTeam roles
Process m anagerSupport mananger
Planning m anager Client liais ionRequirem ent leader
Team leader
Alterations from TSPi:
– Added a role for requirements gathering
– Added a role for client liaison
6PUMPUMAA
Team processTeam process
TSPi processes we used– Cycle planning– Document peer review
Procedures we added– Vision and expectation meetings– Team & client meeting protocol
7PUMPUMAA
Current statusCurrent 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
8PUMPUMAA
Process challengesProcess challenges
Slow start-up Steep learning curve
– Development & execution of education plan
Timely schedule execution– Development of plan & schedule
tracking
9PUMPUMAA
The technology problemThe 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?
10PUMPUMAA
The concept - IThe concept - ICool
picture!Tony will
like it
I’d like to email it to him….
Go to mail program..:
Attach the file..:
I give up!
11PUMPUMAA
PAMDPAMD
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
12PUMPUMAA
The concept - IIThe concept - II
Just choose the email plug-ins.. And send it..Is that all? Wow!!!
Incredible….I love PAMD….I’ll send it to Cliff, Scott, and Dan too!!!
13PUMPUMAA
Technical challengesTechnical challenges
Understanding the Palm technology Understanding the clients’ needs
– Questionnaires lists– Use cases– End to end scenarios – Z-specification
14PUMPUMAA
Lessons learnedLessons learned
Stand-up meetings are needed Deep domain knowledge is needed Formal plan tracking is needed Early cycle planning is needed
15PUMPUMAA
Next semesterNext 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
16PUMPUMAA
Questions?
17PUMPUMAA
For more information, visit the PUMA web site at
http://dogbert.mse.cs.cmu.edu/mse2002/projects/PAMD1
18PUMPUMAA
RisksRisks
Different cultural background – Vision and expectation meetings
Lack of domain knowledge– Education plan
Time constraints
19PUMPUMAA
Use casesUse cases
List Available Services
Get Service
Application
Palm OS Check PAMD availability
Enable Plug-in
Install Plug-in
Register Service
Register Plug-in
Plug-in
Use Service
PAMD User
<<extends>>
<<extends>>