Control logic: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
m →‎top: change |id={{citeseer}} to |citeseerx= using AWB
Citation bot (talk | contribs)
Alter: template type. Add: isbn, doi, volume, series. Upgrade ISBN10 to ISBN13. | Use this bot. Report bugs. | Suggested by AManWithNoPlan | #UCB_webform 293/1972
Line 1: Line 1:
'''Control logic''' is a key part of a software [[computer program|program]] that controls the operations of the program. The control logic responds to commands from the user, and it also acts on its own to perform automated tasks that have been structured into the program.<ref>{{cite web|last=Smith|first=S.E.|title=What Is Control Logic?|url=http://www.wisegeek.com/what-is-control-logic.htm}}</ref>
'''Control logic''' is a key part of a software [[computer program|program]] that controls the operations of the program. The control logic responds to commands from the user, and it also acts on its own to perform automated tasks that have been structured into the program.<ref>{{cite web|last=Smith|first=S.E.|title=What Is Control Logic?|url=http://www.wisegeek.com/what-is-control-logic.htm}}</ref>


[[File:Stopwatch chart.png|thumb|250px|right|Model of a simple stopwatch<ref>{{cite journal | url = http://www.csl.sri.com/~rushby/papers/fase04.ps.gz | last1 = Hamon | first1 = G. | last2 = Rushby | first2 = J. | year = 2004 | title = An Operational Semantics for Stateflow | journal = Fundamental Approaches to Software Engineering (FASE) | pages = 229–243 | location = Barcelona, Spain | publisher = Springer-Verlag }}</ref>]]
[[File:Stopwatch chart.png|thumb|250px|right|Model of a simple stopwatch<ref>{{cite journal | url = http://www.csl.sri.com/~rushby/papers/fase04.ps.gz | last1 = Hamon | first1 = G. | last2 = Rushby | first2 = J. | year = 2004 | title = An Operational Semantics for Stateflow | journal = Fundamental Approaches to Software Engineering (FASE) | series = Lecture Notes in Computer Science | volume = 2984 | pages = 229–243 | location = Barcelona, Spain | publisher = Springer-Verlag | doi = 10.1007/978-3-540-24721-0_17 | isbn = 978-3-540-21305-5 }}</ref>]]


Control logic can be modeled using a [[state diagram]],<ref>{{cite paper | url = http://www.csl.sri.com/users/tiwari/papers/stateflow.pdf | last = Tiwari | first = A. | year = 2002 | title = Formal Semantics and Analysis Methods for Simulink Stateflow Models }}</ref> which is a form of hierarchical [[state machine]]. These state diagrams can also be combined with [[flow charts]] to provide a set of [[computational semantics]] for describing complex control logic.<ref>{{cite conference | last = Hamon | first = G. | year = 2005 | title = A Denotational Semantics for Stateflow | conference = International Conference on Embedded Software | pages = 164–172 | location = Jersey City, NJ | publisher = ACM | citeseerx = 10.1.1.89.8817 }}</ref> This mix of state diagrams and [[flow charts]] is illustrated in the figure on the right, which shows the control logic for a simple stopwatch. The control logic takes in commands from the user, as represented by the event named “START”, but also has automatic recurring sample time events, as represented by the event named “TIC”.
Control logic can be modeled using a [[state diagram]],<ref>{{cite web | url = http://www.csl.sri.com/users/tiwari/papers/stateflow.pdf | last = Tiwari | first = A. | year = 2002 | title = Formal Semantics and Analysis Methods for Simulink Stateflow Models }}</ref> which is a form of hierarchical [[state machine]]. These state diagrams can also be combined with [[flow charts]] to provide a set of [[computational semantics]] for describing complex control logic.<ref>{{cite conference | last = Hamon | first = G. | year = 2005 | title = A Denotational Semantics for Stateflow | conference = International Conference on Embedded Software | pages = 164–172 | location = Jersey City, NJ | publisher = ACM | citeseerx = 10.1.1.89.8817 }}</ref> This mix of state diagrams and [[flow charts]] is illustrated in the figure on the right, which shows the control logic for a simple stopwatch. The control logic takes in commands from the user, as represented by the event named “START”, but also has automatic recurring sample time events, as represented by the event named “TIC”.


==References==
==References==

Revision as of 20:43, 26 January 2022

Control logic is a key part of a software program that controls the operations of the program. The control logic responds to commands from the user, and it also acts on its own to perform automated tasks that have been structured into the program.[1]

File:Stopwatch chart.png
Model of a simple stopwatch[2]

Control logic can be modeled using a state diagram,[3] which is a form of hierarchical state machine. These state diagrams can also be combined with flow charts to provide a set of computational semantics for describing complex control logic.[4] This mix of state diagrams and flow charts is illustrated in the figure on the right, which shows the control logic for a simple stopwatch. The control logic takes in commands from the user, as represented by the event named “START”, but also has automatic recurring sample time events, as represented by the event named “TIC”.

References

  1. ^ Smith, S.E. "What Is Control Logic?".
  2. ^ Hamon, G.; Rushby, J. (2004). "An Operational Semantics for Stateflow". Fundamental Approaches to Software Engineering (FASE). Lecture Notes in Computer Science. 2984. Barcelona, Spain: Springer-Verlag: 229–243. doi:10.1007/978-3-540-24721-0_17. ISBN 978-3-540-21305-5.
  3. ^ Tiwari, A. (2002). "Formal Semantics and Analysis Methods for Simulink Stateflow Models" (PDF).
  4. ^ Hamon, G. (2005). A Denotational Semantics for Stateflow. International Conference on Embedded Software. Jersey City, NJ: ACM. pp. 164–172. CiteSeerX 10.1.1.89.8817.