 |
|
|
|
|
|
|
|
 |
|
||||||
 |
 |
 |
 |
 |
 |
 |
|
|
|
|
 |
|
|
 |
 |
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
All material on this web site is copyrighted by Honourcode, Inc. 1999-2012.
Requirements Development
One of the most significant impacts a systems engineer can have on a project is to ensure the successful identification, analysis and allocation 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. It identifies the sources and types of requirements, including the processes to work from operational definitions into technical requirements. A process for conducting a requirements analysis is presented along with exercises of several requirements analysis methods. It includes techniques to allocate the requirements to the system architecture. Source documents for guidance on drafting requirements documents are also presented along with some of the common software tools used to support requirements analysis and allocation. |
 |
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 product system:
- 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.
| Attend this course if you are:
|
The course is aimed at
|
Course Topics
| 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. Defining Requirements – The
Concept of Operations as a starting point for requirements. Diagrams
for operational definition. How to convert operational definition
into technical requirements. Mission analysis as an engineering
technique. The roles of functions and functional analysis. Exercises
in mission analysis and defining requirements. |
Writing Requirements – Documentation methods for both contracted (one customer under contract) and product (commercially developed) systems. New forms of requirements in agile and extreme development. Specification writing methods and rules. Grammatical constructs and their importance in requirements. Exercises in writing and evaluating requirements, assisted by the “Tiger Pro” requirements evaluation tool. Requirements Analysis – Methods
to ensure that systems requirements are complete, coherent, and
cohesive. Diagramming techniques for functional flow block diagrams,
structured analysis (data flow diagrams), real time state space
analysis, behavior analysis, object oriented analysis, and IDEF
diagramming. Introduction to UML and SysML and their use for requirements
analysis. Strengths and weakness of each method. Survey of software
tools available for requirements analysis. Instructor-led and group
exercises in several methods. |
Requirements Allocation – Requirements as engineering tools during the system architecting and design phases. Allocation methods with examples – direct allocation, apportionment, derivation. Application of requirements management techniques to handle continuous change. Survey of software tools available for requirements management. Exercises in requirements allocation. Continuing Education: This course qualifies for 1.4 CEUs or 14 PDUs |
The Instructors
 Mr.
Eric Honour, CSEP, has been in international leadership of
the engineering of systems for a dozen 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 (International Council on Systems Engineering)
Technical Board in 1994, was elected to INCOSE President for 1997,
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 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, including the Air Combat Maneuvering Instrumentation
systems, the Battle Group Passive Horizon Extension System, the National
Crime Information Center 2000, and the DDC1200 Digital Zone Control
system for heating and air conditioning. Mr. Honour now heads Honourcode,
Inc., a consulting firm offering effective methods in the development
of system products. Mr. Honour has a BSSE (Systems Engineering) from
the US Naval Academy, MSEE from the Naval Postgraduate School, and
is a doctoral candidate at the University of South Australia. |
 Dr.
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. |
Page last modified 6 Oct 12