Ph.D. Systems Engineering
Program Proposal
Presented To:
Dr. Jerrell Stracener
Founding Director, Systems Engineering Program (SEP)
Southern Methodist University
December 15, 2008
Prepared By:
Southern Methodist University (SMU)
SEP Development Team (DT)
PhD Systems Engineering Program Proposal Project Team
Tim Woods
Proposal Team Co-Lead
Dr. Jim Hinderer
Proposal Team Co-Lead
i
Acknowledgements
The leaders of the team would like to acknowledge the efforts placed forward by
the SMU Systems Engineering Development Team (SEP DT) Proposal Team
Members and thank them for their contributions and time in this important activity.
Our gratitude goes out Dr. Jerrell Stracener for his guidance and mentoring
during this activity. This activity would not have been possible without the team’s
efforts and we appreciate all their efforts and time. The SEP DT Proposal Team
Members are listed below.
2
SMU Systems Engineering Development Team Proposal Team Members
Member
Ala AlZubi
Karl Arunski
Chris Askew
Dave Bell
Yvonne Bijan
Brad Blau
Bill Bolick
Keith Castleberry
George Chollar
Gunter Daley
Mike Dietz
Long Dong
Magen Ellis
Floyd Fazi
Rad Field
Olivia Han
Mike Harper
Jim Hinderer*
Mike Hopper
Rusty Husar
Matt Kendall
Sharon Kendall
Michael Kutch
Mike Kutch
Bill Linn
Richard Mcfarland
Randy Moore
Linda O’Brien
Dave Peercy
Jim Rodenkirch
George Salazar
Steve Skinner
Jerrell Stracener
Chris Thompson
Timothy Tsia
Brent Well
William Westerman
Tim Woods*
David Wu
Joe Zarrehparvar
* - Team Leads
Company Affiliation
Texas Instruments
Raytheon Intelligence & Information Systems
Lockheed Martin Missiles & Fire Control
The MITRE Corporation
Lockheed Martin Aeronautics Company
US Navy JTRS
Diversified Technology Incorporated
Boeing Aerospace Support Division
Statistical Design Institute, LLC
Siemens Government Services
Raytheon Space and Airborne Systems
Lockheed Martin Aeronautics Company
Lockheed Martin Missiles & Fire Control
Lockheed Martin Aeronautics Company
SMU
U.S. Navy Office of Assistant Secretary
Raytheon Space and Airborne Systems
L3 Com Integrated Systems
U.S. Navy SPAWAR
Raytheon Network Centric Systems
Raytheon Network Centric Systems
U.S. Army Information Systems Engineering Com
U.S. Navy SPAWAR Systems Center
L-3 Com Integrated Systems
Lockheed Martin Aeronautics Company
Lockheed Martin Aeronautics Company
Bell Helicopter
Sandia Labs
Rodenkirch, LLC (US Navy ret)
NASA JSC
Bell Helicopter
SMU
BAE Systems
Texas Instruments
Raytheon Space and Airborne Systems
Networking Embedded Systems, Inc.
Lockheed Martin Aeronautics Company
Lockheed Martin Aeronautics Company
Location
Richardson, TX
Garland, TX
Grand Prairie, TX
McLean, VA
Fort Worth, TX
San Diego, CA
Ridgeland, MS
Ft. Walton, FL
Dallas, TX
Richardson, TX
Dallas, TX
Fort Worth, TX
Grand Prairie, TX
Fort Worth, TX
Dallas, TX
Dallas, TX
Washington, DC
Dallas, TX
Greenville, TX
San Diego, CA
McKinney, TX
McKinney, TX
Ft. Huachuca, AZ
Charleston, SC
Greenville, TX
Fort Worth, TX
Fort Worth, TX
Fort Worth, TX
Albuquerque, NM
St. George, UT
Houston, TX
Fort Worth, TX
Dallas, TX
Merrimack, NH
Richardson, TX
McKinney, TX
Fort Worth, TX
Fort Worth, TX
Fort Worth, TX
Dallas, TX
3
Table of Contents
1
Executive Overview .................................................................................... 5
2
Introduction ................................................................................................ 5
3
SMU Ph.D. in Systems Engineering Program Description ......................... 6
3.1
Ph.D. SE Program Resources.................................................................. 13
3.1.1
Full time faculty..................................................................................... 13
3.1.2
Adjunct faculty ...................................................................................... 14
3.2
SMU Systems Engineering Program Courses – Current and Proposed .. 15
3.3
Ph.D. SE Applicants and Transfers .......................................................... 39
3.3.1
Ph.D. SE Applicants for January ‘09 Start ............................................ 39
3.3.2
Ph.D. Transfers to Ph.D. SE Program .................................................. 39
3.4
U.S. Ph.D. SE Program Benchmarks ....................................................... 40
3.4.1
Summary of US Ph.D. SE and Related Programs ................................ 40
3.4.2
Comparison and Contrast of Proposed SMU Ph.D. SE Program to
Benchmark Programs ......................................................................................... 40
3.5
Ph.D. SE Planning Guide ......................................................................... 43
Appendix A – Systems Engineering Program Development Team (SEPDT)
Benchmarking Team Final Report ...................................................................... 44
Table of Figures
Figure 1 Analytical Comparison .......................................................................... 43
Table of Tables
Table 1 – Programs Chosen For Final Evaluation Comparison .......................... 40
Table 2 - Attribute Comparison ........................................................................... 42
4
1 Executive Overview
SMU currently offers a Ph.D. in Applied Science, with a concentration in Systems
Engineering, but does not offer a Ph.D. in Systems Engineering. A forty member,
volunteer team was charted as part of SMU’s Systems Engineering Program
Development Team (SEP DT) to assist in developing the proposal for SMU’s
Ph.D. in Systems Engineering program. This effort was initiated in response to
the strong need indicated by employees in the United States Aerospace and
Defense sector, both industry and government.
The team was identified as the Proposal Team and derived from members of the
SEP DT. Team co-leads were Mr. Tim Woods, a Ph.D. Candidate in Systems
Engineering at SMU, and Dr. Jim Hinderer, an Adjunct Professor of Systems
Engineering at SMU. Dr. Jerrell Stracener, SMU Systems Engineering
Program’s founding director, provided consultation and worked closely with the
team. The goal of the team was to write the proposed description of the program,
gather SEP DT data on current Ph.D. in SE programs in the United States and
use the data to support SMU’s Ph.D. SE program proposal.
The Benchmarking Team started gathering data in August 2008 and finished this
proposal in November 2008. This effort utilized the Systems Engineering PhD
Programs Benchmarking final report released by the SEP DT on August 1, 2008.
This report is the culmination of research and analysis and was provided to Dr.
Stracener in November of 2008 as source material for the Ph.D. in Systems
Engineering Program Proposal at SMU.
2 Introduction
This project was chartered by Dr. Jerrell Stracener, SMU Systems Engineering
Program Founding Director, to develop a proposal for a Ph.D. in Systems
Engineering (SE) program reflecting industry and government needs for such a
program and capabilities. He requested that Mr. Tim Woods and Dr. Jim
Hinderer lead the development team. The co-leaders, with assistance from
Jerrell Stracener, assembled a team of industry and government affiliated
personnel. This proposal is the work of the team with close coordination with
Jerrell Stracener.
5
3 SMU Ph.D. in Systems Engineering Program Proposal
Ph.D. Systems Engineering Program (SEP) Description
The Systems Engineering Program is designed to develop expertise for
development and management of systems (products and services) to satisfy
customer requirements, while considering engineering, technology,
environmental, management, risk, and economic factors by viewing the system
as whole, over its life cycle using systems engineering principles, methods and
practices. “Systems thinking” skills are developed which foster more effective
practice for engineers or engineering managers within the business enterprise.
The objective is to provide individuals with the capability to effectively manage
the development and sustainment of complex systems in an ever changing
global environment.
SEP Development
The SMU Systems Engineering Program was developed as a partnership based,
requirements driven program for formally educating students in both the theory
and practice of Systems Engineering.
Introduction
Students receiving a Ph.D. in Systems Engineering are expected to achieve and
demonstrate a mastery of the discipline and to significantly advance the state of
knowledge through an original research effort.
The graduation requirements fall into the categories of completion of a specified
number of graduate credits in appropriate subjects with an acceptable grade
point average, demonstration of understanding of the discipline of Systems
Engineering as evidenced by examination, and, completion of a substantial
research effort documented in a doctoral dissertation.
All requirements must be completed within 7 years of entry into the program.
The steps for completion of the doctoral program are:
6
1.
2.
3.
4.
Initial advising
Basic course work preparatory to the commencement of research work
Selection of a research advisor and supervisory committee
Advanced course work in the chosen research area and guided
dissertation research preparatory to taking the qualifying examination
5. Successful completion of the qualifying examination as determined by
the doctoral advising committee
6. Dissertation research supervised by the candidate’s doctoral advisor
7. Successful defense of the research leading to the Ph.D.
Admission Requirements
Prerequisites to admission to the Ph.D. program are:
Attainment of a Master of Science degree in Systems Engineering or a
related field including Aerospace Engineering, Computer Science,
Electrical Engineering, Engineering Management, Environmental
Engineering, Civil Engineering, Industrial Engineering, Mechanical
Engineering, Mathematics, Statistics, or Physics. In the case of direct
admission without a previous Master of Science degree, the
Baccalaureate degree must be conferred prior to the time the student
begins classes as a graduate student, and the student will fulfill the
requirements for and obtain a Master of Science degree and then
continue working toward the Ph.D. Also, the student’s Grade Point
Average (GPA) must be at least 3.4 on a 4.0-point basis in the
student's junior and senior years.
The student should possess a reasonable level of mathematical
maturity.
All applicants to the Graduate Division with less than 10 years
professional experience in engineering or related technical field must
submit an official Graduate Record Examination (GRE) general test
score before their application can be considered.
Foreign students are required to submit their scores on the Test of
English as a Foreign Language (TOEFL) or its equivalent in addition to
the GRE scores.
The student must receive approval by the Director of the Systems
Engineering program for admission to the Ph.D. program.
7
Minimum of three years industry and/or government engineering
experience preferred.
Initial Advising
Upon entry into the Ph.D. program, students are assigned a faculty advisor who
acts as an academic advisor. The responsibilities of this advisor are to examine
the student's prior background and current state of knowledge, and to
recommend courses to be taken in preparation for the commencement of
research work.
Credit Requirements
A minimum of 54 graduate credits is required beyond the Baccalaureate degree
in order to achieve the Ph.D. degree. In addition to these 54 hours, 24 hours are
required for dissertation credit. Of the 54 graduate credits, a maximum of 30
credit hours may be used if an entering student possesses an M.S. in an
appropriate major from another institution. The following core courses must be
taken at SMU if the student has not received credit for these at another
university:
EMIS 7300 Systems Analysis Methods
EMIS 7301 Systems Engineering Process
EMIS 7303 Integrated Risk Management
EMIS 7305 Systems Reliability, Supportability and Availability Analysis
EMIS 7307 Systems Integration and Test
A minor of a minimum of 12 credits supporting the chosen research area is
required. These courses may be taken in EMIS or a department separate from
EMIS. The minor requirement may be satisfied by transfer credit.
Grades
No graduate credit is earned for a course in which a grade of less than "C-" is
earned. Such courses do, however, count toward the total GPA. In order to
graduate, a student must have a GPA of at least 3.0 on a 4.0 scale. If at any
point a student's GPA drops below 3.0, the student is placed on academic
probation. The student then has one semester to raise his/her GPA back up to
8
3.0 or be dismissed from the program. For part-time students, one semester is
taken to mean 6 credit hours. It is the policy of the School of Engineering that
courses in which an "Incomplete" is granted affect the GPA effective the
semester in which the Incomplete was granted rather than when it is removed.
Therefore, a student should consider himself/herself to be on academic probation
if the grade on currently completed work in the course in which the "I" was
granted would cause the GPA to drop below 3.0.
Advanced Study
Advanced study in Systems Engineering consists of a major concentration area.
A concentration area consists of a number of courses that are related to a
specific sub-field of Systems Engineering. The major concentration consists of a
minimum of 18 credits, no more than 6 of which can be independent study.
Credit earned for the core courses (EMIS 7300, 7301, 7303, 7305, and 7307) will
not be counted for the concentration area. The student must file an Advanced
Study Degree Plan with the department. No degree plan is accepted until
approved by the Chair of EMIS. Credits received prior to filing a degree plan are
not guaranteed to count toward graduation.
Research Advisor and Supervisory Committee
Within two semesters from joining the Ph.D. program, the student must obtain a
research advisor and form a supervisory committee. It is the responsibility of the
student to find a faculty member willing to provide a research topic or to
supervise a topic of the student's choosing. The research advisor must be one of
the full-time faculty members of the EMIS department. The research advisor,
together with the student, should prepare the Advanced Study Degree Plan
discussed above. They should also form the supervisory committee. The
supervisory committee is made up of at least five members. Three resident
tenured or tenure-track faculty members are drawn from the student’s
department and one resident tenured or tenure-track faculty member from each
minor field. The chair of the supervisory committee shall be a resident tenured or
tenure-track member of the school faculty and shall normally be the dissertation
director and a member of the student’s department. Thus, a minimum of four
members must be resident tenured or tenure-track faculty of Southern Methodist
9
University. The supervisory committee must be submitted to the Chair of EMIS
and the Director of the Graduate Division for approval.
Preliminary Counseling Examination and Program of Study
To be eligible for advanced study, a student must demonstrate competence in
Systems Engineering fundamentals by passing the Preliminary Counseling
Examination (PCE). This exam is oral and is administered by three faculty
members. Particular emphasis will be given to the material covered in the
following courses: EMIS 7300, 7301, 7303, 7305, and 7307.
Qualifying Examination
The student must complete all the core courses with an average grade of B+ or
better before he/she can appear for the qualifying exam. The student will give a
written proposal to the committee members. The timing of this submission will be
determined by the thesis advisor and usually occurs at the 40-50% completion
point of the thesis research.
Committee members will submit questions to the Ph.D. dissertation director; the
director and the members will negotiate the content of the questions. The
questions will generally be from areas related to the student’s area of research
and hence the questions will be submitted only after student has submitted the
written proposal. However, should a majority of the committee judge that the
student has not shown strong credentials in one or more of the core areas, the
examination may include questions designed specifically to determine whether or
not the student has sufficient background in those areas. The chair, along with
the other members will decide the outcome (Pass/Fail) of the exam.
Students will have a maximum of two attempts to pass the qualifying examination.
If a student changes her/his area of research significantly, or if significant
changes are made to the composition of the supervising committee, the student
may be required to repeat the qualifying examination.
Change of Committee or Concentration
10
A student may change concentration, research advisor, or supervisory committee
at any point, subject to the approval of the EMIS faculty. Such a change will
generally require the formation of a new supervisory committee, and will
definitely require the filing of a new advanced study plan. The student must take
a qualifying examination in the new concentration area to be admitted to
candidacy. In the event that the student changes concentration after being
admitted to candidacy, the candidacy is revoked and the student must pass the
qualifying examination in the new concentration. Two attempts are allowed for a
student in this position. A student may also change areas before being admitted
to candidacy. In this event, it is possible that one or more unsuccessful attempts
will have been made to pass the qualifying examination. The student may, at the
discretion of EMIS, be allowed two attempts in the new concentration, but under
no circumstances will more than three attempts be allowed at the exam. It is also
possible that a student will change research advisor or composition of the
supervisory committee, while still retaining the same concentration areas. Such
changes may be made only with the approval of EMIS. If the research advisor is
changed, the new research advisor may, at his/her discretion, require a new
qualifying examination. In addition, if the make-up of the supervisory committee
changes substantially, EMIS may require a new qualifying examination to be
taken with the newly constituted committee.
Doctoral Dissertation
The most clearly distinguishing characteristic of a program leading to the Ph.D.
degree is the requirement that the candidate write a dissertation embodying the
results of a significant and original investigation. The dissertation must make a
real contribution to the systems engineering discipline, and it is expected to be a
mature and competent piece of writing. The work reported in the dissertation may
be basic scientific research, engineering research, creative design or a
combination thereof.
The typed original and five copies of the dissertation, each including a copy of
the abstract, must be delivered, together with two extra copies of the abstract
and one extra title page, to the director of the Graduate Division before the
examination period in a regular semester and before examinations in a summer
term. Upon the successful completion of the dissertation defense, the original
11
abstract must be signed by the dissertation advisor, and the original half-title
page of the dissertation must by signed by all of the EMIS faculty members
attending the dissertation defense.
A copy of the bound dissertation will be sent to the student as soon as it is
available following successful completion of the dissertation defense.
Dissertation Defense (Final Examination)
Upon completion of all other requirements, a dissertation defense of the
candidate will be announced, registered with the Graduate Division, and
subsequently conducted by the supervisory committee. The candidate must
make six unbound copies of his dissertation available to the Graduate Division
for distribution to the members of the supervisory committee at least two weeks
in advance of the dissertation defense. This defense, which is conducted orally,
must enable the supervisory committee to satisfy itself that the dissertation is an
original piece of work, either in research or creative design, that it has been
carried out in keeping with the highest standards of investigation and reporting,
and that it makes a contribution to knowledge that is of value to the engineering
profession or scientific community. The defense must be scheduled with the
EMIS departmental office and posted in the School of Engineering. This defense
is open to the public, with the possible exception of a period during which general
questions in Systems Engineering may be asked that is open only to committee
members and EMIS faculty. Satisfactory performance on this defense constitutes
the last requirement to be met for the Ph.D. degree.
12
3.1 Ph.D. SE Program Resources
3.1.1 Full time faculty
The current SMU Lyle School of Engineering full time faculty that are engaged in
systems engineering related teaching and/or research are listed below:
SMU Systems Engineering and Related Faculty – Resident
Faculty
Name
Khaled F. Abdelghany
Frank P. Coyle
LiGuo Huang
Eli V. Olinick
Stephen A. Szygenda
Jeff Tian
Mitchell Thornton
Jerrell T. Stracener
Sukumaran V. S. Nair
JunFang Yu
Title
Assistant Professor
Senior Lecturer
Assistant Professor
Associate Professor
Professor
Associate Professor
Professor
Scholar in Residence
Professor and Chair
Assistant Professor
Department
ECE
CSE
CSE
EMIS
EMIS / CSE
CSE / EMIS
CSE / EE
EMIS
CSE
EMIS
13
3.1.2 Adjunct faculty
The current SMU Systems Engineering Program’s adjunct faculty are listed
below.
SMU SE and Related Faculty – Adjunct Faculty
Name
Affiliation
Arunski, Karl
Askew, Chris
Bell, Bob
Bell, Dave
Broihier, Ann
Chollar, George
Cluff, Kevin
Cochran, David
Cowin, Howard
Daley, Gunter
Delzer, Dennis
Durchholz, Matt
Frailey, Dennis
Hinderer, Jim
Harper, Mike
Ibarra, Gerard
Lipp, John
Mutto, Bill
Oshana, Rob
Rodenkirch, Jim
Rynas, Chris
Sampson, Mark
Skinner, Steve
Vacante, Russell
Wiebelhaus, Dan
Williams, Jeff
Raytheon Intelligence & Information Systems
Lockheed Martin Missiles & Fire Control
Lockheed Martin Aeronautics Company
Mitre Corporation
Raytheon Network Centric Systems
Statistical Design Institute
Abbott Laboratories
Systems Design, LLC
Lockheed Martin Missiles & Fire Control
Siemens Government Services
Raytheon Space and Airborne Systems (Ret)
Lockheed Martin Missiles & Fire Control
Raytheon Space & Airborne System
Raytheon Space and Airborne Systems
L-3 Communications Integrated Systems
Systems Engineering Program - Research
Lockheed Martin Missiles & Fire Control
Abbott Laboratories
Freescale Semi conductor
Diversified Technology Inc.
Raytheon Space and Airborne Systems
Siemens Automation
Bell Helicopter
US DoD Defense Acquisition University
Lockheed Martin Missiles & Fire Control
Bell Helicopter
14
3.2 SMU Systems Engineering Program Courses – Current and
Proposed
The following is a listing of the SMU SE program current and proposed courses.
Current Systems Engineering Courses
EMIS
EMIS
EMIS
EMIS
EMIS
7300
7301
7303
7305
7307
Systems Analysis Methods
Systems Engineering Process
Integrated Risk Management
Systems Reliability, Supportability and Availability Analysis
Systems Integration and Test
EMIS 7310
EMIS 7312
Systems Engineering Design
Software Systems Engineering
EMIS
EMIS
EMIS
EMIS
EMIS
EMIS
EMIS
7315
7318
7320
7330
7335
7340
7347
Systems Architecture Development
Systems Engineering Planning and Management
Systems Engineering Leadership
Systems Reliability Engineering
Human-Systems Integration
Logistics Systems Engineering
Critical Infrastructure Protection/Security Systems Engineering
EMIS
EMIS
EMIS
EMIS
EMIS
EMIS
EMIS
8305
8307
8310
8315
8340
8342
8348
Systems Life Cost & Affordability Analysis
Systems Test and Evaluation
Collective Systems Design
Innovation Systems Design
Systems Engineering Software Tools
Six Sigma Systems Engineering
Supply Chain Systems Engineering
15
Proposed Courses (In Work)












