Automatic Requirements Engineering Model using Goal-Oriented Modelling with Text Pre-Processing Technique

Delima, Rosa; Wardoyo, Retantyo; Mustofa, Khabib

doi:10.1109/icic54025.2021.9632980

Cited by 5 publications

(5 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Feature model [18], [19]; Pattern-based model [20], [21]; MAPE-K model [22], [23]; Agent / multiagent-based model [24] - [28]; Viewpoint model [29] , [30]; Problem-Based model [31], [32]; Continues Collaborative Model (CCM) [33]; Integrated-Secure SDLC model (IS-SDLC) [34]; Requirements frame model [35]; Grid Model [36]; Probabilistic model checking [37]; BIP (Behavior -Interaction -Priorities) Model [38]; [29], [39] model based testing; [40] model driven approach (MDA); [20] Model Driven Development (MDD); BERT Model [41] - [43]; RE-BERT Model [44]; Object-Role Modelling (ORM) notation [45]; i* model [46], [47]; scenario based modeling [48]; QR (Quality Requirements) Pattern [49] Annotated BPMN Model [50] Specific Method…”

Section: Model-based Approachmentioning

confidence: 99%

“…Matching algorithm [62]; Quantum Algorithm [63]; Fuzzy Logic [64] [65]; PageRank Algorithm [41]; Decision Support [66], [67], [28]; Markov decision [68]; Genetic Algorithm [69], [70]; Horspool's Algorithm [71]; Keyphrase algorithm [72]; Naïve Bayes's Algorithm [73] Specific technique/Tools using tool Nomos and NomosT [74]; Automated Planning Technique [75]; Ethnographical [76]; DT-Golog [68]; 4.…”

Section: Model-based Approachmentioning

confidence: 99%

See 1 more Smart Citation

Automatic Requirements Engineering: Activities, Methods, Tools, and Domains – A Systematic Literature Review

Delima

Mustofa

Sari

2023

J. RESTI (Rekayasa Sist. Teknol. Inf.)

View full text Add to dashboard Cite

Requirements engineering (RE) is an initial activity in the software engineering process that involves many users. The involvement of various users in the RE process raises ambiguity and vagueness in requirements modeling. In addition, traditional RE is a time-consuming activity. Therefore various studies have been conducted to support process automation on RE. This paper conducts a systematic literature review (SLR) to obtain information about RE automation related to RE activities, methods/models, tools, and domains. SLR is done through 5 main stages: definition of research questions, conducting the search, screening for relevant papers, data extraction, mapping, and analysis. The data extraction and mapping are carried out on 155 relevant publications from 2016 to 2022. Based on the results from SLR, around 53% of the research focuses on RE automation in analysis and specifications, 40% focuses on elicitation, validation, and requirements management, and 7% focuses on requirements quality. NLP is the most used method in elicitation and specification, while for analysis, machine learning, NLP, and goal-oriented models are mostly used in automatic RE. Furthermore, many papers use specific models and methods for validation and requirements management. From the domain analysis results, it is obtained that more than half of the papers contribute directly to the RE domain, and some contribute to the development of RE automation in the software application domain.

show abstract

Section: Model-based Approachmentioning

confidence: 99%

Section: Model-based Approachmentioning

confidence: 99%

Automatic Requirements Engineering: Activities, Methods, Tools, and Domains – A Systematic Literature Review

Delima

Mustofa

Sari

2023

J. RESTI (Rekayasa Sist. Teknol. Inf.)

View full text Add to dashboard Cite

show abstract

“…In the previous research, a model was developed to automate the requirements engineering process called AREM (Automatic Requirements Engineering Model). AREM can automate three stages of the RE process, such as analysis, specification, and validation of requirements [3]. For the elicitation stage, AREM can handle the process semi-automatically, where the input process of the requirements data still has to be done by users, such as a systems analyst.…”

Section: Introductionmentioning

confidence: 99%

GoEliTool for Software Requirements Elicitation using Goal-Oriented Approach

Delima

Purwadi

2022

JEPIN

View full text Add to dashboard Cite

Requirements engineering (RE) is an essential initial stage in software engineering. The RE process begins with the elicitation stage. This stage collects all user requirements that must be fulfilled by the system which will be developed. A goal-oriented approach is an effective approach used to automate the RE process. The development of goal-oriented input document standards is one of the important issues that has not been widely studied. Therefore, this study developed a goal-oriented input document standard for the requirements elicitation process. A tool is developed based on the form of the input document that has been generated. The development of standard forms of input documents begins with literature study and data collection, analysis, design of standard forms of documents, tool design, tool development, and testing. At the analysis stage, a logical framework and element structure is formulated in a goal-oriented approach. Furthermore, the standard form of input documents is developed. The standard form of the document becomes a guideline for developing tools to process data requirements from elicitation results. Tool testing is carried out using black-box testing. The test results show that the tool can work according to the planned function. The trial of the use of the tools was carried out using five requirements datasets. The results of testing and using the tool through the requirements dataset show that GoEliTools can be used to record data on the requirements of several users for the development of an information system.

show abstract

“…PENDAHULUAN Dalam rekayasa perangkat lunak, rekayasa kebutuhan/requirements engineering (RE) adalah pekerjaan awal yang sangat penting. Beberapa pekerjaan yang tercakup dalam RE adalah pengumpulan kebutuhan, analisis, permodelan, dan validasi kebutuhan [1] [2]. AREM (Automatic Requirements Engineering Model) merupakan model yang telah dikembangkan untuk otomatis RE.…”

unclassified

“…Pendekatan Goal-Oriented merupakan salah satu pendekatan yang populer untuk rekayasa kebutuhan perangkat lunak [3]. AREM mampu mengotomatisasi proses RE mulai dari elisitasi, analisis, dan validasi kebutuhan [1][4] [5].…”

unclassified

Otomatisasi Pembentukan Class Diagram dengan Pendekatan Metode Pemrosesan Teks dan Algoritma CombineTF

Delima,

Chrismanto

2024

JEPIN

View full text Add to dashboard Cite

Spesifikasi kebutuhan merupakan bagian penting dalam proses rekayasa kebutuhan perangkat lunak. Spesifikasi kebutuhan menjadi penghubung antara system analyst dan programmer yang akan melakukan pengembangan sistem. Proses rekayasa kebutuhan merupakan pekerjaan yang bersifat time consuming dan membutuhkan effort yang besar bagi analis sistem. Pekerjaan analis untuk melakukan rekayasa kebutuhan dapat lebih efisien atau lebih cepat dengan bantuan tool untuk mengotomatisasi proses rekayasa kebutuhan. Pada penelitian ini dilakukan pengembangan spesifikasi kebutuhan berupa class diagram secara otomatis dari data kebutuhan. Penelitian ini bermanfaat untuk membantu analis dalam melakukan spesifikasi kebutuhan. Spesifikasi kebutuhan yang dihasilkan merupakan pengembangan dari Automatic Requirments Engineering Model (AREM). Pembentukan class diagram dilakukan melalui tiga tahapan yaitu pembentukan class diagram dari data kebutuhan, penanganan duplikasi objek pada diagram, dan refinement class diagram. Pembentukan diagram pada tahap pertama dilakukan dengan menggunakan pendekatan pemrosesan teks, sementara itu penanganan duplikasi objek dilakukan menggunakan pendekatan term-frequency (TF) dan gabungan algoritma CombineTF dan Jaro-Winkler. Penelitian ini menggunakan dataset kebutuhan untuk pengembangan sistem informasi koperasi. Penelitian berhasil mengembangkan model untuk otomatisasi pembentukan class diagram. Hasil penelitian menunjukan bahwa penanganan duplikasi objek pada class diagram mampu mengatasi 62,5% duplikasi objek dengan nilai precision 0,94 dan nilai akurasi 0,97 untuk nilai threshold algoritma ≥ 0.8.

show abstract

Automatic Requirements Engineering Model using Goal-Oriented Modelling with Text Pre-Processing Technique

Cited by 5 publications

References 7 publications

Automatic Requirements Engineering: Activities, Methods, Tools, and Domains – A Systematic Literature Review

Automatic Requirements Engineering: Activities, Methods, Tools, and Domains – A Systematic Literature Review

GoEliTool for Software Requirements Elicitation using Goal-Oriented Approach

Otomatisasi Pembentukan Class Diagram dengan Pendekatan Metode Pemrosesan Teks dan Algoritma CombineTF

Contact Info

Product

Resources

About