Embed Size (px)
Citation preview
Entrance Security System
Project PlanTeam: Dec07-07
Client: Senior DesignGregory Smith
[email protected] Town Engineering
515-294-1828
Faculty Advisor: Prof. Mani Mina
Team Members:Nahiyan Ali
Shrabantee ChatterjeeVaibhav Kumar
Alex WeigelTao Zeng
DISCLAIMER: This document was developed as a part of the requirements of an electrical and computer engineering course at Iowa Sate 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.
Submitted: 9th February 2007
2
Table of Contents
0.2 LIST OF TABLES................................................6
0.2 LIST OF TABLES......................................................................................................6
0.3 LIST OF SYMBOLS...................................................................................................7
0.3 LIST OF SYMBOLS...................................................................................................7
NONE0.4 LIST OF DEFINITIONS...................................................................................7
0.4 LIST OF DEFINITIONS..............................................................................................8
1. INTRODUCTORY MATERIAL..................................................................................9
1.1 Abstract....................................................................................................................................................................9
1.2 Acknowledgments...................................................................................................................................................9
1.3 Problem Statement..................................................................................................................................................9
1.4 Operating Environment.......................................................................................................................................10
1.5 Intended User(s) and Intended Use(s).................................................................................................................10
1.6 Assumptions and Limitations..............................................................................................................................11
1.7 Expected End Product and Other Deliverables.................................................................................................12
2 PROPOSED APPROACH AND STATEMENT OF WORK........................................12
This section will describe the proposed approach of the team and will extend into the statement of work. The subsections are listed below:......................................................................................................................................12
2.1 Proposed Approach..............................................................................................................................................12
This section would builds on the constraints the design team will face during the development of the system. The bullets below provide a description of each of the design constraints............................................................13
2.2 Statement of Work................................................................................................................................................18
3 ESTIMATED RESOURCES AND SCHEDULES........................................................27
3.1 Estimated Resource Requirement.......................................................................................................................27
3.2 Schedule.................................................................................................................................................................30
i
4. CLOSURE MATERIAL.............................................................................................31
4.1.1 Client Information.............................................................................................................................................31
4.1.2 Faculty Advisor..................................................................................................................................................32
4.1.3 Student Team Information...................................................................................................................................32
ii
0.1 List of Figures
Figure 1: Gantt chart of Expected Project Flow and Time Span.......................................22Figure 2 : Gantt chart of Schedule of Deliverables...........................................................23
iii
0.2 List of Tables
Table 1: Project Milestones and Overall Importance..........................................................9Table 2: Milestone Evaluation Criteria..............................................................................10Table 3: Personal Effort Requirement (hours)...................................................................20Table 4: Other Costs..........................................................................................................21Table 5: Product Cost Analysis.........................................................................................22
iv
0.3 List of Symbols
None
v
0.4 List of Definitions
Diode - A device, as a two-element electron tube or a semiconductor, through which current can pass freely in only one direction
EE - Electrical Engineering EE491 - First semester of Senior Design EE492 - Second semester of Senior Design Interface board - A device that enables communication between devices IR – Infrared LED - Light emitting diode RFID - Radio Frequency Identification SDK – Software Development Kit USB - Universal Serial Bus
vi
1 Introductory Material
This section will introduce the project including the following subsections:
1.1 Executive summary1.2 Acknowledgment1.3 Problem statement1.4 Operating environment1.5 Intended user(s) and use(s)1.6 Assumptions and limitations1.7 Expected end-product and other deliverables
1.1 Executive Summary
The Senior Design Lab of the Department of Electrical and Computer Engineering at Iowa State University has been suffering a multitude of security breaches. Theft, unauthorized entry, unauthorized use of equipment, and increasing concern about vandalism are the main issues of concern. Presently, a numeric combinational code is required to access the lab. This access code is provided to all senior design students to access and use the lab equipment. This security measure is susceptible because this code can be passed by students to other unauthorized people. Furthermore, students have been allowing people without authorization to access the lab by holding the door open for them. The team’s solution to this vulnerability is to implement RFID system to prevent unauthorized access. In addition, the team will use LED sensors to tackle the multiple access issue. Thus, the proposed solution will solve the security breaches.
1.2 Acknowledgments
The entrance security team would like to thank the senior design staff and faculty at Iowa State University for their assistance. The team would also like to thank Professor Mani Mina and Dr. Gregory Smith for the guidance they will provide through the design process.
1.3 Problem Statement
The Senior Design Lab of the Department of Electrical and Computer Engineering at Iowa State University is in need of new security measures. This section addresses the present security concern, and also proposes the team’s solution.
1.3.1 General problem statement
Building security has been a major concern and a difficult goal to accomplish. Keys to locks can be lost or stolen, while combinational locks can be broken or even revealed to unauthorized personnel. At present, the Senior Design Lab for Department of Electrical
1
and Computer Engineering at Town Engineering uses a numerical combinational code to access the lab. This code is provided to authorized EE 491/492 students; however, these codes can be passed to unauthorized personnel. The second issue with the present security system is that students already present in the lab can open doors or hold the door open for unauthorized personnel to enter. This breach in security in the past has resulted in lab equipment being stolen and mishandled. It is apparent that the Senior Design Lab needs a higher level of security, which proves the importance and need of this team project. Thus, the primary goals to accomplish in the project are to:
Allow access to authorized personnel only Prevent multiple entry issues
Any time the above requirements are not met, the security system should trigger an alarm, indicating that an unauthorized person has entered or is trying to access the lab. Furthermore the system should track the daily access of the lab by students and store it in a database. Therefore, if equipment is stolen or mishandled, the appropriate authority could identify who accessed the lab on a particular day.
1.3.2 General solution approach
Understanding the security issues faced by Iowa State University’s Senior Design Lab, the team proposes to use a Radio Frequency Identification System (RFID) as a primary solution. The team has proposed to buy a RFID kit which includes a compatible scanner and RFID tags. The kit further includes an interface board that can be programmed in C and Java for the required security features the team requires. The team believes that this approach will prevent unauthorized access to the lab as the security system will only provide access to people who have obtained the RFID tags. Furthermore, the RFID tags provide higher level security as the system can record who accessed the lab on a particular date. To resolve the issue of an unauthorized person being given access in the presence of an authorized person, the team proposes to use infrared sensors on the base of the door. The infrared will only deactivate for a small fraction of time when the RFID recognizes the tag. However, if the door is opened by a person present in the room, the infrared will still be active and will trigger an alarm as the person is not authenticated. This increases our security to level 2, as lab access is restricted to authorized personnel only and only one entry per card is permitted.
1.4 Operating Environment
The entrance security system will be installed in the Senior Design Lab in the Town Engineering building. The lab is used by Electrical and Computer Engineering students who are currently taking EE 491/492. The system will experience room temperatures ranging from 65°F to 75°F. The security system requires a power supply at all times. If there is a power outage, then the system will be limited to the combinational code. The Senior Design Lab is typically illuminated, and nearby objects will not interfere with the security system.
2
1.5 Intended User(s) and Intended Use(s)
This section defines the intended user(s) and use(s) for the project.
1.5.1 Intended user(s)
The system is designed for the Senior Design Lab in Town Engineering. Any student who is currently taking EE491/492, along with faculty and janitor, are expected to access the lab. The system is expected to be friendly and easily accessible to users, without any technical difficulties. Security personnel are also expected to use this system if an alarm is triggered due to a security breach. Furthermore, authorized users with special needs or disabilities need to be able to operate and access the system.
1.5.2 Intended use(s)
This system is specifically designed for the Senior Design Lab for the Department of Electrical and Computer Engineering in Town Engineering at Iowa State University. This prototype system is intended to improve the current security for the lab. It would prevent unauthorized entrance to the lab by triggering an alarm. At present, this system is specifically designed as per need of the Senior Design Lab, but it could be extended to other buildings and rooms as required.
1.6 Assumptions and Limitations
The system is designed to be user friendly and is expected to maintain the rigidness of a robust security system. The system is adaptive such that most of the assumptions and limitations are spawned from extreme circumstances.
1.6.1 Initial assumptions list
Below is a list of assumptions made for the project:
There is constant AC power available to the device and no power outage is expected. The RFID card is distributed to authorized personnel only. Tampering with the RFID scanner and LED sensors is not expected. The camera installed in the room is expected to handle students triggering the alarm
intentionally. The LED sensor has an unobstructed “line of sight” to the IR receiver. There is a suitable mounting place for the device in the Senior Design Lab.
1.6.2 Initial limitations list
Below is a list of limitations imposed on the team:
Range of RFID tag from the transmitter is only 4 inches
3
AC power outlets in lab are 120V, 60Hz The project has a budget constraint of $150 Number of inputs on the interface board is limited Number of team members is restricted to five The project must be completed by December 2007
1.7 Expected End Product and Other Deliverables
The final prototype and documentation will be composed of:
Mountable wall unit Power supply unit – Converts AC power from the source to DC power for the
position indicators Installation instructions and user manual – a pamphlet including instructions on how
to install and maintain the device Circuit diagram – basic power diagram for the installed system Logic and control software Computer input/output interface board Authorized RFID cards and compatible RFID scanner LED/IR sensor detection Design report Project poster Final report
The logic/control software will be installed on a computer (which has been provided) and will rely on the USB board to communicate with the RFID scanner unit. The USB board will also communicate with the LED/IR sensor outputs and convert them to digital signals which will be processed and handled using the software on the computer.
2 Proposed Approach and Statement of Work
This section will describe the proposed approach of the team and will extend into the statement of work. The subsections are listed below:
2.1 Proposed Approach2.2 Statement of Work
2.1 Proposed Approach
This section elaborates on the functional requirements, constraints, technology, technical approach, technical approach, testing requirements, security, safety, intellectual property, commercialization, possible risks and risk management, project proposed milestones and evaluation and project tracking considerations. In brief this section would expand on the approach towards completing the senior design project.
2.1.1 Functional requirements
4
The objective of this project is to secure the Senior Design Lab from unauthorized access, in an effort to reduce the mishandling of lab equipment and misuse of lab. Below are the broad categories of the functional requirements of the system:
Operational reliabilityo The system must run efficiently in the background without the need of being
attended daily.o The system must not fail at any time as the lab is not monitored.
Functional reliabilityo The system should allow all authorized students and personnel to access the lab.o The system should track and store all persons who access the lab on a certain day.o The system must trigger an alarm if any unauthorized personnel accesses or
attempts to enter the lab.o The system should not trigger a false alarm due to internal error.
Ease of useo The system must not be difficult to operate.
2.1.2 Constraints considerations
This section would builds on the constraints the design team will face during the development of the system. The bullets below provide a description of each of the design constraints.
Range of RFID The RFID scanner only has a range of 4 inches, thus the user is expected to swipe the card close enough to the scanner to gain access to the lab.
LED/IR disable timeAs soon as the RFID scanner recognizes the authorized person, he/she is expected to enter the lab within a small fraction of time (10 seconds) as the LED/IR beam would only be deactivated for that small time to prevent multiple entries.
Checking outThe users inside the lab are expected to also scan the RFID when leaving the lab. This is essential to prevent the alarm from triggering because the infrared will be still active.
Physical sizeThe system must be able to fit near/next to the Senior Design Lab.
Database sizeThe database storing the RFID information must be large enough to keep track of everyone involved with senior design.
5
AC powerA constant AC power of 120V, 60Hz is supplied to the system.
CostThe senior design budget only allows the team to spend $150 on the project.
2.1.3 Technology considerations
The areas of technology that are central to this project are Radio Frequency Identification System (RFID) and IR detection. The RFID system allows a secure method to authenticate authorized personnel. In addition, the IR detection provides the feasibility to prevent multiple access issues related to the security design. The design will also involve an interface board that will communicate between the RFID, IR detection system and the computer to ensure only authorized access is provided to the lab. The computer also is a central part of the design as it will hold the database of all authorized users and also the database of lab access. When the system is complete a suitable mountable solution will also be considered.
2.1.4 Technical approach considerations
This section would discuss our approach to the design of the project and steps involved in achieving a successful working prototype. The approach is divided into research and planning, acquisition, development and simulation, and testing.
Research and PlanningThe security system design must be conceptualized and laid down on paper to understand any logical glitches that might be involved. Further, in this stage it is necessary to research and select the components used to implement the system. The plan will then be finalized in the design document.
AcquisitionThe necessary components referenced in the design document must be purchased from the internet or electronic shops.
Development and SimulationThe development stage will require the team to integrate the RFID and the IR sensor system to the computer using the interface board. It will require system board integration of multiple analog inputs, and the interface board will convert them to digital signals which will be linked to the computer via USB. The next part will require the team to program the board, and build a database in a language that will be compatible with the board. Simulations of the logic will be performed during the programming stage.
6
TestingIn the last phase of the project, the team would perform exhaustive sets of real time testing to make sure the system is not prone to errors and performs as expected.
2.1.5 Testing requirements considerations
This section will elaborate on the different simulation environments in which the design will be tested and also explains the requirements for passing each tests.
Authorized access to the labThe major test consideration is that the system should only allow access to students and personnel who have the appropriate RFID access cards. All other unauthorized personnel access should trigger an alarm, an indication of security breach.
Prevent multiple access scenariosThe second test for the system is that any authorized person present inside the lab can not open the door for an unauthorized person. This will require the LED/IR beam to be active at all times and only deactivate when an authorized person enters or leaves the lab for a small fraction of time.
Logging of lab access in a databaseThe third test is that the security system keeps track of all students and authorized persons who accessed the lab in the last month in a database for future reference.
2.1.6 Security considerations
The end product will require an administrator to operate the security system in an emergency where as unauthorized access is attempted and the alarm rings. This administrator would need control over the complete database and system, thus this administrative password is expected to be confidential.
2.1.7 Safety considerations
During the testing of the device and its installation the team has to must ensure that everything is connected correctly, so that no one will be injured, ruin the circuit components, or damage the system. During the assembly of the final product, it is of utmost importance that it is carefully done as to avoid any failure and waste of money. The security system will not be a hazard for other people or other electrical devices.
2.1.8 Intellectual property considerations
Any intellectual property which develops as a result of this project will be the property of this senior design team and the client.
7
2.1.9 Commercialization considerations
This system should be easy to manufacture and install after the interface board is programmed correctly and the software used for the communication link has been verified to have no errors. The system should be very user friendly and thus an increasing use of the system should not be problematic. The circuit board should not be very sensitive to mechanical vibrations. It is also expected that the LED/IR will last a long time before burning out. Thus, the system could be commercialized for other security needs.
2.1.10 Possible risks and risk management
This section summarizes the elements that the design team has identified as personal and technical risks.
Learning the interface board capabilitiesIt is top priority that the design team understands the functionality of the interface board and its limitations. This board is the sole communication link between the RFID scanner, LED/IR sensor and the computer. Predicting issues related to the interface boards is critical at the beginning of the project.
Learning the programming language
All the members in the design team are Electrical Engineering majors and may require considerable time to become accustomed and comfortable with programming. The team will utilize programming language references to better understand the SDK.
Team member sickness or unavailabilityAs the project moves along, members becoming ill and unavailable may delay the teams progress. Keeping all the team members well informed of individual activities and writing proper documentation will reduce risk exposure.
Falling behind scheduleCarefully planning and adhering to the project schedule will reduce this risk. If the team does fall behind schedule, the team will meet Dr. Mani Mina to plan the next course of action.
The system board and components don’t work appropriatelyDuring the course of design, if the team realizes the functioning of specific components is not as expected, the team would re-think the issue with the faculty advisor and look for other alternative solutions
Professional responsibilitiesAll team members are working outside their normal academics. Work related projects and commitments might arise, detracting from or slowing the project progress. To avoid such conflicts the team members will adhere to the project schedule.
8
2.1.11 Project proposed milestones and evaluation criteria
In order to evaluate the success of the project, several milestones will be set. Below is the list of milestones that should be accomplished by the design team. Table 1 below will define the importance of each task. Table 2 shows:
Project design: The project needs to be well-defined so that the client clearly understands what product/solution they are acquiring from the team.
Technology consideration and selection: The team will need to research what technology needs to be used, in order to solve the client’s problem efficiently, and remain cost effective. The team will have to choose a technology that meets the design requirement.
End product design: When the specific technology is chosen, the team will begin to design the product. The team will make a complete design of the Entrance Security, along with schematics, and block diagrams.
End product implementation: Once the logic behind the design is correct, the team will move toward implementing the product.
End product testing: After implementation of the product, it will be tested, making sure power supply, circuitry, and codes are responding adequately and correctly according to the design logic.
End product documentation: The team will include an instructional manual and all documentation taken throughout the whole project.
Table 1: Project Milestones and Overall ImportanceMilestone Importance
Relative Percentage (%)
End-Product Problem Definition High 17
Technology Considerations High 17
End-Product Design High 17
End-Product Implementation High 18
End-Product Testing High 18
End-Product Documentation Medium 10
End-Product Demonstration Low 3
Total 100
9
Table 2: Milestone Evaluation CriteriaEvaluation Result Numerical Score
Met/Exceeded Standard 92%
Partially Met Standard 50 - 89%
Did not Meet Standard < 50%
The team will evaluate each milestone as completed, marginally completed, or incomplete at all. Grades will be tabulated and a score of 92/100 will be considered as passing.
2.1.12 Project tracking procedures
In order for the project to run smoothly it is important that the project tracking methods are implemented. Below is the list of several tracking measures:
Weekly e-mailWeekly e-mail will be sent by the communications coordinator to all design team members and the faculty advisor to keep track of goals accomplished in the past week and report is expected in the upcoming week.
Tracking and modifying scheduleThe proposed schedule of events will be kept track of, and if the design team falls behind, the schedule will be modified to get closer to the original schedule.
Budget sheetThe budget sheet will be used to track the amount of money that is spent. Accurate records will be kept about expenditures and remaining funds.
2.2 Statement of Work
The Entrance Security System will be a working prototype, integrating both hardware and software. This section will define the problem definition, technology considerations and selection, end-project design, end-product prototype implementation, end product testing, end product documentation, end product demonstration, and project reporting.
2.2.1 Task 1: Problem Definition
Task Objective: The project needs to be clearly defined so that the team will fully understand what to do for the client.
Task Approach: Clearly state the requirements, specifications, and limitations.
10
Task Expected Results: The team will have a good understanding of the project.
2.2.1.1 Subtask 1a Problem Definition Completion:
Task Objective: Clearly define the statement of the problem, the requirements of the project, and specifications made by the client.
Task Approach: The team will read all the included literature pertaining to the project and consult the project scope with the client. Some important issues will be addressed such as available resources, operating conditions, and technical supports.
Task Expected Result: The team will fully understand the scope and the requirements of the project.2.2.1.2 Subtask 1b End-User(s) and End-Use(s) Identification
Task Objective: Identify the users and the uses of the product
Task Approach: The team will hold a meeting with the client and specify the purposes of the project. Also, the users of the system will be identified during the meeting.
Task Expected Result: All the users and uses for the project will be clearly identified at this point.
2.2.1.3 Subtask 1c Constraint Identification
Task Objective: Clearly define all the operating assumptions and limitations that may impede the product development.
Task Approach: A meeting will be organized among all team members for the discussion of any possible constraints for the design.
Task Expected Result: Any possible constraints that will affect the design will be clearly identified.
2.2.2 Task 2: Technology Considerations and Selection
Task Objective: Develop the most effective and economical solution among the available technologies for the project.
Task Approach: Each team member will be assigned a topic on the possible available technology that can be implemented. Research will then be collected. All the topics will be discussed during the team meeting.
Task Expected Result: The most effective and economical solution will be selected.
11
2.2.2.1 Subtask 2a Identification of Possible Technologies
Task Objective: List all potential technologies that can be implemented to the project, and determine what technologies have already been supplied to the clients.
Task Approach: Research the identified applicable technologies for the project, and set up a meeting with clients to discuss what technology is already available for the team.
Task Expected Result: List all the possible technologies and know the strengths and weaknesses of each.
2.2.2.2 Subtask 2b Identification of Selection Criteria
Task Objective: Develop criteria to compare the traits of all the possible technologies.
Task Approach: Discuss the constraint criteria for each technology and analyze its impact on the project design.
Task Expected Result: Be able to evaluate each possible technology on a standard scale.
2.2.2.3 Subtask 2c Technology Research
Task Objective: Research the capabilities of the available techniques.
Task Approach: Conduct extensive research on each possible technology from the list to see which technology is the most suitable for the project.
Task Expected Result: Have a better understanding for each possible technology for the project.
2.2.2.4 Subtask 2d Technology Selection
Task Objective: To determine which technology is the most effective and economical for the project.
Task Approach: From subtasks 2a, 2b, and 2c, the team will analyze the strength and weakness for each technology.
Task Expected Result: The most efficient and most cost effective technology will be chosen for implementation.
2.2.3 Task 3: End-Project Design
12
Task Objective: Implement the best solution from Task 2 for the project.
Task Approach: The project design will follow the best solution the team discovers from research. The parts that are not supplied by the client will be purchased. Modifications may be made in accordance with the process of the design. During the process, such design modifications and respective explanations will be documented.
Task Expected Result: Final design will meet the client’s expected requirements.
2.2.3.1 Subtask 3a Identification of Design Requirements
Task Objective: Clearly define all the specifications and requirements indicated by the clients.
Task Approach: Meet with the client to ensure that all design requirements have been addressed. Develop a comprehensive list of requirements and specifications based on the research that has been done.
Task Expected Result: All the requirements and specifications will be considered before the project design begins.
2.2.3.2 Subtask 3b Design Process
Task Objective: Develop a flowchart of the system and design a circuit level schematic for the product.
Task Approach: The team will break down the design into five parts. Each team member will be responsible for one part, which includes circuit design, implementations, and design testing. At the end, all the parts will be gathered and implemented into the final product design. Modifications may be added during the process of the design.
Task Expected Result: The final product design will be successfully completed by the team.
2.2.3.3 Subtask 3c Documentation of Design
Task Objective: Document the specifications of the design, results of design testing, and instructions for the product.
Task Approach: Each team member will record the design plans, testing results, and specifications of design for each individual part. A final documentation will be written on the record paper provided by each group member.
13
Task Expected Result: Comprehensive documentation of the product design will be delivered to the client.
2.2.4 Task 4: End-Product Prototype Implementation Task Objective: Build a prototype from the product design.
Task Approach: The team will implement the design and test if the product design has met the requirements and specifications.
Task Expected Result: The prototype implementation will be successful and meet all the requirements and specifications that the client has requested.
2.2.4.1 Subtask 4a Identification of Prototype Limitations and Substitutions
Task Objective: Define the operating restrictions of the design.
Task Approach: The team will implement the product design in the form of a prototype and test it in the Senior Design Lab. Test results will be recorded for the team to analyze any identified limitations.
Task Expected Result: Obtain a table of limitations that will be used for the final product documentation.
2.2.4.2 Subtask 4b Implementation of Prototype End Product
Task Objective: Conduct more extensive tests on the prototype to see if the product design has met all the requirements and specifications that are listed in the project plan.
Task Approach: Test the prototype in different operating environments and conditions to see if there are any failures in the product. Every test will be recorded and analyzed. The failure results will be contributed to the limitations of the product, or provide a basis for possible modifications.
Task Expected Result: The product prototype will properly function and meet all the requirements and specifications.
2.2.5 Task 5 – End Product Testing
Task Objective: The team will test the working prototype and make sure that theproduct meets all specifications defined in the project plan.
Task Approach: The product will be tested under several conditions at various levels, such as elapsed time of entry per person, temperature, and vibration. Testing will include documentation of all experiments.
14
Task Expected Results: The test will be used to make adjustments to the prototype.
2.2.5.1 Subtask 5a – Test Planning
Task Objective: Create tests for all functions of the prototype.
Task Approach: Tests will be designed to analyze the functionality of the system. The team will design and test scenarios that could activate the alarm.
Task Expected Results: The team will have a well-defined test plan for the prototype system.
2.2.5.2 Subtask 5b – Actual Testing
Task Objective: To implement all the tests created by the team
Task Approach: The team will conduct all the tests and document the results. Testing will take place in the Senior Design Lab.
Expected Results: The team will keep a data log where all of the tests will be documented and the notes recorded.
2.2.5.3 Subtask 5c – Test Results Evaluation
Task Objective: The team will analyze the test results and make sure that the prototype system operates within the client’s specifications.
Task Approach: Results will be summarized and represented to show expected versus actual outcomes. The team will be looking for areas that indicate specifications not met for the client.
Task Expected Results: Using data from tests, the team will make necessary modifications to the system to improve aspects that may not meet specification.
2.2.5.4 Subtask 5d – Testing Documentation
Task Objective: All testing will be documented for future reference.
Task Approach: The team will write the testing procedure in a log. Documentation will include the specific test procedure, test conditions, test scenarios, observations, results, and any problems that may arise.
Task Expected Results: This document will include all necessary details of the testing period.
15
2.2.6 Task 6 – End Product Documentation
Task Objective: The team will use thoroughly documented work to create instructions for the end-user to continually receive full functionality of the product.
Task Approach: The team will document intended uses, proper care, and clear instruction of use for the product.
Task Expected Results: The team will produce a document intended for the end user.
2.2.6.1 Subtask 6a – Development of End-User Documentation
Task Objective: Develop documents describing the end-product and what the functions are.
Task Approach: The team will describe the functionality, limitations, and proper use of the system. This documentation will also include troubleshooting advice, device capabilities, and an instruction manual for using the product.
Task Expected Results: The team will have documentation explaining the functions and limitations of the end-product.
2.2.6.2 Subtask 6b – Development of End-User Instruction Manual
Task Objective: The team will write a manual for the end product for the client as an instructional guide to use of the system.
Task Approach: The team will write the manual from a new user’s point of view. The instruction manual will include a step-by-step guide for installing the system and providing additional information for its continuing operation. The instructions will be written for an audience with no engineering background.
Task Expected Results: The team will produce a clear and succinct instruction manual for the end-product.
2.2.7 Task 7 – End Product Demonstration
Task Objective: Demonstration of the working prototype and its functions.
Task Approach: The team will present the prototype and display its functions to the client and an industrial review board.
Task Expected Results: The team will demonstrate the working prototype and authenticate that it meets the client’s specifications.
16
2.2.7.1 Subtask 7a – Demonstration Planning
Task Objective: Organize, plan, and arrange for the product demonstration.
Task Approach: The team will create a PowerPoint presentation containing the features of the system, technical design, functionality of the system, financial cost of the entire system, troubleshooting, and limitations.
Task Expected Results: The team will have a rehearsed demonstration ready for presentation.
2.2.7.2 Subtask 7b – Faculty Advisor Demonstration
Task Objective: Demonstrate the prototype system to the faculty advisor.
Task Approach: The team will demonstrate the functions of the system for the faculty advisor. The demonstration will include features of the devices, the limitations, and show that the device meets requirements.
Task Expected Results: To have a successful demonstration of the prototype system for the faculty advisor.
2.2.7.3 Subtask 7c – Client Demonstration
Task Objective: Demonstrate the prototype system to the client.
Task Approach: The team will demonstrate the function and operation of the system for the client. The demonstration will include features of the devices, the limitations, and show that the device meets requirements.
Task Expected Results: To have a successful demonstration of the prototype system for the client.
2.2.7.4 Subtask 7d – Industrial Review Panel Demonstration
Task Objective: Demonstrate the prototype system to the review panel.
Task Approach: The team will demonstrate the function and operation of the system for the panel. The demonstration will include features of the devices, the limitations, and show that the device meets requirements. This will also include a presentation of the technical design and the specific technologies used to solve the problem.
Task Expected Results: To have a successful demonstration of the prototype system for the Industrial Review Panel.
17
2.2.8 Task 8 - Project Reporting
Task Objective: Communicate the advancements and outcome of the complete project.
Task Approach: Document the project from planning to presentation. The reports will be sent to the client to notify them of advancement and problems encountered.
Task Expected Results: To have a documented project which clearly explains and informs the client about the progress.
2.2.8.1 Subtask 8a – Project Plan
Task Objective: The team will produce a plan that will cover the entire process of the project.
Task Approach: The team will follow the project plan as a guide for the project. The plan will clearly outline the entire project description which will include a problem statement, design requirement, design constraints, documentation requirements, tasks, schedules, and budget.
Task Expected Results: This document will clearly outline the team’s proposed plan for the entire project.
2.2.8.2 Subtask 8b – Project Poster
Task Objective: To give a brief description of the project to the public.
Task Approach: The team will design a poster board which will outline the project. The purpose of the poster is to inform the public about the project clearly by using pictures to explain on a theoretical level.
Task Expected Results: To have a visual description that outlines the project clearly.
2.2.8.3 Subtask 8c – End Product Design Report Documentation
Task Objective: To have a document that reports all aspects of the design and the results of each.
Task Approach: The team will document the design process which will include block diagrams, schematic, component datasheet, and the purpose of each design in the system.
Task Expected Results: The team will have a thorough explanation of the design prototype.
18
2.2.8.4 Subtask 8d – Project Final Report Documentation
Task Objective: To present a complete flow of the development of the product, from the early ideas to the finished prototype.
Task Approach: The team will combine all the previous documentation and develop a comprehensive report. This report will include all parts of the project, starting with the problem statement and finishing with the final product documentation. Specifically, this report will include design requirements, design tasks, final design, user documents, documentation of tests performed, and team member logs.
Task Expected Results: To have a document detailing the entire project.
2.2.8.5 Subtask 8e – Weekly E-mail Reporting
Task Objective: To stay in contact with the client and help ensure the project is on track and meets requirements.
Task Approach: The team will send weekly e-mails explaining the progress of the project. The weekly report will include tasks completed in the previous week, tasks to be completed in the next week, obstacles beyond the team’s reach, resource status, and a spending report.
Task Expected Results: To facilitate communication and keep the team members and the client informed about the progress of the project.
2.2.8.6 Subtask 8f – Personal Log
Task Objective: To document time contributions for each member of the team.
Task Approach: Each team member will keep a log book, which will contain their total hours spent for a particular task. This should include specific dates and times, descriptions, results, and any new ideas related to that specific task.
Task Expected Results: To have a documentation of the number of hours spent on specific tasks.
3 Estimated Resources and Schedules
This section includes the following subsections:
3.1 Estimated Resource Requirement 3.2 Schedules
19
3.1 Estimated Resource Requirement
This section describes the financial, personal, and other resources that will be utilized in order to complete the project.
3.1.1 Personal effort requirement
Personal effort requirements are the assumed hours required by each member in the group to finish the project efficiently and in a timely manner. Table 3 shows the breakdown of hours per person in the team.
Task 1: Project Definition
This task includes statement of the problem, requirements, and the specification made by the client.
Task 2: Technical Considerations
This task contains a list of technologies picked by the team that can be used in product design. It includes extensive research of each technology considered and the components needed to implement it. The team will select the best technology that is feasible to approach the prototype design.
Task 3: End-Product Design
This task consists of the design process for the system once a feasible technology is chosen. The end result will be a well-designed concept that meets the client’s requirement.
20
Task 4: End-Product Implementation
This task consists of taking the concept design and implementing it.
Task 5: End-Product Testing
This task consists of testing the implemented design to ensure the prototype functions properly, and meets the client’s need.
Task 6: End-Product Documentation
Since documentation occurs through out the entire project, this task will be to ensure that all documentation is reviewed and logically assembled near the completion of the project.
Task 7: End-Product Demonstration
The task is to demonstrate the end product to the Industrial Review Board, the client, and the advisor.
Task 8: Project Reporting
This task will involve creating a detailed report of the entire process, from problem definition to presentation.
3.1.2 Other resource requirements
There will be other miscellaneous requirements that are not included in the design budget. These resources are listed in Table 4.
Table 4: Other costsItem Cost (estimation)
Paper Printing $ 15.00
Photocopy $ 10.00
Miscellaneous $ 6.00
Total $ 31.00
3.1.3 Financial requirements
This section includes the total financial resources required to conduct the project. Besides the material cost, the cost of labor is also calculated based on the hourly rate of $10.00. The information on Table 5 lists all items including parts, services, equipment, telephone, postage and printing costs.
21
3.2 Schedule
A forecasted timeline for the project has been generated below in Figure 1. This timeline may not be entirely accurate because it may change as the project continues. Figure 1 shows the team’s initial schedule and Figure 2 below shows the deliverable schedule.
Figure 1: Gantt chart of expected project time span
22
Figure 2: Gant chart of schedule of deliverables
4 Closure Material
4.1 Project Team Information
The section includes the contact information for each person that is involved in this project.
4.1.1 Client Information
Dr. Gregory Smith Iowa State UniversityDepartment of Electrical and Computer Engineering, Senior DesignAddress: 2215 Coover Hall, Ames, IA 50011Website: www.ece.iastate.edu
4.1.2 Faculty Advisor
Mina Mani341 DurhamAmes, IA 50011Phone: 515-294-3918 Fax: [email protected]
4.1.3 Student Team Information
Ali Nahiyan3322 Frederiksen CourtAmes, IA 50010Phone (cell): [email protected]
Chatterjee Shrabantee4533 Steinbeck St, #3Ames, IA 50014Phone (cell): [email protected]
23
Kumar Vaibhav5356 Wallace NielsenAmes, IA 50012Phone (cell): [email protected]
Weigel Alex 1208 Cyclone Ave. Ames, IA 50014Phone (cell): [email protected]
Zeng Tao 4810 Mortensen Rd. #311Ames, IA 50014Phone (cell): [email protected]
4.2 Closing Summary
The Senior Design Lab in the Department of Electrical and Computer Engineering at Iowa State University has incurred a number of security breaches. It has been requested to design a system which will solve the issues of providing only authorized access and prevent multiple entries. The design team proposes to implement an RFID security in conjunction with an IR sensor system. The project’s budget is limited to $150 of equipment and the projected total cost including labor is $6511.75. The design and the implementation of the system will be completed by December 2007. The end project deliverables will include the completed prototype and the necessary documentation. The new security system will thus provide an efficient, cost effective, robust, and highly secure solution.
4.3 References
None
4.4 Appendix
None
24
