Entity Relationship Diagram

The purpose of this study was to examine the relationships between assertiveness, self-esteem, and relationship satisfaction while also accounting for the demographic variables of gender, age, relationship duration, and household income. An online survey-based, quantitative study (n=220) examined the following research questions: RQ1. What is the correlation between self-esteem, assertiveness, and relationship satisfaction? RQ2. Does self-esteem mediate the relationship between assertiveness and relationship satisfaction? RQ3. What factors are most significant in predicting relationship satisfaction? It was found that (RQ1) self-esteem and relationship satisfaction (p<.001) and self-esteem and assertiveness were correlated (p<.001). However, because assertiveness was not significantly related to relationship satisfaction, a mediational model was not tested (RQ2). Finally, when examining (RQ3) the most salient factors (length of relationship, income, assertiveness, self-esteem, gender) associated with relationship satisfaction via an ordinal regression model, only self-esteem remained significant (p<.001). The findings support previous research conclusions and suggest that self-esteem has a greater predictive ability on relationship satisfaction than assertiveness, but that further research is needed to understand these findings.

Meerkat is a tool for visualization and community mining of social networks. It is being developed to offer novel algorithms and functionality that other tools do not possess. Meerkat's features include navigation through graphical representations of networks, network querying and filtering, a multitude of graphical layout algorithms, community mining using recently developed algorithms, and dynamic network event analysis using recently published algorithms. These features will allow more insightful exploratory analysis and more robust inferences about communities and the significance of entity relationships. Meerkat is under active development, and future features will include additional options for community mining and visualization, focusing on algorithms and user interface designs not existing in other social network analysis tools.

In 1993 Kennedy identified three elementary structures into which any entity relationship diagram may be decomposed. He later investigated the use of elementary structure counts as the basis of a metric for effort estimation, but found very poor correlation. Some question was raised about the counting strategy employed and about the reliability of the effort data used, both of which could have contributed to the unsatisfactory results. In order to refine methods for counting elementary structures in the entity relationship diagram some mechanism for assigning relative importance to particular entities is necessary. One approach is for the developer to make this decision, but this then precludes the possibility of automation. This paper explores the use of an exhaustive counting method for identifying principal entities, which can in turn be utilised in the subsequent determination of metrics for effort estimation A further eighteen information system development projects have been analysed and details of their entity relationship models and corresponding structure counts. The author has also gone to pains to improve the quality of the associated effort data.

A crucial task in Knowledge Representation is answering queries posed over a knowledge base, represented as a set of facts plus a set of rules. In this paper we address the problem of answering conjunctive queries posed over knowledge bases where rules are an extension of Datalog rules, called Datalog ∃ rules, that may have existentially quantified variables in the head; this kind of rules are traditionally called tuple-generating dependencies (TGDs) in the database literature, but they are broadly used in description logics and in ontological reasoning. In this setting, the chase algorithm is an important tool for query answering. So far, most of the research has concentrated on cases where the chase terminates. We define and study large classes of TGDs under which the query evaluation problems remain decidable even in case the chase does not terminate. We provide tight complexity bounds for such cases. Our results immediately extend to query containment.

Requirements traceability is the ability to follow the life of a requirement i.e. from its origin, to its refinement and inclusion in the requirement specification document, and from there to its subsequent deployment in coding, testing and validation. Pre-Requirement Traceability is concerned with requirement's life before its inclusion in the requirement specification, while Post-Requirement Traceability is concerned with the requirement's life after its inclusion in the requirement specification.

A new data model has been developed to handle information relevant to site-specific life cycle Ž. assessments LCA. The model is orientated towards GIS-representations of three generalised subsystems; the technical, the environmental and the social subsystems. The technical and environmental systems are mainly linked through flows of energy and matter, which are the causes of environmental impacts, which subsequently is perceived, evaluated and acted upon by the social subsystem. For all three systems important differences, attributable to geographical locations can be determined. With the new data model a possibility to enhance LCA and reach more relevant results emerge due to a higher site specificity. The high level data model is expressed as Ž. relations between different entities using the entity relationship ER modelling language. An existing LCA-database, SPINE, which is already used by several companies for decision support in product development, can be utilised since the structure of the database supports geographical information. So far, applications with GIS-data are limited, but examples of area specific LCA impact characterisation factors exist.

