As1 - 1682 - GCS0803 - NX - Hua Kien Phuc - GCS190254 [PDF]

Zitiervorschau

Higher Nationals in Computing

Internet of Things ASSIGNMENT No.1 Project name:

------------------------------

Learner’s name: Hua Kien Phuc Assessor name: NGUYEN VAN SON Class: GCS0803_NX Learner’s ID: GCS190254 Subject’s ID: 1690 Assignment due:

Assignment submitted:

ASSIGNMENT 1 FRONT SHEET Qualification

TEC Level 5 HND Diploma in Computing

Unit number and title

Unit 43: Internet of Things

Submission date

Date Received 1st submission

Re-submission Date

Date Received 2nd submission

Student Name

Student ID

Class

Assessor name

Student declaration I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I understand that making a false declaration is a form of malpractice. Student’s signature Grading grid

P1

P2

P3

P4

M1

M2

M3

M4

D1

D2

 Summative Feedback:

 Resubmission

Feedback:

Grade: Assessor Signature: Internal Verifier’s Comments:

Date:

Signature & Date:

2|Page

ASSIGNMENT 1 BRIEF

Qualification

BTEC Level 5 HND Diploma in Computing

Unit number

Unit 43: Internet of Things

Assignment title Academic Year Unit Tutor Submission

Issue date

date

IV name and date

Submission Format: Format:

This assignment is an Individual assignment and specifically including 1 document: You must use font Calibri size 12, set number of the pages and use multiple line spacing at 1.3. Margins must be: left: 1.25 cm; right: 1 cm; top: 1 cm and bottom: 1 cm. The reference follows Harvard referencing system. The recommended word limit is 2.000-2.500 words. You will not be penalized for exceeding the total word limit. The cover page of the report has to be the Assignment front sheet 1.

Submission Students are compulsory to submit the assignment in due date and in a way requested by the Tutors. The form of submission will be a soft copy posted on http://cms.greenwich.edu.vn/ Note:

The Assignment must be your own work, and not copied by or from another

student or from books etc. If you use ideas, quotes or data (such as diagrams) from books, journals or other sources, you must reference your sources, using the Harvard style. Make sure that you

3|Page

know how to reference properly, and that understand the guidelines on plagiarism. If you do not, you definitely get fail Unit Learning Outcomes: LO1 Analyze what aspects of IoT are necessary and appropriate when designing software applications LO2 Outline a plan for an appropriate IoT application using common architecture, frameworks, tools, hardware and APIs LO3 Develop an IoT application using any combination of hardware, software, data, platforms and services. LO4 Evaluate your IoT application and detail the problem your IoT application solves, the potential impact on people, business, society and the end user and the problems it might encounter when integrating into the wider IoT ecosystem

Assignment Brief and Guidance: You currently work as a product developer for a new startup where you design IoT products for the consumer, corporate, government and defense clients. As part of your role your manager has tasked you to plan and develop a new IoT product, service or application for a potential client. You are required to identify a target user and conduct tests with this user and include this feedback into multiple iterative versions of your product. Part 1 (Assignment 1): For the first part, you must: •

•

Plan an IoT application for a specific target end user and the tests you intend to conduct with this user. This plan will be in the form of a document and will include supporting evidence and material, such as user personas and customer journey maps. Create multiple iterations of your application and modify each iteration with enhancements gathered from user feedback and experimentation. This will follow the pathway outlined in your plan. (log book,)

Part 2 (Assignment 2): For the first part, you must: •

•

Show evidence about Developed IoT application using any combination of hardware, software, data, platforms and services (video or images of your IoT system with code snippet) Evaluate your IoT application and detail the problem your IoT application solves, the potential impact on people, business, society and the end user and the problems it might encounter when integrating into the wider IoT ecosystem

4|Page

5|Page

Learning Outcomes and Assessment Criteria Pass

Merit

Distinction

LO1 Analyse what aspects of IoT are necessary and appropriate when designing software applications P1 Explore various forms of IoT functionality. P2 Review standard architecture, frameworks, tools, hardware and APIs available for use in IoT development.

M1 Evaluate the impact of common IoT architecture, frameworks, tools, hardware and APIs in the software development lifecycle.

