Top Banner
Teamcenter Systems Engineering Barbara Sheeley Matthew McEmber Systems Engineer The Boeing Company July 29, 2009
21
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
  • Teamcenter Systems Engineering

    Barbara SheeleyMatthew McEmberSystems EngineerThe Boeing CompanyJuly 29, 2009

  • Teamcenter System EngineeringTailored Systems Engineering Tool SuiteManage ArtifactsIntegrated Single Source of DataScalableCustomizable

  • Teamcenter Systems EngineeringSystems EngineeringFeatures & UILive Demo

  • Content PaneNotebook PaneNavigation PaneUser Interface

  • Basic TcSE EntitiesProject Root collection of FoldersBuilding Block Basic object used to decompose designRequirement Uniquely identifiable RequirementParagraph Type of Requirement for preserving document structure as a placeholderLink 1 to 1 directional relationship between two entitiesConnection Physical connection between two physical objectsFolder Container for other objectsDocument Type of folder that may contain Requirements, Paragraphs, and Building BlocksProperty Attribute of an entity (color, bit rate, prime engineer, etc)Diagram Visio Diagram attached to an object

  • Sharing a Single Source of Data

    Document

    Document

  • Focus on Data, Generate Views

  • Great Potential for Entity ReuseSource: Siemens DoDAF Module User Manual

  • Systems EngineeringPhysical modelsRequirementsFunctional Architecture(What Has to Be Done)Physical Architecture(How It Is Implemented)One Architecture multiple views captured and linkedLogical Architecture(How It Is Done)

  • Which Data Would You Prefer to Work With?B: Partitioned, Integrated Architectures?A: Mixed, Integrated Architectures?Horizontal Integration Across ArchitecturesVertical Integration Within Architectures

    V.P.

    V.P.

  • Requirements AllocationIntegrated RequirementsSearch Result: Requirements Allocation to Functions and Logical Systems

  • DoDAF Operational-System ArchitecturesOV-2Operational Node ArchitectureOV-5Activity ArchitectureSystem Function ArchitectureSV-4a

  • DoDAF Software ArchitecturesDoDAF Activity ArchitectureRhapsody Use Case Architecture (in TcSE)Use Case Diagram(Rhapsody / Sparx EA)Functional DecompositionIDEF 0 DiagramActivity Diagram(Rhapsody / Sparx EA)

  • Create Ancillary Architectural ViewsSpatialEnvironmental ThreatsManufacturing CellsSuppliersCountries of Originetc

  • System VerificationSpec. Search ResultsExcel Live Test VerificationLive-link back to problem RequirementEnter Verification Status

  • Operational Connectivity Model with Product OverlaySource: Siemens DoDAF Module User Manual

  • System Connectivity Model with Product OverlaySource: Siemens DoDAF Module User Manual

  • Operational to System Connectivity Model with Product Overlay

    Source: Siemens DoDAF Module User Manual

  • Live Demo

  • AcknowledgementsThis presentation would not have been possible without the contributions of:John HerroldRobert Malone