PROJECT PLAN. SDMay06-08

(1)

PROJECT PLAN

SDMay06-08

Faculty Advisor Dr. Zhao Zhang Dr. Arun Somani Client National Instruments Project Members

Austin Kelling – Computer Engineering Gerald Ahn – Computer Engineering Carson Junginger – Computer Engineering Suwandi Chandra – Computer Engineering

REPORT DISCLAIMER NOTICE

DISCLAIMER: This document was developed as a part of the requirements of an electrical and computer engineering course at Iowa State University, Ames, Iowa. This document does not constitute a professional engineering design or a professional land surveying document. Although the information is intended to be accurate, the associated students, faculty, and Iowa State University make no claims, promises, or guarantees about the accuracy, completeness, quality, or adequacy of the information. The user of this document shall ensure that any such use does not violate any laws with regard to professional licensing and certification requirements. This use includes any work resulting from this student-prepared document that is required to be under the responsible charge of a licensed engineer or surveyor. This document is copyrighted by the students who produced this document and the associated faculty advisors. No part may be reproduced without the written permission of the senior design course coordinator.

(2)

1. Introductory Material

This section will cover the introduction to the project. It will include the sections abstract, acknowledgement, problem statement, problem solution, intended user, intended use, assumptions and limitations.

1.1 Abstract

In this project plan report one can expect all the initial plan of the entire project. It contains the problem faced as a result of this project. Also it determines the operating environment, the user, how it can be used, some limitation and assumptions and the expected end products. This project is very important because it will create a new and easy to implement centralized control system in the house or offices that can help the user control all the electronic devices that the user has.

1.2 Acknowledgement

In order to complete this whole project, a lot of help was received from Dr. Zhao Zhang and Dr. Arun Somani, who are project advisors for this group. Some contributions were made by the client, National Instruments, by providing the LabVIEW software, QBX, and other hardware. National Instruments has also given a lot of feedback and some ideas in order to prepare this project plan document.

(8)

1.3 Problem Statement and Solution

1.3.1 Problem Statement

What was found was there are a great amount of demands for the centralized control system in one’s home or office. The goal is to be able to control each kind of equipment in the room automatically when a Bluetooth device comes into or leaves range. This will be useful and marketable due to the increased usage of Bluetooth in society.

1.3.2 Problem Solution

The idea that was decided on was to create one centralized control system in one’s home or office. A QBX module with Bluetooth connectivity will be attached to certain devices in the home or office in order to control them. Also, a server program will be used on a computer in that home or office to tell the QBX what devices to control, and also to configure the QBX modules. In order to control these devices, the QBX will discover when a Bluetooth device comes into range, and then perform certain tasks depending on what the user has configured it to do. Devices that could be used to trigger the QBX are as follows: cell phones, PDAs, Laptops, etc. Figure 2 shows an example use of such a device. The different possibilities for this project are endless. The QBX could be used to turn on lights and set a desired central air conditioning temperature when the Bluetooth device comes into range, allowing a user returning home from work to have a lit up house, that is being cooled or heated to the desired temperature. When the user leaves for work in the morning, the QBX could detect the absence of the Bluetooth device and

turn down the amount of air conditioning to save electricity. A QBX could be attached to an alarm system so that whenever a user leaves the house, the QBX will automatically arm the system, in case the user had forgotten to, and alleviates the user from having to enter in long codes and rushing out of their house once the system is armed. There are many devices that could be used for this project and there are many marketable possibilities.

1.4 Operating Environment

The Operating Environment of this system is inside a

house or small office. This system is intended to be used by the owner of the house or office in order to have total control of the devices and electronic equipments in that room.

Figure 2: Home Control

(9)

1.5 Intended User and Intended Use

This section discusses the intended users and uses of this project.

1.5.1 Intended User

The expected users of this system are people that would like the simplicity of controlling or turning on all their devices in their house or office when they arrive or leave that location. It also utilizes devices that already have Bluetooth technology, which many people have with them all the time. The system will benefit any user wanting a sort of “smart” home or office.

