THE MODEL, THE TEXTUAL AND GRAPHICAL RAS, AND THE … · 2017-02-16 · THE TEXTUAL AND GRAPHICAL...

JOG SYSTEM ENGINEERINGGRAND SYSTEMS DEVELOPMENT

TRAINING PROGRAM INTRODUCTORY PRESENTATION

THE MODEL, THE TEXTUAL AND GRAPHICAL RAS, ,

AND THE SPECIFICATION –A LOGICAL AND EFFECTIVE

PROGRESSIONPresented ByPresented By

Jeffrey O. GradyJOG SYSTEM ENGINEERING

(858) 458-0121

VERSION 14.0 122A-1 c JOG System Engineering

[email protected]

Who Is Jeff Grady?CURRENT POSITION

1993 – PRESENT Owner, JOG System EngineeringSystem Engineering Assessment, Consulting, and Education Firmy g g g

PRIOR EXPERIENCE1954 - 1964 U.S. Marine Corps1964 - 1965 General Precision, Librascope Division

Customer Training Instructor, SUBROC and ASROC ASW Computing Systems1965 - 1982 Teledyne Ryan Aeronautical

Field Engineer, AQM-34 Series Special Purpose Aircraft SystemsProject Engineer, System Engineer on Unmanned Aircraft Systems

1982 - 1984 General Dynamics Convair DivisionSystem Engineer Cruise Missile Advanced Cruise MissileSystem Engineer, Cruise Missile, Advanced Cruise Missile

1984 - 1993 General Dynamics Space Systems DivisionFunctional Engineering Manager Systems Development Department

FORMAL EDUCATIONSDSU BA Math, UCSD Systems Engineering Certificate,SDSU BA Math, UCSD Systems Engineering Certificate,USC MS Systems Management With Information Systems Certificate

INCOSE Founder, Fellow, ESEP, and First Elected SecretaryAUTHOR System Requirements Analysis (3), System Integration, System

Validation and Verification, System Verification, System Engineering


Validation and Verification, System Verification, System Engineering Planning and Enterprise Identity, System Engineering Deployment, System

Synthesis, System Management

The Principal Presentation References“System Requirements Analysis, 2nd Edition”, Jeffrey O. Grady, Elsevier Academic Press, 2014

The Principal Presentation References

"The Model, the Textual and Graphical RAS, and the Specification – A Logical and Effective Progression", Jeffrey O. G d t t bli h d 2013Grady, paper not yet published, 2013

"Universal Architecture Description Framework (UADF)", Jeffrey O Grady Systems Engineering The Journal of TheJeffrey O. Grady, Systems Engineering, The Journal of The International Council On Systems Engineering, Volume 12 Number 2, Summer 2009 (Best Paper 2009)

"Affordable Requirements Verification", Jeffrey O. Grady, INCOSE Insight, July 2013 (Volume 16, Issue 2)


New System RequirementsNew System Requirements Analysis Book in E-Book Format


P t ti Obj tiPresentation Objective

PublishedSpecificationsModel the Problem Space

Annotating Artifacts With MIDMID REQUIREMENTS ENTITY SPECIFICATION

AllocateRequirements

MID REQUIREMENTS ENTITY SPECIFICATION

RAS And on toVerification

ModelVerification

List Artifacts in RAS in MID Alphanumeric Order Derive

RequirementsEmploy UniversalFormat For Entity

Specification


p

What Is a System?What Is a System?

• Collection of product entities intended to achieve aCollection of product entities intended to achieve a specific function

• Immersed in an environment• Product and environmental entities inter-related

through interfaces• Product and interface entities clearly defined in aProduct and interface entities clearly defined in a

set of specifications where all of the content has been derived though application of a model to the problem spaceproblem space


Systems Development

• Define the problem to be solved in a set of product and interface entity specificationsy p

• Solve the problem through synthesis in a three-step process

D i– Design– Procurement– Manufacturing

• Determine extent to which entities and the system comply with the content of the specifications through verificationthrough verification

• Manage the program well throughout its development period


Enterprise Common Process ViewEnterprise Common Process View of System Life Cycle


Major Problem on All Programs -Specification ContentSpecification Content

• Each specification contains the essential characteristics its product or interface entity must possess in the form of req irementspossess in the form of requirements

• An enterprise should derive the content of all specifications on all programs using a single p p g g gcomprehensive universal architecture description framework (UADF) model

