1 / 57

SmartPosition

SmartPosition. Customer Review and Feedback Presentation. Introduction Sections 4 minutes presentation 2 minutes questions 15 minutes questions. Formt. Overview. What you will see in today’s presentation System overview (System Boundary Diagram) The requirements Elicitation Process

joy
Download Presentation

SmartPosition

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. SmartPosition Customer Review and Feedback Presentation

  2. Introduction • Sections • 4 minutes presentation • 2 minutes questions • 15 minutes questions Formt

  3. Overview

  4. What you will see in today’s presentation • System overview (System Boundary Diagram) • The requirements Elicitation Process • User requirements • Specification • Formal Analysis • Testing • System Architecture • Questions Presentation Overview

  5. System Boundary Diagram

  6. A “Meeting of the Minds” • What is the purpose? What did we achieve? • An agreement on the system specifications free from undocumented assumptions. Requirements Elicitation

  7. Requirements Elicitation

  8. Requirements Elicitation

  9. Through this elicitation process we found that the customer was always happy to broaden the scope of the solution and often avoided agreeing on specifics. Requirements Elicitation

  10. Analysis Process

  11. Each stage of the analysis process allowed the project team to identify all aspects of the system that formed a requirement • The formal listing of requirement statements are being used by the system architects to produce both high and low level designs • Any changes to the requirements will result in a formal review of the SRS Analysis Process

  12. User Requirements

  13. The user requirement analysis was taken out in a procedural manner considering the three major steps namely: • 1) Eliciting requirements • 2)Stakeholder identification • 3)Stakeholder interviews • These points can further be elaborated in the report. User Requirements

  14. Analyzing requirements: determining whether the stated requirements are unclear, incomplete, ambiguous, or contradictory, and then resolving these issues. • Recording requirements: Requirements might be documented in various forms, such as natural-language documents, use cases ,user stories, or process specifications. • Eliciting requirements: the task of communicating with the customer or the user to determine what the requirements are. User Requirements

  15. Determining Raw requirements: • Raw Requirements were written down line by line from the specification that was given to us. • In the second step every statement of the raw requirement was cross referenced to check if it fits the 6 characteristics analysis. • To support the analysis a section for actions to be taken is provided to leave feedbacks or arguments that is to be discussed with the client or the stakeholder. User Requirements

  16. 6 characteristics required to fulfill the raw requirements to proceed for informal analysis. • 1) Cohesive • 2) consistency • 3) completeness • 4) feasible • 5) unambiguous • 6) verifiable User Requirements

  17. Architectural and critical requirements: • Critical requirements: • They are the requirements without which the other systems and the requirements would cease to work or synchronize. • Some of the critical requirements are stated below: User Requirements

  18. Each player tracking device shall operate at all times in one of four modes of operation: "TRACK", "REPEL", "TRACK/REPEL" and "OFF" • If a player tracking device cannot establish communication with the main unit after 60 seconds it will enter a standby state • The main unit shall store the last 60 minutes of tracking data • In "REPEL" mode the minimum configurable range between the player tracking devices shall be 3 meters. • All battery powered devices shall run for greater than 300 minutes before needing to be recharged • The iPad application shall provide a warning to the user when the persistent data storage reaches 90% of its capacity User Requirements

  19. Specifications

  20. Formal Analysis

  21. Formal Analysis Diagrams • System interaction • The communication and collaboration between objects within the system • Identifies domain classes, attributes and responsibilities of the system objects • Sequence Diagrams • Communication and interaction between objects • Time sequence behavior • Activity Diagrams • Model workflow • State behavior of system

  22. 3 Sub Systems • Main Unit • Player Tracking Device • iPad application • Initial system synchronisation sequence • Communications between sub systems identified System Setup

  23. View Tracking Data • Communication between sub systems • Position data pushed to main unit • iPad application GUI refresh • Timing of data calls between sub systems

  24. Sub system states identified • Sub system domain classes and functions identified • Workflow needed for a device to alarm Repelling of Players

  25. User Acceptance Testing

  26. User Acceptance Testing

  27. Features which to be tested are typical features of the systems. • They are taken from requirement analysis • Will represent for a complete working system. • Will also ensure the quality of the system Features to be tested

  28. Purpose: is used to train players to spread out on the field and not clump together. • Action: as defined in requirement analysis, if two tracking units come into the range of a tracking unit, they will start beeping. REPEL

  29. REPEL

  30. REPEL

  31. REPEL

  32. REPEL

  33. REPEL

  34. Purpose: reporting twice every second which other units come into the range of a tracking unit. • Action: Each tracking unit is reporting to the main unit twice every second. TRACK

  35. TRACK

  36. TRACK

  37. Purpose: a combination of REPEL and TRACK modes • Action: • If two tracking units come into the range of a tracking unit, they will start beeping. • Each tracking unit is reporting to the main unit twice every second. REPEL/TRACK

  38. REPEL/TRACK

  39. Purpose: avoid any impacts on players in a real soccer game. • Action: • Each tracking unit shall not start beeping in any scenarios. SILENT MODE

  40. SILENT MODE

  41. Purpose: to allow players to turn on/off their tracking units. • Action: • Turn off: device is off and no LED. • Turn on: each tracking unit shall: • Go to sleep if the master unit is off. • Be active if the master unit is on. SWITCH on TRACKING UNIT

  42. SWITCH

  43. SWITCH

  44. Purpose: to allow the coach to switch between modes on the master units. • Action: • Able to put it in Repel mode • Able to put it in TRACK mode • Able to put it in REPEL/TRACK mode • Able to turn it off DIAL on MASTER UNIT

  45. DIAL

  46. DIAL

  47. Battery evaluation • Configurable range • Interference • Waterproof • Stability Other features to be tested

  48. Size and weight • Internal system activities • For example: the system shall improve positional play for soccer teams • External system activities • For example: the system shall be designed so as to enable mass production of the design Features NOT to be tested

  49. Description of the system architecture. (use as many slides as you think necessary) Architecture

  50. Player - User • Coach - User • Project Owner - SportQuick CEO • Project Liaison - SportQuick Project Sponsor • Development Team - Red Team • Regulatory Department - Health and Safety Stakeholder Analysis

More Related