New York University Systems Simulations Engineering Management Discussion

User Generated

ghexvn88

Engineering

New York University

Description

Read Chapter 1

Select two of the System Engineering Methods/Concepts 

Define them, Provide examples in the industry in which they can be used, Explain pros and cons and differences. 

IN YOUR OWN WORDS.  I uploaded the slide and the syllabus of Systems Simulation. 

Unformatted Attachment Preview

The Engineering Design of Systems: Models and Methods 3rd Edition Chapter 1- Overview of the Engineering of Systems Chapter 1- Overview of the Engineering of Systems 1 System Life Cycle Identification of Need Production & Manufacturing Concept Definition Retirement Training Preliminary System Design System Integration Deployment Operation Maintenance Detailed Configuration Item Design Refinement Time Chapter 1- Overview of the Engineering of Systems 2 Cost 100% Cost Committed 80% Cost Incurred 60% 40% Reason Why Engineering a System Needs To Be Done Well Early 20% 0% Conceptual Detailed & Preliminary Design & Design Integration Construction or Production Chapter 1- Overview of the Engineering of Systems Use, Refinement & Disposal Time 3 Definitions of Systems Engineering Chapter 1- Overview of the Engineering of Systems 4 Vee Model of Design and Integration Understand User Requirements, Develop System Concept and Validation Plan Demonstrate and Validate System to User Validation Plan Integrate System and Perform System Verification to Performance Specifications Develop System Performance Specification and System Validation Plan . . . . . . Expand Performance Specifications into CI “Design-to” Specifications and CI Verification Plan Assemble CIs and Perform CI Verification to CI “Design-to” Specifications Systems Engineering Evolve “Design-to” Specifications into “Build-to” Documentation and Inspection Plan Time Inspect “Build-to” Documentation Design Engineering Fab, Assemble and Code to “Build-to” Documentation Chapter 1- Overview of the Engineering of Systems 5 Vee Model with Onion Peels Understand User Requirements, Develop System Concept and Validation Plan Demonstrate and Validate System to User Validation Plan Integrate System and Perform System Verification to Performance Specifications Develop System Performance Specification and System Validation Plan . . . Expand Performance Specifications into CI “Design-to” Specifications and CI Verification Plan Evolve “Design-to” Specifications into “Build-to” Documentation and Inspection Plan . . . Peels of the Onion Assemble CIs and Perform CI Verification to CI “Design-to” Specifications Systems Engineering Design Engineering Inspect “Build-to” Documentation Fab, Assemble and Code to “Build-to” Chapter 1- Overview of the Engineering of Systems Documentation Time 6 Race Car Example of Requirements and Tests Operational Need or Mission Requirements Partially Validated by Operational Test (Proven by Real-World Experience) System Level Requirements Verified by System-Level Tests Component Level Requirements Verified by ComponentLevel Tests Win the Indianapolis 500 • Pretrial average speed of 215 mph • Average speed in the 500 of 190 mph • Top speed of X mph · • Acceleratio n in all directions, g-g space • Average standard pit time of Y seconds • Engine horsepower of x Btu • Body’s drag coefficient of y • Range per tank of gas of z miles “g-g” Design Region for a Racecar (from [Milliken and Milliken, 1995]) Chapter 1- Overview of the Engineering of Systems 7 Expertise Required on the Systems Engineering Team Management Domain/ Stakeholders SE Process Technology (Engineering Disciplines) Modeling, Simulation, Analysis Chapter 1- Overview of the Engineering of Systems 8 Top Down Systems Engineering (TTDSE) System Definition System V,V &A n sig ion De at m eriv n ste D itio Sy nts efin e D A V& em e V, quir ctur Re hite c Ar Subsystem Definition Component Definition CI Definition Subsystem Verification Component Verification CI Verification Discipline Engineering Design Chapter 1- Overview of the Engineering of Systems System analysis; Upgrade selection V, V Re &A T Ar quire esti ch n ite men g ctu t re s Ad Mo jus tm dif ica en tio t n Meta-system analysis; Concept selection 9 Systems Requirements Waterfall Model Software Requirements Preliminary Design Detailed Design Coding and Debugging Integration and Testing Chapter 1- Overview of the Engineering of Systems Operations and 10 Maintenance Spiral Model Cumulative Cost Progress through phases Evaluate Alternatives; Identify and Resolve Risks Determine Objectives, Alternatives, and Constraints Risk Analysis Risk Analysis Risk Analysis Review Commitment Partition Operational 3rd 2nd 1st Prototype Prototype Prototype Prototype Models RequirementsOperational Simulations Benchmarks Plan Concept Software Requirements Detailed Development Software Design Requirements Plan Product Validation Design Code Integration Design Validation and Test Plan Unit Test and Verification Integration and Test Plan Next Acceptance Phases Test Develop and Verify Implementation Next Level Product Chapter 1- Overview of the Engineering of Systems 11 Modeling Approaches • Structured design • • • • N2 Diagrams (or charts) IDEF0 Data flow diagrams Petri nets • Unified Modeling Language (S/W eng’g) • US Dept. of Defense Architecture Framework (DODAF) • Systems Modeling Language (SysML) Chapter 1- Overview of the Engineering of Systems 12 UML Diagram Types Structure Diagrams Class Component Composite structure Deployment Object Package Behavior Diagrams Activity State Machine Use case Chapter 1- Overview of the Engineering of Systems Interaction Diagrams Collaboration Communication Interaction overview Sequence diagram Timing 13 Diagram Types for SysML Structure Diagrams Class – renamed to be Block Definition Internal Block Component Composite structure Deployment Object Package Parametric Design (new) Behavior Diagrams Activity (modified) State Machine Use case Chapter 1- Overview of the Engineering of Systems Interaction Diagrams Collaboration Communication Interaction overview Sequence diagram Timing Requirement (new) Requirement (new) 14 SE Architectures Operational Concept Functional Architecture Physical Architecture Allocated Architecture Chapter 1- Overview of the Engineering of Systems Interface Architecture 15 Sample Physical Architecture F-22 Weapon System Vehicle Avionics Systems Utilities & Subsystems Cockpit Systems Chapter 1- Overview of the Engineering of Systems Electronic Warfare Vehicle Management System Controls & Displays Navigation, Identification Radar Support Training Processing Inertial Reference System 16 Stores Management Life-Cycle Physical Architecture XYZ Weapon System Operational System Manufacturing System Design & Integration System Avionics Systems Deployment System Training System Utilities & Subsystems Electronic Warfare Refinement System Cockpit Systems Vehicle Management System Controls & Displays Navigation, Identification Radar Retirement System Processing Chapter 1- Overview of the Engineering of Systems Inertial Reference System Stores Management 17 Another View of the Design Process Stakeholders’ Need Stakeholders’ Requirement System Design System Allocated Architecture Segment Specs Segment Design Element Design Component Design Segment Allocated Architectures Element Specs Element Allocated Architectures Component Specs Chapter 1- Overview of the Engineering of Systems Component Allocated Architectures CI Specs 18 Document Contents • Definition of stakeholders and their relationships • Stakeholders’ description of the problem and its context • Description of the current system • Description of major objectives in general terms • Definition of the systems engineering management structure and support tools that will be responsible for developing the system Stakeholders’ Need or • Definition of the problem needing solution by the system Stakeholders’ (including the context and external systems with which Requirement the system must interact) (StkhldrsRD) • Definition of the operational concept on which the system will be based • Creation of the structure for defining requirements • Description of the requirements in the stakeholders’ language in great breadth but little depth • Trace of every requirement to a recorded statement or opinion of the stakeholders • Description of trade-offs between performance requirements, including cost and operational effectiveness System Requirements • Restatement of the operational concept on which the (SysRD) system will be based • Definition of the external systems in engineering terms • Restatement of the operational requirements in engineering language • Trace of every requirement to the previous document • Justification of engineering version of the requirements in terms of analyses, expert opinions, stakeholder meetings • Description of test plan for each requirement System Requirements • Documents analyses to show that the requirements in the Validation SysRD are consistent, complete and correct, to the degree possible Chapter 1- Overview of the Engineering of Systems 19 • Demonstrates that there is at least one feasible solution to the design problem as defined in the SysRD Typical Requirements Documents Document Titles Problem Situation or Mission Element Need Statement and Systems Engineering Management Plan (SEMP) Development Period Stakeholders Guidance & Approv als Documents & Money Develop System ABC Design & Integration Documents People & Tools Dev elopment System Chapter 1- Overview of the Engineering of Systems 20 Period of Pre-Initial Operational Capability Stakeholders Spe cifications Guidance & Approvals Docum e nts & M one y M anufacture System ABC Deploy System ABC Deve lop System ABC Docum e nts M anufacture d, De ploye d & Te s te d Ite m s Pe ople & Tools De ve lopm e nt Syste m Train O/M of System ABC Facilitie s , People, & Equipm e nt M anufacturing Syste m Chapter 1- Overview of the Engineering of Systems Training De ploym e nt Syste m Syste m 21 Period of Operational Use and Refinement Stakeholders Guidance & Approvals Spe cifications Docum e nts & M one y Refine System ABC M anufacture System ABC M anufacture d Ite m s Facilitie s , People, & Equipm e nt Training Ite m s Deploy System ABC Ne e ds De ployed Item s Use System ABC Train O/M of System ABC M anufacturing Syste m Docum e nts Traine d O/M Facilitie s , People, & Equipm e nt De ploym e nt Syste m Training Syste m Chapter 1- Overview of the Engineering of Systems Pe ople & Tools Re fine m e nt Syste m 22 Retirement Period Stakeholders Specifications Needs Use System ABC Decom missioned ABC’s Laws & Regulations Deploy System ABC ABC Transported, Decom missioned ABC’s Retire System ABC People & Tools W aste Materials People & Tools Deployment System Chapter 1- Overview of the Engineering of Systems Retirement System 23 Strategic Check 5 Cycle Model Design and Integration Cycles 1. Core cycle: Realization of stakeholder needs, followed by requirements development, design, manufacturing and product delivery 2. Verification cycle: Analysis, simulation, prototyping, integration, and testing Contol Document Controlling Cycles Prof itability? Feasibility? Eff ort? Risks? 4 Translation of Requirements into Abstract Specs Determination of Customer Desire Verification Cycles Improvement of Technologies & External Resources Contol Document 1 Modeling form, function Management Cycles fit, function CUSTOM ER 3. Technologies and external 2 resources cycle: Insertion of Pilot Tests the appropriate technologies form, fit, function and resources into the Delivery systems engineering process & Sales 4. Controlling cycle: 1 Configuration management of Realization the design process and multiple product releases and updates 5. Strategic check cycle: Management assessment and approval of product Chapter 1- Overview of the Engineering of Systems development Prototyping 3 Creation of Abstract Solution Coordination of External Resources Translation into Manuf acturable Solution 3 Order Processing Contol Document 24 Define the Design Problem Five Major Functions of Systems Engineering Design Develop Functional Architecture Design Physical Architecture Develop Allocated Architecture Chapter 1- Overview of the Engineering of Systems 25 Obtain Approval & Document Detailed Functions of Systems Engineering Design Develop Functional Architecture Higher Level Requirements & Constraints from Approved Baseline Define the Design Problem Define the problem, the system/segment/CI Boundary, & the objectives Develop the Op’l Concept for the Sys,Seg,CI under analysis no Define the required behavior in a functional interaction diagram Develop Physical Architecture Define candidate physical solutions Allocate requirements to functions Define the required functional performance by quantitative analysis Evaluate candidate physical solutions & select best based upon objectives & requirements Obtain Approval & Document Document Seg/CI design as approved baseline for next lowest level Obtain approval of boundary, yes Develop Allocated Architecture objectives, Chapter 1- Overview concept of ops, of the Engineering of Systems Plan test Develop requirements, & integration interfaces physical solution, of Seg/CIs between & test plan Seg/CIs 26 Allocate functions to Seg/CIs Functions of the Systems Engineering Integration Process Verification Requirements and Constraints from Approved Baseline CI to be verified Inspect and test to verification requirements to prove readiness for integration with next assembly Integrate with next CI and repeat verification process No Deficiencies Yes Identify and fix correctable deficiencies Yes Modify approved technical baseline to incorporate deviation Correctable No Yes Document uncorrectable deficiencies Chapter 1- Overview of the Engineering of Systems Redesign No For uncorrectable deficiencies, confirm 27 no impact to integration and get deviation approval from buyer Integrated Process for the Product System and Its Qualification System Chapter 1- Overview of the Engineering of Systems 28 • • • • • • • • • • • Types of Systems natural vs. man-made closed vs. open static vs. dynamic simple vs. complex reactive vs. non-reactive precedented vs. unprecedented safety-critical vs. not safety-critical high reliability vs. not high reliability high precision vs. not high precision human-centric vs. non-human high durability vs. not high durability Chapter 1- Overview of the Engineering of Systems 29 Systems Classification Major Process or Operand Major Output Energy Information Matter Transform or Manufacturing Power Plant Process Plant Package Transport or Power Grid Delivery Distribute System Company Store or Dam Dam House Internet Exchange or Auction Energy Market Trade Company Control or Regulate Health Care Company Computer Chip Mint Telecommunication Network Banking Network Public Library Bank News Agency Stock Trading Market International Energy Agency Standards Organization Chapter 1- Overview of the Engineering of Systems Value Monetary Regulator 30 Value of Systems Engineering Value propositions 1. Problem and solution discovery – goal seeking system 2. Communication interface between stakeholders & design engineers 3. Identify and solve show stoppers 4. Error reduction in both the design and product systems 5. Risk reduction of both the design and product systems Chapter 1- Overview of the Engineering of Systems 31 Course Description This course will provide an understanding of simulation methods for the analysis and design of various types of systems. Queueing theory, queueing problems and stochastic systems are simulated using GPSS. Problems and stochastic systems are simulated using GPSS. Continuous and other discrete simulation languages will be discussed. Textbooks: The Engineering Design of Systems: Models and Methods (Wiley Series in Systems Engineering and Management) 3rd Edition Pearson Publishing Publisher: Wiley; 3 edition (February 29, 2016) ISBN-10: 111902790X ISBN-13: 978-1119027904 Course Objective Take a model-based approach to introduce key systems engineering design activities and introduces methods and models used in the real world. This book is divided into three major parts: (1) Introduction, Overview and Basic Knowledge, (2) Design and Integration Topics, (3) Supplemental Topics. The first part introduces the issues associated with the engineering of a system. The second part covers the critical material required to understand the major elements needed in the engineering design of any system: requirements, architectures (functional, physical, and allocated), interfaces, and qualification. The final part reviews methods for data, process, and behavior modeling, decision analysis, system science and analytics, and the value of systems engineering. Chapter 1 has been rewritten to integrate the new chapters and updates were made throughout the original chapters.
Purchase answer to see full attachment
Explanation & Answer:
4 pages
User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.

