Fig 4 - uploaded by Timothy Malche
Content may be subject to copyright.
Feature Driven Development Process [3]

Feature Driven Development Process [3]

Contexts in source publication

Context 1
... of this step has been repeated till there is no more existence of features [6,8,18]. This is shown in Fig-4. E. Dynamic Software Development Method DSDM (Dynamic Software Development Method) in agile project development is forward as well as backward looking framework. ...
Context 2
... of this step has been repeated till there is no more existence of features [6,8,18]. This is shown in Fig-4. E. Dynamic Software Development Method DSDM (Dynamic Software Development Method) in agile project development is forward as well as backward looking framework. ...

Similar publications

Article
Full-text available
Este editorial objetiva apresentar nossa edição especial comemorativa aos 20 anos do Manifesto Ágil. Aqui apresentamos algumas informações relevantes sobre o estado atual das práticas ágeis nas organizações no Brasil a partir de um levantamento desenvolvido pelos editores desta edição especial. Além disso, também apresentamos os artigos enviados e...
Article
Full-text available
Within this paper the initial steps for the realisation of an agile automated system for battery module disassembly will be presented. The state of the art battery modules need to be analysed with regards to their structure, components and the relationship of the components to each other. In particular, the key challenges in battery module disassem...
Article
Full-text available
The research is based on the idea of agile testing, taking the “order cancelled” module of an e-commerce website as an application case, this study is devoted to exploring a feasible and scientific agile testing framework of four quadrants to form an anticlockwise closed loop for guiding the software agile testing process. Furthermore, further work...

Citations

