1. PAISE-3-2-1: P erspective-bridged A rchitecture “Automatic Prototype Generating” Restated with re-ADA By Sheldon X. Liang Computer Science Azusa Pacific University

2.  Review of Previous Work in Ada  Three System Perspectives  Two Traditional Methodologies  One PAISE Transitioning Approach  Conclusion and Acknowledgement PAISE-3-2-1: P erspective-bridged A rchitecture

3.  Review of Previous Work in Ada  Ada-based Support for Abstraction, Encapsulation and Unit Hierarchy, TRI-Ada’91, San Jose, CA, 1991  An initial thought of introducing OO to Ada  Omega: Unified Object Model Easy to Gain Ada’s End, Ada Letters, Vol. 21, 2, (2001)  Some thoughts of unifying ADT, FSA, Task into class-like object  Event-based Implicit Invocation Decentralized in Ada95, Ada Letters, Vol. 22, 1, (2002).  Some initial thoughts of adapting Ada into Architectural Description  Automatic Prototype Generating via Optimized Object Model, Ada Letters, V(2), 2003  Some reflections of prototyping DFD to executable/evolvable product  re-ADA: Reliable Ada-based Descriptive Architecture for C4ISR via a Quantitative Model, ACM SIGAda’08, Portland, OR.  Some creative thoughts of building interoperable architecture PAISE-3-2-1: P erspective-bridged A rchitecture

4.  Three System Perspectives  Conceptual Prototype (Requirements)  Technical Architecture (Transitioning)  Operational Product (Implementation) PAISE-3-2-1: P erspective-bridged A rchitecture

5.  Two Traditional Methodologies  Compartmentalization (SSAD) Good at acquiring requirements at earlier stage Good at acquiring requirements at earlier stage Early and easy to satisfy the customer (prototyping) Early and easy to satisfy the customer (prototyping)  Poor to adjust at later stage  Componentalization (CBSE) Good at adjusting requirements at later stage Good at adjusting requirements at later stage Late and easy to satisfy the customer (sub/ex) Late and easy to satisfy the customer (sub/ex)  Poor to acquire requirements PAISE-3-2-1: P erspective-bridged A rchitecture

6.  One PAISE Transitioning Approach  Perspective Transitioning Approach = SSAD (Structured Systems Analysis & Design) + CBSE (Component-Based Software Engineering) + PAISE (Perspective-bridged Architecture via + PAISE (Perspective-bridged Architecture via Interoperability + Substitutability Extensibility) SSAD Compartmentalization  Good at Req-acquiring CBSE Componentalization  Good at Req-adjusting PAISE-3-2-1: P erspective-bridged A rchitecture

7.  One PAISE Transitioning Approach  Requirements acquiring (earlier) & adjusting (later) SSAD CBSE PAISE Conceptual TechnicalOperational Effectiveness Life Stages PAISE-3-2-1: P erspective-bridged A rchitecture

8.  Formal PAISE  Interoperability  Substitutability  Extensibility PAISE-3-2-1: P erspective-bridged A rchitecture

9.  PAISE Showcase  From context DFD to structured DFD PAISE-3-2-1: P erspective-bridged A rchitecture

10.  PAISE Showcase  From DFD to Perspective-bridged CBSE PAISE-3-2-1: P erspective-bridged A rchitecture

11.  PAISE Showcase  Perspective-bridged CBSE with re-ADA PAISE-3-2-1: P erspective-bridged A rchitecture

12.  Conclusion and Acknowledgement  A successful PAISE bridge between SSAD & CBSE  Full transitioning process from Req. to Impl..  Wise use of advantages in Ada  Substitutability (static and dynamic)  Extensibility (inheritance and polymorphism)  Organizational Units (package, task, subprogram)  A very high level ADL emerges in support of software engineering process PAISE-3-2-1: P erspective-bridged A rchitecture

13.  Conclusion and Acknowledgement Deeply grateful to Ada community where software engineering has been greatly associated with a programming language. Software engineering has developed us at the philosophical depth of recognizing the world. Particularly, we have experienced and enjoyed the beauty of creation not because of our creativity in software engineering, but our humility in awe of the creation of the universe. PAISE-3-2-1: P erspective-bridged A rchitecture