1.5.2 Intended Use

The intended uses include but are not limited to controlling or turning on the following devices: televisions, stereo systems, computers, air conditioning systems, home or office security systems, and more. This system is not expected to be used in an extremely large house, due to the limitations of range associated Bluetooth technology.

1.6 Assumptions and Limitations

1.6.1 List of Assumptions

This section illustrates user assumptions and system assumptions 1.6.1.1 User Assumptions

Only one user can access one QBX box.

The end-user of this system is someone that owns a Bluetooth capable device and a computer.

1.6.1.2 System Assumptions

(10)

There will be one centralized application in the server in order to group all the electronic devices in that room and control them.

1.6.2 List of Limitations

The following are limitations identified with the project: The team will run with a finite budget

Limited time to successfully implement all the functionality from the QBX box in the system and fully utilized the capability of the QBX box.

The QBX is only a prototype so it is hard to make a decision about the price for our end product.

1.7 Expected End-Product and Other Deliverables

The objective of this project is to successfully create a new and centralized control system using Bluetooth technology, a computer server program, and one or more QBX modules. The system also expected to be compatible and easy to customize according to different electronic devices. It will also provide full control of the devices in one’s home.

The QBX module should be packaged in aesthetically pleasing packaging so that it will attract customers.

(11)

2. Proposed Approach and Statement of Work

The proposed approach and statement of work will detail the components and activities necessary to ensure a successful project.

2.1 Proposed Approach

This section will supply the details of the expected end product as well as the functional requirements, constraints considerations, technology considerations, technical approach considerations, testing requirements consideration, and so on.

2.1.1 Functional Requirements

The following illustrates the functional requirements of the expected end product.

The product shall control lists of predefined devices relating to a home/small office. The product shall communicate with operating devices or host computer via Bluetooth and Wi-Fi.

The product shall configure options of the various devices that communicate with QBX modules.

The product shall have defined preferences that each user can set for each QBX controlled device.

The product shall use a safe key for secure communication between QBX module and related devices

The product shall provide a list of functions to a Bluetooth supported devices that can communicate with QBX modules.

The product shall have sensors to determine different measures in the room such as temperature.

The product shall have a user friendly graphic interface on the host computer that controls each QBX module.

The product shall have cell phones with java writer that enables a communication with the QBX module.

2.1.2 Constraint Considerations

(12)

The distance between a QBX module and a QBX controlled device will be limited to a maximum of 60 feet.

The team should program the product with the LabVIEW software only. The extension boards of the QBX are limited and not all available. The QBX is not does not support voltages that are higher than 8VDC. The budget for the project is limited.

The user interface will be in English only.

2.1.3 Technology Considerations

This section defines and evaluates the different types of technology to be considered to be used for the project.

First, one hardware component from National Instruments is required for the team to include in this project.

The QBX Module

Second, the team will choose a suitable technology that communicates with the QBX. The following are the criteria for further evaluation.

The Bluetooth compatibility / connectability The size and weight of a device

Capability to run embedded software

2.1.4 Technical Approach Considerations

This section defines the methodologies that will be used in completing the project.

(13)

The following are the iterative steps:

1. Develop a project plan (goals, schedule, risk solutions) and use cases. 2. Learn more about the QBX module – its extension board.

3. Learn how to communicate between each device. 4. Implement and test the VIs for the QBX module. 5. Develop a demonstration.

6. Organize the resources of the project such as final report, poster, and web pages.

2.1.5 Testing Requirements Considerations

This section illustrates the testing needs to examine the functionalities of the end product. The followings are important factors that need to be tested:

The correct installation of LabVIEW

The communication between the host computer and the hub

The communication between the host computer and the QBX module The communication between the QBX module and the hub

The communication between the QBX and other devices via Bluetooth The VIs’ correct functionalities

(14)

2.1.6 Security Considerations

The security concern with this product is the communication between the QBX and other Bluetooth devices. Since Bluetooth is capable for easy connection, the team’s solution is to set a core safe key so that only permitted users can access the system.

2.1.7 Safety Considerations

