Mind Map 2.pdf Mind Map
 
 
 
 

Mind Map 2.pdf - Mind Map

1 years ago by: Ryan Brown
 
 
  • Transition From Tradition SE to MBSE
    • Advantages
      • Traditional SE
        • Established/knowledge
        • Common understanding
          • Idea
        • Industry wide usage
      • MBSE
        • Improved communication
          • Stakeholders
          • Customers
          • Internal
          • Common language tool
        • Unified representation of the system
        • Increased details
        • Traceability
        • Harmonized activies
        • Better relationships between stakeholders, internal organizations, and impacts related entities
        • Unified representation of the system
        • High level of detail for projects
        • Common language tool
    • Disadvantages
      • Tradition SE
        • Unused applications
        • Systems becoming complex/capability hinders
        • Systems support too many unused applications that can exceed 20% of a company's budget
        • Unable to perform "what-if" scenarios efficiently
        • Unable to see full effect of changes
        • Capability hinders as systems increase in complexity
          • Future project unsuitable
        • Risk missing the flow down from higher level sources
      • MBSE
        • Transition
        • Cost
        • Loss of investments
        • Complicated transition
        • Loss of intellectual and financial investments
        • Extensive upfront costs
      • Fallout
        • Multifaceted business
        • Social
        • Organizational issues
        • Financial budgets
        • Common understanding
    • Effects
      • Financial budget
        • Save up to 68% annually
        • 55% reduction in development costs
      • Common understanding
        • Common language
          • Stakeholders
          • Customers
          • Internal
        • Requirement understanding with customer is mutual
          • Customer
          • Idea
      • Quality
        • Ease of monitoring system development
        • Requirement tracking
      • Personnel
        • Engineers
          • Increase in design ability
          • Facilitating understanding
          • Aiding in decision making ("what-if" scenarios)
          • Explains, controls, and predicts evens (how)
          • Complex systems requirements efficient and highly-capable systems engineering
          • More competitive project bids
        • Stakeholders
          • Decrease in project costs
        • Customers
          • Increase in project flexibility
            • Able to get more "wants" out of a project
    • System Life Cycle
      • Con Ops
        • SOW, strategies, policies
        • Initialize models
      • Requirements
        • Requirements using MBSE software
        • Increased communication and understanding
        • Traceability
      • Design
        • Increased user abilities
        • Linking design to requirements by models
      • Integration/Test/Verification/Validation
        • Linkage to requirements
          • Idea
        • Improved integration
      • Operation and Maintenance
        • Maintenance models
          • Idea
        • Operation models
    • Risks
      • Personnel
        • Commitment
        • Time to learn
      • Developmental
        • Cost
        • Learn new system
      • Functional
        • Loss of documentation
        • MBSE software
        • Loss of Legacy Functionality
Report abuse
More Maps by This User