Requirements Practice

Course Group: 
Systems Engineering

COURSE OVERVIEW

Effective and efficient requirements practices are essential if complex systems are to be developed to meet users' expectations without being delivered late and over-budget. This course provides a broad overview of all aspects of requirements engineering, without focusing on any particular detailed technique or tool (although the requirements for those approaches and applications are clearly identified). The course has a strong practical element, both in terms of the introduction to the topic, as well as formal practice through exercises.

While there is no fixed pre-requisite background required for this course, some familiarity with the systems engineering discipline is assumed.  Prior attendance at the Introduction to Systems Engineering course, or equivalent, is recommended.

Who Should Attend

Course Outline

Presenter Background

Dates & Registration

Duration: 5 days

Delivery mode: Classroom

Locations

Advertised: Canberra & Melbourne

In-house: All states and neighbouring countries, contact the  for more information. Recommended for groups of 10 or more.

What you will receive:

  • Comprehensive course notes
  • UNSW Canberra certificate of completion/attendance*
  • Morning tea, lunch and afternoon tea
  • Micro-credentials: Successful completion of the full five days of Requirements Practice will provide students with advanced standing in the postgraduate micro-credential 3UoC course ZEIT8240 Requirements Practice KnowledgeFor more information on postgraduate credit please visit our Postgraduate Credit and Micro-Credential page.
  • Masters credit: UNSW Canberra allows students who have successfully completed a minimum of 12 days of approved professional education courses to use those courses as credit in eligible postgraduate programs. 

Affiliated courses: Introduction to Systems Engineering (3 days) & Systems Engineering Practice (5 days)

*pending final results

 


 

WHO SHOULD ATTEND

Anyone requiring an understanding of good requirements practices;

Business Managers Project Technical Staff
Project Managers Systems Engineers
Capability Development Staff Hardware and Software Engineers

 


 

COURSE OUTLINE

Introduction

Brief revision of systems, systems engineering, and the role of requirements engineering | Overview of requirements engineering | Relevance and benefits of requirements engineering

Requirements Engineering Framework

Framework | Business needs and requirements | Stakeholder needs and requirements | Stakeholder management | Requirement characteristics| Requirements attributes | Definitions | Requirements elicitation | Requirements validation | Requirements management | Requirements management tools | Requirements engineering tools (requirements breakdown structure and functional flow block diagrams)

Conceptual Design

Define business needs and requirements | Define stakeholder needs and requirements | Define system requirements | Identify stakeholders | Mission, goals, objectives | Validation measures | Context diagram Conceptual Design tutorial

System Requirements

System requirements framework | Define functional/non-functional requirements | Define performance requirements | Define verification requirements | Assign rationale

Writing and Reviewing Requirements

Guidelines for good requirements | Standard requirements templates or boilerplates | Requirements language | Removing ambiguity | Guide for writing requirements | Requirements review tutorial

Defence Capability Definition Documents

Systems acquisition in Defence | Operational Concept Document (OCD) | Function and Performance Specification (FPS) | Test Concept Document (TCD) | Early Test Plan (ETP) | Test and Evaluation Master Plan (TEMP)

Requirements Engineering Exercise 1

This exercise comprises a number of small tasks, each of which is designed to reinforce the teaching points in the preceding instruction. The tasks build on each other to provide participants with a firm practical base of the major exercise.

Requirements Engineering Exercises 2 and 3

These exercises are focused on the activities required to get from early business needs to writing the system-level requirements for a relatively straightforward system based on a functional architecture defined by the major systems-engineering products of Conceptual Design. The exercises provide participants with practice in all aspects of requirements engineering as introduced by the course.

 


 

Mike Ryan  DR MIKE RYAN

 

Dr Mike Ryan holds BE, MEngSc and PhD degrees in electrical engineering from the University of New South Wales. He is a Fellow of Engineers Australia (FIEAust), a Chartered Professional Engineer (CPEng) in electrical and ITEE colleges, a Senior Member of IEEE (SMIEEE), a Fellow of the International Council on Systems Engineering (INCOSE), and a Member of the Australian Institute of Management (AIMM). Since 1981, he has held a number of positions in communications and systems engineering and in management and project management. Since 1998, he has been with the School of Engineering and Information Technology, University of New South Wales, Canberra where he is currently the Director of the Capability Systems Centre. His research and teaching interests are in communications and information systems, requirements engineering, systems engineering, and project management. He is the Editor-in-Chief of an international journal, and is the Chair of the Requirements Working Group of INCOSE. He is the author or co-author of twelve books, three book chapters, and over 180 technical papers and reports.

No dates? Or unable to attend dates shown? Submit an Expression of Interest below to be notified of upcoming courses.

 

COURSE AVAILABILITY

CANBERRA
15 May 2017 - 19 May 2017