Difference between revisions of "User:Shawndouglas/sandbox/sublevel1"

From LIMSWiki
Jump to navigationJump to search
 
(60 intermediate revisions by the same user not shown)
Line 1: Line 1:
Cloud computing has its strongest origins in the "web services" phase of internet development. In November 2000, Mind Electric CEO and [[distributed computing]] visionary Graham Glass, writing for IBM, described web services as "building blocks for creating open distributed systems" that "allow companies and individuals to quickly and cheaply make their digital assets available worldwide," while prognosticating that web services "will catalyze a shift from client-server to peer-to-peer architectures."<ref name="GlassTheWeb00">{{cite web |url=http://www-106.ibm.com/developerworks/library/ws-peer1.html |archiveurl=https://web.archive.org/web/20010424015036/http://www-106.ibm.com/developerworks/library/ws-peer1.html |title=The Web services (r)evolution, Part 1: Applying Web services to applications |author=Glass, G. |work=IBM developerWorks |publisher=IBM |date=November 2000 |archivedate=24 April 2001 |accessdate=21 August 2021}}</ref> At that point, the likes of Microsoft and IBM were already developing toolkits for creating and deploying web services<ref name="GlassTheWeb00" />, with IBM releasing an initial high-level report in May 2001 on IBM's web services architecture approach. In that paper, web services were described by its author Heather Kreger as allowing "companies to reduce the cost of doing e-business, to deploy solutions faster, and to open up new opportunities," while also allowing "applications to be integrated more rapidly, easily, and less expensively than ever before."<ref name="KregerWeb01">{{cite web |url=https://www.researchgate.net/profile/Heather-Kreger/publication/235720479_Web_Services_Conceptual_Architecture_WSCA_10/links/563a67e008ae337ef2984607/Web-Services-Conceptual-Architecture-WSCA-10.pdf |format=PDF |title=Web Services Conceptual Architecture (WSCA 1.0) |author=Kreger, H. |date=May 2001 |publisher=IBM Software Group |accessdate=21 August 2021}}</ref>
{{Saved book
|title=Introduction to Quality and Quality Management Systems
|subtitle=
|cover-image=Time-Quality-Money.png
|cover-color=#fffccc
| setting-papersize = A4
| setting-showtoc = 1
| setting-columns = 1
}}


Here's a recap of thinking on web services at the turn of the century:
==''Introduction to Quality and Quality Management Systems''==
{{ombox
| type      = content
| style    = width: 500px;
| text      = This book should not be considered complete until this message box has been removed. This is a work in progress.
}}
The goal of this short volume is to act as an introduction to the quality management system. It collects several articles related to quality, quality management, and associated systems.


* "[act as] building blocks for creating open distributed systems"<ref name="GlassTheWeb00" />
;1. What is quality?
* "quickly and cheaply make ... digital assets available worldwide"<ref name="GlassTheWeb00" />
:''Key terms''
* "catalyze a shift from client-server to peer-to-peer architectures"<ref name="GlassTheWeb00" />
:[[Quality (business)|Quality]]
* "reduce the cost of doing e-business, to deploy solutions faster, and to open up new opportunities"<ref name="KregerWeb01" />
:[[Quality assurance]]
* "[allow] applications to be integrated more rapidly, easily, and less expensively than ever before"<ref name="KregerWeb01" />
:[[Quality control]]
:''The rest''
:[[Data quality]]
:[[Information quality]]
:[[Nonconformity (quality)|Nonconformity]]
:[[Service quality]]
;2. Processes and improvement
:[[Business process]]
:[[Process capability]]
:[[Risk management]]
:[[Workflow]]
;3. Mechanisms for quality
:[[Acceptance testing]]
:[[Conformance testing]]
:[[Clinical quality management system]]
:[[Continual improvement process]]
:[[Corrective and preventive action]]
:[[Good manufacturing practice]]
:[[Malcolm Baldrige National Quality Improvement Act of 1987]]
:[[Quality management]]
:[[Quality management system]]
:[[Total quality management]]
;4. Quality standards
:[[ISO 9000]]
:[[ISO 13485]]
:[[ISO 14000|ISO 14001]]
:[[ISO 15189]]
:[[ISO/IEC 17025]]
:[[ISO/TS 16949]]
;5. Quality in software
:[[Software quality]]
:[[Software quality assurance]]
:[[Software quality management]]


We'll come back to that. For the next stop, however, we have to consider the case of Amazon and how they viewed web services at that time. Leading up to the twenty-first century, Amazon was beginning to expand beyond its book selling roots, opening up its marketplace to other third parties (affiliates) to sell their own goods on Amazon's platform. That effort required an expansion of IT infrastructure to support web-scale third-party selling, but as it turned out, a lot of that IT infrastructure, while reliable and cost-effective, had been previously added piecemeal, with many components getting "tangled" along the way. Amazon project leads and external partners were clamoring for better infrastructure services. This required untangling the IT and associated provider data into an internally scalable, centralized infrastructure that allowed for smoother communication and [[Information management|data management]] using well-documented APIs.<ref name="FurrierExclusive15">{{cite web |url=https://medium.com/@furrier/original-content-the-story-of-aws-and-andy-jassys-trillion-dollar-baby-4e8a35fd7ed |title=Exclusive: The Story of AWS and Andy Jassy’s Trillion Dollar Baby |author=Furrier, J. |work=Medium.com |date=29 January 2015 |accessdate=21 August 2021}}</ref><ref name="MillerHowAWS16">{{cite web |url=https://techcrunch.com/2016/07/02/andy-jassys-brief-history-of-the-genesis-of-aws/ |title=How AWS came to be |author=Miller, R. |work=TechCrunch |date=02 July 2016 |accessdate=21 August 2021}}</ref> By 2003, the company was indirectly acting as a services industry to its partners. "Why not act upon this strength?" was the sentiment that quickly developed that year, with Amazon choosing to use its internal compute, storage, and database infrastructure and related expertise to its advantage.<ref name="MillerHowAWS16" />
<!--Place all category tags here-->
 
At that point, the paradigm of web services expanded to include infrastructure as a service or IaaS, with compute, storage, and database services running over the internet for web developers to utilize.<ref name="FurrierExclusive15" /><ref name="MillerHowAWS16" /> "If you believe developers will build applications from scratch using web services as primitive building blocks, then the operating system becomes the internet,” noted AWS CEO Andy Jassy in a 2015 retrospective interview.<ref name="FurrierExclusive15" /> From that concept evolved the idea of determining what it would take to allow any entity to run their technology applications over their web-service-based IaaS platform. In August 2006, Amazon introduced its Amazon Elastic Compute Cloud (Amazon EC2), "a web service that provides resizable compute capacity in the cloud."<ref name="AWSAnnounc06">{{cite web |url=https://aws.amazon.com/about-aws/whats-new/2006/08/24/announcing-amazon-elastic-compute-cloud-amazon-ec2---beta/ |title=Announcing Amazon Elastic Compute Cloud (Amazon EC2) - beta |publisher=Amazon Web Services |date=24 August 2006 |accessdate=21 August 2021}}</ref><ref name="ButlerAmazon06">{{cite journal |title=Amazon puts network power online |journal=Nature |author=Butler, D. |volume=444 |issue=528 |year=2006 |doi=10.1038/444528a}}</ref> This quickly prompted others in academic and scientific fields to continue the conversation of turning IT and its infrastructure into a service.<ref name="ButlerAmazon06" /><ref name="KeITeS06">{{cite journal |title=ITeS - Transcending the Traditional Service Model |journal=Proceedings of the 2006 IEEE International Conference on e-Business Engineering |author=Ke, J.-s. |page=2 |year=2006 |doi=10.1109/ICEBE.2006.66}}</ref> In turn, conversations changed, discussing the opportunities inherent to "cloud computing," including Google and IBM partnering to virtualize computers on new data centers for boosting academic research and teaching new computer science students<ref name="LohrGoogle07">{{cite web |url=http://www.nytimes.com/2007/10/08/technology/08cloud.html?_r=1&or |archiveurl=http://www.csun.edu/pubrels/clips/Oct07/10-08-07E.pdf |format=PDF |title=Google and I.B.M. Join in 'Cloud Computing' Research |author=Lohr, S. |work=The New York Times |date=08 October 2007 |archivedate=08 October 2007 |accessdate=21 August 2021}}</ref><ref name="HandHead07">{{cite journal |title=Head in the clouds |journal=Nature |author=Hand, E. |volume=449 |issue=963 |year=2007 |doi=10.1038/449963a}}</ref>, IBM releasing a white paper on cloud computing<ref name="BossCloud07">{{cite web |url=http://download.boulder.ibm.com/ibmdl/pub/software/dw/wes/hipods/Cloud_computing_wp_final_8Oct.pdf |archiveurl=https://web.archive.org/web/20090206015244/http://download.boulder.ibm.com/ibmdl/pub/software/dw/wes/hipods/Cloud_computing_wp_final_8Oct.pdf |format=PDF |title=Cloud Computing |author=Boss, G.; Malladi, P.; Quan, D. et al. |publisher=IBM Corporation |date=08 October 2007 |archivedate=06 February 2009 |accessdate=21 August 2021}}</ref> and announcing its Blue Cloud initiative<ref name="LohrIBM07">{{cite web |url=https://www.nytimes.com/2007/11/15/technology/15blue.html |title=I.B.M. to Push 'Cloud Computing,' Using Data From Afar |author=Lohr, S. |work=The New York Times |date=15 November 2007 |accessdate=21 August 2021}}</ref>, and Google doubling down on its cloud-based software offerings in competition with Microsoft.<ref name="LohrGoogleGets07">{{cite web |url=https://www.nytimes.com/2007/12/16/technology/16goog.html |archiveurl=https://signallake.com/innovation/GoogleMicrosoft121607.pdf |format=PDF |title=Google Gets Ready to Rumble With Microsoft |author=Lohr, S.; Helft, M. |work=The New York Times |date=16 December 2007 |archivedate=16 December 2007 |accessdate=21 August 2021}}</ref>
 
In IBM's 2007 white paper, they described cloud computing as a "pool of virtualized computer resources" that can<ref name="BossCloud07" />:
 
*  "host a variety of different workloads, including batch-style back-end jobs and interactive, user-facing applications";
*  "allow workloads to be deployed and scaled-out quickly through the rapid provisioning of virtual machines or physical machines";
*  "support redundant, self-recovering, highly scalable programming models that allow workloads to recover from many unavoidable hardware/software failures";
*  "monitor resource use in real time to enable rebalancing of allocations when needed"; and
*  "be a cost efficient model for delivering information services, reducing IT management complexity, promoting innovation, and increasing responsiveness through real-time workload balancing."
 
In 2011, the National Institute of Standards and Technology (NIST) came up with a more standards-based definition to cloud computing. They described it as "a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction."<ref name="MellTheNIST11">{{cite web |url=https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-145.pdf |format=PDF |title=The NIST Definition of Cloud Computing |author=Mell, P.; Grance, T. |publisher=NIST |date=September 2011 |accessdate=21 August 2021}}</ref> They went on to highlight the five essential characteristics further<ref name="MellTheNIST11" />:
 
* On-demand self-service: The unilateral provision of computing resources should be an automatic or nearly automatic process.
* Broad network access: Thin- or thick-client platforms, both hardwired and mobile, should allow for standardized, networkable access to those computing resources.
* Resource pooling: A multi-tenant model requires the provisioning of resources to serve a wide customer base, with a layer of abstraction that gives the user a sense of location independence from those resources.
* Rapid elasticity: The platform's resources should be readily and/or automatically scalable commensurate with demand, such that the user sees no negative impact in their activities.
* Measured service: The resources should be automatically controlled and optimized by a measured service or metering system, transparently providing accurate and timely information about resource usage.
 
When we compare these 2007 and 2011 definitions of cloud computing with the comments on web services by Glass and Kreger at the turn of the century (as well as our own derived definition prior), we can't help but see how the early vision for cloud computing has taken shape today. First, web services can indeed be paired with other technologies to form a distributed system, in this case a centralized and scalable computing infrastructure that can be used by practically anyone to run software, develop applications, and "host a variety of different workloads."<ref name="BossCloud07" /> Second, those workloads can be quickly deployed worldwide, wherever there is internet access, and typically at a fair price, when compared to the costs of on-premises data management.<ref name="ViolinoWhere20">{{cite web |url=https://www.infoworld.com/article/3532288/where-to-look-for-cost-savings-in-the-cloud.html |title=Where to look for cost savings in the cloud |author=Violino, B. |work=InfoWorld |date=16 March 2020 |accessdate=21 August 2021}}</ref> Third, new opportunities are indeed developing for organizations seeking to tap into the on-demand, rapid, scalable, and cost-efficient nature of cloud computing.<ref name="OjalaDiscover16">{{cite journal |title=Discovering and creating business opportunities for cloud services |journal=Journal of Systems and Software |author=Ojala, A. |volume=113 |pages=408–17 |year=2016 |doi=10.1016/j.jss.2015.11.004}}</ref><ref name="PetteyCloud20">{{cite web |url=https://www.gartner.com/smarterwithgartner/cloud-shift-impacts-all-it-markets/ |title=Cloud Shift Impacts All IT Markets |author=Pettey, C. |work=Smarter with Gartner |date=26 October 2020 |accessdate=21 August 2021}}</ref> And finally, benefits are being seen in the integration of applications via the cloud, particularly as more options for multicloud and hybrid cloud integration develop.<ref name="PetteyFiveApp19">{{cite web |url=https://www.gartner.com/smarterwithgartner/5-approaches-cloud-applications-integration/ |title=5 Approaches to Cloud Applications Integration |author=Pettey, C. |work=Smarter with Gartner |date=14 May 2019 |accessdate=21 August 2021}}</ref> The early vision that perhaps hasn't been realized is found in Glass' "shift from client-server to peer-to-peer architectures," though discussions about the promise of peer-to-peer cloud computing have occurred since.<ref name="BabaogluEscape14">{{cite journal |title=The People's Cloud |journal=IEEE Spectrum |author=Babaoglu, O.; Marzolla, M. |volume=51 |issue=10 |pages=50–55 |year=2014 |doi=10.1109/MSPEC.2014.6905491 |url=https://spectrum.ieee.org/computing/networks/escape-from-the-data-center-the-promise-of-peertopeer-cloud-computing}}</ref>
 
Though clearly linked to web services and the early vision of cloud computing in the 2000s, the cloud computing of the 2020s is a remarkably more advanced and continually evolving technology. However, it's still not without its challenges today. The data security, privacy, and governance of computing in general, and cloud computing in particular, will continue to require more rigorous approaches, as will reducing remaining data silos in organizations with pivots to hybrid cloud, multicloud, and serverless cloud implementations.<ref name="Goodison10Fut20">{{cite web |url=https://www.crn.com/news/cloud/10-future-cloud-computing-trends-to-watch-in-2021 |title=10 Future Cloud Computing Trends To Watch In 2021 |author=Goodison, D. |work=CRN |date=20 November 2020 |accessdate=21 August 2021}}</ref><ref name="DTCCCloud20">{{cite web |url=http://www.dtcc.com/-/media/Files/Downloads/WhitePapers/DTCC-Cloud-Journey-WP |format=PDF |title=Cloud Technology: Powerful and Evolving |author=DTCC |date=November 2020 |accessdate=21 August 2021}}</ref> But what is "hybrid cloud"? "Serverless cloud?" The next section goes into further detail.
 
==References==
{{Reflist|colwidth=30em}}

Latest revision as of 19:46, 9 February 2022

Introduction to Quality and Quality Management Systems
Time-Quality-Money.png
This user book is a user-generated collection of LIMSWiki articles that can be easily saved, rendered electronically, and ordered as a printed book.
If you are the creator of this book and need help, see Help:Books.

Edit this book: Book Creator · Wikitext
Select format to download:

PDF (A4) · PDF (Letter)

Order a printed copy from these publishers: PediaPress
Start ] [ FAQ ] [ Basic help ] [ Advanced help ] [ Feedback ] [ Recent Changes ]


Introduction to Quality and Quality Management Systems

The goal of this short volume is to act as an introduction to the quality management system. It collects several articles related to quality, quality management, and associated systems.

1. What is quality?
Key terms
Quality
Quality assurance
Quality control
The rest
Data quality
Information quality
Nonconformity
Service quality
2. Processes and improvement
Business process
Process capability
Risk management
Workflow
3. Mechanisms for quality
Acceptance testing
Conformance testing
Clinical quality management system
Continual improvement process
Corrective and preventive action
Good manufacturing practice
Malcolm Baldrige National Quality Improvement Act of 1987
Quality management
Quality management system
Total quality management
4. Quality standards
ISO 9000
ISO 13485
ISO 14001
ISO 15189
ISO/IEC 17025
ISO/TS 16949
5. Quality in software
Software quality
Software quality assurance
Software quality management