This article reports the results of research into software project management. the main contribution of this research is a software project management framework that consists of a static structure, shown in an entity-relationship diagram, and a description of each component of the framework. It also describes the procedure to design and validate the framework. This consists of integrating the solutions

Seiring perkembangan zaman, kini teknologi informasi menjadi mendominasi di segala bidang, terutama bisnis dan ekonomi. Banyak perusahaan yang sudah menerapkan teknologi informasi sebagai alat pendukung dalam proses bisnis perusahaan tersebut. Salah satu penerapan teknologi informasi adalah, baik perusahaan kecil maupun besar sudah menggunakan sistem basis data dalam mengelola data perusahaannya. DBMS (Database Management System). PT Putra Sumber Utama Timber (PSUT) merupakan salah perusahaan yang bergerak di bidang pengolahan kayu lapis. Dalam sistem informasi produksinya, PT Putra Sumber Utama Timber masih menggunakan sistem informasi berbasis komputer dan kertas. Beberapa kendala yang dialami perusahaan dalam menggunakan sistem informasi berbasis komputer adalah adanya duplikasi data, kesulitan dalam pembuatan laporan dan pencarian data. Maka dari itu, PT Putra Sumber Utama Timber (PSUT) perlu menerapkan teknologi sistem basis data dalam proses bisnisnya. Dengan menggunakan sistem basis data dalam proses bisnis perusahaan, dapat membuat pengeluaran biaya dan waktu pengerjaan menjadi lebih efisien.

Kata Kunci: basis data, sistem informasi, teknologi informasi, produksi

is one of six departments that make up the School of Business at the University of Otago. The department offers courses of study leading to a major in Information Science within the BCom, BA and BSc degrees. In addition to undergraduate teaching, the department is also strongly involved in postgraduate research programmes leading to MCom, MA, MSc and PhD degrees. Research projects in spatial information processing, connectionist-based information systems, software engineering and software development, information engineering and database, software metrics, distributed information systems, multimedia information systems and information systems security are particularly well supported. The views expressed in this paper are not necessarily those of the department as a whole. The accuracy of the information presented in this paper is the sole responsibility of the authors. Copyright Copyright remains with the authors. Permission to copy for research or teaching purposes is granted on the condition that the authors and the Series are given due acknowledgment. Reproduction in any form for purposes other than research or teaching is forbidden unless prior written permission has been obtained from the authors.

A web based course monitoring report system is required to be developed. The CMR requires roles
for various number of users such as the Course Leader, Course Moderator, Pro-Vice Chancellor
and Director of Learning and Quality. Each user has specific functions in the system to carry out
in order to the course monitoring report to be approved.
A Course Leader enters details in to the CMR form for a certain course. The CMR Report has to
be created for every academic year. Once the CMR is created, the system sends the Course
Moderator the report for approval. Once the CMR Report is approved by the Course Moderator
the Pro-Vice Chancellor and Director of Learning and Quality can view the report. The Director
of Learning and Quality can comment a report. The system contains an Administrator who can
access and view the overall system. The system contains a guest account which displays reports.

Computer Automated Multi-Paradigm Modelling (CAM-PaM) is an enabler for domain-specific analysis and design. Traffic, a new untimed visual formalism for vehicle traffic networks, is introduced. The syntax of Traffic models is meta-modelled in the Entity-Relationship Diagrams formalism. From this, augmented with concrete syntax information, a visual modelling environment is synthesized using our CAMPaM tool AToM 3 , A Tool for Multi-formalism and Meta-Modelling. The semantics of the Traffic formalism is subsequently modelled by mapping Traffic models onto Petri Net models. As models' abstract syntax is graph-like, graph rewriting can be used to transform models. The advantages of a domain-specific formalism such as Traffic as opposed to a generic formalism such as Petri Nets are presented. We demonstrate how mapping onto Petri Nets allows one to employ the vast array of Petri Net analysis techniques. A Coverability Graph is generated and conservation analysis is automated by transforming this graph into an Integer Linear Programming specification.