– FunctionalFunctional– MSA-PSARE– UML-SysML

UPDM maybe– UPDM maybe• Adopt the Model-RAS-Specification Sequence using

your selected UADF and a template coordinated


with it

Models Channel Requirements Into the Human Mind Through Visionthe Human Mind Through Vision –

A Picture is Worth 103 Words

Hmmm, The aircraft

FUNCTIONALFACET

,must travel from A to B

on a leg. How fast would be appropriate

and at what altitude?

O PHYSICAL

VISION

PROBLEMSPACE

PHYSICALFACET

HAND-EYECOORDINATION

BEHAVIORAL


ANALYSTFACET

The First Objective of ModelingThe First Objective of Modeling- Architecture

Wh t i i bj ti d th t i h t• What mission objective does the customer wish to achieve?

• What product entities shall the system consist of?p y• How shall those product entities be inter-related

through interfaces?Wh t d th t i t i t f?• What does the system environment consist of?

• How are the product entities related to the environment?

• What specialty engineering domains must be respected in the design?


The Second Objective of ModelingThe Second Objective of Modeling- Requirements

Something wanted ornecessary.

ENTITY

Something essential to the existence oroccurrence of anoccurrence of an entity.A necessary character-yistic or attribute of something (or entity).


Progressive Modeling

From work of Brian Mar and Barney Morias


Three UADF Are Available

• A UADF is a comprehensive modeling• A UADF is a comprehensive modeling approach in that it matters not how you will implement the solution in HW, SW, or people doing thingsdoing things

• One model is equally effective in HW and SW• Pick onec o e

– Functional– MSA-PSARE

UML SysML– UML-SysML– UPDM maybe


Functional UADF Functional Flow Diagramming

PLAN MISSION

DATA

USESYSTEM

F47

1

PROCESS LAUNCH

VEHICLE

F471

RECEIVE LAUNCH

VEHICLEF473

IOR AND

PROCESS UPPER

STAGEIOR

INSTALL SOLID

ROCKETS

INTEGRATE UPPER

STAGE

PAYLOAD

INTEGRATEPAYLOAD

INTEGRATE PAYLOAD

FAIRING

PLAN TRANSPORT

MISSION

DATA

PREPARE VEHICLE FOR

LAUNCH IOR

F475

F476 F478 F479 F47A

F47B

F47CIOR

STORE AND PROCESS

PAYLOAD

IOR

LAUNCHVEHICLE

F47S

USE SYSTEM

STORE LAUNCH

VEHICLEF472

REFURBISHLAUNCH PAD

MAINTAIN PADREADINESS

IOR

PROCESS PAYLOAD

FAIRING

PROCESS SOLID

ROCKETS

IOR

MAINTAINREADINESS

EXECUTE LAUNCH

OPERATIONS

LAUNCH ABORT

OPERATIONS

FLIGHTOPERATIONS IOR

DISPOSEOF SOLIDS

F474

F477

F47D

F47E

F47F

F47GF47MF47N OF SOLIDS

DISPOSE OF LAUNCH

VEHICLE

DISPOSE OFFAIRING

UPPER STAGE

FLT OPS SEPARATE

PAYLOAD

PAYLOADOPERATIONS

DESTRUCT

F47EF47G

F47H1

F47H2

F47H3 F47I F47J

F47M

MANAGEOPERATIONS

F47N

SITELOGISTICS

F47P

F47Q

VACATEPAD

F47K

OPERATIONALDISPOSAL

4

DISPOSE OF UPPER

STAGE

LAUNCHVEHICLE

F47H4

F47H5

F47LF47R

DISPOSAL

F47H RECYCLE DESTACKED

END ITEMS

TRANSPORTEND ITEMS

F47


But this technique will work with any UADF.

Functional UADF Product Entity Diagram

TITAN IVVEHICLE

TITAN IVGROUNDSYSTEM

TITAN IVSYSTEM

A

VEHICLEA1

COREVEHICLE

SOLIDROCKET

BOOSTERSA11A13 A12

PAYLOADFAIRING

CENTAURUPPER STAGE

IUSUPPER STAGE

A15

SYSTEM A2

A14

STRUCTURALSYSTEM

TRACKINGSYSTEMINSULATION

MISSIONPECULIAR

KITA1411

