Dynamic Systems Development Method Research Articles

Dynamic Systems Development Method dalam membangun Aplikasi Data Kependudukan Pada Kelurahan Rantau Pulut

Dynamic Systems Development Method (DSDM) can be used as one of the methods in developing and building applications based on the needs and communication of users and developers such as in developing Population Data Application In Rantau Pulut Village. Such as data collection through interviews as one form of communication between developers and users. This research aims to build population applications in Rantau Pulut Village as a solution of data processing both in terms of storage and reporting that can help the processing of data needed to become more effective and efficient as well as a solution for the current system running. Through the stages of DSDM conducted and produce applications that can run in accordance with user needs, especially in terms of reporting generated by the application so that users feel user friendly.

Development of Purchasing Module for Agriculture E-Commerce using Dynamic System Development Model

Trading model has been changing since the vast implementation of Information and Communication Technology in every sector. This model is known as e-Commerce. Unlikely, there is still limited company which specifically trades agriculture product. Agriculture e-Commerce is known as a platform to buy and sell some agriculture products. Agriculture e-commerce has important role to support economic development and market expansion for farmers in particular and people in rural areas in general. There is still limited access and provider which buy and sell agriculture product to farmer and its farmer representative. Therefore, this research develops specific agriculture e-commerce. There are two main modules for agriculture e-commerce, purchasing and buying module. On this article, we acknowledge to develop the first module, which is purchasing module. Purchasing module was developed using Dynamic System Development Method (DSDM). Development phase includes feasibility study, business study, functional model iteration, and design and build model iteration. At the end of the phase, testing is conducted. The result of this study is the prototype of agriculture e-Commerce product with predefined functions. Purchasing module of the system depicts the opportunity for farmer to buy the tools and materials. This system has two main functions: purchasing system management and reporting management. System testing also was conducted to test the system.

Research on the Implementation of a Web Based Institutional Support System for Middle East College: Proof of Concept Study

The research mainly focuses on the mechanism of designing a Web-based Institutional Support System. The paper is aimed towards enhancing the studying and working experience, reducing the faculty man-hours and increasing the student and faculty satisfaction at Middle East College (MEC). Currently, Middle East College is not having any online platform where students or teachers can register their complaints, provide feedback/suggestions, report lost items, register or search for peer tutors etc. These are just some of the challenges currently being faced by the MEC community. The main objective of the paper is to conduct a study on the challenges faced by the student during their course of study at MEC, to provide a sustainable solution by developing an effective, flexible and versatile online system to automate the current manual procedures and make them easier to monitor, manage and resolve. The research analysis provides an effective tool for identifying the target problems. It focuses on the importance of having a user-friendly system that can be easily operated by people of average intelligence. Dynamic Systems Development Method (DSDM) is used for the research and development lifecycle as it mainly focuses on the expeditious delivery of the system within the specified time-frame and allocated budget. After considering and analyzing all the literature sources, gathered data and information, it is found that developing this system is an important step towards the betterment of the students and faculty. It not only improves the reputation and performance of MEC but also enhances the studying/working experience at MEC. By using the proposed system, verified users can log-on using their MEC ID’s and password. The Institutional Support System contains various options such as Complaint Registration, Checking Complaint Status, Adding Suggestions/Feedback, Reporting Lost and/or Broken Items, Managing Peer Tutors, etc. You can also generate various reports on complaints, suggestions, and lost items etc. using the system.

A survey on success factors and obstacles for further adoption of agile in IT organisations

These days IT organisations aspire to implement effective and efficient processes and practices for their software development. One such attempt is by trying to implement agile software development methodologies. Indeed, agile methodologies offer some useful advantages to organisations. These benefits include high team collaboration and customer satisfactions. Numerous agile software development methods such as Scrum, extreme programming (XP), Feature driven development, Kanban, dynamic system development method (DSDM) among many are often being used by various IT organisations. Several studies have shown the success and failure of adoption of agile methods or practices. Our research presents a number of additional critical success factors and obstacles by asking from agile practitioners. Moreover, this paper presents a review of some of the existing studies also. The purpose of this survey is use to present a brief guide related to success factors and obstacles of agile adoption in some companies.

