Towards Large Scale Software Project Development and Management

2013 ◽  
Vol 8 (6) ◽  
pp. 20-35 ◽  
Author(s):  
Tanmaya Kumar Das
Keyword(s):  
Large Scale ◽  
Software Project ◽  
Project Development ◽  
Development And Management

scholarly journals Analysis of Service-Oriented Architecture and Scrum Software Development Approach for IIoT

2021 ◽  
Vol 2021 ◽  
pp. 1-14
Author(s):  
Yanqing Cui ◽  
Islam Zada ◽  
Sara Shahzad ◽  
Shah Nazir ◽  
Shafi Ullah Khan ◽  
...  
Keyword(s):  
Software Development ◽  
Process Model ◽  
Large Scale ◽  
Development Process ◽  
Service Oriented Architecture ◽  
Development Project ◽  
Software Project ◽  
Project Development ◽  
Architectural Framework ◽  
Service Oriented

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.

scholarly journals Scrumban: An Agile Integration of Scrum and Kanban in Software Engineering

2020 ◽  
Vol 9 (4) ◽  
pp. 1626-1634
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Engineering Management ◽  
Organizational Capabilities ◽  
Software Project ◽  
Project Development ◽  
Development Organizations ◽  
Internal States ◽  
Development Processes ◽  
Development And Management

Software Engineering (SE) technologies are emerging day by day and seeking ABPR (Agile Business Process Reengineering) for Software Engineering Management (SEM) frameworks in software development organizations. BPR can enable organizational capabilities to initiate and implement critical change in execution. Under the roof of agile and on the base of empiricism, the Scrum has been proven itself as an ABPR approach for software engineering management in the software development organizations, across the world, by improving productivity, self-organization and collaboration for standard software development processes. Scrum has been leading software project development practices using its own characteristics: Artifacts, Pillars, Values, Events and Roles. But still software project development organizations are facing some issues with their software project development and management processes, like no documentation policy which results into inaccurate estimation, internal states of each work item flowing through the Scrum Board, Sprint tracker and prediction towards goal achievement which can be considered as challenges for Scrum due its limitations as well as Scrum does not allow, any alteration in its rules. Such issues have raised a question against implementation of Scrum and have opened the door for the next level of research to answer the question, how to overcome the limitations of Scrum. Kanban can provide the solution to some of these issues but it can’t provide complete SEM solutions to software Development Organizations. The aim of this research study is empirical analysis about how the formation of hybrid framework Scrumban as an integration of Scrum with Kanban, can resolve challenges of Scrum; using literature reviews, case study reviews, and research surveys; and this research has proposed a conceptual customized Scrumban framework, by keeping Kanban in the center of customization under the bound of Scrum rules. This research also concludes limitations of Scrumban, like project documentation, planning, large scaled project, distributed environment, team capabilities etc.; as each method has its own limitations.

eXtreme Programming

2011 ◽  
pp. 108-133
Author(s):  
Fabrizio Fioravanti
Keyword(s):  
The Other ◽  
Extreme Programming ◽  
Software Project ◽  
Design Development ◽  
Project Development ◽  
Success Story ◽  
Software Projects ◽  
Management Processes ◽  
Main Component ◽  
Development And Management

One of the emerging techniques that is becoming increasingly popular for managing software project is eXtreme Programming (XP) (Beck, 1999, 2000; Williams, 2000). XP surely changes the way in which we develop and manage software, as all the other methodologies related to the Agile Manifesto do (Agile Alliance, 2001; Boehm, 2002; Cockburn, 2001; Highsmith, 2001; Rakitin, 2001). XP has been the methodology that I have adopted in recent years to develop and manage software projects — before modifying it in order to create my own methodology, ADPD (Agile and Defined Project Development), which is described in Chapter XI. In order to understand ADPD, it is necessary to acquire all the possible knowledge about XP, since ADPD is XP 80% and recognizes quite all the values of this revolutionary technique for developing and managing software projects. The most interesting feature of XP consists in the fact that it is human oriented (Brooks, 1995). XP considers the human factor as the main component for steering a project toward a success story. On the other hand, it is important to notice that XP is guided by programming rules, even if its more interesting aspects deal with the values that are the real guides for the design, development, and management processes.

Social Media in DMSS System Development and Management

2013 ◽  
pp. 104-116
Author(s):  
Daniel E. O’Leary
Keyword(s):  
Social Media ◽  
Digital Media ◽  
Support System ◽  
System Development ◽  
Media Content ◽  
Project Development ◽  
Media Technologies ◽  
Use Of Social Media ◽  
Project History ◽  
Development And Management

This paper surveys and extends the use of social media technologies as part of decision making support system (DMSS) development and management. In particular, this paper investigates how social media technologies, such as wikis, blogs, micro-blogs and tagging, have been and can be used to facilitate development and management of DMSS, through communication and collaboration. However, the author suggests going beyond simply communication and collaboration. The particular focus is on using an analysis of digital media content to address a range of issues, including using social media content to facilitate capturing project history, doing an analysis of that content to facilitate documentation development, and monitoring content from social media to provide insights into project development. Domain-based characteristics of the text are investigated to discover meaning in social media content.

Using Genetic Algorithms to Search for Key Stakeholders in Large-Scale Software Projects

2013 ◽  
pp. 118-134 ◽  
Author(s):  
Soo Ling Lim ◽  
Mark Harman ◽  
Angelo Susi
Keyword(s):  
Genetic Algorithms ◽  
Real World ◽  
Large Scale ◽  
Requirements Elicitation ◽  
Software Project ◽  
Software System ◽  
Software Projects ◽  
Key Stakeholders ◽  
Large Software ◽  
Stakeholder Needs

Large software projects have many stakeholders. In order for the resulting software system and architecture to be aligned with the enterprise and stakeholder needs, key stakeholders must be adequately consulted and involved in the project. This work proposes the use of genetic algorithms to identify key stakeholders and their actual influence in requirements elicitation, given the stakeholders’ requirements and the actual set of requirements implemented in the project. The proposed method is applied to a large real-world software project. Results show that search is able to identify key stakeholders accurately. Results also indicate that many different good solutions exist. This implies that a stakeholder has the potential to play a key role in requirements elicitation, depending on which other stakeholders are already involved. This work demonstrates the true complexity of requirements elicitation – all stakeholders should be consulted, but not all of them should be treated as key stakeholders, even if they appear to be significant based on their role in the domain.

Sign in / Sign up

Export Citation Format

Share Document