Moody F061 ISE 491 - 2 Conceptual System Design “Sets the Stage” State the problem Identify the need Conduct advanced system planning & feasibility analysis.

Slides:



Advertisements
Similar presentations
UJTL Ontology Effort TMCM Nelson And Marti Hall. Overview Vision for the UJTL and METLs Scenario Mapping Findings Proposed POA&M outline.
Advertisements

Welcome to SMMs Presentation offering a synopsis of our Emergency Response Service on a 24 Hour basis PRESS RIGHT MOUSE CLICK IF YOU WANT TO MOVE BACK.
Presentation to 2013 NA OmegaPS UGM Chris Mair General Manager - PSSL ILS Standards in Europe + UK !
Machine Elements in Mechanical Design. Introduction Mechanical Systems or Devices are designed to transmit power and accomplish specific patterns of motion.
James Ngeru Industrial and System Engineering
1 The Role of the Revised IEEE Standard Dictionary of Measures of the Software Aspects of Dependability in Software Acquisition Dr. Norman F. Schneidewind.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
BSAD 102 Mike’s Bikes Business Simulation
P09233 Flight Parameter Measurements Michael Skube & James Hunt P09233
P09233 Flight Parameter Measurements Michael Skube P09233
1 California State University, Fullerton Chapter 13 Developing and Managing Information Systems.
Software Requirements
System Implementations American corporations spend about $300 Billion a year on software implementation/upgrade projects.
1 Introduction to System Engineering G. Nacouzi ME 155B.
Overview of Software Requirements
Lead Black Slide. © 2001 Business & Information Systems 2/e2 Chapter 13 Developing and Managing Information Systems.
Systems Engineering Management
TECH 101 Product Design and Manufacturing. TECH 1012 System Life-Cycle Engineering 2 Major phases in almost all products and in many cases services –Acquisition.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
System Implementations American corporations spend about $300 Billion a year on software implementation/upgrade projects.
IE 412: Industrial Facilities Design Prerequisites: Work Study and Methods Engineering, Production Planning and Control Objective: To enable the students.
Dr. Muzaffer Kapanoğlu - Decision Support Systems © 2003 MATERIAL HANDLING (Textbook Chapter 5)
P RODUCT D ESIGN AND D EVELOPMENT Chapter 1 & 2 Development Process and Organization.
5-1 McGraw-Hill/Irwin Copyright © 2010 by The McGraw-Hill Companies, Inc. All rights reserved.
SYSTEM ANALYSIS AND DESIGN
Continuation From Chapter From Chapter 1
Role and Components of Project Evaluation
SUBJECT  Industrial facility design. GROUP MEMBERS H.Hammad Ali 11-IE-32 S.Hammad shah 11-IE-21 Hammad Hassan 11-IE-41.
1 Writing Effective Critical Elements Using the SMART or MARST Formats.
Introduction to Software Quality Assurance (SQA)
Server Virtualization: Navy Network Operations Centers
Quality Function Deployment
Database Design - Lecture 1
Profile and a quick introduction Software Engineering: ) هندسة البرمجيات (in Arabic: is the branch of computer science Designed to develop a set rules.
Chapter 7: The 30 elements of systems engineering
ShopKeeper was designed from the ground up to manage your entire fleet maintenance operations … from 1 user to 100, including full security features that.
Requirements Analysis
Ways for Improvement of Validity of Qualifications PHARE TVET RO2006/ Training and Advice for Further Development of the TVET.
Chapter 16 Structured Systems Analysis. Learning Objectives Know goals, plans, tasks, tools, & results of systems analysis Understand/appreciate costs.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
Planning in production systems Slovak University of Technology Faculty of Material Science and Technology in Trnava.
Chapter 7: A Summary of Tools Focus: This chapter outlines all the customer-driven project management tools and techniques and provides recommendations.
Database System Development Lifecycle 1.  Main components of the Infn System  What is Database System Development Life Cycle (DSDLC)  Phases of the.
Product and Service Design. 4-2 Major factors in design strategy – Cost – Quality – Time-to-market – Customer satisfaction – Competitive advantage Product.
University of Connecticut MECHANICAL ENGINEERING Project Statement.
CLIC Implementation Studies Ph. Lebrun & J. Osborne CERN CLIC Collaboration Meeting addressing the Work Packages CERN, 3-4 November 2011.
Chapter 13 Logistics and Channel Management. Logistics13 Objective 1: L ogistics Planning, implementing, and controlling the physical flows of materials.
Systems Engineering Conceptual System Design. Systems Engineering and Analysis, B.S. Blanchard and W. J. Fabrycky, 3 rd edition, Prentice-Hall, 1998.
Planning and Forecasting. Chapter Objectives Explain the needs for planning and analyze a planning model Be able to solve forecasting problems.
Programmatic issues to be studied in advance for the DEMO planning Date: February 2013 Place:Uji-campus, Kyoto Univ. Shinzaburo MATSUDA Kyoto Univ.
Chapter 6: THE EIGHT STEP PROCESS FOCUS: This chapter provides a description of the application of customer-driven project management.
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
Requirements engineering The process of establishing the services that the customer requires from a system and the constraints under which it operates.
Unit 6 Understanding and Implementing Crew Resource Management.
CHAPTER 2 CONCEPT OF ELECTRONIC COMMERCE. Why Should Companies Use Electronic Marketing  What is the purpose for engaging online communication?  Why.
Supply Chain Performance Measurement “The more you measure, the more you know!” M.Tariq Yousafzai Innovator and Business Creator (ILSCM)
EDGE™ Concept Level Project Plan P08210/11 – Ruggedization of a Data Recorder for a Forklift Truck Shadle Stewart ME Rick Chadwick ME.
Stracener_EMIS 7305/5305_Spr08_ Systems Availability Modeling & Analysis Dr. Jerrell T. Stracener, SAE Fellow Leadership in Engineering EMIS 7305/5305.
Chapter 3 Conceptual System Design
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
©2013 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part.
Website Development and Maintenance Is your Website losing your prospects to your competition?
ME Summer 2013 Systems Engineering, Part II Session July 2013 Mr. Larry Hopp, CPL.
Introduction to Project Management
Classifications of Software Requirements
Chapter 1 Cost control & cost reduction
CH5- SETTING GOALS AND OBJECTIVES, IDENTIFYING STRATEGIES AND TACTICS
Developing Information Systems
Facility Planning Systematics Process
Quick Set-Up Technique
Presentation transcript:

Moody F061 ISE Conceptual System Design “Sets the Stage” State the problem Identify the need Conduct advanced system planning & feasibility analysis Define program requirements Develop operational requirements Propose a maintenance & support concept Identify and prioritize technical performance measures Conduct a system-level functional analysis Perform a systems analysis Develop system specification Conduct a conceptual design review

Moody F062 ISE The first step is understanding the problem... Starts with recognizing that there is a broadly defined need or “want”  ex. 1: the Navy wants a new generation of combat ships that is capable of working closer to shore and to perform a variety of combat operations.  ex. 2: Mercer University needs to meet the growing needs of its science programs, as well as a growing school of engineering. Perform a needs analysis to turn this broad statement into specific system-level requirements.

Moody F063 ISE Needs analysis … growing science & engineering needs:  what functions must be performed to meet the needs? Which are primary and which are secondary? What must be accomplished to meet the need? When must this be accomplished? Where? How often and w/ what frequency?  NOTE: you’re concerned here with the “WHATs” and not the “HOWs”  This is a team effort, including the customer and also the ultimate user of the system  The result is a broad statement of the requirements of the system

Moody F064 ISE Needs analysis … growing science & engineering needs:

Moody F065 ISE Advanced System Planning What does the program need to do to bring the system into being? Key outputs (see figure 3.1, pg. 57)  Program Management Plan (PMP) necessary guidance for all program activities  Systems Engineering Management Plan (SEMP) requirements for implementing the systems engineering program concurrent with system specification  System specification (Type A) high level forms the basis for all lower level specifications

Moody F066 ISE Your turn … As a group, review the documents provided in class and answer the following:  What is the purpose of the PMP?  What are the key features of this PMP?  What is the purpose of the SEMP?  What are the key features of this SEMP?

Moody F067 ISE Conceptual System Design “Sets the Stage” State the problem Identify the need Conduct advanced system planning & feasibility analysis Define program requirements Develop operational requirements Propose a maintenance & support concept Identify and prioritize technical performance measures Conduct a system-level functional analysis Perform a systems analysis Develop system specification Conduct a conceptual design review

Moody F068 ISE System Feasibility Analysis What did you learn last week about determining system feasibility?

Moody F069 ISE System Operational Requirements What type and quantities of equipment, software, personnel, facilities, etc. requirements are anticipated? How is the system to be used, and for how long? What is the anticipated environment at each operational site (user location)? How is the system to be supported, by whom, & for how long?

Moody F0610 ISE Defining the Operational Concept (CONOPS) Example: Vertical Takeoff & Land Tactical Unmanned Aerial Vehicle (VTUAV)  (See examples in handout.)

Moody F0611 ISE ConOps Purpose Articulate VTUAV themes and highlight contributions that it brings to 21st Century naval operations Compressed target kill chain Precision targeting data to support GPS & laser guided munitions coupled with real time damage assessments Contribute to and receive from the “common relevant operational picture” (CROP) Better/improved situational awareness (SA) at all command levels Reliable over the horizon (OTH) command and control

Moody F0612 ISE Step 1: Mission definition Primary, secondary, and alternative missions What? and How? Scenarios, operational profiles may be used Identify dynamic characteristics Include maintenance & support definition

Moody F0613 ISE Step 2: Performance & physical parameters Defines the operating characteristics  size  weight  range  capacity  etc. How do these performance parameters relate to the mission scenarios?

Moody F0614 ISE Step 3: Operational deployment/distribution What’s going where? How much? When? Again, include maintenance & support Example: see figure 3.3, pg. 61, figure 3.5, pg. 63

Moody F0615 ISE Step 4: Operational life cycle How long will the system be in operation? What is the total inventory profile throughout? Who will be operating the system & for how long? Examples: figure 3.7, page 65, figure 3.9, page 66

Moody F0616 ISE Step 5: Utilization requirements How will this be used by the operator in the field? Anticipated usage  hours of operation  percentage of total capacity  operational cycles per month  facility loading Consider elements of the system as well as total system usage

Moody F0617 ISE Step 6: Effectiveness factors How will you determine that the system is efficient or effective? Specified as figures-of-merit (FOMs)  operational availability  mean time between maintenance (MTBM)  failure rate (λ)  operator skill levels & task accomplishment requirements  etc. How are these related to the mission scenarios?

Moody F0618 ISE Step 7: Environment What will the system be subjected to during operational use, and for how long?  temperature  humidity  airborne, ground, or shipboard  arctic or tropics  mountainous or flat  desktop or handheld  etc. Include all transportation, handling, & storage