The team is not working with high voltages or currents so that will not be too much of a concern. Although the safety consideration is minimal, the team shall be careful with any unexpected danger.

2.1.8 Intellectual property consideration

The QBX modules are the property of National Instruments. Therefore access to the QBX module is only acceptable with a permission of National Instruments.

2.1.9 Commercialization considerations

A commercial product is not going to be made from the expected end product. In fact, permission from the National Instruments is needed to make this product commercial. Perhaps high demands may persuade the National Instruments to make a commercial product out of the groups project.

2.1.10 Possible risks and risk management

The followings are possible risks of this project and its solutions.

2.1.10.1 Risk: The QBX module cannot communicate with the host computer. Management: If the team cannot create a communication between the

QBX module and the host computer, help will be requested from National Instruments.

2.1.10.2 Risk: The team is not familiar with using the LabVIEW software.

Management: To learn what the LabVIEW does and how it works, the

(15)

2.1.10.3 Risk: The team is not fully familiar with what the QBX module

capabilities are.

Management: The team shall ask the client for an updated version of

manuals of the QBX module.

2.1.10.4 Risk: There is a possible chance of the team does not complete the

project.

Management: The team shall meet with the advisors to talk about the

progress on the QBX module and write a weekly report to analyze the progress of each week.

2.1.10.5 Risk: A team member might drop the course because of his personal issue. Management: Each team member is to keep a lab notebook to keep

track of what he has done. The team shall have meetings outside of the class to understand what other members are doing on the project.

2.1.10.6 Risk: The team might break the QBX module or hub accidentally. Management: The team shall be very careful working with the QBX

module, but if some reason the QBX module or hub breaks, the team shall contact the National Instruments for repair or a new QBX module.

2.1.11 Project proposed milestones and evaluation criteria

Project success for the project will be based on the ability to meet project goals and milestones. The team’s ability to meet these goals will be evaluated on the following criteria. Each milestone will receive a score based on how well the team satisfied the criteria for that milestone. A rationale for the resultant scores is provided in Table 1 below.

Table 1: Milestone Importance Table

Number Milestone Importance

1 Project Definition High

2 Technology Selection and Usage Medium

3 Initial Product Design High

4 Initial Product Implementation High

5 Project Testing Critical

6 Project Documentation Medium

(16)

2.1.11.1 Milestone: Problem Definition

Description: For successful team project the team must have a clear

definition of the project. The team will define all the aspects of the project and have a clear understanding how the team will use the given technology to benefit the public.

Evaluated By: Client and faculty advisors

Evaluation Criteria: Evaluators will weigh the project definition with

their expectations for the scope of the project and assign a score from the table.

Importance: High

2.1.11.2 Milestone: Technology Selection and Usage

Description: A major part of the project will be finding the right

hardware to use. To do this, the team will get the laptops communicating with the QBX module. Then the team will determine the functionalities of the QBX and the additional expansions.

Evaluated By: Faculty advisors and team members

Evaluation Criteria: The ease of use is the biggest factor of the project.

The team will find hardware that easy to use with the LabVIEW interface.

Importance: Medium

2.1.11.3 Milestone: Initial Product Design

Description: This will include the theoretical design of the team’s

project demo including a description of how all the devices will communicate with the QBX module and how the hub will mediate communication with the QBX modules and the host computer.

Evaluated By: Team members and faculty advisors Importance: High

2.1.11.4 Milestone: Initial Product Implementation

Description: This design should be a complete demo of all intended

functionalities of the QBX module. This includes a server interface with the hub and the host computer. The team will have a demonstration of QBX modules controlling a theoretical home system.

(17)

2.1.11.5 Milestone: Project Testing

Description: This will include the exhaustive testing of all channels of

communication including the QBX to the hub, the hub to the host computer, the QBX to the controlled devices and etc. It will also include careful inspection of virtual instrument code and testing of all VIs. This milestone is essential to insuring the project demo is working consistently.

Evaluated By: Team members Importance: Critical

2.1.11.6 Milestone: Project Documentation

Description: This is compilations of many separate documents including

