1. OPEN-ONES PROJECT MANAGEMENT SYSTEM INSTRUCTOR. LÊ NGỌC THẠCH (MR) TEAM MEMBERS. NGÔ ĐỨC DUY MẠNH HOÀNG TR ƯƠ NG PHẠM NGUYỄN TR Ư ỜNG GIANG TÔ CÔNG THANH HẢI OOPMS Team1

2. CONTENTS  Introduction  Plan  Requirement  Design  Implementation  Summary  Demo and QA OOPMS Team2

3. 3 INTRODUCTION INSTRUCTOR AND TEAM PROBLEMS OUR PROPOSAL APPLICATION OOPMS Team

4. 4 Instructor and Team LE NGOC THACH Instructor NGO DUC DUY Student MANH HOANG TRUONG Student PHAM NGUYEN TRUONG GIANG Student TO CONG THANH HAI Student OOPMS Team

5. 5 Problems CIO.com cites a Dynamic Markets surveyCIO.com cites a Dynamic Markets survey of 800 IT managers, reporting that 62 percent of IT projects fail to meet their schedules. Other data: 49 percent suffered budget overruns 47 percent had higher-than-expected maintenance costs, and 41 percent failed to deliver the expected business value and ROI Why? Inability to meet project requirements Missed deadlines Poor planning Content Deficiencies Exceeded budget How should we improve ? Defining scope clearly, reduce change requests. Meeting tasks deadline, deliverables by planning. Maintaining the required quality levels. Meeting the budget. Team Management. Plan for uncertainty, prepare for the unexpected. OOPMS Team

6. 6 Problems WHAT we are about to DO ???? Software application -Help software team -Assist PM -Help Dev, QA, Tester -Increate performance -Simplify the job -…. OOPMS Team

7. 7 Problems Legacy System.. Legacy system: …. 1.Complicated Process 2.Large cost 3.Not open source 4.Not modulization 5.…. OOPMS Team

8. 8 Our Proposal Easier to control: Schedule, Cost, Quality. By keep tracking: requirement, planner, Project status, timesheet, Defects… Easier to control: Schedule, Cost, Quality. By keep tracking: requirement, planner, Project status, timesheet, Defects… More efficient way to keep updated project’s information and status. More efficient way to keep updated project’s information and status. Project Manager Team Member OOPMS Team

9. 9 Application Web-based APPLICATION Android APPLICATION OOPMS Team

10. 10 SOFTWARE PROJECT PLAN SYSTEM OVERVIEW PROCESS MODEL TOOLS AND TECHNIQUES PROJECT PLAN OOPMS Team

11. 11 System Overview  Online Software Project Management Suite  provides powerful and efficient customized service for numerous kinds of managers from small to medium projects OOPMS Team

12. 12 System Overview Hardware Software. Personal computers for developing: 1 Gb of RAM, 20Gb of hard disk, Core 2 Duo 2.0 Ghz.. A server computer for testing : 2 Gb of RAM, 15Gb of hard disk, Core 2 Duo 2.0 Gh. Web Server: Apache Tomcat 6 + uPortal web app. Development: Glassfish + Portlet Container. Operating system: Windows, Linux. IDE: Eclipse, JSR 168 ( Java Specification Request ). DBMS: Oracle Express 10/11g. Source Control: SVN OOPMS Team

13. 13 Process Model Waterfall process Model OOPMS Team Spiral approach

14. Process Model OOPMS Team14 CMMI-DEV Process  four categories for process improvement and evaluation

15. 15 Tools and technologies Front-end technologies: jsp, jQuery, Javascript, CSS, html Back-end technologies: Hibernate Tools: Eclipse, Android SDK, notepad++, Oracle, uPortal, Glassfish, Portlet Container, MS office, Source Version, Chrome Architecture and design patterns: Three Tiers Architecture, Dependency Injection, Spring MVC Portlet OOPMS Team

16. 16 Project Plan PROJECT PLAN DuyNDTruongMH HaiTCT GiangPNT Requirement Management Android Version Documentation … Framework Timesheet Defect Management Project Planner Project Progress Dashboard Project Management Team Management Project info: cost, product, stage, risk, issue… … … OOPMS Team

17. 17 REQUIREMENT SPECIFICATION USER REQUIREMENT SYSTEM REQUIREMENT NON-FUNCTIONAL REQUIREMENT OOPMS Team

18. 18 User Requirement 1.Dashboard  Projects ‘status 2.Planner  keep track of tasks, progress 3.Project Eye  Project Management 4.Timesheet  Time management 5.DMS  Defect Management 6.Requirements  Requirement Management 7.Admin  User Admin (uPortal) 8.Report  export report 9.Android  Android dashboard version OOPMS Team

19. Document requirements for each use case Each includes:  Use case diagram  Actor  Summary  Goals  Triggers  Preconditions  Post conditions  Success scenarios 19 System Requirement  Exceptions  Relationship  Business rules  Description  Screen  Data field definitions OOPMS Team

20. 20 Non-functional Requirements Performance Usability Reliability Supportability …. OOPMS Team

21. 21 DETAIL DESIGN SYSTEM ARCHITECTURE UI DESIGN DETAIL DESIGN DATABASE DESIGN OOPMS Team

22. Portal - Portlets Offer broad range of resources and services. Allows aggregation of several back-end systems, processes. provide additional services such as single sign-on security, customization (i.e. personalization) etc.  the aggregator of a number of disparate applications in a highly personalized manner. OOPMS Team22

23. Portal - Portlets OOPMS Team23

24. Portal - Portlets OOPMS Team24

25. 25 System Architecture OOPMS Team

26. 26 UI Design OOPMS Team

27. Cost Management Planner – Project Status Report Timesheet DMS 27 Detail Design OOPMS Team

28. Features : support PM in management the budget and expense of the project. Help them make a suitable plan to stay in budget until the end of the project. The Cost Management include : - Budget - Invoice - Planner + One Time Expense + Daily Expense + Exceptional Expense, Exceptional Deduct + Type 28 Cost Management OOPMS Team

29. Features : allow PM to manage the budget of project. Keep the record of budget. 29 Budget OOPMS Team Invoice Features : - PM can see how much money are actually paid. Keep the record of invoice. - Export the invoice report to excel.

30. Features : - Manage the expense that happen once in the project. (money use to buy equipment, pay bill, …v.v) - Have pay function to send the expense to invoice. 30 One Time Expense OOPMS Team

31. 31 Database Design OOPMS Team

32. 32 IMPLEMENT TECHNOLOGIES TOOLS REVIEW TESTING OOPMS Team

33. 33 Technologies OOPMS Team

34. 34 Technologies OOPMS Team

35. 35 Tools OOPMS Team

36. 36 Review OOPMS Team

37. 37 Code - Review OOPMS Team

38. 38 Testing Module codePassFail Untes ted N/A Number of test cases Total 76 Project Eye 28 Planner 10 Requirement 8 8 Timesheet 12 DMS 4 2 6 Dashboard 1 1 2 Admin 3 3 Report 1 4 5 Android 22 OOPMS Team

39. 39 Testing – Response Time OOPMS Team Response time:

40. Features Compatibility Ease of Use Help & Support Pricing and Conditions 40 Summary OOPMS Team

41. 41 DEMO AND QA OOPMS Team

42. 42 Thank You For Listening OOPMS Team