Good Database Design Research Articles

DESIGN OF CASH SALES ACCOUNTING INFORMATION SYSTEM USING RESOURCE EVENT AGENT MODEL AS TOOL IN EDDY MOTOR OFFICIAL WORKSHOP

The role of information systems for accounting is very large because it changes from manual recording to computerized records, so the need for a good database design is essential. A database that meets the normalization rules is needed to support a computerized Accounting Information System (AIS). The Entity Relationship Model (E-R Model) is commonly used to design databases. However, drawing diagrams’ rules are unclear, making it difficult for the data designer to form a database that meets the normalization rules. The REA model is a development of the E-R Model. The REA model was first conceptualized as a framework for building accounting systems in a shared data environment both within companies and between companies. The core feature of the REA model is an object pattern consisting of two mirror images representing the semantics of a business process's input and output components (give-to-get), making it easier to build a data model.

Perancangan Basis Data Menggunakan Normalisasi Tabel Pada Perusahaan Dagang Barokah Abadi

Many human activities are related to information systems. Not only in developed countries, in Indonesia, information systems have been widely applied everywhere, such as in offices, supermarkets, airports, and even at home when users interact with the internet. Increased company operations in business activities can not be separated from information technology. The use of information technology is one of the effective steps in data processing, as well as business transactions using increasingly sophisticated computer equipment. A good database design plays a very important role in the performance and smooth running of an agency. So, in this research, a database design will be carried out with table normalization using MySQL at the Barokah Abadi trading company. This research also designs using entity relationship diagram (ERD).

A Low End Case Tool Synthesizing 3NF Relations Using Bernstein’s Algorithm

Database design is considered good if there are minimum redundancies, no inconsistencies and no anomalies. The quality of a relation schema can be measured using formal and informal approaches. Informal approaches are the basic guidelines for a good database design where as the formal approach for measuring the quality of a relational schema uses the concept of normal forms. The two approaches for designing the database are decomposition approach and synthesis approach. The decomposition approach is time consuming and lengthy where as synthesis approach uses the Bernstein algorithm to convert a relation directly into 3NF. The tool being designed uses synthesis approach and also generates DDL statements for entire database. Students generally find normalization a theoretical concept so a tool has been developed to automate the process of normalization and use it as an teaching aid to enhance their expertise in normalization.

Designing Graph Database for Managing Lecturers Scientific Publications Using Neo4j

This study aimed to implement a database design to manage lecturers’ scientific publications using a graph database. Data of lecturers' scientific publications are very important to be managed properly. These data are much needed as the requirement of university accreditation, university clustering, and proposal of lecturers’ functional positions. The increasing number of data certainly requires a good database design and one of the alternative databases is a graph database which is a model of a NoSQL database. This study was conducted in several stages: data collection and analysis, conceptual level database design, logical level database design, and physical level database design. This study developed a graph database design that stored various data about lecturers' scientific publications using Neo4j.

PERANCANGAN DESAIN BASIS DATA SISTEM INFORMASI GEOGRAFIS TANAH PENDUDUK DENGAN MENERAPKAN MODEL DATA RELASIONAL ( STUDI KASUS : DESA TUMBANG MANTUHE KABUPATEN GUNUNG MAS PROVINSI KALIMANTAN TENGAH )

Database design is a data design process that is used to support the operational activities and goals of organizations and agencies. The use of databases on the geographic information system of residents' lands makes it possible to store, change, and display all data quickly and easily. One of the factors that become a problem in database design is the point of view of seeing data that varies between designers, programmers, and end-users. Therefore we need a methodology in good database design by applying procedures, techniques, tools, and documentation. The method used in this study used the Research and Development (R&D) method, while the database design method used the Database Life Cycle (DBLC) method. The research variables were database design for the geographic information system of resident land with a relational data model. Research aspects include conceptual design, logical design, and physical design. The final result of this research is to produce 10 types of conceptual entities, produce a relationship diagram of the ten logical entities, and produce a physical design consisting of user_admin, user_pengguna, data_desa, data_kecamatan, data_kabupaten, jenis_tanah, data_penduduk, data_buku_c, data_mutasi, and data_sppt tables.

