There are three steps you should take when planning a database. Match each statement with its proper step. 1. Step 1:
Test the fields with some records and actions you will be using in the actual database.
2. Step 2:
Write down the fields you think you need on a piece of paper.
3. Step 3:
Revise the fields as needed.

It really depends on your memory. if you have a great one then probably. i have done it before personally and it’s stuck with me since i was 6. but if you have a bad one then it might stay for a while but i wouldn’t say permanently

If you go to ask a question and say ask, there should be something that looks like this

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

Any multiple choices