Bill Fournier Nov 2014 Systems Engineer for Non SE Bill Fournier 202 255 0760.

Slides:



Advertisements
Similar presentations
Systems Engineering From a Life Cycle Perspective John Groenenboom Director Engineering – Mesa Boeing Rotorcraft Dec 12, 2007.
Advertisements

SEMP vs. PMP Conflict and Partnership
INCOSE Presentation San Francisco Chapter 13 October 2009 Mapping CMMI to Systems Engineering Adrienne Friedman.
College of Continuing Education Systems Engineering Non-credit Certificate.
S Y S T E M S E N G I N E E R I N G.
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
©2006 OLC 1 Process Management: The Foundation for Achieving Organizational Excellence Process Management Implementation Worldwide.
1 Software Requirement Analysis Deployment Package for the Basic Profile Version 0.1, January 11th 2008.
Stepan Potiyenko ISS Sr.SW Developer.
Chapter 1 The Systems Development Environment
1 Introduction to System Engineering G. Nacouzi ME 155B.
System-of-Systems Cost Modeling: COSOSIMO July 2005 Workshop Results Jo Ann Lane University of Southern California Center for Software Engineering.
Secure System Administration & Certification DITSCAP Manual (Chapter 6) Phase 4 Post Accreditation Stephen I. Khan Ted Chapman University of Tulsa Department.
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
Chapter 3: The Project Management Process Groups
PSU CS 106 Computing Fundamentals II Product Life Cycle & SW Product Life Cycle HM 9/3/2007.
Systems Engineering Management
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
BAE SYSTEMS Overview of Systems Engineering at BAE SYSTEMS & ALENIA MARCONI SYSTEMS 8/10/2015/MS By Leigh Watton Friday 27th July 2001.
Engineering Systems of.
SOFTWARE PRODUCTIVITY CONSORTIUM 1 Twelve Roles and Three Types of Systems Engineering Sarah A. Sheard Software Productivity Consortium February 11, 2003.
Chapter 2: Overview of Essentials ISE 443 / ETM 543 Fall 2013.
CMMI Course Summary CMMI course Module 9..
“Here’s why you need the new wheels, too…” Shawn and Steve Image from
Bill Golaz Greg Niemann October 22, 2013 Operations Analysis Workshop “Operational Analysis Measures for Program Start Up”
Standard WBS Version 1.0 WBS2-3.pptPage 1 Standard Work Breakdown Structure Legend = Decomposes to lower level WBS elements 4.0 Implementation 4.0 Implementation.
Chesapeake INCOSE Chapter meeting 20 March
PRODUCT STEWARDSHIP IMPLEMENTATION EXAMPLES AND TOOLS David Sandidge Director, Responsible Care American Chemistry Council May 31, 2011.
The Differences Between the Project Manager and the Systems Engineer Kasse Tim Kasse Kasse Initiatives LLC +1 – USA +49 (0)
From Research Prototype to Production
Rational Unified Process Fundamentals Module 4: Disciplines II.
Software System Engineering: A tutorial
1 Configuration Management “The Cookbook Approach”
Roles and Responsibilities
Engineering System Design
Best Systems Engineering Products Drive CMMI NDIA 6th Annual Systems Engineering Supportability & Interoperability Conference October 21, 2003 Dr. Tom.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
Chapter 12: Systems Investigation and Analysis. Agenda  How to Develop a CBIS?  Systems Development Life Cycle (SDLC)  Prototyping  Join Application.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.
Software Requirements Engineering: What, Why, Who, When, and How
SacProNet An Overview of Project Management Techniques.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Applying Business Process Re-engineering
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
© Mahindra Satyam 2009 Configuration Management QMS Training.
Assessing the influence on processes when evolving the software architecture By Larsson S, Wall A, Wallin P Parul Patel.
Software Engineering - I
DPE CSSW Process Model Annex A WP-400 ECSS Case Study.
1 | 2010 Lecture 3: Project processes. Covered in this lecture Project processes Project Planning (PP) Project Assessment & Control (PAC) Risk Management.
Requirements Development in CMMI
SOLUTION What kind of plan do we need? How will we know if the work is on track to be done? How quickly can we get this done? How long will this work take.
Software Engineering Lecture # 1.
SOFTWARE PROCESS IMPROVEMENT
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
1 Lecture 2.4a: SEF SE Planning and the SEP (SEF Ch 16) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
1 Lecture 2.3: SE Process (SEF Ch 3) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
SYSE 802 John D. McGregor Module 0 Session 3 Systems Engineering QuickView.
2012 Spring Simulation Interoperability Workshop
Applying Business Process Re-engineering
Development Projects / Analysis Projects / On-site Service Projects
INCOSE – North Texas Chapter
Request for Proposal (RFP)
Software Development Process
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
PSS verification and validation
Requirements Development in CMMI
Presentation transcript:

