LS-PRP-PRJ-02 (WPD)

8/6/2019 LS-PRP-PRJ-02 (WPD)

1/34

Q U T A v i o n i c s

4th year Avionics ProjectDoc No: LS-PRP-PRJ-02

Issue: 1.0

Page: 1 of 34

Date: 31 Mar 2011

Last updated by Daniel Ginn on 31 March 2011 Filename: 57506540.docx FileSize: 54331 bytes Template: Project Template.dotx

Landshark

Work Package Description

A Q U T A v i o n i c s P r o j e c t

Prepared by Date _______________Daniel Ginn, Landshark

Checked by Date _______________Damian Mew, Landshark

Approved by Date _______________Damian Mew, Student Manager 2011

Authorised for use by Date _______________Jason Ford, Project Coordinator

QUT AvionicsQueensland University of Technology

CRCSS-EESE, GPO Box 2434Gardens Point Campus

Brisbane, Australia, 4001.

Telephone (+61 7) 3138 2207Facsimile (+61 7) 3138 1516

Email [email protected]

This document is Copyright 2011 by the QUT. The content of this document, except that information which is in the

public domain, is the proprietary property of the QUT and shall not be disclosed or reproduced in part or in whole

other than for the purpose for which it has been prepared without the express permission of the QUT

8/6/2019 LS-PRP-PRJ-02 (WPD)

2/34



Issue: 1.0

Page: 2 of 34

Date: 31 Mar 2011


Revision Record

Document

Issue/Revision

Status

Description of Change Date Approved

1.0 Initial Issue 31 Mar 2011 Damian Mew

8/6/2019 LS-PRP-PRJ-02 (WPD)

3/34



Issue: 1.0

Page: 3 of 34

Date: 31 Mar 2011


Distribution List

Name Affiliation Distribution

Date

Approved

Jason Ford QUT Avionics 01 April 2011 Damian Mew

8/6/2019 LS-PRP-PRJ-02 (WPD)

4/34



Issue: 1.0

Page: 4 of 34

Date: 31 Mar 2011


Table of Contents

Paragraph Page No.

1 Introduction ................................ ................................ ................................ ........................ 81.1 Scope ................................ ................................ ................................ .......................... 81.2 Overview ................................ ................................ ................................ .................... 8

2 Reference Documents ............................... . ................................ ................................ ......... 92.1 QUT Avionics Documents ................................ ................................ .......................... 92.2 Non-QUT Documents ................................ ................................ ................................ . 9

3 Documentation Numbering Scheme ................................ ................................ .................. 104 Work Packet Descriptions (WPD)................................ ................................ ..................... 11

4.1 Conception (Pre-System Definition)................................ ................................ .......... 114.2 Creation (Architectural Design) ................................ ................................ ................ 174.3 Implementation ................................ ................................ ................................ ......... 234.4 Integration/Verification ................................ ................................ ............................. 29

8/6/2019 LS-PRP-PRJ-02 (WPD)

5/34



Issue: 1.0

Page: 5 of 34

Date: 31 Mar 2011


List of Figures

Figure Page No.

No table of figures entries found.

8/6/2019 LS-PRP-PRJ-02 (WPD)

6/34



Issue: 1.0

Page: 6 of 34

Date: 31 Mar 2011


List of Tables

Figure Page No.

Table 3-1 - Documentation Numbering Convention...................... Error! Bookmark not defined.

8/6/2019 LS-PRP-PRJ-02 (WPD)

7/34



Issue: 1.0

Page: 7 of 34

Date: 31 Mar 2011


Definitions

LS Landshark

DM Damian Mew

JL Joshua Lok

MU Mircea Ungureanu

DG Daniel Ginn

IR Infra-red

8/6/2019 LS-PRP-PRJ-02 (WPD)

8/34



Issue: 1.0

Page: 8 of 34

Date: 31 Mar 2011


1 Introduction

1.1 ScopeThis document describes in greater detail what each of the tasks in the timeline shown inthe

Project Management Plan document (RD/1) are.

1.2 OverviewLandshark is a Ground Vehicle that uses a thermal/IR sensor to detect a target. The sensor

contains a single sensing element and uses optical modulation to determine the direction to the

target. The Ground Vehicle is used to either: intercept a target moving; or dock with a statictarget at an operator specified angle. Ground Vehicle guidance to the target is autonomous and

