Introduction to Systems Engineering

1 ENES 489P Hands-On Systems Engineering ProjectsIntroduction to Systems EngineeringMark AustinE-mail: for Systems Research, University of Maryland, College Park p. 1/33 Administrative IssuesClass Web PageSee: SyllabusOutlined on the class web page ..AssessmentProject presentation and report will count for 60% of the final grade. p. 2/33 Lecture 1: Getting opportunities in Systems definition of Systems Study: Systems Engineering for Modern Engineering in Mainstream US Lifecycle of Systems Engineering Development ( , Waterfall, Spiral). of development. p. 3/33 Lecture 1: Getting StartedAt the end of this lecture you should be able to is Systems Engineering ? kinds of problems does the discipline try to solve?

2 Is Systems Engineering important? does a typical Systems Engineering lifecycle look like? are the economic consequences of failing to do proper systemsengineering? there any jobs in Systems Engineering ? p. 4/33 Career Opportunities in Systems Engineering p. 5/33 Our Definition of Systems EngineeringSystems Engineering is a discipline that lies at the cross-roads of Engineering andbusiness ELEMENTSSOFTWARE ELEMENTSHUMAN REQUIREMENTS ,SPECIFICATIONS, goals are to balanced and disciplined approach to thetotal integrationof the system buildingblocks with the surrounding methodology for Systems development that focussed onobjectives,measurement, systematic means to acquire information, and sort out and identify areas fortrade-offsin cost, performance, quality p.

3 6/33 Practicing Systems EngineersTypical concerns on the design is the required functionality? well should the system perform? about cost/econmics? will functionality/performance be verified and validated?Typical concerns on the management processes need to be in place to manage the development? kind of support for requirements management will be needed?Learning how to deal with these concerns in a systematic way is a challengingproposition driven, in part, by a constant desire to improvesystem performanceand extend system functionality. p. 7/33 Understanding system ComplexityTo understand a system , you really need to ways in which it will be used, environment in which it will operate, knowledge, technologies, and methods that go into making a wide range of Engineering applications this problem isquite as Systems become more complex, we need to be strategic in the way weapproach design, , points to the importance Decomposition (to simplify design).

4 (to simplify decision making in design). analysis (our understanding of system behavior needs to be right). p. 8/33 Understanding system ComplexityStrategy:Put original problem aside and focus on understanding the collection ofsubsystems that make up the orginal SubsystemComplex SystemComponentMaybe we can understand this!!!Initially too difficult to Systems through reductionremove detailsImproved questions are the subsytems and how are they connected internally? does the system interact with the surrounding environment? p. 9/33 system Assembly via Integration of Abstractions SubsystemComplex SystemComponentsSystem assembly through integration of abstractionsIncreasing importance of technologySystemfunctionalityObservation sIncreasing opportunity for reuse of lower level entitiesEngineering ConcernsIncreasingly heterogeneousIncreasingly homogeneousIncreasing use of abstractionIncreasing need for formal analysisIncreasing range of functionalityabstractionabstractionInteg ration ofcomponentsFocus on technologyabstraction p.

5 10/33 Case Study: SE for Modern BuildingsModern buildings are:.. advanced, self-contained and tightly controlled environments designedto provide services ( , transportation, artificial lighting, ..etc.).The design of modern buildings is complicated of performance-based design and real-time stakeholders (owners, inhabitants), some with competing size ( , 30,000 occupants; thousands of points of sensing andcontrols for air quality and fire protection.) network structures for the arrangement of spaces, fixedcirculatory Systems (power, hvac, plumbing), dynamic circulatory Systems (flows of energy through rooms; flows of material). p. 11/33 Case Study: SE for Modern BuildingsFramework for interaction of architectural, structural, control, and networkedembedded system design metricsControl SystemControl ViewSpatial constraintsFeasibility ofimplementationSecurity requirementsThermal requirementsElectrical requirementsInformation requirementsNetworked Embedded Systems ViewimplementationFeasibility ofScheduling of thermal comfort, security, electrical and componentsSecurity componentsComputer componentsElectrical Building envelope / structural designof , layout and connectivityExternal FactorsSystem ArchitectureArchitecture / Structural Viewof networked embedded.

