Deliverables Memorandum
Due Date:
April 13th, 2011
Delivery Date:
April 13th, 2011
Author:
Austin Boykin
Reviewers:
Name of Editor:
Signature of Editor:
Signature of Sponsor:
Signature of Advisor:
Email Approval
MEMORANDUM
TO:
Dr. Joseph A. Morgan
THROUGH:
Dr. Rainer Fink
FROM:
Austin Boykin
DATE:
April 13th, 2011
TOPIC:
Deliverables Memorandum
----------------------------------------------------------------------------------------------The purpose of this memo is to list and fully describe the deliverables that BRAC Engineering
Consulting will be presenting as part of the AHCU (Automated Home Control Unit). These
deliverables are items of value to the project’s stakeholders, Shane Dickson and Chris Conger, which
demonstrate our progress on our project.
Deliverables Responsibility
Table 1. Deliverable Responsibility
Deliverable
Functional Block Diagram
Alpha Schematic
Alpha PCB Layout
Hierarchy Chart
Software Function Description
Final Flow Chart
Test Plan
CDR
Source Code Rev. 1
Beta Schematic
Beta PCB Layout
Final Schematic
Final PCB Layout
Soure Code Final Rev.
Bill of Materials
Software/Hardware Documentation
Testing Results
User Manual/Video
Final Prototype Demonstration
contact@bracengr.com
Date of Completion
9/3/2011
9/8/2011
9/14/2011
9/19/2011
9/25/2011
9/29/2011
10/3/2011
10/12/2011
10/17/2011
10/18/2011
10/24/2011
10/30/2011
11/4/2011
11/12/2011
11/14/2011
11/23/2011
11/29/2011
12/7/2011
12/11/2011
1
Responsible Team Member
Brian Arterburn
Chet Dluhos
Chet Dluhos
Austin Boykin
Austin Boykin
Austin Boykin
Brian Arterburn
Ryan Armstrong
Austin Boykin
Chet Dluhos
Chet Dluhos
Chet Dluhos
Chet Dluhos
Austin Boykin
Ryan Armstrong
Brian Arterburn
Brian Arterburn
Ryan Armstrong
Ryan Armstrong
April 13th, 2011
Deliverables Timeline
Figure 1. Deliverables Timeline
contact@bracengr.com
2
April 13th, 2011
Deliverables Explanation
Functional Block Diagram
These block diagrams created in Microsoft Visio provide a low level representation of the new hardware
that we are designing for the AHCU project. The block diagrams show the integration of our hardware as
well as the components that we used to design our boards and how they are interconnected. The
functional block diagram that will be submitted will include all functional components of the AHCU
project. This deliverable will be turned in as a softcopy and hardcopy.
Alpha Schematic
This is our initial schematic created in National Instruments Multisim, which will be given to our
stakeholders to inform them of our initial schematic. These schematics show will show them the basic
layout of our hardware. This deliverable gives our stakeholders a chance to give input on our schematic,
and for use to make any further changes if necessary. This deliverable will be submitted as a softcopy in
PDF format.
Alpha PCB Layout
A revision of our initial PCB layout created in National Instruments Ulti-Board is given to our
stakeholders to show them the general design of our PCB. The Alpha PCB layout will reflect the initial
schematic. This deliverable will be submitted as a softcopy in PDF format.
Hierarchy Chart
A comprehensive diagram submitted which has all our system’s operations organized into steps and
paths. Each path describes the functionality component within our system. This will allow for our
stakeholders to give us input on the logic of this device. This deliverable will be submitted in the form of
a softcopy in PDF format.
Software Function Description
This deliverable will contain the description of each functional component of our software. This will
describe each major function on each individual component of the AHCU system. These components
are the Damper Control Module, Temperature Module, and the Master Control Unit. These function
descriptions will be submitted as an MS Word softcopy and PDF hardcopy.
contact@bracengr.com
3
April 13th, 2011
Final Flow Chart
A flow chart will be created for all functional components of the AHCU project. These charts created in
Microsoft Visio 2010 shows the logic behind our program. These charts provide a general flow of the
program using processes and connectors to explain each path. It will provide our stakeholders with a
general understanding of the processes used in our program. Our stakeholders can refer back to these
flow charts later when they receive our fully documented source code to assist them in the
understanding of the code and what each function does. This deliverable will be turned in as a softcopy
in PDF format and a hardcopy.
Test Plan
At BRAC we will construct our test plan after the second board iteration. The reason we are constructing
the test plan at this time is so that we know what functionality and particular components are necessary
to test. The test plan will have 3 sections: hardware, software, and overall functionality. Hardware will
test particular components on our PCB to make sure they comply with important specifications.
Software will test different functional parts of code. Lastly, our integrated test will fully examine all
aspects of the AHCU project to ensure that all functional requirements have been met. This deliverable
will be submitted as a hardcopy and softcopy.
CDR
The purpose of the Critical Design Review (CDR) is to update our stakeholders on the progress of our
project. It should inform them of how close we are to finishing the project, what problems we have
encountered, and what we have remaining. This presentation should give our stakeholder an idea of
whether or not we will complete our project on time and on budget. This deliverable will be submitted
as a softcopy and hardcopy.
Source Code Rev. 1 Completion
Our system’s last modified draft of code created. This code will give all the functionalities to all
components of the AHCU project. This will be commented code and will be submitted as a softcopy to
the stakeholders.
Beta Schematic
A revision of our initial schematics created in National Instruments Multisim is given to our stakeholders
to inform them of the changes that we have made to our schematics. These revised schematics show
the errors and changes that were made to the initial schematics. This deliverable gives our stakeholders
a chance to give input on our schematics, and allow them to request further changes if necessary. This
deliverable will be submitted as a softcopy PDF format.
contact@bracengr.com
4
April 13th, 2011
Beta PCB Layout
A revision of our initial PCB layout created in National Instruments Ulti-Board is given to our
stakeholders to show them the general overview and size of our PCB. The revised PCB layout will reflect
the changes that were made in the beta schematics. This deliverable will be submitted as a softcopy in
PDF format.
Final Schematic
A revision of our beta schematics created in National Instruments Multisim is given to our stakeholders
to inform them of the changes that we have made to our schematics. These revised schematics show
the final changes that were made to the initial schematics. This deliverable gives our stakeholders the
final chance to give input on our schematics, and allow them to request further changes if necessary.
This deliverable will be submitted as a softcopy format.
Final PCB Layout
A revision of our Beta PCB layout created in National Instruments Ulti-Board is given to our stakeholders
to show them the general overview and size of our PCB. The final PCB layout will reflect the changes that
were made in the beta schematics and our finished design. This deliverable will be submitted as a
softcopy in PDF format.
Source Code Final Rev. Completion
Our system’s final code created. This code will give all the functionalities of the AHCU project in its final
form. This will include each of the separate modules’ own code. These Modules include the Damper
Controller Module, Temperature Module, Master Control Unit. This will be commented code and will be
submitted as a softcopy to the stakeholders.
Bill of Materials
The bill of materials lists every single component that we are using to design our PCB’s. This deliverable
is created in a table format in Microsoft Excel that contains pertinent part information. The deliverable
provides the cost to make a single board and the cost to make a thousand boards. This gives our
stakeholders an idea of how much it will cost them if they were to put this product into production. For
the interest of our stakeholders and for future business opportunities, the pricing of each component
provided in our bill of materials will be the lowest price possible for each component. This deliverable
will be submitted as a softcopy and hardcopy.
contact@bracengr.com
5
April 13th, 2011
Software/Hardware Documentation
These documents present the explanation of software packages and hardware modules. They examine
the usage of software and hardware to control this system. This will describe, in depth, how both our
hardware and software function for each module. This deliverable will be in a formal format. This
deliverable will be submitted as a softcopy to all stakeholders.
Testing Results
Once all of the tests have been performed on the system, the results will be placed in a professionally
formatted document. This document will justify and explain the results of each test. A comparison
between the test results and the expected results will be made to see if the new components meet the
project requirement. The document will also contain a section title “Problems”, where all of the
problems encountered during the test phase will be noted. To make the test results easier to
understand, photos, charts, tables, and graphs will be used. Examples of these aids will include pictures
of the inputs and output signals of a board. This deliverable will be submitted as softcopy and hardcopy.
User Manual/Video
A comprehensive user manual will be printed and presented as a guide for our transceivers operation.
Also, a step by step video will be included to assist in the explanation of the operation of the system.
This will be submitted in softcopy and hardcopy.
Final Prototype Demonstration
This is the process of demonstrating our fully functional working prototype. The demonstration will take
approximately one hour in a location that is to be determined. After the demonstration, we will answer
a series of question or concerns that the audience or our stakeholders may have. With the success of
our demonstration we will hand our prototype over to our sponsor, Dr. Porter.
contact@bracengr.com
6
April 13th, 2011