generated onboard the Ground Vehicle. System operation is done via a remote operators

interface.

8/6/2019 LS-PRP-PRJ-02 (WPD)

9/34



Issue: 1.0

Page: 9 of 34

Date: 31 Mar 2011


2 Reference Documents2.1 QUT Avionics Documents1 LS-PRP-PRJ-01 (Project Management Plan)

2.2 Non-QUT Documents

In the following text, RD/x identifies referenced documents, where "x" denotes the actual

document.

8/6/2019 LS-PRP-PRJ-02 (WPD)

10/34



Issue: 1.0

Page: 10 of 34

Date: 31 Mar 2011


3 Documentation Numbering SchemeThe LS project employs a documentation-numbering scheme with the following basic format:

- - -

()

Valid Project Name

LS Landshark

Valid Project Functional Group (3 characters)

PRP Project Planning

REQ Requirements

DES Designs

TES Testing

OPM Operators Manual

Valid Document Type (3 characters)

PRJ Project Management Plan

PRM Project Risk Management

HSM Health and Safety Risk Management

CUR Customer RequirementsDER Derived Requirements

TST Trade Studies

CON Conceptual Design

PRE Preliminary Design

FIN Final Design

TSC Tests Cases

TSP Test Procedures

USR User Manual

MOM Meeting of Minutes

Sequence Number (2 digit sequential number)

Table 3-1 - Documentation Numbering Convention

8/6/2019 LS-PRP-PRJ-02 (WPD)

11/34



Issue: 1.0

Page: 11 of 34

Date: 31 Mar 2011


4 Work Packet Descriptions (WPD)4.1 Conception (Pre-System Definition)4.1.1 Define Customer RequirementsAIM:

To list what the customer wants from the project.

DESCRIPTION:

This task was done by Paul (the customer), so the responsibility for this was not placed on the

team.

DATE COMMENCED: N/A

DATE COMPLETED: 10/12/2010

MEMBER RESPONSIBLE: Paul

4.1.2 Generate Derived Requirements DocumentAIM:

To list limitations imposed on other subsystems or the project by sources other than the customer.

DESCRIPTION:

This Document will list requirements such as limitations imposed by one subsystem on another.

DATE COMMENCED: 10/01/2011


MEMBER RESPONSIBLE: Joshua Lok

8/6/2019 LS-PRP-PRJ-02 (WPD)

12/34



Issue: 1.0

Page: 12 of 34

Date: 31 Mar 2011


4.1.3 Generate Conceptual Design DocumentAIM:

To show the high level view of the Landshark system.

DESCRIPTION:

This document will be a basic outline to the project, defining the different subsystems.



MEMBER RESPONSIBLE: Damian Mew

4.1.4 Generate Health and Safety Risk Management DocumentAIM:

To list the potential health risks in the course of this project, and then to mitigate them

DESCRIPTION:

This document will be filled out in the QUT required format for a Health and Safety document.




8/6/2019 LS-PRP-PRJ-02 (WPD)

13/34



Issue: 1.0

Page: 13 of 34

Date: 31 Mar 2011


4.1.5 Generate Work Breakdown Structure DocumentAIM:

To identify the tasks throughout all the stages of the project and to present a timeline for the

completion of the project.

DESCRIPTION:

This task will be completed in Microsoft Project, and will show start and finish dates for each

task, as well as who is responsible.




4.1.6 Generate High Level Test Descriptions DocumentAIM:

To determine how each of the customer requirements will be tested.

DESCRIPTION:

This document will list all the test cases that are necessary to verify each customer requirement.

Each test case will list the method of the test, pass and fail cases, and a diagram if necessary.



MEMBER RESPONSIBLE: Daniel Ginn

8/6/2019 LS-PRP-PRJ-02 (WPD)

14/34



Issue: 1.0

Page: 14 of 34

Date: 31 Mar 2011


4.1.7 Generate Configuration Management DocumentAIM:

Explain how the project will handle documentation, and how the subsystems will be run to avoid

large integration problems when that stage arrives.

DESCRIPTION:

This document will explain the processes used in this project.




4.1.8 Generate Work Package Description DocumentAIM:

Gives a short description of the tasks listed in the Project Management Plan (RD/1).