D1 Evaluate specific forms of IoT architecture and justify their use when designing software applications.

M2 Review specific forms of IoT architecture, frameworks, tools, hardware and APIs for different problem-solving requirements.

LO2 Outline a plan for an appropriate IoT application using common architecture, frameworks, tools, hardware and APIs P3 Investigate architecture, frameworks, tools, hardware and API techniques available to develop IoT applications. P4 Determine a specific problem to solve using IoT.

M3 Select the most appropriate IoT architecture, frameworks, tools, hardware and API techniques to include in an application to solve this problem. M4 Apply your selected techniques to create an IoT application development plan.

D2 Make multiple iterations of your IoT application and modify each iteration with enhancements gathered from user feedback and experimentation.

6|Page

Contents 1.

Internet of things (P1, P2, P3) ......................................................................................................... 9 1.1

History of IoT ........................................................................................................................... 9

1.2

Applications ............................................................................................................................. 9

1. Smart home....................................................................................................................................... 10 2. Wearables ......................................................................................................................................... 10 3. Smart City .......................................................................................................................................... 10 4. Smart grids ........................................................................................................................................ 10 5. Industrial internet ............................................................................................................................. 10 6. Connected car ................................................................................................................................... 11 7. Connected Health (Digital health/Telehealth/Telemedicine)........................................................... 11 8. Smart retail........................................................................................................................................ 11 9. Smart supply chain ............................................................................................................................ 11 10. Smart farming ................................................................................................................................. 11 1.3

Trends and characteristics .................................................................................................... 12

1.4 Standard architecture, frameworks, tools, hardware and APIs available for use in IoT development. .................................................................................................................................... 12 M1. Evaluate the impact of common IoT architecture, frameworks, tools, hardware and APIs in the software development lifecycle............................................................................................................ 13 Abstract ................................................................................................................................................. 13 Goal ....................................................................................................................................................... 13 Method ................................................................................................................................................. 13 Results ................................................................................................................................................... 13 M2. Review specific forms of IoT architecture, frameworks, tools, hardware and APIs for different problem-solving requirements. ............................................................................................................. 13 IoT Architecture Basics .......................................................................................................................... 14 Common Architectures: ........................................................................................................................ 14 Three Layer (Tier) IoT Architecture ....................................................................................................... 14 2.

IoT system requirement Specification (P4) ................................................................................... 15

Functions of system .............................................................................................................................. 15 3.

Planning (M4) ................................................................................................................................ 16 3.1

WBS ....................................................................................................................................... 16

3.2.What is WBS ( Work Breakdown Structure ) .................................................................................. 16 Deliverable-Based Work Breakdown Structure .................................................................................... 17 Phase-Based Work Breakdown Structure ............................................................................................. 17

7|Page

1.2 Schedule .......................................................................................................................................... 18 4. Preparing equipments, hardwares, tools (M3) ................................................................................. 18 4.

Feedback (D2) ............................................................................................................................... 19

5.

References .................................................................................................................................... 20

8|Page

1. Internet of things (P1, P2, P3) 1.1 History of IoT The Internet of Things term is created by Kevin Ashton policymaking director of the AutoID Center: "I could be wrong, but I'm fairly sure the phrase "Internet of Things" started life as the title of a presentation I made at Procter & Gamble (P&G) in 1999. Linking the new idea of RFID in P&G's supply chain to the then-red-hot topic of the Internet was more than just a good way to get executive attention. It summed up an important insight which is still often misunderstood."

1.2 Applications We measured three things: What people search for on Google, what people talk about on Twitter, and what people write about on LinkedIn. The highest score received a rating of 100%, the other Internet of Things applications were ranked with a percentage that represents the relation to the highest score (relative ranking).

Figure 1 Aplication

9|Page

