Just need some improvements in own work just in one table and we need a good introduction for my documentation. the teachers giving feedbacks that in m tables. and is the comments we have got Nisha...

Just need some improvements in  own work just in one table and we need a good introduction for my documentation. the teachers giving feedbacks that in m tables. and is the comments we have got Nisha Pate,Wehave just checked some of your work and there are few discrepancies that you will need to fix. Firstly, you need to use the *ERD* as your main point of reference since all the information is there. If an entity has an attribute that has *PK* that indicates that the attribute is a *primary key*, if it has an attribute that has *FK* that indicates that the attribute is a *foreign key*, if it has and attribute or a group of attributes that have both *PK* and *FK* that indicates that the attribute or attributes are *CK* composite keys and finally, if there are attributes that do not have any of these, that means they are neither which simply makes them *normal attributes*. This means that in the *ENTITY SPECIFICATION FORMS*, you are not supposed to give them a status of *FK*, *CK* or *PK* because they are not either of those. Secondly, each *data types* that you identify needs to have a length except for the *DATE*, meaning, if the data type is a number, for example, you would identify it as *NUMBER* and then give it a specific length like *(4)* which means the attribute will have the following data type *NUMBER(4)*. * /THIS IS COMPULSORY/ *. Look at the example from the lecturer's template of *Blackboard* or the ones that I have done. [03/03, 10:03 a.m.] ‪+44 7405 391035‬: Thirdly, you need to identify all of the *relationships* that each entity has with the other entities. The *relationships are the lines or links connecting 2 entities together*. If the lines have *double dashes* on one end that means that end is the *ONE* end and if it has a *crow's foot* on the other end, then that means it is the *MANY* end. So, if it has the *double dashes* on both ends, the relationship is a *ONE-TO-ONE* relationship, and if it has *double dashes* on one end and a * crow's foot* on the other, then this is a *ONE-TO-MANY* relationship. [03/03, 10:03 a.m.] ‪+44 7405 391035‬: In addition to that, in the *validation* column, you do need to right the length of the characters to be entered because you should have identified those in the *data type*. The length is the *number is the brackets*. You also need to show an example in the last column as seen in the template provided by the lecturer. astly, make sure that everything that you do which is related to the *entity specification forms* comes from the *ERD* because that is *where all the information is stored*. All you have to do is refer to that specific diagram. SO i need you to look a the example whici is i n the docoment that i have created and just improve the table by looking a te example and the feedbacks above.