A survey on success factors and obstacles for further adoption of agile in IT organisations

These days IT organisations aspire to implement effective and efficient processes and practices for their software development. One such attempt is by trying to implement agile software development methodologies. Indeed, agile methodologies offer some useful advantages to organisations. These benefits include high team collaboration and customer satisfactions. Numerous agile software development methods such as Scrum, extreme programming (XP), Feature driven development, Kanban, dynamic system development method (DSDM) among many are often being used by various IT organisations. Several studies have shown the success and failure of adoption of agile methods or practices. Our research presents a number of additional critical success factors and obstacles by asking from agile practitioners. Moreover, this paper presents a review of some of the existing studies also. The purpose of this survey is use to present a brief guide related to success factors and obstacles of agile adoption in some companies.

A Review of Scaling Agile Methods in Large Software Development

Agile methods such as Dynamic Systems Development Method (DSDM), Extreme Programming (XP), SCRUM, Agile Modeling (AM) and Crystal Clear enable small teams to execute assigned task at their best. However, larger organizations aim at incorporating more Agile methods owing to the fact that its application is prevalently tailored for small teams. The scope in which large firms are interested will extend the original Agile methods to include larger teams, coordination, communication among teams and customers as well as oversight. Determining particular software method is always challenging for software companies especially when considering start-up, small to medium or large enterprises. Most of large organizations develop large-scale projects by teams of teams or teams of teams of teams. Therefore, most recognized Agile methods or first-generation methods such as XP and SCRUM need to be modified before they are employed in large organizations; which is not an easy task. Accomplishing said task would necessitate large organizations to pick and select from the scaling Agile methods in accommodating a single vision for large and multiple teams. Deciding the right choice requires wholesome understanding of the method including its strengths and weaknesses as well as when and how it makes sense. Therefore, the main aim of this paper is to review the existing literature of the utilized scaling Agile methods by defining, discussing and comparing them. In-depth reviews on the literature were performed to juxtapose the methods in impartial manner. In addition, the content analysis was used to analyse the resultant data. The result indicated that the DAD, LeSS, LeSS huge, SAFe, Spotify, Nexus and RAGE are the adopted scaling Agile methods at large organizations. They seem to be similar but there are discrepancies among them that take the form of team size, training and certification, methods and practices adopted, technical practices required and organizational type.

A Survey-based Analysis of Agile Adoption on Performances of IT Organizations

Numerous IT organizations and companies around the world aspire to improve the efficiency and general standard of their software development. The IT organizations want to seize the opportunities and take advantages of new development processes and methodologies. These advantages include higher customers’ satisfaction and better software quality among many. In order to achieve them, different agile software methodologies such as scrum, Feature driven development, eXtremeProgramming (XP), Dynamic system development method, Kanban and others have been frequently adopted by IT organizations across the world. Several studies have shown that agile software development methods are effective in a lot of settings. This study, in which 40 agile practitioners from Malaysia participated, additionally confirms the effectiveness of agile development methods. Furthermore, this paper presents some of the critical barriers not well-known by IT-organizations. The results of this analysis can be used to guide IT organization from the obstacles they may face while adopting agile in their environments.

Agile Adoption in IT Organizations

Many IT organizations aspire to improve the efficiency and general standard of their software development effort by implementing agile software development practices. Some of the popular agile development methods adopted by IT organizations are Scrum, eXtreme Programming (XP), Kanban, Featured Driven Development (FDD) and Dynamic System Development Method (DSDM). This paper intends to identify and analyze the barriers that impact on the performance of IT organizations that use such agile software development methods. The analysis will help the IT organizations to cater the needed aspects to be successful. The analysis will also help the IT organizations to select the right methodology for their organization. The contribution of this analysis is to present guideline related to avoid or overcome the barriers towards adoption of agile.

