ENGG4000 - Sem 1 2008 - St Lucia - Internal

Authenticated View
Printed: 21 February 2008, 12:40PM
This printed course profile is valid at the date and time specified above. The course profile may be subject to change during the semester – the online version is the authoritative version.

1. General Course Information

1.1 Course Details

Course Code: ENGG4000 Course Title: Introduction to Systems Engineering
Coordinating Unit: School of Information Technology and Electrical Engineering
Semester: Semester 1, 2008    Mode: Internal
Level: Undergraduate
Location: St Lucia
Number of Units: 2    Contact Hours Per Week: 2L2C
Pre-Requisites: CSSE3004 or CSSE3005 or CSSE3006 or ENGG3800 or MECH3100 or MECH3600 or METR3800
Incompatible: ENGG7000
Course Description: Systems engineering overview. System development life cycle; phases & reviews. Requirements analysis. Functional analysis. System architecture & design. Engineering management. Verification and validation. systems engineering tools. Industry standards. Trends in systems engineering.
Assumed Background: It is strongly recommended that students have taken ENGG3800 or have had other experience of working in teams. Familiarity with software engineering principles (eg CSSE 3002) is desirable but not essential.

1.2 Course Introduction

Have you ever wondered how highly complex systems get built?

The world is getting more and more interconnected, and the systems on which the world depends are becoming increasingly complex. Modern aircraft, for example, have computers throughout them, on everything from fly-by-wire flight control, to telemetry in the engines that continuously reports engine status to maintenance engineers on the ground. Modern ATM systems enable people to withdraw money from their home bank account even from the other side of the world. Such systems are complex, and are made up of – and interact with – many other systems.
Systems Engineering (SE) is the discipline of building highly sophisticated systems that work successfully. It is about the key creative processes that transform concepts into system designs, and the key technological and management processes that enable system development to proceed in an orderly, interdisciplinary fashion – maximising opportunities to meet customer needs while minimising risk.

This course is an introduction to SE. It explains key SE practices, including requirements analysis, functional analysis & system design, and verification & validation. It will give students first hand experience of application of SE techniques and tools in team projects. Students will learn principles that apply to all large systems, through the complete system lifecycle – from conception through to disposal – with particular attention to software-intensive systems and systems of systems. It will be illustrated with examples from a wide range of application domains including aerospace, transport, health, defence and emergency dispatch.

Enrolment numbers may be limited because of laboratory space limits.

1.3 Course Staff

Course Coordinator:  Peter Lindsay
Phone: (07) 3365-2005     Email: p.lindsay@uq.edu.au
Campus: St Lucia Room: 78-418
Consultation: 1-2pm Wednesdays


1.4 Timetable

Timetables are available on mySI-net.

Additional Timetable Information
This schedule is subject to change.

Week Number
Monday's Date
Lecture Topic
Prac Session
Assessment
1
25 Feb
Introduction
n/a
 
2
3 Mar
User requirements
Operational concept
 
3
10 Mar
System requirements
User requirements analysis
 
4
17 Mar
Functional analysis
System requirements analysis
Assig 1 (OCD)
Mid-semester break
5
31 Mar
System Requirements Reviews
System requirements briefing
  
6
7 Apr
System modelling
OCD briefing
  
7
14 Apr
System design
System functional analysis
Assig 2 (SRS) 
8
21 Apr
 
System architecture/ Interaction modelling
System requirements review briefing
  
9
28 April
System Analysis & System Integration
System design
Assig 3 (SRR)
10
5 May
N/A
N/A
 
11
12 May
Verification & validation
DOORS
 
12
19 May
Engineering management
CORE
Assig 4 (SDD)
13
26 May
Trends, summary & conclusions
MS Project
 
Revision period
2 June
N/A
 
 

 

2. Aims, Objectives & Graduate Attributes

2.1 Course Aims

This course will introduce students to Systems Engineering (SE).

2.2 Learning Objectives

After successfully completing this course you should be able to:

1  understand the system development lifecycle and key SE processes
2  be familiar with the role & responsibilities of System Engineers
3  know how to apply key SE practices including requirements analysis, functional analysis, system design and test design
4  have experience using CASE tools including DOORS and CORE
5  have experience working in a SE team, from both customer and developer perspectives
6  have experience with presentations and reviews, and with writing industry-style reports
7  have experience with design and architecture description languages
8  be familiar with key industry SE standards

