Course #508-14-SNEC-1

Systems Engineering: Requirements Development and Management

Dates: Apr-02-2014 - Apr-02-2014


I Square Systems

55 John Clarke Road

Middletown, RI  02842

Hours: 8:30am-5:00pm


$150 Government AFCEA Member
        Government Non Member
        Non-Government AFCEA Member
$200 Non-Government Non Member

Special Pricing!!! Full Time Students and Young AFCEANS call 703-631-6137 or email to register.
This course is offered online simultaneously with the classroom version. Save on travel costs and take this course from your home or office. Be sure to indicate whether you are selecting online or classroom attendance during registration.
Note: Please see details in Course Description. 1.Readings may be recommended for class preparation. 2.Education credit details are listed below.

Course Description:


Pre-Requisites:  None.  It is recommended that the student become familiar with either the ISO/IEC/IEEE 29148-2011 specification or most recent INCOSE Handbook. Another reference: Body of Knowledge and Curriculum to Advance Systems Engineering (

This one day class is the first course of a six course series in our C4I Systems Engineering Certification Preparation Program. The objective of the program is to prepare civilian and government professionals to define, develop, design, integrate, test, deploy and sustain C4I (Command, Control, Communications, Computer, and Intelligence) systems for joint military and civilian crisis management operations as from a systems engineering viewpoint.

The course will focus on stakeholder requirements gathering, documentation and management methods.   In addition, the course is designed to provide the necessary C4I SE methods, case studies and exercises to help prepare students to take the International Council on Systems Engineering (INCOSE) Certified Systems Engineering Professional (CSEP) examination series.

C4I systems encompass systems, procedures and techniques used to collect and disseminate information. C4I includes intelligence collection and dissemination networks, command and control networks and systems that provide the common operational/tactical picture. It also addresses Information Assurance (IA) products and services, as well as communications standards that support the secure exchange of information by C4ISR systems. C4ISR technologies (i.e. Information Technology (IT) and Communication and Network Systems) are at the heart of modern crisis management operations.

Crisis management is growing more complex; involving collapsed state institutions, humanitarian catastrophes, human rights violations, displacement and refugees. These developments highlight the need to intensify co-operation between different sectors of civilian and military organizations. C4I systems provide the means for connectivity in support of collaboration among different Services, agencies, and nations.

After completion of class, the student will receive a class completion certificate from AFCEA and email attendance documentation which can be submitted to Global Information Assurance Certification (GIAC) in support of 6 certification maintenance units (CMUs) in support of GIAC cyber security certifications.  To apply for CMUs an individual must purchase an account with GIAC.  Please see

The class, while not prequalified by the International Council on Systems Engineering (INCOSE), does touch on knowledge areas defined by INCOSE's list of Professional Development Activities, and will likely qualify for Professional Development Units (PDUs).   Please review INCOSE's online renewal requirements


this course has been approved for George Mason University (GMU) continuing education units (CEUs) and students can apply to GMU for formal documentation of CEUs earned. 

This course was developed and is maintained by AFCEA's Southern New England Chapter ( the support of AFCEA's Professional Development Center. Stay tuned . . . additional courses in the series to be announced.

Who Should Attend: 

The course is oriented towards Government/Industry systems engineers who are seeking to expand their current engineering skill set and apply it to a C4I domain.  It's also applicable towards personnel seeking a greater systems engineering methodology understanding.  Academia would benefit from its solid systems engineering foundation.

Online Access Requirements:

Prior to signing up and participation, verify online Blackboard/Coursesite classroom web access using laptop from desired location.  Do Steps 1 & 2 (OS/Java confirmation, system requirement info and pseudo classroom system test) as instructed using this link:

Systems Engineering Requirements Development and Management Outline:

Section 1: Requirements Overview

1.0       Overview


2.0       Assumptions, Definitions, Context, Big Picture, Analysis


3.0       Types of Requirements


4.0       Definition of Requirement and Set of Requirements


5.0       Requirements Relationships versus Systems Engineering


6.0       Types of Requirements


Section 2: Requirements Development

1.0        Overview: Creating Order From Chaos

2.0       Stakeholder Analysis

           -          Identify, Interview, Research


3.0       Information Analysis Tools and Development

           -          Affinity Diagram, Pareto Analysis, Input/Output Model

           -          Development of Originating Requirements


4.0       Operational Concepts (CONOPS)

           -          Definition, Process, Hierarchy


5.0       External Systems or Concept Diagram


6.0       Stakeholder Requirements and Development


7.0       System Requirements Development


Section 3: How to Write Requirements

1.0       Standard Formats

           -          INCOSE Handbook (Latest Version)

           -          ISO/IEC/IEEE 29148-2011


2.0       Grammar


3.0       Characteristics of Well Written Requirements

           -         Necessary (Traceability), Design Independent, Unambiguous, Complete

           -         Singular, Feasible, Verifiable, Correct, Grammatically Correct


4.0       Characteristics of Requirements Sets

           -         Unique, Complete, Consistent, Feasible (Attainable)

           -         Bounded, Comparable, Structured, Modifiable


5.0       Language to Avoid

           -         Open-Ended, Non-Verifiable, Comparative, Loopholes, Incomplete References, Negative Statements


6.0       Attributes of Requirements

           -         Additional Elements –Minimum, Unique Identifiers, Source, Rational, Type, Stakeholder Priority, Dependency, Risk, Difficulty


Section 4: Requirements Management

1.0       Definition

2.0       Requirements Traceability, Verification and Change Control

3.0       Requirements Management Tools

              -  DOORS

           -  CORE

           -  SysML

4.0       Exercise:  Manage Requirements Using MS Excel


Mr. Patrick Roach has thirty years of systems engineering experience. He served five years as a nuclear trained submarine officer, serving in USS Skipjack (SSN-585). After leaving active duty, Mr. Roach worked for a defense contractor performing various systems engineering tasks including Reliability, Maintainability, and Availability (RMA), and System Safety. After becoming a government employee, Mr. Roach continued his System Safety and RMA work, as well as Requirements Analysis, System Architecture, Systems Integration and Test. Mr. Roach has served as System Integration Team leader in two submarine program offices. Mr. Roach has a BS in Naval Architecture from the United States Naval Academy and an MS in Systems Engineering from the Naval Post Graduate School.