Embed Size (px)
Citation preview
LessonsLearnedwithData,Requirement,andModelExchange
ATalkintheParkJune21,2016ThomasCapelle
• Sodius'missionistoeasetheflowofengineeringdataacrosstheextendeddesignandimplementationteam
• Ourvisionistobeareliableproviderofproductsandservicesacrosstheengineeringteamthatenablesthem– toconnectbespokesourcesofinformation– navigatetherelationshipsbetweenthesesources– transformotherwiseuselessdataintoactionableinformation
– andopenworkartifactsforformalfeedbackandcrossteamcollaboration.
OurMission
• A20+persontechnologycompanywithrepresentationinFrance,SwitzerlandandtheU.S.
• Founded in1999asSystemsEngineeringtrainingandconsultingcompany
• Specializedincomplexdataintegrationsolutionswithagoaltoeaseandacceleratecollaborationprocesses
• Expertsindesigndatasuchasrequirements,architecturemodels,engineeringmodels,softwaredevelopmentartifacts
• ProviderofcriticalcomponentstoseveralSoftwareOEMs
• Deliverssolutionsworld-wideatlargeaccountswithstringentqualityrequirementsinmarketssuchasDefense,Aerospace,Automotive
6/23/163
WhoisSodius?
Ke y c u s t ome r s
S om e s u p p o r t e d d a t a f o r m a t s
6/23/164
Sodius’LayeredTechnology
IBMRhapsodyOEMModel-basedtransformationandcodegenerationcapabilities
GetYourDataNoMatterWhereitwasAuthored
DataAccess
ReuseYourDataintheFormatYouNeedDataTransformation
GetYourDatatoWhereitisNeededDataIntegration
RLIAWindchill®IntegratesWindchillPLMwithCCMALMviaOSLC
DXLEditor®UniqueEclipseplug-ineditorforDOORSDXLprogramminganddebugging
MDAccess®EMF-based JavalibrariesforR/Waccesstoformat-specificfiles,e.g.DOORS,EnterpriseArchitect,MagicDraw,etc.
MDConnect®Offers contentinEclipse(e.g- DOORSinIBMRSAtools)
MDWorkbench®Eclipse-baseddevelopmentenvironmentforcustomModel-to-TextandModel-to-Modeltransformation
SE-Collab®Shareandannotatecomplexsystemsengineeringartifacts
EngineeringKnowledgeIntegrationStoreandspreadsystemsengineeringartifactssecurely
ExampleInformationExchanges
RequirementNegotiationbetweenanOEMandSupplier
• AutomotiveOEMs,Tier1sandsuppliersarecontinuouslyexchangingrequirements/stakeholderrequests.
• RequirementsManagementToolsandprocessesvaryconsiderablyfromBUtoBU(internally)andbetweenorganizations.Itrequiressupport teamsineachBU(5peoplesmin.)to importandcheckrequirementsexchanges.
• Aharmonizedautomatedtooling&methodissignificantlyhelptoremovethisdrawbackandenablesyncwiththecorporateRM/CMsystem
RequirementSynchronization
StakeholderRequestRoundTripProcess
DOORS
OEMs Supplier
…
BU1
BU2
BUn
…
• Typically,theexchangeisbasedoncustomattributesthathavetobefed(createandupdate)frombothpartstofeasibility/maturity/acceptanceofitems
RMDataMapping
Customer Supplier
MappingRules
Howtoautomate?
DOORS
GetYourDataNoMatterWhereitwasAuthored
DataAccessGetYourDataNoMatterWhereitwasAuthored
DataAccess
ReuseYourDataintheFormatYouNeedDataTransformation
ExampleofAutomatedCollaborationServiceDOORStoIntegritySynchronization
MDWorkbenchWebServicesLayer
DOORSCLIENT
DOORSSERVER
DOORS
1 2 4“Input”DATA “Output”DATASelectServiceAndenterArguments
HTTP/HTTPS
IntegritySERVER
RunMappingRules
Serverside
Doors2Integrity
MDWorkbenchServiceLauncher
3 ProgressOnRemoteExecution
2 SelectService
ClientSide
SODIUSMappingProcessor
MappingbetweenAPIs
FormalModuleRequirementsDocument
StakeholderRequestDocument
ObjectHeading
ObjectText
ObjClass
SafetyLevel
SystemAttributes
CustomAttributes
…
Title
Content.fva
Safety
Category
IntegrityStructureDOORSStructure
Requirement
StakeholderRequest
Object
Mappingprofile
…
…
executes
ExchangeScenario
DOORSModule
1
IntegrityRequirementsDocument
3
DOORStoIntegrityConversion
2 IntegrityToDOORS
5
6
IntegrityRequirementsDocumentEditing
4
DOORSModuleUpdated
DOORStoIntegrityExchangePlatform
WebApplication thatexecutessynchronizationtasksonadedicatedserver
1
2
3
Mappingfeatures
MERGING
ConfigurableMapping(conditions,enums,computedvalues)
TABLE&RichText
ComputedFieldsbyscripts(e.gsetDOORSWebAccessLink)
DefectReportingBetweenanOEMandSupplier
• SynchronizationbetweenXMLdefectreportingandJazzApplications– ExternalData:VariousXMLfilesformatsfromOEMs– CorporateSystem:JAZZCCM
DefectReportingExample
ModelExchangeforDefenseSystems
SharedSystemModel
PTCWindchill
SystemArchitect/Mega
MEGA
SA
Diagrams and Data can be exchanged between tools
UML Base Classes
«metaclass»InformationFlow
«metaclass»Property
«metaclass»Class
whole
1
*
part
1
*
target
1
*
source
1
*
Node«extends»
NodeAssemblyUsage
InformationExchange
target
1
*
source
1
*
class
1
*
type
1
*
NOV-2 Stereotypes
«metaclass»Package
1
ownedMember*
ArchitecturalDescription
NodeRelationshipDescription
ArchitecturalProduct
CompositeStructureModel«extends»
«extends»
owningArchitecture1
products*
«metaclass»PackageableElement
«metaclass»Dependency
«extends»
«extends»
«extends»
NodeConnector«metaclass»Connector
«metaclass»ConnectorEnd
«extends»
1
2
NodeConnectorEnd
«extends»
supportingNeedlines
Needline
NestedConnectorEnd
role connectionContext
«metaclass»StructuredClassifier
1
ownedC
onnector
*
1en
d*
realizingConnector
«metaclass»Activity
«extends»OperationalActivity
NodeHasBehavior
conductedAt
1
*
activityConducted
1
*
«metaclass»NamedElement
supplier
1..*
*
client
1..*
*
NAF Metamodel
• IterativeExchanges– Repetitivetransferuntilagreement
• Informationflowsbothdirections– Additive/corrective
• Informationissplitintopublic(exchangedwithpartner)andprivate(internaldialog/additionaldata)
• Controlledbyprocessoneachside
CommonThemes
• Automations• DataFormat• Process
CommonPains
• Everythingismanual– Dataselection– Exporting– Transferring– Explaining– Importing
• Periodic,human-intensivemeetings
Automations
TheCostofManualEffort
• Lackoftimelyinformation• Introductionoferrors• Lackoftraceability• Lackofconsistencyacrossprojects
DrawbackwithManualExchanges
• Broadercommunication• Completeindependenceofpartnertooling
AdvantageswithManualExchanges
• Needconsistentdataformatsbetweenpartners– Forcebothsidestousethesametool
• Forcebothsidestousesameversionofthesametool– DOORSArchive/Restore
– Relyonexchangestandards• Standardsevolve• Standardsarenotimplementedconsistently• Standardsrarelyincorporateprocess
DataFormats
• PDF’s• Word/Excel
LowestCommonDenominatorAlwaysWins
• ReqIF– Wide-spreadindustryadoption– Littleevolutionbetweenversions
• Facilitatesconsistencybetweenvendorimplementations
– Open-sourceimplementation– Includesprocess!
• STEPAP233• Word
DataFormats– Requirements
ReqIF
• Excel• XML• ASAMISSUE• DaimlerDanTe
• Stillneedtoimport/exportfrominternaldevelopmentdefecttrackers
DataFormats- Defects
• UML,CAD,STEP• Litteredwithissues
– Non-standardimplementationacrosstools– Referencestounavailableresources(internalprofilesorlibraries)
– Lossyexchangeformats• UML:Nodiagrams
DataFormats- Models
• Threeprocessesneedtobeconsidered– Ownerprocess– ExchangeProcess– PartnerProcess
• EachPartnerhasinternalandpublicprocess– Needtomapprivateprocesstopublicprocess
Process
MappingProcess
Internal External
ProposedArchitecture
DefectTracking(Supplier)
DefectTracking(OEM)
DefectTracking(Shared)
StagesastheProcess
DriverandTTSync
Configurer
TasktopSyncgivesinstantvisibility
Intelligentqueriesonlyupdatedefectswhenappropriate,andonlypublish allowedinformation
ExchangeMaturityLevel
0.NoExchanges
1.ManualExchangeofDefects,Requirements
2.AutomaticExchangeofDefects,Requirements
3.ModelExchange
TheFutureofExchanges
OEM Supplier
Present
Afewnarrow,latedesign,developmentexchanges
TheFutureofExchanges
OEM Supplier
Future
Earlyconcepttopost-productionexchanges
• Simpledatabaserecordsaren’tenough
TheFutureofExchanges
• Advancedconceptswillrequiresupplierexpertise– Earlydeliveryoffunctionalmodels– Increasingmodelfidelityforperformanceanalysis– Real-timedataanalytics
• Codewillnotlongerbethedeliverable
TheFutureofExchanges
• Mostcomplexartifacttoexchange– Howtolimitvisibilitytoparts?– Whattodowithdanglingreferences?– Howtoresolveconflicts?
ModelExchange
• Divideyourmodels– Differentteamsshouldowndifferentparts
StrategiesForModelExchange
OwnerA
OwnerB
OwnerC
• Exposeaslittleaspossible– Eachownershouldexplicitlyexposeelementsforotherstouse
StrategiesForModelExchange
PrivateElements
PublicElements
• Controldependencies– Two-waybad,one-waygood
StrategiesForModelExchange
• Heterogeneousengineeringtoolset(tools,versionoftoolsandtheircustomizations)existsinsideorganizationandtheirpartners
• SEactivitiesforsharing,traceabilityandcollaborationonarchitecturesrequirescomplexeffortsinthiscontext– Export(Documents,HTML)– Reviewsgatheredusingmails,Document
(PDF/Word)commentsorExcelsheets– Manytools,licenses,customworkbench
settings– Needtotrainreviewersondesign/req.
tools
• Weworkoncapabilitiestosimplify/enhancecollaborationinthiscontext
CollaborativeModelSharing
DOORSRTC
Simulink Rhapsody
MyVirtualCatalogof« engineering »data
EA
MEGA
SA
Unlockdomains/teamssilostoshareengineering knowledge insideanorganization
• DataarepublishedinthecontextofCMprojectsenablingauthorstoaggregaterequiredinformationforaspecificcontextandlinkfeedbackswiththechangemanagementenvironment
PublishingandReviewingWorkflows
Authors
Stakeholders/Reviewers
AssociateCMProject
PublishData
CreateReview
Reviewandprovidecomments
FeedbacklinkedtoCMsystem
CM
Requirements
Architectures
GetYourDatatoWhereitisNeededDataIntegration
• Provingaccesstomodel information acrossorganizationalboundaries allowsmanagerstogatherefficientstakeholderfeedback
6/23/1645
Web-basedpublish/feedbackcollaborationplatformfortheFrenchMinistryofDefense(DGA)
Requirements
DesignData
Architectures
Classification&Transformation
publishreview
publish
review
publish
SE-Collab
• SE-CollabConnectivity– ConnecttomainSEtoolsusedbyDGA
• ConnectorsonvariousSEtoolscanbepluggedontheplatformtoextractdataanddiagrams.
• Newextensionscanbedevelopedtoaddothertools
– Handle« neutral »dataextractedfromthevarioustoolsincludingdiagramsformodeling
• OSLCAMOntologyusedtexposeanykindofdatatoextrenalsystems
– Categorizeandorganizedata
• SE-CollabReviewCapability– OurconnectorsenablesextractionofdataAND
diagramsallowingvisualreviewsofdata,conformingnativetoolnavigationorspecificone
– Oneuniquewebinterfaceforalltheusers– Reviewstakeholdersdonotneeddesktop
clientsorreviewerswebaccess
SECollaborativeSolutions
DataAccess
WebViews
CollaborativeReviews
Categorize&Organize
HeterogenousToolsetSupport
SE-Collab
• SECollabhelpsextendedteammemberstoshareandreviewtheirmodelingorrequirementworkpublishedfromheterogeneousengineeringtoolset.Itconnectsauthors,reviewers,andstakeholdersonawebplatform.
• Itprovidescapabilitiesthatallowgraphicallycommentingmodelsinsteadofprovidingjusttextualfeedback.
• ItcansupportadvancedreviewworkflowswithitsoptionalintegrationwithChangeManagement(CM)system.
Shareandreviewmodels
SE Authors(Desktop Tools)
Reviewers(Web)
PROVIDE CONTENTS
PROVIDE FEEDBACK
2modesforsharingdataPublisher toselectdatatoshare AUTHORING
AREA
HTTPS
Archive
Connectedordisconnectedmodeallowdifferentmodeaccordingnetworkcontinuityconfigurations
Archive
REVIEWAREA
«MyToolSet »
CMSystem
OptionalLink
• Amaindashboardperproject
WebPortalContent(1/6)
We share DesignsWe contribute toReviews
We can see lastComments
Dataarestored intocontainerProjects
WebPortalContent(2/6)Datacan be navigatedwith customCategories
Diagrams areimportedwith activeDiagramAreas
NavigableLinksamongthewhole design
WebPortalContent(3/6)« Text »Datacanbenavigated with TableViews (here DOORSrequirements)
WebPortalContent(4/6)
AReviewdefinesContributorsandResources
Collaborationwith theconfigured external CMSystem(OSLCCM)
WebPortalContent(5/6)
CollaborativeDiscussionsonDesignitems
Graphical AnnotationsonDiagrams
WebPortalContent(6/6)
Reviews can beexported asReports
ArchitectureOverview
Newconnector
• FullHTTPS/REST,RDF+OSLCImplementation (Open-Services forLifeCycleCollaboration)• ConnectorExtensibility/WebUINavigationCustomization• Repositories
• RTCRepository(atDGA)• StandaloneApacheJenaRepository
• AddLinksbetweenartifactsbycontentanalysis(e.gDOORS/MEGA/SALinks)
ApacheJenaRepository
Extensibility
RDF/SparqlManager
• Duringdesign,thedataexchangedbetweenpartnersthroughoutexternalinterfacesofasystemaredescribedbyasetofXMLfiles– TheyhavetobeintegratedintheSysMLmodelsmanually.– ImpactAnalysisforeachiterationstepiscomplextohandle.
XMLandSysMLSync
Librariesof“technical”types
Partner1
Partner2
Integrator
ModelComplexity
TimeConsuming
ManualErrors
N+1versions
• IntegrationofXMLdataandassistancetoiterations
SysML&XML-BasedToolingInteroperability
Librariesoftypes
OEM1
OEM2
Demande_Prise_Vue«Block»
Parts
Angle_Prise_Vue:AngleTypeClient:ClientTypeID:IntPosition_Prise_Vue:AngleType
Demande_Image«Block»
Parts
Angle_Image:AngleTypeID:IntPosition_Image:PositionType
itsRechercheImgExistante:RechercheImgExistante1
Operations
Consultation_Catalogue():void
Image:Image_Type
Demande_Prise_Vue:Demande_Prise_Vue
Demande_Image:Demande_Image
itsCatalogue:Catalogue1
Operations
Reception():void
Image:Image_Type
«flow»
Image
Demande_Image:Demande_Image
«flow»
Demande_Image:Demande_Image_Type
itsClient:Client1
Operations
Elaborer_Demande_Prise_Vue():void
Demande_Prise_Vue:Demande_Prise_Vue
«flow»
Demande_Prise_Vue
DirectImpact
SuspectedImpact
Useofspecificimporteddatatypes
Impactanalysiswhenimportinganewversionofdatatypeslibraries
SysML&XMLImpactAnalysis
Import/ExportXMLFormats
Analyze themodelaccording domain rules
ManageIterations
v1 v2
• Processdriveseverything• Exchangeswillincreaseincomplexity• Exchangeswillincreaseinfrequency• Modelswillruletheworld
Conclusion