2.3. Graduate Attributes

Successfully completing this course will contribute to the recognition of your attainment of the following UQ (Undergrad Pass) graduate attributes:

GRADUATE ATTRIBUTELEARNING OBJECTIVES
A. IN-DEPTH KNOWLEDGE OF THE FIELD OF STUDY
A1. A comprehensive and well-founded knowledge in the field of study.1, 3, 4, 7, 8
A4. An understanding of how other disciplines relate to the field of study. 
A5. An international perspective on the field of study. 
B. EFFECTIVE COMMUNICATION
B1. The ability to collect, analyse and organise information and ideas and to convey those ideas clearly and fluently, in both written and spoken forms.1, 3, 5
B2. The ability to interact effectively with others in order to work towards a common outcome.3, 5
B3. The ability to select and use the appropriate level, style and means of communication.5, 6
B4. The ability to engage effectively and appropriately with information and communication technologies.5
C. INDEPENDENCE AND CREATIVITY
C1. The ability to work and learn independently.3, 6
C3. The ability to generate ideas and adapt innovatively to changing environments.3, 6
C4. The ability to identify problems, create solutions, innovate and improve current practices.3, 6
D. CRITICAL JUDGEMENT
D1. The ability to define and analyse problems.1, 3
D2. The ability to apply critical reasoning to issues through independent thought and informed judgement.1, 3
D3. The ability to evaluate opinions, make decisions and to reflect critically on the justifications for decisions.1
E. ETHICAL AND SOCIAL UNDERSTANDING
E1. An understanding of social and civic responsibility.1, 2, 8
E2. An appreciation of the philosophical and social contexts of a discipline.1, 2, 8
E4. A knowledge and respect of ethics and ethical standards in relation to a major area of study.2, 8
E5. A knowledge of other cultures and times and an appreciation of cultural diversity.8

Successfully completing this course will contribute to the recognition of your attainment of the following Engineers Australia graduate attributes:

GRADUATE ATTRIBUTELEARNING OBJECTIVES
1. Ability to apply knowledge of basic science and engineering fundamentals1, 3, 4, 6, 7, 8
2. Ability to communicate effectively, not only with engineers, but also with the community at large1, 3, 6, 7
3. In-depth technical competence in at least one engineering discipline1, 3, 4, 7
4. Ability to undertake problem identification, formulation and solution1, 3, 4, 7
5. Ability to utilise a systems approach to design and operational performance1, 3, 4, 7
6. Ability to function effectively as an individual and in multi-disciplinary and multi-cultural teams, with the capacity to be a team leader or manager as well as an effective team member3, 5, 6
7. Understanding of the social, cultural, global and environmental responsibilities of the professional engineer, and for the need for sustainable development2, 5
8. Understanding of the principles of sustainable design and development2
9. Understanding of and commitment to professional and ethical responsibilities2, 6
10. Expectation and capacity to undertake life-long learning1

3. Learning Resources

3.2 Recommended Resources

Richard Stevens et al. Systems engineering: coping with complexity. Prentice Hall Europe, 1998. ISBN 0-13-095085-8 (PSE Library High Use TA168 .S97 1998)

  
 

E. Hull, K. Jackson & J. Dick. Requirements Engineering. Springer Verlag, 2002. ISBN: 1-85233-577-7. (PSE Library TA168 .H84 2002)

  
 
Benjamin S. Blanchard & Wolter J. Fabrycky. Systems engineering and analysis. Prentice Hall, 3rd ed 1998. (PSE Library TA168 .B58 1998)
 
 

Systems engineering fundamentals. Defense Acquisition University Press, 2001. (PSE Library UC263 .S96 2001)

 
 
Martin Fowler. UML distilled : a brief guide to the standard object modeling language. Addison Wesley, 2nd ed 2000. (PSE Library QA76.9.O35 F694 2000)
 
 
Benjamin S. Blanchard. System Engineering Management. John Wiley and Sons, New York, 1998. (PSE Library TA168 .B53 1998)
 
 
Andrew P. Sage & James E. Armstrong, Jr. Introduction to Systems Engineering. Wiley, 2000. ISBN: 0-471-02766-9. (PSE Library TA168 .S15 2000)
 
 
Andrew P. Sage & W.B. Rouse (eds) Handbook of Systems Engineering and Management. John Wiley & Sons, New York, 1999. (PSE Library Ref TA168 .H33 1999)
 
 

