1 / 69

EOSP Fall Semester

EOSP Fall Semester. SCS – Architecture Evolution Team PANGEA 12/13/2007 Version 3.0. Agenda. Project Process Accomplishments Reflection Plan for Spring semester. Team Pangea. Introduction. Client Dr. David Garlan Leading the ABLE research group at CMU Bradley Schmerl

leone
Download Presentation

EOSP Fall Semester

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. EOSPFall Semester SCS – Architecture Evolution Team PANGEA 12/13/2007Version 3.0 2007 Fall Semester EOSP - Architecture Evolution

  2. Agenda • Project • Process • Accomplishments • Reflection • Plan for Spring semester 2007 Fall Semester EOSP - Architecture Evolution

  3. Team Pangea 2007 Fall Semester EOSP - Architecture Evolution

  4. Introduction • Client • Dr. David Garlan • Leading the ABLE research group at CMU • Bradley Schmerl • Technical Advisor • Mentors • Clifford Huff, SEI • Daniel Plakosh, SEI 2007 Fall Semester EOSP - Architecture Evolution

  5. Business context diagram Business GoalClient wants to have a tool: • facilitates research in architecture evolution • can be easily extended with new path analyses and planning tools ABLE Group Requests for tools AcmeStudio Development Group Researchers Provides tools Uses tools & knowledge Software Architects, Researchers in Industry 2007 Fall Semester EOSP - Architecture Evolution

  6. What is AcmeStudio? AcmeStudio Software Architect Software Architecture 2007 Fall Semester EOSP - Architecture Evolution

  7. What is Architecture Evolution? Now 6 months later 1 year later 2007 Fall Semester EOSP - Architecture Evolution

  8. What is Architecture Evolution? Now 6 months later 1 year later 2007 Fall Semester EOSP - Architecture Evolution

  9. What our tool shall do? Architecture Evolution Tool (Eclipse Plug-in) • Representing & manipulating evolution path • Comparing architectural instances • Framework extension for trade-off analysis Instance 2 Instance 3 Future architecture Instance 1 Current architecture Instance 4 Instance 5 Future architecture Extend AcmeStudio Eclipse 2007 Fall Semester EOSP - Architecture Evolution

  10. Agenda • Project • Process • Accomplishments • Reflection • Plan for Spring semester 2007 Fall Semester EOSP - Architecture Evolution

  11. SDLC Selection • High risk project • Busy client • No expertise in eclipse plug-in • Volatile requirements • Infeasible scope • Spiral model selectedfor SDLC • Identify critical risk • mitigate them in each iteration 2007 Fall Semester EOSP - Architecture Evolution

  12. Process Selection • AUP selected as process • Why? • Project context • Unprecedented project • Volatile requirements • Required agility • Decision matrix used for evaluation • Desire for learning new thing 2007 Fall Semester EOSP - Architecture Evolution

  13. How we use spiral? 2007 Fall Semester EOSP - Architecture Evolution

  14. Risk Management 1 2 1 2 1 2 2007 Fall Semester EOSP - Architecture Evolution

  15. Requirement Elicitation Process Activities Artifacts - Needs - Features - Constraints INTERVIEW SOW Quality attributes Functional USE CASE MODELING Suppl. Spec Use case model PAPER PROTOTYPING UI Design Paper Prototype User Reference 2007 Fall Semester EOSP - Architecture Evolution

  16. Project Planning I1: Iteration 1 I2: Iteration 2 I3: Iteration 3 Const.: Construction 2007 Fall Semester EOSP - Architecture Evolution

  17. Task estimation process Iteration begins Planning meeting WBS Team estimates for all tasks Average taken Task owner may override the team estimation 2007 Fall Semester EOSP - Architecture Evolution

  18. Project Tracking Earned Value Analysis 2007 Fall Semester EOSP - Architecture Evolution

  19. Project Tracking (Cont.) Time Allocation (hours, %) Notes: Data is based on Iteration 2 (Total: 3 weeks, 192 hours) 2007 Fall Semester EOSP - Architecture Evolution

  20. Agenda • Project • Challenges • Process • Accomplishments • Reflection • Plan for Spring semester 2007 Fall Semester EOSP - Architecture Evolution

  21. Accomplishments 2007 Fall Semester EOSP - Architecture Evolution

  22. Agenda • Project • Challenges • Process • Accomplishments • Reflection • Plan for Spring semester 2007 Fall Semester EOSP - Architecture Evolution

  23. Iteration1 - What went well? 2007 Fall Semester EOSP - Architecture Evolution

  24. Iteration1 – where to improve? 2007 Fall Semester EOSP - Architecture Evolution

  25. Iteration 2 - what went well? 2007 Fall Semester EOSP - Architecture Evolution

  26. Iteration2 – where to improve? 2007 Fall Semester EOSP - Architecture Evolution

  27. Planning Proposal                Done well Room for improvement Done badly 2007 Fall Semester EOSP - Architecture Evolution

  28. Operation Proposal                  Done well Room for improvement Done badly 2007 Fall Semester EOSP - Architecture Evolution

  29. Problem Definition Proposal          N/A    Done well Room for improvement Done badly 2007 Fall Semester EOSP - Architecture Evolution

  30. Lessons Learned 2007 Fall Semester EOSP - Architecture Evolution Team processes matters Agile & ad-hoc processes easily confused Planning & tracking is not easy Proposals are not overhead Mentors' perspective important Value of core courses

  31. Agenda • Project • Challenges • Process • Accomplishments of this semester • Reflection • Plan for Spring 2007 Fall Semester EOSP - Architecture Evolution

  32. Goals for Spring Semester • Complete architecture and design • Establish process for design and implementation • Complete the implementation for the first use case • Complete requirements elicitation for the remaining high level use cases 2007 Fall Semester EOSP - Architecture Evolution

  33. To-do list for Spring semester • Some items… • Focus on Software Architecture • Need to evaluate the process – AUP, ACDM, XP • Conduct feasibility study • Quality Attribute Workshop (QAW) • Plan for QAW • Supplemental specifications • Proposals • Design proposal • Implementation proposal 2007 Fall Semester EOSP - Architecture Evolution

  34. Questions? 2007 Fall Semester EOSP - Architecture Evolution

  35. Appendix SCS – Architecture Evolution Team PANGEA 12/13/2007 2007 Fall Semester EOSP - Architecture Evolution

  36. Roles for Spring 2007 Fall Semester EOSP - Architecture Evolution

  37. Redefining roles 2007 Fall Semester EOSP - Architecture Evolution

  38. Requirements • What the tool shall do? • Diagram architecture evolution process • Single path evolution • Multi path evolution • Comparing architectural instances • Showing differences between subsequent instances in the path • Quality trade off analysis between evolution paths • Which path is better in terms of time and cost? Project Process Accomplishment Reflection Spring 2007 Fall Semester EOSP - Architecture Evolution

  39. Use case diagram Software Architecture Evolution Tool AcmeStudio Develop Architecture Instance <<include>> UC01: PlanArchitecture Evolution Import Architecture instances <<include>> <<extend>> Software architect <<extend>> Evolve architectural family UC02: View Architectural Animation Evolve Hierarchical representation UC03: AnalyzeQuality Trade-off 3rd party plug-in 2007 Fall Semester EOSP - Architecture Evolution

  40. What our tool shall do? • Compare different instances on the path Instance A on evolution path Instance B on evolution path 2007 Fall Semester EOSP - Architecture Evolution

  41. Success Criteria • Success Criteria • Extend AcmeStudio with robust, reliable and documented implementation • Provide test cases for regression testing of enhanced AcmeStudio • Provide convincing demonstration showing that the architecture evolution tool works 2007 Fall Semester EOSP - Architecture Evolution

  42. AUP overview • The Agile UP lifecycle is • serial in the large • iterative in the small • delivering incremental releases over time.  2007 Fall Semester EOSP - Architecture Evolution

  43. Process Comparison 2007 Fall Semester EOSP - Architecture Evolution

  44. Phases and Milestones of AUP 2007 Fall Semester EOSP - Architecture Evolution

  45. How much did we follow AUP?          Done well Room for improvement Done badly 2007 Fall Semester EOSP - Architecture Evolution

  46. Our process RUP AUP Template (use case specification) Detailed procedure What we learned in class Phases Iteration focus Milestones Set of methodologies Procedures for methodologies Contextual Design Use case, prototyping Estimation techniques Risk Management, others 2007 Fall Semester EOSP - Architecture Evolution

  47. Roles based on AUP • Project Manager • Include responsibilities for Team lead, Planning management, client relation, risk management • Requirement Manager • Process Manager • Software Architect • Configuration Manager • Test Manager • Tool Manager • Technical Investigator • Reviewer • Developer • Tester 2007 Fall Semester EOSP - Architecture Evolution

  48. Documents for process • Proposals • AUP process documents (HTML files) • Supplemental Procedures • Risk management process • Status meeting process • Artifact guides • Experiments template 2007 Fall Semester EOSP - Architecture Evolution

  49. Risk List 2007 Fall Semester EOSP - Architecture Evolution

  50. Risk List • High • Not well-defined scope • Busy client • Medium • Tight delivery schedule (12 months) • Working time for project is condensed & limited • Some constraints in class schedule(Architecture in Spring semester) • Volatile requirements • No expertise in eclipse plug-in architecture • Dependence to Google Doc • Low • Architecture Evolution is emerging area • Unprecedented project • Transition of roles need to happen after fall semester, might hit the schedule and performance/productivity of the team • Electives will force us to change the common work time 2007 Fall Semester EOSP - Architecture Evolution

More Related