From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: ***
X-Spam-Status: No, score=3.8 required=5.0 tests=BAYES_00,INVALID_MSGID,
	RATWARE_MS_HASH,RATWARE_OUTLOOK_NONAME autolearn=no autolearn_force=no
	version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,61353b948f976da3
X-Google-Attributes: gid103376,public
From: "Paul Van Bellinghen" <pvanbell@mhv.net>
Subject: RTSA vs. OO approach to RTE design
Date: 1997/07/13
Message-ID: <01bc8f26$1daae700$16a9f5cd@asip120>#1/1
X-Deja-AN: 256503351
Organization: Home
X-Server-Date: 13 Jul 1997 00:46:42 GMT
Newsgroups: comp.lang.ada
Date: 1997-07-13T00:46:42+00:00
List-Id: <comp.lang.ada>


My company has been using the principles of Real-Time Structured Analysis
to design the software for its real-time embedded systems for several years
(we use Cadre Teamwork with Rational Apex Ada (83) - cross compiled with
VADScross). They (primarily our SW engineering manager) claim that they
have nothing against an object oriented approach but that none of their SW
engineers are trained in applying its principles to an actual system
design. Not being all that knowledgeable in OO design myself, I was
wondering if anyone  is familiar with both approaches to requirements
design/implementation and can give an opinion as to which approach is
better for RT embedded systems?

-- 
Paul Van Bellinghen
Staff Analyst
Lockheed Martin Fairchild
pvanbell@mhv.net