NOTE:::::: I do not want you guys to solve it but can you guys give me academic

Question

NOTE::::::

I do not want you guys to solve it

but can you guys give me academic advise on how to touch this one maybe show me an example.

----------------------------------------

this second phase, you will produce a relational schema from the entity-relationship diagram you came up with in Phase 1, and verify all use cases are being realized. Make sure to address issues (remarks) raised by your instructor in the first phase, if any.

Submit the following:

(1) Complete E/R diagram from Phase 1 (20 points)

On you E/R diagram, clearly describe each entity (including, list of entity attributes, the entity primary key, and any foreign keys) and each relationship with its multiplicities.

(2) Relational Model  (20 points)

Using the method for translating an E/R diagram to relations, produce a set of relations for your database design. As usual, please be sure to underline key attributes in your relations.

(3) Complete Database Functionalities and User Interface  (20 points)

(a) List all actors (i.e. users) of your database

(b) For each actor, list all use-cases including all the steps. For each entity, you must have use cases that perform at least one aggregate query, one insert operation, one delete operation, and one update operation; For each relationship, you must have use cases that perform at least one joint query.

(c) Specify the web interface if you are required to implement it.

(4) Use Case Realization  (20 points)

Provide

(5) Database Prototype  (10 points)

(a) Describe platform and any software tools you plan to use to implement your project.

(b) Clearly indicate how you plan to populate your database.

(6) Project Time Table  (10 points)

(a) List major tasks to a be completed

(b) For each task, indicate team member responsible for competing task and completion data.

Explanation / Answer

Assume you have a system which will have many components human/non-human. Describe each of those components as en entity in ER diagram. Each of these entities will have certain attribute, e.g. if there is a customer entity then it will have customerID, name, order history,etc. If there is an item customer is purchasing then there could be en entity corresponding to that item in your ER diagram which might have attributes such as price, brand, etc. Thus sense of ER-diagram is to identify and model all such entities.

Now once you ave your ER-diag ready, it's easy to transform it into relation model. All you have to you to do is define a schema/relation corresponding to every entity in your ER diagram, all the attributes of this entity will become columns of the relation defined on that entity. Entities will also share some relationships in the ER-diag, which can be transformed into relation model using keys.

Now is time to define some operations in the system, all these entities must be interacting with each other in the form of order purchase, billing, openning new account,etc. Model all these operations as methods in the system and also provide users of the system a place to get integrate with the system which can be in the form of a UI.
All the entities of the ER-diag can perform these operations on the relations defined in step 2.

Define classes or interfaces to model and aggregate all the above mentioned components together and research what kind of data features you are going to need to select appropriate database for the application. If you plan to provide user interface then choose how the data in the database is presented to the users and how to control the operations over data over the period of time.

Related Questions

Navigate

• Browse (All)
• Browse N
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.