Introduction to Systems Engineering (Undergraduate Course)
Acquisition Logistics Systems Engineering
Sustainment Logistics Systems Engineering
Systems Requirements Engineering
Systems Modeling and Simulation
Systems Program Engineering and Management
Systems Program Management
Systems Engineering for IPT leads
Systems Analysis for Decision Making and Control
Survey of Systems Engineering Body of Knowledge
System of Systems Integration and Interoperability System Engineering
Systems Requirements Engineering
The course descriptions for the current courses are shown in the following pages.
16
EMIS 7300 - SYSTEMS ANALYSIS METHODS
COURSE DESCRIPTION
Introduction to modeling and analysis concepts, methods and techniques used in
systems engineering, design of products and associated production and logistics
systems, and analysis of operational system performance. Specific Topics
include: probabilistic and statistical methods, Monte Carlo Simulation,
optimization techniques, applications of utility theory and decision analysis.
COURSE OBJECTIVES
To provide students with an introduction to a variety of analysis types with
emphasis on application to provide a framework for engineering decision making,
including situations in which uncertainty and risk are important.
PREREQUISITES
None
COURSE TOPICAL COVERAGE
 Course Policies and The Role of Probability and Statistics in Engineering
 Sample Spaces and Events
 Interpretations of Probability and Axioms of Probability
 Bayes' Theorem and Revising Probabilities with Bayes' Theorem
 Discrete Random Variables
 Discrete Random Variables: The Uniform and Binomial Distributions
 Discrete Random Variables: Applications of the Binomial Distribution
 Discrete Random Variables: The Geometric and Negative Binomial Distributions
 Discrete Random Variables: The Hypergeometric Distribution
 Discrete Random Variables: The Poisson Distribution
 Midterm Exam 1
 Continuous Random Variables
 Continuous Random Variables: The Normal Distribution
 Continuous Random Variables: The Exponential Distribution
 Continuous Random Variables: The Erlang, Gamma, Weibull, and Lognormal
