can you please draw the ER design question 4

this are the answers for this questions

this are the answers but there is no ER diagram they did not draw i need you to draw for question 4

this are the answers but in question 4 they did not draw the ER diagram

what not clear

this is the question

and this are the answers there is only no ER design i want you to draw only the ER

this are the answers but question he did not draw i want you to draw only all the answers are up it will help look at the answers for question three

my topic is (Automated teller and bank domain) don't changed please Phasel Analysis Report (Conceptual design) 30% The purpose of this task is to analyze the requirements for your domain of application and to express those requirements in a DBMS-independent way. This will be accomplished by using the entity relationship model Your design should include an ER diagram using as many of the entity relationship model constructs as necessary to fully express the database requirements of the application in particular, entities relationships attributes of entities and relationships), generalizations, keys. ind constraints should be included in your design as required by the application The Phase Report should include the following 1. A description of the application domain of your choice. State as clearly as possible what you want to do 2. A description of the functionalities that you plan to offer 3. Ann ER design. For each ently, a diagram or listing showing the attributes of the ently and an indication of any constraints on the entry or to tributes (eg, keys muti-valued attributes, composite attributes to) 4 in your ER design, include all relationships among your entities showing any attributes and constrains my topic is (Automated teller and bank domain) my topic is (Automated teller and bank domain) don't answer with anothor topic please if you don't know don't answer 6:23 Answer 1 of 1 Done Analysis Report on a conceptual design 1. Application domain: Automated Teller and Bank Domain The Automated Teller and Bank domain can be used widely and can reduce a lot of pressure on the Banking Staff as they deal with a lot of people with a lot of queries which might be quite basic but important to the Bank customers and depositors. 2. The Functionalities which can be offered are a. Cash Withdrawal b. Account details c. Cash Deposit d. Registered Mobile number change e. A Mini account statement These are the functions that we would try and include in our ER 3. Attributes that are required for each functionality CASH WITHDRAWAL a. A debit or a credit card issued by the bank b. PIN Number which is set by the customer and is confidential to the customer c. The Amount that needs to be withdrawn d. A Receipt of the transaction ACCOUNT DETAILS a. A debit card or a credit card issued by the bank b. The Registered Mobile number c. Type of account d. A receipt for the transaction CASH DEPOSIT a. Debit card issued by the bank b. Account information of the individual c. Cash counting machine d. A receipt for the transaction REGISTERED MOBILE NUMBER CHANGE a. Debit or a Credit card of the Bank b. Exisitng Resigtered Mobile number c. New mobile number d. Authentication OTP for new Mobile number A MINI ACCOUNT STATEMENT a. Debit or a credit card of the bank b. PIN number of the card c. Requested service d. Receipt of the transaction. 4. The relationship between all of these is these all things can be done on a single computer or a machine one at a time by any person who usually holds a bank- issued credit card or a debit card. There are no such structural constraints in this system and mostly it would be that a camera or a monitoring device should be installed to see in case something goes wrong. Phasel: Analysis Report (Conceptual design) 30% The purpose of this task is to analyze the requirements for your domain of application and to express those requirements in a DBMS-independent way. This will be accomplished by using the entity-relationship model. Your design should include an ER diagram using as many of the entity-relationship model constructs as necessary to fully express the database requirements of the application. In particular, entities, relationships, attributes (of entities and relationships), generalizations, keys. and constraints should be included in your design as required by the application The Phase Report should include the following 1. A description of the application domain of your choice. State as clearly as possible what you want to do 2. A description of the functionalities that you plan to offer. 3. An initial ER design. For each entity, a diagram or listing showing the attributes of the entity and an indication of any constraints on the entity or its attributes (..keys, multi-valued attributes, composite attributes, etc.) 4 In your ER design, include all relationships among your entities showing any descriptive attributes and structural constrains. Phasel: Analysis Report (Conceptual design) 30% The purpose of this task is to analyze the requirements for your domain of application and to express those requirements in a DBMS-independent way. This will be accomplished by using the entity-relationship model. Your design should include an ER diagram using as many of the entity-relationship model constructs as necessary to fully express the database requirements of the application. In particular, entities, relationships, attributes (of entities and relationships), generalizations, keys. and constraints should be included in your design as required by the application The Phase Report should include the following 1. A description of the application domain of your choice. State as clearly as possible what you want to do. 2. A description of the functionalities that you plan to offer. 3. An initial ER design. For each entity, a diagram or listing showing the attributes of the entity and an indication of any constraints on the entity or its attributes (0.9. keys, multi-valued attributes, composite attributes, etc.). 4. In your ER design, include all relationships among your entities showing any descriptive attributes and structural constrains. 6:23 Answer 1 of 1 Done Analysis Report on a conceptual design 1. Application domain: Automated Teller and Bank Domain The Automated Teller and Bank domain can be used widely and can reduce a lot of pressure on the Banking Staff as they deal with a lot of people with a lot of queries which might be quite basic but important to the Bank customers and depositors. 2. The Functionalities which can be offered are a. Cash Withdrawal b. Account details c. Cash Deposit d. Registered Mobile number change e. A Mini account statement These are the functions that we would try and include in our ER 3. Attributes that are required for each functionality CASH WITHDRAWAL a. A debit or a credit card issued by the bank b. PIN Number which is set by the customer and is confidential to the customer c. The Amount that needs to be withdrawn d. A Receipt of the transaction ACCOUNT DETAILS a. A debit card or a credit card issued by the bank b. The Registered Mobile number c. Type of account d. A receipt for the transaction CASH DEPOSIT a. Debit card issued by the bank b. Account information of the individual c. Cash counting machine d. A receipt for the transaction REGISTERED MOBILE NUMBER CHANGE a. Debit or a Credit card of the Bank b. Exisitng Resigtered Mobile number c. New mobile number d. Authentication OTP for new Mobile number A MINI ACCOUNT STATEMENT a. Debit or a credit card of the bank b. PIN number of the card c. Requested service d. Receipt of the transaction. 4. The relationship between all of these is these all things can be done on a single computer or a machine one at a time by any person who usually holds a bank- issued credit card or a debit card. There are no such structural constraints in this system and mostly it would be that a camera or a monitoring device should be installed to see in case something goes wrong. Phase : Analysis Report (Conceptual design) 30% The purpose of this task is to analyze the requirements for your domain of application and to express those requirements in a DBMS-independent way. This will be accomplished by using the entity-relationship model Your design should include an ER diagram using as many of the entity-relationship model constructs as necessary to fully express the database requirements of the application. In particular, entities, relationships, attributes (of entities and relationships), generalizations, keys, and constraints should be included in your design as required by the application. The Phase 1 Report should include the following: 1. A description of the application domain of your choice. State as clearly as possible what you want to do. 2. A description of the functionalities that you plan to offer. 3. An initial ER design. For each entity, a diagram or listing showing the attributes of the entity and an indication of any constraints on the entity or its attributes (e.g., keys, multi-valued attributes, composite attributes, etc.). 4. In your ER design, include all relationships among your entities showing any descriptive attributes and structural constrains. 5:59 all LTE Answer 1 of 1 Done Analysis Report on a conceptual design 1. Application domain: Automated Teller and Bank Domain The Automated Teller and Bank domain can be used widely and can reduce a lot of pressure on the Banking Staff as they deal with a lot of people with a lot of queries which might be quite basic but important to the Bank customers and depositors. 2. The Functionalities which can be offered are a. Cash Withdrawal b. Account details c. Cash Deposit d. Registered Mobile number change e. A Mini account statement These are the functions that we would try and include in our ER 3. Attributes that are required for each functionality CASH WITHDRAWAL a. A debit or a credit card issued by the bank b. PIN Number which is set by the customer and is confidential to the customer c. The Amount that needs to be withdrawn d. A Receipt of the transaction ACCOUNT DETAILS a. A debit card or a credit card issued by the bank b. The Registered Mobile number c. Type of account d. A receipt for the transaction CASH DEPOSIT a. Debit card issued by the bank b. Account information of the individual c. Cash counting machine d. A receipt for the transaction REGISTERED MOBILE NUMBER CHANGE a. Debit or a Credit card of the Bank b. Exisitng Resigtered Mobile number c. New mobile number d. Authentication OTP for new Mobile number A MINI ACCOUNT STATEMENT a. Debit or a credit card of the bank b. PIN number of the card c. Requested service d. Receipt of the transaction. 4. The relationship between all of these is these all things can be done on a single computer or a machine one at a time by any person who usually holds a bank- issued credit card or a debit card. There are no such structural constraints in this system and mostly it would be that a camera or a monitoring device should be installed to see in case something goes wrong. Phase I: Analysis Report (Conceptual design) 30% The purpose of this task is to analyze the requirements for your domain of application and to express those requirements in a DBMS-independent way. This will be accomplished by using the entity-relationship model Your design should include an ER diagram using as many of the entity-relationship model constructs as necessary to fully express the database requirements of the application. In particular, entities, relationships, attributes (of entities and relationships), generalizations, keys, and constraints should be included in your design as required by the application. The Phase 1 Report should include the following: 1. A description of the application domain of your choice. State as clearly as possible what you want to do. 2. A description of the functionalities that you plan to offer. 3. An initial ER design. For each entity, a diagram or listing showing the attributes of the entity and an indication of any constraints on the entity or its attributes (e.g., keys, multi-valued attributes, composite attributes, etc.). 4. In your ER design, include all relationships among your entities showing any descriptive attributes and structural constrains