1 / 12

Microbits project

Microbits project. …Moving from a Problem space to a Solution space. The Problem statement.

acornwell
Download Presentation

Microbits project

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. Microbits project …Moving from a Problem space to a Solution space

  2. The Problem statement • Fitness360 inc. want to produce an app that monitors a number of people for steps (later, more information such as heart rate, body temperature etc.) and relays the information to a database stored on a smartphone. • The smartphone will control a number of Micro:bits via Bluetooth, and they will return their data via Bluetooth. • The smartphone will store the results for each micro:bit and return them on demand via a simple interface • The interface will be as simple as possible on both devices.

  3. Context • Things will have to be relatively simple bearing in mind the stakeholders in this project (KS 3,4) • The designers will have to take account of the learners’ world.(weltanschauung)

  4. Requirements gathering • What exactly will the app do? • How will it do it? • Interview users, gather information: • Structured interviews • Round table conversations • Functional and non-functional aspects

  5. Requirements analysis -> Specification • Having gathered the requirements, we need to sort them into: • Functional (what the app actually does) • Non-functional (user interface etc.)

  6. Specification -> Design; Building a model • What methodology? Iterative prototyping • Think about MVC, 3 layers • Rapid prototyping most realistic • Statecharts / activity diagrams -> Pseudocode for both ends • Action diagrams better than flowcharts?

  7. The Draper Cycle

  8. Flowchart symbols Start / End Direction Process Decision Internal storage Data / input-output Subroutine Database

  9. Possible flowchart for Micro:bit step monitor Initialise Poll Cont request Y Send to cont Get data RQ? N Poll Data request Y N Update steps Get data RQ?

  10. Possible flowchart for smartphone controller

  11. Useful links Advanced article on Real Time system design using UML Article on Soft Systems methodology: http://www.cems.uwe.ac.uk/~fj-Maddix/PGCE/ssm.pdf

More Related