Distributions
 Random Samples and Data Descriptions
 Monte Carlo Simulation
 Queuing Models
 Decision-Making Under Uncertainty
 Midterm Exam 2
 Decision-Making Under Risk
 Utility Theory
 Intro. To Linear Programming
 Review for Final Exam
 Final Exam
COURSE OWNER(S)
Jerrell Stracener, PhD / Eli V. Olinick, PhD
17
EMIS 7301- SYSTEMS ENGINEERING PROCES
COURSE DESCRIPTION
The discipline, theory, economics, and methodology of systems engineering is
examined. The historical evolution of the practice of systems engineering is
reviewed, as are the principles that underpin modern systems methods. The
economic benefits of investment in systems engineering and the risks of failure to
adhere to sound principles are emphasized. An overview perspective distinct
from the traditional design- and analytical-specific disciplines is developed.
COURSE OBJECTIVES
The objective of the course is to provide students with an introduction to systems
engineering fundamentals. This course is an introduction to systems engineering.
It treats systems as a hierarchy of products and then handles each process in
exactly the same way. The course covers program phases and products, and
outlines how to control the systems engineering process. It covers requirements,
design, acquiring products, integration, verification, and sell off. In addition, it
discusses processes, teaming, and the Capability Maturity Model Integrated
(CMMI) assessment method.
PREREQUISITES
None
COURSE TOPICAL COVERAGE
 Course overview, products, cycles, product-base-development-approach, and
definition of system engineering
 Understanding requirements, a.k.a. requirements analysis
 Design
 Design details
 Decision tables
 Acquisition of lower products, and integration
 Verification of requirements, and tracing
 Development examples
 Schedule, budget, and risk control
 Mid-term exam
 Planning, configuration, and environment control
 System engineering processes
 Implementations of system engineering
 Measurements of system engineering
 Final exam
COURSE OWNER(S)
Jim Hinderer, PhD
18
EMIS 7303 - INTEGRATED RISK MANAGEMENT
COURSE DESCRIPTION
An intermediate level approach to systems engineering from a risk management
perspective. Integrated trade studies of program performance, cost, and
schedule requirements are conducted with the aid of risk assessments. Topics
include program planning, requirements management, risk identification and
assessment, risk handling and abatement, risk impact analyses, management of
risk handling and abatement, and subcontractor risk management. Systems
engineering management methods, procedures, and tools are examined.
COURSE OBJECTIVES
PREREQUISITES
None
COURSE TOPICAL COVERAGE
 Course overview, introduction, and what is a risk
 Systems engineering (SE) fundamentals and risk management
 Risk management sub processes
 Risk and its relationship to requirements, and work breakdown structures
 Risk and its relationship to technical reviews, metrics, trade studies
 Integrated systems engineering and risk assessment project
 Risk assessment and identification concepts
 Risk assessment and identification techniques
 Cost risk and exposure
 Risk quantification approaches and metric development
 Techniques for defining individual risk issues for engineering management
 Mid Term Exam
 Alternate methods for assessing risk
 Risk handling and mitigation approaches
 Mitigation plan development and waterfalls
 Willoughby Templates and Best Practices
 Mitigation plan tracking and status techniques
 Subcontractor risk management
 Subcontractor risk and competitive supplier selection
 Risk information management systems and tools
 Schedule risk assessments and Monte Carlo tools
 The risk mitigation plan project
 Metrics
 Mitigation planning and schedule integration
 Risk management plan development
 Final Exam
COURSE OWNER(S)
Bob Bell
19
EMIS 7305 - Systems Reliability, Supportability and Availability
Analysis
COURSE DESCRIPTION
This course is an introduction to systems reliability, maintainability, supportability
and availability (RMS/A) modeling and analysis with an application to systems
requirements definition and systems design and development. Both deterministic
and stochastic models are covered. Emphasis is placed on RMS/A analyses to
establish a baseline for systems performance and to provide a quantitative basis
for systems trade-offs.
COURSE OBJECTIVES
To provide students with an understanding of systems analysis and optimization
as a basis for product and service engineering and development decisions based
on tradeoffs involving multiple alternatives and uncertainty, for application in
industry and government as well as in other engineering courses.
PREREQUISITES
EMIS 7300 and 7301, or equivalent
COURSE TOPICAL COVERAGE
 Reliability Modeling & Analysis
 Reliability Models: Deterministic and Stochastic
 Systems Reliability Analysis
 Systems Reliability Trade-offs and Optimization
 Supportability Modeling and Analysis
 Maintainability
 Prognostics and Health Management
 Level-of Repair Analysis
 Reliability Centered Maintenance Analysis
 Supply Support Analysis
 Availability Modeling and Analysis
 System Availability Models: Deterministic & Stochastic
 System Availability Model Development
 System Availability Analysis
 System-Level Trade Studies
