Networking the Cloud for IoT – Pt 3 Cloud Network Systems Engineering

June 17, 2016 / G C Network / Comments Off

Twitter Feed

From PC Break/Fix to CloudMASTER®

By G C Network | August 29, 2016

https://www.linkedin.com/in/stevendonovan It was late 2011 and Steven Donovan was comfortable working at SHI International Corporation, a growing information technology firm, as a personal computer break/fix technician. His company had been…

Is Data Classification a Bridge Too Far?

By G C Network | August 17, 2016

Today data has replaced money as the global currency for trade. “McKinsey estimates that about 75 percent of the value added by data flows on the Internet accrues to “traditional”…

Vendor Neutral Training: Proven Protection Against Cloud Horror Stories

By G C Network | August 10, 2016

Cloud computing is now entering adolescence. With all the early adopters now swimming in the cloud pool with that “I told you so” smug, fast followers are just barely beating…

Cognitive Business: When Cloud and Cognitive Computing Merge

By G C Network | July 21, 2016

Cloud computing has taken over the business world! With almost maniacal focus, single proprietors and Board Directors of the world’s largest conglomerates see this new model as a “must do”.…

Government Cloud Achilles Heel: The Network

By G C Network | July 9, 2016

Cloud computing is rewriting the books on information technology (IT) but inter-cloud networking remains a key operational issue. Layering inherently global cloud services on top of a globally fractured networking…

System Integration Morphs To Cloud Service Integration

By G C Network | June 19, 2016

Cloud Service Brokerage is changing from an industry footnote toward becoming a major system integration play. This role has now become a crucial component of a cloud computing transition because…

Networking the Cloud for IoT – Pt 3 Cloud Network Systems Engineering

By G C Network | June 17, 2016

