1 / 40

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. Part I (Hisashi) Overview of the project Requirements Part II (Micha) Project management Results, future work. Successes.

nam
Télécharger la présentation

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 • Part I (Hisashi) • Overview of the project • Requirements • Part II (Micha) • Project management • Results, future work

  3. Successes • Team C3PO successfully worked with each other, the client and mentors to: • acquire domain knowledge • define the scope of our project • establish a clear set of requirements to lead us into the architecture phase • Our client is happy!

  4. Project Background • Client • Dr. Sidney Bailin, Knowledge Evolution, Inc., Washington, DC • Software engineer with domain knowledge; developed prototype • Prototype • Developed by client in 2001 • Built on JBuilder 3 IDE and uses Chant SpeechKit(+ MS SAPI) for speech recognition • Addressed the most basic implementation and feasibility aspects of project goals

  5. Problem to Solve • Rationale capture is crucial to sound software design and implementation • Especially evolving designs • Software developers tend not to document rationale • Significant cognitive and motor overhead • May not have articulated rationale to themselves

  6. Proposed Solution • Provide an easier way to document rationale • Capture spoken rationale • Doesn’t interfere with the motor processes of using a design or programming tool • Close to the “running conversation” developers have in their heads • Use speech recognition (SR) to incorporate spoken rationale into software artifacts

  7. Prototype • Demo • What is it like? • How well does it work?

  8. C3PO Project Goals - 1 • Determine whether improved speech recognition is possible • Currently researching latest technology in SR software • Evaluate alternatives to JBuilder as target environment • Selected Eclipse programming environment as the alternative to JBuilder

  9. C3PO Project Goals - 2 • Improve algorithms • Requirements address: • heuristics for elicitation & techniques • speech translation • rationale placement • context-based interpretation

  10. C3PO Project Goals - 3 • Improve user interface (UI) • Requirements address: • elicitation methods • code representation • ability to customize interface • Usability Testing • Summer 2004

  11. Wiki (Web) weekly telecon + requirement session telecon + team web + wiki web Requirement Elicitation Documentation Requirement Map SRS + Tracking Sheet (+Ops Concept) use case (prototype) Communication

  12. Requirement Map

  13. Wiki • Example: "DesignIssue" Page • What can you do with it? • What is it like?

  14. Wiki - Overview Create Page Multiple Editor Edit (Add)

  15. Wiki - To Edit ... Clicking on the link will turn the page to a text box

  16. Wiki - Simple Text Editing

  17. Operations Concept - 1 • User view of requirements • Context diagram a) User b) Microphone /headphones /speakers PC running Win 2000 or Win XP e) Eclipse IDE d) NIRC using Speech Kit I/F to SAPI c) Microsoft SAPI (example SR)

  18. Operations Concept - 2 • User view of requirements • Day in life description • Use cases

  19. Requirement - Future Plan • Ops concept • Add use cases • Non-functional requirements • Quantify/Add • Further understanding of technology, COTS evaluation • Architecture/Design • Requirement Management • Manage "Requirement Tracking Sheet"

  20. Project Management • Project organization and team roles • Overall schedule • Processes • Risks • Lesson Learned

  21. C3PO Organization Fall 2003 semester Kanat Dr. Sidney Bailin, KEI Team leader/ Client Planning manager Dave, Coach, Felix, Soo Yong Technical Team Team writing mentor mentors C3PO Linda QA/Process Development Client liaison manager manager Micha Hisashi Denise

  22. Team C3PO Roles • Team Lead/Planning Manager • SPMP, manage schedule and action item tracking list, allocate tasks, facilitate weekly meetings • Development Manager • SRS, lead requirements elicitation, make technical decisions, manage C3PO website • Client Liaison • Operations Concept Document, facilitate weekly client meetings, act as interface for communications between team C3PO and client • Process Manager • SOW, documentation of team processes, participate in Studio Process meetings, manage Risk List

  23. Schedule Milestones ‘04 Jan Apr May Jun July Aug ‘03 Dec Requirements Elicitation COTS Evaluation Requirements Analysis ★EOSP Architecture & Detail Design ★EOSP Iteration1 System Release1 Iteration2 Final Release EOSP★

  24. Problems at the Beginning… Delay of Work Disorganized Weekly Mtg Takes too much time Cannot see how much we delay Cannot see the progress Problems Distance Client Misunderstanding of Requirements Misunderstanding of verbal communication Lack of Communication Lack of Domain Knowledge

  25. How We Solved the Problem Delay of Work Disorganized Weekly Mtg Team Working Session Meeting Process Establish Goals Takes too much time Roles / Agenda Action Item Tracking Sheet Cannot see how much we delay Assign actions prior to working session Document results Cannot see the progress Resolve Problem Distance Client Wiki Site to communicate w/Client Use case Requirements Map Local domain experts Req. review session Misunderstanding of Requirements C3PO Website Social Events Misunderstanding Of verbal communication Web Update Req. Elicitation Process Lack of Communication Lack of Domain Knowledge

  26. Risks - 1

  27. Risks - 2

  28. Fall Accomplishments • Created SOW, SPMP, SRS, Ops Concept • Validated • Captured initial set of requirements • Reviewed with client • Installed & tested prototype • Established connections w/ local experts • Researched SR (satisfied)

  29. Application of Core Courses • Managing Software Development • SDMP - incorporated in SPMP • QA Plan - will use this document • Risk Plan - currently using • Methods of Software Development • Use cases - initial requirement understanding • Usability - will use in usability testing • Quantitative decision making

  30. Application of Core Courses • Models of Software Systems • Formal modeling next semester • Working relationship w/ MSIT students for future Practicum projects

  31. Future Work • Obtain support from MSIT students • Conduct research & decide on SR engine • Evaluate & purchase COTS software • Collaborate w/ other CMU groups • Establish formal configuration management

  32. Lessons Learned • Multi-cultural teams require more time and effort to establish effective communication among team members • Technology can enhance communication with a distant client • Teleconferencing • Collaborative website (Wiki) • 12 units = 30 hours/week

  33. Questions • How will we work with MSIT student? • How should we proceed in collaborating with other groups in CMU? • How we can improve estimation accuracy? • How much of the architectural and design work will be done in the remaining core courses?

  34. End of Our Presentation Thank You!

  35. Backup Slides

  36. Operations Concept - 1 6.1 NIRC Elicitation Use Case This use case describes how the NIRC system will elicit rationale from the user. This elicitation is based on the following criteria: - Time elapsed since the last comment - LOC written since the last comment - Insertion of method, class, etc since last comment (Can use a or b for actual counting) - On certain events (e.g. class “creation”) This use case covers C3PO Requirement SR13.

  37. Operations Concept - 2 6.1.2 Functions 1. Time elapsed – The user has been coding for 20 minutes since the last rationale was spoken. NIRC detects the 20 minutes time limit and chooses to ask the user “What are you doing now?” This message is retrieved by NIRC from a set of stored prompts. The method of elicitation is voice synthesis, which is achieved via the speech recognition software in the system, and is delivered to the user over headphones or speakers.

  38. Requirement Tracking - 1

  39. Requirement Tracking - 2

  40. CMM Process ImprovementTop-Down VS. Bottom-Up Top-Down Approach Bottom-Up Approach ③Report to management ②Find Solution ③Add process If necessary ① Apply CMM model Based approach for projects SQA “Police” PJ PJ Mentors “Coach” TSP Base Process ②watch the compliances ①Try to find PJ’s strength & weakness CMM Base Process XP Base Process XP Base Process

More Related