1. Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles, rules, etc., classified and arranged in an orderly form so as to show a logical plan linking the various parts. ä A method or plan of classification or arrangement. ä An established way of doing something; method; procedure.

2. Nov. 14, 2007 ä Definition: A set or arrangement of elements that are organized to accomplish some pre-defined goal by processing information. ä Elements ä Software ä Hardware ä People ä Database ä Documentation ä Procedures Computer-Based Systems

3. Nov. 14, 2007 System of Systems -- Example

4. Nov. 14, 2007 The System Engineering Hierarchy ä A hierarchy of views are necessary, for example, ä World View ä Domain View ä Element view ä Detailed View

5. Nov. 14, 2007 Typical Hierarchy

6. Nov. 14, 2007 System Modeling ä Define the processes that define the needs of the view under consideration ä Represent the behavior of the processes and the assumptions on which the behavior is based ä Explicitly define all inputs and outputs to each component ä Define the transformation between inputs and outputs of each component ä Represent all linkages (interfaces)

7. Nov. 14, 2007 Critical Factors ä It is absolutely essential that the following be spelled out completely and in detail ä Assumptions ä Simplifications ä Limitations ä Constraints ä Preferences ä Changes in these is a principal contributor to software change

8. Nov. 14, 2007 Business Process Engineering The system engineering process is called business process engineering when the context of the engineering work focuses on a business enterprise. The system engineering process is called business process engineering when the context of the engineering work focuses on a business enterprise. The goal of businees process engineering (BPE) is to define architectures that will enable a business to use information effectively.

9. Nov. 14, 2007 Business Process Engineering Architecture -- another overused word ä A set of component types together with a set of principles and guidelines for their interconnection. ä Also used to refer to the structure of a system. ä One classification of architectures ä data architecture ä applications architecture ä technology infrastructure

10. Nov. 14, 2007 Business Process Engineering Hierarchy ä Another set of terms or phases of activity ä Information strategy planning (isp) ä Business area analysis (baa) ä Business system design (bsd) ä Construction and integration(C&I)

11. Nov. 14, 2007 A Diagrammatic View

12. Nov. 14, 2007 Information Strategy Planning ä Define strategic business objectives and goals ä Isolate the critical success factors that will enable the business to achieve goals ä Analyze the impact of technology and automation on goals and objectives ä Analyze existing information to determine its role in achieving goals and objectives ä Create a business-level data model

13. Nov. 14, 2007 Information Strategy Planning ä Enterprise Modeling -- a 3-D view ä Organizational structures and functions ä Decomposes business functions to isolate processes that make function happen ä Relate objectives, goals, and CSFs to the organization and its functions ä It is increasingly important that the various functions be interoperable

14. Nov. 14, 2007 Typical Organizational Chart

15. Nov. 14, 2007 Information Strategy Planning ä Business-Level Data Modeling ä focuses on the data objects required to achieve the business functions ä identifies relationships between customers, products, salespersons, etc. ä Culmination - a series of cross reference matrices that establish the relationship between the organization, business objectives and goals, business functions, and data objects.

16. Nov. 14, 2007 Typical Relationship Among Objects

17. Nov. 14, 2007 Business Area Analysis ä Establishes a detailed framework for building an information-based enterprise ä Models ä data models ä process flow models ä process decomposition diagrams ä cross-reference matrices ä Domain View

18. Nov. 14, 2007 Business Area Analysis ä Data Modeling ä Identify data object types (or classes) ä Determine essential attributes ä Determine other objects with which the object has relations ä Determine operations which will need to be performed on the object

19. Nov. 14, 2007 Business Area Analysis ä Process Modeling - describes the business functions within a business area ä Information Flow Modeling - integrates process and data models to show how information flows through a business area

20. Nov. 14, 2007 Typical Process Flow Model

21. Nov. 14, 2007 With Information Flow

22. Nov. 14, 2007 Product Engineering The system engineering process is called product engineering when a product (in this context, a product includes everything from a wireless telephone to an air traffic control system) is to be built. The goal of product engineering is to translate the customer’s desire for a set of defined capabilities into a working product.

23. Nov. 14, 2007 Product Engineering ä The architecture encompasses four components (software, hardware, people, data). ä Develop support infrastructure that includes the technology to tie the components together and the information that is used to support the components. ä Determine requirements from customer ä Systems analysis ä allocate functions and behaviors (to each components) ä determine interfaces ä Component engineering (SE, HW Eng., DB E., Human E) ä Element & Detailed views ä Analysis & design modeling ä Construction & integration

24. Nov. 14, 2007 A Diagrammatic View

25. Nov. 14, 2007 Product Engineering ä Problem solving activity where desired product data, function, and behavior are analyzed and allocated to individual components ä Major activities ä Support infrastructure ä Bound function, performance, constraints, and interfaces ä Develop alternative allocations

26. Nov. 14, 2007 Product Engineering ä Trade-off Criteria ä Project Considerations ä Business Considerations ä Technical Analysis ä Manufacturing Evaluation ä Human Issues ä Environmental Interfaces ä Legal Considerations

27. Nov. 14, 2007 Requirement Engineering The outcome of the system engineering process is the specification of a computer based system at different levels. “How can we ensure that we have specified a system that properly meets customer’s needs and expectations?” Solid requirement engineering is the answer.

28. Nov. 14, 2007 Requirement Engineering ä Requirement engineering process can be described in 5 steps:  Requirement elicitation  Requirement analysis and negotiation  Requirement specification  System modeling  Requirement validation  Requirement management

29. Nov. 14, 2007 System Modeling ä System model template - user interface, input, system function and control, output, maintenance and self-test ä System context diagram - establishes the information boundary between the system being implemented and the environment in which it is to operate ä Architectural flow diagram - shows how information flows between subsystems

30. Nov. 14, 2007 System Model Template

31. Nov. 14, 2007 CLSS Example

32. Nov. 14, 2007 Expanded Example

33. Nov. 14, 2007 Building a Hierarchy

34. Nov. 14, 2007 System Specification ä Document that serves as a foundation for hardware engineering, software engineering, data base engineering, and human engineering ä Describes function and performance of computer-based system as well as constraints ä An essential element required for systems engineering