Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Architecting the Industrial Internet

You're reading from   Architecting the Industrial Internet The architect's guide to designing Industrial Internet solutions

Arrow left icon
Product type Paperback
Published in Sep 2017
Publisher Packt
ISBN-13 9781787282759
Length 360 pages
Edition 1st Edition
Arrow right icon
Authors (3):
Arrow left icon
Robert Stackowiak Robert Stackowiak
Author Profile Icon Robert Stackowiak
Robert Stackowiak
Shyam Varan Nath Shyam Varan Nath
Author Profile Icon Shyam Varan Nath
Shyam Varan Nath
Carla Romano Carla Romano
Author Profile Icon Carla Romano
Carla Romano
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. The Industrial Internet Revolution FREE CHAPTER 2. Architectural Approaches for Success 3. Gathering Business Requirements 4. Mapping Requirements to a Functional Viewpoint 5. Assessing Industrial Internet Applications 6. Defining the Data and Analytics Architecture 7. Defining a Deployment Architecture 8. Securing the Industrial Internet 9. Governance and Assuring Compliance 10. Industrial Internet Use Cases in Various Industries 11. A Vision of the Future 12. Sources

Use cases versus case studies

Often, use cases and case studies are interchangeably used to describe how users interact with the system to achieve a specific business outcome. This is an incorrect use of these terms.

What is a use case?

A use case describes a scenario where a specific problem can be solved by a combination of products and services to reach a defined goal. Use cases often explain exactly how a solution is applied to obtain the desired outcome.

In an emerging area, a use case can help one understand and visualize how technology and related solutions can be applied to solve real-world problems. Technical descriptions, including features and functions, are often too abstract and do not explain how the technology is useful. Too often, technical architects and developers tend to gravitate toward the technology because they think it would be intellectually fun to use...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image