The Differences Between the Project Manager and the Systems Engineer Kasse Tim Kasse Kasse Initiatives LLC +1 – 972 - 987 - 7706 USA +49 (0) 7721 - 407.

Slides:



Advertisements
Similar presentations
CASDA Project Management A presentation to the CASDA Preliminary Design Review IM&T / CASS Dan Miller | CASDA Project Manager 11 March 2014.
Advertisements

System Integration Verification and Validation
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
ClosingExecuting/ Controlling ControllingPlanningInitiatingOpportunityAssessment Client AcceptancePlanning ApprovalInitiating ApprovalOpportunity Assessment.
IT Strategic Planning Project – Hamilton Campus FY2005.
Chapter 5 IT Processes Presented by Dr. Mohamed Sammouda.
SE 555 Software Requirements & Specification Requirements Management.
Managing the Information Technology Resource Jerry N. Luftman
1 Introduction to System Engineering G. Nacouzi ME 155B.
Trade Study Training Need and Goals Need Consistent methodologies and practices performing trade studies Pros/cons, advantages/disadvantages, customer/management.
4. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the elements of project management and the responsibilities of a.
Chapter 3: The Project Management Process Groups
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
4 4 By: A. Shukr, M. Alnouri. Many new project managers have trouble looking at the “big picture” and want to focus on too many details. Project managers.
Chapter 2 - Overview of the Systems Engineering Design Process1 Aerospace Systems Engineering Chapter 2 - Overview of the Systems Engineering Design Process.
Purpose of the Standards
PRESENTED BY TRUST THOMAS EROMOSELE STUDENT NO:
Effective Methods for Software and Systems Integration
Chapter 2: Overview of Essentials ISE 443 / ETM 543 Fall 2013.
Project Management Process Overview
S/W Project Management
Copyright Course Technology 1999
Roles and Responsibilities
System Planning- Preliminary investigation
Rational Unified Process Fundamentals Module 4: Disciplines II.
Organize to improve Data Quality Data Quality?. © 2012 GS1 To fully exploit and utilize the data available, a strategic approach to data governance at.
Software System Engineering: A tutorial
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
© 2015 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part.
Recap from last week Understand organizations, including the four frames, organizational structures. Explain why stakeholder management and top management.
Introduction- Project Management By Ctrl+C & Ctrl+V 1.
Requirements Engineering CSE-305 Requirements Engineering Process Tasks Lecture-5.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Software Project Management
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.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
Project Life Cycle.
Chapter 9 Project Management. Introduction Effective project management requires a well-structured project and diligent oversight A well-structured project.
Certificate IV in Project Management Certificate IV in Project Management Course Structure Course Number Qualification Code BSB41507.
© Mahindra Satyam 2009 Configuration Management QMS Training.
SOFTWARE CONFIGURATION MANAGEMENT. Change is inevitable when computer software is built. And change increases the level of confusion among software engineers.
Lecture 3 Title: Information Technology Project Methodology By: Mr Hashem Alaidaros MIS 434.
Request for Proposal (RFP)
Software Project Management
1 EMS Fundamentals An Introduction to the EMS Process Roadmap AASHTO EMS Workshop.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Consultant Advance Research Team. Outline UNDERSTANDING M&E DATA NEEDS PEOPLE, PARTNERSHIP AND PLANNING 1.Organizational structures with HIV M&E functions.
Maintaining and Sustaining System Integrity Configuration Management for Transportation Management Systems Configuration management (CM) describes a series.
FRAT – A BASIC FRAMEWORK FOR SYSTEMS ENGINEERING By Brian W. Mar and Bernard G. Morais.
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
Apply Project Scope Management Techniques Project Scope Processes – Part 2 Week 4 Certificate IV in Project Management Qualification Code BSB41507.
Software Engineering Lecture 10: System Engineering.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
Request for Proposal (RFP) In response to the RFP – the first step is to prepare a proposal 1. Review Customer Requirements and come up with candidate.
Software Configuration Management (SCM)
Roles and Responsibilities
Software Project Configuration Management
Chapter 11: Software Configuration Management
CS4311 Spring 2011 Process Improvement Dr
Software and Systems Integration
Project Integration Management
IEEE Std 1074: Standard for Software Lifecycle
Software Configuration Management
Chapter 11: Software Configuration Management
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

The Differences Between the Project Manager and the Systems Engineer Kasse Tim Kasse Kasse Initiatives LLC +1 – USA +49 (0) Europe Singapore

PM ProjMgr vs SE Engr - 2 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC Welcome Wilkommen Bienvenido WelKom Bienvenue Bienvenuto Välkommen Tervetuloa Witamy Huan Yín ЌАΛΟΣ ΟΡΙΣΑΤΕ ようこそ

PM ProjMgr vs SE Engr - 3 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC The Systems Engineer

PM ProjMgr vs SE Engr - 4 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC Systems Engineer uNeed Identification and Customer Linkage  Identify the need and the system opportunity by matching need and technical feasibility  Be the link between customer needs and system idea and design during the entire process of system creation uRequirements Engineering  Develop a set of system and functional requirements based on customer needs, wants, constraints and interface requirements

