Abstract

Large-scale control software systems are generally complex to describe, construct, manage, understand, and maintain. This paper approaches to reducing this complexity separate software structural and behavioral descriptions. Much research about control software systems continues on software structures and their patterns, characterizations, and classifications. Currently, research on the behavioral aspect of control software systems includes using formal notations for specifying software behaviors. Large formal specifications, however, can be difficult to create and to understand; more research is needed into methods for assisting software requirements engineers in reducing these difficulties. This paper uses the idea of a software behavioral view. We believe that a fully developed methodology based on views would significantly reduce the complexity of creating and understanding software requirements. This paper deals with the use of view formalism, a state chart based formalism, to specify of control logic for a telephone set system. Keywords: Formal method; requirement specification; control system software; behavioral views and statecharts;

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.