Object oriented data modelling and relational database.

Object oriented data model | Business & Finance homework help

Abstract
Object-oriented data modelling is a type of data modelling that treats data as an object rather than a relational database. It has many advantages over DBMS such as being more efficient in supporting more complex architectures, increased consistency, robustness, and reusability. This paper will give an introduction to object oriented data modeling with discussions around association, generalization and aggregation relationships; cardinalities and other types of constraints; polymorphism; inheritance; and uses within organizations. Additionally it will discuss implications for data management from implementing this system focusing on security aspects needed when dealing with sensitive information in different levels of organizational structure as well as considerations for usability for end users accessing the system.

Introduction
Object-oriented Data Modelling (OODM) is a type of designing model which incorporates object-oriented principles into its framework to process certain specific cases or scenarios related to software development or architecture design effectively [1]. OODM makes use of objects instead of tables or records along with attributes similar to components in traditional models knowns as entities (objects). The main purpose behind using Object Oriented Modeling is representing real world objects accurately by taking their characteristics like state behaviour into consideration [2]. One major advantage it offers over existing databases is rather than forcing developers/architects to think in terms that those systems understand – it allows them to think conceptually about what they’re trying to achieve without concerning themselves too much about how they get there [3]. This can make development significantly faster while at the same time allowing programmers flexibility if they decide changes need to be made later on down the line since there could come up points during development where circumstances shift possibly meaning approaches originally taken are no longer relevant[4]. As such object oriented thinking can enable web application developers avoid certain mistakes like forgetting about critical attributes early on which could lead performance issues down the line if not dealt with initially.[5] It’s becoming increasingly popular due os its integrated support from modern programming languages . Although it has some limitations such missing out amalgamation between potential classes when superimposed upon multiple subclasses , but these challenges have been solved by means algorithms . Therefore utilization off OODM brings desirable outcomes regarding completeness desired applications regarding accuracy & ; integrity . In addition , System designers prefer utilizing OODMs because ease interconnectedness between modules & ; containers wherein lies increase complexity especially distributed systems require interconnection huge datasets more slowly compared conventional methods thus allowing higher scalability capacity given situation arises requiring extension capabilities small section container large environment Association Relationships: An association relationship defines how two classes are related together     through various forms connectivity。

A binary association describes relation between  two instances while ternary one shows successful interconnectivity three  instances respectively ‘many’ specified numbers e . g . one -to – one or   Many – Many likewise any arbitrary figures decided parties involved connecting lines indicate strength relationships define cardinality dimensions 0..1 0..* 1..* references itself class create cycles unnecessary code hence establishing associations removes burden upsurges efficiency Generalization / Aggregation Relationships: Classification grouping functional units whole comprises several parts termed generalisation hierarchy basically denotes subsets source subset inheriting functionality traits provided parent classes topmost given tree arrangement basically serves template offering features facilitating reuse same procedures respective services applied diverse scenarios Another kind characterization aggregating several distinct elements form new unified instance For example petrol engine car definition agglomeration piston crank shaft flywheel conjoined comprise single entity Cardinalities Constraints : Cardinality refers number occurrences particular element conjunction another defined quantities determines either mandatory nonessential aspect operation Polymorphism Inheritance : These both associated term ‘object Orientation’ encircling concepts allow entities changed altered according intended situational demands basic idea works inherited knowledge passed offspring enables execute behaves specialised manner tasks completion Implication Security Considerations : When discussing implications regarding security context involved applying implemented onto organisation realm deal private pertinent considered utmost confidentiality Data shareable depending rules governing access privileges Hierarchical secure payments options safe transaction routes need established provisions powerful Encryption methods safeguard documents exchanged Personal Identification Verification procedures prevent unauthorised intruders accessing interfering confidential resources Usability Considerations Taking account user perspective exercising designed ensure easy navigational transitions avoiding nasty lags response times numerous clicks obtain intended goal results User friendly graphical interface ideal saving cumbersome typing paths build menus roles Likewise user interface layouts themed provide eye pleasing execution processes saves client seeking attending period tutorial sessions boost productivity Also depending degree sophistication employed settings easily adjustable suited individual preferences exploit maximum benefit derived service.