the project plans, project posters, web pages, and user manuals. All the sections of the documents would be edited for clarity and conciseness.

Evaluated By: Course instructor and faculty advisors Importance: Medium

2.1.11.7 Milestone: Project Demonstration

Description: This is where the team gets to show the project that they

have made. The team will make several demonstrations. The faculty advisors, National Instruments, and the industrial review panel will all get to view the final project. It will continue to be improved through the feed back of the people who the team presents.

Evaluated By: The faculty advisors, National Instruments, and the

industrial review panel.

Importance: High 2.1.12 Project tracking procedures

In order to make sure that the project done on time there are several tracking procedure that need to be considered:

• Use Microsoft Project in order to build a Gantt chart that help to track the project progress and make estimation for the whole project.

(18)

• The scheduled in Gantt chart will be made available online in order to make it easier to update when it is need to.

• There will be team meeting before the actual meeting with the faculty advisor in order to prepare and make sure that all the team member know what will be done next.

• The milestone and schedule will continually update as the project progresses. Project tracking will be a big part of the success of this project. In order to establish a timeline, a Gantt chart was created using Microsoft Project. The Gantt chart is a guideline for all deadlines and milestones. The team will continually update the chart as the project progresses to reflect what the team has or has not yet accomplished. The Gantt chart will be kept online and updated. The team will then use the updated charts to decide where to focus its efforts to make accomplishing the deadlines easier.

2.2 Statement of Work

This section will cover all of the work that the group will accomplish over the lifetime of the project. In it we will meticulously describe each of the eight tasks that the group will accomplish. In each task the objective, subtasks, and expected task results will be described. This section is a good review of each of the steps the group plans to take and what the expectations are from each.

Task 1: Definition of Project

In this task the group plans to fully define the project. This includes a full understanding of the hardware’s capabilities, and the software that relates. During this task the group will carefully study and refine the idea of the project and the inner workings of the QBX hardware.

Subtask 1a. Understand Capabilities of QBX

Task Objective: Understand all components of the QBX module. This includes

all prototyping boards, sensors, switches, and functionalities.

Task Approach: The team will read the manuals that came with the QBX

(19)

Expected Task Results: The group will understand the abilities of the QBX

modules and be more equipped to evaluate the possible uses.

Subtask 1b. Identify intended uses

Task Objective: Find out how to use the QBX module in order to create a

solution for a real world problem.

Task Approach: Take a closer look at the National Instruments documentation for

proposed QBX extensions and brainstorm other useful real world applications.

Expected Task Results: An idea for how to use a(n) QBX module(s) to solve a

real world problem that is unique, doable, and useful.

Subtask 1c. Explore possible extension modules

Task Objective: Find out what other prototyping boards and sensors exist for the

QBX module.

Task Approach: Review the two tutorials we have about extension modules for

the QBX, and inquire about other extension modules that are referred to in the QBX manual.

Expected Task Results: The newest hardware available for QBX, and possible

ideas for more uses of QBX.

Task 2: Technology Considerations

In this task our group will consider all the available technology relating to our project, and will determine the best way to utilize it. This will include researching current use of all Bluetooth technology and other problems that exist with it. It will also include researching the capabilities of LabVIEW software, and how it can be best utilized for our project.

Subtask 2a. Understand the QBX hardware

Task Objective: To understand the i/o related to QBX hardware. This includes

how to communicate with it and use all of its features.

Task Approach: Read the manuals from National Instruments, specifically

focusing on the hardware specifics and the tutorials on how to program the QBX

Expected Task Results: The whole group will understand the inner workings of

the QBX module, and will be able to troubleshoot as well as explain to others the functionality of QBX.

Subtask 2b. Determine possible detection devices

(20)

interfaces work the best for detection.

Task Approach: Research Bluetooth range limiting, and the motion detector

extension module for QBX; in order to find out what the best way to detect a person would be.

Expected Task Results: Knowledge of what kind of detection system to use for

project.

Subtask 2c. Determine possible controllable devices

Task Objective: Find out how to control devices by output from the QBX

