Fully Communication Oriented Information Modeling On SME Information Systems Development
Ela Nadila, Kemas Muslim Lhaksmana*, Seno Adi Putra
1School of Computing, Informatics Study Program, Telkom University, Bandung, Indonesia Email: 1[email protected], 2,*[email protected],
Correspondence Author Email: [email protected]
Abstract−Information modeling a very important role in the development of information systems today. Information modeling is an activity to create a conceptual model that includes all significant information in business processes. Using information modeling, a machine is needed for implementation, and redundancy and anomaly problems are also common in databases. This problem arises when the database is not normalized. To solve the problem, this research will analyze the SME information system using the Fully Communication Oriented Information Modeling (FCO-IM) method and compare it with the method without FCO-IM made by 12 designers. The results of the analysis, information modeling using FCO-IM method can produce a relational data schema that already meets 3NF normalization and is suitable for implementation in SME information system development so that it can be used as an option in data modeling and can avoid data redundancy problems.
Keywords: Information System; Information Modeling; FCO-IM; Redundancy; SME.
1. INTRODUCTION
In the development of information systems today, information plays an important role for companies to compete in the business world [1]. Information system is an organized study used by people, complementary networks, hardware and software to collect, filter, process and disseminate information within an organization [2]. Just like a system, an information system has users who record, maintain, and describe information. But both the provider and the user need a machine for their implementation. Information systems should be modeled first to know the flow of information clearly. Information modeling is an activity to create a conceptual model that captures all significant information in business processes [3].
In terms of its use, apart from the need for a machine to implement it, redundancy problems also often occur in databases [4]. Data redundancy is storing the same data repeatedly in several files, therefore similar data when stored causes more than one location. Redundancy causes problems with changing data, and there is a waste of data memory which can also cause data to be inconsistent, which means that similar records have different data [5]. Redundancy can also result in additional costs for higher access [6]. This problem arises when the database is not normalized. Therefore, it is concluded that both for the current data quality and data storage efficiency and for future developments, it is necessary to redesign the data model with an emphasis on normalization [7].
One method to perform information modeling is Fully Communication Oriented Information Modeling (FCO-IM). Data modeling using the FCO-IM method can produce a relational data schema that already meets 3NF normalization to be used as an alternative in data modeling. Thus avoiding data redundancy problems and guaranteeing data integrity without the need to know deep relational concepts and normalization concepts [8].
SME Information System is a web-based marketplace that is engaged in selling basic necessities (such as rice, eggs, sugar, etc.) to improve the welfare of rural communities through trade routes. Therefore, this study models the information contained in the SME information system using the FCO-IM method, then compares it with the results of information modeling without FCO-IM. After that, an analysis of the best results will be carried out. data model based on information obtained from SME. The results of the appropriate analysis will be implemented into the SME information system application database.
2. RESEARCH METHODOLOGY
2.1 Research Stages
The flow of the system built is shown in Figure 1. The method used in this study is the Fully Communication Oriented Information Modeling (FCO-IM) method. There are several stages in conducting research, as listed below:
Figure 1. System Flow Diagram
At this stage of the research, the first step is to collect data from SME users, the next step is to apply the FCO-IM method using Casetalk tools. After getting the results of the relational data model using the FCO-IM method, then testing was carried out on the programmers/designers to describe the relational data model without FCO-IM. The next stage is to perform a comparative analysis of the two results of the relational data model, which is then implemented into software, namely creating a database on the SME information system application. And the last step is to compare which results are suitable for use in the software.
2.2 Case Study
The marketplace is an intermediary between sellers and buyers in cyberspace. The marketplace site acts as a third party in online transactions by providing a place to sell. In the case study above, it is expected that make a database design using data relational model with the following rules:
a. There are 2 users, namely the seller and the buyer b. Each user can create his shop or just search for goods c. Items are grouped into stores
d. In order to sell something, the user needs to create his shop first e. There are product categories
f. Item stock will decrease according to the number of items purchased g. Sellers, buyers ,and products can be identified with different id (unique) h. Payments are made manually, and the seller lists the number of accounts only.
2.3 Normalization
The relational data model is said to be good if it has implemented normalization. Normalization can conclude as a data analysis technique that manages data attributes by grouping so that an entity is not redundant, stable, and flexible. Normalization is carried out as a test in the relational data model to determine whether the relationship is good. That is, insert, update, and delete processes can be performed on one or more attributes without affecting the integrity of the data in the relation. The normalization process for tables in the database can be carried out in several stages of normalization, but this study only describes three standard forms, including:
a. First Normal Form (1NF): There are no repeating and multi-valued attribute, and the primary key for the table or relation has been defined.
b. Second Normal Form (2NF): Meets the 1NF criteria, and here is no partial functional dependency, meaning that non-key attributes are entirely dependent on the primary key.
c. Third Normal Form (3NF): Meets the 2NF criteria, and non-key attributes must not have dependencies transitive function to other non-key attributes. All non-key attributes in relation only have a functional dependence on the primary key in that relation [12].
According to Turnip, Togu Novriansyah stated that a good data model must meet the third normal form so as to maintain data integrity and redundancy [8].
2.4 Fully Communication Oriented Information Modeling (FCO-IM)
FCO-IM is a powerful technique for modeling aspects of conceptual models based on how to communicate information with domain experts by the desired facts of the system to be developed [13]. FCO-IM does not model the structure of the system being developed but models the communication of information about the system to be developed. FCO-IM models information based on facts that are communicated so that it can be displayed through the ER. The model can be automatically transformed into an ERM (Entity-Relationship Model), UML, relational or dimensional model using FCO-IM Bridgetools. The tool used to model information using the FCO-IM method is CaseTalk Educational Version 10.0 [8].
The distinguishing feature of FCO-IM is that it models communications about a particular Universe of Discourse (UoD) completely and exclusively, namely: it does not model the UoD itself, but rather the facts that users exchange when they communicate about the UoD. Therefore, FCO-IM is a member of the family of information modeling techniques known as Fact-Oriented Modeling (FOM), as are Object Relational Mapping (ORM), model set predicators (PSM), and Nijsen Information Analysis Method (NIAM). Fact-oriented modeling is sometimes also indicated as fact-based modeling [14]. The following are the advantages of FCO-IM compared to other information modeling methods:
a. The intensity of user participation makes for good validation.
b. 100% produce a better model design.
c. Can prevent maintenance costs because the documentation is fully integrated.
d. Improve system development towards the realization of a better system.
e. In modeling, its realization and design can reduce time-to-market [3].
2.5 FCO-IM Model with Modeling Tool (CaseTalk)
CaseTalk is a modeling tool based on the FCO-IM method. The following is an explanation of using CaseTalk.
a. Verbalization
Verbalization is the stage for compiling the expression of facts based on information sources that have been defined through analysis.
Tabel 1. Result Verbalization
User 501 is user id Product 306 price is IDR 35000
User 501 is Ela Nadila Product 304 has a description Unique, beautiful, cute, makes the house fresh, wood frame material guaranteed to last long.
User 501 email is [email protected] Product 305 stock is 5
User 501 is located in Garut User 501 orders product 306
User 501 cellphone number is 089602590333 User 501 made a payment of IDR 135000 User 501 has a shop called Herbal Sari Sehat The payment status on user 501 received Store 21 is located in Tegalwaru Street, Tegal Waru,
Ciampea District, Bogor, West Java 16620
User 501 reviews 305 products are reasonable, affordable prices
Store 21 is Herbal Sari Sehat There is a transaction with invoice number 23144
Store 21 cellphone number is 082113114115 Product 501 is categorized as SME Agriculture Store 21 has a description Herbal Sari Sehat is the latest
breakthrough product in the traditional medicine market
User 501 added product 305 to the cart Product 306 is Aloe Vera Drink User 501 adds 10 product to cart b. Classification and Qualification
At this stage, those who will use the FCO-IM method must have the ability to group or categorize the verbalization results into classes. The case studies can be classified into seven classes/elementary fact types:
Users, Transactions, Products, Product Transactions, Categories, Stores, and Carts. The final results of this stage will then be stored in a repository (Information Grammar / IG), and the parts of the sentence are classified in the form of fact types (roles), object types, and label types. This is the result of the classification and qualification of the all table:
Tabel 2. Result Classification and Qualification
Label Object
users
User 501 is user id users:O1 user_id
F4: User <user_id> is user id O1: users <user_id>
User 501 is Ela Nadila users:O1
F1: User <user_id> is <name>
O1: users <user_id>
Label Object user_id name
User 501 email is [email protected] users:O1
user_id email
O2: User <user_id> email is <email>
O1: users <user_id>
User 501 is located in Garut users:O1
user_id address
F2: User <user_id> is located in <address>
O1: users <user_id>
User 501 cellphone number is 089602590333 users:O1
user_id phone
F3: User <user_id> cellphone number is <phone>
O1: users <user_id>
User 501 has a shop called Herbal Sari Sehat users:O1 stores:O3
user_id store_name
F16:User <user_id> has a shop called <store_name>
O1: users <user_id>
O3: stores <store_name>
stores
Store 21 is store id stores:O3 store_id
O3: Store <store_id> is store id O3: stores <store_id>
Store 21 is located in Tegalwaru Street, Tegal Waru, adfe Ciampea District, Bogor, West
dd Java 16620 stores:O3
store_id store_address
O4: Store <store_id> is located in <store_address>
O3: stores <store_id>
Store 21 is Herbal Sari Sehat stores:O3
store_id store_name
F5: Store <store_id> is <store_name>
O3: stores <store_id>
Store 21 cellphone number is 082113114115 stores:O3
store_id phone_store
F6: Store <store_id> cellphone number is
<phone_store>
O3: stores <store_id>
Store 21 has a description Herbal Sari Sehat is the fd latest breakthrough product gf in the traditional medicine market stores:O3
store_id description
F7: Store <store_id> has a description <description>
O3: stores <store_id>
products
Product 306 is product id products:O5
product_id
F4: Product <product_id> is product id O5: products <product_id>
Product 306 is Aloe Vera Drink products:O5
product_id name_product
O5: Product <product_id> is <name_product>
O5: products <product_id>
Product 306 price is IDR 35000 products:O5
product_id price
F8: Product <product_id> price is <price>
O5: products <product_id>
Product 304 has a description Unique, beautiful, cute, g makes the house fresh.
products:O5
product_id description_product
F9: Product <product_id> has a description <
description_product >
O5: products <product_id>
Product 305 stock is 5 products:O5 product_id stock
F20: Product <product_id> stock is <stock>
O5: products <product_id>
transactions
User 501 orders product 306
users:O1 products:O5
user_id product_id
O7: User <user_id> orders product <product_id>
O1: users <user_id>
O5: products <product_id>
User 501 made a payment of IDR 135000 users:O1 transaction:O7
user_id payment_approve
F13: User <user_id> made a payment of
<payment_approve>
O1: users <user_id>
O7:transactions<payment_approve>
The payment status on user 501 received
users:O1 transaction:O7
F14: The payment status on user <user_id> <status>
O1: users <user_id>
Label Object user_id status O7 : transactions <status>
There is a transaction with invoice number 23144
transaction:O7
invoice
F17: There is a transaction with invoice number
<invoice>
O7 : transactions <invoice>
product_transactions
User 501 reviews 305 products are reasonable, affordable prices users:O1 products:O5
user_id product_id review
O9: User <user_id> reviews <product_id>products are <review>
O1: users <user_id>
O5: products <product_id>
LABEL OBJECT
categories
Product 501 is categorized as SME Agriculture users:O1 categories:O6
user_id category_name
O6: Product <product_id> is categorized as
<category_name>
O1: users <user_id>
O6 : categories <category_name>
cart
User 501 added product 305 to the cart users:O1 products:O5
user_id product_id
O8: User <user_id> added product <product_id>to the cart
O1: users <user_id>
O5: products <product_id>
User 501 adds 10 product to cart users:O1 cart:O8
user_id quantity
F15:User <user_id> adds <quantity> product to cart O1: users <user_id>
O8 : cart <quantity>
c. Information Grammar Diagram (IGD)
After the classification and qualification stages are stored in the repository, the information grammar diagram can be displayed. Figure 2 shows the results of the IGD for each fact type and the resulting object.
Figure 2. Information Grammar Diagram d. Constraint
The steps for adding constraints can be done with the help already available in the case talk tools on the repository menu, such as adding uniqueness, totality, subset, equality, exclusion, and cardinality constraints.
F8 : "Product <Product : O5> is <product name>."
O5 : 'product <product id>'
UC3 : "Product is uniquely identified by product id."
UC3 is a unique constraint involved in the IG. A uniqueness constraint defines that the values that may be fill in a particular roles must be unique.
e. Information Grammar Diagram (IGD)
GLR is the last step that must do in the FCO-IM method. This stage also uses the transform feature found in the case talk tool. Case talk will perform every algorithm in each GLR process. This stage will change the ER
to a relational scheme. In this case study, the grouping process is carried out on the invoice with the transactions, and in the reducing process, it will be asked to delete the fact type of the invoice. Figure 3 is a form of FCO-IM result data model generated after the IGD transformation process into a relational schema specified in the MYSQL scripting language.
Figure 3. FCO-IM Result Data Model
3. RESULT AND DISCUSSION
The target audience for making relational data tables without FCO-IM is 12 programmers/designers aged between 23-30 years with alumni majoring in informatics. They are considered experienced in creating relational data tables during college and experience at work.
3.1 FCO-IM Result
After carrying out the 5-step modeling flow in the manufacture of FCO-IM with the case talk tool on the SME information system, the results obtained with seven tables with normalization fulfilled is 3NF.
Table 3. FCO-IM Result
Number of Tables List of Tables Normalization
7
users, stores, products, product_transactions, transactions,
carts, categories
3NF
3.2 Without FCO-IM Result
The results carried out by 12 designers resulted in different tables and normalizations. In the results of table 2, there are at least 3 tables with table names users, stores, products, and no one normalization, and a maximum of 16 tables with table names users, buyers, sellers, stores, carts, orders, search, type_of_payment, selling_product, stock, products, categories, order_details, bank, account_number with 2NF normalization.
As explained in chapter 2 on normalization, it is stated that a good data model must meet the third normal form to maintain data integrity and redundancy. The results of the 12 designers still have one designer with 1NF and seven designers with 2NF. This means that the resulting model does not meet the third normalization.
The most dominant designer writes many tables of users such as users, buyers, sellers, even though these tables can combine into one table with user names, and add role attributes that contain roles (buyer, seller). Some designers do not add a primary key to the relational data model created. Then it can be seen in Table 2, number 11, there are profiles and accounts. These tables have the same attribute contents, so only one table needs to be done, both profiles and accounts.
Table 4. Without FCO-IM Result No Number of
Tables List of Tables Normalization
1 3 users, products, sellers 3NF
2 3 users, stores, products 3NF
3 5 users, stores, products, categories, transactions 3NF 4 7 users, stores, products, categories, payments,
orders, buyers 3NF
5 5 buyers, sellers, stores, products, transactions 3NF 6 7 buyers, sellers, stores, products, categories,
orders, cart_items 3NF
No Number of
Tables List of Tables Normalization
7 6 users, stores, products, categories, invoices,
invoice_details 3NF
8 4 users, products, sellers, categories 3NF
9 16
users, buyers, sellers, stores, carts, orders, search, type_of_payment, selling_product, stock, products, categories, order_details, bank,
rekening_number
3NF
10 4 users, stores, transactions, products 3NF
11 10
accounts, stores, products, categories, transactions, profiles, tokens, roles,
transaction_details, account_store
3NF
12 9
users, customers, sellers, bank_accounts, merchants, products, product_categories,
order_items, order
3NF
3.3 Comparison Result FCO-IM and Without FCO-IM
Evaluation of the database model design produced between the two methods by comparing the number of tables, table names, attributes such as a primary key or naming the same attribute with different tables, normalization level, and also implementation on the SME information system marketplace.
This section describes which information modeling is suitable to be implemented into the SME information system based on the same case study, with the FCO-IM method and without the FCO-IM method.
What was done by 12 designers produced different tables, namely there are at least three tables with table names users, stores, products, and a maximum of 16 tables with table names users, buyers, sellers, stores, carts, orders, search, type_of_payment, selling_product, stock, products, categories, order_details, bank, account_number. In addition, what was done by 12 designers, 3 people did not add a primary key to the table, so it was difficult to distinguish one row from another in the table because it was not unique. The lowest level of normalization produced by 12 designers is a relational scheme that does not meet the first normal form because it does not have a primary key, while FCO-IM already meets the third normal form.
After being researched one by one and trying to be implemented into the database, the resulting table from the 12 designers is not suitable to be implemented in the SME information system marketplace because there are tables that are lacking, and some are excess, resulting in redundancy. After being implemented in the database, the results of information modeling using FCO-IM are suitable for use in the SME information system, because it has resulted in 3NF normalization.
4. CONCLUSION
From the results of the comparison that has been done, it can be seen that the table generated using the FCO-IM method is more suitable to be implemented in SME information systems compared to the method without FCO- IM, which 12 designers carried out. The advantage of this research is that by using FCO-IM, normalization is automatic at 3NF. So there is no need to normalize the manual so that there will be no data redundancy.
Meanwhile, if 12 designers carry out the table results without FCO-IM, some still have normalization that has not reached 3NF. The results of the analysis, information modeling using the Fully Communication Information Modeling (FCO-IM) method can produce a relational data schema that already meets 3 NF normalization and is suitable for implementation in SME information system development so that it can be used as an alternative in data modeling and can avoid data redundancy problems.
ACKNOWLEDGMENT
As a student of Information Science, I am deeply indebted to all the instructors who have helped me with immense patience and motivational support. They were the driving force for me in carrying out and finishing this research work. I am also thankful to Telkom University, my campus, for providing a path to pursue my dreams.
Last but not least, I would like to thank my family, whose love and guidance are with me in whatever I pursue.
REFERENCES
[1] Arif, Donny, Nikma Yucha, Setiawan Setiawan, Dian Oktarina, and Varid Martah. "Applications of Goods Mutation Control Form in Accounting Information System: A Case Study in Sumber Indah Perkasa Manufacturing, Indonesia."
Journal of Asian Finance, Economics and Business 7, no. 8 (2020): 419-424.
[2] Gutandjala, Ilona Irena, Anderes Gui, Siti Maryam, and Vini Mariani. "Information System Risk Assessment And Management (Study Case at XYZ University)." In 2019 International Conference on Information Management and Technology (ICIMTech), vol. 1, pp. 602-607. IEEE, 2019.
[3] Sibuea, Rina. "Pemodelan Informasi Dengan Metode Fco-im." Seminar Nasional Informatika (SEMNASIF). Vol. 1.
No. 5. 2015.
[4] DeCastro-García, Noemí, Ángel Luis Muñoz Castañeda, Mario Fernández Rodríguez, and Miguel V. Carriegos. "On detecting and removing superficial redundancy in vector databases." Mathematical Problems in Engineering 2018 (2018).
[5] Prakosa, Herjuna Ardi, Nadya Chitayae, and Abdul Jalil Rozaqi. "Analisis Entri Data Pada Sistem Pengelolaan Gudang Minimarket Berdasarkan Aspek Kualitas Database." E-Jurnal Jusiti: Sistem Informasi dan Teknologi Informasi 8.1 (2019): 57-66.
[6] Suryaningrat, Suryaningrat. "Perancangan Sistem Informasi Inventori Mesin Konstruksi Ringan Berbasis Web." Jurnal Ilmiah Humanika 3, no. 3 (2020): 30-53.
[7] Prehanto, Dedy Rahman, S. Kom, and M. Kom. Buku Ajar Konsep Sistem Informasi. Scopindo Media Pustaka, 2020.
[8] Turnip, Togu Novriansyah. "Pemodelan Data dengan Fully Communication Oriented Information Modeling (FCO-IM) sebagai Solusi Alternatif Menghasilkan Model Data dengan Bentuk Tabel Normal." Jurnal Ilmiah Maksitek 2.2 (2017).
[9] Nurhasan, Yoseph Ismail, Budiman Dabarsyah, and Hanif Fakhrurroja. "Information model design as model-driven for Service Oriented Architecture (SOA) implementation in PK-BLU institution using SOA Ontology: case study: financial administration bureau Padjadjaran University." In International Conference on ICT for Smart Society, pp. 1-9. IEEE, 2013.
[10] De Cat, Broes, Bart Bogaerts, Maurice Bruynooghe, Gerda Janssens, and Marc Denecker. "Predicate logic as a modeling language: the IDP system." In Declarative Logic Programming: Theory, Systems, and Applications, pp. 279- 323. 2018.
[11] Bakema, G. P., O. S. Santoso, B. Sitohang, and F. Nur Azizah. "The Concept of Data Model Patterns Based on Fully Communication Oriented Information Modeling (FCO-IM)." PhD diss., Hogeschool van Arnhem en Nijmegen, 2010.
[12] Bakema, G. P., O. S. Santoso, B. Sitohang, and F. Nur Azizah. "The Concept of Data Model Patterns Based on Fully Communication Oriented Information Modeling (FCO-IM)." PhD diss., Hogeschool van Arnhem en Nijmegen, 2010.
[13] Zygiaris, Sotirios. "DataBase Design." Database Management Systems. Emerald Publishing Limited, 2018.
[14] Zwart, Jan Pieter, Marco Engelbart, and Stijn Hoppenbrouwers. Fact Oriented Modeling with FCO-IM: Capturing Business Semantics in Data Models with Fully Communication Oriented Information Modeling. Technics Publications, 2015.
[15] Bakema, G., J. P. Zwart, and H. Van der Lek. "Fully Communication Oriented Information Modeling (FCO- IM)." HAN University, The Netherlands (2002).
[16] Rafitricia, Anindya Nadhira. "Pembuatan Basis Data Untuk Visualisasi Model 3D Penggunaan Gedung (Studi Kasus:
Gedung Teknik Geomatika, UPMB Dan UPMS Kampus ITS)." PhD diss., Institut Teknologi Sepuluh Nopember, 2016.
[17] Islam, Nur. "Pengertian, Fungsi, Model dan Contoh ERD" [Online] Available at: https://tisucoding.com/contoh-erd/
[Accessed 14 September 2021] 2021.