A1412 A1419

A1418

STAGE I

STAGE II

SRM 1

SRM 2

A111

A112

A121

A122

PROPULSIONSYSTEM

REACTIONCONTROLSYSTEM

RANGE SAFETYSYSTEM

TELEMETRY& INSTRUMENT-ATION SYSTEM

A1413

A1414

A141A

A141B

INTERSTAGEADAPTER

CENTAURADAPTER

A113

A114

TITAN IV SYSTEM

PROPELLANTCONTROLSYSTEM

HYDRAULICSYSTEM

ELECTRICALPOWERSYSTEM

FLIGHTCONTROLSYSTEM

A1415

A1416

A141C

A141DCan Include Software


TITAN IV SYSTEMPRODUCT ENTITY BLOCK DIAGRAM

SHEET ENG DATE10 11-13-90

PNEUMATICSYSTEM

A1417 A141E

FLIGHTSOFTWARE

A141E

Functional UADFFunctional UADFTop-Level View of System Interface

ENVIRONMENT SYSTEMI2I1I3

AQ

Internal InterfaceI1 Innerface

External InterfaceI2 CrossfaceI2 CrossfaceI3 Outerface


Functional UADFFunctional UADFTwo Interface Reporting Models

Schematic block diagramming Lines define interfaces

A2Blocks are objects selected only from the product entity structure

A1

A4

A3A5

A6

N-square diagrammingstructure

Marked intersections define interfacesXA1

Diagonal blocks are objects only from product entity structure

X XX

XX

X

A1A2

A3A4

A5

X

X

XX

X


Apparent ambiguity reflects directionalityX

A6X

X

Functional UADFSpecialty Engineering Scoping Matrix

2 1

1.1 1.2 1.3 1.4 1.5H21

A11 A12 A13 A14

H22

A15

X X X

XX

2.52.4

C

PRODUCT ID (PID) SpecialtyEngineeringRequirements

Analysis2.1

2.2

2.3

3.1

3 2

H23

H31

H32

H41

X

XXX

X X XX X

X

X

X

X

X

H42 A11

CONSTRAINT PID

CONSTR

PARA

3.2

4.1

4.2

5.1

5.2

H51

H52

H53

XXXX X

X X

X

XX

XXXX

H42 A12

H42 A13

H42 XX

X

AINTS

XFROM

TEMPLATE

5.3

6.1

H71

H61

H71

X X

X X X X

X XX

X

X

SPECIALTY ENGINEERING SCOPING REQUIREMENTS ANALYSIS SHEET

H42 A21


SPECIALTY ENGINEERING SCOPING MATRIX

QU S S S S(IN A COMPUTER DATABASE)

Functional UADFE i l ClEnvironmental Classes

SYSTEMENVIRONMENT

NATURAL SELF IINDUCEDHOSTILENON-

Q

COOPERATIVENATURALENVIRONMENT

SELF-IINDUCEDENVIRONMENT

HOSTILEENVIRONMENTCOOPERATIVE

ENVIRONMENT

SPACE

Q3 Q4 Q1 Q5 Q2

COOPERATIVEENVIRONMENT

MASS AND SPACE

TIME

Q11

MASS ANDENERGY

Q14

TIME

NATURALSTRESSES

Q12


STRESSES

Q13

Functional UADFGeneric External Interface MID

I3136

I21NATURAL

ENVIRONMENT

Q1

I22

I32

I33

II3

7

I38

I39

3A

COOPERATVE SYSTEMS

ENVIRONMENTQ2

SYSTEMI23I1

I33

I34

I33B C

I3D

E

I3 NON-COOPERATIVESYSTEMS

ENVIRONMENTQ3

I24

I34

I35

I3 I3C

I3E

3F

HOSTILESYSTEMS

ENVIRONMENTQ4

SYSTEM

I25

I3

I2

SELF INDUCEDENVIRONMENT

Q5

ELECTRO-MAGNETIC


ENVIRONMENT

AQ

MAGNETICENVIRONMNTAL

EFFECTS

Functional UADFFunctional UADFThree Tier Environmental Modeling

• System level using integrated union of tailored• System level using integrated union of tailored standards

• End item level using three dimensional service use profile

– Product entities– Environmental stresses– Process steps

• Component level using end item zoning and mapping components to zonesmapping components to zones

• Possible need for an environmental sub system


