UTS Engineering and IT 49227 WSN 49227 WSN A2017 Assignment_1 v1.1 (3) 1 of 7 23/03/2017 (zc) 49227 WSN Assignment 1 Scoping the Smart Gym Project Assignment administration Assignment Value: 10% Students to hand in individual work Assignment is due: week 4. The assignment submission should take the form of a report. The total length of the report is no more than 8000 words. You should include a Title Page, the full report, and all references. All information sources must be appropriately acknowledged and a full bibliography is required. It is expected that this will be completely your own work. Therefore using the ‘cut and paste’ technique is not accepted. You should read relevant material, and then write your report in your own words. This report will be submitted to Turnitin, and so will be checked for plagiarism. For more information refer to: wiki.it.uts.edu.au/start/Academic_Integrity www.gsu.uts.edu.au/rules/16-2.html Submission Requirements A soft copy of the assignment must be submitted (in pdf format) to the Assignment Submission area (via Turnitin entry) in UTSOnline. Ensure that your soft copy of the assignment is first checked only via www.turnitin.com and then submitted if satisfying similarity (the lower the better but not higher than 25- 30%) is obtained. Late assignments will incur a penalty of 10% per day. No assignments will be accepted after 7 days (100% marks penalty) as the mark for this assignment will then be zero (0). The submission time and date should be shown on the receipt received from your submission to Turnitin. The Report must have a title page with the following information:  Course Name – Wireless Sensor Networks  Course Number – 49227  Report Title – Written Assignment  Report due date – Week 4  Word Count – Found under ‘Tools’ on the menu bar  Name and Student Number You are to provide a Softcopy of all referenced material or other documents (such as pamphlets) with this assignment on Monday. Proper referencing of all sources is essential. Referencing should follow the Harvard system. If you need assistance with this contact the UTS library or refer to: http://www.bell.uts.edu.au/referencing 90% of all your references must be from an authoritative source, such as Journal Papers, Conferences or Standards. So if you have 10 References, no more than 1 can be from a non-authoritative source, such as Wikipedia or HowStuffWorks. If you have less than 10 References, you are not allowed to use a non-authoritative source. General Note 49227 WSN uses a problem based learning approach to the task of analysing a medium complexity, computer based system, via projects that have teams including no more than 4-5 students. For this assignment students are required to provide an individual perspective on the project's scope, initial requirements (light version), system usage scenarios and preliminary WSN model/architecture. The assignment should discuss the motivation and rationale for the individual choice of sensing/actuation technology that enables the WSN-based solution in context of the problem.UTS Engineering and IT 49227 WSN 49227 WSN A2017 Assignment_1 v1.1 (3) 2 of 7 23/03/2017 (zc) Project’s Brief , Name of the Project: Smart Gym Background The project aims to provide members and management of 24-7 fitness club at UTS with state of the art gymnasium and sport facilities that are safe, secure, highly personalised, available 24-7, well managed and well maintained. Your project need to explore modern WSN technology to cover all personal/group fitness needs and requirements with range of WSN instrumented cardio, free weights, functional training & personal training services. Each member can have an access to smart sensors and each piece of equipment, rooms and other gym facility are to be equipped with a range of sensors and actuators to allow support staff to be well informed about your individual/group needs. Also whenever and intervention or emergency is required the support staff will be able to provide required assistance. WSN instrumented facilities are to enable advanced support and training by monitoring each individual member activity(ies) on daily, weekly and monthly/annual basis. Positive, negative and anomalous health patterns observed thanks to the advanced WSN devices should be reported club members and staff member in order to provide help, training, guidance and possibly assistance with training programs. WSN instrumentation of the equipment should allow reducing the number of possibly accidents, equipment failures, as well as, monitoring patterns of usage of the equipment and the occupancy of gym facilities/rooms by monitoring the facility 24 hours a day. In order to provide training and coaching services, a WSN-based solution should support upload/download of personal data to the cloud, gym server/web site and/or smart phone. Training and coaching function of the gym involves fitness assessment, personal training, small group program, as well as, specialised training (rehabilitation) programs. The WSN will need to support gym’s Cardio equipment such as: elliptical cross-trainers, exercise cycles, rowing machines, stair climbers, and treadmills. Functional training stations that use bosu, kettlebells, medicine balls, plyometric boxes and resistance bands will also require to be monitored using WSN motes Use of WSN technology for personal health, equipment, gym facility monitoring for safety and security as well as for effective gym management is becoming increasingly popular. Typical solutions involve monitoring and tracking of human activity, movement and location, as well as, monitoring events, presence and occupancy monitoring and tracking of humans, objects and rooms. Finding the places and time/day of the human activity congestion, as well as, monitoring the intensity and levels of demand for the equipment, facilities and space is the key to effective functioning of many modern gym facilities/infrastructures (i.e. gyms at sport facilities, gyms at airports, gyms in high rise buildings, gyms in universities, gyms in hotels etc.). Additionally monitoring and tracking of human and machines, events and objects in various locations improve safety and security of the infrastructure;UTS Engineering and IT 49227 WSN 49227 WSN A2017 Assignment_1 v1.1 (3) 3 of 7 23/03/2017 (zc) Architectural Models and Typical Configuration Fig 1. A typical architecture of a Body Area Network (BAN) based solution for the Smart Gym. Fig 2. A topology of 6LowPAN based Body Area Network (BAN) based solution for the Smart Gym. Fig 3. Architecture of the smart mote based on TI CC2650 Sensortag. Sensor devices provided for students in 49227 subjects 1. CC2650 Sensortag motes are equipped with the following on-board 10 sensors: ambient light, digital microphone, magnetic sensor, humidity sensor, pressure sensor, accelerometer, gyroscope, magnetometer sensor, object and ambient temperature sensor. See Fig. 3 2. DFrobot APDS-9960 Gesture Sensor Board https://tronixlabs.com.au/news/new-product-dfrobot-apds9960-gesture-sensor-board-tronixlabs-australia/ 3. MAXREFDES117#: HEART-RATE AND PULSE-OXIMETRY MONITOR https://www.digikey.com/en/articles/techzone/2016/oct/maxrefdes117-heart-rate-and-pulse-oximetry-monitorUTS Engineering and IT 49227 WSN 49227 WSN A2017 Assignment_1 v1.1 (3) 4 of 7 23/03/2017 (zc) Organisation For all Assignments (1/2/3), students are expected to form groups of three or four in order to create a basic prototype for smart gym monitoring and management system that involves sensors, actuators and control devices that are safely placed on the members’ body, the gym equipment and various places (rooms) around the gym. In order to test its functionality, a demonstration shall be held on last day/session of 49227 WSN in Autumn 2017. A practical exam/demo shall be conducted based on the outcome of the demonstration. Further details for this shall be provided closer to the due date. The design and implementation technique is entirely up to the development team; however it is necessary to justify any design decisions made. Submissions shall be marked on the following:  Design ingenuity  System functionality  Code efficiency and effectiveness  Design quality, its justifications and quality of the project documentation Assignment 1 Deliverables: For Assignment 1 individual students are required to provide a light version of the project plan(s) in context of the scope, the team organisation, schedule/milestones and final deliverables. This first assignment is of an introductory nature to the implementation phase of the project. Its focus is on the understanding of the problem space, key/driver requirements, the choice of WSN technology and what would be the initial model of the architecture of proposed solution. Other topics this assignment should cover involve implementation issues, how resources can be critically applied, how the budget can be spent, critical risks/mitigation strategies, commitment to deliverables for the main assignment (Assignment 2) and the development of a Project Systems Engineering Document. Its ultimate aim is to explore, compare and integrate team’s ideas related to development of the final solutions/options. This assignment will help to determine the selection of the preferred option(s) for the final WSN system solution that the team will decide on when working in teams for Assignments 2 and 3. This is the preliminary effort by individual students that needs to help in scoping and the formal analysis phase conducted by the entire Project’s team. The individual students need to prepare a light form of:  Project Definition and Scope  System Requirements Specification;  Initial Architectural model/High Level Design implemented using a formal notation/ methodology.  Project Plan is made of:: System Development Plan, System Test/Integration Plan and System Quality and Assurance Plan; Other deliverables may include artefacts/templates for the group-based efforts, such as:  individual timesheets and budgetary statements, schedules,  meeting/discussion minutes, action sheets,  quality audit reports and review outcomes, project status reports. The aim of this assignment is to: a. State the problem of the assigned project, in a clear and unambiguous way; b. State clearly the magnitude of the task; c. Complete the preliminary analysis of the system for the assigned project; d. Show evidence that the quality management/assurance will be carried out at the individual level. The assignment consists of two main parts: Assignment 1 – Part 1: Project Scope and Light Documentation Deliverable The main purpose of this assignment is to scope the problem, as well as, collect and present together the completed “formal” and “informal” deliverables - which include artefacts from the project process itself.UTS Engineering and IT 49227 WSN 49227 WSN A2017 Assignment_1 v1.1 (3) 5 of 7 23/03/2017 (zc) Principles underlying the project’s scope should include, but not necessarily in this order:  The what - A demonstration to the customer that the project problem is well understood and what shall be the final deliverable.  The how - A proper, realisable schedule for achieving the project, how the budget is to be managed and spent, the project approach and methodology, etc.  The when – A discussion of milestones and what is the outcome of those milestones.  The who – Discussion on participants, how they are organised, any re-structuring issues, etc. You might include a discussion on the resources you intend to use such as CASE tools, COTs, platforms, customer supplied resources, etc. It is assumed the project documentation deliverable will be divided into the following sections and appendices and be handed in a pdf file form. The pdf file should contain page dividers. Dividers should separate each appendix. The first portion of the deliverable shall contain a “road map” that accurately defines the layout of the deliverable and which section/appendix/portion is contained behind each divider. The deliverable document can be tailored as follows: Section 1 Introduction and Scope of the project Aims to explain the problem, its context and provide an overview of the project and should include a “roadmap” / table of content. Section 2 System Requirements Specification – light version  Paragraph/s defining the team’s understanding of the assigned problem relevant to the SRS, supported by a context or boundary diagram and complete with explanatory text. The diagram should include: operational processes (sub-systems/components) and control/data connectivity. This has to be consistent with the development methodology, which must be strictly applied.  Presentation semantics of the requirements – at the least mandatory and non-mandatory phrases.  Presentation of “raw” requirements categorised into functional, non-functional, performance, behavioural and design constraints.  Some evidence of informal/formal analysis including diagrams and one formal method representative of the methodology expressed for the project.  Test/validation components, including degree of planned testing and classes of the test. Section 3 Architecture / High Level Design (Models, Views, Simulation, Mock-up UIs) – light version  Paragraph/s defining the team’s understanding of the assigned problem supported by a context or boundary diagram, complete with explanatory text, strictly for architecture purposes. This has to be consistent with the development methodology, which must be strictly applied.  System’s/Architectural model semantics.  There shall be depictions (graphs, tables, descriptions, etc.) of how the requirements are being “mapped” to the various subsystems, components, etc. The requirements must be directly derived from the SRS, validation/traceability matrix. Section 4 Project Plan(s) – light version System Development Plan (SDP).  SDP semantics.  The plan should extend the preliminary SDP (assignment 1) and include a section describing how much the preliminary SDP (assignment 1) has been altered, and the reasons for the alteration.  Typically the plan should cover, but not be limited to: o SDP Scope and objective; o Group Organisation and Managerial Approach; o Work Breakdown Structure – WBS;UTS Engineering and IT 49227 WSN 49227 WSN A2017 Assignment_1 v1.1 (3) 6 of 7 23/03/2017 (zc) o Schedule: This semester, next semester; o Roles and Responsibilities structure; o Time estimation issues; o Cost estimation and budgeting; and o Critical Risk Identification plus mitigation strategies. System Test/Integration Plan (STP).  STP semantics.  The plan should be refined from that which has been presented for assignment 1.  The plan should cover, but not be limited to: o Testing approaches and criteria; o Scheduling approaches; o Resources and Manpower; o Managerial issues; o Responsibilities; o Discrimination between Low Level, Integration and Validation testing, etc.  Validation issues, including traceability to the requirements, realistic testing that can be carried out within 2 hours in the laboratory.  Pro-forma validation testing report, including separate pages describing each and every test/group of tests.  A section describing how much the preliminary STP (assignment 1) has been altered and the reasons for the alteration.  Make provisions for subsystem/system integration tests and the final acceptance tests (i.e FQT) System Quality Assurance Plan (SQAP).  SQAP semantics.  The plan should extend the preliminary SQAP (assignment 1) and include a section describing how much the preliminary SQAP (assignment 1) has been altered, and the reasons for the alteration.  The plan should cover, but not be limited to: o Process and Product Quality issues and measurement criteria; o Managerial Approach and procedures for assuring the quality of the process and the product; o Policy issues, including the definitions of Risk, Configuration Management, Defect Management, Change Control, Critical event handling, etc. o Section 5 Conclusion.  This section should be structured but not be limited to: o Summary – Summary of your findings;. Section 6 Appendices.  Administration records – including minutes of meetings, action sheets, review results, walkthrough  Other Appendices – containing any other information regarded as relevant i.e. Bibliography. Assignment 1 – Part 2: Selection of Sensor /Actuator Technology The second part should cover the rationale behind the choice of your sensor(s)/actuators(s). Typically this part of the report would include:  What is your selected sensor or set of sensors and application?  Elaborate what the selected sensor (s) supposed to do in WSN-based application  Discuss range of input and output (for example input in degC output in microV... etc.)  Elaborate on linearization issues?UTS Engineering and IT 49227 WSN 49227 WSN A2017 Assignment_1 v1.1 (3) 7 of 7 23/03/2017 (zc)  Discuss what is the accuracy/stability desired (i.e., over what range is this accuracy or stability required?  Discuss what sensitivity is required  Describe what is the impedance at the output  Comment on the error sources in the transducer, single ended output, differential output, noise considerations, offsetting required?  Supplementary data sheets  Typical applications  Other comments? .