1. Smart home Smart Home clearly stands out, ranking as highest Internet of Things application on all measured channels. More than 60,000 people currently search for the term “Smart Home” each month. This is not a surprise. The IoT Analytics company database for Smart Home includes 256 companies and startups. More companies are active in smart home than any other application in the field of IoT. The total amount of funding for Smart Home startups currently exceeds $2.5bn. This list includes prominent startup names such as Nest or AlertMe as well as a number of multinational corporations like Philips, Haier, or Belkin. 2. Wearables Wearables remains a hot topic too. As consumers await the release of Apple’s new smart watch in April 2015, there are plenty of other wearable innovations to be excited about: like the Sony Smart B Trainer, the Myo gesture control, or LookSee bracelet. Of all the IoT startups, wearables maker Jawbone is probably the one with the biggest funding to date. It stands at more than half a billion dollars! 3. Smart City Smart city spans a wide variety of use cases, from traffic management to water distribution, to waste management, urban security and environmental monitoring. Its popularity is fueled by the fact that many Smart City solutions promise to alleviate real pains of people living in cities these days. IoT solutions in the area of Smart City solve traffic congestion problems, reduce noise and pollution and help make cities safer. 4. Smart grids Smart grids is a special one. A future smart grid promises to use information about the behaviors of electricity suppliers and consumers in an automated fashion to improve the efficiency, reliability, and economics of electricity. 41,000 monthly Google searches highlights the concept’s popularity. However, the lack of tweets (Just 100 per month) shows that people don’t have much to say about it. 5. Industrial internet The industrial internet is also one of the special Internet of Things applications. While many market researches such as Gartner or Cisco see the industrial internet as the IoT concept with the highest overall potential, its popularity currently doesn’t reach the masses like smart home or wearables do. The industrial internet however has a lot going for it. The industrial internet gets the biggest push of people on Twitter (~1,700 tweets per month) compared to other non-consumer-oriented IoT concepts.

10 | P a g e

6. Connected car The connected car is coming up slowly. Owing to the fact that the development cycles in the automotive industry typically take 2-4 years, we haven’t seen much buzz around the connected car yet. But it seems we are getting there. Most large auto makers as well as some brave startups are working on connected car solutions. And if the BMWs and Fords of this world don’t present the next generation internet connected car soon, other well-known giants will: Google, Microsoft, and Apple have all announced connected car platforms. 7. Connected Health (Digital health/Telehealth/Telemedicine) Connected health remains the sleeping giant of the Internet of Things applications. The concept of a connected health care system and smart medical devices bears enormous potential (see our analysis of market segments), not just for companies also for the wellbeing of people in general. Yet, Connected Health has not reached the masses yet. Prominent use cases and large-scale startup successes are still to be seen. Might 2015 bring the breakthrough? 8. Smart retail Proximity-based advertising as a subset of smart retail is starting to take off. But the popularity ranking shows that it is still a niche segment. One LinkedIn post per month is nothing compared to 430 for smart home. 9. Smart supply chain Supply chains have been getting smarter for some years already. Solutions for tracking goods while they are on the road, or getting suppliers to exchange inventory information have been on the market for years. So while it is perfectly logic that the topic will get a new push with the Internet of Things, it seems that so far its popularity remains limited. 10. Smart farming Smart farming is an often overlooked business-case for the internet of Things because it does not really fit into the well-known categories such as health, mobility, or industrial. However, due to the remoteness of farming operations and the large number of livestock that could be monitored the Internet of Things could revolutionize the way farmers work. But this idea has not yet reached large-scale attention. Nevertheless, one of the Internet of Things applications that should not be underestimated. Smart farming will become the important application field in the predominantly agricultural-product exporting countries.

11 | P a g e

1.3 Trends and characteristics As the Internet of Things (IoT) permeates homes, cities and office buildings as well as industries like retail and health care, It’s clear that connected devices are changing how people interact with virtually everything around them. Technologies such as 5G – the next generation of cellular connectivity – and edge computing – an architecture bringing compute closer to the users and devices that need it – have enhanced the capabilities of IoT devices. They have made it possible for wearables devices to convey health data in milliseconds, a fingerprint scan to admit you to a building or a voice command to schedule a meeting. 5G and edge computing technologies have furthered the potential of IoT devices, boosting data transport speed and reducing data latency. As a result, IoT market growth is predicted to continue to grow apace in 2020 and beyond. International Data Corporation (IDC) estimates that there will be 41.6 billion connected IoT devices, or “things,” generating 79.4 zettabytes of data in 2025. Despite this growth, and the clear opportunities of IoT in various sectors, successful adoption of IoT technologies faces challenges. In 2017, Microsoft data indicated that 30% of companies’ IoT projects failed at the proof-of-concept phase, and only 26% of projects were deemed successful. That may be because roughly one-half of respondents to a Capgemini study had not identified a clear business case for IoT, and three in five said they struggle to realize value from their initiatives because they lack the analytics capabilities. As partners consider the growth opportunity in selling IoT services, it’s important to consider how these still-nascent technologies can best succeed. According to recent McKinsey data, many companies report a 10-15% cost savings from IoT projects. While substantial, there is still a distance to go to get ROI from these projects.