... Extreme programming [100,101] is a framework of the agile software development methodologies that focuses heavily on coding the most important features first, proceeding iteratively with little or no upfront design. XP found tremendous popularity after its publication by Beck in 1999 and was acknowledged as among the most important software development methodologies up to that date. ...
... Notably, XP relies on deep and constant interaction of the development team with the business users on each iteration, leveraging changes, testing, and continuously refactoring throughout the iterations, as shown in Figure 18. Extreme programming [100,101] is a framework of the agile software development methodologies that focuses heavily on coding the most important features first, proceeding iteratively with little or no upfront design. XP found tremendous popularity after its publication by Beck in 1999 and was acknowledged as among the most important software development methodologies up to that date. ...
... Lean software development (LSD) follows the concept of lean thinking shown in Figure 20, which was introduced in the mid-1950s by Toyota [108], the Japanese car manufacturing company. LSD model guides companies to standardize methodologies, activities, and work products by following some main principles [101,108] • Requires organization-wide cultural change. ...
Full-text available
Article
The key objective of this paper is to investigate the evolution of hybrid software development methods and highlight the main difficulties that arise with regard to information systems (IS) auditing. While technology firms today are under constant pressure to deliver software faster due to emerging needs worldwide, this continuous effort leads to innovative development models, apparently driven by practice. Since modern software development is neither pure linear phases progression nor agile, a challenge arises with regards to selecting the appropriate combination of approaches that serve to reach goals and assure value creation for organizations.
... FIGURE 7. Feature Driven Development Model. [28] D. KANBAN Kanban means 'visual' or 'card' in Japanese and is a visual form of an agile framework. It is a method for managing the logistics chain from a manufacturing perspective, and it is not a structure for controlling inventories [31]. ...
... Extreme programming Model.[28] ...
Full-text available
Article
Software development procedures are constantly evolving to monitor and evaluate the quality and to save money and time. Numerous organizations are migrating away from traditional business models and toward agile methodologies. The purpose of this paper is to illustrate both traditional and agile software development approaches and the numerous techniques associated with them. This analysis conducted identical investigations into two radically different ways of thinking about product development: traditional methods and agile approaches. The paper is supported by several studies commissioned by various organizations to determine the transition from the traditional to the agile paradigm. The follow-up and data analysis explore and reveal changes and emerging trends that arose announcement of the agile technique which is mentioned in this paper, and also has gained increasing prominence in agile in product development over the last couple of years.
... e client's requirements are enhanced and predictability is improved by prioritizing iterations and user stories in accordance with agile principles [4]. ASD (agile software development) involves the rapid and efficient development of products through frequent and complete releases that allow their members and sponsors to assess them before they are released [5,6]. Agile retrospective meetings are used to examine and test the application and process. ...
Full-text available
Article
The SCRUM approach and Service-Oriented Architecture (SOA) framework are critical in assessing the factors that influence the efficiency of a business process and ensuring that business objectives are fulfilled, and the process is on track to meet those objectives. Flexibility and change adoption are critical features for both SCRUM and SOA approaches. Even though both sides encourage agility, the integration of the two independent concepts (SOA is the architectural framework while SCRUM is the development process) should be considered before being used in software management and development projects. This study assessed and analyzed both SCRUM and SOA’s diverse and different software architectural frameworks and development methodologies as well as their environment, which is integrated with the context of software project management and development setup for the software development industry. In addition, this study explores the similarities between the SCRUM process model and the SOA architectural framework to see if they are compatible and, if so, how they may be combined to enhance SOA-based projects. This research also looks at how to build and use a SCRUM methodology for large-scale SOA projects. As a result, SCRUM was chosen as the software development methodology for a research and development project based on SOA. In terms of project development and implementation, the complete project structure is made up of eight main parts.
... In SE scrum is a mash-up of iterative and incremental SD agile model and it mainly focuses on team collaboration and self-organization. The objective of designing Scrum was to increase development speed, define a culture to focus on performance, support stakeholder value creation and improve individual development and quality of life [15][16][17]. ...
Article
Software engineering is a discipline that is little understood by people. It defines how software is developed and maintained to meet the clients’ requirements. Software engineers follow certain systems and standards in their work to meet the clients’ desires. It is on this background that engineers follow specific models in coming up with the final product. One of the models highly used is scrum, which is one of the agile methodologies. However, despite being highly used, it has inherent flaws that need to be corrected. Those flaws are product owner continues changing; do not accept changes in working scrum, sprint’s release time limitation, finally wasting team time within each sprint. This paper presents a new framework, which is an updated version of the current Scrum, to overcome the scum models mentioned issues. In this study, a new framework is presented in a way that is understandable and needed by software developer’s team upon the collected qualitative and quantitative data. The implementation was by making some changes to the current scrum model leading to the “Scrumbear”, certain flaws can be corrected. One of the presented changes involve adding the control master rule to ensure controlling the requirements changing.
... The Agile methods makes the testing becomes an essential component of other parts of the development phases and ensures the continuous product quality (Gil et al., 2016). The agile methods have some similar and difference features, where many studies make a comparison between these methods to show the similar and different aspects, such as Al-Zewairi et al. (2017), , Black (2017), Kumar et al. (2019), Merzouk et al. (2017), and Saleh et al. (2019). Agile methods insist in sharing common values and principles, short iterations, continuous communication among Agile team members, and frequent fast delivery of system under test (Brhel et al., 2015;Tahir, 2019). ...
... Table 2 shows the comparison between them. Some points of this comparison is extracted from a number of studies which include (Al-Zewairi et al., 2017;Black, 2017;Kumar et al., 2019;Merzouk et al., 2017;Mohammad Almseidin et al., 2015;Nawaz & Malik, 2008;Saleh et al., 2019;Sophocleous & Kapitsaki, 2020). However, these studies have not highlighted testing activities and how designing test cases in different Agile methods. ...
Full-text available
Conference Paper
Nowadays the majority of companies in the world are adopting Agile methodology for developing their software products due to the methodology promises to deliver product faster with good quality. The most significant method for checking the quality of a product is software testing. However, in Agile development, software testing is very complex and still has challenges. This is largely happened because the Agile development does not concentrate much on software testing activities. It focuses on customer involvement, short iterations, and regular deliveries. This study is a comprehensive review of the current practices of software testing in the Agile methods. The comparison is made based on some criteria such as change during iteration, acceptance criteria, and quality assurance activities. The aim is to identify the similarities and differences between these methods especially in creating test cases. The study focuses on three common Agile methods which are XP, Scrum and Kanban. The review shows no difference in the techniques for designing test cases between these three methods. This result can contribute to help the developers and testers who adopt Agile methodology to follow the same rule of creating test cases based on the suitable technique in different Agile methods.
... Agile processes (based on agile manifesto [4]) tend to focus on iterations and client suggestions to improve performance and allows for the predictability of varying requirements. Agile software development (ASD) is the development process through which a system is developed efficiently and rapidly by means of regular, frequent, and complete releases permitting the participants and stakeholders to get their hands on the application [5,6]. e application and process are reviewed and tested through agile retrospective meetings. ...
Full-text available
Article
Flexibility and change adoption are key attributes for service-oriented architecture (SOA) and agile software development processes. Although the notion of agility is quite visible on both sides, still the integration of the two diverse concepts (architectural framework and development process) should be well thought of before employing them for a software development project. For this purpose, this study is designed to analyze the two diverse software architectural framework and development approaches, that is, SOA and Scrum process model, respectively, and their integrated environment in software project development setup perspective for Industrial Internet of Things (IIoT). This study also analyzes commonalities among Scrum process model and SOA architectural framework to identify compatibility between Scrum and SOA so that the Scrum process can be constructively used for SOA based projects. This study also examines the proper design and setup of Scrum process suitable for large-scale SOA based projects. For this purpose, an SOA based research and development project is selected as a case study using Scrum as the software development process. The project development and deployment perspective include eight core modules that constitute the overall project framework.
... Project managers can use different methods of implementing agile ideologies. The subsequent discussion will examine extreme programming (XP), Kanban, and scrum [8,9]. ...
Full-text available
Article
Adapting users need to fulfill their requirements and delivering products to be on time within the planned cost, is critical matter that all software project managers (SPM) put the highest priority for it while considering the users satisfaction at the same time. Agile methodology is one of the solutions provided by software engineers (SE), to get the customers involved in the system development life cycle (SDLC) to avoid the risk nonconformance cost. Yet SPM’s still facing the nonconformance costs and the dynamic changes, and the root cause of the issue is not pointed on to find a solution for it. This undertaking research aimed at determining whether software developers understand scrum rules. In addition, how does this knowledge gab affect the software projects success from the project management perspective. Furthermore, the engagement studied the impact of lack of enough knowledge on the topic to project delivery. The collected data from the qualitative and quantitative methods, which was conducted with scrum teams who worked in the health information system (HIS), Educational solutions, and Governmental solutions has showed deviations in organizational practices and team conflicting, competition, and pressure as well as declined product quality.
... Interactions between individuals allow the exchange of information, minimize the necessary documentation and, if necessary, make changes. There are many agile methods such as Agile Modeling, Extreme Programming (XP), Scrum Development, Dynamic Software Development Method (DSDM), Fea-ture Driven Development (FDD), Adaptive Software Development (ASD), Kanban, Lean Software Development (LSD), Rapid Application Development (RAD), Scrumban, and Crystal Methodology [179]. Each one of these methods addresses different perspectives from this methodology. ...
Article
Modern Living, as we know it, has been impacted meaningfully by the Internet of Things (IoT). IoT consists of a network of things that collect data from machines (e.g., mobile devices) and people. Mobile application development is a flourishing tendency, given the increasing popularity of smartphones. Nowadays, users are accessing their desired services on the smartphone by means of dedicated applications as the latter offers a more customized and prompt service. In addition, companies are also looking to persuade users by offering interactive and effective mobile applications. Mobile application developers are using IoT to develop better applications. However, there is no generalized consensus on the selection of best architecture or even the most suitable communications protocols to be used on an IoT application development. Therefore, this article aims at presenting approaches, architectures, and methodologies relevant to the development of mobile IoT solutions.
... The author's work excluded key concepts that should be built to ensure the success of Agile teams in both methodologies. Kumar et al. [2019] studied 13 di®erent Agile methodologies as well. The authors provided a comparison among those methodologies based on 50 di®erent parameters of projects. ...
... Kanban on the other hand is verȳ xable and can take many shapes according to di®erent applications [Yordanova and Toshkov (2019)]. According to Kumar et al. [2019], Kanban can be exposed to frequent changes in the speci¯cations which can overperform Scrum at this point which can only deal with medium level changes. ...
... . User Participation: Scrum encourages user participation and involvement in the development process much more than Kanban. Although applying Kanban as an Agile methodology implies that face-to-face meetings with customers are arranged, these meetings are not as frequent as in Scrum [Kumar et al. (2019)]. ...
Full-text available
Article
This paper provides a systematic comparison between two well-known Agile methodologies: Scrum, which is a framework of doing projects by allocating tasks into small stages called sprints, and Kanban, which is a scheduling system to manage the flow of work by means of visual signals. In this regard, both methodologies were reviewed to explore similarities and differences between them. Then, a focus group survey was performed to specify the preferable methodology for product development according to various parameters in the project environment including project complexity, level of uncertainty, and work size with consideration of output factors like quality, productivity, and delivery. Results show the flexibility of both methodologies in approaching Agile objectives, where Scrum emphasizes on the corporation of the customer and development teams with a focus on particular skills such as planning, organization, presentation, and reviewing which makes it ideal for new and complex projects where a regular involvement of the customer is required, whereas Kanban is more operative in continuous-flow environments with a steady approach toward a system improvement.
Full-text available
Preprint
Existing software development methodologies were mostly focused on team-based development. Solo development presents its own challenges due to the lack of collaboration and resources. Existing solo development methodologies lacked efficiency, modularity, and revisitability, which become the values for the proposed RSSD (Rapid Solo Software Development) methodology. RSSD adopts the same main phases from the Agile methodology (meet, plan, design, develop, test, and evaluate), but with different subphases, values, and optimization measures. The efficiency value focuses on streamlining the planning process, including code structure planning and optimization strategies. Modularity focuses on dividing the codes into smaller functions and reducing dependencies. Lastly, revisitability focuses on improving the clarity of the diagrams, documentation, and code structure for easy revisits. The RSSD methodology was tested on 10 total projects, and respondents agreed that it was helpful to streamline the development process, with an average score of 4.19 out of 5.0. This study contributes to making a streamlined yet effective methodology that helps solo software developers to plan a project in a more structured manner.