1. LANDASAN TEORI 1.1 Basis Data Pengertian Basis Data-Basis Data terdiri dari kata basis dan data. Basis dapat diartikan sebagai markas atau gudang. Sedangkan data adalah catatan atas kumpulan fakta dunia nyata yang mewakili objek seperti manusia, barang, hewan, konsep, peristiwa dan sebagainya yang diwujudkan dalam bentuk huruf, angka, simbol, gambar, teks, bunyi atau kombinasinya. Dengan basis data seseorang dapat menyimpan sebuah informasi, seperti data mahasiswa, kepegawaian atau produk ke dalam media penyimpanan elektronis seperti cakram magnetis (disk) melalui perangkat komputer, Untuk kemudian data tersebut dapat kita gunakan sesuai keperluan. 1.2 ERD ERD adalah salah satu model yang digunakan untuk mendesain database dengan tujuan menggambarkan data yang berelasi pada sebuah database. Umumnya setelah perancangan ERD selesai berikutnya adalah mendesain database secara fisik yaitu pembuatan tabel, index dengan tetap mempertimbangkan performance. Kemudian setelah database selesai dilanjutkan dengan merancang aplikasi yang melibatkan database. ERD memiliki beberapa aliran notasi seperti notasi Chen (dikembangkan oleh Peter Chen), Barker (dikembangkan oleh Richard Barker, Ian Palmer, Harry Ellis), notasi Crow's Foot, dan beberapa notasi lain. Namun yang banyak digunakan adalah notasi dari Chen. Entity Relationship Diagram (ERD) merupakan gambaran yang merelasikan antara objek yang satu dengan objek yang lain dari objek didunia nyata yang sering dikenal dengan hubungan antar entitas. (Yanto, 2016:32) Menurut Dawan (2019), "ERD atau Entity Relationship Diagram merupakan teknik yang digunakan untuk memodelkan kebutuhan data dari suatu organisasi, biasanya oleh sistem analis dalam tahap analisis persyaratan proyek pengembangan sistem". Berikut adalah simbol simbol yang digunakan pada ERD dengan notasi Chen:

Like many things involving technology, the database has a life cycle associated to it. • The DBLC contains six phases: database initial study, database design, implementation and loading, testing and evaluation, operation, and maintenance and evolution. • The image illustrates the position of database design in the context of database development.

Database and data model evolution cause significant problems in the highly dynamic business environment that we experience these days. To support the rapidly changing data requirements of agile companies, conceptual data models, which constitute the foundation of database design, should be sufficiently flexible to be able to incorporate changes easily and smoothly. In order to understand what factors drive the maintainability of conceptual data models and to improve conceptual modelling processes, we need to be able to assess conceptual data model properties and qualities in an objective and cost-efficient manner. The scarcity of early available and thoroughly validated maintainability measurement instruments motivated us to define a set of metrics for Entity-Relationship (ER) diagrams. In this paper we show that these easily calculated and objective metrics, measuring structural properties of ER diagrams, can be used as indicators of the understandability of the diagrams. Understandability is a key factor in determining maintainability as model modifications must be preceded by a thorough understanding of the model. The validation of the metrics as early understandability indicators opens up the way for an in-depth study of how structural properties determine conceptual data model understandability. It also allows building maintenance-related prediction models that can be used in conceptual data modelling practice.

