This tutorial describes the development of product to implement corporate businessstrategy by providing customer perceived value and quality. The tutorial will emphasizethe early stages of product definition and development, beginning with requirementssolicitation. It uses analytical techniques to develop the effectiveness measure criteriaand priorities that drive the solution to a near optimal fit to the market and thebusiness strategy. The approach produces executable requirements and specifications.Engineering your systems with such a model based approach preserves and enhances the bestpractices of systems and software from both the aerospace and the commercial arenas. Fulladvantage is taken of information technology and object-oriented approaches. The approachfollows the best practices of systems engineering, quality methods such as Six Sigma andQTM, as well as mature SEI software practices.
A locomotive example is used throughout the tutorial. It shows how and where the modelbased approach can reduce development cost and time and match the product or service tothe marketplace. It shows how the existing organization may have to change to successfullyadapt to the needs of market, business strategy, and technology change. The same modelingtechniques applied to product or service also are used to describe organizationaladaptation and change.
A single core process for the technical systems work is applied to domain analysis,concept analysis, system analysis, etc., through all of these hierarchical tiers ofdevelopment to provide specifications for detailed component design or for requests forbids from suppliers. The process may be applied top-down or bottom-up, and is tailorableto match the application. Hierarchical development is utilized with full attention toperformance requirements with budgeting and rollup to system level. Optimization based ondefined effectiveness measures and thorough trade-off are emphasized. The effectivenessmeasures are derived from the product company business strategy, from user/owner price andperformance wants, and from the needs of the customers of the user/owner. This approachaligns the engineering with corporate business strategy. Both early confirmation ofrequirements with stakeholders and later validation of requirements are developed from thebeginning by means of executable requirements. Early validation is wedded to riskremediation and successive product releases through successive build and test planning. Aclear distinction is made between the product life cycle, acquisition processes, and theengineering process which is used.
The modeling techniques as described here are not another of the plethora of existingmethodologies, notations, and graphic pictures which are available to do the work. Ratherthe modeling is described in terms of basic work steps and the primitive semantic elementsthat every engineer knows and uses, like: things, part lists, kinds of things,interconnection, functions, inputs & outputs, and the ordering of functions. Thisapproach allows any business to tailor the modeling to its application domain for businessefficiency, and to the background of its staff to minimize training costs and projectrisks. It is consistent with modern object-oriented software notations and techniques.This simplifies and reduces errors in the transition of ECBS information to software anddatabase engineers, a transition of growing importance and concern for both productdevelopment and for business process automation. It enhances the performance of teams thatmust deal with customer, hardware, software and people issues and that incorporatespecialists in all these disciplines. These techniques are equally applicable to thedesign of organizations, teams and processes, though the emphasis of this seminar isapplication products and services.
1. Introduction
1.1 Engineering and complexity
1.2 Origins of modeling in engineering
1.3 Basic abstractions
1.4 Requirements
1.5 Separation of structure and behavior views
1.6 The engineering process
2. Structure
2.1 Objects
2.2 Aggregation
2.3 Interconnection
2.3.1 Context
2.3.2 Assembly
2.4 Classification
2.5 Number
2.6 Examples
2.7 Information models for structure
3. Behavior
3.1 Functions
3.2 Ordering functions
3.3 Input/output
3.4 Example, exercises
3.5 Simulation
3.6 Information models for behavior
3.7 State and functional representations of behavior
4. Core Technical Process
4.1 Assess initial information
4.2 Define Effectiveness Measures
4.2.1 Example, exercises
4.2.2 Flow down and up
4.2.3 Connection to Quality methods
4.2.4 Information model
4.3 Define behavior
4.4 Define structure
4.5 Perform trade-off
4.5.1 Requirements and Effectiveness Measures
4.5.2 Roll-up
4.5.3 Weighting functions
4.6 Create Build, Test, Risk Remediation plan
4.7 The core process as a step in a hierarchical product development
5. Concept Analysis
5.1 Definitions and description, what it is
5.2 Example and exercises
5.2.1 Application of the core process
5.2.2 Application of quality methods
5.2.3 Application of preference assessment methods
6. Locomotive Example, Concept Analysis
6.1 Baseline Locomotive and Organization
6.2 Requirements and effectiveness Measure Elicitation with AHP
6.3 Requirements Elicitation with TQM and Six Sigma
6.4 Analytical Method
7. Subsystem Analysis and Trade-off
7.1 Locomotive decomposition
7.2 Traction and Horsepower
7.3 Reliability, Availability and LRU’s
7.4 Fuel efficiency and Auto-engineer
7.5 Service business and diagnostics
7.6 Pervasive controls and software
8. Organization modification
8. Information models for systems engineering
9. Benefits and introduction to an organization