modules, and to figure out what devices can be switched on and off in this manner.

Task Approach: The team will research possible power relay switching, as well

as other alternatives that would result in the desired functionality. Then it will be tested using a multimeter.

Expected Task Results: A good way to switch electronic devices on and off using

low voltage switching, and a list of controllable devices to control.

Task 3: Project Design

For this task our team will lay out the final design for all hardware and software that will be used. This will include detailed plans of what software will be written and what appliances will be controlled via the CBX module. It will also include a detailed plan of how the CBX module will detect Bluetooth devices.

Subtask 3a. Research and learn interfacing software (LabVIEW)

Task Objective: Learn how to use this powerful software tool to create virtual

instruments to control the I/O from the sensors on the QBX module.

Task Approach: Review information from LabVIEW tutorial on campus, and

practice making small applications that display sensor readings or gather data and write to a file. Then the group can extend those programs into more advanced applications that control devices.

Expected Task Results: All group members will become familiar with LabVIEW

software, and will be able to create simple VI’s to measure various sensors.

Subtask 3b. Communicate between QBX and dual layer network hub

Task Objective: Establish a system of communication between the QBX and hub.

(21)

Task Approach: Try to find the previous projects hub code and communication

scheduling scheme. Then research what would be the best way to communicate between the hub and several QBX modules.

Expected Task Results: A good understanding of Bluetooth one-to-one

communication and to be able to communicate efficiently with one hub and multiple QBX modules.

Subtask 3c. Communicate between QBX and controlled devices

Task Objective: Implementation of QBX switching on/off devices from the

controlled device list.

Task Approach: The team will use the information that it gathered when

researching device control to actually use the QBX to switch on and off these devices according to the schedule stated in section 3.

Expected Task Results: QBX modules will be able to use a primitive Virtual

Instrument (VI) to switch on and off a power strip or controllable devices.

Subtask 3d. Communicate between dual layer hub and host computer

Task Objective: Implementation of wi-fi communication scheme between the

hub and host computer.

Task Approach: Our team will research how to talk with the hub, most likely

using the Real Time LabVIEW module. The communication will transmit data received from the QBX to the host computer running a virtual instrument.

Expected Task Results: An efficient form of wi-fi communication between the

hub and the host computer.

Subtask 3e. Communicate between QBX and detected Bluetooth devices

Task Objective: Implement communication scheme for communicating between

QBX modules and detected Bluetooth devices.

Task Approach: Identify how to detect devices with QBX modues, and determine

how to schedule communication with these devices. Also determine how to detect what device is and how to communicate with it’s native API.

Expected Task Results: Efficient communication between QBX and any

(22)

Task 4: Prototype Implementation

For this task the group will construct a working version of the project design. This step will take many hours of writing code and figuring out exactly how to control devices. The better our team does in design the easier this task will be.

Subtask 4a. Implement LabVIEW VI’s

Task Objective: Create several virtual instruments that will display/coordinate

the desired I/O from the hub and QBX modules to the host computer.

Task Approach: Research what information needs to be monitored, and using the

groups knowledge of LabVIEW write VI’s to control this I/O.

Expected Task Results: A set of powerful customized VI’s that collect, display,

and offer control to the system the group will be implementing.

Subtask 4b. Implement communication system between QBX and network hub

Task Objective: write the code that will run the hub’s communication with the

QBX

Task Approach: Using the knowledge learned from subtask 3b, to write code that

will run on the hub or the host machine and will communicate with the QBX

Expected Task Results: A working communication system between the QBX and

the Bluetooth layer of the hub.

Subtask 4c. Implement communication system between QBX and controlled devices Task Objective: To effectively implement a system that controls selected

electronic devices.

Task Approach: Use the knowledge gained from subtask 3c to implement a

controlled environment between the QBX modules and a power strip that will trigger the switching of proposed controlled devices.

Expected Task Results: The communication system should switch a controlled

device when the QBX sends it a signal to turn on or off.

Subtask 4d. Implement communication system between hub and host computer