COURSE OWNER(S)
Jerrell Stracener, PhD
20
EMIS 7307 - Systems Integration and Test
COURSE DESCRIPTION
This course is an introduction to the management of systems integration and testing (I&T).
Topics include the systems engineering process, specification development for improved I&T,
design reviews, A Spec writing, Systems Engineering Master Plan (SEMP) development, Test
and Evaluation (TEMP) development, verification and analysis considerations
COURSE OBJECTIVES
To prepare students with diverse technical backgrounds and objectives with fundamental
concepts and ideas suitable for use in continuing graduate studies and in engineering &
engineering management through a balance of theory and application involving engineering
decision making in the I&T and T&E environments. Emphasis is placed on early advocacy of
I&T and T&E perspectives in the systems engineering process and design flow.
PREREQUISITES
Graduate student status
COURSE TOPICAL COVERAGE















Explanation of the projects, homework assignments and the grading scheme. Review and overview of Systems
Engineering, it’s need and vocabulary. System I&T definition and relationship to System Engineering.
The I&T perspective and resultant effect on the Systems Engineering process. Review the systems engineering
process as related to I&T.
Specification and design criteria. The design process. Review of the ‘ilities’. I&T/T&E perspective on design
requirements i.e. creating requirements that are verifiable and designs that facilitate integration
I&T role in formal design reviews i.e. conceptual, system, preliminary and critical design reviews. I&T/T&E
perspective when making make vs. buy decisions. Special issues related to COTS and integration. I&T role in
program planning.
First midterm exam
Developing the SEMP including SOW, WBS, spec tree, TPMs, schedules, cost projections. Interface
documentation, risk management and safety plans. Special considerations for spiral development.
Verification types i.e. analysis, demonstration, test, inspection and simulation. The applicability of each type to
the way a requirement is written. Criteria for selecting the verification type when writing Section 4 of an A-spec
and subservient specs. Analysis considerations.
Analysis considerations continued. Management of T&E. How to deal with and make use of required IV&V.
How to write a TEMP. DOD5000 implications to I&T/T&E. Making earned value work for the I&T or T&E
manager. Developing an I&T friendly WBS.
Second Midterm Exam
T&E planning, Industry support of T&E and TEMP.
Developmental tests the various types, uses and responsibilities.
Operational tests, the various types, uses and responsibilities. Importance of OT&E to the commercial as well
as military markets.
Organizational considerations to facilitate I&T. Use of IPTs, including integrated test teams, to improve both
technical and cost/schedule performance. Use of concurrent engineering to improve time to market without
negatively effecting the I&T process
Specialized testing. Course Recap
Final Exam
COURSE OWNER(S)
William D. Bell, D. Eng.; Mike Hopper, D. Eng
21
EMIS 7310 - SYSTEMS ENGINEERING DESIGN
COURSE DESCRIPTION
This course is an introduction to system design of complex hardware and software
systems. Specific topics include design concept, design characterization, design
elements, reviews, verification and validation, threads and incremental design,
unknowns, performance, management of design, design metrics, and teams. The class
will center on the development of real-world examples
COURSE OBJECTIVES
The objective of the course is to provide students with an introduction to systems
engineering design. It covers designing systems including concept, partitioning, and
design details. The course discusses thread analysis, structure analysis, and objectoriented design. The course covers mathematics for system engineering, interfaces,
vibration, power, cooling, sensors, signal processing, and control..
PREREQUISITES
None
COURSE TOPICAL COVERAGE
 Course overview, and basics of design
 Details of design
 Design documentation
 Architectural design
 Functional design
 Interface design
 Sensors
 Mid-term exam
 Strength of materials
 Vibration
 Power, cooling, packaging, and electromagnetic compatibility
 Matrices, errors, and coordinate rotations
 Complex numbers, differential equations, and transforms
 Convolutions, discrete Fourier transforms, and filters
 Final exam
COURSE OWNER(S)
Jim Hinderer, PhD
22
EMIS 7312 - Software Systems Engineering
COURSE DESCRIPTION
The course focuses on the engineering of complex systems that have a strong software
component. For such systems, software often assumes functions previously allocated to
mechanical and electrical subsystems, changing the way systems engineers must think
about classical systems issues. The course provides a framework for addressing
systems engineering issues by focusing on the Software Engineering Institute's
Systems Engineering Capability Maturity Model (SE-CMM). Topics include deriving and
allocating requirements, system and software architectures, integration, interface
management, configuration management, quality, verification and validation, reliability,
and risk.
COURSE OBJECTIVES
To prepare students with diverse technical backgrounds and objectives with
fundamental software systems engineering concepts, methods, and techniques for use
in continuing graduate studies and in engineering & engineering management through a
balance of theory and application involving key concepts of the Software Engineering
Body of Knowledge. Emphasis is placed on requirement engineering and modeling,
design architectures and verification and validation.
PREREQUISITES
None
COURSE TOPICAL COVERAGE











Course Overview, Introduction
Software Engineering Development
Processes
Requirements Management
Requirements elicitation
Requirements Modeling (State
machines and State Charts)
Requirements Modeling (Entity
Relationship Diagrams, Data Flow
Diagrams)
Sequence Enumeration
Software design processes and lifecycle
Software Architectures
Software Design Processes
Object Oriented Analysis and Design













Midterm Exam (On Campus)
Formal Methods of Specification
Software Design Processes
Software Design (Real-Time Systems)
Software Design (Distributed Systems)
Software Design (User Interface Design)
Software Implementation
Verification and Validation
Software Testing
Software Testing (Black Box and White
Box Techniques)
Critical Systems Development
Course Recap & Project Presentations
Final Exam
COURSE OWNER(S)
Rob Oshana; Ann Broihier
23
EMIS 7315- Systems Architecture Development
COURSE DESCRIPTION
A design-based methodology approach to system architecture development using
emerging and current enterprise architecture frameworks. Structured analysis and
object-oriented analysis and design approaches will be covered. Enterprise architecture
frameworks including the Zachman framework, FEAF, DoDAF, ANSI/IEEE-1471 and
others will be examined. Executable architecture model approaches will be studied as
tools for system-level performance evaluation and tradeoff analyses. Case studies will
be examined in enterprise architecture development. Issues related to the integration
architecture design processes into the larger engineering-of-systems environment will
also be covered.
COURSE OBJECTIVES
The goal of the course is to provide students with an introduction why and when
architectures are needed and what functions they serve. Application of design
processes will be used to achieve the architectural design of candidate systems.
Emerging trends in architecture development in government and commercial industry
will be included in context of existing engineering processes.
PREREQUISITES
EMIS 7301
COURSE TOPICAL COVERAGE














Introduction to Architecture
Development
Systems Architecting Overview
Standards: Zachman, TOGAF, FEAF,
TEAF, IEEE 1471
The DoD Architecture Framework
Mapping to the Zachman Framework
The DoDAF View Products
Structured Analysis Review
Activity Modeling, IDEF0
Data Modeling, Rule Modeling
Dynamics Modeling, Integrated
Dictionary
Mid-term Examination
Object Oriented Analysis & Design
Basic Principles, UML
Diagramming















Architecture Development
Architecture Development Process
within the Systems Engineering Process
Examples
The System Architect’s Role
Cultural Issues
Other Topics in Architecture
Development
ConOps Development
Service-Oriented Architectures (SOA)
Model-Driven Architectures (MDA)
Component-Based Architectures
IT-Centric Architecture Development
SysML
Tools
Final Examination
COURSE OWNER(S)
Chris Askew; Jim Rodenkirch
24
EMIS 7318 - Systems Engineering Planning and Management
COURSE DESCRIPTION
Provide a practical coverage of tasks, processes, methods and techniques to establish
the process of systems engineering and its role in the planning and management of
programs. The tasks and roles of Program Manager and Systems Engineer are
unveiled for establishing program operations and communications framework.
Techniques are presented for developing an integrated program/project plan by defining
the role of the systems integrator and identifying useful tools for planning and managing
systems integration of various sized projects. The student learns to prepare for and
successfully complete key program milestone reviews by identifying essential material
content and proving the design basis. The course leads the student through the
systems development process by showing how to plan for and manage change by
implementing methods for configuration, change, and risk management. The program
life cycle is concluded by planning the transition of systems engineering processes from
development to production and field support.
COURSE OBJECTIVES
Provide students with proven methods and techniques for developing and implementing
the process of systems engineering in the planning and management of systems
development programs through the use of techniques currently employed on
Government and Commercial programs. Lead students through program phases by
establishing program framework, developing integration plans, preparing for and
successfully executing key program milestone reviews, managing program change, and
sizing tasks for production, fielding and spiral growth.
PREREQUISITES
EMIS 7301
COURSE TOPICAL COVERAGE
 Understanding the process of systems