Explanation & Answer

Attached.

Running Head: SYSTEM SIMULATIONS

1

SYSTEM SIMULATIONS
Student’s Name
Institution
Date

SYSTEM SIMULATIONS

2

The waterfall model of software engineering and it's defined as the method that uses
sequential evolution of life cycles of a system. The advantage of using the software, it's easy to
monitor the processes while disadvantage lies on its ability to allow interaction between the
adjacent phases.
The spiral model of software engineering and it's defined as a risky way of developing
software. The advantages include its ability to run large projects, secure approvals and control of
the documents. The disadvantage consists of, it requires people with experience to use, and it's
not suitable for little risks (The Engineering Design of Systems, 2016).
The differences between the two models include;
1. Waterfall model it's a linear method to develop software while the spiral model it's a risk
driven method.
2. Waterfall allows minimum customer interaction compared to the Spiral model that enable
customers to be part of the process.
3. Waterfall models, it's simple and easy while spiral it's very complicated.

Introduction
A system refers to where hardware, software, tools, people, procedures work together to
achieve the same goal after some time. The people in charge of any organization should take care
of the objectives and ensure that they work correctly to their best. Having in mind that each
group approached it's only a subsystem under a more significant or more extensive system. The
stakeholders make objectives if their team, it's the work of engineers to implement and make
sure that all the desires achieved. Through observation, engineers identify the best procedure,
cheap, and that consumes a lesser period to accomplish the objectives. The significant attraction

SYSTEM SIMULATIONS

3

of the engineers can get termed as ensuring that the life cycle of the system con...


Anonymous
Excellent resource! Really helped me get the gist of things.

Studypool
4.7
Trustpilot
4.5
Sitejabber
4.4

Related Tags