Bill Fournier Nov 2014 Systems Engineer for Non SE Bill Fournier

Agenda History/Value/Application Definitions Whom How-–Technical,(user) project (PM & PC) and Agreement(Contracts ), Tailoring, SpE CASE Job advertisement for SEs Recruiters Future References

History/Value/Application History- SE- Products, Processes, People- use, fix –Pyramids/Greek/Romans/Ren/ British Train/ Model T/ WW I tank –WW II- too much one person to detail design Value - % SE knee of curve for cost and schedule control Applicable –Government- user need document –Commercial- Marketing / focus groups –International –Services Bill Fournier

Definitions I Systems- Products, Processes and People & boundaries, Purpose 3 SE POVs – interdisciplinary, iterative, and recursive, way of thinking, feedback loops, top down and bottom up Requirements- Needs & technical requirements CONOPS- plans how use system Functions- verbs things systems must do to do mission Physical Architecture/Design- nouns products decomposed which expected to meet requirements and their interrelationships Implementation- Build & Code development system Integration- put subsystems and lower together Verification- Prove by Objective Evidence that the requirement has been met with the final configuration. TADI Validation- Assess we meet what user needed Test- method of assessing progress towards showing system works Production- Make final hardware built and coded in quantity Operation and Maintenance- use, maintain Disposal- retire/recycle Bill Fournier

Definitions II PM- Program/Project/Product Manager Configuration Management – Plan, ID, control, status, audit the technical baseline of system Trade Studies- analyze alternatives trades Technical /Design Reviews- decide if maturity worth going forward Risk/Issues- things could go wrong / have gone wrong TPMs- key early warning indicators of problems Acquirer- manager the development contract for the stakeholder Supplier- designs, builds/codes to meet contract(s) SpE- SE like specialties with narrower focus Bill Fournier

Whom EE IE OR ISE Technical PM Requirements Eng’g Designers Analyst Bill Fournier

Stages Exploratory Research Concept Development Production Utilization Support Retirement Bill Fournier

Technical Processes (Users) Stakeholder Req. Def. Inputs Req. Analysis Source Documents Arch. Design Stakeholder Needs Implementation Project Constraints Integration Verification Outputs Validation Balanced System Operation Maintenance Disposal Cross- Cutting Bill Fournier

Project Processes (PM & PC) Project Planning Project Assessment and Control Decision Making- Trade study Risk & Opportunity Management- Prob. & Impact Configuration Management Information Management Measurement- MOE/MOP/TPM Bill Fournier

Agreement Processes Bill Fournier Acquisition Supply

Tailoring Cost of formality Cost of Miss communications Reduce theoretical overall cost Bill Fournier

SpE Analysis Logistics- RAM… Cost effectiveness EMI Environmental Impact Interoperability LC cost Manf. and producability Safety & health hazard Sustainment Training needs Human factors Value Engineering Bill Fournier

CASE Computer Aided Systems Engineering How can computers help ? Bill Fournier

SE Job Advertising Table 1. Systems Engineering Roles Role Abbr. Short Name 1 RO Requirements Owner 2 SD System Designer 3 SA System Analyst 4 VV Validation/Verification Engr. 5 LO Logistics/Ops Engineer 6 G Glue Among Subsystems 7 CI Customer Interface 8 TM Technical Manager 9 IM Information Manager 10 PE Process Engineer 11 CO Coordinator 12 CA Classified Ads SE Bill Fournier

Future Software intensive Speed of Development Greater Specialization Recycle Systems Interfaces SE even greater value Bill Fournier

Processes Technical (User) Project (PM & PC) Contracting (Contracts) Tailoring (All) SpE (SpE) Bill Fournier

Related and Overlapping ISO 9000 Lean Six Sigma ITIL CMMI Bill Fournier

References INCOSE SE handbook version October 2011 ( version 4 will come out in 2015) INCOSE.org – CASE tool survey, certification, chapters ISO/IEC 15288:2008 DAU.edu Linkedin my group, my TR book Honourcode roles.pdf Bill Fournier