기능주도개발 Agile 방법을 사용할 때의 안전한 소프트웨어 개발에 관한 문헌연구

Agile 방법론은 시간적 제약하에서도 효율적인 개발 프로세스로 빠르게 제품을 완성할 수 있는 방법으로 알려져 있다. 하지만 scrum, XP, DSDM 등과 같은 여타 Agile 방법들처럼 기능주도개발 (FDD) Agile 방법도 보안요소의 불가용성으로 인해 비판을 받고 있다. 이러한 이슈를 보다 자세히 살펴보기 위해 본 연구는 2001년부터 2012년사이에 나타난 연구들에 대한 체계적인 문헌연구를 수행하였다. 본 연구 결과, 현재 FDD 방법은 안전한 소프트웨어 개발을 부분적으로 지원하고 있는 것으로 나타났다. 하지만 안전한 소프트웨어 사용에 관한 상세한 정보가 문헌에 거의 나타나고 있지 않은 것으로 보아 이 분야에 대한 연구 노력은 거의 없어 보인다. 따라서 현재의 5단계 FDD 방법은 안전한 소프트웨어 개발에 충분하지 않음을 알 수 있고 결국, 본 연구는 FDD 방법에서 보안에 기반을 둔 새로운 수행 단계와 프랙티스가 제안될 필요가 있음을 보여준다. Agile methodologies have gained recognition as efficient development processes through their quick delivery of software, even under time constraints. However, like other agile methods such as Scrum, Extreme Programming (XP) and The Dynamic Systems Development Method (DSDM), Feature Driven Development (FDD) has been criticized due to the unavailability of security elements in its twelve practices. In order to examine this matter more closely, we conducted a systematic literature review (SLR) and studied literature for the years 2001-2012. Our findings highlight that, in its current form, the FDD model partially supports the development of secure software. However, there is little research on this topic, as detailed information about the usage of secure software is rarely published. Thus, we have been able to conclude that the existing five phases of FDD have not been enough to develop secure software until recently. For this reason, security-based phase and practices in FDD need to be proposed.

Risk Management in Agile Model

Risk Management in Agile Model

Web Engineering Security (WES) Methodology

The World Wide Web has had a significant impact on basic operational economical components in global information rich civilizations. This impact is forcing organizations to provide justification for security from a business case perspective and to focus on security from a web application development environment perspective. This increased focus on security was the basis of a business case discussion and led to the acquisition of empirical evidence gathered from a high level Web survey and more detailed industry surveys to analyse security in the Web application development environment. Along with this information, a collection of evidence from relevant literature was also gathered. Individual aspects of the data gathered in the previously mentioned activities contributed to the proposal of the Essential Elements (EE) and the Security Criteria for Web Application Development (SCWAD). The Essential Elements present the idea that there are essential, basic organizational elements that need to be identified, defined and addressed before examining security aspects of a Web Engineering Development process. The Security Criteria for Web Application Development identifies criteria that need to be addressed by a secure Web Engineering process. Both the EE and SCWAD are presented in detail along with relevant justification of these two elements to Web Engineering. SCWAD is utilized as a framework to evaluate the security of a representative selection of recognized software engineering processes used in Web Engineering application development. The software engineering processes appraised by SCWAD include: the Waterfall Model, the Unified Software Development Process (USD), Dynamic Systems Development Method (DSDM) and eXtreme Programming (XP). SCWAD is also used to assess existing security methodologies which are comprised of the Orion Strategy; Survivable / Viable IS approaches; Comprehensive Lightweight Application Security Process (CLASP) and Microsoft’s Trust Worthy Computing Security Development Lifecycle. The synthesis of information provided by both the EE and SCWAD were used to develop the Web Engineering Security (WES) methodology. WES is a proactive, flexible, process neutral security methodology with customizable components that is based on empirical evidence and used to explicitly integrate security throughout an organization’s chosen application development process. In order to evaluate the practical application of the EE, SCWAD and the WES methodology, two case studies were conducted during the course of this research. The first case study describes the application of both the EE and SCWAD to the Hunterian Museum and Art Gallery’s Online Photo Library (HOPL) Internet application project. The second case study presents the commercial implementation of the WES methodology within a Global Fortune 500 financial service sector organization. The assessment of the WES methodology within the organization consisted of an initial survey establishing current security practices, a follow-up survey after changes were implemented and an overall analysis of the security conditions assigned to projects throughout the life of the case study.