Perancangan Basis Data Sistem Informasi Penjualan Barang (Studi Kasus: Minimarket “ABC” Sidareja)

Data processing to produce a computerized information is a tool that needed at this time in various types of business because the information capable presented within quickly and accurately time. Information which capable of quickly and accurately presented can produce quickly and effective decision but the database design that applied in a database management system is no less important Good database design will facilitate the implementation of aplications and optimize the performance of the database manajemen system itself.

Data Modeling Guidelines for NoSQL Document-Store Databases

Good database design is key to high data avail-ability and consistency in traditional databases, and numerous techniques exist to abet designers in modeling schemas appropri-ately. These schemas are strictly enforced by traditional database engines. However, with the emergence of schema-free databases (NoSQL) coupled with voluminous and highly diversified datasets (big data), such aid becomes even more important as schemas in NoSQL are enforced by application developers, which requires a high level of competence. Precisely, existing modeling techniques and guides used in traditional databases are insufficient for big-data storage settings. As a synthesis, new modeling guidelines for NoSQL document-store databases are posed. These guidelines cut across both logical and physical stages of database designs. Each is developed based on solid empirical insights, yet they are prepared to be intuitive to developers and practitioners. To realize this goal, we employ an exploratory approach to the investigation of techniques, empirical methods and expert consultations. We analyze how industry experts prioritize requirements and analyze the relationships between datasets on the one hand and error prospects and awareness on the other hand. Few proprietary guidelines were extracted from a heuristic evaluation of 5 NoSQL databases. In this regard, the proposed guidelines have great potential to function as an imperative instrument of knowledge transfer from academia to NoSQL database modeling practices.

An Ameliorated Methodology to Abstract Object Oriented Features from Programming System

In software testing through reverse engineering, the programming semiotics are to be transformed to Unified Modeling Language (UML) semiotics. This process needs the abstraction of UML syntactics, semantics from the programming system. As a preamble, this paper attempts to develop an automated methodology to abstract object oriented technology (OOT) components required for the class diagram from the programming system to be tested for its correctness & completeness. The methodology comprises of initial classing & slicing the programming system on the referenced attributes of the entry with no defined attributes and then using the sole referenced entry and sole defined entry on these sliced programming units the candidate key/s are identified which are used to find individual object structure of the class in our classing technique. The programming system is sliced based on individual class structure and then these slices are used to obtain the object methods through whose nature of the parameters we identify the interrelationship between the classes and their types. The intermediate clairvoyant study of parameter indicates the visibility of the object methods. This paper contains the detailed procedure for each method of our automated methodology. Therefore, their correctness and completeness is self evident. The proposed procedures are based on sound logical positivism and implicitly incorporate good database design and good software engineering principles. This paper reengineers the programming system into various appropriate UML design diagrams so as to reduce the enormity of the syntactics and semantics of programming language into limited syntactics and semantics. This enables to develop the correct and complete software testing methodology.

Automating the Lower and Higher Normal Form Process for the Database Systems

is an important technique for the analysis of relational databases. It aims to create a set of relational tables with minimum data redundancy that preserve consistency and facilitate correct insertion, deletion, and modification. It is very much time consuming to do this data analysis manually. Thus in this paper, a system is proposed which aims to automate the most complex phase of the database design normalization. It will help to achieve a good database design and eliminate the drawbacks of manual normalization process. This system is suitable to eliminate redundancy and inconsistent dependency automatically. It aims to handle the normalization process up to fifth normal. This includes creating tables and establishing relationships between those tables by using their general definitions in a step-by-step feature on the set of functional dependencies to remove redundant data. Then this system is tested on many examples with multiple candidate keys taken from different sources.

Gamified Approach to Database Normalization