1. What two conditions must be met before an entity can be classified as a weak entity? Give an example of a weak entity. To be classified as a weak entity, two conditions must be met: 1. The entity must be existence-dependent on its parent entity. 2. The entity must inherit at least part of its primary key from its parent entity. entity: 1. CLASS is clearly existence-dependent on COURSE. (You can database course exists.) 2. CRS_CODE. The CRS_CODE attribute is also the PK of COURSE. The conditions that define a weak entity are the same as those for a strong relationship between an entity and its parent. In short, the existence of a weak entity produces a strong relationship. And if the entity is strong, its relationship to the other entity is weak. (Note the solid relationship line in the tex decisions. For instance, if the database designer had decided to use a single-attribute as shown in 8, the CLASS entity wou CLASS_CODE, which is not derived from the COURSE entity.) In this case, the relationship between COURSE and CLASS is weak. However, regardless of how the designer classifies the relationship weak or strong CLASS is always existence-dependent on COURSE. 2. A strong relationship exists when en entity is existence-dependent on another entity and inherits at least part of its primary key from that entity. The Visio Professional software shows the strong relationship as a solid line. In other words, a strong relationship exists when a weak entity is related to its parent entity. (Note the discussion in question 1.)

Sistem Point of Sales merupakan sistem yang sangat berguna bagi
sebuah usaha restoran seperti RESTO. Penerapan sistem Point of Sales bagi RESTO dapat membantu mempermudah dan mempercepat proses kerjanya.

Dalam sistem Point of Sales ini terdapat berbagai fitur seperti:
a. Pencatatan transaksi
b. Pencatatan reservasi
c. Pencatatan data master
d. Pembuatan laporan otomatis
Fitur-fitur tersebut di atas akan mempermudah RESTO dalam menjalankan
proses bisnisnya, serta membantu manajer usaha untuk mendapatkan
rekapitulasi hasil usaha dalam periode tertentu dengan mudah.

Dimensional modelling is a conceptual modelling technique developed for designing data warehouse structures. It has become the predominant approach to designing data warehouses in practice and has proven to be highly successful in developing database structures that can be used directly by end users. This paper examines the nature of dimensional modelling and its relationship to traditional Entity Relationship (ER) modelling. It shows that a dimensional model is just a restricted form of an ER model, and that there is quite a straightforward mapping between the two. Understanding the relationship between the two types of models can help to bridge the gap between operational system (OLTP) design and data warehouse (OLAP) design. It also helps to resolve the difficult problem of matching supply (operational data sources) and demand (end user information needs) in data warehouse design. Finally, it results in a more complete dimensional design, which is less dependent on the designer's ability to choose the "right" dimensions. The paper also reports some preliminary results from empirical testing of the approach.

Fire is as destructive as it is useful. Without a proper pro-active approach to preventing fire outbreaks, the results could be extremely disastrous when they occur. Thus, there is a need for a fast and convenient way of reporting fire incidents. The growing usage of smartphones provides a way of equipping the public with a means of reporting fire incidents to ensure prompt response and proper management of the incidents. In this paper, we analyze the manual process of reporting fire outbreaks and design an automated FEAP-a mobile application, to enable the public to quickly alert nearest fire emergency units of any possible fire incidents. We developed FEAP with the aid of the Software Development Life Cycle (SDLC) phases and Unified Modeling Language (UML) which was used as a model to visualize the design view of the application. An Entity Relationship Diagram (ERD) was used for database design and a simple Graphical User Interface (GUI) prototype of the proposed application was designed. Our work highlights a practical application of analysis and design concepts in developing software to provide an efficient solution in reporting fire outbreaks.

The aim of the project was to design a database in Oracle SQL Developer to provide the functional requirements of patient in Hospital management system.
The project requirements included:
• Describe data using an Entity Relationship Diagram (ERD) including primary and foreign keys, constraints, attributes, relationship cardinality and assumptions where necessary
• Using Oracle and SQL create the database entities required to support the data storage needs of the Hospital management system
• Populate each entity with records
• Create reports for management (using SQL) according to outlined requirements
• Describe major considerations  to securing patient data using Oracle

"Databases are powerful data storage and manipulation facilities which can be used to organize and optimize workload. The large amounts of data that they manage make them complex entities which demand a rigorous yet flexible approach to its
design and implementation. Universities make use of databases to manage and optimize information flow. This project designed functions specifically for the Department of Electrical and Computer Engineering at the University of the West Indies. Such
functions included managing lecturing staff research interests, scheduled times, and assigned courses. Administrative staff users were given functions to search listings and assign courses to both lecturing staff and special groups.