Functional UADF Process Flow Diagram N d d P t f th E d It E i t l M d lNeeded as Part of the End Item Environmental Model


Systems Development Using the MSA-PSARE UADFPSARE UADF

Assign Product Entity MID (A) to Super Bubbles


Assign Product Entity MID (A) to Super BubblesAssign Interface MID (I) to Functional Relations (R)

System Development Using theSystem Development Using the UML-SysML UADF

System

Terminator 1 Terminator 2

Context Diagram1

Sequence Diagram

StateDiagram

Dynamic Analysis5A

7

Cycle to Lower Tiers9

Terminator 3

Use Case

2 Top Level

5B Communication

Diagram

5

InteractionDiagram for

Each scenario

Product EntityStructure

8

Possible Extended and/or I l d d U C

Use Case

3

Use Case for

Each Terminator

Activity DiagramWith Swimlanes

6B

Each scenario

OR

Use Case

Use Case

Use Case

Use Case

Included Use Cases

Scenario Set For Each

U C

4

6A

Activity Diagram for

Each Scenario

RequirementsOR


Use Case

No Matter the UADF Selected –Employ Three-Dimensional Requirements Traceability

LONGITUDINAL TRACEABILITY

Parent ChildVERIFICATION

SYNTHESIS

VERTICAL TRACEABILITY

Parent-ChildSource

Rationale

LATERIAL TRACEABILITY Derivation

REQUIREMENTS

DerivationFrom

Models


REQUIREMENTS

Suggested Specification Section 3Suggested Specification Section 3 Template

TIMID ADVANCE3. REQUIREMENTS 3.4 Specialty Engineering Requirements3.1 Modeling 3.5 Environmental Requirements3.2 Performance Requirements 3.5.1 Natural Environment

TIMID ADVANCE

3.3 Interface Requirements 3.5.2 Cooperative Environment3.3.1 Internal Interfaces (I1) 3.5.3 Non-Cooperative Environment3.3.2 External Interfaces (I2) 3.5.4 Hostile Environment3.3.3 Outside Interfaces (I3) 3.5.5 Self-Induced Environment

3. REQUIREMENTS 3.3.2.1 Natural Environment3 1 Modeling 3 3 2 2 Cooperative Systems Environment

AGGRESSIVE ADVANCE

3.1 Modeling 3.3.2.2 Cooperative Systems Environment 3.2 Performance Requirements 3.3.2.3 Non-Cooperative Environment3.3 Interface Requirements 3.3.2.4 Hostile Environment3.3.1 Internal Interfaces 3.3.2.5 Self-Induced Environment3.3.2 External Interfaces 3.4 Specialty Engineering Requirements


Unique Modeling Artifact IdentificationUnique Modeling Artifact IdentificationTo Support Lateral Traceability

MID MEANING PARA DEPT PREFERRED MODEL---------- ----------------------------------------- ------------ --------- ---------------------------------------A Product Entity 3.1 331 Product Entity Block DiagramF Functionality 3.1 331 Functional Flow DiagrammingH Specialty Engineering Domain 3.4 331 Specialty Engineering Scoping MatrixH1 Engineering Domain 3.4.1 3XX -H11 Aerodynamics 3 4 1 1 321 Modeling and SimulationH11 Aerodynamics 3.4.1.1 321 Modeling and SimulationH12 Thermodynamics 3.4.1.2 322 Thermodynamic AnalysisH13 Structural Integrity 3.4.1.3 323 Modeling and SimulationH14 Structural Statics 3.4.1.4 323 Modeling and SimulationH15 Structural Dynamics 3.4.1.5 323 Modeling and SimulationH2 Logistics Domain 3.4.2 341 Functional Flow DiagrammingI Physical Interface 3.3 331 N-Square Diagramy gI1 Internal Interface 3.3.1 331 N-Square DiagramI2 External Interface 3.3.2 331 N-Square DiagramI3 Outside Interface 3.2.3 331 N-Square DiagramJ Functional Interface NA 331 N-Square DiagramP Process - - Process Flow DiagramQ Environment 3.5 331 Three Tier ModelQ1 Natural Environment 3 5 1 331 StandardsQ1 Natural Environment 3.5.1 331 StandardsQ11 Space 3.5.1.1 331 Mission Analysis and PackagingQ12 Time 3.5.1.2 331 Time LinesQ13 Natural Stresses 3.5.1.3 331 StandardsQ2 Cooperative Environment 3.3.2 331 N-Square DiagramQ3 Non-Cooperative Environment 3.3.3 331 Threat AnalysisQ4 Hostile Environment 3.3.4 331 Threat Analysis


