All material on this web site is copyrighted
by Honourcode, Inc. 1999-2016.
One of the most significant impacts a systems engineer can have
on a project is to ensure the successful identification, analysis,
allocation and management of requirements. This course provides
both lecture and practical work on the creation and use of requirements
in a system development.
The course begins with an overview of the purpose and use of requirements.
We identify the possible sources of requirements, and how to define
requirements from each type of source. We teach how to write requirements,
with practical hands-on practice on each type of requirement. We
also focus on the entire set of requirements, with methods to graphically
analyze the requirements to ensure completeness, correctness, and
cohesion. We teach requirements allocation, how to decompose high-level
requirements into lower-level requirements that create meaningful
practical specifications for the system components. Finally, we
look at the structure and tools for requirements management, to
ensure that all requirements are met and that non-required features
are not created.
The proper use of requirements is one of the core tools of complex systems
engineering. From beginning to end, good systems engineers use requirements
as the primary definition for the system and its elements, to help the
- Meet the operational and customer needs
- Fit within the intended system environment
- Provide sufficient robustness and reliability
- Offer appropriate flexibility
- Meet the entire life cycle
Register here to receive more information
on our courses.
course if you are:
- Faced with requirements challenges or program overruns
- Designing or redesigning large systems and need better technical
- Transitioning from software engineering to systems engineering.
- Improving your systems engineering skill set.
is aimed at
- Product engineers
- Systems engineers
- Design engineers
- Acquisition and contracts personnel
- Program/project managers
- Test and logistic support leaders
- Others who participate in defining/using requirements in system/product
Requirements Overview –
What are requirements and how do they fit in to system development?
Context of system development models. Role of requirements. Importance
of requirements. Requirements cycles for contracted, R&D, and
Stakeholder Requirements –
Defining the system at its highest level, in terms of the stakeholder
needs. The basic steps in understanding a new system. Problem definition
with the stakeholders. System boundaries and life cycle. System
environment. Define the need in operational terms. What to do with
the operational descriptions. Quantify the need to allow effective
trade offs. Application of SysML diagrams for operational definition.
Defining Requirements –
How to convert operational descriptions into technical requirements.
Five types of requirements and the characteristics of each type.
Create functional and performance requirements using mission analysis
as an engineering technique. Interface requirements as a definition
of system boundaries; how to create them. Constraint requirements
on the system, its environment, and its development. Verification
requirements as the basis for system proof. Requirements document
types – specifications, use cases, agile, SCRUM. Formal equirements
Requirements Analysis – Methods
to ensure that systems requirements are complete, coherent, and
cohesive. Working with requirements interactions. Diagramming techniques
to evaluate sets of requirements. Useful SysML diagrams: use case,
activity, state machine diagrams. Strengths and weakness of each
Case Study – Small-group
study of a virtual development project in five segments to apply
the learned methods. Defining the need; Converting stakeholder requirements
to technical requirements; Writing good requirements; Requirements
analysis; Requirements allocation.
Requirements Allocation –
Requirements as engineering tools during the system architecting
and design phases. Overview of system architecture and how requirements
are used to define components. Allocation methods with examples
– direct allocation, apportionment, derivation. Application
of allocation methods to different types of high-level requirements.
Architectural design using requirements
Requirements Management –
Using a requirements database to allow requirements to guide the
design. Requirements management methods; when to do what tasks.
Feedback to the system development so that requirements act as the
guide. Ensuring the system meets all requirements and does not add
unnecessary functions. The link between requirements management
and system verification. Attributes of requirements management databases.
Survey of requirements management tools. Simple management in Excel
Continuing Education: This course qualifies for 2.1 CEUs or 21
Eric Honour, CSEP, INCOSE Fellow, and former INCOSE President,
has been in international leadership of the engineering of systems
for over 20 years, part of a 40+ year career of complex systems development
and operation. His energetic and informative presentation style actively
involves class participants. He was the founding Chair of the INCOSE
Technical Board in 1994, and served as Director of the Systems Engineering
Center of Excellence (SECOE). He was selected in 2000 for Who’s
Who in Science and Technology and in 2004 as an INCOSE Founder. He
is on the editorial board for Systems Engineering. He has
been a successful entrepreneur, systems engineer, engineering manager,
and program manager at Harris Information Systems, E-Systems Melpar,
and Singer Link, preceded by nine years as a US Naval Officer flying
P-3 aircraft. He has led or contributed to the development of 17 major
systems.. Dr. Honour has a BSSE (Systems Engineering) from the US
Naval Academy, MSEE from the Naval Postgraduate School, and PhD from
the University of South Australia based on his ground-breaking work
to quantify the value of systems engineering.
Scott Workinger has led innovative technology development
efforts in complex, risk-laden environments for 30 years in the fields
of manufacturing (automotive, glass, optical fiber), engineering and
construction (nuclear, pulp & paper), and information technology
(expert systems, operations analysis, CAD, collaboration technology).
He currently teaches courses on program management and engineering
and consults on strategic management and technology issues. Scott
has a B.S in Engineering Physics from Lehigh University, an M.S. in
Systems Engineering from the University of Arizona, and a Ph.D. in
Civil and Environment Engineering from Stanford University.
Glen Francisco (CSEP, PMP) has over 17 years of experience
developing new technologies, service, products, and applications for
both private and government uses. He has a personable, engaging teaching
style that keeps a class alive with information. He has worked as
an engineer, Lead Systems Engineer, Project Engineer and Program Manager
for a number of military & commercial companies to include Boeing
(McDonnell Aircraft Company), Lockheed Martin (Martin Marietta), Texas
Instruments, Raytheon, ELCAN Optical and DRS Technologies. His product
systems have supported security surveillance, paramilitary (fire,
police & EMS), automotive and industrial markets using passive
thermal imaging technologies and other wavelength illuminated electo-optical
imaging laser radar technologies. He was selected in the 2006 Marquis
Publication of Who’s Who in America. Glen has presented over
a dozen papers at security & defense symposium. He holds multiple
patents in active terminal guidance missile trajectory control and
low cost plastic thermal management. He is a firefighter, emergency
medic, firefighting instructor, and private pilot. He developed &
introduced Thermal Imaging Cameras into the firefighting market in
2001, technology saving hundreds of lives and millions of dollars
Page last modified 12 May 17