Ensuring Robustness and Reliability of Object Oriented Software Using MASCOT 3
This paper presents the use of MASCOT 3 as a design tool for the production of robust and reliable Object Oriented software.
Object-Oriented design for software systems is a fast growing area of research and development, although currently there is no methodology to ensure the robustness and reliability of the software produced.
The MASCOT 3 design methodology, designed for use in the development of real-time systems by Ken Jackson et al., may prove to be an ideal way of developing OO software.
The paper describes the use of MASCOT 3 for the design of an Object-Oriented software system and discusses the resulting strengths of the design provided by the MASCOT 3 methodology.
MASCOT 3 provides: a formalism, which is machine and language independent, for the expression of the system in terms of system/sub-system network diagrams and text; a methodology for the design, implementation, testing, documentation and maintenance of the software; and a kernel which provides run-time executive control for synchronisation and scheduling of real-time processing, and which can be utilised to control the parallel processing of operations on Objects.
Further, the formalism supports the design of Objects using MASCOT 3’ s basic design entities; it provides a natural way of expressing classes and hierarchical relationships between objects; the MASCOT 3 design template automatically aids the reuse of software objects; MASCOT 3’s Access Interface can be used to represent and ensure legal messages between objects; and the formalism supports the information hiding and abstract data typing associated with OO design.
KeywordsMutual Exclusion Access Procedure Network Diagram Multiple Inheritance Access Interface
Unable to display preview. Download preview PDF.
- 2.Bloor, R., Object-Orientation has the edge over leading languages, DECUSER pp. 55–56 October 1989.Google Scholar
- 3.Kim, W., Architectural Issues in Object-Oriented Databases, Journal of Object-Oriented Programming, Vol. 2, No.6, March/April 1990.Google Scholar
- 4.Object-Oriented Programming for Artificial Intelligence-A Guide to Tools and System Design, Chapter 1, Object Oriented Programming Defined pp. 3–13, Addison-Wesley 1989.Google Scholar
- 5.Sommerville, I., Software Engineering 3rd Edition, Chapter 11, Object-Oriented Design pp. 203–231, Addison-Wesley, 1989.Google Scholar
- 6.Pressman, R.S., Software Engineering A Practitioners Approach, Chapter 9 McGraw-Hill Int., 1988.Google Scholar
- 7.Booch, G., Object Oriented Development, IEEE Transactions on Software Engineering, February 1986.Google Scholar
- 8.Booch, G., Software Components with Ada Structures, Tools and Subsystems, Chapter 2, pp. 10–32, Benjamin Cummins, 1987.Google Scholar
- 10.Jackson, K., MASCOT 3 and its relationship to other Methods and Ada.Google Scholar
- 12.Jackson, K., MASCOT.Google Scholar
- 14.Controlled Requirements Specification (CORE), Seminar Manual, Mullery, G.Google Scholar
- 15.HOOD Manual Issue 2.2 Revised by Robinson, P.J., Software Engineer ing Section, European SpaceAgency.Google Scholar