1 / 48

MOSP from Bosch Buzzers (Spring 2008)

MOSP from Bosch Buzzers (Spring 2008). Darpan Saini Yongjoon Choi Vytesh Ramesh Liang-Yun(Mac) Wang Yun-Yin(Melody) Huang. Outline. Project Overview Process and Semester Plan Architecture Driver and Scope Architecture and Experiment Risk Analysis Detailed Plan and Execution

yvon
Download Presentation

MOSP from Bosch Buzzers (Spring 2008)

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. MOSP from Bosch Buzzers(Spring 2008) Darpan Saini Yongjoon Choi Vytesh Ramesh Liang-Yun(Mac) Wang Yun-Yin(Melody) Huang

  2. Outline • Project Overview • Process and Semester Plan • Architecture Driver and Scope • Architecture and Experiment • Risk Analysis • Detailed Plan and Execution • Conclusion and Q&A Bosch Buzzers - MOSP Spring2008

  3. Project goal • Short research report in GSD best practice • Produce a prototype for software to assist in collaboration and conformance checking during the design phase • This prototype could later be extended as a research tool Bosch Buzzers - MOSP Spring2008

  4. The project Design Collaboration Tool Whiteboard Conformance Checking Online Chatting History Playback UML Modeling Current Bosch GSD Practice Bosch Buzzers - MOSP Spring2008

  5. Clients, mentors & technical advisors • Client • Robert Bosch LLC Research &Technology Center, North America • Representatives: • Dr. Chris Martin • Dr. Charles Shelton • Dr. Marcelo Cataldo • Mentors • Mel Rosso-Llopart • Felix Bachmann • Technical advisor • Dr. Jim Herbsleb • Tony Lattanze Bosch Buzzers - MOSP Spring2008

  6. ACDM stages Stage 1: Discover architecture drivers Complete Stage 2: Establish project scope Processing Stage 3: Create notional architecture Incomplete Stage 4: architecture review 5. Production Go? No-Go? Stage 6: Experiment planning Stage 6: Production planning Stage 7: Experiment executing and refine architecture Stage 7: Production Bosch Buzzers - MOSP Spring2008

  7. The team Bosch Buzzers - MOSP Spring2008

  8. First Half Jan Feb Bosch Buzzers, MSE, CMU 2007-2008

  9. Later Half Mar Apr May Bosch Buzzers, MSE, CMU 2007-2008

  10. Architecture driver and Scope • Techniques used to stabilize the requirements • Academic paper survey • Existing tool survey and demonstration • Paper prototype • Expert opinion Bosch Buzzers, MSE, CMU 2007-2008

  11. Scope Refinement and Requirement Stabilization • Nov 07 • Build a prototype tool to assist communication and conformance checking during the design phase • Dec 07 • A UML-aware, shared whiteboard • Conformance checking • Jan 08 • Survey of design collaboration • Several paper prototyping sessions and existing tool demonstration • Meetings with Jim and Marcelo • Feb 08 • Poster board with individual view ports Bosch Buzzers, MSE, CMU 2007-2008

  12. Requirements stability Bosch Buzzers - MOSP Spring2008

  13. Architecture driver - Paper Prototyping 1 Bosch Buzzers - MOSP Spring2008

  14. Architecture driver - Paper Prototyping 2 Poster board vytesh chat Chat UML diagram is saved as XML format Whiteboard is saved as jpeg, gif format Bosch Buzzers - MOSP Spring2008

  15. Architecture driver - Paper Prototyping 3 • Conformance part was risky from the beginning • How did we stabilize this? • Reduced the scope by negotiating with client • Paper prototyping Bosch Buzzers - MOSP Spring2008

  16. Reflection on Paper Prototyping • Quick feedback • Clients appreciate the results of paper prototyping • Both clients and team gain more understanding about the tool • Need customer’s involvement to get detail requirements Bosch Buzzers - MOSP Spring2008

  17. Architecture and Experiment • Use ADD to make sure the quality attributes are answered and requirements filled Bosch Buzzers - MOSP Spring2008

  18. ADD - 1 Bosch Buzzers, MSE, CMU 2007-2008

  19. ADD - 2 Bosch Buzzers, MSE, CMU 2007-2008

  20. ADD - 3 Client (B) Client (B) Link A Client (A) with Facilitator’s Right Link A Link A Collaboration Server (C) Management console (E) Link C Link B Team Version Controlled File Repository Session File Repository (D) Bosch Buzzers, MSE, CMU 2007-2008

  21. ADD - 4 UML Model UML Editing tool Link B Link A Whiteboard Poster board Graphical Subsystem Bosch Buzzers, MSE, CMU 2007-2008

  22. Experiment and Exploration • Openfire • Jazz • UML Editing tool Bosch Buzzers, MSE, CMU 2007-2008

  23. Risk Analysis • SRE (Small Team Risk Evaluation) • Threshold of success: 5 • Duration: 5 hours • Total risks identified: 23 • Define mitigation for top 3 risks Bosch Buzzers - MOSP Spring2008

  24. Risk Status (Top 3) Bosch Buzzers - MOSP Spring2008

  25. Risk mitigation • Team members to spend 3 afternoons per week in the cave as common team time. • We dropped evaluation of Openfire, and put the freed resource on evaluating Jazz. • Had eclipse plug-in development knowledge sharing session. Bosch Buzzers - MOSP Spring2008

  26. Detailed Plan and Execution • Short-term plan • Use two weeks as an iteration • Managing engineer assigned main task and responsibilities • Team members define subtasks and exit criteria • Quality manager assures the quality of subtask Bosch Buzzers, MSE, CMU 2007-2008

  27. Earned Value Bosch Buzzers - MOSP Spring2008

  28. Proposals • Update • Planning proposal • Operational proposal • Problem definition proposal • Created • Design proposal (for architecture) • Planned • Design proposal (for detail design) • Implementation proposal Bosch Buzzers - MOSP Spring2008

  29. Workspaces • Set up Wiki website onhttp://128.2.188.131/ • Requirement document • Architecture document • Meeting minutes • Cross reference for traceability • Maintain change history • Set up SVN server • Version control • Timesheet • Semester/short-term plan • Action item/task tracking form Bosch Buzzers - MOSP Spring2008

  30. Conclusion • Accomplishment • SRS delivered • Notional architecture • SRE • Preparation • Started knowledge transfer • Experiment plan Bosch Buzzers - MOSP Spring2008

  31. Questions to mentors • How do we know our progress on architecture? • How do we estimate the time we require to finish architecture and detail design? • Whether the evaluation of tools and technology can be treated as experiment in ACDM? • Is there any tool for requirement and architecture traceability? • Is there any better way to trace if we are following ACDM process? Bosch Buzzers - MOSP Spring2008

  32. Bosch Buzzers - MOSP Spring2008

  33. Happy Spring Break!

  34. Backup Slides

  35. Case 0: Work Alone Rule Rule 4, 6 Eclipse platform 1,8 UML Editing Tool Conformance Manager Subclipse 3,9 2,10 5,7 Local hard drive UML Model Subversion server version controlled file repository (remote) Bosch Buzzers - MOSP Spring2008

  36. Case 1: Initiate Session 1,4 Model Files Model Files Eclipse platform Session Console UML Editing Tool (E) 5 9 2 Client Session Server Descriptor file 6,8 7 3 Local hard drive UML Model Camel Server UML Model Bosch Buzzers - MOSP Spring2008

  37. Case 2: Join and Continue Client Status Whiteboards Model Files Model Files 1,4 Eclipse platform Session Console 5 2 Client Session Server Descriptor file 3 7 6 UML Editing Tool (E) Chat Log Camel Server Bosch Buzzers - MOSP Spring2008

  38. Case 3: Playback Client Status (J) Whiteboards (H) Model Files (F) Model Files Client (A) Session Console 1,2 5 UML Editing Tool (E) 3 Client Session (G) Local/network hard drive 4 Session files Chat Log (L) Bosch Buzzers - MOSP Spring2008

  39. Server Side (Logic View) Client Session (G) Client Cache of Chat Log, Model Files, Whiteboards, and Client Status (H) Java EE Application Server (A) Whiteboards (D) Client Status (E) Model Files (C) Model Files Server Session (B) Link A Chat Log (F) Link B Web Server (I) Link C Management Console (J) Bosch Buzzers - MOSP Spring2008

  40. Client Side (Logic View) Client Status (J) Whiteboards (H) Client (A) Model Files (F) Rule (D) Model Files Rule Model Files (B) Conformance Manager (C) Link C Link B Link A Server Session (P) UML Editing Tool (E) Session Data: Chat Log, Model Files, Whiteboards, and Client Status (Q) Link E Link D Client Session (G) Graphical Encapsulation (N) Link F Link I Whiteboard view (I) Link H Link G Link J Poster board view (K) Graphical Subsystem (O) Link K Chat view (M) Chat Log (L) Bosch Buzzers - MOSP Spring2008

  41. Basic architecture for conformance checking Model Files Conformance Manager Rule (D)‏ Rule Graphical Encapsulation Graphical Encapsulation UML Editing Tool Bosch Buzzers, MSE, CMU 2007-2008

  42. WBS and Assigned Value Basic architecture (5pt) Server Architecture Connection (40pt) Live session data sync (20pt) Session management (5pt) Operating model (10pt) Persistence of session data (5pt) Basic architecture (5pt) Client Architecture (45pt) Whiteboard (15pt) Poster board integration (15pt) Playback (5pt) Session Management (5pt) Monitor Console (5pt) Bosch Buzzers, MSE, CMU 2007-2008

  43. Effort distribution Bosch Buzzers - MOSP Spring2008

  44. Time spent for each week Bosch Buzzers - MOSP Spring2008

  45. Earned Value - semester Bosch Buzzers - MOSP Spring2008

  46. Initial Plan for next semester Bosch Buzzers - EOSP Fall2007

  47. Review process Bosch Buzzers - MOSP Spring2008

  48. Knowledge sharing process Bosch Buzzers - MOSP Spring2008

More Related