- Core Courses
- Presentations
- Tutorials
- Quarter-Based Courses
- Semester-Based Courses
- Other Courses
- Special Courses
- Courses Built For Client Ownership
Systems Development Training Program
This training program consists of six groups of courses: (1) most popular core courses that fit into the JOG System Engineering foursome of system development activities, (2) other courses that are available in general because someone else has requested that they be presented, (3) special courses that combine parts of other courses, and (4) courses that are built for a client where the client takes ownership of the course. The latter are, of course, not available to the general public. In each case the courses are organized into four subsets: (1) presentations that commonly require 1 hour to present on a system engineering topic most often having been presented at companies and conferences upon request, (2) tutorials and workshops completed in one or two eight-hour periods of time, (3) quarter-length courses that require three-days for a short course presentation or one quarter at a university, and (4) semester-length courses that require four or five days for a short course presentation or one semester at a university.
There is only one course in each of the five system development activity categories for the most popular courses so those courses are all numbered course 1 in those categories. Those categories are: (0) overviews of the entire system development life cycle, (1) management across the life cycle, (2) requirements work, (3) synthesis work, and (4) verification. In the other course set there are in some cases multiple courses so the general course X is shown. When you click on one of those boxes all of the available courses will be listed.
Some courses listed may not include explanatory information at the time you view the web site even though the course of interest has been previously presented simply because there is a tremendous amount of information involved and JOG System Engineering is continuing to build the content as time goes by. You can contact Jeff Grady as noted in web site Section 11 to obtain the latest information on any of these courses.
The intent is that all courses will eventually become coordinated with features needed to be effective as distance learning products. At present only course 322-2428 on universal architecture description framework (UADF) qualifies. All of the courses in this catalog started with course 321-1321 developed as the first class offered by UC San Diego in 1990 and taught by the owner of JOG System Engineering while he was the Manager of Systems Development at General Dynamics Space Systems Division. Each course is coordinated with a student manual in three divisions: (1) text that is either a specially prepared document, one of the owner’s four current textbooks, or a combination of both, (2) a trio of exhibits supplying presentation materials, workshop guide, and administration materials, and (3) supporting materials providing examples of documents covered in the course. Many of these are available for download from this web site in Section 5.
Figure 3-3 Training Program Menu Options
Core Program Courses
The core program series of courses is oriented around a collection of four activities that collectively comprises the system development process life cycle. These four fundamental activities are: (1) management a program across the development life cycle, (2) accomplish requirements analysis and publish specifications as a prerequisite to design, (3) accomplish synthesis through a series of three transformations (requirements to design, design to procurement of materials needed to manufacture, and parts lists to manufactured product), and (4) verification that the product characteristics match the content of the specifications. One course for each of these four fundamental activities is included in this set forming a system engineering certificate program plus one overview course that covers the whole set. The term “grand systems” is used in course names to emphasize that the courses coordinate with the concept that an enterprise and all of its programs are systems just as the product systems those programs are involved in are systems. An enterprise and a program are predominantly process systems rather than the predominantly product systems being created by programs. In an enterprise that treats itself and all of its programs as systems as well as the products created by the programs, Jeff Grady claims that enterprise is practicing grand systems development. Many of the same techniques applied in developing product systems will provide good service in creating and improving enterprise and program process-oriented systems. This concept is primarily covered in the grand systems management courses 321-311 and 321-411.
321 Core Courses
321 PROGRAM PRESENTATIONS
Presentations generally require one hour to complete. Core program presentations focus on the four fundamental activities plus an overview from the perspective of the owner of JOG System Engineering.
321-101 Systems Overview
This two-hour presentation covers the whole grand systems development life cycle focusing attention to the four critical functions that must be mastered on every program, (1) management, (2) requirements, (3) synthesis, and (4) verification, from a systems engineering perspective.
321-111 Systems Management
A one-hour focus on enterprise and program management from a system engineering perspective. Emphasis is placed on defining the architecture of the enterprise that includes a common process that is selectively brought into the integrated program management plan and schedule and the application of cross-functional teams on programs coordinated with the product entities that must be a part of the system.
321-121 Systems Requirements Analysis
A one-hour presentation of the most essential activities in the accomplishment of requirements analysis on a program focusing on the application of modeling to understanding the problem space and developing the solution space models. Requirements are derived from models and allocated to product entities. A three phase verification process is covered: (1) item qualification, (2) item acceptance, and (3) system test and evaluation.
321-131 Systems Synthesis
Synthesis consists of three important activities on every program. First we must develop a design based on our understanding of the requirements for an entity. Next we must determine where to acquire the parts and materials needed based on the design. Finally, we must manufacture the product. These three steps are summarized in a one-hour session.
321-141 Systems Verification
This one-hour presentation coordinates the definition of a verification requirement for each product requirement in each specification with verification tasks of four kinds (test, analysis, examination, and demonstration) each of which will have to be planned, implemented, reported upon, and reports audited.
321-2 CORE PROGRAM TUTORIALS
These training products are tutorials and workshops that require one or two days to complete.
321-201 Systems Overview
This tutorial provides a brief insight into the whole development life system from need through requirements, synthesis, verification, and the management influence that must embrace the whole program.
321-211 Systems Management
The four fundamental steps in system development are summarized, vocabulary developed, and enterprise planning activities are covered.
321-221 Systems Requirements
Hardware and software structured models are offered for all of the kinds of requirements that appear in specifications. Requirements tools and management topics (traceability, margins, budgets, and TPM) are also covered.
321-231 Systems Synthesis
Covers the principal responsibilities of system engineers during the design process involving interface integration, system optimization, trade studies, and design review support systems.
321-241 Systems Verification
An effective framework is offered within which V&V work can be planned and implemented. Documentation methods are covered encouraging integrated plans and reports.
321-3 CORE PROGRAM QUARTER-BASED COURSES
Each courses in this section requires three days in short course format or one university quarter (commonly three months) when offered as a long course presented a few hours a day or evening one or two times a week. These four courses form a certificate program that covers the complete system development life cycle from a system engineer’s perspective as illustrated in Figure 3-4 consisting of requirements, synthesis, and verification within the context of a sound enterprise and program management infrastructure. The system development process begins by understanding the required functionality for the “Use System” function expressed at the top-level as a need statement. This ultimate functionality is modeled in the Grand Systems Definition function where it drives the content of system and subordinate specifications.
Figure 3-4 Program System Life Cycle
The content of the specifications drives cross-functional teams to develop designs compliant with the driving specifications and integrated across the system. Other synthesis work includes procurement of materials called for by the engineering and manufacturing of product. The product entities are subjected to a three-tier verification process to determine the relationship between the design and content of the driving specifications.
When presented for a company, the outline can be tailored to best satisfy the client needs. Outlines offered for Section 321-3 courses include references to the textbook used plus the INCOSE System Engineering Handbook for those students interested in moving toward readiness to pass the INCOSE Certified Systems Engineering examination.
An effort is underway to convert the courses in this category for delivery to students in one or more locations anywhere in the World through real time presentation via a web site. JOG System Engineering is experimenting with the use of http://www.GoToMeeting/Training.com for this purpose. The intent is to migrate all courses to this capability while not inhibiting their delivery using instructor in the classroom mode.
321-301 Systems Overview
A quarter-based overview course is available but the semester-based course 321-401 is a more satisfactory course because both courses have to cover the whole sweep of a program from beginning to end and the quarter-based course is somewhat time limited in coverage.
321-311 Systems Management
The course provides a broad introduction to system development giving insights into the reasons why this process has evolved linked to human characteristics that have not changed in thousands of years and will likely be with us for a very long time into the future. A definition of systems and system engineering is included along with an introduction to several standards that have evolved to guide organizations in accomplishing this work on programs. When offered at an enterprise, that enterprise’s preferred standards and internal practices will be respected.
The four fundamental system development techniques will be introduced and discussed to provide an overall understanding of the process and as preparation for further study of these techniques in other classes offered subsequently in this or other programs. The first of these four techniques is to define a problem as a precursor to solving it through design. Most engineers have been educated in engineering schools as great problem solvers but have not discovered the wisdom of first defining the problem. This is done through requirements analysis consummating the results in a specification. The second step is synthesis of those requirements, or design, during which system engineers, who are specialists in complexity and generalism, accomplish integration and optimization work at the system level across the boundary conditions respected by development teams. The third step involves proving that the solution derived is a valid solution for the problem defined in the specification and this process is called verification. The forth element covered is the technical management process supporting program management which is the principal area of interest in this first course.
The generic course features a workshop activity oriented toward a generic system development process that can be used as a template on any program. This model may be altered for on-site delivery at a company focused tightly on compatibility with preferred company methods.
Course 321-311 Cross-Reference Matrix
HR TOPIC TITLE GSD REF INCOSE SEH ---------------------------------------------------------------------------------------------------- 01 Introduction to the Course and Certificate Program 1 1, 2, A, B, C and Introduction to System Engineering - - 02 A Generic Life Cycle Development Process 2.1, 2.2, 4 3 03 A Generic Life Cycle Development Process - - (Continued) - - 04 Organizational Structures 3 H 05 Generic Development Process Workshop 4 - 06 Generic Development Process Workshop (Continued) - - 07 Standards and Continuous Improvement 2.3 10, G.3 08 Practices Development and Documentation 2.3 G.1, G.2 09 Generic Process Documentation Workshop 2.3 - 10 Generic Process Documentation Workshop (Continued) - - 11 Program Phasing and Reviews 2.1 3 12 Product System Definition 5.1, 5.2 4.1-4.4, E 13 Program Work Definition 5.3, 5.4, 5.5 5, 8.6 14 Program Work Definition (Continued) - - 15 Program Estimating and Earned Value Systems 5.3, 6.8 Not Covered 16 Program Risk Management 6.2 7.3 17 Program Planning Workshop 5 - 18 Program Planning Workshop (Continued) - - 19 Baselines and Configuration Management 6.9 5.7 20 Program Libraries and Data Management 6.4. 6.8 5.8 21 Technical and Management Tools Base 6.10 Not Covered 22 Deployment Motivation 7.2 Not Covered 23 System Engineering Maturity Assessment 7.1 Not Covered 24 Student Workshop Presentation - -
321-321 Systems Requirements
This course is based on a one-quarter course taught at the University of California, San Diego at least once a year since 1990 as a part of their system engineering certificate program and since then Jeff has taught this course over 120 times. It follows his book System Requirements Analysis originally written to support the first class of the UCSD certificate program and published by McGraw-Hill in 1993. In 2006 the book was re-published under the same title by Elsevier Academic Press. The full course covers structured models for both performance (functional) requirements and design constraints (non-functional requirements). It can be focused on grand systems (generic problem set in combination with the enterprise vision or mission), hardware, or software as a function of the company needs. A very simple progressive method is offered for writing requirements that is fit into one of several structured models covering each kind of requirement that a specification customarily must contain. Traceability, verification, applicable documents analysis, margins and budgets, specification practices, and technical performance measurement are covered as a part of a risk activity. Several hardware and software decomposition models (TSA, MSA, PSARE, OOA, UML, SysML, IDEF, and DoDAF) are presented and the utility of computer requirements tools and models addressed. The concurrent engineering team approach is stressed using the V, waterfall, spiral, or N sequence model.
JOG System Engineering encourages the relationship between model and analyst shown in Figure 3-5. The analyst manipulates the system need using models to extract essentially three different views of the evolving system (functional view that tells what the system must do, the entity view that tells what the system shall consist of, and the behavioral view that tells how those entities must behave to achieve desired functionality. Over time the unknown problem space dissipates and the diagrammatic treatments that precipitate on the three facets derived from the use of a set of models form a clear view of the system architecture that provides insights into the requirements appropriate for inclusion in specifications and an insight into what the systems must consist of as a prelude to design. The chief interactions between the modeling approach applied and the analyst is vision applied to the evolving modeling artifacts and his/her hand-eye coordination in acting on those modeling artifacts using pencil and paper or computer modeling tools.
Figure 3-5 The Relationship Between the Model and the Analyst
System engineering surveys commonly reveal that requirements analysis is the area most in need of improvement in companies. Few development teams, whether focused on grand systems, hardware, or software, perform the requirements analysis process well as a prerequisite to design work. There is good acceptance in management and at the working level of the problems exposed in these surveys but enduring difficulty in implementing improvements is a reality.
The instructor maintains that those who perform this work need classroom exposure to the fundamentals covered in this course as well as experience in applying them in accordance with a written company practice covering the requirements analysis process using a set of models and computer tools. Some companies have implemented this complete prescription but most continue to experience problems in timely and effective requirements definition and capture. The organization within which these system engineers work also must recognize and act on the recognition that a program should be prepared to do this work well including selection of models and templates and mapping these to the functional departments that provide the people. Finally, the organization should implement a system architecture report within which the results of their modeling work can be captured and even configuration managed over time.
Course 321-321 Cross-Reference Matrix
PER TOPIC TITLE TEXT INCOSE ---------------------------------------------------------------------------------------------------- 01 Introduction to Requirements Analysis 2.1 2.1, 2.2, 2.3, 2.7, 02 Introduction to Requirements Analysis (Continued) 2.8, 3 03 Requirements Fundamentals 2.2.1, 2.2.3 04 Requirements Relationships 2.2.2 8.4 05 Initial System Analysis 2.3.1 8.1, 8.2, 11.6, 11.8 06 Functional Analysis 2.3.1, 9.1, 9.2, D.1, D.3 07 Functional Analysis (Continued) 2.3.2 D.5, D.9 08 Performance Requirements Analysis 2.3.4 8.3, D.4 09 Product Entity Synthesis 2.3.5 10 10 Interface Identification and Requirements Analysis 2.3.6 D.2 11 Interface Identification and Requirements Analysis (Continued) 12 Specialty Engineering Requirements Analysis 2.3.7 11.9-11.15, 11.3, 11.5, 11.6, 11.7 13 Environmental Requirements Analysis 2.3.8 11.4 14 Structured Analysis Documentation 2.3.11 15 Software Modeling Using MSA/PSARE 2.4.1, D.7 2.4.2 16 Software Modeling Using OOA/UML 2.4.4 D.8 17 Software Modeling Using OOA/UML 18 Software Modeling Using DoDAF 2.4.5 19 Universal Architecture Description Framework 9 9.5 20 Universal Architecture Description Framework 21 Specification Management 2.6, 2.7 8.5 22 Requirements Risk Abatement 2.7.2 6, D.10 23 Tools Discussion 2.7 9.3 24 Requirements Verification Overview 2.6.6 11.2, 11.3 25 Problem Space Modeling Workshop - - 26 Solution Space Modeling Workshop - - 27 Workshop Submission and Briefing - -
321-331 Systems Synthesis
The course covers the work of a system engineer during the period intervening between the completion of the requirements work and the beginning of the verification work. It covers the three transforms that occupy this space: (1) the transformation of the content of the specifications into product designs, (2) the transformation of the designs into an organized approach for acquiring the materials needed to manufacture the product, and (3) the transformation of the available materials into final products suitable for delivery to the customer through manufacture and assembly. For the system engineer, this work focuses on interface development, integration, optimization, trade studies, and design reviews. One brief workshop asks students to interview a design engineer asking how the engineer believes he or she actually creates a design solution and report the results to the class. The question is the degree to which the designer appeals to logic or the subconscious in this work.
Course 321-331 Cross-Reference Matrix
HR TOPIC TITLE GSD REF INCOSE SEH ---------------------------------------------------------------------------------------------------- 01 Introduction to Grand Systems Synthesis 1.1 Not Covered 02 System Synthesis Fundamentals 1.3 Not Covered 03 Common Process and Program Planning 1.2, 3.2 5.2 04 Teams and Team Work 1.4-3.1.7 H 05 System Definition and Concept Development 3.1, 3.2, 3.4 K 06 System Definition and Concept Development - - (Continued) - - 07 Interface Definition 3.3 N.2 08 Risk Management 4.1 7.3 09 Product Design 4.5 4.5 10 Design Decision-Making 4.2 7.1, L.3 11 Design and Trade Study Workshop 4.3 - 12 Design and Trade Study Workshop (Continued) - - 13 Design Domain Integration 4.4 4.6, 8.2, N 14 Specialty Engineering Integration 5 9, L, L.1, M 15 Configuration Management 4.6 8.3, G.4 16 ICWG Workshop 3.3 Not Covered 17 ICWG Workshop (Continued) - - 18 Procurement and Material 6.1 6.5, 6.7, 6.8, 8.1, F 19 Manufacturing and Quality Integration 6.2, 6.3 6.6, 8.7 20 Verification Integration 4.7 Not Covered 21 Design Review Preparation, Implementation, 4.5 Not Covered and Closeout - - 22 Design Review Workshop - - 23 Design Review Workshop (Continued) - - 24 The Future of Synthesis 7 Not Covered
321-341 Systems Verification
The course covers the process of designing an effective and affordable verification process through which a program may collect the information needed to reach a sound decision in concert with its customer on the question of whether or not the product developed satisfies the previously agreed upon requirements for the product. The ELSEVIER column provides references to the recently published Elsevier Academic Press “System Verification” book whereas the CRC PRESS column gives references to an earlier book by the title “System Validation and Verification published by CRC Press. The INCOSE SEH column gives references to the INCOSE System Engineering Handbook.
One of the principal points made in the course is that your skill in writing good requirements for a product will be improved by improving your skill in writing good verification requirements at the same time you write the product requirements. In fact if, you could do only one thing to improve your organization’s specification development ability, your instructor believes that one thing should be do require that verification requirements be written on the same day as the product requirements before the sun goes down. All too often one will find that the reason the engineer has trouble writing a verification requirements is that the product requirements is un-verifiable and the work of trying to write a verification requirement will make this clear.
The course also focuses on the transformation between collections of verification strings and the verification tasks in which it will be proven whether or not the product design can satisfy specification content and how to manage the significant bookkeeping problems encountered in keeping track of all of the information accumulated.
Course 321-341 Cross-Reference Matrix
HR TOPIC TITLE CRC PRESS ELSEVIER INCOSE SEH ---------------------------------------------------------------------------------------------------- 01 Verification Introduction 1 1.1, 1.3 8.10 02 Verification Introduction 03 Requirements and Specifications 1 1.2 7.2 Overview 04 Requirements and Specifications Overview 05 Verification Requirements 4 2.1 - Identification 06 Verification Requirements Identification (Continued) 07 Verification Requirements Writing 4 2.1 - Workshop 08 Verification Requirements Writing - Workshop (Continued) 09 Top-Down Verification Planning 5 2.2 - & Documentation 10 Top-Down Item Qualification 5 2.2 - Planning Workshop 11 Top-Down Item Qualification - Planning Workshop (Continued) 12 Bottom-Up Item Qualification 6 2.3, 2.4, 2.5 - Planning Analysis 13 Bottom-Up Item Qualification 6 2.3, 2.4, 2.5 - Planning Workshop 14 Bottom-Up Item Qualification - Planning Workshop (Continued) 15 Item Qualification Implementation 7, 8 2.4, 2.5, 2.6 - and Reporting 16 Item Qualification Verification 9 2.7, 2.8 - Management & Audit 17 FCA Workshop 9 2.7, 2.8 - 18 FCA Workshop (Continued) - 19 System Verification Planning 10 4.1, 4.2 - 20 System Verification Planning (Continued) 21 Acceptance Verification Planning 11, 12, 13 3.1, 3.2, 3.3, 3.4 - Management, and Audit 22 Acceptance Verification Planning 11, 12, 13 3.1, 3.2, 3.3, 3.4 - Workshop 23 Re-Verification & Verification - 4.3 - Variations 24 Process Verification 14 5.1, 5.2 -
321-4 CORE PROGRAM SEMESTER-BASED COURSES
Courses offered in this section will require four days to complete when offered in a short course format or one university semester (four months) when offered a few hours a day or evening one or two times per week. Outlines can be tailored to best match client needs.
An effort is underway to convert the courses in this category for delivery to students in one or more locations anywhere in the World through real time presentation via a web site. JOG System Engineering is experimenting with the use of //www.GoToMeeting/Training.com for this purpose. The intent is to migrate all courses to this capability while not preventing their delivery using instructor in the classroom mode. The first course being updated to this configuration is 321-428 listed under Other Semester-Based Courses.
321-401 Systems Overview
The overview course was originally developed for Applied Technology Institute (ATI) several years ago and is still offered once a year in a public forum on each coast. Refer to Section 313 of this web site for the public calendar under the course title “Total Systems Engineering Development and Management.” The whole system development life cycle process covered in four separate courses is discussed in four days, one day for each of the four fundamental development activities: (1) Management stretching across the whole program, (2) requirements, (3) synthesis, and (4) verification.
Course 321-401 Cross-Reference Matrix
HR TOPIC TITLE GSD REF INCOSE SEH ---------------------------------------------------------------------------------------------------- 0 Course Introduction 1 Management Segment 1-1 Introduction to System Engineering 1-2 Development Process Overview 1-3 Enterprise Re-Engineering 1-4 Program Design 1-5 Program Estimating and Earned Value Systems 1-6 Program Risk Management 1-7 Baselines and Configuration Management 1-8 System Engineering Maturity 2 Requirements Segment 2-1 Requirements Introduction 2 2-2 Requirements Relationships 2-3 Requirements Elicitation and Program Beginnings 4.2, I.1, I.2, 2-4 Traditional Structured Analysis 4.3, 4.4, I.3, I.4, J.1, J.2 2-5 Traditional Structured Analysis K.1, K.2, K.3 2-6 Computer Software Structured Analysis 2-7 Computer Software Structured Analysis 2-8 Specification Publishing and Management 7.2, I.5, J3 3 Synthesis Segment 3-1 Introduction to System Synthesis 3-2 Product Design 3-3 Other Product Sources 3-4 Interface Development 3-5 Interface Development 3-6 Trade Studies and Decision-Making 3-7 Design Reviews 3-8 Manufacturing and Quality 4 Verification Segment 4-1 Introduction to Verification 4-2 Requirements Validation 4-3 Item Qualification Requirements Identification 4-4 Verification Requirements Writing Workshop 4-5 Item Qualification Planning and Documentation 4-6 Top-Down Item Qualification Planning Workshop 4-7 Item Qualification Implementation, Reporting, Management, and Audit 4-8 Item Acceptance and System Test and Evaluation Overview
Several clients over a period of years have requested various versions of a comprehensive system engineering overview course that have resulted in the availability of course 401 with several different configurations, one of which will generally satisfy the training needs of the client. The figure below illustrates six course configurations, A through F. All of these configurations cover the whole system development life cycle and thus the course is referred to as the Grand Systems Overview course. This course may be accomplished on any schedule selected by the client where the client is located in close proximity to San Diego, CA. Where the instructor must travel some distance to the client some schedules become more cost efficient than others. The figure and table below show six configurations accomplished in some number of trips. The numbers under the configuration letter columns in the table are in 8-hour days. The numbers in the figure tell the number of contact hours for each component. The course components are explained in the table below. The outline for this course above corresponds to course configuration A.
Number of Days Course Component Title Color Black & White Background A B C D E F ---------------------------------------------------------------------------------------------------- Systems Management Red Lines slopes down to the left 1 1 2 1 2 3 Systems Requirements Orange Lines sloping down to the right 1 2 5 3 3 3 Systems Synthesis Green Vertical lines 1 1 1 1 1 3 Systems Verification Blue Horizontal lines 1 1 1 1 1 3
Figure 3-6 Systems Overview Course Configurations
The components can be scheduled in a wide array of possibilities but they are arranged in the figure in ways that clients have ordered them where configurations A and B are commonly done in a single trip and the others in one trip for each vertical slice. For example, configurations C, D, and E could all be accomplished in two or three two-day trips and one three-day trip while configuration F could be accomplished in four three-day trips. The reader will note that configuration F is essentially the whole four-course system engineering program in three-day courses while configuration A is the whole program in a one-day tutorial format. Clearly, a configuration could be provided composed of four four-day (semester-length) courses. A company can pick a configuration that respects their understanding of their strengths and weaknesses.
321-411 Systems Management
The course provides a broad introduction to system development giving insights into the reasons why this process has evolved linked to human characteristics that have not changed in thousands of years and will likely be with us for a very long time into the future. A definition of systems and system engineering is included along with an introduction to several standards that have evolved to guide organizations in accomplishing this work on programs. When offered at an enterprise, that enterprise’s preferred standards and internal practices will be respected.
The four fundamental system development techniques will be introduced and discussed to provide an overall understanding of the process and as preparation for further study of these techniques in other classes offered subsequently in this or other programs. The first of these four techniques is to define a problem as a precursor to solving it through design. Most engineers have been educated in engineering schools as great problem solvers but have not discovered the wisdom of first defining the problem. This is done through requirements analysis consummating the results in a specification. The second step is synthesis of those requirements, or design, during which system engineers, who are specialists in complexity and generalism, accomplish integration and optimization work at the system level across the boundary conditions respected by development teams. The third step involves proving that the solution derived is a valid solution for the problem defined in the specification and this process is called verification. The forth element covered is the technical management process supporting program management which is the principal area of interest in this first course.
Unique ideas are exposed for organizing work from the perspective of the enterprise and its programs with encouragement for following a common process on all programs.
The generic course features a workshop activity oriented toward a generic system development process that can be used as a template on any program. This model may be altered for on-site delivery at a company focused tightly on compatibility with preferred company methods.
Course 321-411 Cross-Reference Matrix
HR TOPIC TITLE GSD REF INCOSE REF ---------------------------------------------------------------------------------------------------- 01 Introduction to the Course and Certificate 1.1 2 Program 02 Introduction to System Engineering 03 A Generic Life Cycle Development Process 1.2.1, 1.2.2, 1.4 3. 4 04 A Generic Life Cycle Development Process 05 A Generic Life Cycle Development Process 06 Organizational Structures 1.3 7 07 Organizational Structures 08 Generic Development Process Workshop 1.4 2.7, 7 09 Generic Development Process Workshop 10 Practices Development and Documentation 1.2.3 C 11 Practices Development and Documentation 12 Generic Process Documentation Workshop 1.2.3 C 13 Generic Process Documentation Workshop 14 Program Phasing and Reviews 1.5.3 3 15 Program Phasing and Reviews 16 Product System Definition 1.5.1 8,9,10,D 17 Program Work Definition 1.4.1, 1.5.3, Not Covered 18 Program Work Definition 1.5.5 19 Program Work Definition 20 Program Staffing 21 Program Estimating and Earned Value Systems 1.5.3 C.10.2 22 Program Risk Management 1.6.2 6 23 Program Risk Management 24 Program Planning Workshop 1.5.3 C 25 Program Planning Workshop 26 Baselines and Configuration Management 3 5.2 27 Program Libraries and Data Management 1.6.4 5.2 28 Technical and Management Tools Base 3 Not Covered 29 Technical and Management Tools Base 30 System Engineering Deployment Motivation 1.7.2 Not Covered 31 System Engineering Maturity Assessment 1.7.1 5 32 Student Workshop Presentation Not Covered
321-421 Systems Requirements
This course is based on a one-quarter course taught at the University of California, San Diego for several years as a part of their system engineering certificate program. It follows Jeff Grady's book System Requirements Analysis originally written to support the first class of this UCSD certificate program and published by McGraw-Hill in 1993 updated in manuscript form in 1999. The full course covers structured models for both performance (functional requirements) and design constraints (non-functional requirements). It can be focused on grand systems (generic problem set in combination with the enterprise vision or mission), hardware, or software as a function of the company needs. A very simple progressive method is offered for writing requirements and that is fit into one of several structured models covering each kind of requirement that a specification customarily must contain. Traceability, verification, applicable documents analysis, margins and budgets, specification practices, technical performance measurement, and requirements integration are all covered in the full course. Several hardware and software decomposition models are presented and the utility of computer requirements tools and models addressed. The concurrent engineering team approach is stressed using the V, waterfall, spiral, or N sequence model.
Book content is supplemented with additional material derived from books by DeMarco, Yourdon and Coad, Hatley and Pirbhai, Booch, and Rumbaugh for computer software requirements analysis. The course also extends requirements analysis work to what the instructor calls Universal Architecture Description Framework (UADF) that encourages selection of one of three particular set of models that are collectively comprehensive feeding a universal specification structure where all of the content of all of the specifications are derived from modeling. Those UADF are: (1) functional, (2) MSA-PSARE, and (3) UML-SysML.
Course 321-421 Cross-Reference Matrix
HR TOPIC TITLE GSD REF INCOSE SEH ---------------------------------------------------------------------------------------------------- 01 Introduction 02 Requirements Fundamentals 03 Specification Structures 04 Specification Practices 05 Applicable Documents, Laws, and Regulations 06 Introduction to the Use of Computer Tools 07 Modeling Fundamentals 08 Values Engineering 09 Initial System Analysis 10 Functional Analysis 11 Functional Analysis Variations 12 Performance Requirements Analysis 13 Product Entity Synthesis 14 Interface Identification and Definition 15 Interface Identification and Definition 16 Specialty Engineering Requirements 17 Environmental Requirements 18 Vertical and Longitudinal Traceability 19 Lateral Traceability and Modeling Work Capture 20 Requirements Risk Management 21 Margins and Budgets 22 Verification Overview 23 Precedented Development Differences 24 Introduction to Computer Software Analysis 25 Modern Structured Analysis 26 PSARE 27 PSARE 28 Early OOA 29 Unified Modeling Language 30 Unified Modeling Language 31 SysML 32 DoDAF 33 DoDAF 34 Universal Modeling Using Flow Charting 35 Universal Modeling Using SysML and UML 36 Universal Modeling Using SysML and UML 37 Starting With Functional Analysis and UML 38 Universal Modeling Using PSARE 39 Universal Modeling Using PSARE 40 Future of Model-Driven Development
321-431 Systems Synthesis
The semester-based synthesis course merges the quarter-length synthesis course with the quarter-length effectiveness course dealing with specialty engineering disciplines and enterprise and program design coverage from course 322-332 to provide a comprehensive course for that period of the system development life cycle between completion of the requirements work and the beginning of the verification work.
Course 321-431 Cross Reference Matrix
HR TOPIC TITLE GSD REF INCOSE SEH ---------------------------------------------------------------------------------------------------- 01 Introduction to Systems Synthesis 3.1.1 Not Covered 02 Enterprise Re-engineering and Synthesis 3.1.2, 3.2 5.2 03 Enterprise Re-engineering and Synthesis (Continued) 04 Organizational Structures and Cross-Functional Teams 3.1.4-3.1.7, H 05 Enterprise Practices Development and Maintenance 06 Program Life Cycle Models and Phasing 07 Problem Space Modeling and Product Entity Definition 3.3.1, 3.3.2, 3.3.4, K 08 Early Program Solution Space Synthesis 09 Program Development 10 Program Development (Continued) 11 Program Cost Estimating and Earned Value 12 Program Risk Management 3.4.1 7.3 13 Design Source and Product Design Approaches 3.4.5 4.5 14 Design Source and Product Design Approaches 15 Simulation, Development Evaluation Testing, and Special Aids 16 Design Decision-Making and Trade Studies 3.4.2 7.1, L.3 17 Design and Trade Study Demonstration 3.4.3 - 18 Design and Trade Study Demonstration (Continued) - - 19 Interface Definition and Integration 3.3.3 N.2 20 Interface Definition and Integration (Continued) 21 Design Domain Integration 3.4.4 4.6, 8.2, N 22 Design Domain Integration (Continued) 23 Detail Specification Development 24 Configuration Management 25 ICWG Demonstration 4.6 8.3, G.4 26 ICWG Demonstration (Continued) 27 Design Review Preparation, Implementation, 3.4.5 Not Covered and Closeout - - 28 Introduction to Specialty Engineering 29 Reliability 30 Maintainability 31 Availability Overview and RAM Workshop 32 Life Cycle Cost 33 Queuing Theory and Applications 34 Logistics Engineering Overview 35 System Safety and Human Engineering Overview 36 System Analysis Disciplines Overview 37 Procurement and Material Integration 3.6.1 6.5, 6.7, 6.8, 8.1,F 38 Manufacturing and Quality Integration 3.6.2, 3.6.3 6.6, 8.7 39 Workshop Project Design Review Presentation - - 40 The Future of Synthesis 3.7 Not Covered
321-441 Systems Verification
The semester length verification course extends the verification process beyond the product system to provide coverage of the application of verification to the other two systems that must be dealt with – the program and the enterprise. The design reviews are covered in the synthesis course but the functional configuration audits (FCA) and physical configuration audit (PCA) are included in this course so that in the two courses the complete story on major reviews and audits is covered. Engineers and managers in a company often believe that the purpose of verification is to prove that the product satisfies its requirements but the work of a verification engineer is a much more difficult case of determining the relationship between the product design and the driving requirements and reporting the truth to management. The truth is sometimes very difficult to deal with and provides stresses that managers should resolve with integrity as should the verification engineers in reporting results.
Course 321-441 Cross Reference Matrix
HR TOPIC TITLE GSD REF INCOSE SEH ---------------------------------------------------------------------------------------------------- 01 Introduction to Verification 1.1, 1.3 8.10 02 Introduction to Verification 03 Requirements and Specifications Overview 1.2 7.2 04 Requirements and Specifications Overview 05 Program Integrated Test and Evaluation Master Plan 06 Program Integrated Test and Evaluation Master Plan 07 Item Performance Specifications 08 Item Qualification Verification Overview 09 Qualification Verification Requirements Identification 2.1 - 10 Qualification Verification Requirements Identification 11 Top-Down Verification Planning & Documentation 2.2 - 12 Top-Down Verification Planning & Documentation 13 Bottom-Up Item Qualification Planning and 2.3, 2.4, 2.5 - Documentation 14 Bottom-Up Item Qualification Planning and Documentation 15 Item Qualification Implementation and Reporting 2.4, 2.5, 2.6 - 16 Item Qualification Verification Management 2.7, 2.8 - 17 Functional Configuration Audit (FCA) - 18 Functional Configuration Audit (FCA) - 19 Qualification Verification Variations 20 Item Acceptance Verification Overview 21 Item Detail Specifications 22 Item Acceptance Requirements Identification 23 Item Acceptance Verification Planning 24 Item Acceptance Verification Planning Management 3.1, 3.2, 3.3, 3.4 - 25 Physical Configuration Audit (PCA) 26 Acceptance Verification Planning Workshop 3.1, 3.2, 3.3, 3.4 - 27 System Test and Evaluation Overview 28 System Specification 29 System Verification Requirements Identification 30 System Verification Planning and Documentation 4.1, 4.2 - 31 System Verification Planning and Documentation 32 System Verification Management 33 Operational Test and Evaluation Support 34 Re-Verification 4.3 - 35 Enterprise Common Process 36 Enterprise and Program Process Maturity 37 Enterprise Verification 38 Enterprise Verification 39 Program Verification 5.1, 5.2 - 40 Program Verification
322 OTHER COURSES
322-1 OTHER PRESENTATIONS
322-10 OTHER OVERVIEW PRESENTATIONS
322-103 UAV Development Good Humor
Offers a humorous insight into the early days of unmanned photo reconnaissance accomplished in North Vietnam and China using converted target drones from Teledyne Ryan Aeronautical Company. Developed for presentation at the 2010 San Diego INCOSE Chapter Mini Conference.
322-11 OTHER MANAGEMENT PRESENTATIONS
322-112 Systems Engineering For Managers
This three-hour tour of system engineering was originally presented at Johns Hopkins University for a class of employees of the Applied Physics Laboratory that is part of Johns Hopkins. It covers the complete system development life cycle from a management perspective.
322-113 Systems Engineering For Executives
A one hour presentation originally offered to a class at the Executive Program for Scientists and Engineers (EPSE) at University of California San Diego.
322-12 OTHER REQUIREMENTS PRESENTATIONS
322-122 Requirements Analysis
A one-hour presentation focused on the analysis work that develops the content of specifications through modeling.
322-123 Requirements Management
A one-hour presentation focused on the management aspects of requirements work. This includes development of enterprise specification templates and data item descriptions, assigning clear department responsibility for accomplishing requirements analysis work on programs as a function of the standard template paragraphing structures, arriving at a decision on what modeling set to employ and training people to apply it well, and specification publishing.
322-124 RAS-Centered Requirements Analysis
Explains the concept that every requirement should be derived from a model and that linkage should be captured in a requirements analysis sheet (RAS) implemented in a computer database or tool.
322-125 Multichannel Modeling
A one-hour presentation on the application of coordinated set of models on programs within an enterprise. This was the beginning of the JOG System Engineering interest that led to development of the universal architecture description framework (UADF).
322-128 Universal Architecture Description Framework
A one hour presentation introducing the reality that we have no comprehensive models today that can be applied by an enterprise on all of its programs no matter how they decide to implement the design. Three comprehensive models are offered composed of models available today. They are: (1) functional, (2) MSA-PSARE, and (3) UML-SysML.
322-12A Traceability
Three kinds of traceability are discussed in this one-hour presentation: (1) hierarchical traceability where subordinate requirements are linked to the related parent requirements and source and rationale data are noted, (2) lateral traceability that links every requirement to the modeling artifact from which it was derived, and (3) longitudinal traceability linking requirements to the design features that implement them and the verification requirements corresponding to them.
322-12E A Simple Prescription for Requirements Success
A one-hour presentation of the central points concerning a practical approach to modeling systems deriving requirements appropriate for the product entities of the system from modeling artifacts, and publishing specifications containing these requirements.
322-12K Requirements Tools and Their Improvement
The state of requirements tools is discussed and improvements that could be made to cause them to be more effective.
322-13 OTHER SYNTHESIS PRESENTATIONS
322-132 System Effectiveness
A one-hour presentation introduces the several disciplines that commonly must be applied on programs. These include reliability, maintainability, availability, mass properties, safety, and several others noted. The modeling approaches employed are discussed.
322-14 OTHER VERIFICATION PRESENTATIONS
322-2 OTHER TUTORIALS
322-21 OTHER MANAGEMENT TUTORIALS
322-212 Systems Engineering Deployment
The principal steps in providing an effective system engineering capability that can be deployed into programs are discussed. Based on the lecturer’s book by the same name.
322-213 Systematic Enterprise Re-Engineering
Presents a powerful structured enterprise re-engineering model coupled with a variation on the US Air Force integrated management system that optimizes a seamless program planning process which pulls functional department resource strings into the program and offers a common program basis encouraging coordinated metric collection and closed loop continuous process improvement.
322-214 System Thinking
322-215 Introduction to Systems Engineering
Provides a one-day tutorial discussing the foundations of systems engineering and key activities applied on programs.
322-216 A Short Story of Systems Engineering
This tutorial was motivated by a need to intellectually describe a simplified systems engineering capability in a proposal in the interest of controlling cost.
322-22 OTHER REQUIREMENTS TUTORIALS
322-222 Systems Requirements Analysis
Hardware and software structured models are offered for every kind of requirement that will have to be identified in a specification. Modeling is combined with requirements elicitation of knowledge from the customer.
322-223 Systems Requirements Management
This one-day tutorial focuses on the management of the requirements analysis activity early in a program when a great deal of modeling is being accomplished and follows the program into a more important application of configuration management of the specifications and related databases and models.
322-224 Functional Analysis
Covers the use of functional flow, IDEF-0, enhanced functional flow, and behavioral diagramming as a way of gaining insight into performance capabilities/requirements and association of these requirements with needed product entities and interfaces.
322-225 Modern Structured Analysis and PSARE
A one-day tutorial exploring the use of modern structured analysis (MSA) and process for system architecture and requirements engineering (PSARE) in the development of software, hardware, and systems. PSARE, earlier referred to as Hatley-Pirbhai (HP), was actually developed as a system model that can be applied to systems and the hardware entities within as well as the software.
322-226 UML/SysML
A one-day tutorial to introduce the UML and SysML modeling concepts. Covers the diagrams and how they are used to gain an insight into appropriate requirements for inclusion in specifications.
322-227 DoDAF
This one-day tutorial provides an overview of the very complicated Department of Defense Architecture Framework intended for the development of information systems. We will cover the diagrams and how they are used and the Unified Process for DoDAF MoDAF (UPDM) that is implementing DoDAF using UML artifacts.
322-228 Universal Architecture Description Framework
Covers the emergence of a universal model for use in developing systems no matter the implementation intended. Coordinates with the model-driven development paradigm and provides a universal specification format.
322-22A Three-Dimensional Traceability
Covers traditional vertical traceability dealing with parent-child relationships, longitudinal traceability dealing with traceability from the requirements through the design and verification work, and lateral traceability dealing with traceability between specification content and the models through which specification content was derived.
322-22B The Past, Present, and Future of Structured Analysis
The history of the use of structured analysis in requirements analysis work beginning with flow charting and running through UML with an extrapolation about where we are going as UML is made universal and model driven development comes on line.
322-22C Requirements Analysis and Management Infrastructure
This one-day tutorial covers the most important elements of the requirements analysis and management work.
322-22D Up-To-Date Requirements
Combines RAS-Complete with effective use of structured analysis and a database.
322-22E A Simple Prescription For Requirements Success
Prescribes an understandable course of action for an enterprise that wants to improve its performance in requirements work.
322-22F An Effective Specification Development Algorithm
Covers the employment of traditional structured analysis combined with UML to accomplish all requirements analysis.
322-23 OTHER SYNTHESIS TUTORIALS
322-232 Systems Effectiveness
Covers RAM modeling as well as safety, human engineering, mass properties, and specialized design and analysis work.
322-234 Concept Development
One-day tutorial covers the first step in the design process where designers and design teams formulate alternative concepts that have some chance of meeting requirements in the related specification. Trade studies are discussed as one way to reach a good decision between competing concepts.
322-23A Trade Study Practices
Three trade matrix approaches are discussed with emphasis on the multivariate approach supported by a three-part value system (raw parameter values, weighting factors, and utility curves) and sensitivity evaluation.
322-23B Interface Development
Interface development techniques within teams and across team and associate boundaries are covered including schematic block and n-square diagrams, ICDs, and use of an ICWG to control associate interface development in accordance with a joint interface development plan.
322-23C Design Reviews
This one-day tutorial on the planning and implementing design reviews is based on the content of MIL-STD-1521B. Covers preliminary and detail design reviews as well as reviews within a program for chief engineer and program manager review and approval of concepts and solutions to problems encountered.
322-24 OTHER VERIFICATION TUTORIALS
322-3 OTHER QUARTER-BASED COURSES
322-30 OTHER QUARTER-BASED OVERVIEW COURSES
322-301 Systems Overview
The overview course covers the whole system development life cycle process available in four separate courses in four days, one day for each of the four fundamental development activities: (1) Management stretching across the whole program, (2) requirements, (3) synthesis, and (4) verification.
322-305 Systems Overview for White Sands Missile Range
This is a special version of course 322-301 developed for and presented at White Sands Missile Range.
322-31 OTHER QUARTER-BASED MANAGEMENT COURSES
322-32 OTHER QUARTER-BASED REQUIREMENTS COURSES
322-322 Systems Requirements Analysis
This course focuses on the application of functional analysis for the identification of an appropriate product entity structure and performance requirements for those entities augmented with interface analysis to synthesize the relationships between the entities based on the way that functionality was allocated to the entities and exposing appropriate interface requirements using n-square and schematic block diagrams, a specialty engineering scoping matrix teamed with specialty engineering models as the basis for identifying specialty engineering requirements, and a three layer environmental requirements analysis model for system, end items, and components. The premise is that all requirements should be derived from models. The course offers models appropriate for identification of requirements for systems and hardware entities. Flow-charting was initially employed in software work and that application is briefly covered for historical purposes but students are encouraged to study MSA, PSARE, OOA, UML, or DoDAF for computer software requirements analysis.
Course 322-322 Cross-Reference Matrix
HR TOPIC TITLE GSD REF INCOSE SEH ---------------------------------------------------------------------------------------------------- 01 Introduction 1, 2.4 2.1, 2.2, 2.3, 2.7, 2.8, 3 02 Requirements Fundamentals 2.1 03 System Definition and Requirements Elicitation 3.1 4.3.1.1, 4.3.1.2 04 Requirements Elicitation and Writing Workshop 05 Requirements Relationships 2.2, 2.3 8.4 06 Relationships Workshop 07 Functional Analysis 3.2, 3.3, 3.9 9.1, 9.2, D.1, D.3, 08 Functional Analysis (Continued) D.5, D.6 09 Functional Analysis (Continued) 10 Performance Requirements Analysis 3.4 8.3, D.4 11 Architecture Synthesis 3.5 10 12 Interface Identification & Requirements Analysis 3.6 D.2 13 Environmental Requirements Analysis 3.8 11.4 14 Environmental Requirements Analysis 15 Specialty Engineering Models 3.7 11.3-11.7, 16 Specialty Engineering Models (Continued) 11.9-11.15 17 Process-Oriented Software Models - Flow Charting 4.1, 4.2 D.7 18 MSA and PSARE 4.2 19 Object Oriented Models UML and SysML 4.4 D.8 20 Object Oriented Models UML and SysML (Continued) 21 Data-Oriented Models and DoDAF 4.3, 4.5 Not Covered 22 Universal Architecting 23 RAS Complete Summary 3.10, 3.11 Not Covered 24 Student Workshop Presentation
322-323 Systems Requirements Management
The course covers some history of the requirements and specification process employed in industry. Specification templates are studied as well as their place in the requirements work. A universal specification structure is offered that is coordinated with several different structured analysis modeling techniques. The use of standards is discussed as a way of introducing large tracts of requirements applicable to the design of multiple entities and the necessary tailoring of these standards emphasized. Requirements relationships including traceability are covered. The review and approval of specifications and changes to them is a key element of the course. Requirements validation, including the use of technical performance measurement (TPM), leading to an identification and mitigation of performance risks is covered. Management support work dealing with the use of margins and budgets is included.
Course 322-323 Cross-Reference Matrix
HR TOPIC TITLE GSD REF INCOSE REF ---------------------------------------------------------------------------------------------------- 01 Introduction To Requirements Management 2.7.1 02 Program Preparation 2.7.7 03 Structured Analysis Documentation 2.3.11 04 Specification Content Practices 2.6 05 Specification Development, Configuration 2.6 Control, and Change Processing 06 ICD Management 2.7.5 07 Applicable Documents, Laws, and Regulations 2.6.4 08 Functional Analysis Extension 09 Functional Analysis Extension (Continued) 10 Interface Analysis Extension 11 Interface Analysis Extension (Continued) 12 Specialty Engineering Extension 13 Environmental Modeling Extension 14 MSA/PSARE Extension 15 Requirements Integration and Impact Analysis 2.7.4 16 Requirements Validation and Risk Management 2.7.2 17 Requirements Risk and Validation Workshop 18 Budgets and Margins Management 2.2.3 19 Budgets and Margins Workshop 20 Requirements Traceability 2.2.2 21 Technical Performance Measurement 2.7.2.4.6 22 TPM Workshop 23 Verification Management 2.5 24 Tools
322-324 Functional Analysis
The first model applied in system engineering was functional analysis where the analyst attempts to understand the problem space by identifying what the system must accomplish and then allocating that functionality or performance requirements derived from those functions to product entities following the lead of the architect Louis Sullivan who offered that “form should ever follow function.” The course covers its application to systems and hardware but also for historical background its initial application to computer software development. Variations including IDEF-0, enhanced functional flow block diagramming, behavioral diagramming, and hierarchical functional analysis are included. Solution space models for product entity, interface, specialty engineering, and environmental requirements identification are also included to form a comprehensive modeling capability. Periods 25, 26, and 27 only appear in a quarter length university course implementation. A 24 contact hour short course does not include the workshop.
Course 322-324 Cross-Reference Matrix
HR TOPIC TITLE GSD REF INCOSE SEH ---------------------------------------------------------------------------------------------------- 01 Introduction to Requirements Analysis 1 2, 4.1 02 Introduction to Requirements Analysis (Continued) - - 03 Requirements Fundamentals 2.1, 2.3 4.3 04 Requirements Relationships 2.2 I.4 05 Initial System Analysis 3.1 4.2, I.1, I.2, L.3 06 Functional Analysis 3.1, 3.2 4.4, I.3, I.6, J.1, - J.2, L.2 07 Functional Analysis (Continued) - - 08 Functional Analysis Variations 09 Functional Analysis Demonstration/Workshop - - 10 Performance Requirements Analysis 3.4 I, I.4 11 Performance Requirements Extraction Demonstration - - 12 Classroom Workshop Time - - 13 Product Entity Synthesis 3.5 4.7, K 14 Product Entity Synthesis (Continued) 15 Interface Identification 3.6 Not Covered 16 Interface Requirements Definition 17 Interface Requirements Definition 18 Specialty Engineering Requirements Analysis 3.7 9, L.1, M 19 Specialty Engineering Requirements Analysis (Continued) 20 Environmental Requirements Analysis 3.8 Not Covered 21 Environmental Requirements Analysis (Continued) 22 Classroom Workshop Time - - 23 Specification Management 6, 7 1.5, 7.2 24 Requirements Risk Abatement 7.2 7.3 25 Requirements Verification Overview 5 4.7, 4.9, 8.9, 8.10 26 Tools 8 J.3 27 Workshop Presentation - -
322-325 MSA-PSARE
Provisions for a future course covering the integrated application of modern structured analysis (MSA) as practiced by Yourdon, DeMarco, Constantine, and others and the process for system architecture and requirements engineering (PSARE) as practiced by Hatley, Pirbhai, and Hruschka with MSA being a subset of PSARE where real-time criticality is not a primary concern. Both can be applied as software dedicated models or expanded as in PSARE to embrace the complete system creating a UADF (see 32528) A lot of people fail to understand that Hatley and Pirbai actually created a universal architecture description framework (UADF) in PSARE (previously called HP) that has several advantages over the other two UADF recognized by the owner of JOG System Engineering.
322-326 UML-SysML
Provisions for a future course covering an integrated application of unified modeling language (UML) and system modeling language (SysML) for software and systems modeling respectively or creating a UADF (see 32528).
322-327 DoDAF
Provisions for a future course covering integrated definition (IDEF) languages and Department of Defense Architecture Framework (DoDAF).
322-328 Universal Architecture Description Framework
The history of system and software engineering modeling for the purpose of understanding problem space and communicating the results of an analysis of problem space in the form of specifications is about to come full circle. This story emerged from the mud of the past in the 1950's with fairly universal application of flow charts and evolves through many modeling capabilities to an approaching merging of UML and SysML to form what the instructor calls a universal architecture description framework (UADF). There do seem to be a few pieces missing to completely cover the problem and solution space associated with all possible systems, however implemented, and that void is filled. The intent is to provide a single modeling capability that any enterprise can train its workforce to apply to any system development problem so as to produce a good set of specifications no matter how the system and its parts will be implemented.
This course will offer three views of a universal modeling capability to support the requirements analysis work for any system. The course is intended for system and software engineers. Some knowledge of modeling and system or software requirements and specifications work will be helpful. An INCOSE SEH reference is not included because the SEH does not include detailed modeling methods coverage. The GSD REF column references are to Jeff Grady’s textbook, “System Requirements Analysis” from Elsevier extended by an extensive paper that began life as an INCOSE Journal paper titled “Universal Architecture Description Framework” that was awarded the Journal best paper award for 2009 by INCOSE.
Course 322-328 Cross-Reference Matrix
LESSON TITLE GSD REF TEXT PAPER ---------------------------------------------------------------------------------------------------- 01 Introduction 1 1.1 1 02 Requirements Fundamentals 2 1.1 1 03 Architecture and Modeling 1.2 4, 11 04 Introduction to UADF 1.3, 4.1 2, 3, 9 05 MSA and PSARE 4.2 2.4 4.4 06 MSA and PSARE 07 MSA/PSARE UADF 4.4 08 UML and SysML UADF 4.4 2.5 4.2, 4.3 09 UML and SysML UADF 10 SYSML-UML UADF 4.3 6 11 SYSML-UML UADF 12 Workshop Time - - - 13 Functional Analysis 3.1, 3.2 2.1, 2.2 4.1 3.3 14 Functional Analysis Variations 3.9 4.1 15 Performance Requirements Analysis 3.4 2.2, 2.3 4.1 and the RAS 16 Product Entity Synthesis 3.5 2.3 4.1 17 Interface Identification and Definition 3.6 2.3 4.1 18 Specialty Engineering Requirements 3.7 2.3 4.1 19 Environmental Requirements 3.8 2.3 4.1 20 Functional Analysis UADF 4.2 21 Functional Analysis UADF 22 Universal Specification 5 2.2 23 Workshop Time - - - 24 IDEF and DoDAF Addition 4.5 2.6, 2.7 4.5 25 IDEF and DoDAF Addition 26 Management Infrastructure and the Future 6 5, 6 10, 13 27 Workshop Presentation - - -
322-33 OTHER QUARTER-BASED SYNTHESIS COURSES
322-332 Systems Effectiveness
There are many ways that specialty engineers support the success of the system development effort. A brief history helps to explain how these disciplines came into being. It also opens up a door that many would prefer to remain shut dealing with how specialty engineers are often treated on a development program. The work specific to several disciplines is then discussed not with the goal in mind of preparing the student to actually do the work but to prepare the system engineer to understand the benefits of having this work accomplished by professionals on a program.
Course 322-332 Cross-Reference Matrix
HR TOPIC TITLE GSD REF INCOSE SEH ---------------------------------------------------------------------------------------------------- 01 Introduction to Specialty Engineering 02 The Addition of Concurrent Engineering & IPPT 03 The Special Societal Problems 04 Reliability Overview 05 Reliability Modeling and Allocation 06 Failure Modes Effects and Criticality Analysis 07 Reliability Analysis, Prediction, and Verification 08 Maintainability Overview 09 Maintainability Modeling and Allocation 10 Maintainability Analysis, Prediction, and Verification 11 Availability Overview 12 RAM Workshop 13 Queuing Theory and Applications 14 Logistics Engineering Overview 15 Logistics Engineering Overview 16 Operability 17 System Safety Overview 18 Human Engineering Overview 19 Safety and Human Engineering Workshop 20 Security Engineering Overview 21 Parts, Materials, and Processes 22 Mass Properties 23 Life Cycle Cost 24 System Analysis Disciplines Overview
322-333 Systems Synthesis and Effectiveness
The course combines the synthesis and effectiveness courses though the semester-based course (321-432) is a better choice for this topic in that the two components do not have to be compressed to the extent necessary to fit both ideas within 24 contact hours.
322-34 OTHER QUARTER-BASED VERIFICATION COURSES
322-4 OTHER SEMESTER-BASED COURSES
322-40 OTHER SEMESTER-BASED OVERVIEW COURSES
322-402 Systems Overview
The overview course was originally developed for Applied Technology Institute (ATI) several years ago and is still offered once a year in a public forum on each coast. Refer to Section 313 of this web site for the public calendar under the course title “Total Systems Engineering Development and Management.” The whole system development life cycle process covered in four separate courses is discussed in four days, one day for each of the four fundamental development activities: (1) Management stretching across the whole program, (2) requirements, (3) synthesis, and (4) verification.
This course is an extended version of course 321-401 achieving the extension by doubling the length of the requirements component recognizing the relative difficulty of successfully performing the four component parts covered in the certificate program on the job.
Course 322-402 Cross-Reference Matrix
HR TOPIC TITLE GSD REF INCOSE SEH ---------------------------------------------------------------------------------------------------- 0 Course Introduction 1 Management Segment 1-1 Introduction to System Engineering 1-2 Development Process Overview 1-3 Program Process Transform 1-4 Organization Approaches and Teaming 1-5 Program Estimating and Earned Value Systems 1-6 Program Risk Management 1-7 System Engineering Maturity 2 Requirements Segment 2-1 Introduction to Requirements 2 2-2 Requirements Relationships 2-3 Requirements Elicitation and Mission Analysis 4.2, I.1, I.2, 2-4 System and Hardware Functional Analysis 4.3, 4.4, I.3, I.4, J.1, J.2 2-5 System and Hardware Functional Analysis K.1, K.2, K.3 Variations 2-6 Performance Requirements Analysis 2-7 Product Entity Synthesis 2-8 Interface Definition and Requirements Analysis 2-9 Specialty Engineering Requirements Analysis 2-10 Environmental Requirements Analysis 2-11 Computer Software Analysis Introduction and Early Models (Flow Charts, MSA, and PSARE) 2-12 OOA, UML, and SysML 2-13 DoDAF 2-14 Universal Architecture Description Frameworks 2-15 Requirements Management 2-16 Specification Publishing 7.2, I.5, J3 3 Synthesis Segment 3-1 Product Design 3-2 Trade Studies and Decision-Making 3-3 Configuration and Data Management 3-4 Interface Development 3-5 Specialty Engineering Integration 3-6 Engineering Domain Integration 3-7 Manufacturing, Quality, and Supplier Integration and Management 3-8 Program Phasing and Reviews 4 Verification Segment 4-1 Introduction to Verification 4-2 Item Qualification Requirements Identification 4-3 Item Qualification Top-Down Planning and Documentation 4-4 Item Qualification Bottom-Up Planning and Documentation 4-5 Item Qualification Implementation, Reporting, Management, and Audit 4-6 Item Acceptance 4-7 System Test and Evaluation Overview 4-8 System Engineering Maturity
322-41 OTHER SEMESTER-BASED MANAGEMENT COURSES
322-42 OTHER SEMESTER-BASED REQUIREMENTS COURSES
Courses offered in this section will require four days to complete when offered in a short course format or one university semester (four months) when offered a few hours a day or evening one or two times per week. Outlines can be tailored to best match client needs.
322-422 Systems Requirements Analysis
The semester based version of course 222 covers requirements analysis in the context offered by the course UADF and management so it is a thoroughly up-to-date requirements course supporting the next system engineering paradigm. As in all requirements courses offered by JOG System Engineering it encourages that all requirements be derived from models and it offers several universal architecture description frameworks to support that capability.
Course 322-422 Cross Reference Matrix
HR TOPIC TITLE GSD REF INCOSE SEH ---------------------------------------------------------------------------------------------------- 01 Introduction 02 Requirements Fundamentals 03 Specification Structures 04 Specification Practices 05 Applicable Documents, Laws, and Regulations 06 Introduction to the Use of Computer Tools 07 Modeling Fundamentals 08 Value Engineering 09 Initial System Analysis 10 Functional Analysis 11 Functional Analysis Variations 12 Performance Requirements Analysis 13 Product Entity Synthesis 14 Interface Identification and Definition 15 Interface Identification and Definition 16 Specialty Engineering Requirements 17 Environmental Requirements 18 Vertical and Longitudinal Traceability 19 Lateral Traceability and Modeling Work Capture 20 Requirements Risk Management 21 Margins and Budgets 22 Verification Overview 23 Precedented Development Differences 24 Introduction to Computer Software Analysis 25 Modern Structured Analysis 26 PSARE 27 PSARE 28 Early OOA 29 Unified Modeling Language 30 Unified Modeling Language 31 SysML 32 DoDAF 33 DoDAF 34 Universal Modeling Using Flow Charting 35 Universal Modeling Using SysML and UML 36 Universal Modeling Using SysML and UML 37 Starting With Functional Analysis and UML 38 Universal Modeling Using PSARE 39 Universal Modeling Using PSARE 40 Future of Model-Driven Development
322-424 Systems Requirements Management
322-428 Universal Architecture Description Framework
This course recognizes that many very bright people invented systems modeling methods over the past 50-60 years but that few had made any attempt to integrated and optimize across these models. Thus there is no single comprehensive model available to those developing new systems. The course offers three universal architecture description frameworks (UADF) each constructed from available models. Any one of these models can be applied comprehensively to every program an enterprise might undertake no matter how it chooses to implement the design in hardware, software, and people doing things.
The references in the GSD REF column of the outline are in the form “m.n” where “m” is the part and “n” is the chapter in the Elsevier textbook “System Requirements Analysis”. If there is a number after the chapter “n” it refers to a paragraph number within that chapter. The DIV 1 column provides references to a text supplied in Division 1 of the student manual with this course that is supplementary to the content of the published book. The Division 1 text was derived from a paper written by Jeff Grady for the INCOSE Journal and selected as best Journal paper of 2009. The paper was edited to coordinate as Part 9 of the Elsevier book. Refer to the table of contents of Division 1 for page numbers in the content of Division 1 text material.
The INCOSE column in the table provides references to paragraph numbers in the INCOSE System Engineering Handbook of particular help to people taking this course as preparation for the INCOSE certification exam.
Course 322-428 Outline
HR TOPIC TITLE GSD REF DIV 1 INCOSE ---------------------------------------------------------------------------------------------------- 01 Introduction 1 1 2.1, 2.2, 2.3, 2.7, 2.8, 3, 8.4 02 Requirements Fundamentals 2.1, 2.3 - 8 03 Specification Fundamentals 5.1 - 8.5 04 Modeling Fundamentals 3.2 - - 05 The Appeal of Computer Tools 2.8 - 9.3 06 Initial System Analysis 3.1 - 8.1, 8.2, 11.6, 11.8 07 Initial System Analysis (Continued) 3.1.1, 11.16 08 Functional Analysis 3.1, 9.3.1 9.1, 9.2, D.1, D.3 3.3 D.5, D.9, 8.3, 8.4 09 Functional Analysis Variations 3.9 9.3.1 9.5 10 Performance Requirements Analysis 3.4 9.3.1 8.3, D.4, 9.2.2 11 Product Entity Synthesis 3.5 9.3.1 10 12 Interface Identification and Definition 3.6 9.3.1 D.2, 9.2.4 13 Interface Identification and Definition 14 Specialty Engineering Requirements 3.7 9.3.1 11.9-11.15, 11.3, Analysis 11.5, 11.6, 11.7 15 Environmental Requirements Analysis 3.8 9.3.1 11.4 16 Introduction to UADF 9.1, 9.2 17 Introduction to Computer Software 4.1 - - Analysis Early Methods 18 Modern Structured Analysis 4.2 9.3.4 D.7 19 PSARE 9.3.4 20 UADF Using MSA/PSARE 9.3.4 21 Unified Modeling Language 4.4 9.3.2 D.8 22 Unified Modeling Language (Continued) 23 System Modeling Language (SysML) 9.3.3 24 UADF Using UML/SysML 9.3.2, 9.3.3 25 DoDAF 4.5 9.3.5 - 26 DoDAF (Continued) - 27 IDEF and OOA Exclusion 4.4 - D.8 28 Specification Update - - - 29 Total Traceability - 9.5.1 30 Modeling Work Capture 3.11 - - 31 Modeling Work Capture 32 Future of Model-Driven Development 8 9.6 -
322-429 Systems Requirements and Verification
322-43 OTHER SEMESTER-BASED SYNTHESIS COURSES
322-432 Systems Effectiveness
322-433 Systems Synthesis and Effectiveness
322-44 OTHER SEMESTER-BASED VERIFICATION COURSES
323 SPECIAL COURSE CONFIGURATIONS
These courses have been assembled from parts of other courses to satisfy specific client needs. They may require 2, 3, or 4 days to complete.
323-1 Composite Management Courses
323-2 Composite Requirements Courses
323-21 Total Systems Requirements
323-22 Systems Requirements and Verification
323-3 Composite Synthesis Courses
323-31 Enterprise, Program, and Product Systems Synthesis
324 CLIENT COURSE DEVELOPMENT AND SALE
JOG System Engineering develops system engineering courses for sale to companies based on their requirements. Generally, these courses are taught once by JOG System Engineering followed by delivery of the course materials. Courses have been built for FAA, Raytheon, BAE Systems, General Dynamics Land Systems Division, and Cubic in the past. These courses are owned by the client subsequent to delivery and cannot be offered by JOG System Engineering to other parties. The cost of these courses is negotiated individually because of the variation in the difficulty of building the course.