Each function intended to provide easy access to information from which users could manage schedules, organize data, and manage time better. This was aided by the reminder and email generation functions which generated files which could be imported into the standard departmental email, Outlook. The database was implemented using an SQL database server and an Apache web server. Functions were performed using PHP scripts and the user interacted with a user-friendly interface with a navigational menu. The final system performed well especially in error detection and speed of displayed results."

Pembayaran administrasi sekolah mempunyai peran penting dalam menunjang aktivitas sekolah, di dalam aktivitas tersebut SD Beyond memiliki kendala yaitu masih banyaknya kesalahan dalam proses pendataan pembayaran, tidak tertagihnya pembayaran, dan pembuatan
laporan yang selama ini masih secara manual membutuhkan waktu yang lama. Oleh karena itu tujuan penulis melakukan analisis ini adalah untuk membuat rancangan sistem basis data yang dapat menjadi solusi pemecahan dari kendala di atas.

Rancangan sistem basis data ini diharapkan dapat membantu SD Beyond khususnya staff tata usaha untuk dapat menghasilkan informasi yang akurat. Setelah melakukan perancangan terhadap sistem basis data, penulis hendak mengimplementasikan SQL query terhadap sistem basis data yang telah dirancang.

The main aim of developing this system is to provide blood to the people who need at immediate levels. The number of people in demand of blood for transfusions are increasing day by day.  Using this system any user can search for available person readily available to donate blood for particular group type in the particular city. So if the blood is not available at the nearest blood bank, the user can use this online dbms system and get it as soon as possible and can save someone's life. This system is easy to use entering basing registration details.

UNIT II DATABASE DESIGN
Entity-Relationship model – E-R Diagrams – Enhanced-ER Model – ER-to-Relational Mapping –
Functional Dependencies – Non-loss Decomposition – First, Second, Third Normal Forms, Dependency
Preservation – Boyce/Codd Normal Form – Multi-valued Dependencies and Fourth Normal Form – Join
Dependencies and Fifth Normal Form.

This paper first examines crime situation in Benin metropolis using questionnaire to elicit information from the public and the police. Result shows that crime is on the rise and that the police are handicapped in managing it because of the obsolete methods and resources at their disposal. It also reveals that members of the public have no confidence in the police force as 80% do not report cases for fear of exposure to the informant to the criminal. In the light of these situations, the second part of the paper looks at the possibility of utilizing GIS for effective management of crime in Nigeria. This option was explored by showing the procedural method of creating 1) digital landuse map showing the crime locations, 2) crime geo-spatial database, and 3) spatial analysis such as query and buffering using ILWIS and ArcGIS software and GPS. The result of buffering analysis shows crime hotspots, areas deficient in security outfit, areas of overlap and areas requiring constant police patrol. The study proves that GIS can give a better synoptic perspective to crime study, analysis, mapping, proactive decision making and prevention of crime. It however suggests that migrating from traditional method of crime management to GIS demands capacity building in the area of personnel, laboratory and facilities backed up with policy statement.

Data warehousing systems enable enterprise managers to acquire and integrate information from heterogeneous sources and to query very large databases efficiently. Building a data warehouse requires adopting design and implementation techniques completely different from those underlying information systems. In this paper we present a graphical conceptual model for data warehouses, called Dimensional Fact model, and propose a semi-automated methodology to build it from the pre-existing Entity/Relationship schemes describing a database. Our conceptual model consists of tree-structured fact schemes whose basic elements are facts, attributes, dimensions and hierarchies; other features which may be represented on fact schemes are the additivity of fact attributes along dimensions, the optionality of dimension attributes and the existence of non-dimension attributes. Compatible fact schemes may be overlapped in order to relate and compare data. Fact schemes may be integrated with information of the conjectured workload, expressed in terms of query patterns, to be used as the input of a design phase whose output are the logical and physical schemes of the data warehouse.