engineering and its role in planning and
management of projects
Framing the roles of program manager and
systems engineering
Establishing program framework
Establishing program operations and
communications framework
Converting contract proposal wording into
contract requirements
Developing an integrated program/project plan
Defining systems integration
The role of the systems integrator
Developing measures of performance and
effectiveness
Components of the integrated program/project
plan
Systems integration tools
Synthesizing the plan to the project
Preparing for and successfully completing key
program milestone reviews
 Major program reviews and essential material













content
Proving the design basis
Presentation of results
Managing program change
Configuration / change management
Concurrent engineering; planning for pitfalls
Identifying and mitigating risks due to change
Impact of change to production and fielded
systems
The role of Integrated Logistics, Support &
Training (ILS&T) in engineering
change management
Planning Program Transition from Development
to Production
Phases of production
Systems Engineering for production and field
support
Assessing the holistic approach to systems
engineering
COURSE OWNER(S)
Steve Skinner, PhD
25
EMIS 5/7320 - Systems Engineering Leadership
COURSE DESCRIPTION
This course augments the management principles embedded in the systems
engineering process with process design and leadership principles and practices.
Emphasis is placed on leadership principles by introducing the underlying behavioral
science components, theories and models. The course demonstrates how the elements
of systems engineering, project management, process design, and leadership integrate
into an effective leadership system.
COURSE OBJECTIVES
To provide students with the building blocks of effective, technical leadership and an
understanding of how those building blocks integrate into a system that enables
management of the technical professionals who develop systems.
PREREQUISITES
EMIS 7301
COURSE TOPICAL COVERAGE
 Leadership
 Leader thought process
 Interactional framework of leadership
 Follower variables and characteristics
 Situational dynamics
 Organizational culture
 Team design
 Project Management
 Relationships between management practices and leadership principles
 Systems Engineering
 Systems Engineering planning and control mechanisms
 Process Design
 Influence of information and queuing theory on integrated product development process
design
COURSE OWNER(S)
Karl Arunski
26
EMIS 7330/5330 - SYSTEMS RELIABILITY ENGINEERING
COURSE DESCRIPTION
An in-depth coverage of tasks, processes, methods and techniques for achieving &
maintaining the required level of system reliability considering operational performance,
Customer satisfaction and affordability. Specific topics include: Establishing System
Reliability requirements, reliability program planning, system reliability modeling &
analysis, system reliability design guidelines & analysis, system reliability test and
evaluation, and maintaining inherent system reliability during production & operation.
COURSE OBJECTIVES
To provide students with proven methods and techniques for developing reliable
systems utilizing systems engineering principles along with systems analyses as a basis
for trade-offs involving systems configurations, component reliability, systems
operational requirements, cost and risk applicable for all products and services, as well
as to other engineering & design courses.
PREREQUISITES
EMIS 7300 or permission of instructor
COURSE TOPICAL COVERAGE
 Introduction to system reliability concepts, Customer expectations, market competition
and system performance, effectiveness, affordability warranty and customer satisfaction.
 System reliability requirements and relationship to system safety, cost of ownership,
maintainability, supportability, logistics, quality and operational availability, and reliability
program planning.
 System reliability modeling & analysis – types of models, system reliability measures,
series configurations and redundant configurations, system reliability allocations &
predictions.
 System reliability design guidelines & analysis – design-to guidelines & best practices,
failure modes, effects and criticality analysis (FMECA), Fault Tree Analysis (FTA), Worst
Case Analysis (WCA), prognostics & health monitoring analysis (PHMA), reliability
Centered Maintenance Analysis (RCMA) and integrity analysis.
 System Reliability Test & Evaluation – types of reliability tests, test planning, reliability
growth planning, assessment & management, Environmental Stress Screening (ESS),
operational reliability tests and Failure Reporting & Corrective System (FRACAS).
COURSE OWNER(S)
Jerrell Stracener, PhD
27
EMIS 7335 - Human-Systems Integration (HSI)
COURSE DESCRIPTION
This course advances the understanding and application of cognitive-science principles,
analysis-of-alternatives methods and engineering-best practices for addressing the role
of humans within the design of high-technology systems. In addition, HSI-specific
processes (e.g., task-centered design; human-factors engineering; manpower,
personnel and training; process analysis; usability testing and assessment) are
presented and discussed.
COURSE OBJECTIVES
The objectives of this course are to teach systems-engineering students about what
constitutes HSI, how HSI is typically implemented within engineering/softwaredevelopment environments, and how HSI can be implemented within a spiral-acquisition
framework. Students learn how HSI contributes to engineering-process improvement;
how the analysis, design and development of effective system capabilities is facilitated
by agile human-centered design approaches, and how process analysis, usability
testing and human-performance assessment are crucial systems-engineering feedback
mechanisms.
PREREQUISITES
EMIS 7301
COURSE TOPICAL COVERAGE
 Cognitive-Science Principles
 Analysis of Alternatives (AoA) Methods
 Engineering Best Practices
 Task-Centered Design Guidelines
 Human Factors Engineering (HFE)
 Manpower, Personnel and Training (MPT) Consideration
 Process Analysis
 Usability Testing
 Human-Performance Assessment
COURSE OWNER(S)
Bill Mutto, PhD
28
EMIS 7340 - LOGISTICS SYSTEMS ENGINEERING
COURSE DESCRIPTION
An introduction to concepts, methods and techniques for engineering and development
of logistics systems associated with product production/manufacturing, product order
and service fulfillment, and product/service/customer support, utilizing system
engineering principles and analyses. Specific topics include: logistics systems
requirements, logistics systems design & engineering concurrently with product and
service development, transportation & distribution, supply/material support, supply web
design & management and product/service/customer support.
COURSE OBJECTIVES
To provide students with concepts, methods and techniques for treating the logistics
function associated with products and services as a system – during product and
service design and development, production/manufacturing and product usage/service
delivery – from concept through customer/product support that are essential for all
business enterprises, especially e-business. Emphasis is placed on application of
methods and techniques through problem definition & solving and case studies.
PREREQUISITES
MATH 2339 or equivalent
COURSE TOPICAL COVERAGE















Introduction - Principles of Systems Engineering, Project Description and Review, History of
Logistics, Definition of Logistics, Difference between Logistics and Systems Engineering and
Supply Chain Management
Principles of Logistics SE – Forward and Reverse Logistics; Basic Elements of Logistics, the 7R’s
Manpower and Personnel - Design Considerations; Staffing Requirements
Forecasting – Types and Models used in short, mid, and long term planning; Staff Planning and
Support
Concepts of Logistic Systems / Facility/Warehouse Analysis & Design - Warehouse and Design
Considerations; Warehouse Design and Location, View of the Logistics’ Role in the Operational
Phase of the System’s LC
Finance Role in the Logistics World – Future and Present Values, Cost Trade-off Analysis
Review – Integrating forecasting, concepts of logistic system, facility warehouse analysis and
design, and finance into logistics systems engineering
Maintainability Analysis – Maintainability Prediction, Maintainability in the role of Logistics;
Support of Logistic Systems; Modeling Logistic Systems using Maintainability Analysis
Midterm – In class
Reliability Logistic Modeling – Identifying Reliability of Logistic Systems, Modeling Logistics
Systems using Reliability Analysis, Trade-off Analysis
Inventory – Economic Order Quantity, Fill Rate, and Safety Stock, Customer Service
Spare Part Analysis – Predictions, Probability of Success, Modeling Logistics Systems
Packaging and Distribution and Distribution Systems - Design Guidelines and Evaluation
Tradeoffs
Class Review and Case Studies - Lectures 6-10, & 15; Real Case Studies
Final – In class
COURSE OWNER(S)
Jerrell T. Stracener, PhD / Gerard Ibarra, PhD
29
EMIS 7347 - Critical Infrastructure Protection/Security Systems
Engineering
COURSE DESCRIPTION
The purpose of the course is to present systems engineering (SE) concepts as applied
to the protection of the United States’ critical infrastructure (CI). A top-level systems
viewpoint provides a greater understanding of this system-of-systems (SOS). Topics
include: the definition and advantages of SE practices and fundamentals; system
objectives that include the viewpoint of the customer, user, and other stakeholders; the
elements of the CI and their interdependencies; the impact transportation system
disruptions; and systems risk analysis.
COURSE OBJECTIVES
The objective of the course is to provide students with an understanding of systems
engineering application to the critical infrastructure engineering and analysis. This
course will enable students to understand the stakeholders’ viewpoints in defining
requirements, determining feasible solutions and the CI as a SOS. Furthermore, the
class will develop a model for the infrastructure and its interdependencies, and it will
develop a risk analysis for protection of the critical infrastructure.
PREREQUISITES
EMIS 7301, EMIS 7303
COURSE TOPICAL COVERAGE













Introduction to System Engineering as it
related in CISE
Using Systems Engineering for Problem
Solving
Definitions and Applications of Systems
Engineering
Importance of Understanding the
Problem
Identifying and Understanding the
Stakeholders’ Viewpoint
Fundamentals of the CI
What is the CI and CIP
Viewing the CI as a SOS and an
Extended Enterprise System
Defining the CI
Modeling the Interdependencies of the CI
Mapping the Environment
Defining the CI Architecture and
Interfaces
The Highly Important Transportation
Element of the CI