DESCRIPTION:

The document lists an aim, description, start and finish date and the member responsible for each

task.




8/6/2019 LS-PRP-PRJ-02 (WPD)

15/34



Issue: 1.0

Page: 15 of 34

Date: 31 Mar 2011


4.1.9 Generate Project Risk Management DocumentAIM:

To list possible problems in the project, and the mitigate them.

DESCRIPTION:

This document will use the same table as the health and safety document.




4.1.10 Establish Project CostAIM:

Determine how much money is available for the project, and how much money is required for

each subsystem

DESCRIPTION:

This will involve chasing up the relevant university staff to determine how much money is

allocated to each student, as well as determining how much limitation must be placed upon

acceptable costs of individual parts investigated in trade studies.




8/6/2019 LS-PRP-PRJ-02 (WPD)

16/34



Issue: 1.0

Page: 16 of 34

Date: 31 Mar 2011


4.1.11 Concept ReviewAIM:

Pause and look back on what we have developed so far and make sure that we are making choices

that are requirement driven.

DESCRIPTION:

This will involve a review of each subsystem by the project manager as well as the entire team.



MEMBER RESPONSIBLE: Damian Mew, Whole team.

8/6/2019 LS-PRP-PRJ-02 (WPD)

17/34



Issue: 1.0

Page: 17 of 34

Date: 31 Mar 2011


4.2 Creation (Architectural Design)4.2.1 Perform Target Vehicle Trade StudyAIM:

Investigate suitable remote control vehicles to serve as the target vehicle.

DESCRIPTION:

This document will show various options and list the benefits and drawbacks of each option.




4.2.2 Perform Ground Vehicle Trade StudyAIM:

Investigate suitable remote control vehicles as a basis for the Ground Vehicle, or propose custom

designs that meet the requirements.

DESCRIPTION:





8/6/2019 LS-PRP-PRJ-02 (WPD)

18/34



Issue: 1.0

Page: 18 of 34

Date: 31 Mar 2011


4.2.3 Perform Target Seeker Sensor Trade StudyAIM:

Investigate various components that are required to create the IR seeker.

DESCRIPTION:




MEMBER RESPONSIBLE: Mircea Ungureanu

4.2.4 Perform Target Seeker SupportingElectronics Trade StudyAIM:

Investigate various components that are required to help the IR seeker to perform its function.

DESCRIPTION:





8/6/2019 LS-PRP-PRJ-02 (WPD)

19/34



Issue: 1.0

Page: 19 of 34

Date: 31 Mar 2011


4.2.5 Perform Target Seeker Design and Operation Methodology Trade StudyAIM:

Investigate how an IR seeker works and the various options for meeting the customer and derived

requirements.

DESCRIPTION:





4.2.6 Develop Ground Vehicle Interception Logic and MethodologyAIM:

Investigate methods of bearing only interception.

DESCRIPTION:

This will be a purely research orientated task.




8/6/2019 LS-PRP-PRJ-02 (WPD)

20/34



Issue: 1.0

Page: 20 of 34

Date: 31 Mar 2011


4.2.7 Generate Preliminary Design DocumentAIM:

Detail the proposed solution to the project

DESCRIPTION:

While this document is not a final design, it gives a good deal of detail as to what parts will be

used, and how each subsystem will proceed to meet the requirements.



MEMBER RESPONSIBLE: Whole team

4.2.8 Begin IR Source Detection Software DevelopmentAIM:

Begin the software code required to identify the bearing to the target.

DESCRIPTION:

This code will take the raw data from the IR sensor and convert it to a bearing measurement.




8/6/2019 LS-PRP-PRJ-02 (WPD)

21/34



Issue: 1.0

Page: 21 of 34

Date: 31 Mar 2011


4.2.9 Begin Controls Software Development and SimulationAIM:

Begin work on the Automation software code, in addition to creation of a simulator for the

project.

DESCRIPTION:

This code will be initially produced in MATLAB, and then later on converted to whatever

language is required by the logic board.




4.2.10 Health and Safety ApprovalAIM:

Have the Health and Safety document signed off by all relevant staff.

DESCRIPTION:

This document must be signed by the project supervisor, and the health and safety officer, as well

as his superior. No work can be commenced until this document has been approved.




