scholarly journals Pendekatan Kesamaan Semantik dan Struktur dalam Kasus Penggunaan untuk Mendapatkan Kembali Spesifikasi Kebutuhan Perangkat Lunak

Author(s):  
Ferdika Bagus Permana ◽  
Daniel Oranova Siahaan

Abstrak— Di dalam pengembangan perangkat lunak berskala besar, terdapat jumlah dokumen kebutuhan perangkat lunak yang sangat banyak dalam sekali proses elisitasi yang mungkin dihasilkan untuk domain yang berbeda dari setiap tim pengembang. Dokumen-dokumen ini mungkin digunakan kembali untuk mengurangi biaya dan waktu guna pengembangan perangkat lunak berikutnya. Oleh karena itu dibutuhkan suatu mekanisme untuk mendapatkan dokumen tersebut kembali yang sesuai dengan kebutuhan pengguna secara efektif dan efisien.Makalah ini mengusulkan suatu pendekatan kesamaan semantik dan struktur dalam deskripsi kasus penggunaaan guna mendapatkan kembali dokumen spesifikasi kebutuhan perangkat lunak. Dari kasus penggunaan yang didapatkan kembali tersebut kemudian dibuat suatu urutan atau ranking kesamaan kasus penggunaan berdasar suatu threshold yang telah didapatkan berdasar nilai kesepakatan tertinggi dengan pakar pada proses pengujian.Pendekatan menggunakan kesamaan semantik pada kata dan kalimat ini merupakan pendekatan yang diajukan sebagai pengganti dari pendekatan sebelumnya yaitu menggunakan term frequency dan keyword atau kata kunci. Metode ini diujicobakan pada percobaan dengan menggunakan 20 kueri deskripsi kasus penggunaan. Tiga skenario yang berbeda disusun untuk menginvestigasi nilai threshold yang ideal, mengetahui perbedaan hasil atau result set dengan pendekatan sebelumnya dan untuk mengetahui efek kombinasi struktur deskripsi kasus penggunaan pada masukan kueri terhadap hasil kueri yang didapatkan. Kata Kunci—Temu Kembali Kasus Penggunaan, Kesamaan Semantik, Sistem Temu Kembali InformasiAbstract— In software industry, there are tremendous number of software requirements documents in effect of large scale of software development. These collections of software requirements documents can be reused in order to cut off the development time and reduce the cost. There is a need to retrieve one or more of those documents which is suitable with the user’s specifications for the new software development. So, if we can retrieve many similar software requirements to a new project, development process will be less costly and less error because the retrieved software requirements can be tailored to the new case with fewer modifications. This paper presents a methodology to retrieve software requirements documents using structured base of use case description semantic similarity computation. Each element of query use case description will be calculated with the use case description in the collections or repository. The semantic similarity score is used to rank the use case in the collections and to retrieve the requirement documents to be used in the new software project development. We introduce a semantic similarity computation approach as a substitute of term frequency and keyword approach. We validate the usefulness of our method through the experiment using 20 cases. Three experiment scenarios are presented to investigate the ideal threshold value, the retrieval result differences with previous approach and to find out the effect of various combinations of structural query to the retrieval result.Keywords— Use Case Retrieval, Semantic Similarity, Information Retrieval 

2021 ◽  
Vol 2021 ◽  
pp. 1-14
Author(s):  
Yanqing Cui ◽  
Islam Zada ◽  
Sara Shahzad ◽  
Shah Nazir ◽  
Shafi Ullah Khan ◽  
...  

Flexibility and change adoption are key attributes for service-oriented architecture (SOA) and agile software development processes. Although the notion of agility is quite visible on both sides, still the integration of the two diverse concepts (architectural framework and development process) should be well thought of before employing them for a software development project. For this purpose, this study is designed to analyze the two diverse software architectural framework and development approaches, that is, SOA and Scrum process model, respectively, and their integrated environment in software project development setup perspective for Industrial Internet of Things (IIoT). This study also analyzes commonalities among Scrum process model and SOA architectural framework to identify compatibility between Scrum and SOA so that the Scrum process can be constructively used for SOA based projects. This study also examines the proper design and setup of Scrum process suitable for large-scale SOA based projects. For this purpose, an SOA based research and development project is selected as a case study using Scrum as the software development process. The project development and deployment perspective include eight core modules that constitute the overall project framework.


2020 ◽  
Author(s):  
Remo De Oliveira Gresta ◽  
Elder Cirilo

Identifiers are one of the most important sources of domain information in software development. Therefore, it is recognized that the proper use of names directly impacts the code's comprehensibility, maintainability, and quality. Our goal in this work is to expand the current knowledge about names by considering not only their quality but also their contextual similarity. To achieve that, we extracted names of four large scale open-source projects written in Java. Then, we computed the semantic similarity between classes and their attributes/variables using Fasttext, an word embedding algorithm. As a result, we could observe that source code, in general, preserve an acceptable level of contextual similarity, developers avoid to use names out of the default dictionary (e.g., domain), and files with more changes and maintained by distinct contributors tend to have better a contextual similarity.


Author(s):  
Deokyoon Ko ◽  
Sooyong Park ◽  
Yourim Kim ◽  
Soojin Park ◽  
Suntae Kim

Completeness in software requirements specification is one of the key factors for successful software development. For specifying software requirements, scenario-based approach is broadly used, comprising a basic flow regarding the successful use of the system, and alternative flows describing abnormal or less frequent interactions of the system. However, alternative flows tend to be frequently missed in many cases, because of the relative lower significance rather than the basic flow, which eventually have an influence on achieving the completeness of software requirements. In order to address the issue, we propose an approach for automatically recommending alternative flows from a basic flow by extracting the essential use case patterns based on the occurrence patterns of the agents and measuring the verb similarity between the main verbs of each scenario. In order to validate our approach, we apply it to three industrial case studies, and show comprehensiveness of the suggested alternative flows and synergic effectiveness for inexperienced developers.


1992 ◽  
Vol 71 (6) ◽  
pp. 2-11 ◽  
Author(s):  
Stacey J. Gelman ◽  
Fred M. Lax ◽  
Joseph F. Maranzano

Sign in / Sign up

Export Citation Format

Share Document