BENCHMARKING AND CONFIGURATION OF OPENSOURCE MANUFACTURING EXECUTION SYSTEM (MES) APPLICATION

Information now is an important element to every growing industry in the world. Inorder to keep up with other competitors, endless improvements in optimizing overall efficiency areneeded. There still exist barriers that separate departments in PT. XYZ and cause limitation to theinformation sharing in the system. Open-Source Manufacturing Execution System (MES) presentsas an IT-based application that offers wide variety of customization to eliminate stovepipes bysharing information between departments. Benchmarking is used to choose the best Open-SourceMES Application; and Dynamic System Development Method (DSDM) is adopted as this workguideline. As a result, recommendations of the chosen Open-Source MES Application arerepresented.Keywords: Manufacturing Execution System (MES); Open Source; Dynamic SystemDevelopment Method (DSDM); Benchmarking; Configuration

INTEGRATION OF DATABASE INTO BUSINESS PROCESS TO SUPPORT IMPLEMENTATION OF CUSTOMER RELATIONSHIP MANAGEMENT: CASE STUDY IN PT TDI

Information now is an important element to every growing industry in the world. Inorder to keep up with other competitors, endless improvements in optimizing overall efficiency areneeded. There still exist barriers that separate departments in PT. XYZ and cause limitation to theinformation sharing in the system. Open-Source Manufacturing Execution System (MES) presentsas an IT-based application that offers wide variety of customization to eliminate stovepipes bysharing information between departments. Benchmarking is used to choose the best Open-SourceMES Application; and Dynamic System Development Method (DSDM) is adopted as this workguideline. As a result, recommendations of the chosen Open-Source MES Application arerepresented.

A Review on Software Development Security Engineering using Dynamic System Method (DSDM)

methodology such as Scrum, Extreme Programming (XP), Feature Driven Development (FDD) and the Dynamic System Development Method (DSDM) have gained enough recognition as efficient development process by delivering software fast even under the time constrains. However, like other agile methods DSDM has been criticized because of unavailability of security element in its four phases. In order to have a deeper look into the matter and discover more about the reality, we conducted a literature review. Our findings highlight that, in its current form, the DSDM does not support developing secure software. Although, there are a few researches on this topic about Scrum, XP and FDD but, based on our findings, there is no research on developing secure software using DSDM. Thus, in our future work we intend to propose enhanced DSDM that will cater the security aspects in software development.

Configuration Issues and Efforts for Configuring Agile Approaches-Situational based Method Engineering

In software development process, the requirements are not stable and keep on changing according to the customers. In such dynamic situations the developers are required to use dynamic approaches for software development. The agile methodology provides dynamic methods such as extreme programming, scrum, feature driven approach and dynamic system development method. Studies reveals agile methods are not anti- methods and can be tailored as any other traditional methods. This paper investigates tailoring of various agile methods, approaches required to tailor the method components of agile methods. Further, this paper proposes the configuration issues and configuration efforts which must be kept in mind during tailoring of the agile components.

A Survey of the Use of Agile Methodologies in Different Indian Small and Medium Scale Enterprises (SMEs)