1.4 Standard architecture, frameworks, tools, hardware and APIs available for use in IoT development. Still, when talking about the Internet of Things, much attention is paid to its potential. News about what IoT will be able to do and how it will empower our lives keeps flooding in, but for many it may seem that these uplifting visions don’t translate into reality as fast as we wish they could. Nevertheless, the big change does happen, yet it happens in dribs and drabs rather than in giant leaps. The reason for this is quite simple, but it tends to stay out of the public eye: it is the inherent diversity of IoT systems that stifles the progress and often stands in the way to make all things connected. As one of two presumably biggest challenges standing before IoT (the other being security), fragmentation is at the core of the Internet of Things because of the diverse nature of the Things that it aims to connect. Putting any IoT system to work requires harnessing all the resources, hardware, software, and systems, however varied they all may be, into one single

12 | P a g e

framework to form an integrated, reliable, and cost-effective solution. In simple terms, every IoT deployment needs a rock-solid IoT architecture to be able to serve its designed purpose; the resulting efficiency and applicability of the system largely depends on the quality of the infrastructure developed. M1. Evaluate the impact of common IoT architecture, frameworks, tools, hardware and APIs in the software development lifecycle. Abstract Motivation: In modern it systems, the increasing demand for computational power is tightly coupled with ever higher energy consumption. Traditionally, energy efficiency research has focused on reducing energy consumption at the hardware level. Nevertheless, the software itself provides numerous opportunities for improving energy efficiency. Goal: Given that energy efficiency for it systems is a rising concern, we investigate existing work in the area of energy-aware software development and identify open research challenges. Our goal is to reveal limitations, features, and tradeoffs regarding energyperformance for software development and provide insights on existing approaches, tools, and techniques for energy-efficient programming. Method: We analyze and categorize research work mostly extracted from top-tier conferences and journals concerning energy efficiency across the software development lifecycle phases. Results: Our analysis shows that related work in this area has focused mainly on the implementation and verification phases of the software development lifecycle. Existing work shows that the use of parallel and approximate programming, source code analyzers, efficient data structures, coding practices, and specific programming languages can significantly increase energy efficiency. Moreover, the utilization of energy monitoring tools and benchmarks can provide insights for the software practitioners and raise energyawareness during the development phase. M2. Review specific forms of IoT architecture, frameworks, tools, hardware and APIs for different problem-solving requirements.

There are essentially three major types of IoT architectural contexts: application specific, open platform and Network as a Service (NaaS). This article summarizes the leading trends in end-to-end, open platform IoT architectures where scalability and interoperability are major driving factors. In alignment with the NetBurner philosophy, a viewpoint is taken that a modular and interoperable approach to IoT architectures can help reduce risk and time to market, while at the same time increasing innovation. Therefore, the article also leans away from architectures

13 | P a g e

which risk dependencies on proprietary protocols or NaaS architectures, also known as “vendor lock-in”. IoT Architecture Basics So what are we looking for in an “end-to-end” or complete IoT architecture anyway? Here are some important requirements [1] [2] : Concurrent Data Collection – support for collection, analysis and control from a large number of sensors or actuators Efficient Data Handling – minimize raw data and maximize actionable information Connectivity and Communications – provide network connectivity and flexible, robust protocols support between sensors/actuators and the cloud Scalable – scale individual elements in the system using the same architecture Security – end to end encryption and monitoring Availability and Quality of Service – minimal latencies and fault tolerant Modular, Flexible and Platform-independent – each layer should allow for features, hardware or cloud infrastructure to be sourced from different suppliers Open Standards and Interoperable – communication between the layers should be based on open standards to ensure interoperability Device Management – enable automated/remote device management and updates Defined APIs – each layer should have defined APIs that allow for easy integration with existing applications and integration with other IoT solutions

