1 / 13

Kanat Abirov Micha Ikeda Denise Varga Hisashi Yoshida

Kanat Abirov Micha Ikeda Denise Varga Hisashi Yoshida. - Team Lead - Process Manager - Client Liaison - Dev Manager. Agenda. Project Intro Requirements Categories Fall Delivery Plan Accomplishments Future Work Risks and Mitigation. Project Intro. Dr. Sidney Bailin, Client

avak
Download Presentation

Kanat Abirov Micha Ikeda Denise Varga Hisashi Yoshida

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Agenda • Project Intro • Requirements Categories • Fall Delivery Plan • Accomplishments • Future Work • Risks and Mitigation

  3. Project Intro 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 effectivelycapture design rationale • Rationale that is captured is oftenpoorly maintained Project Goal • System to capture design solutions rationale using Speech Recognition technology • Rationale capture process should be non-intrusive

  4. Requirements Categories • Elicitation Protocols • Structure of Speech Recognition • Placement and Format of Rationale • Code Representation • Navigation • Speech Recognition Training • Usability Testing

  5. Fall Delivery Plan

  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. Future Work 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

  8. Risks and Mitigation

  9. Questions to Mentors • What is the risk of relying on CMU experts?

  10. Questions? or Answers? ???

  11. Requirements Categories 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)

  12. Requirements Categories 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

  13. Process Flow Process work products Requirements Doc. (Dr.Sydney’s Final Report) Develop Test Case Test Document Develop Test Infra & Tools KEI Project Power Point Requirement Development Develop Software Design Test Program Software Requirement Spec. Use Cases Test Software And System Design Document Software Project Planning Project Management Product Engineering Implement Software Design Software (Source & Object) Test Report Risk Management Schedule SPMP SOW System Test (QA Div.) Software Project Tracking and Oversight Shipping Software Measurement & Metrics Team Mtg Minutes Post Mortem Final Report

More Related