Dokumen Deskripsi Perancangan Perangkat Lunak
(DPPL) ini merupakan dokumen yang mendefinisikan perancangan perangkat lunak SIGIT (Sistem Informasi Gym Berbasis IT). Dokumen ini digunakan sebagai acuan teknis pengembangan perangkat lunak Studio Gym Fit & Fun dan acuan implementasi pada tahap berikutnya.

organizations of Bangladesh can no more be maintained manually. There is a growing need for the information to become computerized so that it can be suitably stored. This is where databases come into the picture. Databases are convenient storage systems which can store large amounts of data and together with application programs such as interfaces they can aid in faster retrieval of data. An initiative was taken to design a complete database system for a hospital management such as Bangladesh Institute of Research and rehabilitation in Diabetes,

Dokumen Deskripsi Perancangan Perangkat Lunak
(DPPL) ini merupakan dokumen yang mendefinisikan perancangan perangkat lunak SILIPI (Sistem Informasi Listrik Pintar). Dokumen ini digunakan sebagai acuan teknis pengembangan perangkat lunak PT. Electronic Indonesia dan acuan implementasi pada tahap berikutnya.

Th 4+1 ViewMOdel organizes a description of a sojiware architecture using Jive conmwent views, each of which e all have seen turely partitioning the software or many-books and-articles in which a single diagram attempts to capture the gist of a system architecture. But when you look carefully at the diagram's boxes and arrows, it becomes clear that " Architeas capture their design decision5 in four views and use t,r,e~fih vim to illustrate and validate them.

We present a system for measuring the Function Point software metric from specifications expressed in the form of an Entity Relationship (ER) diagram and a Data Flow Diagram (DFD). As a first step towards the implementation of the system, the informal Function Point counting rules have been translated into rigorous rules expressing properties of the ER-DFD. Prolog was chosen for the implementation because of its declarativity and maintainability. Thanks to its relational representation, it was possible to directly represent the input ER-DFD with Prolog facts. Declarativity allowed a straightforward translation of the rigorous rules into code and a quick implementation of a working prototype. Finally, maintainability was a primary concern since the Function Point counting method is continually evolving.

Conceptual modeling is one of the most important phases in designing database applications. The success of this design relies heavily on how clearly the real world requirements are represented in the conceptual model. To date, the Extended Entity Relationship (EER) model extended from the traditional Entity Relationship (ER) model is a widely used modeling technique during the phase of conceptual modeling. This paper identifies semantic ambiguities that are still present in the EER model leading to incorrect knowledge representation and eventually to incorrect design of relational database schema. These ambiguities are identified in case of many-to-many relationships which have their own attributes. This paper shows that mapping such relationships to a relational database schema generates relations having primary keys which cannot guarantee unique tuples for real world data thus violating the definition of a primary key. In addition, it shows that these relations may not satisfy second normal form. A number of such cases are elaborated and a new concept of multi-valued relationship attribute is introduced that can successfully represent these real world constraints. For this concept, a diagrammatic notation to use in ER diagram is introduced. A mapping algorithm to transform the corresponding EER model to a relational database schema is also defined. This concept of multi-valued relationship attribute and its mapping to relational schema generate relations which satisfy higher normal forms.

Since its introduction, the Entity-Relationship (ER) model has been the vehicle of choice in communicating the structure of a database schema in an implementation-independent fashion. Part of its popularity has no doubt been due to the clarity and simplicity of the associated pictorial Entity-Relationship Diagrams ("ERD's") and to the dependable mapping it affords to a relational database schema. Although the model has been extended in different ways over the years, its basic properties have been remarkably stable. Even though the ER model has been seen as pretty well "settled," some recent papers, notably [4] and [2 (from whose paper our title is derived)], have enumerated what their authors consider serious shortcomings of the ER model. They illustrate these by some interesting examples. We believe, however, that those examples are themselves flawed. In fact, while not claiming that the ER model is perfect, we do believe that the overhauls hinted at are probably not necessary and possibly counterproductive.