3.3 University Learning Resources

Access to required and recommended resources, plus past central exam papers, is available at the UQ Library website (http://library.uq.edu.au/search/r?SEARCH=ENGG4000).

The University offers a range of resources and services to support student learning. Details are available on the myServices website (https://student.my.uq.edu.au/).

3.4 School of Information Technology and Electrical Engineering Learning Resources

Students enrolled at St Lucia who wish to retain a hard copy of this profile can use the free print quota provided each semester to students enrolled in courses in the School of Information Technology & Electrical Engineering. For information on how to use this print quota, see the School Policy on Student Photocopying and Printing (St Lucia) (http://www.itee.uq.edu.au/about_ITEE/policies/copy-print.html). Students enrolled at the Ipswich campus will either be provided with a hard copy or given directions in class on how to obtain a free copy.

ITEE course websites can be found at http://www.itee.uq.edu.au/~COURSECODE. Many ITEE courses also have Usenet newsgroups, named uq.itee.COURSECODE. Instructions for accessing newsgroups are available at http://studenthelp.itee.uq.edu.au/faq/1stYearFAQ.html#accessnews.

3.5 Other Learning Resources & Information

Handouts will be made available on the course web site www.itee.uq.edu.au/~engg4000/.

4. Teaching & Learning Activities

4.1 Learning Activities

Date
Activity
Learning Objectives
25 Feb 08 00:00 - 26 May 08 00:00
 Lectures (Lecture): There is a two-hour lecture each week (with a comfort break): Monday 4-6pm in room 78-224.
1, 2, 3, 8
3 Mar 08 00:00 - 26 May 08 00:00
 PracsA (Practical): Prac session commencing in week 2: Monday 10-12 in room 78-208.
1, 2, 3, 4, 5, 6, 7, 8
5 Mar 08 00:00 - 28 May 08 00:00
 PracsB (Practical): Prac session commencing in week 2: Wednesday 10-12 in room 78-208.
1, 2, 3, 4, 5, 6, 7, 8

5. Assessment

5.1 Assessment Summary

This is a summary of the assessment in the course. For detailed information on each assessment, see 5.5 Assessment Detail below.

Assessment Task
Due Date
Weighting
Learning Objectives
Presentation
Assignment 5. Verbal presentation
defined in the prac session
10%
5, 6
Report
Assignment 1. OCD
25 Feb 08 17:00 - 20 Mar 08 17:00
10%
1, 2, 3, 5, 6, 8
Report
Assignment 2. SRS
21 Mar 08 17:00 - 18 Apr 08 17:00
15%
1, 2, 3, 5, 6, 8
Report
Assignment 3. SRR
4 Apr 08 17:00 - 2 May 08 17:00
5%
1, 2, 3, 6, 8
Report
Assignment 4. SDD
25 Apr 08 17:00 - 23 May 08 17:00
20%
1, 2, 3, 4, 5, 6, 7, 8
Exam - during Exam Period (Central)
Final Exam
Examination Period
40%
1, 2, 3, 5, 7, 8

5.2 Course Grading


Grade 1, Fail: Fails to demonstrate most or all of the basic requirements of the course:  0-19

Grade 2, Fail: Demonstrates clear deficiencies in understanding and applying fundamental concepts; communicates information or ideas in ways that are frequently incomplete or confusing and give little attention to the conventions of the discipline:  20-44

Grade 3, Fail: Demonstrates superficial or partial or faulty understanding of the fundamental concepts of the field of study and limited ability to apply these concepts; presents undeveloped or inappropriate or unsupported arguments; communicates information or ideas with lack of clarity and inconsistent adherence to the conventions of the discipline:  45-49

Grade 4, Pass: Demonstrates adequate understanding and application of the fundamental concepts of the field of study; develops routine arguments or decisions and provides acceptable justification; communicates information and ideas adequately in terms of the conventions of the discipline:  50-64

Grade 5, Credit: Demonstrates substantial understanding of fundamental concepts of the field of study and ability to apply these concepts in a variety of contexts; develops or adapts convincing arguments and provides coherent justification; communicates information and ideas clearly and fluently in terms of the conventions of the discipline:  65-74

Grade 6, Distinction: As for 5, with frequent evidence of originality in defining and analysing issues or problems and in creating solutions; uses a level, style and means of communication appropriate to the discipline and the audience:  75-84

Grade 7, High Distinction: As for 6, with consistent evidence of substantial originality and insight in identifying, generating and communicating competing arguments, perspectives or problem solving approaches; critically evaluates problems, their solutions and implications: 85-100 

Other Requirements & Comments :

Since all the assignment work is team-based, the exam is an important discriminator in determining the final mark. For this reason, students' marks will be capped as follows:

The final mark will be capped at 84% if they score less than 32 out of 40 on the exam.
The final mark will be capped at 74% if they score less than 28 out of 40 on the exam.
The final mark will be capped at 64% if they score less than 24 out of 40 on the exam.
The final mark will be capped at 49% if they score less than 20 out of 40 on the exam.


5.3 Late Submission

Due to the interlinked nature of the assignments, and the dependency relationship between the customer and developer teams, it is critical that the submission schedule is adhered to closely by all concerned. (This is very much the case in industry!)
A penalty of 20% of the maximum mark for a written assignment will be deducted for each day late (including Saturday and Sunday) unless an acceptable explanation is provided to the lecturer-in-charge. Where the assignment involves a verbal presentation, not making the verbal presentation at the scheduled time will result in a maximum of half marks for the whole assignment.
Requests for extensions will only be considered under exceptional circumstances, and only if submitted in writing in advance of the due date and accompanied by documentary evidence of extenuating circumstances (e.g. medical certificate). If the extension will affect the shadow team, it will need to be negotiated with them also.

5.4 Other Assessment Information

Assignments 1-5 are team, rather than individual, assignments. Teams of 2-3 students will be established in the Prac in week 2. The assignments will apply SE methods and tools to application projects, which will be described in class. Students will get experience from two different perspectives: customer and developer. Professional systems engineers often have to play both these roles, sometimes even on the same project (e.g. when subsystem or component development is outsourced).

Each team will tackle two application projects in parallel, carried right through the semester:

·        One of the application projects – called the Customer Application Project (CAP) – will be undertaken from the customer perspective.
·        The other application – the Developer Application Project (DAP) – will be undertaken from the developer perspective.

Teams will be paired, so that one team plays the customer role and the other team plays the developer role, working on a shared application project. The lecturer will also participate in the customer role for all the application projects. Customers will review developer’s work, and vice-versa. As happens in industry, reviews will include verbal presentations (in prac sessions), with questions and answers. The lecturer will assign the application projects to teams and determine the pairings of teams.
The sequence of assignments follows part of the typical systems development lifecycle, from development of operational concept, through requirements analysis to system design and allocation of requirements to system components. The criteria for each assignment and submission details will be supplied with the assignment specification.

This course will use criterion-referenced marking, meaning that students can determine their final grade from their component marks (without worrying about any “grading curves” being applied to normalise the collective results). At the discretion of the Lecturer, final grades may be scaled upwards but not downwards.

The mark for each team assignment will be allocated to team members weighted according to percentages agreed to collectively by the team at time of submission, up to a maximum of full marks for any particular assignment. These percentages are constrained to lie in the following ranges (min, mid, max) and sum to 100 (variations outside these ranges must be discussed with the Lecturer):


2 member teams:
35 – 50 – 65
3 member teams:
25 – 33 – 40

However, it is expected that each team member will contribute substantially to each team assignment.
Assessment criteria will be supplied with the assignment specification.

5.5 Assessment Detail

Assignment 5. Verbal presentation
Type: Presentation
Learning Objectives Assessed: 5, 6
Due Date:
         defined in the prac session
Weight: 10%
Task Description:
·        Assignment type: team
·        Deliverable: A short verbal presentation on one of the 3 team deliverables; the selection will be made by the lecturer in the Prac in week 3; each member will be expected to speak
·        Learning objectives: verbal communications

Criteria & Marking: Marking Criteria can be found on the course webpage www.itee.uq.edu.au/~engg4000/ together with detailed information on the assignment. 
Assignment 1. OCD
Type: Report
Learning Objectives Assessed: 1, 2, 3, 5, 6, 8
Due Date:
         25 Feb 08 17:00 - 20 Mar 08 17:00
Weight: 10%
Task Description:
·        Assignment type: team
·        Role: Customer
·        Deliverable: A written report – an Operational Concept Document (OCD) – for the Customer Application Project
·        Learning objectives: user requirements analysis, report writing

Criteria & Marking: Marking Criteria can be found on the course webpage www.itee.uq.edu.au/~engg4000/ together with detailed information on the assignment.
Submission: All written assignments will be submitted electronically via the School’s assignment submission web page: http://submit.itee.uq.edu.au/. Assignments 1-4 must each be accompanied by a coversheet – signed by all members of the team and deposited in the course’s submission box on Level 1 of the GPSouth building before the assignment deadline – declaring that the submission is the team’s original work and indicating how marks should be allocated within the team.
Assignment 2. SRS
Type: Report
Learning Objectives Assessed: 1, 2, 3, 5, 6, 8
Due Date:
         21 Mar 08 17:00 - 18 Apr 08 17:00
Weight: 15%
Task Description:
·        Assignment type: team
·        Role: Developer
·        Deliverable: A written report – a System Requirements Specification (SRS) – for the Developer Application Project, from the OCD supplied by the customer
·        Learning objectives: system requirements analysis, industry-style report writing

Criteria & Marking: Marking Criteria can be found on the course webpage www.itee.uq.edu.au/~engg4000/ together with detailed information on the assignment.
Submission: All written assignments will be submitted electronically via the School’s assignment submission web page: http://submit.itee.uq.edu.au/. Assignments 1-4 must each be accompanied by a coversheet – signed by all members of the team and deposited in the course’s submission box on Level 1 of the GPSouth building before the assignment deadline – declaring that the submission is the team’s original work and indicating how marks should be allocated within the team.


Assignment 3. SRR
Type: Report
Learning Objectives Assessed: 1, 2, 3, 6, 8
Due Date:
         4 Apr 08 17:00 - 2 May 08 17:00
Weight: 5%
Task Description:
·        Assignment type: team
·        Role: Customer
·        Deliverable: A written report – the System Requirements Review (SRR) – for an SRS that will be supplied by the customer
·        Learning objectives: system requirements review, industry-style report writing

Criteria & Marking: Marking Criteria can be found on the course webpage www.itee.uq.edu.au/~engg4000/ together with detailed information on the assignment.
Submission: All written assignments will be submitted electronically via the School’s assignment submission web page: http://submit.itee.uq.edu.au/. Assignments 1-4 must each be accompanied by a coversheet – signed by all members of the team and deposited in the course’s submission box on Level 1 of the GPSouth building before the assignment deadline – declaring that the submission is the team’s original work and indicating how marks should be allocated within the team.
Assignment 4. SDD
Type: Report
Learning Objectives Assessed: 1, 2, 3, 4, 5, 6, 7, 8
Due Date:
         25 Apr 08 17:00 - 23 May 08 17:00
Weight: 20%
Task Description:
·        Assignment type: team
·        Role: Developer
·        Deliverable: A written report – a System Design Document (SDD) – for the DAP, based on the SRS from Assignment 2 and customer review comments
·        Learning objectives: system functional analysis, system design, industry-style report writing, UML, Rational Rose, DOORS

Criteria & Marking: Marking Criteria can be found on the course webpage www.itee.uq.edu.au/~engg4000/ together with detailed information on the assignment.
Submission: All written assignments will be submitted electronically via the School’s assignment submission web page: http://submit.itee.uq.edu.au/. Assignments 1-4 must each be accompanied by a coversheet – signed by all members of the team and deposited in the course’s submission box on Level 1 of the GPSouth building before the assignment deadline – declaring that the submission is the team’s original work and indicating how marks should be allocated within the team.

Final Exam
Type: Exam - during Exam Period (Central)
Learning Objectives Assessed: 1, 2, 3, 5, 7, 8
Due Date:
         Examination Period
Weight: 40%
Perusal: 10 minutes
Duration: 120 minutes
Format: Short answer, Short essay, Problem solving
Task Description:

The final exam in this course is a "closed book" exam.


Criteria & Marking: See the course webpage www.itee.uq.edu.au/~engg4000/ for examples of previous exams; criteria and marking will be on the same basis again this year.

6. Policies & Guidelines

 
This section contains the details of and links to the most relevant policies and course guidelines. For further details on University Policies please visit myAdvisor and the University Handbook of Policies and Procedures.

6.1 Assessment Related Policies and Guidelines

University Policies & Guidelines

An overview of the University’s assessment-related policies can be found on myAdvisor (http://www.uq.edu.au/myadvisor/index.html?page=2910).

Academic Integrity
It is the University's task to encourage ethical scholarship and to inform students and staff about the institutional standards of academic behaviour expected of them in learning, teaching and research. Students have a responsibility to maintain the highest standards of academic integrity in their work. Students must not cheat in examinations or other forms of assessment and must ensure they do not plagiarise.

Plagiarism
The University has adopted the following definition of plagiarism:

Plagiarism is the act of misrepresenting as one's own original work the ideas, interpretations, words or creative works of another. These include published and unpublished documents, designs, music, sounds, images, photographs, computer codes and ideas gained through working in a group. These ideas, interpretations, words or works may be found in print and/or electronic media.

Students are encouraged to read the UQ Academic Integrity and Plagiarism policy (http://www.uq.edu.au/hupp/index.html?page=25128) which makes a comprehensive statement about the University's approach to plagiarism, including the approved use of plagiarism detection software, the consequences of plagiarism and the principles associated with preventing plagiarism.

Feedback on Assessment
Feedback is essential to effective learning and students can expect to receive appropriate and timely feedback on all assessment. For a detailed explanation of the feedback you are entitled to, you should consult the policy on Student Access to Feedback on Assessment. (http://www.uq.edu.au/hupp/index.html?page=25114&pid=25075)

As a student you have a responsibility to incorporate feedback into your learning; make use of the assessment criteria that you are given; be aware of the rules, policies and other documents related to assessment; and provide teachers with feedback on their assessment practices.

There are certain steps you can take if you feel your result does not reflect your performance. Please refer to the myAdvisor web site. (http://www.uq.edu.au/myadvisor/index.html?page=2953&pid=2910)

School of Information Technology and Electrical Engineering Assessment Guidelines

Misconduct

Further to the statement on academic integrity and plagiarism above, students are required to read and understand the ITEE policy on Student Misconduct (http://www.itee.uq.edu.au/about_ITEE/policies/student-misconduct.html).

Late Arrival or Non-attendance at Examinations

The policy and procedure for late arrival or non-attendance at centrally controlled examinations is set out in the University's Examinations policy (HUPP 3.30.5), sections 8 and 10.2.

The way in which late arrival at a School-controlled examination is dealt with will be at the discretion of the course coordinator, who may be guided by the policy for centrally controlled exams.

In the case that a student requests a special exam for a School-controlled exam, the request will be considered and, if allowed, the timing shall be determined by the course coordinator, in consultation with the School's Chief Examiner where necessary, and in accordance with HUPP 3.30.5. Unless otherwise indicated in the Course Profile, applications must be made in writing to the Head of School no later than one week after the exam. Late applications will not be accepted.
 
Examination Feedback
 
In addition to the advice above, students wishing to view examination answer scripts and/or question papers should consult with the School office (Room 217, General Purpose South Building [78], St Lucia; Room 218, Building 1, Ipswich) regarding arrangements. The ITEE policy on exam script viewing is available at http://study.itee.uq.edu.au/current_students/exam_script_viewing.html.

Supplementary Assessment

If you fail this course you may be eligible for supplementary assessment - see the general award rules and/or your program rules for details. You should note that even though you may be eligible for supplementary assessment under these rules, in some circumstances there may be no practical assessment that can be offered to allow you to meet the minimum passing requirements. These circumstances may include failure based on:
  • group or team based assessment;
  • attendance or class participation requirements;
  • laboratory-based assessment, where laboratories can't practically be made available after classes have finished;
  • project or thesis-based assessment, where a significant period of time would be required to undertake supplementary assessment;
  • progressive assessment, where subsequent assessment items build on earlier assessment items; or
  • multiple assessment items, where it is impractical to offer multiple supplementary assessment items.
If the course coordinator determines that there is no practical supplementary assessment that can be offered to allow you to improve your grade, then you will not be offered supplementary assessment and your grade will remain unchanged.

6.2 Other Policies and Guidelines

University Policies and Guidelines

Placement Courses
Students on a placement course – also known as a work placement, internship, industry study, industry experience, clinical practice, clinical placement, practical work, practicum, fieldwork, teaching practice – should refer to the University policy, Placement Courses (http://www.uq.edu.au/hupp/index.html?page=25120&pid=25075) for detailed information.
 
Working with Children
Students whose studies include a professional/work placement, internship, clinical practice, teaching practice or other similar activity which involves them in regular contact with children should refer to the University policy, Working with Children Check - "blue card" (http://www.uq.edu.au/hupp/index.html?page=25004&pid=24963) to find out how to apply for a ‘blue card’.
 
Students with a Disability
Any student with a disability who may require alternative academic arrangements, including assessment, in the course/program is encouraged to seek advice at the commencement of the semester from a Disability Adviser at Student Support Services. Refer to the University policy, Students with a Disability (Disability Action Plan) (http://www.uq.edu.au/hupp/index.html?page=25122&pid=25075) and to the policy on Special Arrangements for Examinations for Students with a Disability (http://www.uq.edu.au/hupp/index.html?page=25111&pid=25075

Where an adjustment is made to an accredited program, it is the responsibility of the relevant Faculty to liaise with professional and registration bodies regarding the acceptability of the change/s.  

Occupational Health and Safety
Undergraduate Students (http://www.uq.edu.au/hupp/index.html?page=25055&pid=25015) and Postgraduate Students (http://www.uq.edu.au/hupp/index.html?page=25057&pid=25015) should be familiar with the University policies on occupational health and safety in the laboratory.

Other School of Information Technology and Electrical Engineering Guidelines

Ethical Clearance
If your course involves assignment or project work involving human subjects or human-related materials, you must investigate the need for ethical clearance and obtain it when required. Information on ethical clearance can be found at http://www.uq.edu.au/research/orps/index.html?page=5064&pid=5256.

Learning Summary

 

Below is a table showing the relationship between the learning objectives for this course and the broader graduate attributes developed, the learning activities used to develop each objective and the assessment task used to assess each objective.

Learning Objectives

After successfully completing this course you should be able to:

1  understand the system development lifecycle and key SE processes
2  be familiar with the role & responsibilities of System Engineers
3  know how to apply key SE practices including requirements analysis, functional analysis, system design and test design
4  have experience using CASE tools including DOORS and CORE
5  have experience working in a SE team, from both customer and developer perspectives
6  have experience with presentations and reviews, and with writing industry-style reports
7  have experience with design and architecture description languages
8  be familiar with key industry SE standards


Assessment & Learning Activities

  Learning Objectives
  1 2 3 4 5 6 7 8
Learning Activities
Lectures (Lecture)
selected
selected
selected
        
selected
PracsA (Practical)
selected
selected
selected
selected
selected
selected
selected
selected
PracsB (Practical)
selected
selected
selected
selected
selected
selected
selected
selected
Assessment Tasks
Assignment 5. Verbal presentation        
selected
selected
    
Assignment 1. OCD
selected
selected
selected
  
selected
selected
  
selected
Assignment 2. SRS
selected
selected
selected
  
selected
selected
  
selected
Assignment 3. SRR
selected
selected
selected
    
selected
  
selected
Assignment 4. SDD
selected
selected
selected
selected
selected
selected
selected
selected
Final Exam
selected
selected
selected
  
selected
  
selected
selected

Graduate Attributes

Successfully completing this course will contribute to the recognition of your attainment of the following UQ (Undergrad Pass) graduate attributes:

  Learning Objectives
  1 2 3 4 5 6 7 8
Graduate Attributes
A IN-DEPTH KNOWLEDGE OF THE FIELD OF STUDY
A1. A comprehensive and well-founded knowledge in the field of study.
selected
  
selected
selected
    
selected
selected
A4. An understanding of how other disciplines relate to the field of study.                
A5. An international perspective on the field of study.                
B EFFECTIVE COMMUNICATION
B1. The ability to collect, analyse and organise information and ideas and to convey those ideas clearly and fluently, in both written and spoken forms.
selected
  
selected
  
selected
      
B2. The ability to interact effectively with others in order to work towards a common outcome.    
selected
  
selected