healthy kids zone
Download
Skip this Video
Download Presentation
Healthy Kids Zone

Loading in 2 Seconds...

play fullscreen
1 / 46

Healthy Kids Zone - PowerPoint PPT Presentation


  • 80 Views
  • Uploaded on

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.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Healthy Kids Zone' - lloyd


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
things don t change
Things Don’t Change
  • System Objectives
  • Benefit Chain Diagram
  • System Boundary Diagram
  • Project Constraints
  • Element Relationship Diagram
  • Business Workflow Diagram
  • Level of Services
prototype

Prototype

Junjunji

progress
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.
things don t change1
Things don’t change
  • System Context Diagram
  • Hardware Component Diagram
  • Software Component Diagram
  • Deployment Diagram
  • Sequence Diagram
outline
Outline
  • Use cases
  • Database schema
  • Internal Interfaces
use cases
Use cases
  • Adapt with requirement & test cases updates
  • 12 top-level use cases in web and mobile
database
Database
  • Store critical information of surveys/paths/schools/questions/answers and relations between them
  • Support features like markers/comments/images/path display
coincomo assessment
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
project plan
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)
test plan cases

Test Plan & Cases

Chenglu Wang

test identifier case basis
Test Identifier & Case Basis
  • 12 Modules ---- 12 Test Identifier
  • 32 Features ---- 24 Test Case
  • 62 Small Features ---- 62 Win Condition
relationship between identifier and test case
Relationship between Identifier and Test Case
  • The whole diagram will be showed in Visio
feasibility analysis

Feasibility Analysis

Chad Honkofsky

current risks
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
definition of done
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
ad