1. SmartPosition Customer Review and Feedback Presentation

2. Format of Presentation Introduction Major sections of the project ◦Each section will be presented for 4 minutes ◦Followed by 2 minutes of discussion Finally 15 Minutes of Questions

3. Presentation Overview What you will see in today’s presentation ◦System overview ◦The requirements Elicitation Process ◦User requirements (URS) ◦Specification (SRS) ◦Formal Analysis ◦Testing ◦System Architecture ◦Questions

4. Overview The SmartPosition System An aid to improve the outcomes of soccer teams.

5. System Boundary Diagram

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

7. Requirements Elicitation The First Question - Pressman states The first question an engineer asks the client should be context free, focused on the customer and other stakeholders.

8. Requirements Elicitation Formal Requirements Specification Informal Requirements Raw Requirements Concept Inception

9. Analysis Process

10. 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

11. 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

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

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

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

15. User Acceptance Testing Detail the product testing techniques used at the user acceptance level. Describe what will be tested, what will not be tested and why.

16. User Acceptance Testing Detail the product testing techniques used at the user acceptance level. Describe what will be tested, what will not be tested and why.

17. Features to be tested 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

18. REPEL 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.

19. REPEL

20. REPEL

21. REPEL

22. REPEL

23. REPEL

24. TRACK 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.

25. TRACK

26. TRACK

27. REPEL/TRACK 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.

28. REPEL/TRACK

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

30. SILENT MODE

31. SWITCH on TRACKING UNIT 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.

32. SWITCH

33. SWITCH

34. DIAL on MASTER UNIT 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

35. DIAL

36. DIAL

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

38. Features NOT to be tested 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

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

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

41. System Qualities After analysing the stakeholders and non- functional requirements the following have appeared identified as the most important system qualities Availability Usability Modifiability Testability

42. Conceptual View

43. Implementation View

44. Candidate 1

45. Candidate 2

46. Candidate Evaluation Each criterion is given a score from 1 to 5. The candidate with the most points, is selected and candidate with the least points is the fall back option.

47. Build Plan List availability dates Describe how the team intends to build the product. Give a timeline etc.