Task Objective: Write a small server application that will manage

communications between the hub and the host computer.

Task Approach: Use the assumed knowledge of TCP/IP and the RT module to

create a system that will send and receive data to and from the host computer.

Expected Task Results: An efficient way of communication between the hub and

the host computer.

(23)

Subtask 4e. Implement communication system between QBX and detected Bluetooth

devices

Task Objective: Write a program that is run on the QBX that detects nearby

Bluetooth devices and offers a list of customizable menu options.

Task Approach: The team will have to find a good way to detect what kind of

device has contacted the QBX module, and offer commands to that device in its native API.

Expected Task Results: Firmware on the QBX that will communicate with all

Bluetooth devices.

Task 5: Testing

This task is the longest and most tedious. In it the group will extensively test the prototype that they implemented. Inevitably the prototype will not work perfectly, and these tests are designed to find and correct any flaws. Each test will be developed, carried out, and then the changes, if any, will be implemented.

Subtask 5a. Create test cases to check VI’s correctness and functionality

Task Objective: To plan and develop a test that will check the VI’s correctness

and functionality.

Task Approach: The group will create a set of known inputs where the outputs

are also known, by observation the group will test if the output is correct or not.

Expected Task Results: A rigorous test for the VI’s correctness and functionality

will be created.

Subtask 5b. Test VI’s correctness and functionality

Task Objective: To test the VI’s correctness and functionality.

Task Approach: The team will execute the previously designed test. The team

will compare the expected output with the actual output. The group will also debug minor errors if they come up during testing.

Expected Task Results: The team will test the VI’s correctness and functionality.

If they pass the test the team will move on. If they don’t, the team will have to redesign and re-test.

Subtask 5c. Create test cases to check hub to QBX communication

Task Objective: To plan and develop a test that will check the hub to QBX

(24)

Expected Task Results: A rigorous test for the hub to QBX communication will

be created.

Subtask 5d. Test hub to host computer’s communication

Task Objective: To test the hub to host computer’s communication correctness

and functionality.

Task Approach: The team will execute the previously designed test. Our team

will compare the expected output with the actual output. It will also debug minor errors if they come up during testing.

Expected Task Results: The team will test the hub communication correctness

and functionality. If they pass the test the team will continue. If they don’t, our team will have to redesign and re-test.

Subtask 5e. Create test cases to test QBX and controlled device communication

Task Objective: To plan and develop a test that will check the QBX and

controlled device communication.

Expected Task Results: A rigorous test for the QBX device controlling will be

created.

Subtask 5f. Test QBX and controlled device communication

Task Objective: To test the QBX and controlled device communication.

Task Approach: The team will execute the previously designed test. The team

will compare the expected output with the actual output. It will then debug minor errors if they come up during testing.

Expected Task Results: The team will test the QBX device controlling

correctness and functionality. If they pass the test the team will continue. If they don’t, our team will have to redesign and re-test.

Subtask 5g. Create test cases to test communication between hub and host computer Task Objective: To plan and develop a test that will test communication between

hub and host computer.

(25)

Expected Task Results: A rigorous test for the hub to host computer

communication will be created.

Subtask 5h. Test communication between hub and host computer

Task Objective: To test the communication between hub and host computer. Task Approach: The team will execute the previously designed test. It will

compare the expected output with the actual output. It will also debug minor errors if they come up during testing.

Expected Task Results: The team will test the hub communication correctness

and functionality. If they pass the test the team will move on. If they don’t, our group will have to redesign and re-test.

Subtask 5i. Create test cases to test QBX and detected Bluetooth device

communication

Task Objective: To plan and develop a test that will test QBX and detected

Bluetooth device communication.

Expected Task Results: A rigorous test for QBX to Bluetooth device

communication will be created.

Subtask 5j. Test communication between the QBX module and detected Bluetooth

device communication.

Task Objective: To test the communication between the QBX module and

detected Bluetooth devices.

Task Approach: The team will execute the previously designed test. Then it will

compare the expected output with the actual output. It will also debug minor errors if they come up during testing.

