\SlideFrontPage{\myInput{\prefix abstract}}

\SlideFigure{Figure of Contents$^{\mbox{\small {\bf TM}}}$}{AACLlogo}
%what do we teach
\SlideFigure{What do we teach bachelor students?}{AACLbachelors}
\SlideFigure{Mono-disciplinary engineering}{BSEARmonoEngineering}
\SlideFigure{Huge differences in language and way of thinking}{BSEARmonoEngineeringCharacteristics}
\SlideFigure{Multi-disciplinary design and engineering}{BSEARmultiEngineering}
\SlideFigure{Architecting: Fit-For-Purpose}{BSEARarchitecting}
\SlideFigure{Delivery at the end of this module}{BSEARdeliveries}
\SlideFigure{More specific deliveries}{BSEARdeliveriesElaborated}
\SlideFigure{}{AACLmastersAndParttimers}

%Why, what do we assume? connect breadth and depth, abstraction levels, roles
\SlideFigure{Why, what do we assume?}{AACLlogoAssumptions}
\SlideFigure{Problem: Disconnect between Breadth and Depth}{RATWdisconnect}
\SlideFigure{Assumption 1: Architects form the Hinge}{RATWbreadthAndDepth}
\SlideFigure{Level of Abstraction Single System}{RAPpyramid}
%\SlideFigure{From system to Product Family or Portfolio}{DRALpyramidGrowth}
%\SlideFigure{Product Family in Context}{RAPdiabolo}
%\SlideFigure{RA: Capturing the Essence}{RAPdiaboloRA}
%\SlideFigure{Engineering}{LAWFengineering}
%\SlideFigure{Design}{LAWFdesign}
\SlideFigure{Assumption 2: Architecting at Multiple Levels of Abstraction}{LAWFdiabolo}
\SlideFigure{Assumption 3: Main Roles in Product Creation}{PCPoperationalOrganization}

%Why, what to achieve? content leadership, integral, holistic, big picture, good system fitting context
\SlideFigure{Why, what to achieve?}{AACLlogoGoal}
\SlideFigure{Responsibilities according SARCH course}{RSAresponsibilities}
\SlideFigure{Ability to go Deep where needed}{DTAtrapezoidChain}
\SlideFigure{Participating in Product Creation and Strategy}{SAPprocessSimplified}

%Past, where were companies? system level ill understood, context ill connected, lacking effectiveness and efficiency
\SlideFigure{Past, where were companies?}{AACLlogoPast}
\SlideFigure{}{AACLacademicDisclaimer}
\SlideFigure{Observations Based on Actual Contacts}{AACLcompanyContacts}
\SlideFigure{Status in the Past}{AACLstatusPast}
\SlideFigure{Frequently observed gaps}{DRALgaps}
\SlideFigure{The Data behind the Statements}{AACLpastPresenceSystemRole}
\SlideFigure{Need for Architecting is Increasing!}{BCURRtrends}

%Today, where are companies?
\SlideFigure{Today, where are companies?}{AACLlogoToday}
\SlideFigure{Presence and Awareness of Systems Role}{AACLstatusPastAndToday}
\SlideFigure{Some Observations}{AACLobservations}

%Why are we in this state?
\SlideFigure{Why are we in this state?}{AACLlogoWhyState}
\SlideFigure{Some Reasons for Stagnation}{AACLreasonsForStagnation}
\SlideFigure{The Playing Field}{SEMABentitiesInTime}
\SlideFigure{and its Main Challenges}{SEMABchallenges}

%Future what and how to teach?
\SlideFigure{Future what and how to teach?}{AACLlogoTeaching}

\SlideFigure{What is Competence?}{AACLcompetence}
\SlideFigure{Competence Program Partitioning}{AACLcompetenceProgram}
\SlideFigure{Flows}{AACLcompetenceProgramHow}

\SlideFigure{}{AACLsummary}

%\SlideFigure{}{AACLescapeDirections}