Lack of support for Entity-Relationship (E-R) semantics and the disconnect between objectoriented programming language (OOPLs) and database languages remain key roadblocks to the effective use of object-orientation in information system development. We have defined SOODAS (Semantic Object-Oriented Data Access System), a purely object oriented language that supports E-R semantics and set level querying, and provides related development tools.

The Teton Whitewater Kayak case is designed to provide students with a challenging hands-on exercise in relational database design. It is extensive enough to provide a stimulating exercise, but not so large as to be overwhelming. This case can be utilized for a group project in a database management or database design course. The case is sufficiently detailed to challenge students as they apply the design concepts explained in class to a problem that closely simulates a real-world problem. An associated project can be broken into deliverables, or individual components that cover a single task, to make the project more manageable. Some of the suggested deliverables associated with this project include the design of entity-relationship diagrams, normalization of the database schema, table creation, SQL query design, form and report design, and stored procedure and trigger design. The problem was designed to be extensible. For example, while it does into include credit card processing or selling equipment on consignment, those features can be easily added to make the case more complex. The case can even be extended for use in an analysis and design class, as the services provided by the company are presented as a set of processes that can be easily represented in a data flow diagram.

Many database applications manage information that varies over time, and most of the database schemas forthese applications were designed using one of the several versions of the Entity-Relationship (ER) model.In the research community as well as in industry, it is common knowledge that temporal aspects of dataare pervasive and important to the applications, but are also difficult to capture using

Many CASE tools for information systems engineering can input a conceptual data model of an application and map this to a logical data model for implementation. Typically this involves mapping an ER (Entity-Relationship) conceptual schema to a relational database schema. Since the graphic notation of ER, or the mapping algorithm itself, fails to capture many constraints and derivation rules, these additional features must be coded up manually. Object-Role Modelling (ORM) provides a simpler and richer notation, enabling most of these additional features to be catered for in the mapping. The most well known version of ORM is NIAM, and a number of CASE tools now support this method. Recently, an extended ORM language called FORML has been developed which is even more expressive, and a complete mapping algorithm has been developed and automated. This paper provides an overview of the mapping algorithm and the use of role-graphs for automation.

This research argues that the formative assessment of student coursework in freeform, diagram-based domains can be automated using CBA techniques in a way which is both feasible and useful. Formative assessment is that form of assessment in which the objective is to assist the process of learning undertaken by the student. The primary deliverable associated with formative assessment is feedback. CBA courseware provides facilities to implement the full lifecycle of an exercise through an integrated, online system. This research demonstrates that CBA offers unique

Object-Role Modeling (ORM) is a method for modeling and querying an information system at the conceptual level, and mapping between conceptual and logical (e.g. relational) levels. ORM comes in various flavors, including NIAM (Natural language Information Analysis Method). This article provides an overview of ORM, and notes its advantages over Entity Relationship and traditional Object-Oriented modeling.

In Object Orientation, the Generalisation/Specialisation hierarchy and the Whole/Part relationship are prevalent classification schemes for object types. This paper presents a new classification scheme for object types, called &quot;existence dependency&quot;. Existence dependency captures ...

As technology advances, information in different organizations of Bangladesh can no more be maintained manually. There is a growing need for the information to become computerized so that it can be suitably stored. This is where databases come into the picture. Databases are convenient storage systems which can store large amounts of data and together with application programs such as interfaces they can aid in faster retrieval of data. An initiative was taken to design a complete database system for a hospital management such as Bangladesh Institute of Research and rehabilitation in Diabetes, Endocrine and Metabolic disorders (BIRDEM) in Dhaka so that its information can be stored, maintained, updated and retrieved conveniently and efficiently. The existing information in BIRDEM is partly computerized via databases only in patients' admissions, doctors' appointments and medical tests and reports sections. A partly slow and tedious manual system still exists in BIRDEM for example, in record of ambulances in service, assigning ward boys and nurses to rooms, the billing process and record of doctors' prescriptions etc. However, this paper outlines one complete database design for the entire BIRDEM hospital in which data maintenance and retrieval are in perfect harmony and speedy. Sample SQL-based queries executed on the designed system are also demonstrated.