This HTML5 document contains 74 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
dctermshttp://purl.org/dc/terms/
n18http://dbpedia.org/resource/Wikipedia:
dbohttp://dbpedia.org/ontology/
n6http://dbpedia.org/resource/File:
foafhttp://xmlns.com/foaf/0.1/
n12https://global.dbpedia.org/id/
dbthttp://dbpedia.org/resource/Template:
rdfshttp://www.w3.org/2000/01/rdf-schema#
freebasehttp://rdf.freebase.com/ns/
n16http://
n4http://commons.wikimedia.org/wiki/Special:FilePath/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
wikipedia-enhttp://en.wikipedia.org/wiki/
provhttp://www.w3.org/ns/prov#
dbphttp://dbpedia.org/property/
dbchttp://dbpedia.org/resource/Category:
xsdhhttp://www.w3.org/2001/XMLSchema#
wikidatahttp://www.wikidata.org/entity/
dbrhttp://dbpedia.org/resource/

Statements

Subject Item
dbr:Control–feedback–abort_loop
rdfs:label
Control–feedback–abort loop
rdfs:comment
Too often systems fail, sometimes leading to significant loss of life, fortunes and confidence in the provider of a product or service. It was determined that a simple and useful tool was needed to help in the analysis of interactions of groups and systems to determine possible unexpected consequences. The tool didn’t need to provide every possible outcome of the interactions but needed to provide a means for analysts and product/service development stakeholders to evaluate the potential risks associated with implementing new functionality in a system. They needed a brainstorming tool to help ascertain if a concept was viable from a business perspective. The control–feedback–abort loop and the analysis diagram is one such tool that has helped organizations analyze their system workflows an
foaf:depiction
n4:CFALOOP2_Fig2.jpg n4:CFALOOP3_Fig3.jpg n4:CFALOOP4_Fig4.jpg n4:CFALOOP5_Fig5.jpg n4:CFALOOP1_Fig1.jpg n4:Control_Chart1_Fig9.jpg n4:Control_Chart2_Fig10.jpg n4:Control_Chart3_Fig11.jpg n4:Control_Chart4_Fig12.jpg n4:CFALOOP6_Fig_6.jpg n4:CFALOOP8_Fig7.jpg n4:CFALOOP9_Fig8.jpg
dcterms:subject
dbc:Systems_analysis
dbo:wikiPageID
23565965
dbo:wikiPageRevisionID
795196363
dbo:wikiPageWikiLink
n6:Control_Chart4_Fig12.jpg dbr:Status_quo dbr:Product_Development_and_Management_Association dbr:Wait_state dbr:Data_point dbr:Sampling_rate n6:CFALOOP8_Fig7.jpg dbr:Control_theory n6:CFALOOP9_Fig8.jpg dbr:General_Dynamics n6:CFALOOP1_Fig1.jpg n6:CFALOOP2_Fig2.jpg n6:CFALOOP3_Fig3.jpg n6:CFALOOP4_Fig4.jpg n6:CFALOOP5_Fig5.jpg n6:CFALOOP6_Fig_6.jpg dbr:Stop_sign dbr:Traffic_sign dbr:Control_chart dbr:System_dynamics dbc:Systems_analysis n6:Control_Chart1_Fig9.jpg n6:Control_Chart2_Fig10.jpg dbr:Software_testing dbr:Systems_Thinking n18:MOS dbr:Fortune_500 dbr:Instructional_design n6:Control_Chart3_Fig11.jpg
dbo:wikiPageExternalLink
n16:www.icc.edu n16:www.itmanageag3.com
owl:sameAs
n12:4iRYD freebase:m.06zjw5v wikidata:Q5165956
dbp:wikiPageUsesTemplate
dbt:Multiple_issues dbt:Commons_category dbt:ISBN dbt:Cleanup dbt:Dead_link dbt:Refimprove
dbo:thumbnail
n4:CFALOOP1_Fig1.jpg?width=300
dbp:bot
InternetArchiveBot
dbp:date
August 2017
dbp:fixAttempted
yes
dbo:abstract
Too often systems fail, sometimes leading to significant loss of life, fortunes and confidence in the provider of a product or service. It was determined that a simple and useful tool was needed to help in the analysis of interactions of groups and systems to determine possible unexpected consequences. The tool didn’t need to provide every possible outcome of the interactions but needed to provide a means for analysts and product/service development stakeholders to evaluate the potential risks associated with implementing new functionality in a system. They needed a brainstorming tool to help ascertain if a concept was viable from a business perspective. The control–feedback–abort loop and the analysis diagram is one such tool that has helped organizations analyze their system workflows and workflow exceptions. The concept of the Control–Feedback–Abort (CFA) loop is based upon another concept called the ‘Control – Feedback Loop'. The Control – Feedback Loop has been around for many years and was the key concept in the development of many electronic designs such as Phase-Lock Loops. The core of the CFA loop concept was based on a major need that corporate executives and staff can anticipate the operation of systems, processes, products and services they use and create before they are developed.
prov:wasDerivedFrom
wikipedia-en:Control–feedback–abort_loop?oldid=795196363&ns=0
dbo:wikiPageLength
17876
foaf:isPrimaryTopicOf
wikipedia-en:Control–feedback–abort_loop
Subject Item
dbr:Control_theory
dbo:wikiPageWikiLink
dbr:Control–feedback–abort_loop
Subject Item
dbr:Thermodynamic_equilibrium
dbo:wikiPageWikiLink
dbr:Control–feedback–abort_loop
Subject Item
dbr:CFA_Loop
dbo:wikiPageWikiLink
dbr:Control–feedback–abort_loop
dbo:wikiPageRedirects
dbr:Control–feedback–abort_loop
Subject Item
dbr:Control-Feedback-Abort_Loop
dbo:wikiPageWikiLink
dbr:Control–feedback–abort_loop
dbo:wikiPageRedirects
dbr:Control–feedback–abort_loop
Subject Item
dbr:Control-feedback-abort_loop
dbo:wikiPageWikiLink
dbr:Control–feedback–abort_loop
dbo:wikiPageRedirects
dbr:Control–feedback–abort_loop
Subject Item
wikipedia-en:Control–feedback–abort_loop
foaf:primaryTopic
dbr:Control–feedback–abort_loop