Common Architectures: While we can’t cover all of the possibilities and permutations, the following group of architectures should give you a greater understanding of the core design considerations and typical primary functional layers in an end-to-end IoT stack.

Three Layer (Tier) IoT Architecture While there are myriad bits that build a complete end-to-end IoT architecture, this architecture simplifies it down to three fundamental building blocks [3] : Perception layer – Sensors, actuators and edge devices that interact with the environment Network Layer – Discovers, connects and translates devices over a network and in coordination with the application layer Application Layer – Data processing and storage with specialized services and functionality for users

14 | P a g e

2. IoT system requirement Specification (P4) Project name

IoT Avoid Obstacles ( IAO)

21st , March 2021 Project end date 8th , May 2021 Description This project provide an IoT that avoid obstacles with the shape base on car. We hope that our product can help the car industry in Vietnam crate more car which can help the citizens reduce the number of possible accidents that happen suddenly. Project aim Scope - Bringing the safety for people when - Applied as a functional part of a smart driving in the road. vehicle. - Creating an IoT that help people reduce - Technologies: IoT Sensor, C language. accidents. - Applicable to reduce unexpected accidents - Contributing the development of smart from road users. cars. Risk and issue Deliverables IAO can consume a lot of energy Apply IoT into the system IAO may does not work well on rough Generate consolidated project status report roads Constraints Finacial Limit budget for implement project. $100 Working between team members is difficult. Project team : Wibu team Project manager Nguyen Le Quynh [email protected] Tien System researcher Hua Kien Phuc Gmail [email protected] System designer Pham Hoang Vy Vy [email protected] Developer Bui Vu Giang Son [email protected] Communication Strategy - Team leader report to the project manager every week. - Update progress to team leader every day. Sign off Name Signature Date (MM/DD/YYYY) Executive Sponsor Department Sponsor Project Manager Nguyen Le Quynh Tien Tien Project start date

Functions of system To clear our IAO, we will show you a table of function below which describe each function that we insert in IAO: Function Description

15 | P a g e

Auto operation When user operate IAO, it will automatic drive itself. This function is similarly with auto car driving. Avoid obstacle When IAO meet an barrier, it will stop and find another way then continue to drive on its ways. Proximity sensor Find another way to go when there is an obstacle in it road.

3. Planning (M4) 3.1 WBS

3.2.What is WBS ( Work Breakdown Structure ) Breaking work into smaller tasks is a common productivity technique used to make the work more manageable and approachable. For projects, the Work Breakdown Structure (WBS) is the tool that utilizes this technique and is one of the most important project management documents. It singlehandedly integrates scope, cost and schedule baselines ensuring that project plans are in alignment. The Project Management Institute (PMI) Project Management Book of Knowledge (PMBOK) defines the Work Breakdown Structure as a “deliverable oriented hierarchical decomposition of the work to be executed by the project team.” There are two types of WBS: 1) Deliverable-Based and 2) Phase-Based. The most common and preferred approach

16 | P a g e

is the Deliverable-Based approach. The main difference between the two approaches are the Elements identified in the first Level of the WBS. Deliverable-Based Work Breakdown Structure A Deliverable-Based Work Breakdown Structure clearly demonstrates the relationship between the project deliverables

the Level 1 Elements are summary deliverable descriptions. The Level 2 Elements in each Leg of the WBS are all the unique deliverables required to create the respective Level 1 deliverable. Phase-Based Work Breakdown Structure a Phase-Based WBS, the Level 1 has five Elements. Each of these Elements are typical phases of a project. The Level 2 Elements are the unique deliverables in each phase. Regardless of the type of WBS, the lower Level Elements are all deliverables. Notice that Elements in different Legs have the same name. A Phase-Based WBS requires work associated with multiple elements be divided into the work unique to each Level 1 Element. A WBS Dictionary is created to describe the work in each Element.