Analyzing the Transportation/Logistics of
the CI
Determining the Effects due to an
Interruption
Reliability and Availability Models for the
CI
What is Reliability
Applying Reliability Models to the CI
Understanding Availability
Using the Availability Analysis in the CI
Risk Identification, Evaluation and Plan
for Mitigation
Reviewing the Concepts of Risk Analysis
Assessing the CI’s Risk
Developing Terrorist Scenarios
Applying Risk Analysis Models
Case Studies
The Port of Houston
Additional Ports
COURSE OWNER(S)
Gerard Ibarra, PhD
30
EMIS 7370/STAT 5340 - PROBABILITY AND STATISTICS FOR
ENGINEERS
COURSE DESCRIPTION
This course is an introduction to fundamentals of probability, probability distributions
and statistical techniques used by engineers and physical scientists. Topics include
basic concepts and rules of probability, random variables, probability distributions,
expectation and variance, sampling and sampling distributions, statistical analysis
techniques, statistical inference – estimation and tests of hypothesis, correlation and
regression, and analysis of variance.
COURSE OBJECTIVES
To prepare students with diverse technical backgrounds and objectives with
fundamental probabilistic & statistical concepts, methods, and techniques for use in
continuing graduate studies and in engineering & engineering management through a
balance of theory and application involving engineering decision making, including
situations in which uncertainty and risk are important. Emphasis is placed on problem
definition, solution and interpretation of results.
PREREQUISITES
MATH 2339 or equivalent
COURSE TOPICAL COVERAGE
 Introduction, Overview, Probability - Basic Concepts and Approaches, Probability Counting Techniques
 Probability - Independence & Fundamental Rules, Conditional Probability and Bayes'
Theorem
 Discrete Random Variables and Probability Distributions, Binomial, Negative Binomial
and Geometric Distributions
 Hypergeometric and Poisson Distributions, Continuous Random Variables and
Probability Distributions
 Normal (Gaussian) & Lognormal Distributions, Exponential & Weibull Distributions
 Gamma & Beta Distributions, t-,Chi-Squared & F-Distributions
 Functions of Random Variables, Sampling & Sampling Distributions
 Statistical Analysis of Random Samples
 Midterm Exam
 Estimation - Basic Concepts & Estimation of Proportions, Means, Standard Deviations &
Percentiles
 Test of Hypothesis - Basic Concepts & Test of Proportions ,Tests of Means and
Variances , Joint Probability Distributions
 Covariance & Correlation, Simple Linear Regression
 Design of Experiments & One Factor Experiments, Randomized Block Experiments
 Course Recap & Project Presentations
 Final Exam
COURSE OWNER(S)
Jerrell T. Stracener, PhD
31
EMIS 8305 - Systems Life Cycle Cost & Affordability Analysis
COURSE DESCRIPTION
This course will provide an understanding of Systems affordability concepts and the life
cycle cost process. The importance of using these concepts in optimizing
engineering/business decisions will be examined with emphasis being placed on the
evaluation of alternatives weighing costs, risks, reliability, maintainability, supportability,
weight, performance, and other benefit/risk parameters. Topics include, total ownership
cost, estimating methods & techniques, cost analysis process, system trade studies,
sensitivity analysis, risk analysis & simulation, and system cost effectiveness.
COURSE OBJECTIVES
The objective of this course is to provide the student with a variety of tools, techniques,
and methods in projecting systems life cycle cost when evaluating not only
engineering/business alternatives but also individual purchase decisions. Upon
completion, the student will be able to apply the techniques throughout the
design/evaluation process and have the awareness of the impact their decisions have
on system affordability.
PREREQUISITES
EMIS 7301, 7303 &7305
COURSE TOPICAL COVERAGE





















Introductory Concepts
Life Cycle Process Overview
Cost Impact of Change
System Cost Effectiveness
Systems Affordability Concepts
Design-to-Cost (DTC)
Reliability/Maintainability Impact on
Operating & Support (O&S) Cost
Total Ownership Cost/Life Cycle Cost
Costs An Independent Variable & Target
Cost
Case Study
Estimating Methods/Techniques
Subjective (Engineering Judgment)
Quantitative (Parametric/Statistical)
Learning Curves
Standard Hours/Realization
Cost Estimation Relationships
Development
Economic Analysis
Parametric Models
Systems Analysis Process
Definition/Planning
Data Collection/Normalization























Targets/goals/metrics
Tracking/reporting
Calibration/maintenance
System Trades
Parameters
Cost Drivers
Trade Space
Weighting Parameters
Modeling
Break-even/sensitivity
Utility Curves
Case Study
Systems Risk Analysis & Simulation
Technical
Performance
Schedule/Cost
Simulation Techniques
Software
Case Study
Special Topics
Warranty Cost Risk
Software Estimating
Schedule Risk
COURSE OWNER(S)
32
EMIS 8307 - Systems Test and Evaluation
COURSE DESCRIPTION
An in-depth coverage of the test and evaluation (T&E) techniques that have evolved in
response to the increasing complexity and interdependency of systems. Types of
testing will be examined (developmental, operational, etc.) as well as the tailoring of
testing based on the end user (commercial, military). The T&E process, from
requirements analysis through test conduct and reporting, as well as the various types
of associated documentation will be covered. Test techniques associated with different
disciplines (such as software, reliability, human factors) will be covered. The course
concludes with a review of the best practices in Systems T&E.
COURSE OBJECTIVES
The objective of the course is to provide students with an introduction to the types of
testing as well as the T&E Engineering process. Topics will include requirements
analysis, detailed planning, resources, test conduct, analysis and reporting. We will
examine the many varieties of T&E in the commercial arena as well as in US DoD and
foreign military environments.
PREREQUISITES
EMIS 7301 and EMIS 7307
COURSE TOPICAL COVERAGE
 T & E Concepts
 T&E in Systems Engineering
 Drivers of T&E
 Test & Evaluation Types
 Developmental
 Production
 Marketing
 Operational
 In-service
 Disposal
 Evolution of T&E Practices
 Commercial
 US Defense
 Foreign Defense
 Other US Government
 T&E Engineering
 Requirements Analysis
 Planning
 Resources
 Test conduct


















Analysis
Reporting T&E Program
Documentation
T&E Master Plan
Categorization of test problems
T&E report
T&E requirements in contracts
T&E Techniques
T&E of computer software
Reliability T&E
Environmental T&E
Human Engineering T&E
Testing for Safety
Design-limit testing
Interoperability
Live-fire T&E
Modeling and Simulation
Computer-aided T&E Tools
Best Practices in Systems T&E
COURSE OWNER(S)
Mike Hopper, D.Eng
33
EMIS 8310 - Collective System Design
COURSE DESCRIPTION
This course focuses on the design of sustainable and robust systems within
organizations. Collective System Design (CSD) enhances lean and six-sigma based
implementations to ensure long-term sustainability and robustness. Some people call
the Collective System Design methodology and principles, “next generation lean” as it
applies systems engineering principles to the design of organizational processes and
systems. The course applies to the design of a wide range of commercial and
governmental systems in the areas of manufacturing, product engineering, contract and
program management, service industries and business systems. A class project with a
local business or agency will enable students’ to practice the application of CSD.
COURSE OBJECTIVES
Provide students with the knowledge and skills to evaluate existing systems issues and
to re-design and effectively deploy a new system design with an organization;
understand the principles of robust and sustainable designs; understand the pitfalls to
avoid when implementing Lean and Six Sigma. Understand the history and origin of
Lean/TPS (Toyota Production System), Six-Sigma and Lean-Sigma.
PREREQUISITES
EMIS 7301, 7310, and 8342
COURSE TOPICAL COVERAGE














Introduction to Collective
System Design
Introduction to System Design
Principles
Process Mapping
Understanding Existing
System Functional
Requirements (FRs) and
Physical Solutions (PSs)
Class Project: Select a Project
and Process Map the Existing
System
History of Manufacturing and
Manufacturing Improvement
History of Lean/TPS
The Industrial Revolutions
TPS Principles
Six Sigma and DMAIC
Other Methodologies
Evaluating Types of System
Designs
Class Project: Impute FRs and
PSs of the Existing System;
Evaluate Type of Design
Understanding and
Establishing Purpose with an
Existing Organization














Who are the Customers?
Understanding their needs.
Expressing needs as FRs
How to get people to express
the real FRs
Establishing Collective
Agreement: Thinking versus
Thought
Determining the System
Design Boundary and
Interfaces
Class Project: Determine the
System Boundary; Understand
the Customer Needs,
Candidate FRs, Hypothesize
the PSs
Designing a Robust and
Sustainable System
Creating a System Design
Map
Implementing the System
Design
TPS Simulation
Push versus Pull
Standardizing the Work
Designing a System to Rapidly
Identify and Resolve Problems