Expected Task Results: The team will test the QBX to Bluetooth device

communication correctness and functionality. If they pass the test the team will continue. If they don’t, our team will have to redesign and re-test.

Task 6: Documentation

(26)

Subtask 6a. Create reference manual

Task Objective: To keep track of all tests and procedures used. To state why the

team is doing this project, and most importantly so others can continue the research our group started.

Task Approach: All records of experiments, ideas, and implementations will be

recorded in lab notebooks, or kept by the team leader. Our team will keep a constant compilation of these records and in the end make a reference manual.

Expected Task Results: A complete manual that explains all about the system we

have designed, what our group has done to test it, and how it works in general.

Subtask 6b. Create support document

Task Objective: To create a user-friendly manual on how to use the system our

team designed.

Task Approach: The team will have to organize all data on how to use the system

our team created, and keep the terms appropriate for the audience. This will tell the reader how to operate the system, as well as, constraint considerations and how to fix common problems.

Expected Task Results: Creation of a complete user-support document. Task 7: Demonstration

In this task the group will demonstrate the working and tested prototype. The demo will have to be constructed and gone over many times before presenting. Each time a demo is given, helpful feedback will be taken and changes will be made to the demo.

Subtask 7a. Plan demonstration

Task Objective: To plan the demonstration for faculty advisors, client, and

industrial review panel.

Task Approach: The team will need to develop a eye-catching presentation to

impress the judges at the international design competition. The system demo will need to work flawlessly and be able to be extensible to the real world. It will also need to be professional, and the correct amount of time.

Expected Task Results: An interesting presentation that presents both our

(27)

Subtask 7b. Faculty Advisor demonstration

Task Objective: To demonstrate the completeness of the project to the faculty

advisors of the project.

Task Approach: This will be the demonstration described above, but tailored to

the faculty advisors interests. This will also be a good place to get feedback from our advisors.

Expected Task Results: A successful demonstration with positive and negative

feedback to change the project demonstration.

Subtask 7c. Client (National Instruments) demonstration

Task Objective: To demonstrate the completeness and functionality of the project

to the client.

Task Approach: The demonstration will be the same as above, only tailored to

the needs and preferences of National Instruments and modified from advisor feedback.

Expected Task Results: The demonstration will exceed the clients expectations,

and will lead to marketability of the product.

Subtask 7d. Industrial Review Panel presentation

Task Objective: To demonstrate the completeness and functionality of the project

to the industrial review panel.

Task Approach: The demonstration will be tailored to the professionals in the

industrial review panel, and will demonstrate the projects completeness and marketability.

Expected Task Results: The team will gain valuable experience presenting in

front of professionals, and will receive feedback for future business presentations

Task 8: Project Reporting

This task will last for the life of the project. Weekly e-mails will be sent to faculty advisors, and client contacts in order to establish strong communication between everyone involved with the project. A project poster and final project report will also be composed stating the progress of the project and the success of the final product.

Subtask 8a. Weekly e-mail reporting

Task Objective: To inform the faculty advisors, client, and team members the

(28)

Task Approach: The member who is responsible of writing the weekly e-mail

receives the progress from other members and sends out an e-mail contains of the accomplishment of last week, goals for the next week, time and cost spent for the project and the current problems

Expected Task Results: Any personnel who is directly related to the project will

receive the weekly e-mail report.

Subtask 8b. Project poster development

Task Objective: To develop a poster that reflects the scopes, plan, summary,

estimated and actual time/cost spent on the project

Task Approach: The team will create a poster based on the outline from the

course package and add in visuals, graphs, charts, etc.

Expected Task Results: The poster should have summary of the project and be

informative, easy to read and understand for other students and anyone who is interested.

Subtask 8c. Final Project Report

Task Objective: To create a final report that summarizes the whole project

Task Approach: The team is to edit, summarize the existing documents and

merge them into a final document that has project information containing from the scope/vision of the project to the lesson learned and conclusion.

Expected Task Results: The final project report should contain the information of

(29)

3. Estimated Resources and Schedule