17 | P a g e

1.2 Schedule Project plan Researchin g Sketching ideas Design project charter, WBS and schedule IoT design drawings Coding (Tinkercad) Assemble Testing Finishing products Report

Start date 22nd , March 2021 26th, March 2021

End date 25th , March 2021

Executor Hua Kien Phuc

Status Done

29th, March 2021

Done

30th, March2021

31th, March 2021

Hua Kien Phuc Bui Vu Giang Son Pham Hoang Vy Vy Nguyen Le Quynh Tien

1st, April 2021

2nd , April 2021

Nguyen Le Quynh Tien

Done

3rd , April 2021

5th , April 2021

Bui Vu Giang Son

Done

6th, April 2021 10th, April 2021 15th, April 2021

9th, April 2021 14th, April 2021 16th, April 2021

Bui Vu Giang Son Pham Hoang Vy Vy

Done Done Done

16th, April 2021

17th, April 2021

Nguyen Le Quynh Tien

Done

Done

4. Preparing equipments, hardwares, tools (M3) 1 x Mica four-wheel chassis 4 x Wheels 4 x Geared motor

18 | P a g e

1 x Battery box 4 x 18650 IRN batteries 1 x Switch 1 x L298N Motor Control Circuit 1 x Arduino Uno R3 Module 1 x 9g Servo Tower Pro Servo Motor 1 x SRF05 ultrasonic sensor module 4. Feedback (D2)

19 | P a g e

5. References

20 | P a g e

• •

•

•

•

•

•

•

•

•

•

•

Postscapes. 2021. Internet of Things (IoT) History | Postscapes. [online] Available at: [Accessed 2 April 2021]. DataFlair. 2021. IoT Applications | Top 10 Uses of Internet of Things - DataFlair. [online] Available at: [Accessed 2 April 2021]. OpenMind. 2021. Ten Trends of Internet of Things in 2020 | OpenMind. [online] Available at: [Accessed 2 April 2021]. UbuntuPIT. 2021. Top 20 Emerging IoT Trends That Will Shape Your Future Soon. [online] Available at: [Accessed 2 April 2021]. Appinventiv. 2021. Top 18 IoT Trends That Every Entrepreneur Must Know in 2021. [online] Available at: [Accessed 2 April 2021]. GeeksforGeeks. 2021. Architecture of Internet of Things (IoT) - GeeksforGeeks. [online] Available at: [Accessed 2 April 2021]. S. Abdulsalam, D. Lakomski, Q. Gu, T. Jin, and Z. Zong. 2014. Program energy efficiency: The impact of language, compiler and implementation choices. In Proceedings of the 2014 International Green Computing Conference (IGCC’14). 1--6. K. Aggarwal, A. Hindle, and E. Stroulia. 2015. GreenAdvisor: A tool for analyzing the impact of software evolution on energy consumption. In Proceedings of the 2015 IEEE International Conference on Software Maintenance and Evolution (ICSME’15). 311--320. G. Agosta, M. Bessi, E. Capra, and C. Francalanci. 2011. Dynamic memoization for energy efficiency in financial applications. In Proceedings of the 2011 International Green Computing Conference and Workshops. 1--8. Anys Bacha and Radu Teodorescu. 2013. Dynamic reduction of voltage margins by leveraging on-chip ECC in itanium II processors. In Proceedings of the 40th Annual International Symposium on Computer Architecture (ISCA’13). ACM, New York, NY, 297--307. Anys Bacha and Radu Teodorescu. 2014. Using ECC feedback to guide voltage speculation in low-voltage processors. In Proceedings of the 47th Annual IEEE/ACM International Symposium on Microarchitecture (MICRO-47). IEEE Computer Society, Los Alamitos, CA, 306--318. Woongki Baek and Trishul M. Chilimbi. 2010. Green: A framework for supporting energy-conscious programming using controlled approximation. In Proceedings of

21 | P a g e

the 31st ACM SIGPLAN Conference on Programming Language Design and Implementation (PLDI’10). ACM, New York, NY, 198--209.

22 | P a g e