Slide 1Slide 2Slide 3Slide 4Slide 5Slide 6Slide 7Slide 8Slide 9How Would You Define SE?Systems Engineering…The Systems ViewpointSlide 13Systems Engineering ObjectivesIntegrated Product Teams (IPTs)Systems Engineering TasksSlide 17Bi-directional RequirementsTraceability Flow [System to Item Overview]Bi-directional Requirements Traceability Flow [Verification Activity]Slide 20Requirements TasksSlide 22Slide 23Requirements and DesignWhy is it Important to Manage Requirements?Integration TasksWhy is Integration Important?Slide 28Verification TasksWhy is Verification Important?Characteristics of SEsSlide 32Slide 33Slide 34Slide 35Slide 36Slide 37Slide 38Slide 39Slide 40Slide 41Slide 42Slide 43Slide 441Colorado Space Grant ConsortiumColorado Space Grant ConsortiumGateway To SpaceASEN / ASTR 2500Class #08Gateway To SpaceASEN / ASTR 2500Class #082Announcements:3-Best Class guest lecture we have had this semester-Announcements-Next time is Team Time-Attendance will be taken but then…Today:Today:4- Thanks for everyone’s extra effort on Sunday- Especially want to thank those that helped set up and tear down> Kathleen B. > Emily F.> Anthony C. > Charles H.> Jordan D. > Kirstyn J.> Blake F. > Chris K.> Chris K. > Michael L.> Tiffany M. > Matthew P.- Next Sunday Training is September 27, 2009Announcements:Announcements:5- Proposals are due Thursday at 6:00 PM via email- Next Tuesday will be Conceptual Design Reviews- Each team will have only 5 minutes to present- Going over 5 minutes will hurt your grade- Each team member will be in the front of the room and shall help with the actual presentationAnnouncements:Announcements:6- Grades will be posted by Wednesday evening on the class website- You will need your password- Your password will be emailed to you by JenniferAnnouncements:Announcements:7Colorado Space Grant ConsortiumColorado Space Grant ConsortiumQuestions?Questions?8Today…We have our first guest lecturer of the semester.Topic is System EngineeringLet’s welcome…Julia Chu from Lockheed Martin9Introduction toIntroduction toSystems Engineering Systems Engineering Julia Chu Julia Chu September 15, 2009September 15, 2009Some material developed by P. Robitaille and INCOSESome material developed by P. Robitaille and INCOSE10How Would You Define SE?How Would You Define SE?How Would You Define SE?How Would You Define SE?11Systems Engineering…Systems Engineering…• Is a systematic, interdisciplinary approach that transforms Is a systematic, interdisciplinary approach that transforms customer needs into a total system solutioncustomer needs into a total system solution• Is led by systems engineersIs led by systems engineers-But all But all functions play a role; Integrated via clear roles & functions play a role; Integrated via clear roles & responsibilitiesresponsibilities•Must be rigorously applied across programMust be rigorously applied across program• Is the technical "glue" which makes separate design Is the technical "glue" which makes separate design disciplines and subsystems function together to provide disciplines and subsystems function together to provide an integrated system which performs a specific joban integrated system which performs a specific job. . Systems Engineering is a PROCESS -Not an organization12The Systems ViewpointThe Systems Viewpoint• The Design Engineer has the specialist's The Design Engineer has the specialist's viewpoint. Views the system from the inside.viewpoint. Views the system from the inside. - Concerned with other system elements only as Concerned with other system elements only as they affect their own design task; but not they affect their own design task; but not necessarily how theirs may affect othersnecessarily how theirs may affect others• The Systems Engineer has the systems The Systems Engineer has the systems viewpoint. Views the system from the outside.viewpoint. Views the system from the outside. - Concerned with the effect of all system Concerned with the effect of all system elements as they affect overall system design / elements as they affect overall system design / performance / cost / scheduleperformance / cost / schedule13 Systems Engineering must focus on the entire problem: optimize the whole, not the parts!Why Systems Engineering?14Systems Engineering ObjectivesSystems Engineering Objectives • Systematic elimination of less desirable concepts and Systematic elimination of less desirable concepts and early selection of a single preferred system approach.early selection of a single preferred system approach.• Early identification and resolution of critical problem Early identification and resolution of critical problem areas.areas.• Focusing of technical expertise to match program needs.Focusing of technical expertise to match program needs.• Maintaining compatibility among separate but interrelated Maintaining compatibility among separate but interrelated technical activities.technical activities.• Maintaining technical oversight and configuration control Maintaining technical oversight and configuration control throughout concept definition, design, implementation, and throughout concept definition, design, implementation, and support phases.support phases.Key objective: achieve a balanced, affordable design that meets stakeholder needs15 Integrated Product Teams (IPTs)Integrated Product Teams (IPTs) Integrated Product Teams (IPTs)Integrated Product Teams (IPTs)Systems Engineering Integration Team (SEIT) Program Business Support IPT The SEIT Provides SE Guidance & Support to other The SEIT Provides SE Guidance & Support to other IPTs which apply SE Process to their activities.IPTs which apply SE Process to their activities.CustomerCustomerProduct 2 IPTProduct 1 IPTProduct 3IPTProduct N IPTCustomerCustomerCustomerCustomerCustomerCustomerCustomerCustomerCustomerCustomerProgram ManagementIntegrated Product Team (IPT)16Systems Engineering TasksSystems Engineering TasksState the problem Design the system Produce documentationUnderstandcustomer needsDo sensitivityanalysesLead teamsDiscoverrequirementsAssess & manageriskAssess performanceValidaterequirementsDo reliabilityanalysesPrescribe testsInvestigatealternativesIntegrate systemcomponentsConduct reviewsDefine quantitativemeasuresDesign & manageinterfacesVerify requirementsDefine the systemmodelExecuteconfigurationmanagementPerform totalsystem testPerform functionaldecompositionIntegrate projectmanagementRe-evaluate &Improve