UNIVERSITY

OF

SOUTHERN CALIFORNIA

Systems Engineering Theory & Practice

ISE 541

Jim Hines

Summer 2007

UNIVERSTY OF SOUTHERN CALIFORNIA

COURSE OBJECTIVES AND REQUIREMENTS

SYSTEMS ENGINEERING THEORY AND PRACTICE (ISE 541)

Instructor: Jim Hines

Phone: 562-714-4326

E-Mail:

Class:M,06:00 PM-09:10 PM; OHE 100D

Office Hours: 05:00 PM Monday GER Room 240 or in classroom before class

Teaching Assistant:

Phone:

Email:

Office Hours:

Contact usanytime if you wish to meet with us individually or as a group. If you are unable to reach us by phone, leave a message with your phone number or E-mail. We will return your call or E-mail as soon as possible.

Textbooks: Systems Engineering and Analysis, 4rd edition (738 pp.) Benjamin S. Blanchard and Wolter J. Fabrycky, 2005 Prentice Hall (not mandatory)

Website: USC URL _Learning

Blackboard

Administrative:

Neil Teixeira [Technical Support
Online Services, Webcast Problems, Software Questions or General Technical Questions

Jared Laux [ DEN Exams and Proctoring,(213) 821-3136
fax: (213) 821-0851

Mary Ordaz, ISE Student Services Assistant, 213-740-4886

Course Description:

Systems engineering is the evolving discipline that addressed the management of increasing complexity in military, industrial, commercial and civil systems. Over the past few decades, especially since the massive applications available from digital computers and software, the complexity of systems for a great variety of applications has threatened to overwhelm previous management processes. Furthermore, this complexity has resulted in developmental failures, cost overruns, schedule slippage, customer dissatisfaction and environmental disasters.

Among the topics to be covered in the class are:

……………………..Perspectives of systems and systems engineering

……………………..General statement of the complexity of a problem

……………………..Integrated Product & Process Development

……………………..System acquisition & life cycle

……………………..Definition Phase

……………………..Requirements & functional analysis

……………………..Specifications

……………………..Systems Engineering Management Plans

……………………..Design & build phase

……………………..Synthesis & architecting

……………………..Verification, validation, and test

……………………..Systems analysis & control

……………………..Risk management

……………………..Affordability

……………………..Design for specialties

……………………..Integrated Master Plan & Schedule

……………………..Capability Maturity Models

Course Objectives:

Scope

Systems Engineering is a scientific way to understand the underlying structure and characteristics of systems and their complexities. This course will acquaint you with concept of systems and the role systems engineering plays in their development. It will also provide a basic framework for planning and assessing system development and how systems analysis methods and techniques are integrated within the systems engineering process.

Goals

  • Establish an understanding of basic system and systems engineering concepts and terms
  • Introduce systems engineering as a problem solving process and its relationship to program life cycle
  • Discuss useful theories, models, techniques and tools
  • Address design for operational feasibility (specialty engineering) concepts
  • Present an overview of systems engineering management

Course Highlights: (Detailed agenda for each session in Attachment 2, course Outline)

There will be:

1)Exercises.

2)Midterm exam.

3)Final exam.

4)Class Project

As in the “real world” of systems engineering involves teamwork. As a result we will be forming teams for working on selected Exercises & the class project. Each team is required to demonstrate that they can perform selected Exercises and develop a Systems Engineering Management Plan (SEMP) or a Systems Specification. Each team will be required for their project make an initial “white paper” presentation on their respective plans to the rest of the class. The white paper will contain the Subject matter, Team members, Table of Contents, Scope, Feasibility, and Applicable Documents. A written Systems Engineering Management Plan (SEMP) or a Systems Specification, representing the collective efforts of all team members, shall be submitted not later than the last class session. A presentation of the final plan or specification will be made during the last two sessions. You are highly encouraged to utilize the knowledge acquired in the lectures and any other publications that are relevant to the development of your systems engineering management plan or specification. Reminder: It is important that the team demonstrate that the team knows how to write a SEMP or Specification; not that it should be a final complete product.

Grading: USC Grading Policiesshall be followed.

Activity Weighting Factor

Systems Engineering Management Plan / Systems Specification Project 25%

Mid Term 25%

Final Exam 25%

Exercises 25%
100%

Academic Integrity Statement - "The School of Engineeringadheres to the University's policies and procedures governing academic integrity as described in USC Campus. Students are expected to be aware of and to observe the academic integrity standards described in USC Campus, and to expect those standards to be enforced in this course.

Students with Disabilities:

"Any Student requesting academic accommodations based on a disability is required to register with Disability Services and Programs (DSP) each semester. A letter of verification for approved accommodations can be

obtained from DSP. Please be sure the letter is delivered to me (or to TA) as early in the semester as possible. DSP is located in STU 301 and is open 8:30 a.m. - 5:00 p.m., Monday through Friday. The phone number for DSP is (213)740-0776."

University of Southern California
Course Outline
Systems Engineering Theory and Practice (ISE 541)

