Microsoft Word – F22DesignProject.docx
Fall 22 Version 0.1 1
Copyright By PowCoder代写 加微信 powcoder
CSE/EEE 120 Capstone Design Project Fall 2022
Security Gate Control Project Summary
The goal of this project is to design part of the controller to control a security gate. The project is
now in the prototype stage, where a simplified version of the home security system will be built.
There are two inputs and two outputs:
P=1 indicates a password has been entered; P=0 indicates no password has been entered.
F=1 indicates the password is correct; F=0 indicates the password is incorrect.
W=1 warning that an incorrect password has been entered; W=0 prior clock did not have an incorrect
G=1 open the security gate; G=0 close the security gate.
The system operates in the following manner:
• The machine starts in the “Wait” state where the system is assumed to be “armed”. The front gate
and the warning signal should be off.
• When the user attempts to feed in a password (P=1) and the password is correct (F=1), the system
opens the front gate (G=1), and the warning signal is off (W=0)
• If the front gate opens, it is up to you to decide what the system does next.
• When the user attempts to feed in a password (P=1) and the password is wrong (F=0), the system
keeps the front gate shut (G=0), and the warning signal is goes on (W=1).
• The system gives the user several additional opportunities to feed in the correct password. If the
total number of consecutive incorrect passwords fed is 𝑛 or more, then the system keeps the warning
signal on indefinitely until the system gets reset asynchronously.
• If the user feeds in the correct password before reaching the 𝑛th wrong consecutive attempt, the
system opens the gate and stops the warning signal.
• Since you are designing a prototype, you should allow the following flaw in the system for testing
purposes: where the user can trick the system by stopping feeding in any passwords. At which point,
the system “forgets” the number of consecutive incorrect passwords fed in.
• It is up to you to assume a value for 𝑛, but it must be not less than 2 and not more than 4.
• To allow people time to get through the gate, it must remain open for at least 2 clocks.
• It is up to you to determine when the gate closes and what it means if P-0 and F-1.
Once you go through this customer discovery, create two finite state machine designs applying
what you learned from your interviews and using different assumptions. This means
documenting the assumptions made for each design and going through the design process (State
Definition Table, State Transition Diagram, State Transition Table, Combinational Logic
Design). Note that the two designs you create must be functionally different. That is, you can’t
create the same design once as a Mealy machine and once as a Moore machine. That is, the
Fall 22 Version 0.1 2
assumptions you make must be different for the two designs. In addition, at least one of the
designs must be based on Karnaugh maps and logic gates. You will also need to incorporate
flip-flops with asynchronous clear and reset.
Once you have completed two different designs, you will need to choose one design to
implement and simulate in Digital. To do this, you will need to select at least 5 different criteria
to use for comparison of each design and aid in your decision-making process. These criteria
can originate from your customer interviews or from your own engineering intuition. Examples
of criterion can be “ease of design, ease of understanding how it works, size of circuit, extra
features.” Each criterion must be given a weight (totaling 100%) of how important it is to
include in the final design. Each design will then need to be rated against how well it meets each
of the suggested criteria. Based on these ratings, select the best design that meets the customer’s
needs, and implement it in Digital, then simulate it through enough clock cycles showing each
possible state transition. (Depending on your design, this may take multiple simulations.) In
addition, you must show that each position can be visited using proper moves.
Items which go into your template include all your design documents. These include state
definition tables, state transition diagrams, Karnaugh maps, behavioral equations, etc. When you
implement the design in Digital, be sure to include a screenshot of your completed design.
You will also create a video in which you showcase your design. Topics to be covered in the video
should include, but are not limited to,
1. The design assumptions you made
2. A brief description of your two designs and why the one you built was best
3. Showing your Digital design schematic and its features
4. Simulating the design in Digital showing some different scenarios and showing you
visiting each state and enough of the transitions from each state to demonstrate your design.
Deliverables
• You need to propose two different sets of assumptions. That is, how your two designs
• You need to design two finite state synchronous machines that you can demonstrate to your
stakeholders. This would usually be the company liaison, but in this class the stakeholders
are your (UG)TAs, classmates, and instructors.
• The designs must be different in their functionality.
• You should comment on why your controller adds value from multiple perspectives
(technological, societal, financial, environmental, etc.). One or two sentences is sufficient.
• The number of states is not defined, you can use as few or as many as you need to provide
the desired functionality. The minimum number of states permitted is 5.
• If something is not clearly documented in the summary, you need to make assumptions.
The assumptions need to be documented.
Fall 22 Version 0.1 3
• Please remember that you can design the state machines and add functionality to the design
as you see fit. However, you need to collect feedback from at least three stakeholders.
Again, stakeholders are your UGTAs, the lab TAs, and the instructors.
• You should describe in a sentence or two how you changed your design based on the
feedback you received.
• You can use D flip flops, T flip flops or J-K flip flops in your design. The type does not
matter. Mixing different types of flip flops with different trigger edge sensitivity is possible
but not recommended.
• You need to properly document your designs. If you do a “classic” paper-based design,
you need to include diagrams and state tables as well as K-Maps and logic. If you decide
to go with a different implementation (ROM, HDL), you need to comment your code. You
must have a schematic design in Digital which matches your simulation.
• You need to pick the best design and explain why it is the best. It is very helpful to have
judgement metrics in mind, for example, number of states, features, ease of building,
number of logic elements, your understanding of the design, or others that you can come
up with. You need to define the weight of each of these metrics. That is, ease of building
is worth 10 points, number of logic elements 20 points, number of states 40 points, etc.
Award points to each design. For example, if one design is easier to build than the other, it
might get 6 of the 10 points in the category while the other design gets the remaining 4.
The design which has the highest point total is the best! Again, it is up to you to define the
categories (minimum of 5) and the number of points each category is worth. You must
justify the points awarded with one sentence per category. (Do NOT write an essay!)
• You will need to simulate one design in Digital and show the simulation in your video. The
simulation must demonstrate that you meet the rules and must also show how your
assumptions modified the base specification.
• A short video, the contents of which were described above.
• Upload your completed template (which must include a link to your video) and a zip
file of your capstone folder. Upload the template separately even if it is in your zip
file. There will be a 5-point deduction if your template is not submitted separately.
Grading Policy
The grade will be allocated as follows:
• 5% for the value proposition.
• 5% for the stakeholder interviews.
• 5% for documenting the changes performed to your original idea.
• 20% for documentation in the report of how the first circuit performs the application.
• 20% for documentation in the report of how the second circuit performs the application.
• 5% for establishing reasonable criteria for picking one design as the “best” design. (The
one design you build in the hardware lab does not need to be the “best” design.)
• 5% for picking a preferred, “best” design.
Fall 22 Version 0.1 4
• 15% for Digital implementation
• 15% for the video demonstration.
• 5% for following design template guidelines (organization, legibility)
2% (Extra Credit) Completed Self-Assessment Worksheet
程序代写 CS代考 加微信: powcoder QQ: 1823890830 Email: powcoder@163.com