May 6, 2002

PUMA SPRING 2002 PUMA SPRING 2002 EOSPEOSPPUMA SPRING 2002 PUMA SPRING 2002 EOSPEOSP

PUMPUMAA

2

AgendaAgenda

IntroductionProject organizationProcess Benefits from mini-SRE ArchitectureAchievementsProject demonstrationNext steps

3

Who we areWho we are

PUMA Portable Ubiquitous Middleware Architecture Team members Adrian Sia, Hernan Eguiluz, Venkat Govi, You Jung Kim

Constantin Kostenko, Bhuricha Sethanandha (MSIT) Technical writer

Kimberly Callaghan Mentors Anthony Lattanze, Cliff Huff Client SEI: Dan Plakosh, Scott Hissam

4

PAMD project overviewPAMD project overview

Plug-in Architecture for Mobile Devices– an architectural style for a run-time infrastructure

to allow applications to interact with plug-ins

Deliverables– a plug-in architecture for the Palm devices

– applications & plug-ins to demonstrate PAMD concepts

– an SEI technical note describing the architecture and its rationale

– a programmer’s reference document

5

Team rolesTeam roles

 

  Process/SupportManager<Venkat>

Development Manager

<You Jung>

Team leader<Adrian>

PlanningManager<Hernan>

6

Process improvementProcess improvement

Management Risks identification and tracking (mini-SRE) Weekly tracking of action items Weekly review of plans Cycle planning (stabilized) Regular time slots for project activities

Technical Develop prototypes to minimize risks Peer review

– Code walk-through

– Document review

7

Risks and mitigation strategies (cycle 2)Risks and mitigation strategies (cycle 2)

Risks Mitigation Strategy1. The team is making the project “too complex”

Simplify the requirements and develop prototypes to validate them

2. The team does not have in-depth understanding of the requirements

3. The team is unsure of plug-in discovery in Palm OS environment

8

Benefits of mini-SREBenefits of mini-SRE

Identified risks from team and client’s perspective

Re-aligned our understanding about requirements with client

Improved communication between client and team

Gained confidence in project

9

PrototypingPrototyping

Strategy– Creating throw-away prototypes– Mitigating technical risks– Prioritizing by requirements– Distributing work and sharing knowledge

Prototypes – Plug-in manager: Plug-in invocation,

Beaming, Hot-sync– Plug-ins: Complex data type passing, a plug-

in using another plug-in– Sample PAMD-aware applications

10

Driving qualitiesDriving qualities

Developer-friendly Usability

– PAMD should be easy to use

Performance – PAMD should meet users’ working pace in terms of

response time

Availability– PAMD should be available for service when PDA is

turned on

Portability– PAMD should be portable on Palm OS 3.1 – 4.0

11

ArchitectureArchitecture

PAMD-aware application

PAMDplug-in

Shared memory

Palm OSsystem DB

Plug-in registryPAMD

Plug-in manager

Application

Memory

Service Launch

Method invocation

DB connection

Direct memoryaccess

Plug-in

Database

Port

Plug-in managerIndirect Invocation/Shared Memory

12

AchievementsAchievements

Received customer approval of SOW Finalized SRS, revised SPMP Developed RMP Developed several risk-reduction prototypes Improved customer satisfaction Developed an architecture Developed a detailed draft of technical note

13

Next stepsNext steps

Verification of requirements– Developer’s reference document (API)

– Formal methods

Activate QA role for code & document Develop reference implementation Develop test plan Perform daily plan-tracking Prepare for ATAM

14

Lessons learned Lessons learned

KISS – Keep it simple, s….. ! Benefits of mini-SRE Benefits of prototyping Benefits of architectural reasoning Importance of tracking actions and plan

reviews

PAMD PAMD DemonstrationDemonstration

Questions?

16

Risks and mitigation strategies (cycle 3)Risks and mitigation strategies (cycle 3)

Risks Mitigation Strategies1. To develop high quality Technical Note on time

Start outline draft early and refine iteratively

Prioritize work

2. Availability of technical writer

Arrange weekend

meetings with technical

writer and use email for

communication

3. SRS may be inconsistent Formal review of SRS

at team level

17

Prototypes informationPrototypes information

Prototype Hrs LOC

Plug-in Manager ~44 ~754

Plug-in (Complex Data-type) ~10 ~119

Plug-in calling Plug-in ~5 ~41

Beam ~18 ~70

Hotsync ~25 ~50

PAMD application ~11 ~310

18

Lessons learned last semesterLessons learned last semester

Stand-up meetings are needed Deep domain knowledge is needed Formal plan tracking is needed Early cycle planning is needed

19

Application Service Launch Method invocation Plug-in registrationPlug-in

Legend

Plug-in manager

ApplicationPAMDPlug-in

1: A plug- in is registered in PAMD

2: Ask for the available plug -in list to PAMD

3: Ask for the execution of the selected

4: Load the plug-and run it.

PAMD

ApplicationPAMDPlug-in

1: A plug-in PAMD

2: Ask for the available plu

3: Ask for the execution of the selected plug-in

4: Load the plug-in-and run it.

System ContextSystem Context