Class Project: Create the
System Design Map for the
New Design; create the
process map of how the
organization identifies and
responds to problems
conditions that affect the
achievement of the FRs
Resource Allocation to Sustain
the System Design
Management Accounting
versus Financial Accounting
The Pitfalls of Traditional
Management Accounting
Avoiding the “Lean/Six-Sigma ”
Implementation Pitfalls
Gaining collective agreement
about how to manage the
system’s
Class Project: Identify the
existing organizational
barriers; create a desired state
process flow chart of how
resources will be allocated to
achieve FRs.
COURSE OWNER(S)
David Cochran, PhD
34
EMIS 8315 - Innovation in Systems Design
COURSE DESCRIPTION
This course provides a foundation of modern theory and practice of product innovation
in three parts. First, it will review the typical barriers to disruptive innovation:
technological, organizational and market-driven. Second, cases of fast innovation will
be reviewed with a focus on systems and technology. Third, the system engineer’s role
in innovation will be covered with such methods as Quality Function Deployment (QFD),
Axiomatic Design, the Theory of Inventive Problem Solving (TRIZ), and basic
intellectual property protection. The students will practice methods and explore and
develop disruptive innovation in a class project.
COURSE OBJECTIVES
To provide systems engineers with knowledge to foster innovation throughout their
careers. This includes the ability to recognize and clear roadblocks and the modern
tools necessary for faster product innovation.
PREREQUISITES
EMIS 7301 and 7310
COURSE TOPICAL COVERAGE
 Innovation in systems development
 The business need
 Organic innovation vs acquisition
 Levels of discovery
 Three-dimensions of innovation
 Typical vs Fast innovation with
systems cases
 Timeliness-to-market
 Appropriate-level of inventing
 Product differentiation and VOC
 Fast Innovations Case Studies
 Increasing learning cycle speed
 Managing flexible specifications
 Disruptive innovation theory
 Low end, new market, new value
 Identifying signals of change
 Open vs closed innovation models
 Lead-user model
 Technology-based disruption in
systems
 Disk drive
 Aviation



















Semiconductors
Telecommunications
Quality Function Deployment &
systems reqts
Axiomatic Design
Design domains
Requirement independence
Minimizing information content
Axiomatic Design of Systems
Inventive cases
TRIZ Elements of excellence
Ideality definition
Functionality mapping
Resources
TRIZ Contradiction Elimination
Inventive principles
Case studies
Intellectual property in systems
development
Patent law basics
IP resources on the internet
COURSE OWNER(S)
Kevin Cluff, PhD
35
EMIS 8340 - SYSTEMS ENGINEERING TOOLS
COURSE DESCRIPTION
Computerized tools perform the vital function of capturing and delivering Systems
Engineering information throughout the product development life cycle. This course
surveys the many tools, methods, and techniques that are applied to engineering
systems from inception to disposal: scope/needs evaluation, requirements analysis,
functional and physical allocation, optimization, test validation/verification, and product
management. Hands-on use of systems engineering software will enable students to
identify and apply appropriate tools through the life cycle of a product they develop.
COURSE OBJECTIVES
Since entire courses are taught on many of the individual topics covered in this course,
the goal is to integrate the tools with the SE process and explore how and when tools
are applied. Tools described in this course include methods, techniques, and
computerized tools. Since many different tools apply throughout the product life cycle,
the goal is to provide an understanding of what tools apply, how to apply them to
systems engineering problems, as well as when to apply them. As a result, students
will leave this course with a “tool kit” of Systems Engineering tools that can be applied to
engineering in their ongoing course work and every-day jobs.
PREREQUISITES
EMIS 7301 Systems Engineering Process
COURSE TOPICAL COVERAGE
 Before Requirements
 Systems Engineering process from a
tools perspective
 Standard Tools, including training on
course standard SE development
environment
 Scope Statements
 Requirements Definition
 Requirements Elicitation
 Requirements Organization
 Requirements Allocation
 Requirements Documentation
 Functions, Architecture, and Trade
Studies
 Functional Analysis
 Alternatives and scoring













Partitioning/Allocation
Architectural trade studies
Optimization
Technical Performance
Management
Design for
Test/Validation
Requirement Validation
Requirement Verification
Program/Project Management
Risk
Project Management
Dash Boards
Requirement Change and CM
COURSE OWNER(S)
Mark Sampson
36
EMIS 8342 - Six Sigma for Systems Engineering
COURSE DESCRIPTION
Methods and tools for the application of Six Sigma concepts as a part of the systemsengineering design process for developing quality products. Topics: assessing the
“predicted quality” of a product through requirements analysis, development a
quantitative process based on engineering best practices, and its application to trade
studies, model development, and operations analysis.
COURSE OBJECTIVES
The goal of the course is to provide students with an introduction to the prediction of
system performance in the presence of uncertainty and the processes and tools that
can enable its execution. This includes the investigation and discussion of established
concepts of how to extract the customer needs, develop requirements and assess the
risk of non-compliance in production and user environments.
PREREQUISITES
EMIS 7301, EMIS 7302
COURSE TOPICAL COVERAGE





















Introductory Concepts
Systems Engineering Overview
Six Sigma Overview
Design for Six Sigma Overview
Probability and Statistics (Ch 14)
Statistics for Six Sigma
Requirements Generation and
Flowdown (Ch 2)
Needs vs. Requirements
Kano Model
Quality Function Deployment
Conjoint Analysis
Developing and Evaluating Alternatives
Methods for Innovation (Ch11)
Qualitative Trade Studies
Quantitative Trade Studies
Requirement Modeling & Simulation
(Ch4)
Analytical Models (Equations)
Empirical Models
(Regression and DOE) (Ch 9)
Semi-Empirical Models




















Statistical Sensitivity Analysis
Taylor Series Concepts (Ch 14)
Derivation of Response Mean &
Variance
Variance Contributions
Probability of Non-Compliance
Calculations
Monte Carlo Analysis
Random Number Generation
Response Data Analysis
Variance Contributions
Parameter Correlations
Distribution Fitting
Optimization Methods & Analysis (Ch 4)
Optimization Concepts
Single vs. Multi-Objective Optimization
Optimization DFSS
Design Verification
Gage Repeatability & Reproducibility
Measurement Systems Analysis (Ch10)
Producer & Consumer Risk Analysis
COURSE OWNER(S)
George Chollar, PhD
37
EMIS 8348 Supply-Chain Systems Engineering
COURSE DESCRIPTION
The course introduces supply-chain design, development, and management
concepts and principles from a systems perspective. Topics include: the system
life cycle; influences of reliability, maintainability, and supportability (RMS) and
risk analysis associated with supply-chain design, development, and
management; supply-chain management strategies; high-level supply-chain and
transportation concepts and theories; and deterministic system modeling based
on customers’ needs, requirements, and functional analysis.
COURSE OBJECTIVES
The objective of the course is to provide students a fundamental understanding
of relating SE practices and methodologies to supply-chain design, development,
and management. The student learns the importance of applying SE concepts to
the supply-chain design, development, and management. Outcomes of the
course include development and understanding of functional analysis,
incorporating risk analysis and mitigation techniques, and fusing reliability
analysis as applied to supply-chain design, development, and management.
PREREQUISITES
EMIS 7301, EMIS7303, EMIS 7340
COURSE TOPICAL COVERAGE
















Fundamentals of Supply Chains
Definition of Supply Chains
Difference between Logistics and
Supply Chain Management (SCM)
SCM Concepts and Strategies
SCM Technology Tools
Advance Planning and Scheduling
(APS)
Enterprise Resource Planning (ERP)
Legacy Systems
Supply Chain Design
Understanding the Customer
Requirement Analysis
Functional Analysis
Incorporating the Life Cycle
Trade Analysis
Supply Chain Development
Reliability - Understanding and
Design
