Dwight Bues & Kevin Jackson (This is Part 3 of a three part series that addresses the need for a systems engineering approach to IoT and cloud network design. Networking the Cloud for IoT –…

Networking the Cloud for IoT – Pt. 2 Stressing the Cloud

By G C Network | June 12, 2016

Dwight Bues & Kevin Jackson This is Part 2 of a three part series that addresses the need for a systems engineering approach to IoT and cloud network design. Part…

Networking the Cloud for IoT – Pt. 1: IoT and the Government

By G C Network | June 7, 2016

Dwight Bues & Kevin Jackson This is Part 1 of a three part series that addresses the need for a systems engineering approach to IoT and cloud network design:…

Parallel Processing and Unstructured Data Transforms Storage

By G C Network | May 31, 2016

(This post originally appeared on Direct2Dell, The Official Dell Corporate Blog) Enterprise storage is trending away from traditional, enterprise managed network-attached storage (NAS) and storage area networks (SAN) towards a…

« Previous
1
…
11
12
13
14
15
…
73
Next »

Dwight Bues & Kevin Jackson

(This is Part 3 of a three part series that addresses the need for a systems engineering approach to IoT and cloud network design. Networking the Cloud for IoT – Pt. 1: IoT and the Government , Networking the Cloud for IoT – Pt. 2 Stressing the Cloud )

The Case For Cloud Network Systems Engineering

IoT networking requirements are vastly different from those supported by today’s cloud network. The processing and transport levels are multiple orders of magnitude higher than ever seen before. More importantly though, societal economic and the safety ramifications of making mistakes during this transition are off the scale. This is why system engineering of the cloud computing network is now an immediate global imperative.

System engineering has many different aspects, but it all starts with the question, “What do I really want to know?” This is the beginning of the CONOPSdocument referenced earlier. This document captures User Needs which are formal statements of what the user wants from the system. This CONOPS leads to Derived Requirements which, through an iterative process, are analyzed against a Target Architecture. Once a project is underway, methods of Integration are planned in order to provide Validation(did we build the right system?) and Verification (did we build the system right?) of the requirements. Further considerations for SE include: how to conduct Peer Reviews of a design (either Systems, Hardware, or Software), studying Defects, and establishing processes to ensure the Qualityof the final product and Compliance with Standards.

While multiple sources indicate that the business world is investing heavily in the IoT, there are no indication that these investments are addressing the question of what does society really want to know in the IoT world. To ensure success, design formality is necessary, lest “IoT” become the latest retired buzzword. Dr. Juran, in Juran on Leadership for Quality, makes the point that quality improvement programs failed because leadership assigned vague goals and responsibilities, while failing to commit resources to staff projects and reward achievements. This caused TQM, 6 Sigma, and the like to be relegated to the “dustbin” of quality programs. Is it wise to relive this error in our transition to IoT?

Ten Steps of Design Rigor

Jay Thomas in the Embedded Magazine article “Software Standards 101: Tracing Code to Requirements,” opined that the embedded industry standard for making systems safe or secure include:

Performing a safety or security assessment;
Determining a target system failure rate;
Using the target system failure rate to determine the appropriate level of development rigor;
Using a formal requirements capture process;
Creating software that adheres to an appropriate coding standard;
Tracing all code back to their source requirements;
Developing all software and system test cases based on requirements;
Tracing test cases to requirements;
Using coverage analysis to test completeness against both requirements and code; and
For certification, collect and collate the process artifacts required to demonstrate that an appropriate level of rigor has been maintained.”

Using this model, security issues must be addressed through a multi-layered approach. From a system engineering point of view, users must be forced to implement complex passwords and Public Key Infrastructure (PKI) certifications must be a minimum requirement for operating across the IoT network. The article, “How to protect Wearable Devices Against Cyberattacks,” in IEEE Roundup online magazine, postulated that, where there are devices with limited functionality, they can be linked to the user’s smartphone, which can act as a conduit for the device’s information, thus securing it from the outside world. Most importantly of all, though, is ensuring that the proper amount of Systems Engineering design rigor has been exercised in the development process. This makes defects easier to find and much less costly than a multimillion-dollar security breach.

Although it would be simply impossible to implement this type of rigor globally across the cloud and its underlying network, embedded systems tenets could be applied to individual IoT projects. Since embedded systems also have a history of low development overhead, minimal memory or storage per unit, and cost-driven development cycles, a more rigorous IoT design process may save society from seeing a collapse of the cloud. In the past, this type of design rigor has paid off in successful, maintainable designs. Let’s therefore use what we’ve learned from the past to avoid a future that none of us want to see.

Dwight Bues, of Engility Corp., is a Georgia Tech Computer Engineer with 30+ years’ experience in computer hardware, software, and systems and interface design. He has worked in Power Generation, Communications, RF, Command/Control, and Test Systems. Dwight is a Certified Scrum Master and teaches courses in Architecture, Requirements, and IVV&T. He is also a certified Boating Safety instructor with the Commonwealth of Virginia and the United States Power Squadrons. He is currently working several STEM projects, sponsoring teams for competitions in the Aerospace Industries Association’s (AIA) Team America Rocketry Challenge (TARC) and the Robotics Education and Competition Foundation’s, Vex Skyrise Robotics Challenge.

Kevin L. Jackson is a globally recognized cloud computing expert, a cloud computing and cybersecurity Thought Leader for Dell and IBM and Founder/Author of the award winning “Cloud Musings” blog. Mr. Jackson has also been recognized as a “Top 100 Cybersecurity Influencer and Brand” by Onalytica (2015), a Huffington Post “Top 100 Cloud Computing Experts on Twitter” (2013), a “Top 50 Cloud Computing Blogger for IT Integrators” by CRN (2015) and a “Top 5 Must Read Cloud Blog” by BMC Software (2015). His first book, “GovCloud: Cloud Computing for the Business of Government” was published by Government Training Inc. and released in March 2011. His next publication, “Practical Cloud Security: A Cross Industry View”, will be released by Taylor & Francis in the spring of 2016

( This content is being syndicated through multiple channels. The opinions expressed are solely those of the author and do not represent the views of GovCloud Network, GovCloud Network Partners or any other corporation or organization.)

↑ Grab this Headline Animator

Follow me at https://Twitter.com/Kevin_Jackson

Posted in Uncategorized