Q yQ5 Self-Induced Environment 3.3.5 331 No Specific ModelR Requirement 3 3XX -

RAS-Complete In Table FormMODEL ENTITY REQUIREMENT ENTITY PRODUCT ENTITY DOCUMENT ENTITYMID MODEL ENTITY NAME RID REQUIREMENT PID ITEM NAME PARA TITLE--------- ------------------------------------------------ ---------- -------------------------------------------- --------- --------------------------------- ------------ ------------------------------F47 Use System A Product SystemF471 Deployment Ship Operations A Product SystemF4711 Store Array Operationally RXR67 Storage Volume < 10 ISO Vans A1 Sensor Subsystem

H Specialty Engineering Disciplines A Product SystemH11 Reliability REW34 Failure Rate < 10 x 10-6 A1 Sensor Subsystem 3.1.5 ReliabilityH11 Reliability RG31R Failure Rate < 3 x 10-6 A11 Cable 3.1.5 ReliabilityH11 R li bilit RFYH4 F il R t < 5 10 6 A12 S El t 3 1 5 R li bilitH11 Reliability RFYH4 Failure Rate < 5 x 10-6 A12 Sensor Element 3.1.5 ReliabilityH11 Reliability RG8R4 Failure Rate < 2 x 10-6 A13 Pressure Vessel 3.1.5 ReliabilityH12 Maintainability R6GHU Mean Time to Repair < 0.2 Hours A1 Sensor Subsystem 3.1.6 MaintainabilityH12 Maintainability RU9R4 Mean Time to Repair < 0.4 Hours A11 Cable 3.1.6 MaintainabilityH12 Maintainability RJ897 Mean Time to Repair < 0.2 Hours A12 Sensor Element 3.1.6 MaintainabilityH12 Maintainability R9D7H Mean Time to Repair < 0.1 Hours A13 Pressure Vessel 3.1.6 Maintainability

I System Interface A Product SystemI System Interface A Product SystemI1 Internal Interface A Product SystemI11 Sensor Subsystem Innerface A1I181 Aggregate Signal Feed Source RE37H Aggregate Signal Feed Source A1 Sensor Subsystem

Impedance Impedance= 52 ohms + 2 ohmsI181 Aggregate Signal Feed Load RE37I Aggregate Signal Feed Load A4 Analysis and Reporting

Impedance Impedance= 52 ohms + 2 ohms SubsystemI2 System External Interface A Product System

Q System Environment A Product SystemQH Hostile Environment A Product SystemQI Self-Induced Environmental A Product System

StressesQN Natural Environment A Product SystemQN1 Temperature R6D74 -40 degrees F< Temperature A Product System

< +140 degrees F


< +140 degrees FQX Non-Cooperative Environmental A Product System

Stresses

The Requirements Analysis SheetThe Requirements Analysis Sheet (RAS)

• Tabular RAS in a computer database from• Tabular RAS in a computer database from which specifications may be printed is needed on every program

• Graphical RAS will be used in this presentation to explain the content and loading the tabular RAS from models

• In this presentation the functional UADF modeling artifacts are used in building the graphical RAS but the idea is compatible withgraphical RAS but the idea is compatible with the other two UADF as well


Capture the Model and pConfiguration Manage It

• Systems Architecture Report (SAR) Recommendedy p ( )• For the Functional UADF the following appendices

are suggestedA Functional Flow DiagramA Functional Flow DiagramB Environment (Natural, Cooperative, Non-cooperative,

Hostile, Self-Induced)C P d t E tit Bl k DiC Product Entity Block DiagramD Interface Diagram (Schematic Block or N-Square

Diagram)S SE Specialty Engineering Scoping Matrix

F Process DiagramG RAS or reference to its location


Graphical RAS – Performance Requirements Plane

PRODUCTA

PRODUCTA

R4jU864 NEED

A24 A43

ENTITY AXIS (PID)F

ENTITY AXIS (PID)F

F472

R7Y5j6S

In theProgram Beginning F472

3

F473D

RK4I76dPERFORMANCE

FUNCTION

