Adapting eXtreme Programming Approach in Developing Electronic Document Online System (eDoc)

2013 ◽  
Vol 321-324 ◽  
pp. 2938-2941 ◽  
Author(s):  
Ida Aryanie Bahrudin ◽  
Rafizah Mohd Hanifa ◽  
Mohd Ezree Abdullah ◽  
Muhammad Firdaus Kamarudin

eXtreme Programming (XP) is one of new discipline of software development methodology on values of simplicity, communication, feedback and also courage. XP is an explorative and agile development method that seeks to satisfy the customer through early and continuous delivery of valuable software. XP software development process starts with planning, and all iterations consist of four basic phases in its life cycle: designing, coding, testing, and listening. This paper tends to report the experience in adapting XP in developing electronic document online system for the use of Centre for Diploma Studies, Universiti Tun Hussein Onn Malaysia (eDoc). The project under study is a system that is use to store office documents such as letter in an online database. The objective of this paper is to discuss the XP practices that had been choosed and also the lesson learnt by practising XP in developing eDoc.

Author(s):  
Vijayan Sugumaran ◽  
Gerald DeHondt

Software reuse has been discussed in the literature for the past three decades and is widely seen as one of the major areas for improving productivity. Agile development techniques were first developed in the mid-1990s as a code-oriented method of software development that seeks to improve upon the traditional plan-based methodologies. Both approaches bring value to the software development process. The purpose of this chapter is to propose a framework that will integrate the strengths of code reuse into the Extreme Programming methodology. It is believed that this approach will lead to a more effective method of software development.


2017 ◽  
Vol 10 (13) ◽  
pp. 143 ◽  
Author(s):  
Jayasudha R ◽  
Viswanathan V ◽  
Shanthi P

The concept of reuse is applied in one of the agile development methodologies called the scrum. Sprint is a single functionality and the result at the end of the sprint functionality is derived as the shippable or bugs. This paper makes an attempt to use the concept of reuse in the agile software development to meet the dynamic change of customer requirements in banks. A banking project is created using both waterfall model and scrum model, and the knowledge gained is stored in the ontology-based repository for the first time. Again, the same project is created for different vendors using the ontology-based repository. The result shows that maximum sprint is reused and all the knowledge gained is stored in the form of ontology. This ontology helps identify the shippable component of each sprint which is a small executable functionality. This leads to less cost and time to deliver the product. The main aim is to increase the availability of the reusable artifacts, which lead to increase the reusability of the developer. The experimental results show improvements in the performance of retrieving the components for the software development.  


Author(s):  
MICHAEL GELFOND ◽  
HALINA PRZYMUSINSKA

This paper is an attempt at mathematical investigation of software development process in the context of declarative logic programming. We introduce notions of specification and specification constructor which are developed from natural language description of a problem. Generalizations of logic programs, called lp-functions are introduced to represent these specifications. We argue that the process of constructing lp-function representing a specification S should be supported by certain types of mathematical results which we call representation theorems. We present two such theorems to illustrate the idea.


2020 ◽  
Vol 22 (3) ◽  
pp. 19-34
Author(s):  
Jerome Vogel ◽  
Rainer Telesko

Today, IT and especially the development of customer-focused software, has become one of the most important elements for a company to remain competitive. The primary purpose of this article is to determine whether it is possible to improve the agile development of a company by adjusting its software development process in terms of cultural, technical, and managerial dimensions. Based on a literature analysis and practical experience in the company, different influencing factors and parameters, which affect the value creation throughout the software development process of a company were derived and clustered. Out of these clusters, a framework (Agile Method Construction Set) based on a Microsoft Excel questionnaire was created in order to analyze and identify optimization potential in the development process of a company. This construction set was adapted to meet the requirements of the development department of a large Swiss insurance company in order to validate and test the framework with real data.


2021 ◽  
Author(s):  
Pau Julià ◽  
David Salvador ◽  
Marc Peña

Software development methodologies have evolved during the last years to reduce the time to market to the minimum possible. Agile is one of the most common and used methodologies for rapid application development. As the agile manifesto defines in its 12 principles, one of its main goals is to satisfy the customer needs through early and continuous delivery of valuable software. Significantly, that none of the principles refers to security. In this paper, we will explain how Typeform integrates security activities into the whole development process, reducing at the same time the phases on the S-SDLC to reduce friction and improve delivery while maintaining the security level.


Author(s):  
Nouf Bin saif ◽  
Mashael Almohawes ◽  
Nor Shahida Mohd Jamail

<p>In software development process, user can take part in any phase of the process, depending on what model is being applied. Lack of user involvement can result in a poorly designed solution, or even a solution that conflicts with user’s needs. This review paper presents the impact of user involvement in software development process. In this study, different software development processes will be reviewed, show where the user usually gets involved in different models such as: Structural (Waterfall, V-model) and incremental (Scrum-extreme programming XP). As each model differs from the other, each of them has a different perspective of where user should take part and where they should not. This can be an asset that helps project managers, and leaders to develop suitable strategies to follow in their projects.</p>


Author(s):  
Rajani Dixit ◽  
Brij Bhushan

In a traditional software development process such as the Waterfall Model, works best in a stable environment. But, it is not flexible when it comes to change. There is a gap in the interaction between the users and the development team which leads to incomplete and misunderstood specification. Because of this, the end product is sometimes a surprise to users and this gap accelerates incorrect development of the software product. Once requirements are frozen there is no scope of accepting changes. There is a need for a framework which holds the solution for all these situations. With this premise, the agile development methodology came into existence. Scrum, an agile approach supports continuous collaboration among the customer, team members, and other stakeholders. Its time-boxed approach and continuous feedback from the product owner ensures the development of working product with essential features at all the time. This paper explains the agile software development approach, its proclamation and different frameworks of agile approach. Further illustrate most widely used framework: Scrum. This research paper covers the implementation and application of Scrum. It focuses on why Scrum is preferred over the Waterfall Model with the help of some survey results and later a discussion on some Scrum Metrics which will be helpful and accounting for the best Scrum Practices in achieving goals set by the software development team, the product owner and the customers. The outcome of this study shows that Scrum Metrics is critical and highly valuable for successful product development. The quantitative insight that these metrics provide for the Scrum Team, Product Owner and Stakeholders is necessary for achieving strong project dynamics and optimal results.


Sign in / Sign up

Export Citation Format

Share Document