Semester 1
Name: Peter de Haan

Short Bio:
After graduating from the University of South Australia in 1994, Peter worked predominately in the defence industry in software/systems engineering roles across a variety of projects providing him with exposure to the systems/software development lifecycle. Projects on which Peter has worked include: ANZAC Frigate Combat System, Jindalee and JORN Radar Systems, Seahawk Helicopter Simulator and Naval Imaging Systems. Outside of defence, Peter’s projects included control systems for Steel Rolling Mill and a prototype Train Simulator driver trainer. During a 5 year tenure at BAE Systems Peter was the Systems/Software Engineering Environment Lead for the Engineering Division with a brief that oversaw all BAE Systems projects in Australia. After taking a sabbatical during which he became an owner/builder to oversee the building of his bespoke home, Peter has taken up a position as a Project Officer in the Performance and Stress Testing Group for QA Operations Branch, Department of Human Services while undertaking an MBA at the University of Adelaide http://www.linkedin.com/in/dehaan

Email: peter.dehaan@adelaide.edu.au

Phone: +61 8 8313 7422


Semester 2
Email: d.harvey@adelaide.edu.au

Opening intensive:
Thursday 30th & Friday 31st July 2015
9am-6pm
Nexus10 UB34 Seminar Room 3G
 
Closing intensive:
Tuesday 22nd & Wednesday 23rd September 2015
9am-6pm
Nexus10 UB34 Seminar Room 3G

1	Knowledge and understanding of the concepts and techniques of systems engineering.
2	Knowledge and ability to capture, interpret and document the systems requirements and activities associated with the analysis and design of systems.
3	Knowledge and ability to develop the requirements for systems engineering integration verification and validation.
4	Knowledge and ability to promote team work and effective communications in the development and support of systems engineering within projects.
5	Knowledge and understanding of the application of design techniques and appropriate technologies to support the systems engineering process.
6	Appreciation of the benefits of continuing personal and professional development in the rapidly developing and increasingly complex field of systems engineering and integration.
7	Appreciation of the leadership roles and knowledge of the skills required to encourage wider community involvement in the successful and sustainable development and management of the systems associated with projects.
8	Appreciation of ethical, social and cultural issues and an understanding of the implication of these issues in the sustainable development and management of the systems associated with projects.

The University’s preferred textbook supplier is Unibooks: http://www.unibooks.com.au/ 

Text book:
Richard Stevens, Peter Brook, Ken Jackson and Stuart Arnold, (1998), “Systems Engineering – Coping with Complexity", Prentice Hall, ISBN 0-13-095085-8

There is a wide range of material on the course topic available. The following provides some additional reading guidance if you are interested in reading further on the topic.

Blanchard, Benjamin S. and Fabrycky, Wolter J., 1990, The System Design Process, C3, Systems Engineering and Analysis, Prentice Hall,
Hitching, Derek, K., 1992, Understanding Systems, C1, Putting Systems to Work, John Wiley
Lacy, J., A., 1994, C2, Systems Engineering Activities, from: Systems Engineering Management, McGraw-Hill,
Wieringa, R., J., 1996, Systems, C2, Requirements Engineering, John Wiley
Robertson S and Robertson J, 1999, C5, Trawling for Requirements, Mastering the Requirements Process, Addison – Wesley,
Grady, J O, 1993, Structured Analysis, Structured Analysis from: System Requirements Analysis, McGraw-Hill,
DAU (Defense Acquisition University) Design Synthesis, Defense Acquisition University Press, Fort Belvoir,
The Test and Evaluation Process: excerpt from The Test and Evaluation management Guide, Defense Acquisition University Press, Fort Belvoir, 2001
NAS Systems Engineering Manual,
Sproles, Noel, 2002, Formulating Measures of Effectiveness, Systems Engineering Vol 5, No 4, (5.2) © 2002 Commonwealth of Australia. Exclusive worldwide publication rights in the article have been transferred to Wiley Periodicals
Clark, James and Johnson, James, A Primer on Logistics, webalmc.lee.army.mil/issues/MayJune02
Blanchard, Benjamin, 1998, Measures of Logistics, Chapter 2 of Logistics Engineering and Management, 5th Edition, Prentice Hall
Blanchard, Benjamin, 1991, Case Study Examples, Systems Engineering Management, John Wiley
Strengers, G, Development of Operational Concept Descriptions, Tenix Systems Division.
Kapurch, S. J. (ed), 2010, NASA Systems Engineering Handbook, Diane Publishing Company
Walden, D and Roedler, G (eds), 2015, INCOSE Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities, 4th Edition, John Wiley

Library Resources
The University of Adelaide’s Barr Smith Library provides a range of learning resources including texts, journals, periodicals, magazines, and access to online databases and information services. It also offers a virtual library which is accessible via the University’s website. The University Library web page is: http://www.adelaide.edu.au/library/ 
From this link, you are able to access the Library's electronic resources.

