MODEL REQUIREMENT TRACEABILITY UNTUK METODE PENGEMBANGAN PERANGKAT LUNAK FEATURE DRIVEN DEVELOPMENT (FDD)

AbstractA recent study conducted by the Standish Group in 2012 shows that in the preparation of requirements becomes one of the critical success factors of a software. Requirements traceability is the method used to explore inter-linkages or inter-relations requirement, so that when an error occurs in one or more functions on a software, or changes in the requirements, then it can easily be identified requirements which are problematic. Feature Driven Development (FDD) is one of the Agile method that does not have a fixed rule in the formation of inter-search requirement models and inter-feature. By using grounded theory in research, such as open coding, axial coding, and selective coding, and sorting. The research began with the determination of the review and identification of the problem, collect relevant data, perform data analysis, and the final document the results. Based on the test results, the modeling traceability requirements in the FDD method can assist in tracing linkages, inter-relations requirements as well as inter-feature during software development. And can be used as documentation of a software development work.Keywords : requirement, traceability, relation, Feature Driven Development, and grounded theory.Penelitian terbaru yang dilakukan oleh Standish Group pada tahun 2012 menunjukkan bahwa dalam penyusunan requirements menjadi salah faktor penentu keberhasilan sebuah perangkat lunak. Requirement traceability merupakan metode yang digunakan untuk menelusuri keterkaitan atau interkoneksi antar-requirement, sehingga ketika terjadi kesalahan dalam satu atau lebih fungsi pada sebuah perangkat lunak, atau terjadi perubahan requirement, maka dengan mudah dapat diidentifikasi requirement mana yang bermasalah. Metodologi pengembangan perangkat lunak Feature Driven Development (FDD) merupakan salah satu bagian dari metode Agile dimana pendekatan FDD dilakukan secara adaptif dalam pengembangan sistem. FDD merupakan Agile Method yang belum mempunyai aturan baku dalam pembuatan model penelusuran antar-requirement maupun antar-feature. Requirement pada FDD tidak secara eksplisit dapat digali, dicari, dan diatur. Namun dokumentasi requirement dibutuhkan pada proses pembentukan feature list. Oleh sebab itu dibutuhkan suatu dokumentasi model penelusuran antar requirements. Pembuatan model penelusuran requirement dengan menggunakan metode grounded theory yaitu diantaranya adalah open coding, axial coding, selective coding, dan sorting. Penelitian bermula dengan penentuan bidang kaji dan identifikasi masalah, mengumpulkan data-data terkait, melakukan analisis data, dan terakhir mendokumentasikan hasil. Berdasarkan hasil uji, pembuatan model penelusuran requirement pada metode FDD dapat memudahkan penelusuran jika terjadi kesalahan dalam testing hasil akhir program dan dapat dijadikan sebagai acuan pembuatan fungsi dalam pengembangan proyek selanjutnya.Kata kunci : requirement, penelusuran, keterkaitan, Feature Driven Development, dan grounded theory

Application of Stochastic Reliability Modeling to Waterfall and Feature Driven Development Software Development Lifecycles

There are many techniques for performing software reliability modeling. In the environment of software development some models use the stochastic nature of fault introduction and fault removal to predict reliability. This thesis research analyzes a stochastic approach to software reliability modeling and its performance on two distinct software development lifecycles. The derivation of the model is applied to each lifecycle. Contrasts between the lifecycles are shown. Actual data collected from industry projects illustrate the performance of the model to the lifecycle. Actual software development fault data is used in select phases of each lifecycle for comparisons with the model predicted fault data. Various enhancements to the model are presented and evaluated, including optimization of the parameters based on partial observations

Design and Development of Student Admission System in the State University of Jakarta

Student admission system is a must in every university, and so in the State University of Jakarta. Web applications are more widely used in the development of information systems because of the ease in distributing information to many users. By using the concept of re-used oriented, student admission system built in 2015 is developing by adding, editing, and deleting a requirement based on policy that enforce today. Moreover, adding web service as an intermediary between system and database as an extra feature in new system. The research was conducted using the Feature Driven Development (FDD) which is one of the Agile Method that does not have fixed rule in traceability model between requirement and feature, where this research went through several stages, namely needs to develop an overall model, build a feature list, plan by feature, design and build by feature. This study produces several products, there are Software Requirement Specification (SRS) and system that are built with React-Redux for its front-end and Laravel as its back-end.     Keywords: design and development, requirement, re-used oriented, feature driven development, web servic

PENGEMBANGAN APLIKASI JASA PEMANDU WISATA MENGGUNAKAN METODE FEATURE DRIVEN DEVELOPMENT

Today, technology and tourism are increasingly developing in Indonesia, but there is few information services provide as a reference standard of tourists and guides to obtain guide service information. Usually tourists look for guide service information by accessing Google or accessing forums for outdoor activities on social media. We need information that can be a reference standard or facilitate tourists and guides related to the information of guide services that can be seen in completed, clear and up to date. GuideMe application is designed using a feature driven development method which is an agile process that refers to code documents in the form of features that make it easier for developers and clients to get an idea of the system that is being worked on. Develop the overall model, build features and plans based on features done before development work begins, while design based on features and build on features afterwards. The design results are implemented in mobile applications that are easy to use so that it will optimize the work of capable and experienced tour guide service

Learning From the Case Studies, How Global Software Development Process is Executed in an Agile Method Environment

. The biggest challenge in Global Software Development (GSD) is the efficiency of time to develop. GSD provides a guidance to use the process along with up-front analysis method like unified process or waterfall method. Although, it gives a benefit through comprehensive documentation and its clearness, it gives inhibits the organization which wants use GSD but in a rush. Agile methods claim an efficient and the effective approach to software development. This paper reports on how organizations combine the GSD process with agile methods like eXtreme Programming (XP), Scrum, Agile Unified Process (Agile UP), Feature Driven Development (FDD), and Microsoft Solution Framework Agile (MSF Agile). The paper uses case study to get organization experiences and describe useful practices for the organization that want to implement GSD with an agile method.

Adoption of agile software methodology among the SMEs developing an IoT applications

Agile software methodology framework has been used frequently in the software development industry especially among the small medium (SME) companies. In this paper, we conducted a case study among the four selected SME companies that have been developing the Internet of Things application (IoT) as their business core. The results found that all the companies under study are using extreme programming (XP), Dynamic System Development Methodology (DSDM), Feature Driven Development (FDD) and Lean as chosen development methodology. However, the most used agile methodology framework is the Scrum techniques. The study shows that companies applied Agile SDM. This is because, the Agile SDM help the software developer teams to organize their task efficaciously, and able to make frequent delivery to their stakeholders and users