6 Positioning and connectivityBuiliding Networks DesignSpatio temporalconstraintsExternal environmentOccupant functionality p. 12/33 Case Study: SE for Modern BuildingsSystem LevelSubsystem LevelComponent LevelArchitectural ConcernsForm and , access, level spaces, po-sitioning of spaces, con-nectivity among and spaces, por-tals, doorways, ConcernsStructuralassemblies,overall system stabilityFrame, floor, and , and column el-ements,beam/columnjoints, material ConcernsAccess, comfort, safetyHVAC, lighting, fire pro-tectionHeat exchangers, pipes,elevators,escalators,sprinklers p. 13/33SE in Mainstream US IndustryTraditional Engineering and Systems Engineering serve complimentary roles: Traditional on generation of knowledge needed to ceate new technologies and newthings.

7 Systems on understanding how existing technologies and things can be integratedtogether in new ways (..to create new kinds of Systems ).So here s the bottom line:.. Systems engineers need traditional engineers, and viceversa. p. 14/33SE at the Organizational Level BreadthDepth Systems EngineeringSimulationModeling and Networking .. Systems Tools ..Strategic planning ..Finance, Accounting ..disciplinesdisciplinesdisciplinesEngin eeringComputer hardware among disciplinesSystems analysis and trade offLiaison amongLiaison amongLiaison amongFocus on:..liaison among disciplines, supported by formal methodsfor Systems analysis anddesign. p. 15/33SE at the Project LevelSystems are developed by teams of engineers the team members must be able tounderstand one-another s of team efforts.

8 Competing design and marketTrade off cost and of system 2 Subsystem 3 Subsystem 1 EPAS pecification 1 Specification 2 Specification 3 Systems IntegrationWorking Systemand 1 Team Team 3 Req 3 / Spec. 3 Req 2 / Spec. 2 Req 1 / Spec. 1 Development ProcessViewpointsCoordination of of concerns forTest TestVerificationValidation studies to balance p. 16/33SE at the Project LevelKey to gather requirements that might extend beyond functionality, performance andcost ( , social concerns, political concerns, long-term sustainability)? of the design problem into several levels of abstraction and viewpointssuitable for concurrent development by design teams; of good design alternatives from modular components; of the design team efforts into a working system ; mechanisms that provide a designer with critical feedback on thefeasibility of a system architecture, and make suggestionsfor design methods for early validation/verification of Systems .

9 P. 17/33SE at the Product Level p. 18/33SE at the Product LevelKey to describe what a product does? Can this be done formally? to describe pre-conditions for using a product? to describe a products interfaces? to describe various representations (visual, mathematical). p. 19/33 End-to-End Lifecycle Development SystemsIntegrationBuild and Test Create Project Concept Generate RequirementsSystem Architecting Function analysis Requirements analysis system Synthesis Validation Validation VerificationSystems Engineering Development Physical Design Tradeoff analysis Validation Verification Verification ValidationSystem DesignPlanning and AnalysisThe principal products of Systems Engineering developmentare as follows: Requirements specification; system (logical) architecture; system (physical)design; the physical system products are produced by the following processes: Requirements Engineering ; system architecting; Systems design andintegration.

10 Optimization and trade-off analysis ; validation and verification. p. 20/33 End-to-End Lifecycle DevelopmentTechnical process for system SynthesisFunction AnalysisRequirements AnalysisControl Factors-- Requirements-- Functions-- Reuse of componentsAssessment of Risks and Uncertainty-- Cost estimate-- Performance estimate-- ScheduleSystem ArchitectureNeeds p. 21/33 End-to-End Lifecycle DevelopmentThe terms system validation and verification refer to two basic concerns, arewe building the right product and are we building the product right? Satisfactory answers to both questions are a prerequisite to /SpecificationsSystemDesignCustomerNeeds VerificationValidation and verification concerns are a prerequisite to customer acceptance.