NOTE: Unless otherwise noted, all reading assignments are from Blanchard & Fabrycky’s Systems Engineering and Analyses text.

Session 1:Introduction and Orientation – May 21, 2007

  • Introductory remarks on the nature and requirements of the course-and other administrative issues.
  • READING ASSIGNMENT: (before the class session)
  • Preface; Chapters 1
  • LECTURE TOPICS (Introduction, System Definitions and Concepts)
  • Definitions
  • Why Systems Engineering?
  • Systems Engineering Process & Products
  • Application of Systems Engineering

Be sure to turn in your Student Profiles before next class.

Student
Name / Phone/FAX / E-mail
Company & Location / Systems Engineering
Experience / Industry Experience / Number of ISE Courses
Taken

Session 2: Introduction to Systems– June 4, 2007

  • READING ASSIGNMENT (BEFORE THE CLASS SESSION):
  • Chapter 2 & Appendix A.2
  • Chapter 3, 4
  • LECTURE TOPICS (Bringing Systems into Being)
  • Systems Engineering Discipline
  • The Systems Engineer and Project Manager
  • Systems Acquisition & Life Cycle
  • Design Reviews

Session 3:Systems Design Process– June 11, 2007

  • PROJECT TEAM ASSIGNMENTS (teams will be organized for the class project plans)
  • LECTURE TOPICS (Conceptual Systems Design)
  • Definition Phase
  • Specifications
  • Systems Engineering Management Plan (SEMP)

Session 4: Systems Design Process (Cont.) – June 18, 2007

  • PROJECT TEAM ADJUSTMENTS – If required
  • READING ASSIGNMENT (BEFORE THE CLASS SESSION):
  • Appendix A.1
  • LECTURE TOPICS (Conceptual & Preliminary System Design)
  • Identification of Need (Mission Analysis)
  • Quality Functional Deployment
  • Systems Requirements Analysis

Session 5: Systems Design Process (Cont.) – June 25, 2006

  • PROJECT TEAM ADJUSTMENTS – If required
  • READING ASSIGNMENT (BEFORE THE CLASS SESSION):
  • Appendix A.1
  • LECTURE TOPICS (Conceptual & Preliminary System Design)
  • Functional Analysis & Allocation

Session 6: “White Paper Presentations” July 2, 2007

  • EXERCISE 1: REQUIREMENTS
  • EXERCISE 2: FUNCTIONAL ANALYSIS
  • WHITE PAPER PRESENTATIONS FROM PROJECT TEAMS

Session 7: “White Paper Presentations” (Cont.) & Midterm July 9, 2007

  • WHITE PAPER PRESENTATIONS FROM PROJECT TEAMS
  • MIDTERM

Session 8:Systems Design Process (Cont.) – July 16, 2006

  • READING ASSIGNMENT (BEFORE THE CLASS SESSION)
  • Chapter 5 & 6
  • LECTURE TOPICS (Detailed Design & Test)
  • Design / Build Activities
  • Synthesis
  • Verification & Validation

Session 9:Systems Design Process (Cont.) – July 23, 2007

  • READING ASSIGNMENT (BEFORE THE CLASS SESSION):
  • Chapter 7 & 19 section 4 (19.4)
  • EXERCISE 3: DESIGN SYNTHESIS
  • EXERCISE 4: VERIFICATION
  • LECTURE TOPICS (System Analysis)
  • Trade Studies
  • Effectiveness/ Cost Analysis
  • Risk Management

Session 10: Design for Operational Feasibility – July 30, 2007

  • READING ASSIGNMENT (BEFORE THE CLASS SESSION):
  • Chapter 12 – 17 & CAIV article
  • EXERCISE 5: TRADE STUDY
  • EXERCISE 6: RISK MANAGEMENT
  • LECTURE TOPICS (Design for Operational Feasibility)
  • Design for Operational Feasibility (Specialty Engineering)
  • Affordability

Session 11: Systems Design Evaluation (Control) – August 6, 2006

READING ASSIGNMENT (BEFORE THE CLASS SESSION)

  • Chapter 11
  • EXERCISE 7: AFFORDABILITY
  • EXERCISE 8: SPECIALTY ENGINEERING
  • LECTURE TOPICS (System Control)
  • Baseline & Configuration Management
  • Interface Management
  • Technical Performance Measurements
  • Quality & Control Concepts

Session 12: Systems Engineering Management – April 16, 2006

READING ASSIGNMENT (BEFORE CLASS SESSION):

  • Chapters 18 & 19
  • EXERCISE 9: TECHNICAL PERFORMANCE MEASUREMENT
  • LECTURE TOPICS (SYSTEMS ENGINEERING PLANNING & ORGANIZATION AND PROGRAM MANAGEMENT AND CONTROL)
  • Integrated Product & Process Development
  • Integrated Master Plan and Integrated Master Schedule
  • Work Breakdown Structure
  • Capability Maturity Models