This paper explores how gamification can be applied in learning the normalization concepts in database. Modeling the concept with game challenges improves the learning. The model consists of different levels; each level corresponding to a normal form. The levels are further divided into stages. On crossing each stage, the student (player) would get points depending on the difficulty level. The gamification provides positive effect; however, the effects are greatly dependent on the context in which the gamification is being implemented, as well as on the users using it. A good database design depends on tools required to minimize redundancy and anomalies, preserve known functional dependencies, prevent spurious information from emerging, and identifying keys. This proposed model will make learning normalization more interactive and easier. General Terms Database Normalization, Gamification in education, Virtual Learning Environments, game mechanic

Neonatal Informatics—Dream of a Paperless NICU: Part Five: Putting “IT” All Together

The promise of computer-assisted neonatal intensive care unit (NICU) medical management is an intellectually global challenge. In early 2009, President Obama presented a “carrot and stick” plan to accelerate use of electronic health records. Financial incentives are offered to early adopters who meaningfully use certified systems; penalties begin in 2015 for those who do not. NICU critical care environments are extremely difficult to computerize because clinical data are time-dependent and highly variable, use repeated measures of many different elements, and run in real-time. Effective clinical computerization requires translation of complex human thinking models into software bits and bytes. All efforts require a logical, stepwise approach to designing effective databases and systems, and no existing system is currently adequate. Creating meaningful computerization for a busy NICU remains an ongoing challenge. On a daily basis, bedside visit and other care-related notes that outline the patient's condition, medications, treatments, nutrition, new problems, care being provided, plans, and family updates must be generated by physicians or neonatal nurse practitioners (NNPs). Clinical data management in NICUs is currently a “mixed model.” Real-time information management by typing is extremely difficult for hands-on critical caregivers, both in paper records and in computer systems. Workarounds involving paper remain the most common current practice in many institutions (including the scrub pants’ notational workaround). Medicolegal and service billing rules require documentation, and hundreds of different approaches are used, none of which is “certified.” Vendors’ old databases and newer databases designed by nonengineering individuals for clinical documentation tend to have significant technical problems that limit usability. In the future, good database design using modern techniques and technology should improve the situation. Direct download from devices and laboratories to local real-time systems is on the horizon, as is voice recognition for neonatal applications. However, for this year and through 2011, NICUs are not on the radar. Industry and political focus remains on administrative and population “quality management” functionality, now known as “meaningful use.” Emerging drafts of criteria for 2011 incentive payments formally excluded all hospitalists and infants younger than age 2 years from eligibility. Head circumference, respiratory rate, and temperature are not official parts of the vital signs specifications criteria for testing. The dream of a paperless NICU remains only a dream.

The existence condition of γ-acyclic database schemes with MVDs constraints

It is very important to use database technology for a large-scale system such as ERP and MIS. A good database design may improve the performance of the system. Some researches show that a γ-acyclic...

Implementing The Information Processes Underlying The Sales/Collection Cycle Using Access

The objective of this paper is to provide the reader with some exposure as to how accounting information is recorded and processed when a strict relational database approach is implemented. The application described is from the sales/collection cycle and it should provide the information customer with a meaningful Access database exercise that will allow the user to implement the concepts set forth in good database design, as well as the event-driven approach to business technology solutions. The text of this article is excerpted in the form of a student exercise and is included as an Appendix, which can be used as an assignment by the AIS professor.

Modeling security-relevant data semantics

The use of an extended data model which represents both integrity and secrecy aspects of data is demonstrated. This Semantic Data Model for Security (SDMS) provides a technique that assists domain experts, security officers, and database designers in first understanding their security requirements, and then translating them into a good database design. Identifying security requirements at this semantic level provides the basis for analyzing the security requirements and the database design for inference and signaling vulnerabilities. Another contribution is a comprehensive taxonomy of security-relevant data semantics that must be captured and understood to implement a multilevel secure automated information system.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">&gt;</ETX>