PERFORMANCE REQUIREMENTS

PLANE

FUNCTIONAXIS (FID)

E l i


FUNCTIONAXIS (FID)

Evolving

Graphical RAS – Internal Interface PlaneGraphical RAS Internal Interface PlaneA11

A12

A13

A14

A15

A16

A21

A22A22

A23

A24

A25

A26

A27

A28

A31

A32

A33

A34

A41

A42


A43

A44

Graphical RAS – Rotate Internal Interface Plane

R6Ih743 INTERFACEREQUIREMENT

PRODUCT ENTITY

AXISPRODUCT ENTITYPRODUCT ENTITY

A24

PRODUCT ENTITYA43

INTERNALINTERFACE

PLANEPLANE


Graphical RAS – Functional Plane Coordinated With Interface Plane

F A24

PRODUCTENTITY A

A43R6Ih743

AXIS (PID)A

F4723

R7Y5j6S

INTERFACEPLANE

F473D

RK4I76dPERFORMANCE REQUIREMENTS

FUNCTION

REQUIREMENTSPLANE


AXIS (FID)

Graphical RAS – Specialty Engineering Plane

SPECIALTYDOMAINDOMAIN

SPECIALTYENGINEERING

REQUIREMENTS

H2R5hY746

PRODUCTENTITY

A43


Graphical RAS E t d d

SPECAILTYDOMAIN

– Extended Interface Plane SPECIALTY

ENGINEERINGREQUIREMENTS

PLANE

PRODUCTENTITY

ENVIRONMENTALENTITY

EXTERNALINTERFACE

INTERNALINTERFACE

Q2Q3Q4 Q1Q5

PERFORAMNCEREQUIREMENTS

PLANE

ENVIRONMENTALPLANE


FUNCTION

Complete Graphical RASSPECIALTY

SPECIALTY

ENGINEERINGDOMAIN

H2R5hY746

A43

PRODUCTENTITY

SPECIALTYENGINEERING

PLANE

ENVIRONMENTAL R Y45K6

A24Q253ENVIRONMENTAL

ENTITY

PERFORAMNCEREQUIREMENTS

PLANE

ENVIRONMENTALPLANE

QQ2Q3Q4Q5

R3Hy5e6

RxY45K6F4723

F532

FUNCTION

Q1

QQ3QQ5

INTERFACE

R6Ih743

INTERNAL

EXTERNAL


PLANE

Model - RAS - SpecificationModel RAS SpecificationSequence

PublishedSpecifications

Model the Problem SpaceAnnotating Artifacts With MID


AllocateRequirements


RAS And on toVerification

ModelVerification

List Artifacts in RAS in MID Alphanumeric Order Derive

RequirementsEmploy UniversalFormat For Entity

Specification


pMANAGE THE WHOLE WELL

Prescription For the Enterprise That Has Not Yet Reached Perfection

1. Adopt a UADF and insist that all persons doing architecture development and p p g prequirements analysis work use it.

2. Adopt a way of uniquely identifying all modeling artifacts from which requirements may be derived.

3. Adopt a means by which personnel may capture modeling and specification content such that they may be configuration managed There are not any computer toolssuch that they may be configuration managed. There are not any computer tools known to the author that could capture all of the modeling and documentation features covered in the paper but one could build a simple text-oriented database linked to hand drawn or computer application graphics modeling artifacts.

4. Adopt a means for personnel to accomplish modeling work and retention of masters in the formal system baseline documentation.

5. Adopt a set of specification templates coordinated with modeling.6. Establish a policy such as Table 1 of the supporting text suggests that clearly assigns

responsibility for all specification content to personnel from specific functional departments on all programs.departments on all programs.

7. Prepare a written document telling how this work is to be done on programs.8. Train all personnel who have a role in this work in the appropriate parts of it assigned

to their functional department.9. Establish a quality assurance means that will assure that the work is accomplished in

d ith th d i t ti d t t l i t


accordance with the prepared instructions and contractual requirements on programs.

THE MODEL, THE TEXTUAL AND GRAPHICAL RAS, AND THE … · 2017-02-16 · THE TEXTUAL AND GRAPHICAL...

Documents

Transcript of THE MODEL, THE TEXTUAL AND GRAPHICAL RAS, AND THE … · 2017-02-16 · THE TEXTUAL AND GRAPHICAL...