“Formal Language Specification” Please respond to the following:
- Examine the syntax and semantics of Linear Temporal Logic (LTL) closely. Determine whether you find it easier or harder to read and understand than other formal modeling languages. Provide a rationale.
- Differentiate between instance variables and state variables and provide examples of each. Determine which of the two types of variables could adversely impact a design if used improperly in a system and explain why.
Classmate:
Examine the syntax and semantics of Linear Temporal Logic (LTL) closely. Determine whether you find it easier or harder to read and understand than other formal modeling languages. Provide a rationale.
Linear temporal logic (LTL) is neither hard nor easy to understand than other modeling languages. However, it needs to be explained better. When provided with a key list of the symbols within the LTL model and an explanation of how each symbol is being used, I can understand how the syntax is used but not enough to the point where I can efficiently use it to build models on my own.
Differentiate between instance variables and state variables and provide examples of each. Determine which of the two types of variables could adversely impact a design if used improperly in a system and explain why.
Instance variables are variables that are specific to a specific object. State variables have values that control the specific state of an object (Lamsweerde, 2009). Examples of an object instance variables might be: name and age. Examples of state variables might be: thermostat on and check engine light on. State variables are the ones that could adversely impact a design if improperly used because it could change the way the system behaves to something that is not desirable nor safe. For example, if a “thermostat on” state variable was improperly used, it could, for all possible states, cause the temperature to become dangerously cold when ever the ambient temperature in the room reached a threshold triggering the air conditioner to turn on.
References
Lamsweerde, A. V. (2009). Requirements Engineering: From System Goals to UML Models to Software Specifications. Chichester, West Sussex, England: John Wiley & Sons, Ltd. Retrieved May 28, 2018, from https://strayer.vitalsource.com/#/books/978EUDTE00270/