This section will describe the utilization of team resources and the schedule the team will follow. It will also give estimations of how long each task will take the team, and how much the project will cost, assuming fair minimum wage of $11.00 per hour.

3.1 Personal Effort Requirements

The amount of time spent on each task of the project has been estimated by the members of the team and put into a table. The estimates are rough and also try to account for unforeseen obstacles that will take up more time than expected. For each task and member of the group, a number of hours is listed as the expected amount of time to be spent working on that particular task. These columns and rows are also totaled, showing the total number of hours for each task, and each member.

(30)

Table 2: Personal Effort Estimation (hours) Pe rs on ne l Pr ob le m D ef in iti on Te ch no lo gy C on si de ra tio ns D es ig n Pr ot ot yp e Im pl em en ta tio n Te st in g D oc um en ta tio n D em on st ra tio n Pr oj ec t R ep or tin g To ta ls Carson Junginger 6 15 24 18 4 9 15 19 110 Austin Kelling 9 12 20 15 11 16 14 22 119 Gerald Ahn 10 13 22 16 10 17 15 24 127 Suwandi Chandra 6 10 24 21 3 5 13 16 98 Total 31 50 90 70 28 47 57 81 454

3.2. Other Resource Requirements

The cost for other resource requirements will be very low due to the fact that all of the needed hardware has been donated by National Instruments. The use of certain items for demonstration will also be assumed donated as they will not stay with the project. The table below shows the different resources that are expected to be used.

Table 3: Estimated Other Resources

Item Team Hours Other Hours Cost

Project Poster 14 2 $70.00

Television 0 0 Donated

Radio 0 0 Donated

Lamp 0 0 Donated

(31)

3.3 Financial Requirements

The cost for the project is shown in the following project. The totals for labor are assuming that all team members are being paid an hourly wage of 11.00 dollars per hour.

Table 4: Estimated Financial Costs

Item W/O Labor With Labor

Parts/Materials

Project Poster $70.00 $70.00

NI Microprocessors Donated Donated

NI two-layer hubs Donated Donated

Subtotal $70.00 $70.00 Labor ($11.00/hour) Carson Junginger $1,210.00 Austin Kelling $1,309.00 Gerald Ahn $1,397.00 Suwandi Chandra $1,078.00 Subtotal $4,994.00 Total $70.00 $5,064.00

3.4 Project Schedule

(32)

Figure 4: Gantt chart – part 1

(33)

4. Closure Materials

This section provides the client, faculty advisor and team member’s information and the closing summary.

4.1 Project Team Information

This section contains the contact information for everyone involved in this project.

4.1.1 Client Information

David Gardner National Instruments

Address: 1159 N. Mopac Expwy. Austin, TX 78759 Phone: 979-575-0300

Email: [email protected]

4.1.2 Faculty Advisor Information

Dr.Arun Somani

Office Address: 2211 Coover Hall Ames, IA 50011 Office Phone: 515-294-0042 Office Fax: 515-294-3637 Email: [email protected] Dr. Zhao Zhang

Office Address: 368 Durham Ames, IA 50011 Office Phone: 515-294-7940 Office Fax: 515-294-1152 Email: [email protected]

4.1.3 Student Team Information

Gerald Ahn

(34)

Address: 1415 Coconino Rd #208 Ames, IA 50014

Email: [email protected] Phone: 515-451-7101

Austin Kelling

Major: Computer Engineering

Address: 1273 Friley Dodds

Ames, IA 50012 Email: [email protected] Phone: 610-972-8074 Carson Junginger

Major: Computer Engineering Address: 225 N. Hyland Ave #12

Ames, IA 50014 Email: [email protected] Phone: 563-249-3459

Suwandi Chandra

Major: Computer Engineering Address: 2609 Aspen Rd #7

Ames, IA 50014 Email: [email protected] Phone: 515-441-6273

4.2 Closing Summary

(35)

4.3 References

[1] Ghercioiu, Marius. “The QBX, Getting Started Guide”. June, 2004. [2] Ghercioiu, Marius. “QBX Manual”. June, 2004