Session 13: Team Presentations – April 23, 2006

  • EXERCISE 10: INTEGRATED PLANNING
  • TEAM PRESENTATIONS OF SEMP or SPECIFICATION
  • SUBMIT TWO (2) COPIES OF SEMP or SPECIFICATION FOR REVIEW AND GRADE

Session 14: Team Presentations (Cont.) – May 7, 2006

  • TEAM PRESENTATIONS OF SEMP or SPECIFICATION
  • FINAL EXAM

International Council of Systems Engineers (INCOSE) The International Council on Systems Engineering is a not-for-profit membership organization founded in 1990. INCOSE is an international authoritative body promoting the application of an interdisciplinary approach and means to enable the realization of successful systems.

UNIVERSITY OF SOUTHERN CALIFORNIA
SYSTEMS ENGINEERING MANAGEMENT PLAN (SEMP) & SYSTEMS REQUIREMENT DOCUMENT TEAM PROJECT

INSTRUCTIONS & REQUIREMENTS

RATIONALE: The Systems Engineering Management Plan (SEMP) guides and controls the technical efforts of a project. The SEMP reflects an integrated technical effort responsible for product development that balances all the factors with meeting a system’s life cycle requirements. The SEMP is a living document and needs to be structured to allow for ease of updating reflecting changes and progress throughout a stage of the life cycle.

Technical requirements are documented through a series of specifications. The single most important engineering design document, defining the system functional baseline including the results from the needs analysis, feasibility analysis, operational requirements and the maintenance concept, top level functional analysis and allocation and identifying critical key performance parameters (KPPs) is the Systems Specification.

Selection of the project may be based on the Students’ own development or possible related to one or more of the students’ area of work. The aim of the team systems engineering plan is to allow each student to apply the course concepts in a real world application.

The following guidelines should be observed.

GUIDELINES: Each team should develop the concept or idea collectively, by adhering to the following criteria:

  • The project must involve at least the entire team as full time persons over the project’s duration. The delivered document shall address a system whose life cycle would be sufficient to occupy the delivering team with full time engineering tasks for at least (but not significantly more than) 6 months. The portion of the life cycle addressed should cover acquisition to commencement of use and may or
    may not include disposal, depending upon the system.
  • The plan may contain both “internal” labor and “external” (or subcontracted) services. Subcontracting for
    services is very much in keeping with current IPPD practices.
  • The students may draw upon a project concept or non-executed project related to his/her work, providing these conditions are met:
  • The choice of the project must not involve disclosure of proprietary information or other data of a proprietary nature peculiar to the organization. If used at all, such information or data must be disguised or altered.
  • The project has not been implemented to date, not is the project readied for implementation. Use of an implemented project plan would constitute an unethical practice. The student may draw upon studies related to an implemented project, document such use, or draw upon components of a larger project in which the student is involved, where, in the later case, the student knows that the component has not been implemented.

HOW TO DECIDE/SELECT A PROJECT: First, examine possible topics based upon a discussion with your team members and your instructor, you may have a number of very workable engineering topics available to you. Here are some topics:

Development of a new or modifying an existing system

The more critical items to consider in selecting the topical area for your project are:

  1. You are interested in the project’s concept(s) and you could use the project as a reference point across this course.
  2. There is enough substance in the project, organizational relevance, or institutional basis, to justify the time and effort.

SELECTION OF TEAM MEMBERS:

The information you provided in the STUDENT PROFILES is used for creating the Project Teams. Several criteria will be used,

Including

  • Similarity of interest or industry in which is employed
  • Diversity in level of experience in systems engineering

Note: Optionally the students may wish to organize their own teams with minimum instructor intervention.

WHAT’S EXPECTED OF EACH TEAM? WHAT SHOULD EACH PROJECT PLAN ENTAIL?

The “white paper” for the SEMP or SPECIFICATION is due in Session #6 and presentations shall be made in Sessions #6 and #7. The final project is due Session #13 and presentations shall be made in Sessions #13 & #14. Each team shall present its report to the rest of the class. The observing students and the instructor shall play the role of senior corporate managers. You are encouraged to comment or ask or ask questions of the project team making the presentation. Your instructor shall also be the moderator. The use of visual aids or handouts is up to the discretion of the presenting teams.

It is strongly suggested that you set up a schedule for your project’s completion. This is not only good practice, it will give you a sense of what a schedule means.

Session 6 & 7 – Initial “White Paper” Presentation

After getting together and selecting a project, each team shall develop a top-level “White Paper” proposal, which should incorporate the following elements. This presentation simulates the act of “defining the problem” and “performing the process planning” of the project:

The “paper” shall be orally presented to the class in any form or media the presenting team decides. Much of the content developed for this session’s presentation should be salvageable for final plan or specification.

Session 13 & 14 – Final Presentations

This presentation highlights the important “How To” points of the written SEMP or SPECIFICATION, which shall be submitted in Session 13.

BY ALL MEANS, IF YOU HAVE QUESTIONS ON THE LEVEL OF DETAIL, FORMATS, OR EXPECTED STANDARDS ASK.