Other resources
If you are a member of the PMI (http://www.pmi.org/Membership.aspx) you will “gain exclusive access to PMI publications and our global standards*, networking options with our chapters and online communities of practice, and leadership and volunteer opportunities. You’ll also receive discounts on certification exams and renewals, as well as our professional development offerings.” Student membership is USD$40 to join and USD$30 to renew.

* Log in to access complimentary read-only PDFs of all of PMI's published standards or take advantage of discounts on paperback editions
http://www.pmi.org/PMBOK-Guide-and-Standards/Standards-Library-of-PMI-Global-Standards.aspx

MyUni is the University of Adelaide's online learning environment. It is used to support traditional face-to-face lectures, tutorials and workshops at the University. MyUni provides access to various features including announcements, course materials, discussion boards and assessments for each online course of study (see: https://myuni.adelaide.edu.au)

This course is offered in blended learning mode with the face-to-face component offered as intensives.

As a guide, a 3 unit course comprises a total of 156 hours work (this includes face-to-face contact, any online components, and self directed study).

This is a draft schedule and session dates are a guide only. The timetable may be changed during the course delivery if necessary.

Learning Activities Summary

Intensive	Content	Readings	Activities
1	Introduction to Systems Engineering	Stevens Chapter 1 and 2	Report Questions Class exercise
	Requirements Engineering	Stevens Chapter 3	Report Questions Class Workshop
2	System Design	Stevens Chapter 4	Report Questions Class exercise
	Verification and Validation	Stevens Chapter 5	Report Question Class exercise
3	Systems Analysis	Stevens Chapter 11	Report Questions Class exercise
	Operational Concept Documents	Strengers, G Development of Operational Concept Descriptions (see readings)	Report Questions Class exercise
4	Engineering Specialties	Chapter 2, “The Measures of Logistics” from: Blanchard B, 1998, “Logistics Engineering and Management”; Prentice Hall	Report Questions Class exercise
	Systems Engineering Management	Stevens Chapters 6,7,8 and 13	Report Questions Class exercise

None

Assessment No.	Form of Assessment/ Collaborative Task	Length (in word count)	Due	Weighting	Learning Outcome
1	Class Participation	n/a	10%	ongoing	1,3,6-8
2	Group Assignment	2000 words	25%	See MyUni	1-5
3	Individual Reports (2)	2 reports or 1500 words	30%	See MyUni	1,3,5
4	Individual Assignment	3000 words	35%	See MyUni	1,5-8
	Total			100%

Students must complete all course assessment requirements and must attend lectures to be eligible to pass the course.

Course results are subject to moderation by the ECIC Board of Examiners

Assessment 1: Class participation
Weighting: 10%
Due Dates: ongoing
Submission Details: N/A

Task:
Attend all intensives and contribution to exercise and the workshop conducted.

Criteria by which your assessment will be marked:
Involvement and contribution to class activities

Learning objectives with this assessment (refer to section 2.1): 1,3,6,7,8


Assessment 2: Group Assignment
Weighting: 25%
Due Dates: See MyUni
Submission Details: Online through MyUni via Turnitin

Task:
Question 1:
Perform a Requirements Analysis for your chosen system:
Answers to this question must include but are not limited to:-
· Provide overview material for the system such that the reader is provided with an understanding of the system under review.
· Construct a context diagram.
· Construct two specific mission analyses.
· List the constraints on the project and the system.
· Select three requirements for analysis. Determine if each requirement is considered a good requirement, ie unambiguous, complete, consistent, demonstrable, states “what” not “how”, and is correct. Check that any performance criteria are reasonable. Utilise the primitive requirement analysis technique and the requirement parsing technique where appropriate. Determine the requirement type (quantitative, qualitative, derived, allocated) for each requirement. List any queries and address these with the customer to clarify each requirement, where necessary.
· Identify derived requirements.
· Construct a Requirements Traceability Matrix, listing all the requirements, including those derived and allocated. Identify if requirement is functional, or non-functional.

Question 2:
Provide a Functional Analysis of the chosen system:
Answers to this question must include but are not limited to:-
· Prepare a functional hierarchy for the system.
· Construct a level 1 FFBD for the System. Expand this diagram to level 2.
· Create an N2 chart for the System. Indicate all the functional interfaces at level 2.
· Develop a timeline diagram for the System mission and another lower level timeline for a critical performance requirement of the System.
· Identify the verification method for each function shown in the level 2 FFBD.
· Update the traceability matrix mapping requirements, functions and verification methods.
If a requirement cannot be readily mapped to a function, review your functional decomposition and make adjustments as required. Reflect all alterations in diagrams.

Scope:
This assignment will assess your understanding of the requirements engineering and functional analysis course topics.

Length and Presentation:
Nominally 2000 words (per student in the team), but the length of the assignment will be governed by the choice of subject matter and therefore can vary greatly;.

Criteria by which your assessment will be marked:
The assignment is divided into two questions of which the Requirements Traceability Matrix is common to both. Due to the importance of the role of requirements in systems engineering questions have been weighted as follows:
· Question 1: will attract 60% of the assessment
· Question 2: will attract 40% of the assessment

The assignment will be graded on
· Logic and flow of argument (logical linkages in the material presented);
· Ability to present relevant material clearly and succinctly;
· Application of key relevant theories and concepts; and
· Relevance to the topic.

Learning objectives with this assessment (refer to section 2.1): 1,2,3,4,5

Assessment 3: Individual Reports (2)
Weighting: 30%
Due Dates:
Report 1: See MyUni
Report 2: See MyUni

Submission Details: Online through MyUni via Turnitin link

Task:
Exercises from the course topics to be nominate during lectures, provide answers to one per report (4 in total). The questions will be drawn from the course notes and will be determined by the lecturer based on needs of the each course cohort.

Scope:
Possible text here: Reports 1 and 2 will assess your understanding of the course topic presented over days 1 and 2

Length and Presentation:
1500 words each report

Criteria by which your assessment will be marked:
· Logic and flow of argument;
· Ability to present your findings clearly and succinctly;
· Application of key relevant theories and concepts;
· Research skills and use of data to support the analysis;
· Relevance to the topic.

Learning objectives with this assessment (refer to section 2.1): 1,3,5



Assessment 4: Individual Assignment
Weighting: 35%
Due Dates: See MyUni
Submission Details: Online through MyUni via Turnitin link

Task:
This assignment is a continuation of work begun in Group Assignment. The same system should be used for this assignment as used in the group assignment..

Question 1: Provide a Functional Allocation and Synthesis of the chosen system:
Answers to this question must include but are not limited to:-

Construct a system physical hierarchy for the system under study.

Identify any trade studies that may be appropriate.
· Allocate function(s) to each physical element. If a function cannot be readily mapped to an element, review your functional and physical architectures and make any adjustments as required. Reflect the alterations in the appropriate diagrams.
· Update the traceability matrix. Check that the verification methods are still appropriate for each requirement. If not, update the traceability matrix appropriately and flag modifications to the customer for discussion.

Question 2: Provide Systems Analysis elements of the chosen system by:
· Creating a State Transition Diagram for the System.
· Select one of the trade studies you identified above and list the potential alternate solutions. Use the Pugh’s controlled convergence method to help select the best solution.


Question 3: Speciality Engineering:
· Identify any human factors that need to be taken into consideration and reflected in the requirements.
· Identify the failure modes of the System. How do these impact the missions of the systems developed earlier?

Question 4: Systems Engineering Management:
· Identify three risks to the project, assess their likelihood and consequence, discuss how these risks should be addressed.
· Develop a Systems Engineering Management Plan template suited to the system.

Scope:
This assignment will assess your understanding of the course topic presented over days 3 and 4.

Length and Presentation:
Nominally 3000 words, but the length of the assignment will be governed by the choice of subject matter and therefore can vary greatly.

Criteria by which your assessment will be marked:
All questions are considered of equal value and will be assessed on:
· Logic and flow of argument (logical linkages in the material presented);
· Ability to present relevant material clearly and succinctly;
· Application of key relevant theories and concepts; and
· Relevance to the topic.

Learning objectives with this assessment (refer to section 2.1): 1,5,7,8

All text based assignments must be submitted via MyUni.
Please refer to step by step instructions: http://www.adelaide.edu.au/myuni/tutorials/files/AssignmentStudentSubmission.pdf

There are a few points to note about the submission of assignments:

• Assignment Submission:  Assignments should not be emailed to the instructor; they must be lodged via the MyUni Course site (unless specified to do both). Note that assignments may be processed via TURNITIN, which is an online plagiarism prevention tool.
• Cover Sheet:  Please submit, separate to your assignment, the completed University of Adelaide Assessment Cover Sheet providing details of yourself and your team members (if applicable), your assignment, the course, date submitted, etc. as well as the declaration signed by you that this is your (your team’s) work.  Note that the declaration on any electronically submitted assignment will be deemed to have the same authority as a signed declaration.
• Backup Copy of Assignments:  You are advised to keep a copy of your assignments in case the submitted copy goes missing.  Please ensure that all assignment pages are numbered. If your assignment contains confidential information, you should discuss any concerns with the Course Lecturer prior to submission.
• Extensions of Time:  Any request for an extension of time for the submission of an assignment should be made well before the due date of the assignment to the Course Lecturer.  Normally, extensions will only be granted for a maximum of two weeks from the original assignment submission date.  Extensions will only be granted in cases of genuine extenuating circumstances and proof, such as a doctor’s certificate, may be required.
• Failure to submit: Failure to submit an assignment on time or by the agreed extension deadline may result in penalties and may incur a fail grade.  Note that a late penalty of 5% of the total available marks for that assessment item will be incurred each day an assignment is handed in late (Unless otherwise stated in section 5.2 or 5.3).  Assignments handed in after 14 days from the due submission date will fail even if a 100% mark is granted for the work.