1 / 55

DOCVIEWER

DOCVIEWER. EPP | 10 th December 2009 | IKARUPROJECTS. Agenda. Introduction Recap Architecture and Design Demo Planning and Tracking Reflection. Introductions. Client Bharat Gorantla Mentor Phil Bianco Team iGreen Sai Sharan Donthi Vignesh Murugesan Vikram Subramanian.

kirk
Download Presentation

DOCVIEWER

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. DOCVIEWER EPP | 10th December 2009 | IKARUPROJECTS

  2. Agenda • Introduction • Recap • Architecture and Design • Demo • Planning and Tracking • Reflection Team iGreen

  3. Introductions • Client • Bharat Gorantla • Mentor • Phil Bianco • Team iGreen • Sai Sharan Donthi • Vignesh Murugesan • Vikram Subramanian Team iGreen

  4. Project Context Microsoft Office, Adobe Reader, Open Office, ?? Internet PDF PPT DOC ODT Learner Teacher Data Transfer Team iGreen

  5. Context Diagram Web Application Viewer Converter Legend Developed by Team iGreen Client Application Uses Team iGreen

  6. C&C View Team iGreen

  7. Viewer Design Spoke indicates a new screen Team iGreen

  8. Accomplishments • Deliverables: ZOOM Pagination Delivered Converter Viewer Full-screen Search ‘Must Have’s 8 Team iGreen Team iGreen

  9. DocViewer - Demo Team iGreen | Phil Bianco | DocViewer | IKaruProjects Team iGreen

  10. Recap– Summer of ‘09 • SOW, SRS |Quality Attribute Workshop • Scope | Clarity between technical constraints and QA’s.  • Extreme Programming • Spike Solutions  • Test Driven Development  • Quality Assurance  • Earned Value Planning and Tracking  • Plan revision | Team velocity •  - Went well |  - Satisfactory |  - Didn’t go well Team iGreen

  11. Goals and Objectives – Fall ‘09 • Pair Programming • Continuous Risk Management • Process for Quality Assurance • Deliver the must have requirements • Deliver Word (doc, docx), PowerPoint (ppt, pptx) • Deliver the viewer part developed using FLEX Team iGreen

  12. SDLC & Process • Extreme Programming • Iterative delivery | Two semesters | Small Team • Project Characteristics • Selected Agile Life Cycle Model. • Frequent delivery & continuous client interaction • Short span of the project • Small Team • Possibility of changes in requirements Team iGreen

  13. SDLC & Process • XP continued…. • Paired comparison - Estimation • Risk Management | CRM | SRE • Risk Identification – At the beginning of Iteration • Risk mitigation strategies | Contingency plans immediately Team iGreen

  14. Planning And Estimation data • Planning Data • Available Number of Hours : 470 hrs • Number of hours planned for : 485 hrs • Number of hours kept in Buffer : 134 hrs • Number of iterations : 4 • 3 Iterations for ‘Must have’s and 1 Iteration for ‘Nice to have’ Team iGreen

  15. CPV Vs. EV and Actual Effort Deployment Iteration 4 Iteration 3 Iteration 2 Iteration 1 SAD Planned SRS SOW ITR - 1 Achieved Iteration 1 SRS & SOW SAD Weeks Team iGreen

  16. Iteration 1 EV Analysis Buffer completely utilized Backlog - Iteration 2 Backlog – Iteration 3 Team iGreen

  17. Estimated Effort Split-up Team iGreen

  18. Effort Spent - Activities Team iGreen

  19. Reflections – Planning And Tracking • Finding algorithms is not easy  • Planned for 2 Converter POCs | Performed five  • Four converter POCs | One Viewer POC • Planned only 2 POCs - Should have kept it open  • Plan revision | 09/11  • Reprioritization from client - Could have asked earlier  • Plan revision | 10/10  •  - Satisfactory |  - Went well |  - Didn’t go well Team iGreen

  20. Reflections - Proof Of Concepts Team iGreen

  21. Client Feedback 1- Can Improve 2-Matched Expectations 3-Exceeded Expectations Team iGreen

  22. Thank You Team iGreen

  23. Back Up Slides Back Up Slides Team iGreen

  24. Architecture Team iGreen

  25. Document Formats • Adobe PDF • Microsoft Word – doc & docx • Microsoft Powerpoint – ppt & pptx • Open Office Text Document - .odt & .sxw • Open Office Presentation - .odp & .sxi • Adobe Postscript • Microsoft Excel • Open Office Spreadsheet • Plain Text • Rich Text Format Team iGreen

  26. Functional Requirements & QAs Performance – Priority 1 A 2MB File should be converted within 10 seconds Converter Extensibility – Priority 2 A newly developed document converter should be integrated in to the converter component within 40 person days . Team iGreen

  27. Constraints • Technical • Should be provided as an API to hook in to the client web application. • Should be developed using Java. • Business • Should be developed only using open source tools. • Should be developed in two semesters. Team iGreen

  28. C&C View Team iGreen

  29. C&C View Team iGreen

  30. Requirements Team iGreen

  31. Requirements Engineering • Requirements Development • Functional User Quality Attributes Technical • Business • Requirements Analysis • Prioritization of • Features Quality Attributes • Must Haves and Nice to Haves • Requirements Specification • IEEE SRS Format • Use cases for functional requirements • 6 part scenario documentation for quality attributes Team iGreen

  32. Planning and Tracking Beware! So much of numbers Team iGreen

  33. Tracking Process • Earned Value Tracking • Granularized Tasks | Effort | Value • Planned Value Baseline • Effort Available | Features | Iterations • Weekly Tracking and Backlog list • Planned Value Baseline | Earned Value for 2 weeks • Example : Once upon a time…in the next slide • Tracking helped us! • Backlog List | Allocation | Time box Team iGreen

  34. Iterations and Features Team iGreen

  35. Planned Effort for Phases Team iGreen

  36. Effort Spent on Phases Team iGreen

  37. Effort Split in Iteration 2 Team iGreen

  38. Effort split for Iteration 3 Team iGreen

  39. Effort Spent Split – Iteration 4 Team iGreen

  40. Reflections -Requirements • Quality Attributes  • Client was familiar with Quality Attribute Workshop, so we could directly start from • Business Goals • Scenario Brainstorming • Scenario Consolidation, Prioritization and Refinement • Identifying the system boundary and scope. • Clarity between technical constraints and quality attributes •  - Satisfactory |  - Went well |  - Didn’t go well Team iGreen

  41. Process Matrix Team iGreen

  42. Process Team iGreen

  43. Architecture Design Process Gather Architectural Drivers Identify Notional Architecture Apply ADD and Refine Architecture Develop Run-Time, Static and Allocation views Review Architecture Legend Activities Control Flow Team iGreen

  44. Module & Package View Team iGreen

  45. Allocation View Team iGreen

  46. Implementation • Low – Level Design • Test Driven Development Team iGreen

  47. Project Management • People • Project Plan • Tracking and Revising Plan • Risk Management • Reflections Team iGreen

  48. What Now? • Analyze why the Earned Value is more/less • Productivity | Estimation | Process • Activities that have not added value but consumed effort • Backlog List | Buffer Time | Allocation | Time-box • Update the Project Overhead Activities / Tasks • Estimate and revise plan • Steps to achieve productivity • Training | CPI| Evaluation | Feedback Team iGreen

  49. Project Plan • Planning Process • Interim plan initially • Quickly develop the MACRO plan • Delphi Estimation Method • Activities | ‘Expert’ Opinion | Consensus • “Granularized” Activities and Tasks for Tracking • Release Plan & Iterations Plan - Deliverable based Planning • Requirements | Iterations | Plan Team iGreen

  50. Risk Management • Risk Management Process • Informal Risk Management Plan • Identify | Prioritize | Mitigate | Contingency plan • Learning FLEX |Unplanned activities| Delphi Estimation • For example: • FLEX is new | Learning curve| Training • Training is our mitigation strategy • Entry Criteria | Exit Criteria • No contingency plan for the Risk Team iGreen

More Related