1. Kanat Abirov Micha Ikeda Denise Varga Hisashi Yoshida - Team Lead - Process Manager - Client Liaison - Dev Manager

2. MOSP 10/17/2003 Slide 2 Agenda  Project Intro  Requirements Categories  Fall Delivery Plan  Accomplishments  Future Work  Risks and Mitigation

3. MOSP 10/17/2003 Slide 3 Dr. Sidney Bailin, Client  Software engineer with 25 years of experience  Domain knowledge; developed a prototype  Located in Washington, D.C. Problem  Software engineers often do not effectively capture design rationale  Rationale that is captured is often poorly maintained Project Goal  System to capture design solutions rationale using Speech Recognition technology  Rationale capture process should be non-intrusive Project Intro

4. MOSP 10/17/2003 Slide 4  Elicitation Protocols  Structure of Speech Recognition  Placement and Format of Rationale  Code Representation  Navigation  Speech Recognition Training  Usability Testing Requirements Categories

5. MOSP 10/17/2003 Slide 5 Fall Delivery Plan

6. MOSP 10/17/2003 Slide 6 Accomplishments Set project framework  Created initial SPMP, SOW, and Risk Management documents  Established team web-site  Installed client’s prototype  Created high level requirements Established C3PO team processes  Established team roles and responsibilities  Established weekly mentor and client meetings  Established weekly team work-sessions  Involved personnel (Eric) from the LTI as domain experts

7. MOSP 10/17/2003 Slide 7 Project Artifacts  Refine project artifacts and validate them with stakeholders  Create requirements specification  Create operations concept document  Validate the artifacts with stakeholders Future Actions  Elicit and analyze requirements  Get expertise from on-campus researchers  Identify and implement team process improvements Future Work

8. MOSP 10/17/2003 Slide 8 Risks and Mitigation PriorityRisk StatementMitigation 1Scope is not defined  Evaluate options to get big picture  Propose options to client 2Cross-cultural team (Communication)  Set weekly work-session  Have team social events 3High technical complexity  Use on-campus expertise 4Distant client - No money to meet face-to-face  Have weekly teleconference  Update team website  Use Wiki-site 5Team turnover Kanat leaves team  Share knowledge 6Lack of domain experience  Use on-campus expertise  Team education

9. MOSP 10/17/2003 Slide 9 Questions to Mentors  What is the risk of relying on CMU experts?

10. MOSP 10/17/2003 Slide 10 Questions? or Answers? ???

11. MOSP 10/17/2003 Slide 11 Elicitation Protocols  How and when to prompt user for spoken rationale  How to interpret spoken rationale (word-for-word, context matching)  Adjustable levels of interaction (intrusive vs. non-intrusive)  Initiation mechanisms (user vs. system) Structure of Speech Recognition  Vocabulary of software engineering  Mechanism for interpretation of speech into comments Placement and Format of Rationale  Where to put comments  Representation in some coding standard (e.g. Javadoc) Requirements Categories

12. MOSP 10/17/2003 Slide 12 Code Representation  Abstract tree structure  Cursor position vs. position of comment insertion  Intelligence built into system to make placement decisions  Degree of user interaction allowed Navigation  Voice-prompted cursor movement  “Undo” command via voice Speech Recognition Training  Training the system to recognize user’s voice  Training the system in the proper vocabulary Requirements Categories

13. MOSP 10/17/2003 Slide 13 Process Flow Requirement Development Software Project Planning Software Project Tracking and Oversight Develop Software Design Develop Test Infra & Tools Develop Test Case Test Software And System Implement Software Design Requirements Doc. (Dr.Sydney’s Final Report) Schedule Measurement & Metrics Test Program Test Report System Test (QA Div.) Shippin g Softwar e Product Engineering Project Management KEI Project Power Point Process work products Software (Source & Object) Post Mortem Final Report Team Mtg Minutes SPMPSOW Use Cases Software Requirement Spec. Design Document Test Document Risk Managemen t