8/6/2019 LS-PRP-PRJ-02 (WPD)

22/34



Issue: 1.0

Page: 22 of 34

Date: 31 Mar 2011


4.2.11 Preliminary Design ReviewAIM:

To stop and look back on how we have progressed in the project and whether this is the right

direction.

DESCRIPTION:

The proposed Preliminary Design must be reviewed by the Project Manager and the whole team.



MEMBER RESPONSIBLE: Damian Mew, Whole team

4.2.12 Begin Purchasing of Subsystem ComponentsAIM:

Confirm purchases and order them and have the cost reimbursed.

DESCRIPTION:

To purchase an item with university funds, the item must be approved by Jason Ford, then the

item is purchased with our own money, and then a reimbursement is obtained from the QUT staff.



MEMBER RESPONSIBLE: Whole team

8/6/2019 LS-PRP-PRJ-02 (WPD)

23/34



Issue: 1.0

Page: 23 of 34

Date: 31 Mar 2011


4.3 Implementation4.3.1 Prepare Target Vehicle Modification DrawingsAIM:

Recording of changes made to the Target Vehicle.

DESCRIPTION:

The customer has stipulated that a drawing of the system is better than a description, where

appropriate, therefore the modifications required to the Target Vehicle will be done up in a CAD

program.



MEMBER RESPONSIBLE: Joshua Lok, Daniel Ginn

4.3.2 Prepare Ground Vehicle Modification DrawingsAIM:

Recording the detailed construction and modification details made to the Ground Vehicle.

DESCRIPTION:

These detailed CAD drawings are always necessary for easy understanding of an object, and is

common industry practice.



MEMBER RESPONSIBLE: Damian Mew, Daniel Ginn

8/6/2019 LS-PRP-PRJ-02 (WPD)

24/34



Issue: 1.0

Page: 24 of 34

Date: 31 Mar 2011


4.3.3 Prepare IR Seeker Assembly DrawingsAIM:

Recording the design of the IR seeker, a point of great interest for the customer and supervisor of

the project.

DESCRIPTION:





MEMBER RESPONSIBLE: Mircea Ungureanu, Daniel Ginn

4.3.4 Prepare IR Seeker Assembly DrawingsAIM:

Recording the design of the IR seeker, a point of great interest for the customer and supervisor of

the project.

DESCRIPTION:






8/6/2019 LS-PRP-PRJ-02 (WPD)

25/34



Issue: 1.0

Page: 25 of 34

Date: 31 Mar 2011


4.3.5 Prepare Sonar Sensor Assembly DrawingsAIM:

Recording the design of the sonar assembly. Although of limited interest, this will show the sonar

system in its own subsystem.

DESCRIPTION:





MEMBER RESPONSIBLE: Joshua Lok, Daniel Ginn

4.3.6 Assemble/Modify Target VehicleAIM:

The modification of the target vehicle to the stage that full testing can be carried out with it.

DESCRIPTION:

All modifications outlined in the CAD drawings relating to this vehicle will be implemented.




8/6/2019 LS-PRP-PRJ-02 (WPD)

26/34



Issue: 1.0

Page: 26 of 34

Date: 31 Mar 2011


4.3.7 Assemble/Modify Ground VehicleAIM:

The construction of the Ground Vehicle in accordance with the proposedCAD drawings.

DESCRIPTION:

The Ground Vehicle will be constructed here so that it is ready to begin testing. As it is common

that things rarely go according to plan, whatever changes thatare made to the Ground Vehicle

should be reflected in the CAD drawings as well.




4.3.8 Assemble/Modify Target SeekerAIM:

Construct IR seeker.

DESCRIPTION:

This section of the project involves producing a finalised version of the IR system.



MEMBER RESPONSIBLE: Damian Mew, Mircea Ungureanu

8/6/2019 LS-PRP-PRJ-02 (WPD)

27/34



Issue: 1.0

Page: 27 of 34

Date: 31 Mar 2011


4.3.9 Install Sonar Sensor To Ground VehicleAIM:

Simple installation of Sonar Seeker to Ground Vehicle

DESCRIPTION:

Since this item is purchased off the shelf, little bench testing will be required, so it can be install

very early.



MEMBER RESPONSIBLE: Damian Mew, Joshua Lok

4.3.10 Prepare Environmental ControlEquipmentAIM:

