Ontology Based Software Design Documentation For Design Reasoning

2019 ◽  
Author(s):  
Dhanushka B. Jayasuriya ◽  
Indika Perera
Keyword(s):  
Software Design ◽  
Design Documentation ◽  
Design Reasoning

scholarly journals Recovering Software Design from Interviews Using the NFR Approach: An Experience Report

2014 ◽  
Vol 2014 ◽  
pp. 1-14
Author(s):  
Nary Subramanian ◽  
Steven Drager ◽  
William McKeever
Keyword(s):  
Air Force ◽  
Software Design ◽  
Experience Report ◽  
Natural Evolution ◽  
Design Engineers ◽  
Us Air Force ◽  
The Us ◽  
Design Documentation ◽  
Actual Design ◽  
The Phoenix

In the US Air Force there exist several systems for which design documentation does not exist. Chief reasons for this lack of system documentation include software having been developed several decades ago, natural evolution of software, and software existing mostly in its binary versions. However, the systems are still being used and the US Air Force would like to know the actual designs for the systems so that they may be reengineered for future requirements. Any knowledge of such systems lies mostly with its users and managers. A project was commissioned to recover designs for such systems based on knowledge of systems obtained from stakeholders by interviewing them. In this paper we describe our application of the NFR Approach, where NFR stands for Nonfunctional Requirements, to recover software design of a middleware system used by the Air Force called the Phoenix system. In our project we interviewed stakeholders of the Phoenix system, applied the NFR Approach to recover design artifacts, and validated the artifacts with the design engineers of the Phoenix system. Our study indicated that there was a high correlation between the recovered design and the actual design of the Phoenix system.

scholarly journals Improving software design reasoning–A reminder card approach

2018 ◽  
Vol 144 ◽  
pp. 22-40 ◽  
Author(s):  
Antony Tang ◽  
Floris Bex ◽  
Courtney Schriek ◽  
Jan Martijn E.M. van der Werf
Keyword(s):  
Software Design ◽  
Design Reasoning

scholarly journals Pengukuran Fungsionalitas Perangkat Lunak Menggunakan Metode Function Point Berdasarkan Dokumentasi Desain

2013 ◽  
Vol 7 (2) ◽  
pp. 111
Author(s):  
Anie Rose Irawati ◽  
Khabib Mustofa
Keyword(s):  
Software Design ◽  
Unified Modeling Language ◽  
Modeling Language ◽  
Use Case ◽  
Size Measurement ◽  
End User ◽  
Unified Modeling ◽  
Functional Size Measurement ◽  
Function Point ◽  
Design Documentation

AbstrakPerkiraan nilai perangkat lunak yang disepakati oleh end user dan tim pengembang harus dinyatakan dalam besaran tertentu, salah satunya adalah dalam u ku ran fungsionalitas (functional size measurement/FSM).Metode Function Point (FP) merupakan salah satu metode yang digunakan untuk mendapatkan ukuran fungsionalitas, pertama kali dikenalkan oleh Allan Albrecht dan kemudian terus dikembangkan sampai saat ini oleh International Function Point User Goup (IFPUG). Tujuan dari pengukuran menggunakan FP adalah untuk mendapatkan ukuran biaya, durasi, dan jumlah sumber daya yang diperlukan oleh sebuah proyek perangkat lunak dan dapat dilakukan pada setiap tahap pengembangan perangkat lunak. Pengukuran FP memerlukan keahlian dalam hal analisis perangkat lunak dan hasil perhitungannya dinyatakan valid jika dilakukan oleh seseorang yang mempunyai sertifikasi FP (certified FP) dari IFPUG.Penelitian ini bertujuan untuk membangun sebuah sistem yang dapat memberikan kemudahan bagi pelaku pengukuran perangkat lunak dalam menganalisis perangkat lunak dengan metode Function Point berdasarkan pada IFPUG CPM 4.3.1.Penelitian ini menghasilkan sistem yang membantu pengguna untuk melakukan analisis FP dengan cepat dan dengan validitas yang tinggi. Sistem yang dibuat mampu menghitung FP sesuai dengan dokumentasi yang dimiliki software dan menggunakan input berupa dokumen XMI yang di-eksport dari Use Case Diagram, Class Diagram dan perpaduan antara Use Case dan Class. Selain itu, penelitian ini menunjukkan pola bahwa semakin lengkap dokumen UML (Unified Modeling Language) yang dimiliki oleh sebuah perangkat lunak maka semakin akurat hasil perhitungan FP yang didapatkan. Kata kunci— Pengukuran perangkat lunak, UML, Function Point, dokumentasi desain perangkat lunak.  AbstractEstimated value of software as agreed by the end user and the developer team should be expressed in a certain magnitude, one of which is the measure of functionality (functional size measurement / FSM).Function Point (FP) Method is one of the methods used to obtain the size of the functionality, first introduced by Allan Albrecht and then further developed by the International Function Point User Goup (IFPUG). FP is a method to get a measure of the cost, duration, and amount of resources required by a software project and can be done at any stage of software development. However, Function Point measurement requires expertise in software analysis and the results of the calculation are valid if done by someone with IFPUG certification.This study realizes a system that is convenient for actors in analyzing software using Function Point method based on IFPUG CPM 4.3.1.The system helps users to perform FP analysis in a faster way and confers accurate results. The system is able to count FP based on software design documentation and uses XMI document exported from use case diagrams, class diagrams, and diagrams illustrating the use cases and classes relationship as an input. The study also indicates that the more complete software UML (Unified Modeling Language) documents, the more accurate the FP calculation results obtained. Keywords— Software measurement, UML, Function Point, software design documentation.

Sign in / Sign up

Export Citation Format

Share Document