You are to create the following as separate components in VHDL CODE and link them together in VHDL CODE

1. Create a 4-bit shift register that has the following capabilities:
It can have its contents cleared.
2. It can shift its contents to the left, with the lsb being filled by 1-bit input.
3. It can rotate its contents to the left. |
4. List all control inputs needed from the FSM.
2. Create a 4-bit counter that has the following capabilities:
1. It can have its value reset to zero.
2. It can increment by 1
3. It can increment by 2
4. List all control inputs needed from the FSM.
3. Create a state machine that will do the following (in separate states),
Clear the register and reset the counter.
Perform some action on register (you specify which)
3. Perform some action on the counter (you specify which)
Perform a different action on the register (you specify which).
5. Perform a different action on the counter (you specify which).

Solution: the categorization of functional and non-functional requirement are as follows: some of the more typical functional requirements include: • business rules• transaction corrections, adjustments and cancellations• administrative functions• authentication• authorization levels• audit tracking• external interfaces• certification requirements• reporting requirements• historical data• legal or regulatory requirementswhile,some typical non-functional requirements are: • performance – for example response time, throughput, utilization, static volumetric• scalability• capacity• availability• reliability• recoverability• maintainability• serviceability• security• regulatory• manageability• environmental• data integrity• usability• interoperability

My favorite is "be concise."have you ever received an email and had to read a page full of information? by the time you finished reading it, you had to re-read it? i have even hit "reply" so that i could break it down into separate paragraphs and send it back to myself.what is concise? get to the point, fast. when opening an email like this, some will close it or print it to read later.i learned to use the subject line to prepare the reader for content. such as, "need on (blank), " "info only re: (blank)," "request input on (blank)," "read before (blank) meeting." these are just some.if you are asking for something, make that your first sentence. follow this by who, what, when, where, and how. use these, as necessary. example; (1) who (who needs it and or who does it), (2) what (specific description of what is needed), (3) when (specific, i need this by 8: 00 am monday or i need this by 10: 00 am today), (4) where (does it have to be printed and taken to someone, maybe the place of the meeting), (5) how (i need it scanned or faxed back to me at this email address, provide me with a hard copy).do not send yet. re-read it. did some spell check change a word? maybe let someone else read it for understanding. you want to avoid multiple emails asking for clarification. if important, put a read receipt on it. you will know it was opened, not necessarily read.end with a you.

Ineed more infomation