Prior to the use of Agile Methodologies in software industry, the software projects were chaotic and unpredictable. As a result the processes which are best suited for well-defined problem domains cannot manage such software projects. It had been seen that with highly detailed user interface designs, specifications and plans, the software developed turned out different from its original intent because customer requirements change frequently. The crux of Agile Methodologies is that the changes in the requirement can be managed software even during the development cycle of the software development. A survey of 18 SMEs catering software market has been carried out for finding software development scenarios. Eight Agile Methodologies had been studied and surveyed which I found effective in current scenario of software development. These are Extreme Programming, Scrum, Crystal Methodologies, Rational Unified Process, Adaptive Software Development, Feature Driven Development, Dynamic Systems Development Method and Lean Development. And it has been discovered that majority of SMEs follow Scrum for their software development .And other SMEs are also developing their software projects with the help of Scrum variants like scrum and waterfall model as they are using Scrum in requirement gathering, management level processes, and development using waterfall model. This paper summarizes the trends followed for software development in SMEs and it has been shown graphically also.

Teorizando as práticas dos métodos ágeis no desenvolvimento de software visando ao processo de inovação das empresas

Brazilian IT executives are being challenged to play an active and important role in the innovation process within their organizations. The purpose of this study is to explore agile software development methods in facing this challenge. We deployed a practice theory framework, in particular that of Orlikowski, in order to analyze practices from seven agile methods – eXtreme Programming (XP), Dynamic Systems Development Method (DSDM), Scrum, Crystal, Agile Modeling (AM), Feature Driven Design (FDD) and Adaptive Software Development (ASD). Results show practices grouped into five underlying factors – learning, iteractive, customer, human and technical; in addition, they explain the shift in focus of the agile development in reference to previous methods, centering on the individual and their actions in social relations in place of essentially technical issues. Findings suggest that agile software development methods have principles and practices better suitable to the innovation challenge than their predecessors do. Furthermore, their practices can aid the organization in the constitution of institutional properties useful to the process of business model innovation.

Teorizando as práticas dos métodos ágeis no desenvolvimento de software visando ao processo de inovação das empresas

Brazilian IT executives are being challenged to play an active and important role in the innovation process within their organizations. The purpose of this study is to explore agile software development methods in facing this challenge. We deployed a practice theory framework, in particular that of Orlikowski, in order to analyze practices from seven agile methods – eXtreme Programming (XP), Dynamic Systems Development Method (DSDM), Scrum, Crystal, Agile Modeling (AM), Feature Driven Design (FDD) and Adaptive Software Development (ASD). Results show practices grouped into five underlying factors – learning, iteractive, customer, human and technical; in addition, they explain the shift in focus of the agile development in reference to previous methods, centering on the individual and their actions in social relations in place of essentially technical issues. Findings suggest that agile software development methods have principles and practices better suitable to the innovation challenge than their predecessors do. Furthermore, their practices can aid the organization in the constitution of institutional properties useful to the process of business model innovation.

AN APPROACH FOR THE METAMODEL OF THE FRAMEWORK FOR A PARTIAL AGILE METHOD ADAPTATION

Today, such information system development methods as Extreme Programming, Scrum, Dynamic Systems Development Method, Crystal family, Agile modeling, OpenUP and others are being positioned as proven alter-natives to the more traditional plan-driven approaches. However, although there are a variety of agile methods to choose from, the formal methods for their partial adaptation and customization are lacking. The main aim of this paper is to present a metamodel of the framework for a partial agile method adaptation. The paper presents the process of metamodel construction from the concepts that are both direct and indirect solutions to the sub-problems of the partial agile method adaptation. The presented paper extends some of our earlier and more fragmented findings that have been described in our previous work. http://dx.doi.org/10.5755/j01.itc.40.1.194

UML and agile methods

The principles of good software development are improving. We have better answers today about how to develop more effective software then we did yesterday. We may not have complete answers about how to produce quality software but we are getting closer. Two significant advances in the past few years are the Unified Modeling Language (UML), both the notation and its associated process(RUP) and the agile software development model in all of its variations including: Adaptive Software Development (ASD), Dynamic Systems Development Method (DSDM), Feature Driven Development (FDD), Scrum, and eXtreme Programming (XP).