The Differences Between the Project Manager and the Systems Engineer

1. Kasse Initiatives The Differences Between theProject Managerand theSystems Engineer Tim Kasse Kasse Initiatives LLC+1 – 972 - 987 - 7706 USA +49 (0) 7721 - 407 - 851 Europe +65 6430 6769 Singapore

2. Welcome ようこそ WelKom Huan Yín Bienvenido Bienvenue Wilkommen ЌАΛΟΣ ΟΡΙΣΑΤΕ Bienvenuto Välkommen Witamy Tervetuloa

3. The Systems Engineer

4. Systems Engineer • Need 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 • Fred Brooks – Mythical Man Month – Systems Czar • Requirements Engineering • Develop a set of functional and non-functional requirements based on customer needs, wants, constraints and interface requirements

5. Systems Engineer - 2 • Define the Functional Architecture • A functional architecture is: • A set of activities or functions that are arranged in a specific order and when activated, achieves a set of requirements • Divide and allocate the functional requirements into different subfunctions and modes of operation • Define the Physical Architecture • A physical architecture is: • A representation of the physical resources • Expressed as nodes that constitute the system and their connectivity • Expressed in the form of links

6. Systems Engineer - 3 • An important task in the architecture development process is to define the operational concept • A concise statement that describes how the goal will be met • How will the system look and act in the operational environment • Operational 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 • Refine requirements through the definition of the Operational Concept and the creation of Operational Scenarios

7. Systems Engineer - 4 • Define the technical architecture • A minimal set of rules governing the arrangement, interaction, and interdependence of the parts or elements that must ensure that a conformant system satisfies a specified set of requirements • Provides the framework upon which engineering specifications can be derived, guiding the implementation of the system

8. Systems Engineer - 5 • Generating a system architecture as part of the systems engineering process can be seen as a deliberate approach to deal with the uncertainty that characterizes these complex, unprecedented systems – a critical part of Risk Management

9. Systems Engineer - 6 • Analysis, Development, and Testing • Collect data from various sources, perform modeling and simulation and analyze them as a basis for decision making • Verify if the system is designed to its requirements • Peer Review Systems, Requirements and Interface Specifications • Test that the system, as built, will meet those requirements as designed • Use simulation • Use prototypes

10. Systems Engineer - 7 • Trade-Off Analysis • Conduct technical and tradeoff analysis leading to the resolution of technical problems at different interface points • Quadruple Constraints • Cost • Schedule • Performance • Quality

11. Systems Engineer - 8 • Allocate to • Hardware • Software • Electronics • Mechanics • Hydraulics…….. • Choose among • Build • Buy • Supplier • Reuse

12. Systems Engineer - 9 • Conduct risk assessment on the various system elements • Identify sources of risk • Categorize the risk with the parameters of probability, consequences or impact and time frame • Consider catastrophic risks • Calculate risk priority • Provide inputs into possible risk mitigation techniques • Managing the Interaction • Manage the interaction with various engineering groups that perform the subsystem’s design while integrating various people and disciplines

13. Systems Engineer - 10 • Integration • 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 • May guide the integration team

14. Systems Engineer - 11 • System Performance • Evaluate the performance and qualifications of the final system through testing and simulation • Cradle to Grave  Requirements Elicitation to Systems Testing • Customer Demonstration • Demonstrate the integrated system to customers in their operational environment

15. Relationship between Systems and Software Engineering System Operational Requirements Software Preliminary Design Software Detailed Design Software -Code -Test -Integrate SYSTEMS ENGINEERING -Qualification Test -Customer Acceptance -QT & E System Integration Test CONTINUED SYSTEMS ENGINEERING INVOLVEMENT Systems Operational Requirements Systems Requirements Analysis Systems Design Hardware Requirements Analysis Hardware Preliminary Design Hardware Detailed Design Hardware -Fabricate -Test -Integrate Integrated Logistics Support and Other Disciplines

16. The Project Manager

17. Project Manager • Head 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 • Interface 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

18. Project Responsibilities Customer Quality Management Project Leader Management Configuration Management

19. Project Manager - 2 • Project 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

20. Project Control System Customer Requirements Changes From “the Software Engineer’s Handbook” by McDermid Project Management Error Report Change Requests Work Assignments Status Reports Technical Development Intermediate Development Products Draft Products Reject Standards And Procedures Quality Management Accepted Products Products Configuration Management

21. Project Manager - 3 • Provide 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?

22. Project Manager - 4 • What must I produce? • When must it be produced? • Who do I give it to? • How will my product be evaluated?

23. Project Manager - 5 • The 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 • Coordinates or even integrates the subordinate plans including Quality Assurance, Configuration Management, Testing, Database, Hardware, Software, etc.

24. Project Manager - 6 • Issue status reports on the progress of the project compared to the plan • Remember reporting on “True Progress” is dependent on knowing the quality of the life-cycle work product that is being referenced • Respond to requests for changes to the plan • Give guidance for corrective action

25. Project Manager - 7 • Facilitate the team process, using trained and experience in interpersonal skills • Remove obstacles for the team so they can do the job they are asked to do • Politics • Tools • Equipment • Process • Training • Act as the key interface with the project sponsor • Act as the key interface with the project customer

26. Project Manager - 8 • 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

27. Summary • Successful projects have the technical leadership of the Systems Engineer and the management guidance of the Project Manager

28. Welcome ようこそ WelKom Huan Yín Bienvenido Bienvenue Wilkommen ЌАΛΟΣ ΟΡΙΣΑΤΕ Bienvenuto Välkommen Witamy Tervetuloa

29. Kasse InitiativesContact Information • Kasse Initiatives LLC • PMB 293 • 1900 Preston Road, Suite 267 • Plano, Texas 75093 • 972 – 987 – 7601 Office • 972 – 987 – 7607 FAX • www.kasseinitiatives.com