1 / 46

Healthy Kids Zone

Healthy Kids Zone. Team 14. Operational Concept Description. Xu Zhang. Things Don’t Change. System Objectives Benefit Chain Diagram System Boundary Diagram Project Constraints Element Relationship Diagram Business Workflow Diagram Level of Services. System Capabilities.

lloyd
Download Presentation

Healthy Kids Zone

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. Healthy Kids Zone Team 14

  2. Operational Concept Description Xu Zhang

  3. Things Don’t Change • System Objectives • Benefit Chain Diagram • System Boundary Diagram • Project Constraints • Element Relationship Diagram • Business Workflow Diagram • Level of Services

  4. System Capabilities

  5. Things do change

  6. Prototype Junjunji

  7. Progress • Deploy HKZ website and database on the GoDaddy server which clients provide. • Changed part of website user interface • Changed part of mobile user interface • Prototyping connection between mobile and database (on remote server) to exchange the data.

  8. Change on website UI

  9. Change on mobile UI

  10. System Architecture Ye Tao

  11. Things don’t change • System Context Diagram • Hardware Component Diagram • Software Component Diagram • Deployment Diagram • Sequence Diagram

  12. Outline • Use cases • Database schema • Internal Interfaces

  13. Use cases • Adapt with requirement & test cases updates • 12 top-level use cases in web and mobile

  14. Butterfly

  15. Peacock

  16. Goldfish

  17. Answer a Question

  18. Answer a Question cont’d

  19. Database • Store critical information of surveys/paths/schools/questions/answers and relations between them • Support features like markers/comments/images/path display

  20. Database Schema

  21. Interfaces

  22. Life Cycle Plan Yang Wang

  23. Roles & Responsibilities

  24. COINCOMO Assessment • Total team efforts = 9.77 person month • One team efforts = 1.67 person month • So we need 5.85 person • 7 in 577a and 6 in 577b, still acceptable

  25. ProjectPlan • 12 Modules ---- 12 Test Identifiers • 32 Features ---- 24 Test Cases • 62 Small Features ---- 62 Win Condition • 3 Construction Iterations • Iteration 1 (2.13 – 3.5) • Iteration 2 (3.6 – 3.26) • Iteration 3 (3.26 – 4.16) • Transition Iteration (4.16 – 4.30)

  26. Traceability Matrix

  27. Iteration Plan

  28. Transition Plan

  29. Test Plan & Cases Chenglu Wang

  30. Test Strategy

  31. Test Identifier & Case Basis • 12 Modules ---- 12 Test Identifier • 32 Features ---- 24 Test Case • 62 Small Features ---- 62 Win Condition

  32. Relationship between Identifier and Test Case • The whole diagram will be showed in Visio

  33. Requirement Traceability Matrix

  34. Test Plan

  35. Test schedule

  36. Acceptance Test

  37. Test Case List

  38. Test Case List (cont’d)

  39. Test Case TC-02-02

  40. Test Case TC-02-02 (cont’d)

  41. Feasibility Analysis Chad Honkofsky

  42. Current Risks • Development to proceed without formal interface definition • Define general messages for each interface • Proceed with development and interface definition concurrently • Expect some updates • Development will help drive the definition of interface • Undefined survey export format • Walk through statistical analysis of paper survey results with customer to glean information • Mobile app prototype has minimal working code • Team meeting this weekend to further decompose tasks needed for mobile development

  43. Traceability Matrix

  44. Definition of Done • Source code checked into github repository • Baseline compiled without error from repository • Deploy module to appropriate test environment • Unit Tests Completed • Code and Unit Test Peer Review Completed • Incorporated Peer comments to source code and checked into repository • New Baseline compiled without error • Re-run Unit Test

  45. Metrics (Effort Report)

More Related