PM ProjMgr vs SE Engr - 5 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC Systems Engineer - 2 uDefinition of Functionality (Functional Architecture)  Divide and allocate the functional requirements into different subfunctions and modes of operation uOperational Concept  Serve as the lead in envisioning the system’s operational concept and create the link between the system’s requirements and the system’s configuration

PM ProjMgr vs SE Engr - 6 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC Systems Engineer - 3 uArchitectural Design  Design the system architecture based on the operational concept and operational scenarios uAnalysis, Development, and Testing  Collect data from various sources, perform modeling and simulation and analyze them as a basis for decision making  Determine if the system is designed to its requirements  Test and verify that the system, as built, will meet those requirements as designed

PM ProjMgr vs SE Engr - 7 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC Systems Engineer - 4 uTrade-Off Analysis  Conduct technical and tradeoff analysis leading to the resolution of technical problems at different interface points  Conduct risk assessment on the various system elements uManaging the Interaction  Manage the interaction with various engineering groups that perform the subsystem’s design while integrating various people and disciplines

PM ProjMgr vs SE Engr - 8 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC Systems Engineer - 5 uIntegration  See the entire picture and how each part is contributing to the performance and feasibility of the system as a whole  Coordinate the work of the various disciplines involved and manage the interfaces among them so that the result is an overall optimum system  Perform the integration of the various subsystems into a total system uSystem Performance  Evaluate the performance and qualifications of the final system through testing and simulation

PM ProjMgr vs SE Engr - 9 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC Systems Engineer - 6 uCustomer Demonstration  Demonstrate the integrated system to customers in their operational environment

PM ProjMgr vs SE Engr - 10 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC Relationship between Systems and Software Engineering Integrated Logistics Support and Other Disciplines Software Preliminary Design System Operational Requirements Software Detailed Design Software -Code -Test -Integrate Hardware Requirements Analysis Hardware Preliminary Design Hardware Detailed Design Hardware -Fabricate -Test -Integrate Systems Operational Requirements Systems Requirements Analysis Systems Design System Integration Test -Qualification Test -Customer Acceptance -QT & E CONTINUED SYSTEMS ENGINEERING INVOLVEMENT

PM ProjMgr vs SE Engr - 11 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC The Project Manager

PM ProjMgr vs SE Engr - 12 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC Project Manager uHead of the Project  The Project Manager (Project Leader) is the head of the project  The Project Manager has the ultimate responsibility for the planning and control of everything related to the project uInterface Liaison  The Project Manager must interface with the quality manager, the configuration management manager, the integration and test manager, management of other disciplines outside of the project, and the customer

PM ProjMgr vs SE Engr - 13 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC Project Responsibilities Project Leader Management Quality Management Customer Configuration Management

PM ProjMgr vs SE Engr - 14 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC Project Manager - 2 uProject Control System  The Project Manager must establish the feedback loops depicted in the figure shown on the following slide  The Project Manager must ensure that the basic controls are in place to guide the project effort toward its objective

PM ProjMgr vs SE Engr - 15 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC Project Control System Technical Development Project Management Quality Management Configuration Management From “the Software Engineer’s Handbook” by McDermid Error Report Change Requests Work Assignments Draft Products Status Reports Accepted Products Reject Customer Requirements Changes Standards And Procedures Intermediate Development Products

PM ProjMgr vs SE Engr - 16 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC Project Manager - 3 uProvide Direction  The Project Manager must provide direction to the project team and be able to answer questions including:  For whom do I work?  What is expected of me?  Why is it expected of me?  What tools and facilities are available to me?  How do I do what is expected?  What training is available to me?

PM ProjMgr vs SE Engr - 17 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC Project Manager - 4 uProvide Direction - continued  What must I produce?  When must it be produced?  Who do I give it to?  How will my product be evaluated?

PM ProjMgr vs SE Engr - 18 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC Project Manager - 5 uThe Project Manager is the DRIVER and as such takes on the responsibility for many diverse tasks including:  Lead the project team through the process of creating and executing the project plan  Mold the project members into a project team  Obtain approvals for the project plan  Issue status reports on the progress of the project compared to the plan  Respond to requests for changes to the plan

PM ProjMgr vs SE Engr - 19 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC Project Manager - 6  Facilitate the team process, using trained and experience in interpersonnel skills  Remove obstacles for the team so they can do the job they are asked to do  Act as the key interface with the project sponsor  Act as the key interface with the project customer  Ensure that the relevant stakeholders are involved throughout the project lifecycle as required  Call and run regular project meetings  Issue the final project report  Capture lessons learned and update the process database

PM ProjMgr vs SE Engr - 20 Version NDIA SysEngr Conf © 2003 Kasse Initiatives, LLC Summary uSuccessful projects have the technical leadership of the Systems Engineer and the management guidance of the Project Manager