With the massive growth of the organizations files, the needs for archiving system become a must. A lot of
time is consumed in collecting requirements from the organization to build an archiving system. Sometimes
the system does not meet the organization needs. This paper proposes a domain-based requirement
engineering system that efficiently and effectively develops different archiving systems based on new
suggested technique that merges the two best used agile methodologies: extreme programming (XP) and
SCRUM. The technique is tested on a real case study. The results shows that the time and effort consumed
during analyzing and designing the archiving systems decreased significantly. The proposed methodology
also reduces the system errors that may happen at the early stages of the development of the system.
Transitioning IT Projects to Operations Effectively in Public Sector : A Case...ijmpict
Operational effectiveness is measured by the application availability to end-users and the extent of
convenient usage of the application to perform their business functions. This paper demonstrates how
varying project transition process can affect the operational effectiveness. This explanatory case study
uses various projects in a South Australian government agency as the candidates for evaluation. With
various applications that existed in the production environment, the end-users had varying levels of
satisfaction. This research analyses factors influencing the operational efficiency the projects in transition
from project delivery into operations. The evidence clearly demonstrates criticality of the transition
process of applications from project delivery phase to operations phase. The research analyses the
findings specific to government agencies and presents recommendations. These findings can be useful to
public sector agencies for improving availability of IT applications in operations.
CRESUS-T: A COLLABORATIVE REQUIREMENTS ELICITATION SUPPORT TOOLijseajournal
Communicating an organisation's requirements in a semantically consistent and understandable manner
and then reflecting the potential impact of those requirements on the IT infrastructure presents a major
challenge among stakeholders. Initial research findings indicate a desire among business executives for a
tool that allows them to communicate organisational changes using natural language and a model of the IT
infrastructure that supports those changes. Building on a detailed analysis and evaluation of these findings,
the innovative CRESUS-T support tool was designed and implemented. The purpose of this research was to
investigate to what extent CRESUS-T both aids communication in the development of a shared
understanding and supports collaborative requirements elicitation to bring about organisational, and
associated IT infrastructural, change. In order to determine the extent shared understanding was fostered,
the support tool was evaluated in a case study of a business process for the roll out of the IT software
image at a third level educational institution. Statistical analysis showed that the CRESUS-T support tool
fostered shared understanding in the case study, through increased communication. Shared understanding
is also manifested in the creation of two knowledge representation artefacts namely, a requirements model
and the IT infrastructure model. The CRESUS-T support tool will be useful to requirements engineers and
business analysts that have to gather requirements asynchronously.
An Investigation of Critical Failure Factors In Information Technology ProjectsIOSR Journals
Rate of failed projects in information technology system project remains high in comparison with other infrastructure or high technology projects. The objective of this paper is to determine and represent a broad range of potential failure factors during the implementation phase and cause of IS/IT Project defeat/failure. Challenges exist in order to achieve the projects goal successfully and to avoid the failure. In this research study, 12 articles were studied as significant contributions to analyze developing a list of critical failure factors of IT projects
Distributed Software Development Process, Initiatives and Key Factors: A Syst...zillesubhan
Geographically Distributed Software Development (GSD) process differs from Collocated Software Development (CSD) process in various technical aspects. It is empirically proven that renowned process improvement initiatives applicable to CSD are not very effective for GSD. The objective of this research is to review the existing literature (both academia and industrial) to identify initiatives and key factors which play key role in the improvement and maturity of a GSD process, to achieve this goal we planned a Systematic Literature Review (SLR) following a standard protocol. Three highly respected sources are selected to search for the relevant literature which resulted in a large number of TOIs (Title of Interest). An inter-author custom protocol is outlined and followed to shortlist most relevant articles for review. The data is extracted from this set of finally selected articles. We have performed both qualitative and quantitative analysis of the extracted data to obtain the results. The concluded results identify several initiatives and key factors involved in GSD and answer each research question posed by the SLR.
CRESUS: A TOOL TO SUPPORT COLLABORATIVE REQUIREMENTS ELICITATION THROUGH ENHA...cscpconf
Communicating an organisation's requirements in a semantically consistent and understandable manner and then reflecting the potential impact of those requirements on the IT infrastructure presents a major challenge among stakeholders. Initial research findings indicate a desire among business executives for a tool that allows them to communicate organisational changes using natural language and a simulation of the IT infrastructure that supports those changes. Building on a detailed analysis and evaluation of these findings, the innovative CRESUS tool was designed and implemented. The purpose of this research was to investigate to what extent CRESUS both aids communication in the development of a shared understanding and supports collaborative requirements elicitation to bring about organisational, and associated IT infrastructural, change. This paper presents promising results that show how such a tool can facilitate collaborative requirements elicitation through increased communication around organisational change and the IT infrastructure.
Architectural approaches for implementing Clinical Decision Support Systems i...Luis Felipe Tabares Pérez
Clinical Decision Support Systems (CDSS) were explicitly introduced with the aim of providing knowledge to clinicians in order to influence its decisions and, therefore, improve patients’ health care. Its architectural approaches are based on Cloud Computing, which provides on-demand computing resources over internet. The goal of this presentation is to determine and discuss key issues and approaches involving architectural designs of a CDSS using cloud computing.
AN OVERVIEW OF EXISTING FRAMEWORKS FOR INTEGRATING FRAGMENTED INFORMATION SYS...ijistjournal
Literatures show that there are several structured integration frameworks which emerged with the aim of facilitating pplication integration. But weakness and strength of these frameworks are not known. This
paper aimed at reviewing these frameworks with the focus on identifying their weakness and strength. Toaccomplish this, recommended comparison factors were identified and used to compare these frameworks.Findings shows that most of these structure frameworks are custom based on their motives. They focus onintegrating applications from different sectors within an organization for the purpose of eliminating communication inefficiencies. There is no framework which guides pplication’s integrators on goals of integrations, outcomes of integration, outputs of integration and skills which will be required for
types of applications expected to be integrated. The study recommended further study on integration
framework especial on designing unstructured framework which will support and guide application’s
integrators with consideration on consumer’s surrounding environment.
Transitioning IT Projects to Operations Effectively in Public Sector : A Case...ijmpict
Operational effectiveness is measured by the application availability to end-users and the extent of
convenient usage of the application to perform their business functions. This paper demonstrates how
varying project transition process can affect the operational effectiveness. This explanatory case study
uses various projects in a South Australian government agency as the candidates for evaluation. With
various applications that existed in the production environment, the end-users had varying levels of
satisfaction. This research analyses factors influencing the operational efficiency the projects in transition
from project delivery into operations. The evidence clearly demonstrates criticality of the transition
process of applications from project delivery phase to operations phase. The research analyses the
findings specific to government agencies and presents recommendations. These findings can be useful to
public sector agencies for improving availability of IT applications in operations.
CRESUS-T: A COLLABORATIVE REQUIREMENTS ELICITATION SUPPORT TOOLijseajournal
Communicating an organisation's requirements in a semantically consistent and understandable manner
and then reflecting the potential impact of those requirements on the IT infrastructure presents a major
challenge among stakeholders. Initial research findings indicate a desire among business executives for a
tool that allows them to communicate organisational changes using natural language and a model of the IT
infrastructure that supports those changes. Building on a detailed analysis and evaluation of these findings,
the innovative CRESUS-T support tool was designed and implemented. The purpose of this research was to
investigate to what extent CRESUS-T both aids communication in the development of a shared
understanding and supports collaborative requirements elicitation to bring about organisational, and
associated IT infrastructural, change. In order to determine the extent shared understanding was fostered,
the support tool was evaluated in a case study of a business process for the roll out of the IT software
image at a third level educational institution. Statistical analysis showed that the CRESUS-T support tool
fostered shared understanding in the case study, through increased communication. Shared understanding
is also manifested in the creation of two knowledge representation artefacts namely, a requirements model
and the IT infrastructure model. The CRESUS-T support tool will be useful to requirements engineers and
business analysts that have to gather requirements asynchronously.
An Investigation of Critical Failure Factors In Information Technology ProjectsIOSR Journals
Rate of failed projects in information technology system project remains high in comparison with other infrastructure or high technology projects. The objective of this paper is to determine and represent a broad range of potential failure factors during the implementation phase and cause of IS/IT Project defeat/failure. Challenges exist in order to achieve the projects goal successfully and to avoid the failure. In this research study, 12 articles were studied as significant contributions to analyze developing a list of critical failure factors of IT projects
Distributed Software Development Process, Initiatives and Key Factors: A Syst...zillesubhan
Geographically Distributed Software Development (GSD) process differs from Collocated Software Development (CSD) process in various technical aspects. It is empirically proven that renowned process improvement initiatives applicable to CSD are not very effective for GSD. The objective of this research is to review the existing literature (both academia and industrial) to identify initiatives and key factors which play key role in the improvement and maturity of a GSD process, to achieve this goal we planned a Systematic Literature Review (SLR) following a standard protocol. Three highly respected sources are selected to search for the relevant literature which resulted in a large number of TOIs (Title of Interest). An inter-author custom protocol is outlined and followed to shortlist most relevant articles for review. The data is extracted from this set of finally selected articles. We have performed both qualitative and quantitative analysis of the extracted data to obtain the results. The concluded results identify several initiatives and key factors involved in GSD and answer each research question posed by the SLR.
CRESUS: A TOOL TO SUPPORT COLLABORATIVE REQUIREMENTS ELICITATION THROUGH ENHA...cscpconf
Communicating an organisation's requirements in a semantically consistent and understandable manner and then reflecting the potential impact of those requirements on the IT infrastructure presents a major challenge among stakeholders. Initial research findings indicate a desire among business executives for a tool that allows them to communicate organisational changes using natural language and a simulation of the IT infrastructure that supports those changes. Building on a detailed analysis and evaluation of these findings, the innovative CRESUS tool was designed and implemented. The purpose of this research was to investigate to what extent CRESUS both aids communication in the development of a shared understanding and supports collaborative requirements elicitation to bring about organisational, and associated IT infrastructural, change. This paper presents promising results that show how such a tool can facilitate collaborative requirements elicitation through increased communication around organisational change and the IT infrastructure.
Architectural approaches for implementing Clinical Decision Support Systems i...Luis Felipe Tabares Pérez
Clinical Decision Support Systems (CDSS) were explicitly introduced with the aim of providing knowledge to clinicians in order to influence its decisions and, therefore, improve patients’ health care. Its architectural approaches are based on Cloud Computing, which provides on-demand computing resources over internet. The goal of this presentation is to determine and discuss key issues and approaches involving architectural designs of a CDSS using cloud computing.
AN OVERVIEW OF EXISTING FRAMEWORKS FOR INTEGRATING FRAGMENTED INFORMATION SYS...ijistjournal
Literatures show that there are several structured integration frameworks which emerged with the aim of facilitating pplication integration. But weakness and strength of these frameworks are not known. This
paper aimed at reviewing these frameworks with the focus on identifying their weakness and strength. Toaccomplish this, recommended comparison factors were identified and used to compare these frameworks.Findings shows that most of these structure frameworks are custom based on their motives. They focus onintegrating applications from different sectors within an organization for the purpose of eliminating communication inefficiencies. There is no framework which guides pplication’s integrators on goals of integrations, outcomes of integration, outputs of integration and skills which will be required for
types of applications expected to be integrated. The study recommended further study on integration
framework especial on designing unstructured framework which will support and guide application’s
integrators with consideration on consumer’s surrounding environment.
Productivity Factors in Software Development for PC PlatformIJERA Editor
Identifying the most relevant factors influencing project performance is essential for implementing business strategies by selecting and adjusting proper improvement activities. The two major classification algorithms CRT and ANN that were recommended by the Auto Classifier tool in SPSS Modeler used for determining the most important variables (attributes) of software development in PC environment. While the accuracy of classification of productive versus non-productive cases are relatively close (72% vs 69%), their ranking of important variables are different. CRT ranks the Programming Language as the most important variable and Function Points as the least important. On the other hand, ANN ranks the Function Points as the most important followed by team size and Programming Language.
The recruitment of new personnel is one of the most essential business processes which affect the quality of human capital within any company. It is highly essential for the companies to ensure the recruitment of right talent to maintain a competitive edge over the others in the
market. However IT companies often face a problem while recruiting new people for their ongoing projects due to lack of a proper framework that defines a criteria for the selection process. In this paper we aim to develop a framework that would allow any project manager to
take the right decision for selecting new talent by correlating performance parameters with the
other domain-specific attributes of the candidates. Also, another important motivation behind this project is to check the validity of the selection procedure often followed by various big companies in both public and private sectors which focus only on academic scores, GPA/grades
of students from colleges and otheracademic backgrounds. We test if such a decision will produce optimal results in the industry or is there a need for change that offers a more holistic approach to recruitment of new talent in the software companies. The scope of this work extends beyond the IT domain and a similar procedure can be adopted to develop a recruitment
framework in other fields as well. Data-mining techniques provide useful information from the historical projects depending on which the hiring-manager can make decisions for recruiting high-quality workforce. This study aims to bridge this hiatus by developing a data-mining
framework based on an ensemble-learning technique to refocus on the criteria for personnel selection. The results from this research clearly demonstrated that there is a need to refocus on the selection-criteria for quality objectives.
Agile software development methodologies have gained traction in the recent past since it was introduced in the mid 90s. They have also been highly adopted in the software development group. In the past 15 years, there have been enormous researches which have been done on agile methodologies and surveys done on the methods of agile methods. In this paper, a survey of various studies on agile methodologies will be conducted using a compare and review review method. There is also a mention of the other agile methods which have not been widely researched. Mrunmayee Gondhalekar | Yogeshchandra Puranik "Agile Methodologies" Published in International Journal of Trend in Scientific Research and Development (ijtsrd), ISSN: 2456-6470, Volume-5 | Issue-4 , June 2021, URL: https://www.ijtsrd.compapers/ijtsrd42493.pdf Paper URL: https://www.ijtsrd.comcomputer-science/other/42493/agile-methodologies/mrunmayee-gondhalekar
Working software measures the progress. Basically, Agile method involves interleaving the specification, implementation, design and testing. Series of versions are developed with the involvement of and evaluation by the stake holders in each version. Agile methods aim at reducing the software process overheads (like documentation) and concentrate more on code rather than the design. Customer involvement, incremental delivery, freedom of developers to evolve new working methods, change management, and last but not the least simplicity is the basic essence of Agile development. Agile methodologies are well suited for small as well as medium sized projects.
Wow! Nearly 3,000 views since I posted this document.
I wrote this to help five R&D project managers to document the results of their efforts. It appears many of you found it helpful, as well.
International Journal of Engineering Research and Applications (IJERA) aims to cover the latest outstanding developments in the field of all Engineering Technologies & science.
International Journal of Engineering Research and Applications (IJERA) is a team of researchers not publication services or private publications running the journals for monetary benefits, we are association of scientists and academia who focus only on supporting authors who want to publish their work. The articles published in our journal can be accessed online, all the articles will be archived for real time access.
Our journal system primarily aims to bring out the research talent and the works done by sciaentists, academia, engineers, practitioners, scholars, post graduate students of engineering and science. This journal aims to cover the scientific research in a broader sense and not publishing a niche area of research facilitating researchers from various verticals to publish their papers. It is also aimed to provide a platform for the researchers to publish in a shorter of time, enabling them to continue further All articles published are freely available to scientific researchers in the Government agencies,educators and the general public. We are taking serious efforts to promote our journal across the globe in various ways, we are sure that our journal will act as a scientific platform for all researchers to publish their works online.
EMPIRICAL STUDY OF THE EVOLUTION OF AGILE-DEVELOPED SOFTWARE SYSTEM IN JORDAN...ijbiss
The focus of agile in software development methods and practices. How to take effective methods in use
have received less attention. Especially in a large organization is not a little to take in agile methods to use.
This paper discusses the adoption and level of experience of the use of agile practices in three companies
in the software development company wide contacts in Jordan. The more practices that relied on largescale
flexibility to measure the progress made by the code work, that the developers efforts to the task of
estimating, to the use of coding standards, and the lack of overtime continuous, has a team to develop their
own operations, to use the limited documentation, and to have the team in one place facility. The adoption
of agile practices of the test, any test of the first unit tests and automated, and low. Some can only appear
agile practices without the adoption of a conscious, because developers find them useful. So it seems that
an emergency operation aimed at agility may also neglect the important agile practices.
There are essential security considerations in the systems used by semiconductor companies like TI. Along
with other semiconductor companies, TI has recognized that IT security is highly crucial during web
application developers' system development life cycle (SDLC). The challenges faced by TI web developers
were consolidated via questionnaires starting with how risk management and secure coding can be
reinforced in SDLC; and how to achieve IT Security, PM and SDLC initiatives by developing a prototype
which was evaluated considering the aforementioned goals. This study aimed to practice NIST strategies
by integrating risk management checkpoints in the SDLC; enforce secure coding using static code analysis
tool by developing a prototype application mapped with IT Security goals, project management and SDLC
initiatives and evaluation of the impact of the proposed solution. This paper discussed how SecureTI was
able to satisfy IT Security requirements in the SDLC and PM phases.
RECOMMENDATION GENERATION JUSTIFIED FOR INFORMATION ACCESS ASSISTANCE SERVICE...ijcsit
Recommendation systems only provide more specific recommendations to users. They do not consider
giving a justification for the recommendation. However, the justification for the recommendation allows the
user to make the decision whether or not to accept the recommendation. It also improves user satisfaction
and the relevance of the recommended item. However, the IAAS recommendation system that uses
advisories to make recommendations does not provide a justification for the recommendations. That is why
in this article, our task consists for helping IAAS users to justify their recommendations. For this, we
conducted a related work on architectures and approaches for justifying recommendations in order to
identify an architecture and approach suitable for the context of IAAS. From the analysis in this article, we
note that neither of these approaches uses the notices (IAAS mechanism) to justify their recommendations.
Therefore, existing architectures cannot be used in the context of IAAS. That is why,we have developed a
new IAAS architecture that deals separately with item filtration and justification extraction that
accompanied the item during recommendation generation (Figure 7). And we haveimproved the reviews by
adding users’ reviews on the items. The user’s notices include the Documentary Unit (DU), the user Group
(G), the Justification (J) and the weight (a); noted A=(DU,G,J,a).
Model-Driven Context-Aware Approach to Software Configuration Management: A F...theijes
The International Journal of Engineering & Science is aimed at providing a platform for researchers, engineers, scientists, or educators to publish their original research results, to exchange new ideas, to disseminate information in innovative designs, engineering experiences and technological skills. It is also the Journal's objective to promote engineering and technology education. All papers submitted to the Journal will be blind peer-reviewed. Only original articles will be published.
Challenges for Managing Complex Application Portfolios: A Case Study of South...IJMIT JOURNAL
This research explores the challenges in management and the root cause for complex application portfolios in the public sector. It takes Australian public sector organisations with the case of South Australia Police (SAPOL) for evaluation it being one of the significant and mission critical state government agencies. The exploratory research surfaces some of the key challenges using interview as primary data collection source, along with archive records, documentation, and direct observation as secondary sources. This paper reports on the information analysed surfacing eight key issues. It highlights that the organic growth of the technology portfolios, with mission criticality has resulted in many quick fixes which are not aligned with long term enterprise architectural stability. Integration of different mismatched technologies, along with the pressure from the business to always keep the lights on, does not provide the opportunity for the portfolios to be rationalised in an ongoing way. Other issues and the areas for further study are explored at the end.
Doctoral Consortium "Networked Innovation - necessity, challenges and and research issues"
Tampere, Finland, September, 15-18,2011
www.nitim.eu is Ph.D. network on Network, Information Technology and Innovation Management
AN OVERVIEW OF EXISTING FRAMEWORKS FOR INTEGRATING FRAGMENTED INFORMATION SYS...ijistjournal
Literatures show that there are several structured integration frameworks which emerged with the aim of facilitating application integration. But weakness and strength of these frameworks are not known. This paper aimed at reviewing these frameworks with the focus on identifying their weakness and strength. To accomplish this, recommended comparison factors were identified and used to compare these frameworks. Findings shows that most of these structure frameworks are custom based on their motives. They focus on integrating applications from different sectors within an organization for the purpose of eliminating communication inefficiencies. There is no framework which guides application’s integrators on goals of integrations, outcomes of integration, outputs of integration and skills which will be required for types of applications expected to be integrated. The study recommended further study on integration framework especial on designing unstructured framework which will support and guide application’s integrators with consideration on consumer’s surrounding environment.
Ludmila Orlova HOW USE OF AGILE METHODOLOGY IN SOFTWARE DEVELO.docxsmile790243
Ludmila Orlova
HOW USE OF AGILE METHODOLOGY IN SOFTWARE DEVELOPMENT INFLUENCE AGILITY OF THE BUSINESS
Agile methodology is widely distributed tool for software development. Presented article explore research data about use of these tools, its influence to quality of the end product and performance of development and overall agility of business and companies.
KEYWORDS:
Agile, software development, agile business
CONTENT
1 INTRODUCTION
2 AGILE SOFTWARE DEVELOPMENT
3 SCALING AGILE
4 AGILE BUSINESS
5 CONCLUSION
REFERENCES
1 INTRODUCTION
Fast pace of science progress in solid state electronics led to incredible progress of computer devices that on its turn demanded software to control and manage the power of computer calculations and usage.
Software engineering emerged in the beginning of 20th century and by the end of it became separate state of art science, activity and the profession for millions. There are about 18.2 million software developers worldwide, a number that is due to rise to 26.4 million by 2019, a 45% increase, says Evans Data Corp. in its latest Global Developer Population and Demographic Study (P. Thibodeau, 2013). Along with growing number of software developers (software development firms, projects and people involved), increased the need for effective management of software development process. This demanded new approach and methodology from business researchers and managers. In the last several decades there was huge number of research, both in IT field and business management dedicated to this area.
Popularity of agile software development methods started about decade ago and at present these methods are employed by many big, medium size and small companies. Still growing attention to agile methods from software development specialists confirm these methods filled the lack of management techniques for software development that emerged and developed extremely fast along with speedy advancement of hardware in IT area. Great number of research done in areas such as changes in performance of software development using agile methods or scaling agile for large companies and teams. Also one of modern trends is an attempt to apply agile methodology for project management, marketing, sales and other activities. Goal of this article is to explore influence of application agile methods in software development to agility of whole company and business. Presented work based on secondary data taken from a multiple sources, the work performed as an exploratory study and a review of existing research in the area.
2 AGILE SOFTWARE DEVELOPMENT
Definition of an adjective agile in English is: able to move quickly and easily or able to think and understand quickly (Oxford Dictionary, 2015). The most often contemporary use presented by the following sentence: Relating to or denoting a method of project management, used especially for software development, that is characterized by the division of tasks into ...
Productivity Factors in Software Development for PC PlatformIJERA Editor
Identifying the most relevant factors influencing project performance is essential for implementing business strategies by selecting and adjusting proper improvement activities. The two major classification algorithms CRT and ANN that were recommended by the Auto Classifier tool in SPSS Modeler used for determining the most important variables (attributes) of software development in PC environment. While the accuracy of classification of productive versus non-productive cases are relatively close (72% vs 69%), their ranking of important variables are different. CRT ranks the Programming Language as the most important variable and Function Points as the least important. On the other hand, ANN ranks the Function Points as the most important followed by team size and Programming Language.
The recruitment of new personnel is one of the most essential business processes which affect the quality of human capital within any company. It is highly essential for the companies to ensure the recruitment of right talent to maintain a competitive edge over the others in the
market. However IT companies often face a problem while recruiting new people for their ongoing projects due to lack of a proper framework that defines a criteria for the selection process. In this paper we aim to develop a framework that would allow any project manager to
take the right decision for selecting new talent by correlating performance parameters with the
other domain-specific attributes of the candidates. Also, another important motivation behind this project is to check the validity of the selection procedure often followed by various big companies in both public and private sectors which focus only on academic scores, GPA/grades
of students from colleges and otheracademic backgrounds. We test if such a decision will produce optimal results in the industry or is there a need for change that offers a more holistic approach to recruitment of new talent in the software companies. The scope of this work extends beyond the IT domain and a similar procedure can be adopted to develop a recruitment
framework in other fields as well. Data-mining techniques provide useful information from the historical projects depending on which the hiring-manager can make decisions for recruiting high-quality workforce. This study aims to bridge this hiatus by developing a data-mining
framework based on an ensemble-learning technique to refocus on the criteria for personnel selection. The results from this research clearly demonstrated that there is a need to refocus on the selection-criteria for quality objectives.
Agile software development methodologies have gained traction in the recent past since it was introduced in the mid 90s. They have also been highly adopted in the software development group. In the past 15 years, there have been enormous researches which have been done on agile methodologies and surveys done on the methods of agile methods. In this paper, a survey of various studies on agile methodologies will be conducted using a compare and review review method. There is also a mention of the other agile methods which have not been widely researched. Mrunmayee Gondhalekar | Yogeshchandra Puranik "Agile Methodologies" Published in International Journal of Trend in Scientific Research and Development (ijtsrd), ISSN: 2456-6470, Volume-5 | Issue-4 , June 2021, URL: https://www.ijtsrd.compapers/ijtsrd42493.pdf Paper URL: https://www.ijtsrd.comcomputer-science/other/42493/agile-methodologies/mrunmayee-gondhalekar
Working software measures the progress. Basically, Agile method involves interleaving the specification, implementation, design and testing. Series of versions are developed with the involvement of and evaluation by the stake holders in each version. Agile methods aim at reducing the software process overheads (like documentation) and concentrate more on code rather than the design. Customer involvement, incremental delivery, freedom of developers to evolve new working methods, change management, and last but not the least simplicity is the basic essence of Agile development. Agile methodologies are well suited for small as well as medium sized projects.
Wow! Nearly 3,000 views since I posted this document.
I wrote this to help five R&D project managers to document the results of their efforts. It appears many of you found it helpful, as well.
International Journal of Engineering Research and Applications (IJERA) aims to cover the latest outstanding developments in the field of all Engineering Technologies & science.
International Journal of Engineering Research and Applications (IJERA) is a team of researchers not publication services or private publications running the journals for monetary benefits, we are association of scientists and academia who focus only on supporting authors who want to publish their work. The articles published in our journal can be accessed online, all the articles will be archived for real time access.
Our journal system primarily aims to bring out the research talent and the works done by sciaentists, academia, engineers, practitioners, scholars, post graduate students of engineering and science. This journal aims to cover the scientific research in a broader sense and not publishing a niche area of research facilitating researchers from various verticals to publish their papers. It is also aimed to provide a platform for the researchers to publish in a shorter of time, enabling them to continue further All articles published are freely available to scientific researchers in the Government agencies,educators and the general public. We are taking serious efforts to promote our journal across the globe in various ways, we are sure that our journal will act as a scientific platform for all researchers to publish their works online.
EMPIRICAL STUDY OF THE EVOLUTION OF AGILE-DEVELOPED SOFTWARE SYSTEM IN JORDAN...ijbiss
The focus of agile in software development methods and practices. How to take effective methods in use
have received less attention. Especially in a large organization is not a little to take in agile methods to use.
This paper discusses the adoption and level of experience of the use of agile practices in three companies
in the software development company wide contacts in Jordan. The more practices that relied on largescale
flexibility to measure the progress made by the code work, that the developers efforts to the task of
estimating, to the use of coding standards, and the lack of overtime continuous, has a team to develop their
own operations, to use the limited documentation, and to have the team in one place facility. The adoption
of agile practices of the test, any test of the first unit tests and automated, and low. Some can only appear
agile practices without the adoption of a conscious, because developers find them useful. So it seems that
an emergency operation aimed at agility may also neglect the important agile practices.
There are essential security considerations in the systems used by semiconductor companies like TI. Along
with other semiconductor companies, TI has recognized that IT security is highly crucial during web
application developers' system development life cycle (SDLC). The challenges faced by TI web developers
were consolidated via questionnaires starting with how risk management and secure coding can be
reinforced in SDLC; and how to achieve IT Security, PM and SDLC initiatives by developing a prototype
which was evaluated considering the aforementioned goals. This study aimed to practice NIST strategies
by integrating risk management checkpoints in the SDLC; enforce secure coding using static code analysis
tool by developing a prototype application mapped with IT Security goals, project management and SDLC
initiatives and evaluation of the impact of the proposed solution. This paper discussed how SecureTI was
able to satisfy IT Security requirements in the SDLC and PM phases.
RECOMMENDATION GENERATION JUSTIFIED FOR INFORMATION ACCESS ASSISTANCE SERVICE...ijcsit
Recommendation systems only provide more specific recommendations to users. They do not consider
giving a justification for the recommendation. However, the justification for the recommendation allows the
user to make the decision whether or not to accept the recommendation. It also improves user satisfaction
and the relevance of the recommended item. However, the IAAS recommendation system that uses
advisories to make recommendations does not provide a justification for the recommendations. That is why
in this article, our task consists for helping IAAS users to justify their recommendations. For this, we
conducted a related work on architectures and approaches for justifying recommendations in order to
identify an architecture and approach suitable for the context of IAAS. From the analysis in this article, we
note that neither of these approaches uses the notices (IAAS mechanism) to justify their recommendations.
Therefore, existing architectures cannot be used in the context of IAAS. That is why,we have developed a
new IAAS architecture that deals separately with item filtration and justification extraction that
accompanied the item during recommendation generation (Figure 7). And we haveimproved the reviews by
adding users’ reviews on the items. The user’s notices include the Documentary Unit (DU), the user Group
(G), the Justification (J) and the weight (a); noted A=(DU,G,J,a).
Model-Driven Context-Aware Approach to Software Configuration Management: A F...theijes
The International Journal of Engineering & Science is aimed at providing a platform for researchers, engineers, scientists, or educators to publish their original research results, to exchange new ideas, to disseminate information in innovative designs, engineering experiences and technological skills. It is also the Journal's objective to promote engineering and technology education. All papers submitted to the Journal will be blind peer-reviewed. Only original articles will be published.
Challenges for Managing Complex Application Portfolios: A Case Study of South...IJMIT JOURNAL
This research explores the challenges in management and the root cause for complex application portfolios in the public sector. It takes Australian public sector organisations with the case of South Australia Police (SAPOL) for evaluation it being one of the significant and mission critical state government agencies. The exploratory research surfaces some of the key challenges using interview as primary data collection source, along with archive records, documentation, and direct observation as secondary sources. This paper reports on the information analysed surfacing eight key issues. It highlights that the organic growth of the technology portfolios, with mission criticality has resulted in many quick fixes which are not aligned with long term enterprise architectural stability. Integration of different mismatched technologies, along with the pressure from the business to always keep the lights on, does not provide the opportunity for the portfolios to be rationalised in an ongoing way. Other issues and the areas for further study are explored at the end.
Doctoral Consortium "Networked Innovation - necessity, challenges and and research issues"
Tampere, Finland, September, 15-18,2011
www.nitim.eu is Ph.D. network on Network, Information Technology and Innovation Management
AN OVERVIEW OF EXISTING FRAMEWORKS FOR INTEGRATING FRAGMENTED INFORMATION SYS...ijistjournal
Literatures show that there are several structured integration frameworks which emerged with the aim of facilitating application integration. But weakness and strength of these frameworks are not known. This paper aimed at reviewing these frameworks with the focus on identifying their weakness and strength. To accomplish this, recommended comparison factors were identified and used to compare these frameworks. Findings shows that most of these structure frameworks are custom based on their motives. They focus on integrating applications from different sectors within an organization for the purpose of eliminating communication inefficiencies. There is no framework which guides application’s integrators on goals of integrations, outcomes of integration, outputs of integration and skills which will be required for types of applications expected to be integrated. The study recommended further study on integration framework especial on designing unstructured framework which will support and guide application’s integrators with consideration on consumer’s surrounding environment.
Ludmila Orlova HOW USE OF AGILE METHODOLOGY IN SOFTWARE DEVELO.docxsmile790243
Ludmila Orlova
HOW USE OF AGILE METHODOLOGY IN SOFTWARE DEVELOPMENT INFLUENCE AGILITY OF THE BUSINESS
Agile methodology is widely distributed tool for software development. Presented article explore research data about use of these tools, its influence to quality of the end product and performance of development and overall agility of business and companies.
KEYWORDS:
Agile, software development, agile business
CONTENT
1 INTRODUCTION
2 AGILE SOFTWARE DEVELOPMENT
3 SCALING AGILE
4 AGILE BUSINESS
5 CONCLUSION
REFERENCES
1 INTRODUCTION
Fast pace of science progress in solid state electronics led to incredible progress of computer devices that on its turn demanded software to control and manage the power of computer calculations and usage.
Software engineering emerged in the beginning of 20th century and by the end of it became separate state of art science, activity and the profession for millions. There are about 18.2 million software developers worldwide, a number that is due to rise to 26.4 million by 2019, a 45% increase, says Evans Data Corp. in its latest Global Developer Population and Demographic Study (P. Thibodeau, 2013). Along with growing number of software developers (software development firms, projects and people involved), increased the need for effective management of software development process. This demanded new approach and methodology from business researchers and managers. In the last several decades there was huge number of research, both in IT field and business management dedicated to this area.
Popularity of agile software development methods started about decade ago and at present these methods are employed by many big, medium size and small companies. Still growing attention to agile methods from software development specialists confirm these methods filled the lack of management techniques for software development that emerged and developed extremely fast along with speedy advancement of hardware in IT area. Great number of research done in areas such as changes in performance of software development using agile methods or scaling agile for large companies and teams. Also one of modern trends is an attempt to apply agile methodology for project management, marketing, sales and other activities. Goal of this article is to explore influence of application agile methods in software development to agility of whole company and business. Presented work based on secondary data taken from a multiple sources, the work performed as an exploratory study and a review of existing research in the area.
2 AGILE SOFTWARE DEVELOPMENT
Definition of an adjective agile in English is: able to move quickly and easily or able to think and understand quickly (Oxford Dictionary, 2015). The most often contemporary use presented by the following sentence: Relating to or denoting a method of project management, used especially for software development, that is characterized by the division of tasks into ...
An Empirical Study of the Improved SPLD Framework using Expert Opinion TechniqueIJEACS
Due to the growing need for high-performance and low-cost software applications and the increasing competitiveness, the industry is under pressure to deliver products with low development cost, reduced delivery time and improved quality. To address these demands, researchers have proposed several development methodologies and frameworks. One of the latest methodologies is software product line (SPL) which utilizes the concepts like reusability and variability to deliver successful products with shorter time-to-market, least development and minimum maintenance cost with a high-quality product. This research paper is a validation of our proposed framework, Improved Software Product Line (ISPL), using Expert Opinion Technique. An extensive survey based on a set of questionnaires on various aspects and sub-processes of the ISPLD Framework was carried. Analysis of the empirical data concludes that ISPL shows significant improvements on several aspects of the contemporary SPL frameworks.
1
45
Table of Contents
Introduction3
Need for technology-based solutions3
Infrastructure Automation Tools4
Implementation4
The Central Theory: Organizational Management and Memory4
Organizational Management4
Organizational Memory4
Need of Data Archival And Storage5
Data Storage.5
Types of Storage.6
Data Archival9
Data Archival Process9
Archiving principles12
Data Management Systems12
Enterprise Resource Planning Systems (ERP systems) for data integration.13
Microservices.15
Properties of Monolithic.17
Conclusion22
References24
Introduction
Technology is considered vital in today's globalized world. Especially in terms of business, information technology has both quantifiable and unquantifiable benefits. It is essential to communicate with customers and stakeholders regularly and necessary for communicating quickly and clearly. It helps in implementing business operations efficiently and effectively, also. A business with robust technological capacity creates new opportunities for a company to stay ahead of the competition and grow eventually (Rangus & Slavec, 2017). Consequently, it also makes dynamic teams that can interact from anywhere in the world—furthermore, technology aids in understanding the business needs and managing and securing confidential and critical data.Need for technology-based solutions
The need for data recovery, active and continuous data processing by its life cycle of significance and utility for research, scientific and educational purposes (Bukari Zakaria & Mamman, 2014). The acknowledgment that information is an organization's key asset since late, decisively affecting its profitability, has contributed to some comprehensive corporate memory approaches. The key causes of competitive advantage are corporate memory and organizational learning ability (C. Priya, 2011). Hence the main obstacle is the effectiveness of information management while ensuring the consistency of training facilities.
Organizations need robust technology-based solutions. Thus, software developers have developed and deployed various forms of overtime architectures that enable software products to become resource-effective and usable. Some architectures implement their frameworks in either one layer or various layers or levels (Suresh, 2012). It is understood that ERP implementation efficiency of ERP implementations is influenced by the rise or excess of a certain degree of capability in the volume of data to process (Johansson, 2012). In the last couple of decades, new architectures have been created with creativity that offers optimum solutions. Thus, the microservices architecture is gaining room and becoming part of the technological, financial, and advertising decision-making process. Microservices replace monolithic, tightly dispersed system-focused applications with an independent operation (Vrîncianu, Anica-Popa, & Anica-Popa, 2009).Infrastructure Automation Tools
One issue as microservices are applied is that any s ...
1
45
Table of Contents
Introduction3
Need for technology-based solutions3
Infrastructure Automation Tools4
Implementation4
The Central Theory: Organizational Management and Memory4
Organizational Management4
Organizational Memory4
Need of Data Archival And Storage5
Data Storage.5
Types of Storage.6
Data Archival9
Data Archival Process9
Archiving principles12
Data Management Systems12
Enterprise Resource Planning Systems (ERP systems) for data integration.13
Microservices.15
Properties of Monolithic.17
Conclusion22
References24
Introduction
Technology is considered vital in today's globalized world. Especially in terms of business, information technology has both quantifiable and unquantifiable benefits. It is essential to communicate with customers and stakeholders regularly and necessary for communicating quickly and clearly. It helps in implementing business operations efficiently and effectively, also. A business with robust technological capacity creates new opportunities for a company to stay ahead of the competition and grow eventually (Rangus & Slavec, 2017). Consequently, it also makes dynamic teams that can interact from anywhere in the world—furthermore, technology aids in understanding the business needs and managing and securing confidential and critical data.Need for technology-based solutions
The need for data recovery, active and continuous data processing by its life cycle of significance and utility for research, scientific and educational purposes (Bukari Zakaria & Mamman, 2014). The acknowledgment that information is an organization's key asset since late, decisively affecting its profitability, has contributed to some comprehensive corporate memory approaches. The key causes of competitive advantage are corporate memory and organizational learning ability (C. Priya, 2011). Hence the main obstacle is the effectiveness of information management while ensuring the consistency of training facilities.
Organizations need robust technology-based solutions. Thus, software developers have developed and deployed various forms of overtime architectures that enable software products to become resource-effective and usable. Some architectures implement their frameworks in either one layer or various layers or levels (Suresh, 2012). It is understood that ERP implementation efficiency of ERP implementations is influenced by the rise or excess of a certain degree of capability in the volume of data to process (Johansson, 2012). In the last couple of decades, new architectures have been created with creativity that offers optimum solutions. Thus, the microservices architecture is gaining room and becoming part of the technological, financial, and advertising decision-making process. Microservices replace monolithic, tightly dispersed system-focused applications with an independent operation (Vrîncianu, Anica-Popa, & Anica-Popa, 2009).Infrastructure Automation Tools
One issue as microservices are applied is that any s ...
Agent Assisted Methodologies have become an
important subject of research in advance Software Engineering.
Several methodologies have been proposed as, a theoretical
approach, to facilitate and support the development of complex
distributed systems. An important question when facing the
construction of Agent Applications is deciding which
methodology to follow. Trying to answer this question, a
framework with several criteria is applied in this paper for the
comparative analysis of existing multiagent system
methodologies. The results of the comparative over two of them,
conclude that those methodologies have not reached a sufficient
maturity level to be used by the software industry. The
framework has also proved its utility for the evaluation of any
kind of Agent Assisted Software Engineering Methodology.
Integrated Analysis of Traditional Requirements Engineering Process with Agil...zillesubhan
In the past few years, agile software development approach has emerged as a most attractive software development approach. A typical CASE environment consists of a number of CASE tools operating on a common hardware and software platform and note that there are a number of different classes of users of a CASE environment. In fact, some users such as software developers and managers wish to make use of CASE tools to support them in developing application systems and monitoring the progress of a project. This development approach has quickly caught the attention of a large number of software development firms. However, this approach particularly pays attention to development side of software development project while neglects critical aspects of requirements engineering process. In fact, there is no standard requirement engineering process in this approach and requirements engineering activities vary from situation to situation. As a result, there emerge a large number of problems which can lead the software development projects to failure. One of major drawbacks of agile approach is that it is suitable for small size projects with limited team size. Hence, it cannot be adopted for large size projects. We claim that this approach can be used for large size projects if traditional requirements engineering approach is combined with agile manifesto. In fact, the combination of traditional requirements engineering process and agile manifesto can also help resolve a large number of problems exist in agile development methodologies. As in software development the most important thing is to know the clear customer’s requirements and also through modeling (data modeling, functional modeling, behavior modeling). Using UML we are able to build efficient system starting from scratch towards the desired goal. Through UML we start from abstract model and develop the required system through going in details with different UML diagrams. Each UML diagram serves different goal towards implementing a whole project.
Reducing Technical Debt: Using Persuasive Technology for Encouraging Software...Hayim Makabee
Technical debt is a metaphor for the gap between the current state of a software system and its hypothesized ‘ideal’ state. One of the significant and under-investigated elements of technical debt is documentation debt, which
may occur when code is created without supporting internal documentation, such as code comments. Studies have shown that outdated or lacking documentation is a considerable contributor to increased costs of software
systems maintenance. The importance of comments is often overlooked by software developers, resulting in a notably slower growth rate of comments compared to the growth rate of code in software projects. This research aims to explore and better understand developers’ reluctance to document code, and accordingly to propose efficient ways of using persuasive technology to
encourage programmers to document their code. The results may assist software practitioners and project managers to control and reduce documentation debt.
An interactive approach to requirements prioritization using quality factorsijfcstjournal
As the prevalence of software increases, so does the complexity and the number of requirements assoc
iated
to the software project. This presents a dilemma for the developers to clearly identify and prioriti
ze the
most important requirements in order to del
iver the project in given amount of resources and time.
A
number of prioritization methods have been proposed which provide consistent results, but they are v
ery
difficult and complex to implement in practical scenarios as well as lack proper structure to
analyze the
requirements properly. In this study, the users can provide their requirements in two forms: text ba
sed
story form and use case form.
Moreover, the existing prioritization techniques have a very little or no
interaction with the users. So, in t
his paper an attempt has been made to make the prioritization process
user interactive by adding a second level of prioritization where after the developer has properly a
nalyzed
and ranked the requirements on the basis of quality attributes in the first le
vel, takes the opinion of distinct
user’s about the requirements priority sequence. The developer then calculates the disagreement valu
e
associated with each user sequence in order to find out the final priority sequence.
Requirement engineering is a key ingredient for software development to be effective. Apart from the
traditional software requirement which is not much appropriate for new emerging software such as smart
handheld device based software. In many perspectives of requirement engineering, traditional and new
emerging software are not similar. Whereas requirement engineering of traditional software needs more
research, it is obvious that new emerging software needs methodically and in-depth research for improved
productivity, quality, risk management and validity. In particular, the result of this paper shows that how
effective requirement engineering can improve in project negotiation, project planning, managing feature
creep, testing, defect, rework and product quality. This paper also shows a new methodology which is
focused on users work process applicable for eliciting the requirement of traditional software and any new
type software of smart handheld device such as iPad. As an example, the paper shows how the methodology
will be applied as a software requirement of iPad-based software for play-group students.
An Agile Software Development FrameworkWaqas Tariq
Agility in software projects can be attained when software development methodologies attain to external factors and provide a framework internally for keeping software development projects focused. Developer practices are the most important factor that has to cope with the challenges. Agile development assumes a project context where the customer is actively collaborating with the development team. The greatest problem agile teams face is too little involvement from the customer. For a project to be agile, the developers have to cope with this lack of collaboration. Embracing changing requirements is not enough to make agile methods cope with business and technology changes. This paper provides a conceptual framework for tailoring agile methodologies to face different challenges. The framework is comprised of three factors, namely, developer practices, customer collaboration, and predicting change
A Novel Optimization towards Higher Reliability in Predictive Modelling towar...IJECEIAES
Although, the area of software engineering has made a remarkable progress in last decade but there is less attention towards the concept of code reusability in this regards.Code reusability is a subset of Software Reusability which is one of the signature topics in software engineering. We review the existing system to find that there is no progress or availability of standard research approach toward code reusability being introduced in last decade. Hence, this paper introduced a predictive framework that is used for optimizing the performance of code reusability. For this purpose, we introduce a case study of near real-time challenge and involved it in our modelling. We apply neural network and Damped-Least square algorithm to perform optimization with a sole target to compute and ensure highest possible reliability. The study outcome of our model exhibits higher reliability and better computational response time
International Journal of Engineering Research and Applications (IJERA) is an open access online peer reviewed international journal that publishes research and review articles in the fields of Computer Science, Neural Networks, Electrical Engineering, Software Engineering, Information Technology, Mechanical Engineering, Chemical Engineering, Plastic Engineering, Food Technology, Textile Engineering, Nano Technology & science, Power Electronics, Electronics & Communication Engineering, Computational mathematics, Image processing, Civil Engineering, Structural Engineering, Environmental Engineering, VLSI Testing & Low Power VLSI Design etc.
A Study of Software Size Estimation with use Case Pointsijtsrd
Estimates for cost and schedule in software projects are based on a prediction of the size of the system. Software size estimation is the most important role in software cost estimation. Use Case Point method can provide software size estimation at the early stage of the development process. Software size estimation is based on the high level speciation of Use Case. This paper describes a simple approach to software size estimation base on use case models the "Use Case Points Method. This model is imported into an estimating tool. To get software size with Use Case Point, the needed factors are the number of use cases and their complexity, the number of actors and their complexity, technical complexity factors TCF , and environmental complexity factors ECF . The system computes unadjusted use case points UUCP , adjusted use case points UPC , and the total effort in staff hours. Aye Aye Seint "A Study of Software Size Estimation with use Case Points" Published in International Journal of Trend in Scientific Research and Development (ijtsrd), ISSN: 2456-6470, Volume-3 | Issue-5 , August 2019, URL: https://www.ijtsrd.com/papers/ijtsrd26531.pdfPaper URL: https://www.ijtsrd.com/computer-science/other/26531/a-study-of-software-size-estimation-with-use-case-points/aye-aye-seint
Does a Hybrid Approach of Agile and Plan-Driven Methods Work Better for IT Sy...IJERA Editor
With a focus on large-scale IT system development projects in diverse enterprises, this research suggests that a hybrid approach combining agile and plan-driven management methods should fit in a wider context of specific project characteristics. Although the extant research illuminates the advantages of the hybrid approach, very few empirical studies actually suggested that the hybrid approach can improve the likelihood of project success. This research results show that the hybrid approach should be more scalable than the agile method, and that the hybrid approach can provide better cost-benefit ratios compared to the traditional plan-driven method. These quantitative and qualitative findings offer a practical recommendation for the project manager or the project management office to utilize the hybrid approach appropriately.
Agile techniques that utilize iterative development are broadly used in various industry projects as a lightweight development technique which can satisfy the continuous changes of requirements. Short repetitions are used that are required for efficient product delivery. Traditional and old software development methods are not much efficient and effective to control the rapid change in requirements. Despite the benefits of Agile, criticism on agile methodology states that it couldn’t succeed to pay attention to architectural and design issues and therefore is bound to produce small design-decisions. The past decade has observed numerous changes in systems development with many organizations accepting agile techniques as a viable methodology for developing systems. An increase in the number of research studies reveals the growing demand and acceptance of agile methodologies. While most research has focused on acceptance rate and adaptation of agile practices, there is very limited knowledge of their post-adoption usage and incorporation within organizations. Several factors explain the effective usage of agile methodologies. A combination of previous research in Agile Methodologies, Diffusion of Innovations, Information Systems implementation, and Systems Development has been carried out to develop a research model that identifies the main factors relevant to the propagation and effective usage of agile methodologies in organizations.
Similar to AN ITERATIVE HYBRID AGILE METHODOLOGY FOR DEVELOPING ARCHIVING SYSTEMS (20)
Modern design is crucial in today's digital environment, and this is especially true for SharePoint intranets. The design of these digital hubs is critical to user engagement and productivity enhancement. They are the cornerstone of internal collaboration and interaction within enterprises.
Globus Connect Server Deep Dive - GlobusWorld 2024Globus
We explore the Globus Connect Server (GCS) architecture and experiment with advanced configuration options and use cases. This content is targeted at system administrators who are familiar with GCS and currently operate—or are planning to operate—broader deployments at their institution.
TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERRORTier1 app
Even though at surface level ‘java.lang.OutOfMemoryError’ appears as one single error; underlyingly there are 9 types of OutOfMemoryError. Each type of OutOfMemoryError has different causes, diagnosis approaches and solutions. This session equips you with the knowledge, tools, and techniques needed to troubleshoot and conquer OutOfMemoryError in all its forms, ensuring smoother, more efficient Java applications.
Experience our free, in-depth three-part Tendenci Platform Corporate Membership Management workshop series! In Session 1 on May 14th, 2024, we began with an Introduction and Setup, mastering the configuration of your Corporate Membership Module settings to establish membership types, applications, and more. Then, on May 16th, 2024, in Session 2, we focused on binding individual members to a Corporate Membership and Corporate Reps, teaching you how to add individual members and assign Corporate Representatives to manage dues, renewals, and associated members. Finally, on May 28th, 2024, in Session 3, we covered questions and concerns, addressing any queries or issues you may have.
For more Tendenci AMS events, check out www.tendenci.com/events
Providing Globus Services to Users of JASMIN for Environmental Data AnalysisGlobus
JASMIN is the UK’s high-performance data analysis platform for environmental science, operated by STFC on behalf of the UK Natural Environment Research Council (NERC). In addition to its role in hosting the CEDA Archive (NERC’s long-term repository for climate, atmospheric science & Earth observation data in the UK), JASMIN provides a collaborative platform to a community of around 2,000 scientists in the UK and beyond, providing nearly 400 environmental science projects with working space, compute resources and tools to facilitate their work. High-performance data transfer into and out of JASMIN has always been a key feature, with many scientists bringing model outputs from supercomputers elsewhere in the UK, to analyse against observational or other model data in the CEDA Archive. A growing number of JASMIN users are now realising the benefits of using the Globus service to provide reliable and efficient data movement and other tasks in this and other contexts. Further use cases involve long-distance (intercontinental) transfers to and from JASMIN, and collecting results from a mobile atmospheric radar system, pushing data to JASMIN via a lightweight Globus deployment. We provide details of how Globus fits into our current infrastructure, our experience of the recent migration to GCSv5.4, and of our interest in developing use of the wider ecosystem of Globus services for the benefit of our user community.
First Steps with Globus Compute Multi-User EndpointsGlobus
In this presentation we will share our experiences around getting started with the Globus Compute multi-user endpoint. Working with the Pharmacology group at the University of Auckland, we have previously written an application using Globus Compute that can offload computationally expensive steps in the researcher's workflows, which they wish to manage from their familiar Windows environments, onto the NeSI (New Zealand eScience Infrastructure) cluster. Some of the challenges we have encountered were that each researcher had to set up and manage their own single-user globus compute endpoint and that the workloads had varying resource requirements (CPUs, memory and wall time) between different runs. We hope that the multi-user endpoint will help to address these challenges and share an update on our progress here.
We describe the deployment and use of Globus Compute for remote computation. This content is aimed at researchers who wish to compute on remote resources using a unified programming interface, as well as system administrators who will deploy and operate Globus Compute services on their research computing infrastructure.
SOCRadar Research Team: Latest Activities of IntelBrokerSOCRadar
The European Union Agency for Law Enforcement Cooperation (Europol) has suffered an alleged data breach after a notorious threat actor claimed to have exfiltrated data from its systems. Infamous data leaker IntelBroker posted on the even more infamous BreachForums hacking forum, saying that Europol suffered a data breach this month.
The alleged breach affected Europol agencies CCSE, EC3, Europol Platform for Experts, Law Enforcement Forum, and SIRIUS. Infiltration of these entities can disrupt ongoing investigations and compromise sensitive intelligence shared among international law enforcement agencies.
However, this is neither the first nor the last activity of IntekBroker. We have compiled for you what happened in the last few days. To track such hacker activities on dark web sources like hacker forums, private Telegram channels, and other hidden platforms where cyber threats often originate, you can check SOCRadar’s Dark Web News.
Stay Informed on Threat Actors’ Activity on the Dark Web with SOCRadar!
Understanding Globus Data Transfers with NetSageGlobus
NetSage is an open privacy-aware network measurement, analysis, and visualization service designed to help end-users visualize and reason about large data transfers. NetSage traditionally has used a combination of passive measurements, including SNMP and flow data, as well as active measurements, mainly perfSONAR, to provide longitudinal network performance data visualization. It has been deployed by dozens of networks world wide, and is supported domestically by the Engagement and Performance Operations Center (EPOC), NSF #2328479. We have recently expanded the NetSage data sources to include logs for Globus data transfers, following the same privacy-preserving approach as for Flow data. Using the logs for the Texas Advanced Computing Center (TACC) as an example, this talk will walk through several different example use cases that NetSage can answer, including: Who is using Globus to share data with my institution, and what kind of performance are they able to achieve? How many transfers has Globus supported for us? Which sites are we sharing the most data with, and how is that changing over time? How is my site using Globus to move data internally, and what kind of performance do we see for those transfers? What percentage of data transfers at my institution used Globus, and how did the overall data transfer performance compare to the Globus users?
How Does XfilesPro Ensure Security While Sharing Documents in Salesforce?XfilesPro
Worried about document security while sharing them in Salesforce? Fret no more! Here are the top-notch security standards XfilesPro upholds to ensure strong security for your Salesforce documents while sharing with internal or external people.
To learn more, read the blog: https://www.xfilespro.com/how-does-xfilespro-make-document-sharing-secure-and-seamless-in-salesforce/
Code reviews are vital for ensuring good code quality. They serve as one of our last lines of defense against bugs and subpar code reaching production.
Yet, they often turn into annoying tasks riddled with frustration, hostility, unclear feedback and lack of standards. How can we improve this crucial process?
In this session we will cover:
- The Art of Effective Code Reviews
- Streamlining the Review Process
- Elevating Reviews with Automated Tools
By the end of this presentation, you'll have the knowledge on how to organize and improve your code review proces
Listen to the keynote address and hear about the latest developments from Rachana Ananthakrishnan and Ian Foster who review the updates to the Globus Platform and Service, and the relevance of Globus to the scientific community as an automation platform to accelerate scientific discovery.
In software engineering, the right architecture is essential for robust, scalable platforms. Wix has undergone a pivotal shift from event sourcing to a CRUD-based model for its microservices. This talk will chart the course of this pivotal journey.
Event sourcing, which records state changes as immutable events, provided robust auditing and "time travel" debugging for Wix Stores' microservices. Despite its benefits, the complexity it introduced in state management slowed development. Wix responded by adopting a simpler, unified CRUD model. This talk will explore the challenges of event sourcing and the advantages of Wix's new "CRUD on steroids" approach, which streamlines API integration and domain event management while preserving data integrity and system resilience.
Participants will gain valuable insights into Wix's strategies for ensuring atomicity in database updates and event production, as well as caching, materialization, and performance optimization techniques within a distributed system.
Join us to discover how Wix has mastered the art of balancing simplicity and extensibility, and learn how the re-adoption of the modest CRUD has turbocharged their development velocity, resilience, and scalability in a high-growth environment.
Quarkus Hidden and Forbidden ExtensionsMax Andersen
Quarkus has a vast extension ecosystem and is known for its subsonic and subatomic feature set. Some of these features are not as well known, and some extensions are less talked about, but that does not make them less interesting - quite the opposite.
Come join this talk to see some tips and tricks for using Quarkus and some of the lesser known features, extensions and development techniques.
Climate Science Flows: Enabling Petabyte-Scale Climate Analysis with the Eart...Globus
The Earth System Grid Federation (ESGF) is a global network of data servers that archives and distributes the planet’s largest collection of Earth system model output for thousands of climate and environmental scientists worldwide. Many of these petabyte-scale data archives are located in proximity to large high-performance computing (HPC) or cloud computing resources, but the primary workflow for data users consists of transferring data, and applying computations on a different system. As a part of the ESGF 2.0 US project (funded by the United States Department of Energy Office of Science), we developed pre-defined data workflows, which can be run on-demand, capable of applying many data reduction and data analysis to the large ESGF data archives, transferring only the resultant analysis (ex. visualizations, smaller data files). In this talk, we will showcase a few of these workflows, highlighting how Globus Flows can be used for petabyte-scale climate analysis.
Designing for Privacy in Amazon Web ServicesKrzysztofKkol1
Data privacy is one of the most critical issues that businesses face. This presentation shares insights on the principles and best practices for ensuring the resilience and security of your workload.
Drawing on a real-life project from the HR industry, the various challenges will be demonstrated: data protection, self-healing, business continuity, security, and transparency of data processing. This systematized approach allowed to create a secure AWS cloud infrastructure that not only met strict compliance rules but also exceeded the client's expectations.
How to Position Your Globus Data Portal for Success Ten Good PracticesGlobus
Science gateways allow science and engineering communities to access shared data, software, computing services, and instruments. Science gateways have gained a lot of traction in the last twenty years, as evidenced by projects such as the Science Gateways Community Institute (SGCI) and the Center of Excellence on Science Gateways (SGX3) in the US, The Australian Research Data Commons (ARDC) and its platforms in Australia, and the projects around Virtual Research Environments in Europe. A few mature frameworks have evolved with their different strengths and foci and have been taken up by a larger community such as the Globus Data Portal, Hubzero, Tapis, and Galaxy. However, even when gateways are built on successful frameworks, they continue to face the challenges of ongoing maintenance costs and how to meet the ever-expanding needs of the community they serve with enhanced features. It is not uncommon that gateways with compelling use cases are nonetheless unable to get past the prototype phase and become a full production service, or if they do, they don't survive more than a couple of years. While there is no guaranteed pathway to success, it seems likely that for any gateway there is a need for a strong community and/or solid funding streams to create and sustain its success. With over twenty years of examples to draw from, this presentation goes into detail for ten factors common to successful and enduring gateways that effectively serve as best practices for any new or developing gateway.
top nidhi software solution freedownloadvrstrong314
This presentation emphasizes the importance of data security and legal compliance for Nidhi companies in India. It highlights how online Nidhi software solutions, like Vector Nidhi Software, offer advanced features tailored to these needs. Key aspects include encryption, access controls, and audit trails to ensure data security. The software complies with regulatory guidelines from the MCA and RBI and adheres to Nidhi Rules, 2014. With customizable, user-friendly interfaces and real-time features, these Nidhi software solutions enhance efficiency, support growth, and provide exceptional member services. The presentation concludes with contact information for further inquiries.
Prosigns: Transforming Business with Tailored Technology SolutionsProsigns
Unlocking Business Potential: Tailored Technology Solutions by Prosigns
Discover how Prosigns, a leading technology solutions provider, partners with businesses to drive innovation and success. Our presentation showcases our comprehensive range of services, including custom software development, web and mobile app development, AI & ML solutions, blockchain integration, DevOps services, and Microsoft Dynamics 365 support.
Custom Software Development: Prosigns specializes in creating bespoke software solutions that cater to your unique business needs. Our team of experts works closely with you to understand your requirements and deliver tailor-made software that enhances efficiency and drives growth.
Web and Mobile App Development: From responsive websites to intuitive mobile applications, Prosigns develops cutting-edge solutions that engage users and deliver seamless experiences across devices.
AI & ML Solutions: Harnessing the power of Artificial Intelligence and Machine Learning, Prosigns provides smart solutions that automate processes, provide valuable insights, and drive informed decision-making.
Blockchain Integration: Prosigns offers comprehensive blockchain solutions, including development, integration, and consulting services, enabling businesses to leverage blockchain technology for enhanced security, transparency, and efficiency.
DevOps Services: Prosigns' DevOps services streamline development and operations processes, ensuring faster and more reliable software delivery through automation and continuous integration.
Microsoft Dynamics 365 Support: Prosigns provides comprehensive support and maintenance services for Microsoft Dynamics 365, ensuring your system is always up-to-date, secure, and running smoothly.
Learn how our collaborative approach and dedication to excellence help businesses achieve their goals and stay ahead in today's digital landscape. From concept to deployment, Prosigns is your trusted partner for transforming ideas into reality and unlocking the full potential of your business.
Join us on a journey of innovation and growth. Let's partner for success with Prosigns.
A Comprehensive Look at Generative AI in Retail App Testing.pdfkalichargn70th171
Traditional software testing methods are being challenged in retail, where customer expectations and technological advancements continually shape the landscape. Enter generative AI—a transformative subset of artificial intelligence technologies poised to revolutionize software testing.
A Comprehensive Look at Generative AI in Retail App Testing.pdf
AN ITERATIVE HYBRID AGILE METHODOLOGY FOR DEVELOPING ARCHIVING SYSTEMS
1. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
DOI: 10.5121/ijsea.2019.10102 17
AN ITERATIVE HYBRID AGILE METHODOLOGY FOR
DEVELOPING ARCHIVING SYSTEMS
Khaled Ebrahim Almajed,Walaa Medhat and Tarek El-Shishtawy
Faculty of Computers and Informatics, Benha University, Information Systems
Department,Egypt.
ABSTRACT
With the massive growth of the organizations files, the needs for archiving system become a must. A lot of
time is consumed in collecting requirements from the organization to build an archiving system. Sometimes
the system does not meet the organization needs. This paper proposes a domain-based requirement
engineering system that efficiently and effectively develops different archiving systems based on new
suggested technique that merges the two best used agile methodologies: extreme programming (XP) and
SCRUM. The technique is tested on a real case study. The results shows that the time and effort consumed
during analyzing and designing the archiving systems decreased significantly. The proposed methodology
also reduces the system errors that may happen at the early stages of the development of the system.
KEYWORDS
Requirement Engineering (RE), Agile, SDLC, Extreme Programming (XP), SCRUM, Archiving.
1. INTRODUCTION
Requirements engineering is a collection of methods related to describing and discovering the
main objective of the system under developing. It works as the link between customers’ real-
world needs and other clients involved in the system such as software owner or software
developer [1].
The title "requirements engineering" may appear a slightly heavy. The two words provide some
poor meanings. Requirement points to somebody out there making the requiring: a special client
who understands what he requires. In several projects, the client knows requirements as the list of
needs. In tradition, very few systems have an individual client, but rather a different group of
people who will be involved in one way or another by the software aka stakeholders.
Stakeholders may have different and inconsistent needs or goals. Their goals or needs may not be
clear or may be hard to explain. Maybe they do not know what they need or what can be
achieved. Therefore, the inquiry about what they ‘need or require’ is not likely to be useful [2].
"Engineering" refers to an engineering system in its own right, considering it is really a part of a
bigger method of engineering software-intensive systems. Engineering term also recommends
that the requirements engineering process outputs required to be fully engineered, where those
'outputs' are normally known to be detailed specifications. In different projects, a big deal of care
2. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
18
is assured when assigning terms. That is because sometimes misunderstandings lead to major
problems that could lead to a problem of security. It could be reasonable not to record complete
terms or specifications in other projects. In various requirements engineering methods, it is the
understanding that is reached from using the necessary systematic technique for analysis that is
necessary, rather than the documented terms or specifications [3].
Agile is used for specifying means of planning and making work wherein it is agreed that doing
modifications as required is an essential piece of the task. Agile in business indicates that an
organization is regularly in a state to perform market changes. Agile in software development is
adjusted to express the capability to respond to technology, people, and requirements changes.
The most known agile methodologies are XP and SCRUM.
Extreme Programming [4] agile methodology founders pointed to develop a proper Object
Oriented (OO) technique for projects where teams utilized by a little or dozen developers in one
place. The technique is based on five underlying concepts: simplicity, communication, courage,
respect, and feedback. SCRUM is a methodology for agile requirement engineering to ensure
teamwork and iterative incremental progress that ensure reaching the client goals for developing
any software project, SCRUM like any agile methodology can handle the multiple changes for
the client requirement. SCRUM has three core concepts which are inspection, transparency, and
adaptation.
Archiving Systems are very important nowadays specially for large and governmental
institutions. They make use of huge structured and unstructured data [5]. The unstructured data or
files need to be archived electronically to facilitate the automation of the work process. Since
these institutions have many stakeholders, the process of gathering requirements is not easy.
This paper proposes a hybrid Agile methodology that combine the two best methodologies
SCRUM and extreme programming. We called the methodology “An Iterative Hybrid Agile
Methodology for Developing Archiving Systems”. HyArchive is an iterative and incremental
hybrid agile software development framework merging between SCRUM and XP to solve the
problem of gathering requirements to build archiving systems for large governmental institution.
The paper is organised as follows: An overview of the previous works related to our subject is
presented in section 2. In section 3, a comparison between Agile methodologies is presented. In
section 4, HyArchive Methodology is presented. In section 5, three different case studies are
presented, before drawing the conclusion in section 6.
2. RELATED WORKS
In [6] the authors showed that the department of information technology is a critical and
important factor that affects the practices of agile, and the current researches have not explored
the relationship between the usage of agile practices and information technology department.
They showed that how the main propose of their study is to explore/test two different types of
agile practices (technical and social) and four competing culture forms. They also showed how
the findings add value to the current literature by combining the competing values with the
3. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
19
literature which affects the information technology department level and agile development level.
Authors concluded the research with listing the research limitations, as the sample consisted of
only the US-based firms. The researchers identified a potential pool of participants using
LinkedIn, that's beside some departments of information technology that may only adopt agile
practices for less information technology projects.
In [7]the authors examined the previous work and found that forty-seven studies have examined
the identification of stakeholder techniques in Requirements Engineering. They concluded that it
is very important to consider that because the sources are unstructured and the high level of the
analysed studies that are not heterogeneous, meta-analysis methods are not applied. Their
findings, included an examination of the shortcomings found in this systematic literature review,
produce definite evidence to support additional study in the development of new techniques to
appropriately complete Stakeholder identification. They showed that all the analysed papers show
the discrepancies between current stakeholders involved in software development as each one
have various interests and priorities.
In [8]the authors showed that methodology selection of software development for all projects is
important and has a high impression of client satisfaction and the selection mainly done by
experience or in many cases a rational particularly in the third world countries such as Sudan.
They showed that Sudan has various companies that still in the start-up phase or have small
resources and they have a difficulty in software methodology choice. They also showed that
Sudan government is the principal buyer of local software products and the government is
shifting the industry of software to offer high-quality products to decrease the process of buying
the software from foreign organizations. They showed how the small or medium companies use
the Agile techniques on software development and how these techniques or methods is a way of
getting a guaranteed high-quality product.In addition, how the Agile methods are the most known
techniques nowadays that is because agile methods fit with the change of requirement and it only
works to satisfy the clients’ needs. They were mainly focused on filling the gap of information
missing in existing literature reviews by making a review on most known and most used agile
methods.
In [9] the authors constructed a case study on an e-business project to introduce trading based on
web, logistics, and marketing to medium and small-sized enterprises. They showed that the
project will help them in building a collection of new application modules combining with their
legacy information systems, which will increase their IT platform and allow them to achieve their
system aims. The authors found that the used method was more helpful and they also merged the
advantages of various modeling method.Thus enhanced the outcome of modelling work and
afford a full understanding of the process of business to the end user, and developer.
In [10] the authors tackled that Agile SCRUM methodology and agile extreme programming
methodology when used on the project, the productivity is improved.They compared and
analyzed the two methods to figure out the discrepancies and the relationship between them.They
have applied the two methods on the same project and compared the acceptance of each method
on the project.
4. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
20
In [11] the authors developed a methodology that supported the Enterprise Resource Planning
system arrangement functions to client specifications. Authors developed a systematic approach
that can help to recognize the new functions of the Enterprise Resource Planning system, through
which a conventional combination of the requirements three parts are guaranteed. They have
established a post-traceability connection between Enterprise Resource Planning functionality
and requirements, giving an intended view of what the Enterprise Resource Planning system can
do. They proposed the requirements process of matching that mainly Enterprise Resource
Planning driven. They decreased the number of deviations from the Enterprise Resource Planning
functionality in a provided installation besides taking the advantage of the full Enterprise
Resource Planning functionality power.
In [12] the authors showed how the agile methodologies are widely used these days in IT industry
and show how each method has its benefits and its limitations that need a solution. They clarified
that SCRUM agile and extreme programming agile methods are the most agile used methods in
the business and both of them can be used if the client did not have a clear requirement of his/her
project. They introduced a new agile method that merges between SCRUM and XP and showed
how the new method can be applied to increase the productivity and be useful if applied with
small or large projects.
In [13] the authors showed how companies or organizations that work on software development
can offer the production of a helpful software on short time with decreasing the cost. They
showed how the agile methodologies improved the process of software production. They listed
the benefits, advantages, and the disadvantages of the agile methodologies especially SCRUM
and XP. They also showed the importance of agile methods and how these methods divide the
large project into small tasks to finish and deliver each task in its time with a high quality.
In [14] the authors showed how requirement engineering is an important field and critical phase
of the production process of any software. They showed how its importance increases more and
more because of the changes in the project requirement during the production phase. How the
traditional process and methods cannot solve the problem of changing requirement. They studied
the agile methods such as SCRUM and XP clarifying their importance to the requirement
engineering methods. They concluded that extreme programming method was beneficial to small
projects and can be used with large projects but after defining its limitations.
In [15] the authors showed the importance of the SCRUM agile method and how it's critical when
other researchers think about making or producing a new hybrid agile methodology. SCRUM is
the best from the author's opinion based on a review they already made. Their research objective
was to provide a full description of agile methods and how SCRUM method is the most used,
merged, helpful, productive and beneficial method among the other agile methods. They also
showed the importance of merging two or more agile methods to improve the performance of
software production. Their conclusion showed how the SCRUM method was the most used one
while crystal and Kanban ere not mentioned.
In [16] the authors showed how agile accelerated the software delivery process, addresses
software changes and increases productivity. The authors’ objectives were to design an approach
5. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
21
that can be combined with agile methodologies for software development in order to increase
productivity. Their results showed how agile SCRUM is the most frequently integrated method
and when SCRUM used, the usability and quality improved. They also showed the importance of
using the DT approach and how it improved the communication between the customer and the
development team during the whole cycle of software development.
3. AGILE METHODOLOGIES
There are many Agile methodologies in the literature as illustrated in Figure 1. In the next
subsections, we will tackle the best used methodologies from the literature Scrum and XP then,
we will compare between them.
Figure 1. Agile methodologies
4. SCRUM
The Scrum process that carry out the requirements with a very high quality in compliance with
the most used standards is shown in the following steps [17]:
Planning the tasks for the product owner: when planning the tasks for the product owner any
newly formed team found a challenge on how to find its ability/capacity for the Sprints
development or how many items can be scheduled in a Sprint. Therefore, it is recommended to
run very short Sprints at the first, which gives the team the ability to adjust the time for the
Sprints in order to finish in a timely manner. On the other side, the Product Owner works with his
Stakeholders so that they can maximize the benefits and works with the team to find the best
solution for a requirement. A requirement must be worked on so that it can deliver a return at the
end.
Organization of the product backlog: The Multi-Level Product Backlog is an important tool for
the Scrum built-in requirements engineering process. An effective Product Backlog must have a
good organization and structure and this can be used for both the development and organization
of Sprints. The product backlog has three different stages. Stage 3 where the requirements are
collected, Stage 2 where the requirements specified, and Stage 1 where the requirements
6. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
22
transferred into a state through quality gates between the levels, which meet the requirements of
the Team regarding estimates that are more precise.
Quality gates: there are quality gates between the three-staged product backlog these gates are
checklists that verify the quality of requirements, for example in Stage 3 the product owner
collects unspecified features, ideas, and change requests. The product owner should have a
minimal set of information attached when an item enters the product backlog at this stage, then he
works on the refinement of this information if it has considered important for him. At the end
when an item is important enough to enter the stage of detailed requirement engineering, the
following quality gate has to be passed.
5. EXTREME PROGRAMMING (XP)
Extreme Programming (XP) is an agile software development framework that develop a
methodology suitable for Object Oriented (OO) projects and aims to produce a software of a high
quality using teams of a dozen or fewer programmers in one location. Extreme Programming is
the most specific of the agile frameworks and it is based on five underlying values [18].
Extreme programming consists of small, extended development team that works in the same
place. Software requirements are dynamically changing. Extreme Programming five values are
simplicity, communication, courage, respect, and feedback. Extreme programming main players
are the Customer, the Developer, the Tracker, and the Coach. Although XP is based on specifying
particular practices for the development team to follow, it is not establishing specific roles for any
of its players.
Extreme Programming planning releases and also different concepts are shown in the following
points:
Planning Game
The planning starts at the beginning of each iteration where the stakeholders of the project meet
to define, estimate and prioritize the “User Stories” (i.e. requirements) for the next release.
Small Releases
There are two types of version releases: initial version and working version. The initial version is
produced after a few iterations and it does not implement all features, but only essential ones.
While, a working version is produced after a few weeks and contains most of the features.
Metaphor
It is used in the modelling of the software system and is constructed by all the stakeholders.
7. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
23
Simple Design
It is the base of the XP methodology and applies to the requirements gathering, system design,
coding, and communications with the customer.
Tests
In XP methodology, testing is considered one of the major activities to ensure high quality
product in addition to high customer satisfaction. Testing begins before the coding phase, where
developers are required to prepare the test functions prior writing the code itself. While,
customers are required to prepare the functional test scenarios for each iteration.
Refactoring
It means that any changes made on the system must uphold the simplicity feature.
Pair Programming
Coding of the software system is carried out in a group of two developers.
Continuous Integration
New parts of the software system are integrated as soon as they pass both the unit and functional
test cases.
Collective Ownership
The ownership of the code produced belongs to all developers.
On-Site Customer
Someone from the customer side must work with the development team at all times.
40-Hour Weeks
The maximum working hours per week for developers must not exceed 40-hours, which implies
that the requirements must be revised too.
Open Workspace
All work, including coding and development must take place in a common environment.
8. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
24
XP and SCRUM Differences and Similarities
Differences
SCRUM team works on a higher priority than extreme programming team in backlogs.
Extreme programming main player is the product owner but in SCRUM is not.
SCRUM is not engineering practice field but XP is an engineering practice.
Extreme programming method takes less time than SCRUM method. Extreme
Programming method takes two weeks at the most but SCRUM takes up to one month in
order to finish the process.
The maintenance and improvements for extreme programming are more easily than
SCRUM method where the changing not allowed through the iteration process if sprint
begins.
Similarities
Both SCRUM and Extreme Programming can work iteratively but with a different time for each
one, and the work based on priority depends on the process that needs to be done.
In general, we will compare the agile methodologies and describe the agile limitations in the
following subsections.
Agile Limitations
The availability of the customer may not be possible.
Methods rules must be given by experienced teams.
Defining a proper iteration' functionality required.
Communication skills required for the teams.
Iterations must be designed properly which needs special design skills.
Comparison between agile Methodologies
Table 1 shows a comparison between Agile Methodologies while Table 2 lists the traditional
techniques that are used in different agile methodologies.
9. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
25
Table 1. Comparison between Agile Methodologies
# Agile Method Requirements Representation Customer Role
1 XP User Stories (written cards and conversations)
Requirements are not assumed to be complete or
sharply stated.
Destroy user stories after implementation.
On-site
customer is
required to
participate in
requirements
definition,
estimation and
prioritize.
2 Scrum User stories are used.
The actual requirements are defined based on the
discussion of user stories between software owner
and software developers.
Software owner
plays the lead
role in defining
the
requirements
3 FDD UML diagrams are used.
List of features is used to manage the functional
requirements.
Requirements are first represented in a high-level
context.
For each modeling area, the requirements are
modeled per domain.
After requirements are modeled, it should be peer-
reviewed.
Undefined.
4 Lean
Development
Just-In-Time methodology is applied in
requirements gathering.
User stories (cards) are also used by the customer
to specify initial requirements and sample screens
by the developers.
Developers then provide a time estimate for each
card.
Provide input
on initial user
stories.
5 ASD Requirements’ gathering is part of the speculation
phase.
Undefined.
6 Kanban User stories are used to define each sprint main
goal.
Each sprint handles a single user story.
Each story is divided into the server-side and
client-side task.
Each task is further divided into subtasks.
Undefined.
7 AUP Requirement phase consists of the following
activities:
- Identifying stakeholders
- Understanding problem
- Establishing the estimation basis.
- Defining user interface.
User stories are used in the construction phase.
Requirements are presented as Business Use Case
Model.
Undefined.
8 DSDM Requirements are gathered and prioritized during
the feasibility phase.
Undefined.
10. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
26
Table 2. Traditional technique exist in scrum and XP
HyArchive Methodology
We propose a hybrid Agile technique that merges the two most known agile methodologies:
extreme programming (XP) and SCRUM. The main concept is to integrate agile methods XP,
SCRUM with the software development life cycle (SDLC) methods to build an efficient
archiving technique. Hy Archive is a technique for managing an archiving system' development
process. It is designed for teams of developers who: break their work into actions like SCRUM
that can be completed within fixed duration cycles (called "sprints"), and collaborate to deliver
workable Archiving software every sprint. Hy Archive is an iterative and incremental hybrid agile
software development framework merging between SCRUM and XP for managing the
development process of an archiving system.
HyArchive Main Players
There are four core players in the HyArchive methodology:
Product Owner
HyArchive Development Team
HyArchive Analyst
HyArchive Master
These are ideally co-located to deliver potentially shippable an archiving system increments every
sprint.
Product Owner: The product owner represents the archiving system customer or stakeholders
and is responsible for ensuring that the development team delivers value to the business. The
11. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
27
product owner defines the product in customer-centric terms (typically user stories), adding them
to the archiving system backlog, and prioritizes them based on importance and dependencies.
Teams should have one product owner. This role should not be combined with that of the
HyArchive master. The HyArchive product owner should focus on the business side of the
archiving system development and spend the majority of their time liaising with stakeholders and
should not dictate how the team reaches a technical solution.
HyArchive Development Team: The HyArchive development team is accountable for
producing potentially shippable product increments every sprint (the sprint goal).The HyArchive
development team execute all needed tasks to produce the product increments.
HyArchive Analyst: As we know one of agile weakness is the design needs that should be kept
simple and maintainable. Thus requiring effective design skills. Therefore, the HyArchive analyst
plays an important role and can’t be one of the team members. The analyst main rule is designed
to sketch and to design data structure and then write the algorithms in a step-by-step way with the
development team. He also works with the HyArchive master to guarantee the efficiency of data
structure, OOP, and testing concepts on our technique.
HyArchive Master: The HyArchieve master facilitates the HyArchive technique.The HyArchive
master is accountable for removing impediments to the ability of the HyArchive development
team to deliver the archiving system goals. That’s besides ensuring that the HyArchieve
methodology implementation is correctly followed. The core responsibilities of a HyArchive
master include:
Enabling the HyArchive development team to know the progress of the product, along
with the input from key stakeholders.
Arrange with the product owner to schedule a meeting with the HyArchive development
team to address if what planned is the best for the project or not.
Deliver the archiving system with good-quality features.
Guarantee the best progress.
Helping the stakeholders to learn HyArchieve principles.
HyArchive Algorithm
Figure 2shows the flowchart of the HyArchive algorithm.
The HyArchive algorithm is listed here from the start until publishing the system.
1- Collect Requirements from customer (Rx).
2- Collect Requirements from S/W owner & S/W developers (Ry).
3- Compare (Rx) and (Ry) and get matched Requirements.
4- Store requirements into three ordered classes:
12. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
28
(a):contains (Rx)∩ (Ry).
(b):contains (Rx) — (Ry).
(c):contains (Ry) — (Rx).
5- Work on requirements of class (a).
6- Get customer feedback & store results in class (b).
7- Work on requirements of class (b).
8- Get user feedback & store result in class (b).
9- Work on requirements of class (c).
10- Get user feedback & store result in class (b).
11- Work on requirements of class (b).
12- Get user feedback & store results in class (b).
13- Review requirements in class (b) by S/W owner & developer.
14-Discuss R(b) by S/W owner & developer & customer.
15- Decide final set of requirements to be implemented.
16- Release the system to review team.
17- Release the system to testing team.
18- Publish the system.
Figure 2.HyArchiveAlgorithm Flowchart
13. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
29
HyArchive Work Flow
Figure 3 shows the flowchart of the HyArchive methodology which contain the following main
steps.
A sprint is a core unit in HyArchive methodology.
The sprint is a time-boxed effort.It is restricted to a specific duration.
The duration is fixed in advance for each sprint.
The sprint backlog is defined at the beginning of each sprint, after identifying each sprint
work.
Ensures the best for what planned through a meeting in each sprint between the
HyArchive analyst and the product owner.
Make a full review of the end of each sprint to the stakeholders to list improvements and
lessons for the next sprints.
Figure 3.HyArchive Work Flow
4.3.HyArchive Sprint
The HyArchive sprint contains the following:
Exploring Requirements.
Development team meeting with the product owner.
Algorithm design.
Scheduling.
Coding.
Testing.
Case Studies
Three case studies are conducted, one for Extreme programming method, one for the Scrum
method, and one for our new method HyArchive. All the studies were conducted in order to make
an archiving system for three different departments. These methods applied on three departments
that were suffering from the large amount of documents and the un-automated workflow in a
governmental Organization.
14. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
30
Three teams were chosen to compare the effectiveness of the proposed approach with existing
approaches. Each team is assigned to implement the Archiving system using one methodology.
Three departments used to apply the implemented techniques. The first team took an assignment
of implementing the archiving system in the HR department. The second team took an
assignment of implementing the archiving system in the training department. The third team is
assigned to implement the archiving system in the Administration and organization department.
Table 3 shows the comparison between departments and illustrates the amount of documents in
each department.
Table 3. Comparison between departments of case studies
Meetings were held with the personnel in charge and employees in three different departments.It
was agreed to build an electronic archive system with the following features:
1. Provide spatial space, dispense the archived papers and piles of transactions and files.
2. Linking the parts of the institution no matter how far away between places.
3. Easy and fast transfer of messages and electronic documents between branches of the
organization or outside the scope of the organization.
4. Easy access to electronic documents.
5. Regardless of the location of the beneficiary or user of these documents.
6. Monitoring the documents and their transformation.
7. Follow-up, development, and knowledge of the course of transactions within the system.
8. Multiple access points for documents electronically saved which facilitates the retrieval
of documents.
9. Fast access to the beneficiaries and their services, minimizing errors and violating
regulations.
10. Minimize reviews of government departments by beneficiaries.
11. Centralization in dealing with documents and thus not inconsistency and repetition in
issuing orders or decisions.
12. Standardization in dealing with documents linking information in more than one database
both inside and outside the parent organization.
13. Increase the performance of government institutions as well as private sector institutions.
HyArchieve Case Study
The main purpose of conducting the case study is to develop an archiving system following the
new proposed method HyArchieve. The total time for this case study was eight weeks not
15. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
31
including the training time of the new proposed methodology HyArchieve. MySQL, MS Test,
and crystal report,are tools used during the work. The HyArchieve team was consisting of eight
members, 4 developers/designers, 3 testers, and one HyArchieve master that deals with the team
and acts as the product owner too.
Scrum Case Study
The main purpose of conducting the case study is to develop an archiving system following the
principles of Scrum method. The total time for this case study was eight weeks not including a
training program that includes the principles of the Scrum methodology. The Scrum team was
consisting of eight members, 4 developers/designers, 3 testers, and one Scrum master that deals
with the team and acts as the product owner too.
Extreme programming Case Study
The main purpose of conducting the case study is to develop an archiving system following the
principles of the extreme programming method. The total time for this case study was eight
weeks not including a training program that includes the principles of the extreme programming
methodology. The main propose of the training was to ensures that the team understands the
concept "keep it simple", and to work in pairs correctly. The XP team was consisting of eight
members, four developers/designers, 3 testers, and XP master that deals with the team and acts as
the product owner too.
Results
All the studies were conducted in order to build similar archiving systems for three different
departments. All case studies were conducted in Kuwait country, and a team of eight members is
selected to work on all the case studies in order to generate the results. More details provided in
the below table. In comparing the three methodologies, the same features were used in [19].
Table 4 and Table 5 illustrate that HyArchieve was conducted by a team consists of eight people.
They took 35 days to complete their mission. The system was released five times each one with
an updated issue. The numbers of tasks of the system were 50 tasks come from 56 user story. It
seems that 56 is a large number but in our system, it is preferred to gather a large number of tasks
to increase accuracy. The overall work takes 800 working hours. The productivity comes equal to
50% and the defects are 10% based on the user's opinions collected from prepared survey. That
leads to company satisfaction equal to 95.2%.
16. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
32
Table 4. Definition of the criteria of evaluation
Table 5. The results of evaluating the three conducted Case Studies
As shown in the results, the performance of the projects is calculated by dividing the total effort
of the entire project over total work hours. We can say that using the hybrid method HyArchive is
much better for customers than using XP or scrum.This is because by comparing the value 51 %
(for HyArchive method) with the value of scrum 41 % or XP 44 %, it is correct to use the hybrid
method that gives a value much close to the value resulted from each individual method. The
performance of the project is calculated by the following equation:
Project performance =
total effort of the entire project
total work hours
(1)
17. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
33
Table 6. Comparison between the existence of traditional techniques methods HyArchieve, Scrum, and XP
methods
Table 7 and Table 8show that HyArchive was conducted by a set of requirements equal to 16.
At least 2 users participate in any requirement. The effort is the amount of work unit required to
complete any given task. The effort done for each requirement was 42.77 unit of work, the effort
done for each user story is 27.3 unit of work and this number is the mean of the values that
represent the unit of works in each iteration. Total effort is calculated as the result of adding effort
per requirement and the other efforts.
Table 7. The Data description of the three conducted Case Studies
18. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
34
Table 8. Results of evaluating the three conducted Case Studies
Table 9. Comparison between the three used Methodologies
CONCLUSION
We have proposed a new Agile methodology for building archiving system that tries to fill gaps
in agile and guarantee the high-quality archiving system. It is called HyArchive: Hybrid Agile
Archiving Technique. HyArchive merges between most known agile methodologies named
extreme programming (XP) and SCRUM. The technique is implemented to reduce the time and
effort consumed during analyzing and designing the archiving systems. The proposed
methodology reduce the system errors happen at the early stages of the development of the
system. HyArchive helps the organizations in designing their archiving system that satisfies their
needs in minimum time and effort. Hyarchive was implemented and compared to other
19. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
35
methodologies Scrum and XP and show a superior performance.It depends on values of courage,
correspondence, criticism, simplicity, adaptability, flexibility, and efficiency.As shown in the
results, using the hybrid method HyArchive is much better for customers than using XP or scrum
as it gives 51 % performance of the project using HyArchive method) with the performance of the
project while scrum gives 41 % performance and XP gives 44 %. The Hyarchive show a
beneficial use in requirement engineering process to build archiving systems for governmental
institutions.
REFERENCES
[1] Nuseibeh, B.; Easterbrook, S. Requirements engineering: a roadmap. ICSE'00. Proceedings of the
conference on the future of Software engineering. pp. 35–46, 2000.
[2] Kotonya, Gerald; Sommerville, Ian (September 1998). Requirements Engineering: Processes and
Techniques. John Wiley & Sons, 1998.
[3] Chemuturi, M. (2013). Requirements Engineering and Management for Software Development
Projects, 2013.
[4] Sriram,RandMathew,S.K Global Software Development Using Agile Methodologies: A Review of
Literature. 2012 IEEE International Conference on Man- agement of Innovation and Technology,
Bali, 2012.
[5] Medhat, W, Fouad, KM, Yousef, AH, and Moawad, IF, published in 12th international conference of
Computer Engineering and Systems (ICCES), 2017
[6] ManjulGuptaa, Joey F. Georgeb, andWeidongXiaa, “Relationships between IT department culture
and agile software development practices: An empirical investigation”, “International Journal of
Information Management44 (2019) 13–24”, 2019.
[7] Pacheco, C., and Garcia, I. A systematic literature review of stakeholder identification methods in
requirements elicitation. Journal of Systems and Software, 85(9), 2171-2181, 2012.
[8] Amani Mahdi Mohammed, Hisham Mohamed Abushama, “Popular Agile Approaches in Software
Development: Review and Analysis”, Researchgate Conference Paper • August 2013.
[9] Shen, H., Wall, B., Zaremba, M., Chen, Y., & Browne, J. Integration of business modelling methods
for enterprise information system analysis and user requirements gathering. Computers in Industry,
54(3), 307-323, 2014.
[10] Mohammad Almseidin, Khaled Alrfou’2, Nidal Alnidami3 and Ahmed Tarawneh, “A Comparative
Study of Agile Methods: XP versus SCRUM ”, International Journal of Computer Science and
Software Engineering (IJCSSE), Volume 4, Issue 5, May 2015
[11] Khaleel, Y., Abuhamdah, A., Sara, M. A., & Al-Tamimi, B. Components and Analysis Method of
Enterprise Resource Planning (ERP) Requirements in Small and Medium Enterprises (SMEs).
International Journal of Electrical and Computer Engineering, 6(2), 682, 2016.
[12] Farrukh Musa, and Muhammad Ali Tariq, “Agile Methodology: Hybrid Approach Scrum and XP ”,
International Journal of Scientific & Engineering Research, Volume 8, Issue 4, April-2017.
[13] Ankita Sharma, and Manav Bali, “Comparative Study on Software Development Methods: Agile vs
Scrum ”, International Journal of Emerging Research in Management &Technology, June 2017.
[14] Apoorva Singh and Dhirendra Pandey, “Implementation of Requirement Engineering in Extreme
Programing and SCRUM ”, International Journal of Advanced Research in Computer Science
Volume 8, No. 5, May – June 2017.
20. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.1, January 2019
36
[15] Sara Ashraf, Shabib Aftab, “Scrum with the Spices of Agile Family: A Systematic Mapping”, I.J.
Modern Education and Computer Science, 2017.
[16] Julio Cesar Pereiraa, and Rosaria de F. S. M. Russoa, “Design Thinking Integrated in Agile Software
Development: A Systematic Literature Review”, “international Conference on Project Management /
HCist– International Conference on Health and Social Care Information Systems and Technologies”,
2018.
[17] Sultania, A. K. (2015, February). Developing software product and test automation software using
Agile methodology. In Proceedings of the 2015 Third International Conference on Computer,
Communication, Control and Information Technology (C3IT) (pp. 1-4). IEEE.
[18] Kniberg, H. (2015). Scrum and XP from the Trenches. Lulu. com.
[19] Kevin Thompson, Ph.D. “How to Estimate Capacity for Work in Agile Teams”, 2012.