Daniel Siahaan

Dr. Daniel Siahaan

orcid

Research Focus & Metrics

Academic Career Length

14Years (2013-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
2 April 2021 in IEEE Access
Verified
Journal Article
Open access
Indra Kharisma RaharjanaIndra Kharisma Raharjana
Indra Kharisma Raharjana
DSDaniel Siahaan
Daniel Siahaan
CFChastine Fatichah
Chastine Fatichah
Context: User stories have been widely accepted as artifacts to capture the user requirements in agile software development. They are short pieces of texts in a semi-structured format that express requirements. Natural language processing (NLP) techniques offer a potential advantage in user story applications. Objective: Conduct a systematic literature review to capture the current state-of-the-art of NLP research on user stories. Method: The search strategy is used to obtain relevant papers from SCOPUS, ScienceDirect, IEEE Xplore, ACM Digital Library, SpringerLink, and Google Scholar. Inclusion and exclusion criteria are applied to filter the search results. We also use the forward and backward snowballing techniques to obtain more comprehensive results. Results: The search results identified 718 papers published between January 2009 to December 2020. After applying the inclusion/exclusion criteria and the snowballing technique, we identified 38 primary studies that discuss NLP techniques in user stories. Most studies used NLP techniques to extract aspects of who, what, and why from user stories. The purpose of NLP studies in user stories is broad, ranging from discovering defects, generating software artifacts, identifying the key abstraction of user stories, and tracing links between model and user stories. Conclusion: NLP can help system analysts manage user stories. Implementing NLP in user stories has many opportunities and challenges. Considering the exploration of NLP techniques and rigorous evaluation methods is required to obtain quality research. As with NLP research in general, the ability to understand a sentence’s context continues to be a challenge.

13 July 2020 in Lontar Komputer : Jurnal Ilmiah Teknologi Informasi
Verified
Journal Article
Open access
PDF file
MAMohammad Nazir Arifin
Mohammad Nazir Arifin
DSDaniel Siahaan
Daniel Siahaan
Reusing software has several benefits ranging from reducing cost and risk, accelerating development, and its primary purposes are improving software quality. In the early stage of software development, reusing existing software artifacts may increase the benefit of reusing software because it uses mature artifacts from previous artifacts. One of software artifacts is diagram, and in order to assist the reusing diagram is to find the level of similarity of diagrams. This paper proposes a method for measuring the similarity of the use case diagram using structural and semantic aspects. For structural similarity measurement, Graph Edit Distance is used by transforming each factor and use case into a graph, while for semantic similarity measurement, WordNet, WuPalmer,and Levenshtein were used. The experimentation was conducted on ten datasets from variousprojects. The results of the method were compared with the results of assessments from experts.The measurement of agreement between experts and method was done by using Gwet’s AC1 andPearson correlation coefficient. Measurement results with Gwet’s AC1 diagram similarity are 0,60,which were categorized as “moderate" agreement and the result of measurement with Pearsonis 0.506 which means there is a significant correlation between experts and methods. The resultshowed that the proposed method can be used to find the similarity of the diagram, so finding andreuse of the diagram as a software component can be optimized.

1 July 2019
Verified
Conference Paper
Closed access
Indra Kharisma RaharjanaIndra Kharisma Raharjana
Indra Kharisma Raharjana
DSDaniel Siahaan
Daniel Siahaan
CFChastine Fatichah
Chastine Fatichah
To specify good requirements, system analysts need to understand the domain knowledge of the system. There are several techniques in requirements elicitation to improve domain knowledge understanding, such as user interviews, questioners, document analysis, and brainstorming. Most of these techniques require profound stakeholder involvement. However, not all software projects can do this task due to limited time or availability of stakeholders. In agile software development, the user story is the de facto standard used for capturing and writing functional requirements. The user story is an appropriate format and easy to understand for writing the results of requirements elicitation. This study purposes a conceptual model to extract user story from online news for improving domain knowledge understanding. The information in the online news contained lesson learned related to certain events. This information may improve the functionality of the software products. The user story consists of three aspects, namely: who, what, and why. Aspect of who represents the role or user, aspect of what shows the purpose or feature, while the aspect of why explains the reason. This format can summarize the lessons learned in the news. Our experimental results indicate that this conceptual model can extract user story from online news. The model manages to extract 105 user stories from 92 aspects of what/why candidate and 109 aspects of who candidate.

10 March 2023 in Information and Software Technology
Verified
Journal Article
Closed access
DSDaniel Siahaan
Daniel Siahaan
Indra Kharisma RaharjanaIndra Kharisma Raharjana
Indra Kharisma Raharjana
CFChastine Fatichah
Chastine Fatichah


15 May 2021 in Register: Jurnal Ilmiah Teknologi Sistem Informasi
Verified
Journal Article
Open access
PDF file
ETEvi Triandini
Evi Triandini
RFReza Fauzan
Reza Fauzan
DSDaniel Siahaan
Daniel Siahaan
SRSiti Rochimah
Siti Rochimah
ISI Gede Suardika
I Gede Suardika
DKDevi Karolita
Devi Karolita
Every piece of software uses a model to derive its operational, auxiliary, and functional procedures. Unified Modeling Language (UML) is a standard displaying language for determining, recording, and building a software product. Several algorithms have been used by researchers to measure similarities between UML artifacts. However, there no literature studies have considered measurements of UML diagram similarities. This paper presents the results of a systematic literature review concerning similarity measurements between the UML diagrams of different software products. The study reviews and identifies similarity measurements of UML artifacts, with class diagram, sequence diagram, statechart diagram, and use case diagram being UML diagrams that are widely used as research objects for measuring similarity. Measuring similarity enables resolution of the problem domains of software reuse, similarity measurement, and clone detection. The instruments used to measure similarity are semantic and structural similarity. The findings indicate opportunities for future research regarding calculating other UML diagrams, compiling calculation information for each diagram, adapting semantic and structural similarity calculation methods, determining the best weight for each item in the diagram, testing novel proposed methods, and building or finding good datasets for use as testing material.