To prepare the testing area for testing.

DESCRIPTION:

This task prepares all the necessary equipment to perform the tests in the High Level Test

Descriptions.




8/6/2019 LS-PRP-PRJ-02 (WPD)

28/34



Issue: 1.0

Page: 28 of 34

Date: 31 Mar 2011


4.3.11 Prepare Safety and Protective EquipmentAIM:

To ensure the safety of all in the vicinity of the project.

DESCRIPTION:

This is extremely important, to avoid injury to persons or equipment.




4.3.12 Dry Run Testing of Subsystems FunctionalityAIM:

Bench testing of components, to make sure they work to specifications.

DESCRIPTION:

This is the first true testing of the subsystems, to see if they actually do work, and what needs to

be done to make them work to specifications.



MEMBER RESPONSIBLE: Whole Team

8/6/2019 LS-PRP-PRJ-02 (WPD)

29/34



Issue: 1.0

Page: 29 of 34

Date: 31 Mar 2011


4.4 Integration/Verification4.4.1 Integrate All Subsystems Into OneAIM:

To make one whole system

DESCRIPTION:

This combining of subsystems which should all be individually working and within specifications,

will cause new problems and complexities, which must be overcome.




4.4.2 Update High Level Test DescriptionsAIM:

With the Tests now imminent, the detailed descriptions of how each test will be run must be

recorded.

DESCRIPTION:

This step leads the way to commencement of testing.




8/6/2019 LS-PRP-PRJ-02 (WPD)

30/34



Issue: 1.0

Page: 30 of 34

Date: 31 Mar 2011


4.4.3 Test LS System Against High Level Test DescriptionsAIM:

To compare the system with the full requirements of the project

DESCRIPTION:

These tests will show any short comings of the design, which will then be dealt with.




4.4.4 Create Test LogAIM:

To list all tests performed, and some basic information about each one.

DESCRIPTION:

This document is necessary to show recording and proof of work.




8/6/2019 LS-PRP-PRJ-02 (WPD)

31/34



Issue: 1.0

Page: 31 of 34

Date: 31 Mar 2011


4.4.5 Perform Design Modifications And ImprovementsAIM:

Make changes to bring the system up to compliance with the customer requirements

DESCRIPTION:

All changes that are made must be recorded in the CAD drawings.




4.4.6 Upgrade Software For ImprovementsAIM:

Make changes to software code to make the Ground Vehicle behave better.

DESCRIPTION:

Many tweaks will be possible once a good feel for how the system behaves as a whole has been

obtained. Flaws in the software can then be patched up.




8/6/2019 LS-PRP-PRJ-02 (WPD)

32/34



Issue: 1.0

Page: 32 of 34

Date: 31 Mar 2011


4.4.7 Generate Final Design DocumentAIM:

Produce the final designs of the Landshark Project

DESCRIPTION:

Once all the final changes have been made, the system as it now is will be show in full detail in

this document.



MEMBER RESPONSIBLE: Damian Mew, Joshua Lok

4.4.8 Perform Final Testing Against High Level Test DescriptionsAIM:

To ensure the whole system does work as required, and to avoid anyembarrassingly obvious

failures that should have been picked up in testing.

DESCRIPTION:

This will very much be a repeat of the previous tests, although all Test Cases must pass.




8/6/2019 LS-PRP-PRJ-02 (WPD)

33/34



Issue: 1.0

Page: 33 of 34

Date: 31 Mar 2011


4.4.9 Update Test LogsAIM:

Complete the Test Logs.

DESCRIPTION:

With the final private tests now complete, the Test Log can be wrapped up.




4.4.10 Perform Acceptance Test on LS SystemsAIM:

Present completed project to Project Supervisor.

DESCRIPTION:

Prove to Project Supervisor that the Landshark Project is now ready for presentation and delivery

to customer.



MEMBER RESPONSIBLE: Whole Team, Jason Ford

8/6/2019 LS-PRP-PRJ-02 (WPD)

34/34



Issue: 1.0

Page: 34 of 34

Date: 31 Mar 2011

4.4.11 Generate Operators ManualAIM:

Create document to make handover of the Landshark Project smooth to the customer.

DESCRIPTION:

This document will make the user intelligent to the proper use of the Landshark Project.


