Already have an account? Get multiple benefits of using own account!
Login in your account..!
Remember me
Don't have an account? Create your account in less than a minutes,
Forgot password? how can I recover my password now!
Enter right registered email to receive password!
Q. Explain data aggregation and discuss different design constraints.
Sol. Aggregation One limitation of the E-R model is that it cannot express relationships among relationships. To illustrate the need for such a construct consider the ternary relationships works on which we will see between a employee, branch and job (see figure). Now, suppose we want to record managers for tasks performed by an employee at a branch that is we want to record managers for (employee branch job) combinations. Let us assume that there is an entity set manager. One alternative for representing these relationships is to create a quaternary relationship manages between employee, branch, job and manager (A quaternary relationships required a binary relationship between manager and employee would not permit us to represent which (branch, job) combinations of an employee are managed by which manager.) Using the basic E R modeling constructs we obtain the E R diagram of given figure. It appears that the relationship sets works on and manages can be combined into one single relationship set. Nevertheless we should not combine them into a single relationship since some employee; branch job combinations may not have a manager. There is redundant information in the resultant figure however since every employee; branch job combination it manages is also in works on. If the managers were a value rather than manager entity we could instead make manager a multivalued attribute of the relationship works on. But doing so makes it more difficult to find for example employee branch job triples for which a manager is responsible. Since the manager is manager entity this alternative is ruled out in any case. The best way to model a situation such as the just described is to use aggregation. Aggregation is an abstraction through which relationship are treated as higher level entities. Thus for our example we regard the relationship set works on as a higher level entity set called works on. Such an entity set is treated in the same manager between works on and manager to represent who manages what tasks. Figure shows a notation for aggregation commonly used to represent the above situation.
What is the difference between SQL Server 2000 clustered and nonclustered indexes? With a clustered index, the data are kept in the bottom level of the index and in the similar
Assigning Responsibility for Operation Many operations might have obvious target objects, but some of these operations could be used at numerous places in an algorithm, by one
i need help for assignment ..
sql is relationally complete-justify
What is a shadow copy scheme? It is simple, but efficient, scheme known as the shadow copy schemes. It is based on making copies of the database called shadow copies that singl
Differentiate between Primary and secondary storage? Primary and secondary storage - Primary storage device stores the data temporarily. Primary storage is commonly used thro
lock and types of lock
What are the Objectives of Advance object design After this unit, you shall be able to: combine three OOAD models to obtain operations on the classes; develop algo
Illustrate about the advanced object design Advanced object design is a complex task. The objects discovered through analysis serve as a skeleton of design. The operations reco
Benefits of using heuristics
Get guaranteed satisfaction & time on delivery in every assignment order you paid with us! We ensure premium quality solution document along with free turntin report!
whatsapp: +91-977-207-8620
Phone: +91-977-207-8620
Email: [email protected]
All rights reserved! Copyrights ©2019-2020 ExpertsMind IT Educational Pvt Ltd