Abstract
Views are vehicles for separation of concerns. They allow developer to address only those concerns or criteria that are of interest, ignoring others that are unrelated. For complex real-time systems, there are usually multiple parties involved in system development, which are concerned with different views of a system. This paper discusses a single design methodology that covers all phases of the life cycle, ensuring that specific real-time system requirements of the software will be met. This methodology emphasize the identification of different views on the system under construction. Each of these views can be constructed using common notations and techniques, including structured notations as well as formal specification. The proposed methodology is illustrated by specifying a heater system.
Sign-in/Register to access full text options 
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 callDisclaimer: 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.