Maintainability - Factors and Analysis
Supportability – Considerations
Building Supply Chain Models
Understanding Optimization Models
Considering the System – Life Cycle
Writing the Requirements
Formulating the Supply Chain
Architecture
Solving Supply Chain Models
Mathematically / Graphically
Microsoft Excel (Linear Programming)
Risk Analysis for the Supply Chain
Understanding Risks
Categorizing Risks
Various Risks Models (HHM, TTS,
FMECA)
Developing Risk Models for Supply
Chains
Managing the Supply Chain
COURSE OWNER(S)
Junfang Yu, PhD
38
3.3 Ph.D. SE Applicants and Transfers
3.3.1 Ph.D. Transfers to Ph.D. SE Program
The following current SMU PhD students, with the except of Tom Blakely, have
stated their intent to transfer to the PhD SE program upon approval:
Name
Yvonne Bijan
Tom Blakely
Rusty Husar
John Serocki
Azi Sharif
Rich Volkert
Tim Woods
Kevin Zummo
Organization Affiliation
Lockheed Martin Aeronautics Company
Lockheed Martin Aeronautics Company
US Navy SPAWAR
US Navy SPAWAR
US Navy SPAWAR
US Navy SPAWAR
Lockheed Martin Aeronautics Company
Lockheed Martin Aeronautics Company
Location
Ft Worth, TX
Ft Worth, TX
San Diego, CA
San Diego, CA
San Diego, CA
San Diego, CA
Ft Worth, TX
Ft Worth, TX
Current
PhD
Program
PhD OR
PhD AS
PhD AS
PhD AS
PhD AS
PhD AS
PhD AS
PhD AS
3.3.2 Ph.D. SE Applicants
Student Interest in PhD SE
The following have made application or in the process of making application, to
the Ph.D. in Applied Science Program with the intent to transfer to the Ph.D. SE
Program when the program is approved:
Name
Bill Akin
Ala Alzubi
Randy Ausbern
Richard L. Brouse
Robert Caldwell
Roger Carver
Long Dong
Daniel Flis
Lisa Hunt
Ailer Cordero Kochan
William Mark Lipsmeyer
Thang C Nguyen
James Sutton
Jennifer So
Keith Wilkins
David Wu
Organization Affiliation
Advanced Information Services
Texas Instruments
Lockheed Martin Aeronautics Company
Lockheed Martin Aeronautics Company
Lockheed Martin Aeronautics Company
Lockheed Martin Aeronautics Company
Lockheed Martin Aeronautics Company
Lockheed Martin Aeronautics Company
Lockheed Martin Aeronautics Company
L-3 Com Integrated System
Lockheed Martin Aeronautics Company
Lockheed Martin Aeronautics Company
Lockheed Martin Aeronautics Company
Lockheed Martin Aeronautics Company
Lockheed Martin Aeronautics Company
Lockheed Martin Aeronautics Company
Location
Charleston, SC
Dallas, TX
Ft. Worth, TX
Ft. Worth, TX
Ft. Worth, TX
Ft. Worth, TX
Ft. Worth, TX
Ft. Worth, TX
Greenville, TX
Ft. Worth, TX
Ft. Worth, TX
Ft. Worth, TX
Ft. Worth, TX
Ft. Worth, TX
Ft. Worth, TX
39
3.4 U.S. Ph.D. SE Program Benchmarks
The SEP DT Benchmarking Team performed research into current Ph.D. in
Systems Engineering Programs in the United States. This research was the
basis for the team’s final report comparing and contrasting SMU’s current Ph.D.
in Applied Science with a Major in Systems Engineering against the current
programs. The following sections show the data from the report updated to the
proposed Ph.D. in SE program. The full Benchmarking Team report is given in
Appendix A.
3.4.1 Summary of US Ph.D. SE and Related Programs
SMU’s proposed Ph.D. in SE program was compared against 10 other Systems
Engineering programs in the United States. The programs evaluated are shown
in the following table.
Table 1 – Programs Chosen For Final Evaluation Comparison
University/College
Location
George Washington University
Massachusetts Institute of Technology
Oakland University
Southern Methodist University
Stevens Institute of Technology
Texas Tech University
Washington, DC
Cambridge, MA
Rochester, MI
Dallas, Texas
Hoboken, NJ
Lubbock, TX
The University of Alabama in Huntsville
The University of Arizona
University of Southern California
University of Virginia
Huntsville, AL
Tucson, AZ
Los Angeles, CA
Charlottesville, VA
Washington University
St. Louis, MO
Program
Doctor of Science
PhD in Engineering Systems
PhD in Systems Engineering
Proposed PhD in Systems Engineering
Doctoral Programs in Systems Engineering
Doctor of Philosophy in Systems and
Engineering Management
PhD in Systems Engineering
PhD in Industrial & Systems Engineering
PhD in Systems Engineering
PhD in Systems Engineering
Doctor of Science in Systems Science and
Mathematics
3.4.2 Comparison and Contrast of Proposed SMU Ph.D. SE
Program to Benchmark Programs
A comparison of SMU’s proposed Ph.D. in Systems Engineering and the other
10 programs shows the following:


GRE Requirement
o All programs required the GRE.
o SMU’s proposed program requires the GRE if the student has less
than 10 years of industry experience.
Residency
o All programs, except SMU’s, require at least a minimum of 1 year
residency, with one program requiring two years.
40
o The proposed SMU Ph.D. in SE program does not have a
residency requirement.




Total Credit Hours
o The average credit hours required was 76.2 hours, with a high of 90
and a low of 64. The mode was 72 and the median was 75 hours.
o SMU’s proposed program requires 78 total credit hours and was
slightly above the average of 76.2.
Course Credit Hours
o The average was 54.8 credit hours of course work beyond the
bachelors, with a high of 66, a low of 36 hours, a mode of 54 and a
median of 55 credit hours.
o At 54 credit hours of course work, SMU’s proposed program is just
below the average, but well above the low and equal to the mode.
Dissertation Credit Hours
o The average was 20.2 credit hours of dissertation work, with a high
of 30, a low of 4, a mode of 24 and a median of 24 credit hours.
o SMU’s proposed programs 24 dissertation credit hours is above
average and just below the high of 30 and equaled the mode and
median.
Transfer Credit Hours
o The average allowed transfer credits was 28.4 with a high of 33, a
low of 24, and a median and mode of 30.
o SMU allows 30 transfer credit hours, but varies that number as
individual circumstances require.
A summary of the data gathered in the final evaluation is shown in Table 2.
41
Table 2 - Attribute Comparison
Data Gathered
2. Admission requirements
a. GRE
b. Residency
3. Degree Requirements
Total Credits Required
b. Course Credits Required
c. Dissertation Credits Required
d. Transfer Credits Allowed
e.
Other
4. Degree Roadmap
a. Qualifying Exam
b. Oral Exam/Research Exam
c. Dissertation Defense
Other
d. Time Limits
5. Program Characteristics
a. Program
b. Faculty - Full and part time
c. Students - Full and part time
6. Delivery methods
GWU
MIT
Yes
Partial1
Yes
Partial2
OU
Yes
Partial1
78
54
24
Yes
Yes
SIT
Yes
Unknown
80
56
24
32
Yes
Yes
Yes
SMU*
Yes
Yes
Yes
Yes
None
90
60
30
30
Yes
Yes
Yes
Private
Defense
7
Department Department Department School
11
50
6
60
Resident
Resident
Combo
TTU
Yes
Partial1
78
54
24
30
Yes
Yes
Yes
Yes
Yes
Yes
Preliminary
QE
6
7
34
82
TUAH
TUA
Yes
Partial1
72
60
12
24
USC
Yes
Partial1
84
66
18
33
Yes
Yes
Yes
Yes
Yes
Yes
Preliminary
Exam
5
UV
Yes
Unknown
72
54
18
24
Yes
Partial1
64
60
4
30 Varies
Yes
Yes
Yes
10
WUSTL
Yes
Partial1
72
48
24
Yes
Yes
Yes
6
72
36
24
24
Yes
Yes
Yes
7
5
Department Department Department Department Department Department Department
36
14
9
27
53
27
33
37**
50
Combo
Resident
Combo
Resident
Resident
Partial1 = 1 year of full time study
Partial2 = 2 years of full time study
Combo = Distance and Resident classes
* - Proposed Ph.D. in Systems Engineering
** - Applicants and Transfer Requests
Note: Blank field indicates information was not found during research.
42
Ph.D. Programs Credit Hours Vs. SMU Ph.D. SE Program
100
90
Hi, 90
SMU
Average
Hi
Low
Mode
Median
Data Range
80
Average, 76.2
70
Median, 75
Credit Hours
Mode, 72
Low, 64
Hi, 66
60
Median, 55
Average, 54.8
50
Mode, 54
40
Median and Mode, 30
Low, 36
Hi, 33
Hi, 30
30
Average, 28.375
Median and Mode, 24
Low, 24
20
Average, 20.2
10
Low, 4
0
Total Credit Hours
Required
Course Credit Hours,
Above Bachelors,
Required
Dissertation Credit
Hours
Required
Transfer Credit Hours
Allowed
Figure 1 Analytical Comparison
Figure 1 shows the analysis of the evaluation programs, including SMU’s data,
against SMU’s proposed Ph.D. SE program.
3.5 Ph.D. SE Planning Guide
The current Ph.D. Applied Science Major in Systems Engineering Planning
Guide will form the basis for the Ph.D. SE Planning Guide.
Ph.D.ASwSE.Plannin
g.Guide.ppt
43
Appendix A – Systems Engineering Ph.D. Programs
Benchmarking Final Report
To insure the proposed SMU Ph.D. in Systems Engineering (SE) program was
comparable to other current Ph.D. in SE programs, a twenty member volunteer
team formed as part of SMU’s Systems Engineering Program Development
Team (SEPDT). The team was identified as the Benchmarking Team and
derived from members of the SEPDT. Team co-leads were Tim Woods, a Ph.D.
Candidate in Systems Engineering at SMU, and Dr. Jim Hinderer, an adjunct
Professor of Systems Engineering at SMU. Dr. Jerrell Stracener, SMU Systems
Engineering Program’s founding director, provided consultation and support to
the team. The goal of the team was to gather data on current Ph.D. in SE
programs in the United States and use the data to build a comparison basis for
the proposed Ph.D. in SE program at SMU.
The Benchmarking Team started gathering data in February 2007 and finished in
April 2008. This report is the culmination or research and analysis and was
provided to Dr. Stracener in June of 2008. The Benchmarking Team analyzed
data from 128 schools. The team found 53 Ph.D., 82 Masters, and 63 Bachelor
degree programs that at first review were Systems Engineering related. The
Benchmarking Team’s Final Report is attached.
Benchmarking Final
Report.pdf
44
Appendix B – Ph.D. Applied Science Applications
45