The document discusses a study of the adoption of agile practices in three telecommunications companies in Jordan. It finds that:
1) The companies used some agile practices like continuous integration and collective code ownership but did not follow full agile methodologies.
2) Adoption levels varied across practices and companies, with measurement by working code and coding standards seeing higher adoption.
3) Experiences with practices were mixed, with benefits seen in visibility of progress but challenges in refactoring large code bases.
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.
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.
The document describes a new methodology for eliciting software requirements for smart handheld devices. The methodology is focused on users' work processes. It involves observing users' activities, identifying stakeholders, discussing requirements with stakeholders, finding inspiration from other software, and brainstorming user needs and goals. As an example, the methodology is applied to develop an iPad-based software for improving the learning performance of playgroup students.
Requirement Elicitation Model (REM) in the Context of Global Software Develop...IJAAS Team
Contxext:Requirement elicitation is difficult and critical phase of requirement engineering and the case is worst in global software development (GSD). The study is about requirement elicitation in the context of GSD. Objective: Development of requirement elicitation model (REM) which can address the factors that have positive impact and the factors that have negative impact during elicitation in GSD. The propose model will give solutions and practices to the challenges during elicitation. Method: Systematic literature review (SLR) and empirical research study will be used for achieving the goals and objectives. Expected outcomes: The expected results of this study will be REM that will help vendor organizations for better elicitation during GSD.
IRJET- Factors in Selection of Construction Project Management Software i...IRJET Journal
The document discusses factors to consider when selecting construction project management software in India. It conducted interviews with 15 experts in the construction industry with experience ranging from 5-30 years. The interviews aimed to understand the software selection process. Based on the literature review and interviews, the document proposes a model for software selection with 8 steps: 1) identify software options, 2) review organization policies, 3) analyze the project's needs, 4) analyze the client's needs, 5) inquire the purpose of planning, 6) analyze software performance and price, 7) check available skills, and 8) select and use software. The model categorizes factors as either project specific or general to guide effective software selection.
Survey Based Reviewof Elicitation ProblemsIJERA Editor
Any software development process is the combination of multiple development activities and each activity has a
vital role in the software development cycle. Requirement Engineering is the main and basic branch of Software
Engineering, it has many phases but the most initial phase is Requirement Elicitation. In this phase requirements
are gathered for system development.
This paper provides a literature review of the requirements engineering processes performed in traditional and
modern development processes and analyses the problems in the requirements elicitation phase. This problem
analysis is based on a survey which was conducted in University. A questionnaire posing questions regarding
the problems in requirement elicitation was given to final year computer science graduate students who are
working on their final year project as a requirement for their degree. The theoretical analysis of the
questionnaire further clarifies the problems. This problems analysis will help to find out the main problems
which are faced by the perspective software developers
This document summarizes a thesis review on the practices and challenges of implementing agile software development methodology at Ethiopian Airlines. The research studied agile practices through surveys of 72 IT developers and interviews with managers. It found that while agile has benefits, Ethiopian Airlines faces challenges including lack of formal training, awareness issues, documentation problems, and difficulty forming self-organized teams. The researchers proposed a "Task based agile development methodology" guideline to address the challenges and help full adoption of agile. However, the study was limited to one organization and had a small data set.
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.
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.
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.
The document describes a new methodology for eliciting software requirements for smart handheld devices. The methodology is focused on users' work processes. It involves observing users' activities, identifying stakeholders, discussing requirements with stakeholders, finding inspiration from other software, and brainstorming user needs and goals. As an example, the methodology is applied to develop an iPad-based software for improving the learning performance of playgroup students.
Requirement Elicitation Model (REM) in the Context of Global Software Develop...IJAAS Team
Contxext:Requirement elicitation is difficult and critical phase of requirement engineering and the case is worst in global software development (GSD). The study is about requirement elicitation in the context of GSD. Objective: Development of requirement elicitation model (REM) which can address the factors that have positive impact and the factors that have negative impact during elicitation in GSD. The propose model will give solutions and practices to the challenges during elicitation. Method: Systematic literature review (SLR) and empirical research study will be used for achieving the goals and objectives. Expected outcomes: The expected results of this study will be REM that will help vendor organizations for better elicitation during GSD.
IRJET- Factors in Selection of Construction Project Management Software i...IRJET Journal
The document discusses factors to consider when selecting construction project management software in India. It conducted interviews with 15 experts in the construction industry with experience ranging from 5-30 years. The interviews aimed to understand the software selection process. Based on the literature review and interviews, the document proposes a model for software selection with 8 steps: 1) identify software options, 2) review organization policies, 3) analyze the project's needs, 4) analyze the client's needs, 5) inquire the purpose of planning, 6) analyze software performance and price, 7) check available skills, and 8) select and use software. The model categorizes factors as either project specific or general to guide effective software selection.
Survey Based Reviewof Elicitation ProblemsIJERA Editor
Any software development process is the combination of multiple development activities and each activity has a
vital role in the software development cycle. Requirement Engineering is the main and basic branch of Software
Engineering, it has many phases but the most initial phase is Requirement Elicitation. In this phase requirements
are gathered for system development.
This paper provides a literature review of the requirements engineering processes performed in traditional and
modern development processes and analyses the problems in the requirements elicitation phase. This problem
analysis is based on a survey which was conducted in University. A questionnaire posing questions regarding
the problems in requirement elicitation was given to final year computer science graduate students who are
working on their final year project as a requirement for their degree. The theoretical analysis of the
questionnaire further clarifies the problems. This problems analysis will help to find out the main problems
which are faced by the perspective software developers
This document summarizes a thesis review on the practices and challenges of implementing agile software development methodology at Ethiopian Airlines. The research studied agile practices through surveys of 72 IT developers and interviews with managers. It found that while agile has benefits, Ethiopian Airlines faces challenges including lack of formal training, awareness issues, documentation problems, and difficulty forming self-organized teams. The researchers proposed a "Task based agile development methodology" guideline to address the challenges and help full adoption of agile. However, the study was limited to one organization and had a small data set.
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.
The Impact of In-House Software Development Practices on System Usability in ...IJMIT JOURNAL
In-house software development is a critical phenomenon for the production of efficient and effective
software in generating requisite job output. A few studies have devoted efforts towards establishing the
impact of in-house software development on software. Therefore, this paper is an effort towards
establishing the impact of in-house software development practices on system usability. In pursuit of this
paper, a sample of a sample size of 169, at 95% confidence level, with margin error of 5% was drawn from
bold software users, i.e. 300 employees who used the all software including those dealing with the main
stream activities. A total of 102 respondents actually responded to the questionnaires. The Online Sample
Calculator was used to draw the sample. Quantitative data were collected using semi-structured
questionnaires and processed using the SPSS. Descriptive statistics were applied in the analysis. Findings
of the study indicate that software development practices, specifically usability test and user involvement in
software designing and development had an impact on determining software usability for in-house
software. The paper concludes that software development practices shape the design of the software; hence
influence usability of the software produced. Recommended is therefore that software usability test and
user involvement in software designing and development be promoted for effective software production
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.
A FRAMEWORK FOR INTEGRATING USABILITY PRACTICES INTO SMALL-SIZED SOFTWARE DEV...ijseajournal
Usability now appears to be a highly important attribute for software quality; it is a critical factor that
needs to be considered by every software-development organization when developing software to improve
customer satisfaction and increase competition in the market. There exists a lack of a reference model or
framework for small-sized software-development organizations to indicate which usability practices should
be implemented, and where in the system-development life cycle they need to be considered. We offer
developers who have the objective of integrating usability practices into their development life cycle a
framework that characterizes 10 selected user-centered design (UCD) methods in relation to five relevant
criteria based on some ISO factors that have an effect on the selection of methods (ISO/TR16982). The
selection of the methods for inclusion in the framework responds to these organizations’ needs; and we
selected basic methods that are recommended, cost-effective, simple to plan and apply, and easy to learn by
developers; and which can be applied when time, resources, skills, and expertise are limited. We favor
methods that are generally applicable across a wide range of development environments. The selected
methods are organized in the framework according to the stages in the development process where they
might be applied. The only requirement for the existing development life cycle is that it to be based on an
iterative approach.
This document summarizes research on factors that contribute to the success of software projects. It discusses functional requirements, operational quality, and usability. The introduction provides background on the importance of quality management and identifies reasons why software projects fail. The literature review then summarizes several studies that have examined how reliability, response time, usability, and meeting user requirements impact project success. Finally, the document discusses the need to balance functionality and usability through various design and testing approaches.
Running head finding employment as a java developer DIPESH30
This document outlines an action research methodology to help the author find employment as a Java developer. It discusses how action research is collaborative and cyclical in nature, involving planning, action, observation, and reflection. The author believes action research is well-suited for this project because it allows input from other professionals and repetition until goals are achieved. Action research will also help the author develop practical skills and perspectives to make effective career decisions.
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.
The document discusses the context of global software development (GSD), highlighting key challenges, best practices, and benefits based on a review of past research. Some major challenges of GSD include poor communication, lack of trust and coordination due to factors like cultural and time zone differences. Establishing trust between client and vendor organizations is important. The review also identifies best practices for GSD, such as cultural understanding and clear development processes. Benefits of GSD include lower costs, faster delivery, and access to skilled resources globally, though issues remain that more research is needed to address challenges on the vendor side of GSD relationships.
Running head kotter’s model 1 kotter’s model 6DIPESH30
This case study examines how Ericsson, a leading provider of information and communication technology, implemented changes using Kotter's 8-step change model. It details how Ericsson created a sense of urgency around transitioning to 4G technology, formed a guiding coalition to lead the change, and communicated a clear vision. Ericsson also empowered employees by providing training, planned short-term wins to maintain motivation, and consolidated improvements to institutionalize the new approaches. Implementing Kotter's full model helped Ericsson successfully transition to 4G while maintaining its customer focus and shared values.
Software requirements prioritization is a
recognized practice in requirements engineering (RE)
that facilitates the management of stakeholders’
subjective views as specified in their requirements
listing. Since RE process is naturally collaborative in
nature, the intensiveness from both knowledge and
human perspectives opens up the problem of decision
making on requirements, which can be facilitated by
requirements prioritization. However, due to the large
volume of requirements elicited when considering an
ultra-large-scale system, existing prioritization
techniques proposed so far suffer some setbacks in
terms of efficiency, effectiveness and scalability. This
paper employed the use of a more efficient ranking
algorithm for requirements prioritization based on the
limitations of existing techniques. The major objective
is to provide a well-defined ranking procedure through
analysis, suitable for prioritizing software requirements.
An empirical evaluation of the proposed technique was
made using a typical scenario of the Pharmacy
Information System at the Obafemi Awolowo
University Teaching Hospital Complex (OAUTHC) as a
case study. The results showed the computation of the
positive ideal solution (PIS) and negative ideal solution
(NIS), as well as the closeness coefficient (CC) for 4
requirements across 3 stakeholders. The CC showed the
final ranks of requirements, where R4 with 2.09 point is
the most valued requirements, while R1 and R2 with
CC of 1.37 and 1.05 were next in the order of priority
respectively. The CC provides the medium through
which problems of multiple criteria decision making
can be handled, so as to determine the order of priority
of the available alternatives. The paper conveyed
encouraging evidence for the software engineering
community that is capable of resolving redundant
specified requirements, thereby providing the potential
that will facilitate effective and efficient decision
making in handling the differences amongst
requirements that have been prioritized. Thus,
prioritizing software requirements with the
recommended ranking procedure during software
development is crucial and vital in order to reduce
development cost.
Running head cyber security competition framework cyber securiDIPESH30
This document proposes a cyber security competition framework using action research. It discusses action research methodology, which involves planning, taking action, observing results, and reflecting to improve solutions in iterative cycles. The framework aims to address cyber threats by protecting vital business assets and data, rather than just technological vulnerabilities. It will reorient security from devices/locations to roles and data, and introduce approaches to manage evolving business needs and threats. Implementing the cyber competition program through action research ensures the solutions framework continually improves after each research cycle.
The document discusses a study on the need for a rating system for software quality. It notes that while software quality has been extensively studied, there has been little research into explicitly rating software quality. The study aims to review previous literature and develop the scope for a rating system to provide more information to end-users. It outlines some key metrics considered in software quality like complexity, efficiency, functionality and maintainability. The document includes a graph showing the evolution of software quality research over time and a flowchart depicting the software quality assurance and development process.
Performance Evaluation of Software Quality ModelEditor IJMTER
With the advent of Internet revolution and the emergence of knowledge based systems, Quality acquires a wider
and more challenging dimension. Quality has evolved and undergone transformation from the inspection era to
the quality control regime and then to quality management and finally to the present TQM approach. At every
stage of the transformation “Quality” has been attaining wider dimension with respect to Customer focus,
continual improvement and has been evolving for addressing increasing demands of customers with respect to
delivery of products and services.
A Guideline Tool for Ongoing Product Evaluation in Small and Medium-Sized Ent...IJECEIAES
As consumer demand for user friendly software increases, usability evaluation is crucial to develop software systems which are easy to learn and use. However, implementation of usability evaluation is challenging for small and medium-sized enterprises (SMEs) due to factors such as lack of technical expertise, knowledge and experience of methods and standards. This results in neglect, or poorly executed evaluations of projects, resulting in software that disappoints and frustrates clients. To overcome this loss of competitiveness, we propose here a visual incorporation tool derived from ISO standards that would assist software development teams in SMEs in understanding and implementing usability evaluations. It shows fundamental Usability Engineering (UE) and Software Engineering (SE) activities and artifacts relevant to the usability evaluation and software development process, with potential incorporation points being highlighted. Dependencies and relationships are shown by links between activities and artifacts. Additionally, convergent artifacts of both disciplines were identified and shown. Evaluation of the proposed tool was based on the questionnaire results of software development practitioners from SMEs.
This document discusses the hurdles and enablers to adopting software product line practices in large corporate organizations, specifically large banks. It identifies some key hurdles including: different business units perceiving little return on investment for cross-unit product lines; and difficulties motivating investment and changing funding models. It proposes some enabling mechanisms that are showing positive results, such as aligning product lines with strategic business goals and establishing executive sponsorship. Large banks present additional challenges to product line adoption due to their multiple divisions, legacy systems, and focus on short-term profits over long-term IT strategies.
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.
REGULARIZED FUZZY NEURAL NETWORKS TO AID EFFORT FORECASTING IN THE CONSTRUCTI...ijaia
Predicting the time to build software is a very complex task for software engineering managers. There are complex factors that can directly interfere with the productivity of the development team. Factors directly related to the complexity of the system to be developed drastically change the time necessary for the completion of the works with the software factories. This work proposes the use of a hybrid system based on artificial neural networks and fuzzy systems to assist in the construction of an expert system based on rules to support in the prediction of hours destined to the development of software according to the complexity of the elements present in the same. The set of fuzzy rules obtained by the system helps the management and control of software development by providing a base of interpretable estimates based on fuzzy rules. The model was submitted to tests on a real database, and its results were promissory in the construction of an aid mechanism in the predictability of the software construction
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.
7.significance of software layered technology on size of projects (2)EditorJST
The objective of the software engineering is committed to build software projects within the budget, time and required quality. Software engineering is a layered paradigm comprised of process, methods, tools and quality focus as bedrock to develop the product. Software firms build software projects of varying sizes constrained on resources, time and functional requirement. Impact of software engineering layered technology may vary according to the size of the projects during their development. Quantitative evaluation of layer significance on size of the software project could be categorized as a complex task because it involves a collective decision on multiple criteria. Analytic Hierarchy Process (AHP) provides an effective quantitative approach for finding the significance of software layered technology on size of the projects. This paper presents the estimations through quantitative approach on real time data collected from several software firms. These findings help for a better project management with respect to the cost, time and resources during building a software project.
Extreme Programming (XP) is an agile methodology widely used for software development. However, XP is not as effective for medium and large projects due to weaknesses like poor documentation and lack of risk awareness. This paper reviews several studies on adapting XP for different project sizes through practices like extended planning, architecture design, and risk management. Case studies show the adapted XP approach can provide benefits to medium and large projects similar to what standard XP delivers for small projects.
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 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
EuroSPI O'Donnell Richardson Agile Methods in a Very Small CompanyMichael O'Donnell
This document discusses a case study of implementing agile methods at a small Irish software company called Sporting Software Ltd. The company tried implementing Extreme Programming (XP), an agile method, but ultimately declared it a failure. Some of the key problems encountered were lack of management support for agile methods and pre-existing employment contracts that did not align with agile values. The case study highlights that implementing agile methods can be challenging for small, remotely located companies.
The Impact of In-House Software Development Practices on System Usability in ...IJMIT JOURNAL
In-house software development is a critical phenomenon for the production of efficient and effective
software in generating requisite job output. A few studies have devoted efforts towards establishing the
impact of in-house software development on software. Therefore, this paper is an effort towards
establishing the impact of in-house software development practices on system usability. In pursuit of this
paper, a sample of a sample size of 169, at 95% confidence level, with margin error of 5% was drawn from
bold software users, i.e. 300 employees who used the all software including those dealing with the main
stream activities. A total of 102 respondents actually responded to the questionnaires. The Online Sample
Calculator was used to draw the sample. Quantitative data were collected using semi-structured
questionnaires and processed using the SPSS. Descriptive statistics were applied in the analysis. Findings
of the study indicate that software development practices, specifically usability test and user involvement in
software designing and development had an impact on determining software usability for in-house
software. The paper concludes that software development practices shape the design of the software; hence
influence usability of the software produced. Recommended is therefore that software usability test and
user involvement in software designing and development be promoted for effective software production
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.
A FRAMEWORK FOR INTEGRATING USABILITY PRACTICES INTO SMALL-SIZED SOFTWARE DEV...ijseajournal
Usability now appears to be a highly important attribute for software quality; it is a critical factor that
needs to be considered by every software-development organization when developing software to improve
customer satisfaction and increase competition in the market. There exists a lack of a reference model or
framework for small-sized software-development organizations to indicate which usability practices should
be implemented, and where in the system-development life cycle they need to be considered. We offer
developers who have the objective of integrating usability practices into their development life cycle a
framework that characterizes 10 selected user-centered design (UCD) methods in relation to five relevant
criteria based on some ISO factors that have an effect on the selection of methods (ISO/TR16982). The
selection of the methods for inclusion in the framework responds to these organizations’ needs; and we
selected basic methods that are recommended, cost-effective, simple to plan and apply, and easy to learn by
developers; and which can be applied when time, resources, skills, and expertise are limited. We favor
methods that are generally applicable across a wide range of development environments. The selected
methods are organized in the framework according to the stages in the development process where they
might be applied. The only requirement for the existing development life cycle is that it to be based on an
iterative approach.
This document summarizes research on factors that contribute to the success of software projects. It discusses functional requirements, operational quality, and usability. The introduction provides background on the importance of quality management and identifies reasons why software projects fail. The literature review then summarizes several studies that have examined how reliability, response time, usability, and meeting user requirements impact project success. Finally, the document discusses the need to balance functionality and usability through various design and testing approaches.
Running head finding employment as a java developer DIPESH30
This document outlines an action research methodology to help the author find employment as a Java developer. It discusses how action research is collaborative and cyclical in nature, involving planning, action, observation, and reflection. The author believes action research is well-suited for this project because it allows input from other professionals and repetition until goals are achieved. Action research will also help the author develop practical skills and perspectives to make effective career decisions.
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.
The document discusses the context of global software development (GSD), highlighting key challenges, best practices, and benefits based on a review of past research. Some major challenges of GSD include poor communication, lack of trust and coordination due to factors like cultural and time zone differences. Establishing trust between client and vendor organizations is important. The review also identifies best practices for GSD, such as cultural understanding and clear development processes. Benefits of GSD include lower costs, faster delivery, and access to skilled resources globally, though issues remain that more research is needed to address challenges on the vendor side of GSD relationships.
Running head kotter’s model 1 kotter’s model 6DIPESH30
This case study examines how Ericsson, a leading provider of information and communication technology, implemented changes using Kotter's 8-step change model. It details how Ericsson created a sense of urgency around transitioning to 4G technology, formed a guiding coalition to lead the change, and communicated a clear vision. Ericsson also empowered employees by providing training, planned short-term wins to maintain motivation, and consolidated improvements to institutionalize the new approaches. Implementing Kotter's full model helped Ericsson successfully transition to 4G while maintaining its customer focus and shared values.
Software requirements prioritization is a
recognized practice in requirements engineering (RE)
that facilitates the management of stakeholders’
subjective views as specified in their requirements
listing. Since RE process is naturally collaborative in
nature, the intensiveness from both knowledge and
human perspectives opens up the problem of decision
making on requirements, which can be facilitated by
requirements prioritization. However, due to the large
volume of requirements elicited when considering an
ultra-large-scale system, existing prioritization
techniques proposed so far suffer some setbacks in
terms of efficiency, effectiveness and scalability. This
paper employed the use of a more efficient ranking
algorithm for requirements prioritization based on the
limitations of existing techniques. The major objective
is to provide a well-defined ranking procedure through
analysis, suitable for prioritizing software requirements.
An empirical evaluation of the proposed technique was
made using a typical scenario of the Pharmacy
Information System at the Obafemi Awolowo
University Teaching Hospital Complex (OAUTHC) as a
case study. The results showed the computation of the
positive ideal solution (PIS) and negative ideal solution
(NIS), as well as the closeness coefficient (CC) for 4
requirements across 3 stakeholders. The CC showed the
final ranks of requirements, where R4 with 2.09 point is
the most valued requirements, while R1 and R2 with
CC of 1.37 and 1.05 were next in the order of priority
respectively. The CC provides the medium through
which problems of multiple criteria decision making
can be handled, so as to determine the order of priority
of the available alternatives. The paper conveyed
encouraging evidence for the software engineering
community that is capable of resolving redundant
specified requirements, thereby providing the potential
that will facilitate effective and efficient decision
making in handling the differences amongst
requirements that have been prioritized. Thus,
prioritizing software requirements with the
recommended ranking procedure during software
development is crucial and vital in order to reduce
development cost.
Running head cyber security competition framework cyber securiDIPESH30
This document proposes a cyber security competition framework using action research. It discusses action research methodology, which involves planning, taking action, observing results, and reflecting to improve solutions in iterative cycles. The framework aims to address cyber threats by protecting vital business assets and data, rather than just technological vulnerabilities. It will reorient security from devices/locations to roles and data, and introduce approaches to manage evolving business needs and threats. Implementing the cyber competition program through action research ensures the solutions framework continually improves after each research cycle.
The document discusses a study on the need for a rating system for software quality. It notes that while software quality has been extensively studied, there has been little research into explicitly rating software quality. The study aims to review previous literature and develop the scope for a rating system to provide more information to end-users. It outlines some key metrics considered in software quality like complexity, efficiency, functionality and maintainability. The document includes a graph showing the evolution of software quality research over time and a flowchart depicting the software quality assurance and development process.
Performance Evaluation of Software Quality ModelEditor IJMTER
With the advent of Internet revolution and the emergence of knowledge based systems, Quality acquires a wider
and more challenging dimension. Quality has evolved and undergone transformation from the inspection era to
the quality control regime and then to quality management and finally to the present TQM approach. At every
stage of the transformation “Quality” has been attaining wider dimension with respect to Customer focus,
continual improvement and has been evolving for addressing increasing demands of customers with respect to
delivery of products and services.
A Guideline Tool for Ongoing Product Evaluation in Small and Medium-Sized Ent...IJECEIAES
As consumer demand for user friendly software increases, usability evaluation is crucial to develop software systems which are easy to learn and use. However, implementation of usability evaluation is challenging for small and medium-sized enterprises (SMEs) due to factors such as lack of technical expertise, knowledge and experience of methods and standards. This results in neglect, or poorly executed evaluations of projects, resulting in software that disappoints and frustrates clients. To overcome this loss of competitiveness, we propose here a visual incorporation tool derived from ISO standards that would assist software development teams in SMEs in understanding and implementing usability evaluations. It shows fundamental Usability Engineering (UE) and Software Engineering (SE) activities and artifacts relevant to the usability evaluation and software development process, with potential incorporation points being highlighted. Dependencies and relationships are shown by links between activities and artifacts. Additionally, convergent artifacts of both disciplines were identified and shown. Evaluation of the proposed tool was based on the questionnaire results of software development practitioners from SMEs.
This document discusses the hurdles and enablers to adopting software product line practices in large corporate organizations, specifically large banks. It identifies some key hurdles including: different business units perceiving little return on investment for cross-unit product lines; and difficulties motivating investment and changing funding models. It proposes some enabling mechanisms that are showing positive results, such as aligning product lines with strategic business goals and establishing executive sponsorship. Large banks present additional challenges to product line adoption due to their multiple divisions, legacy systems, and focus on short-term profits over long-term IT strategies.
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.
REGULARIZED FUZZY NEURAL NETWORKS TO AID EFFORT FORECASTING IN THE CONSTRUCTI...ijaia
Predicting the time to build software is a very complex task for software engineering managers. There are complex factors that can directly interfere with the productivity of the development team. Factors directly related to the complexity of the system to be developed drastically change the time necessary for the completion of the works with the software factories. This work proposes the use of a hybrid system based on artificial neural networks and fuzzy systems to assist in the construction of an expert system based on rules to support in the prediction of hours destined to the development of software according to the complexity of the elements present in the same. The set of fuzzy rules obtained by the system helps the management and control of software development by providing a base of interpretable estimates based on fuzzy rules. The model was submitted to tests on a real database, and its results were promissory in the construction of an aid mechanism in the predictability of the software construction
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.
7.significance of software layered technology on size of projects (2)EditorJST
The objective of the software engineering is committed to build software projects within the budget, time and required quality. Software engineering is a layered paradigm comprised of process, methods, tools and quality focus as bedrock to develop the product. Software firms build software projects of varying sizes constrained on resources, time and functional requirement. Impact of software engineering layered technology may vary according to the size of the projects during their development. Quantitative evaluation of layer significance on size of the software project could be categorized as a complex task because it involves a collective decision on multiple criteria. Analytic Hierarchy Process (AHP) provides an effective quantitative approach for finding the significance of software layered technology on size of the projects. This paper presents the estimations through quantitative approach on real time data collected from several software firms. These findings help for a better project management with respect to the cost, time and resources during building a software project.
Extreme Programming (XP) is an agile methodology widely used for software development. However, XP is not as effective for medium and large projects due to weaknesses like poor documentation and lack of risk awareness. This paper reviews several studies on adapting XP for different project sizes through practices like extended planning, architecture design, and risk management. Case studies show the adapted XP approach can provide benefits to medium and large projects similar to what standard XP delivers for small projects.
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 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
EuroSPI O'Donnell Richardson Agile Methods in a Very Small CompanyMichael O'Donnell
This document discusses a case study of implementing agile methods at a small Irish software company called Sporting Software Ltd. The company tried implementing Extreme Programming (XP), an agile method, but ultimately declared it a failure. Some of the key problems encountered were lack of management support for agile methods and pre-existing employment contracts that did not align with agile values. The case study highlights that implementing agile methods can be challenging for small, remotely located companies.
AN ITERATIVE HYBRID AGILE METHODOLOGY FOR DEVELOPING ARCHIVING SYSTEMSijseajournal
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.
AN ITERATIVE HYBRID AGILE METHODOLOGY FOR DEVELOPING ARCHIVING SYSTEMSijseajournal
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.
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.
The document summarizes and compares two software development methods: Dynamic Systems Development Method (DSDM) and Rapid Application Development (RAD). It provides an overview of the characteristics and principles of DSDM, including that it is more suitable for in-house and market-driven projects rather than contract-driven projects. The major weakness is that requirements are loosely defined and it is difficult to plan. However, the major strength is that the end products fit business needs well since users are heavily involved. It also briefly summarizes RAD and identifies some similarities and differences between the two methods.
HYBRID PRACTICES IN GLOBAL SOFTWARE DEVELOPMENT: A SYSTEMATIC LITERATURE REVIEWijseajournal
Although agile methods in their purest way fit several companies, it has been a challenge to perform them in environments with distributed teams developing large software applications. Contractual items, for projects under development for external organizations, introduce additional complexities for pure agilebased approaches. The majority of global teams and companies use hybrid development practices that combine different development methods and frameworks. This research provides results from an empirical field study on how the hybrids practices are adopted in Global Software Development (GSD) projects. A systematic literature review was conducted to capture the status of combining agile with plan-driven in GSD projects. The results were limited to peer-reviewed conference papers or journal articles, published between 2001 and 2020. The present study selected 37 papers from five different bibliographic databases. In the end, 16 practices were summarized and described as hybrid by GSD projects. Based on the findings of this study, the authors can conclude that the contribution of this study is not only limited to identifying how hybrid development practices are applied in GSD but also allowing that practitioners can have a basis for adapting their development methods.
Using Machine Learning embedded in Organizational Responsibility Model, added to the ten characteristics of the CIO Master and the twelve competencies of the workforce can help lead the Digital Transformation of the traditional public organizations to the Exponential.
Maturity modle proposal v1 networked business quickversionJan Kwiecien
The document proposes a maturity model framework for surveying companies' use of emerging technologies. The framework assesses companies across four dimensions - governance, organizational anchoring, business view, and technology - at five levels of maturity from initial to innovative. Each level is defined by characteristics within the four dimensions. The framework draws inspiration from literature on process maturity models and aims to understand how companies employ technologies to support business goals and how their usage can be measured.
A Comparative Analysis Of Various Methodologies Of Agile Project Management V...Brittany Allen
This document provides a comparative analysis of project management methodologies, specifically comparing the Project Management Body of Knowledge (PMBOK) and various agile project management approaches. It first describes the key processes and knowledge areas of PMBOK. It then outlines some popular agile methodologies like Scrum, Extreme Programming (XP), and Feature Driven Development (FDD). The document aims to identify similarities and differences between the traditional PMBOK framework and more flexible agile approaches.
This document summarizes the results of an online survey about factors influencing the adoption of agile practices. The survey received 103 responses. Based on the results, the authors hypothesized that: 1) Extreme Programming is the most popular adopted agile methodology. 2) Agile methodologies are chosen more by small teams. 3) Direct interaction with stakeholders is the most effective way to gather requirements. 4) User stories and diagrams are commonly used to capture requirements in agile. 5) Agile gives higher access to stakeholders to resolve problems quickly. 6) Adopting agile increases customer satisfaction and productivity. The survey results provide preliminary support for these hypotheses.
International Journal of Computational Engineering Research(IJCER)ijceronline
International Journal of Computational Engineering Research(IJCER) is an intentional online Journal in English monthly publishing journal. This Journal publish original research work that contributes significantly to further the scientific knowledge in engineering and Technology.
AGILE OR PLAN-DRIVEN SOFTWARE DEVELOPMENT METHODOLOGY SELECTION USING PERSON...Kaela Johnson
This document discusses a research paper that investigated how the personality traits of software developers, as measured by the Big Five personality dimensions, can predict their suitability for either plan-driven or agile software development methodologies. The researchers analyzed how traits like extraversion and agreeableness relate to a developer's interest in either methodology. Understanding personality traits could help match developers to the methodology and development team best suited to their skills and working style, potentially improving software project success rates.
The result of applying a new testing model for improving the quality of softw...amiraiti
This paper shows the result of applying a new testing model which provides the know-how for performing the different activities covered in the test process for functional testing. It was noticed that the customer risks experienced during examining the accuracy of software used in different business sectors are not the main focus of the Quality Control team members. Moreover there are no standard testing techniques used by the team members during creating the test conditions and test cases, the result is a lot of reworks.
A PROPOSED HYBRID AGILE FRAMEWORK MODEL FOR MOBILE APPLICATIONS DEVELOPMENT ijseajournal
With the increasing in mobile application systems and a high competition between companies, that led to
increase in the number of mobile application projects.
Mobile software development is a group of process for creating software for mobile devices with limited
resources like small screen, low-power. The development of mobile applications is a big challenging
because of rapidly changing business requirements and technical constraints for mobile systems. So,
developers faced the challenge of a dynamic environment and the Changing of mobile application
requirements. Moreover, Mobile applications should adapt appropriate software development methods that
act in response efficiently to these challenges.
However, at the moment, there is limited knowledge about the suitability of different software practices for
the development of mobile applications. According to many researchers ,Agile methodologies was found to
be most suitable for mobile development projects as they are short time, require flexibility, reduces waste
and time to market.
Finally, in this research we are looking for a suitable process model that conforms to the requirement of
mobile application, we are going to investigate agile development methods to find a way, making the
development of mobile application easy and compatible with mobile device features.
Today in era of software industry there is no perfect software framework available for
analysis and software development. Currently there are enormous number of software development
process exists which can be implemented to stabilize the process of developing a software system. But no
perfect system is recognized till yet which can help software developers for opting of best software
development process. This paper present the framework of skillful system combined with Likert scale. With
the help of Likert scale we define a rule based model and delegate some mass score to every process and
develop one tool name as MuxSet which will help the software developers to select an appropriate
development process that may enhance the probability of system success.
The agile software development methods have demonstrated success in increasing responsiveness to the needs of customers. So the most of software industry preferred the agile methods. These methods have
increased demand by the companies, but the agile methods at larger scale are more challenging and
problematic compared to the smaller projects. For that, to become the norm for a large and complex project a new adaptive agile framework is proposed. Also, the proposed framework will help to achieve long-term organizational and learning of agile teams and help to increase the employee motivation and satisfaction by improving their skill. Thus the organizations will have success in sustaining their team and increasing its productivity.
An Exploratory Study of Usability Practice from User-Centered Design View: M...Ruby Kuo
The document summarizes an exploratory study on usability practice from a user-centered design perspective in Taiwan's internet industry. Through in-depth interviews with 14 professionals, the study found:
1) Usability knowledge and skills were generally lacking, with most learning through experience rather than formal training.
2) Design methods were typically linear rather than iterative as recommended by user-centered design. Deadlines often took priority over usability.
3) While usability testing and prototyping were acknowledged as helpful, they were seldom used due to schedule and budget constraints. Users tended to be involved primarily to satisfy business goals rather than design goals.
Similaire à EMPIRICAL STUDY OF THE EVOLUTION OF AGILE-DEVELOPED SOFTWARE SYSTEM IN JORDANIAN'S TELECOM (20)
One factor that encourages the investment climate to run in a positive trend is the ability of organizers to
package these investment activities. Positive things that have emerged in line with the increasingly
dynamic information technology-based (IT) industry in Indonesia are the increasing number of events with
the theme of business matching, investor forums, business networking, and other similar events. This
indicates that business players and investors are increasingly interested in IT-based industries. Business
matching is the implementation of events that bring together buyers and UMKM producers to communicate
about requests and supplies and matters related to them. It can be said that business matching is an
activation of the info booth. Business matching is expected to generate real and direct trade. At this point
in time, it can be said that the quality of events with the theme of business matching and investor forums is
still far from expectations. If we attend events like this, it can be seen that the purpose of holding the event
is still not in focus and it is almost certain that the startups featured have not gone through a strategic and
well-managed selection process.
Call for papes !!! International Journal of Business Information Systems Stra...ijbiss
International Journal of Business Information Systems Strategies (IJBISS) is a Quarterly peer-reviewed and refereed open access journal that publishes articles which contribute new results in all areas of the Business Information Systems Strategies. A business information system is the study of merging new information technology in the field of business management. The emphasis of implementing Business Information systems is to improve the effectiveness and efficiency of an organization. This journal publishes research and case study papers related to development of information technology based business strategies, cross-cultural issues, and global organizational systems. This journal aims to provide a platform for exchanging ideas in new emerging trends that needs more focus and exposure and will attempt to publish proposals that strengthen our goals.
Effective OBT is part and parcel of quality MET provided by any maritime institute. To know the current status of the effectiveness of the OBT in Tanzania, the present study applies Extended DEMATEL Model to evaluate the challenges facing OBT in Tanzania. We firstly use expert opinions to identify the challenges and we then apply the Evaluation Model to rank the challenges facing OBT in Tanzania. The most prevalent challenges that are critical for effective OBT in Tanzania are identified and presented. The study reveals that the major challenges in descending order are Shortage of maritime simulators to complement OBT, Lack of ocean going vessels flying Tanzanian flag, and Lack of dedicated training ships. On the other hand, the minor challenges in descending order for effective OBT in Tanzania are Ineffective enforcement of Tanzania merchant shipping Act 2003, Decline of fleet owned and operated by SINOTASHIP, Shortage of merchant vessels undertaking coastal shipping in Tanzania waters, and Scarcity of qualified officers for effective OBT. The future extension of this study could be the analysis of the Tanzania Investment Policy in the Maritime Transport and Port Sector.
Model for Implementing Successful Customer Relationship Management in Saudi T...ijbiss
The telecommunications sector in Saudi Arabia is continuously seeking to a close relationship with their customers. Most telecom companies have Customer Relationship Management (CRM) system. However,
implementing CRM systems have a low success rate. This paper aims to propose a model that helps the telecom companies to increase the level of implementing successful CRM system. A model is drawn to
identify the critical success factors that contribute to successful CRM system in Saudi telecommunication sector. Seven basic hypotheses were tested, as parts of a theoretical model of successful CRM system.
Data was collected through a questionnaire. The empirical analysis was carried out using a structural equation model and regression. In addition, follow-up interviews were conducted with a small number of top
managers. Data obtained from the questionnaire was triangulated with data gathered from follow-up interviews. The findings revealed that the seven hypotheses were supported and lead to CRM success.
Assessing the Impact of Relationship Quality on Online Adoption ijbiss
Relationships are strongly embedded in Indian culture due to its high-context nature. Because of this, the role of relationship marketing has been advanced in a variety of services viz., banking, retailing, telecom, etc and hence the competition amongst various service providers has increased. Traditionally, relationship management used to be personal interaction based phenomenon but with IT as an enabler for online channels, the need for creating and growing relationships have transpired in a big way. With the advent of technological changes in the business environment, customers are seeking better alternatives to reduce the frequency of visiting the bank branch physically and are relying more on the virtual mode for transacting. Hence, banks and other service organizations are strongly focussing on the digital (online) channels for facilitating monetary transactions and hence gaining competitive advantage. In the virtual mode, the concept of relationships appears to be unrealistic due to the absence of human interface. However, significant studies have been conducted in this regard which focus on the influence of relationship quality factors viz., trust, commitment, satisfaction, etc. towards adopting the online channel for carrying out financial transactions. Relationship quality focuses on evaluating the strength of relationships, which affects customer loyalty. There exists a dearth of such significant studies in the Indian context. The present research will focus on bridging this gap in the literature. This paper will follow a causal research design for empirically analysing the impact of RQ factors towards adopting online mode for banking transactions. It will also investigate the future intentions of the customers toward using the online channels for carrying out financial transactions.
The Impact of Technology Based Self Service Banking Dimensions on Customer Sa...ijbiss
The technology based self service banking (TBSSB) refers to automated banking services that customer avail in self service mode using various electronic banking channels, without any interaction with bank employees. This paper investigates the relationship between key dimensions (factors) of TBSSB service
quality and Customer Satisfaction. A structured questionnaire was formulated by identifying and adapting attributes on the basis of past studies on service quality of automated services and customer satisfaction. Data was collected from sample of bank customers in India. The collected data was divided into two subsamples of equal size. The TBSSB service quality and customer satisfaction dimensions were identified by
conducting an exploratory factor analysis (EFA) on the half of the collected data using SPSS 16.0 software. Factor structure was confirmed by conducting confirmatory factor analysis (CFA) using AMOS 20.0 software on the remaining half of the collected data. The proposed model was empirically tested for unidimensionality, reliability, and validity. AMOS 20.0 was also used to examine the link amid TBSSB service quality and Customer Satisfaction by testing hypotheses using structural equation modeling (SEM). This study may help banks’ management to investigate the customers’ quality perceptions about TBSSB services, thereby helping banks to formulate strategies to improve the quality of service and customer satisfaction.
Trust Evaluation Using an Improved Context Similarity Measurementijbiss
In context-aware trust evaluation, using ontology tree is a popular approach to represent the relation between contexts. Usually, similarity between two contexts is computed using these trees. Therefore, the performance of trust evaluation highly depends on the quality of ontology trees. Fairness or granularity consistency is one of the major limitations affecting the quality of ontology tree. This limitation refers to inequality of semantic similarity in the most ontology trees. In other words, semantic similarity of every two adjacent nodes is unequal in these trees. It deteriorates the performance of contexts similarity computation. We overcome this limitation by weighting tree edges based on their semantic similarity. Weight of each
edge is computed using Normalized Similarity Score (NSS) method. This method is based on frequencies of concepts (words) co-occurrences in the pages indexed by search engines. Our experiments represent the better performance of the proposed approach in comparison with established trust evaluation approaches. The suggested approach can enhance efficiency of any solution which models semantic relations by
ontology tree.
Mathematical Assessment of "Blogging Effect" on Consumer Buying Behavior ijbiss
The Internet has escorted in mammothalterations in the marketing strategy by coalescing many diversities of business models involving affiliate marketing, direct sales, viral marketing and marketing online. It has been evidenced that blogs play an imperative role in facilitating customers to form a buying decision. In fact, blogs have an upshot on purchase behavior far more than the social networking platforms. Blogs have
unremittingly garnered a reliable audience. When the demonstrative bond between the blogger and the consumers gets very substantial, it can lead the latter to really build a buying decision. The impact of blogs is so intense that it is sometimes stated as “Blogging Effect” on buying behavior. The present study is an endeavor to derive the two important mathematical instigation of the “blogging effect”-
A Study on the Sectors of Economy Serviced by Pre-Industry System Developers ...ijbiss
In the emergence of transformative global economy, information system has became a necessity in businesses to obtain organizations operational excellence, adaptation to new business models, improved decision making and providing exceptional customer service, and eventual competitive advantage of the enterprise setting while keeping business alliances. This paper presents sectors of economy serviced by the pre-industry developers, explores the evolution of computer-based information system designed and developed by pre-industry system developers, and examine the effects of an information system in business to countervail indentified recurring problems. Nineteen of forty-six identified sectors of economy falls in the categories of primary, secondary, tertiary, quarternary and quinary were the recipient of computer-based system designed and developed. There have been several effects of computer-based systems to organizations, including the implied relevance to their business processes, continuum process improvement, business process reengineering, business driver and facilitator, and customer satisfaction.
Transaction Profitability Using HURI Algorithm [TPHURI]ijbiss
Business intelligence (BI) is formulation of business strategies which help organizations to achieve its objectives and to predict its future. Data mining is often referred as BI in the domain of business. One of the major tasks in data mining is Association Rule Mining (ARM). ARM techniques incorporated in BI systems can be utilized in business decision-making such as retail shelf management, catalog design, customer segmentation, cross-selling, quality improvement and bundling products marketing.
ARM technique is used for the identification of frequent itemsets from huge databases and then generating strong association rules by considering each item having same value. But in a large number of real world applications, items have different values according to their impact on the respective decision making processes. Traditional ARM techniques cannot fulfil the arising demands from these applications. The data mining researchers are continuously improving the quality of ARM technique by incorporating the utility of items. The utility of item is decided by its contribution towards the business profit or quantity of the item sold, etc. Hence Utility mining focuses on identifying the itemsets with high utilities.
Jyothi et al proposed HURI algorithm in [2] for producing high utility rare itemset according to users’ interest. An algorithm Transaction Profitability using HURI [TPHURI] is proposed in this paper which is a modified version of HURI. TPHURI finds profitable transactions consisting of high utility rare items and also finds the share of such items in the overall profit of the transactions.
Empirical Study of the Evolution of Agile-developed Software System in Jordan...ijbiss
The document discusses a study of the adoption of agile practices in three telecommunications companies in Jordan. It finds that:
1) The companies used some agile practices like continuous integration and collective code ownership but did not follow full agile methodologies.
2) Adoption levels varied across practices and companies, with measurement of progress through working code seeing higher adoption.
3) Experiences with practices were mixed, with continuous integration and collective ownership more widely used than pair programming.
Enhanced Decision Support System for Portfolio Management Using Financial Ind...ijbiss
This document describes a decision support system for portfolio management that uses financial indicators to recommend stocks for purchase or sale. The system analyzes data from the Iranian stock market from 2001-2011. It first groups stocks and then calculates eight common financial indicators for each stock, including RSI, CCI, EMV, and ROC. These indicators predict whether a stock is oversold (good to buy) or overbought (good to sell). The system ranks stocks for each group based on the indicators and recommends the top 5 stocks to buy and 5 to sell, providing purchase and sale suggestions with high accuracy.
Most viewed article for an year - International Journal of Business Informati...ijbiss
International Journal of Business Information Systems Strategies (IJBISS) is a Quarterly peer-reviewed and refereed open access journal that publishes articles which contribute new results in all areas of the Business Information Systems Strategies. A business information system is the study of merging new information technology in the field of business management. The emphasis of implementing Business Information systems is to improve the effectiveness and efficiency of an organization. This journal publishes research and case study papers related to development of information technology based business strategies, cross-cultural issues, and global organizational systems. This journal aims to provide a platform for exchanging ideas in new emerging trends that needs more focus and exposure and will attempt to publish proposals that strengthen our goals.
Current issues - International Journal of Business Information Systems Strate...ijbiss
The document discusses challenges facing on-board training (OBT) in Tanzania. It applies the Extended DEMATEL method to evaluate these challenges based on expert opinions. The method involves identifying challenges, establishing direct relation matrices, and calculating importance weights to determine major and minor challenges. The study finds the most significant challenges are the shortage of maritime simulators, lack of ocean-going vessels flying the Tanzanian flag, and lack of dedicated training ships. The minor challenges are ineffective enforcement of shipping laws, decline of a shipping company's fleet, shortage of coastal vessels, and lack of qualified officers for effective OBT.
EVALUATION OF THE CHALLENGES FACING ONBOARD TRAINING IN TANZANIA: A DEMATEL M...ijbiss
The document discusses challenges facing on-board training (OBT) in Tanzania. It applies the Extended DEMATEL method to evaluate these challenges based on expert opinions. The method involves identifying challenges, establishing direct relation matrices, and calculating importance weights to determine major and minor challenges. The study finds the most significant challenges are the shortage of maritime simulators, lack of ocean-going vessels flying the Tanzanian flag, and lack of dedicated training ships. The minor challenges are ineffective enforcement of shipping laws, decline of a shipping company's fleet, shortage of coastal vessels, and lack of qualified officers for effective OBT.
Call For Papers - International Journal of Business Information Systems Strat...ijbiss
International Journal of Business Information Systems Strategies (IJBISS) is a Quarterly peer-reviewed and refereed open access journal that publishes articles which contribute new results in all areas of the Business Information Systems Strategies. A business information system is the study of merging new information technology in the field of business management. The emphasis of implementing Business Information systems is to improve the effectiveness and efficiency of an organization. This journal publishes research and case study papers related to development of information technology based business strategies, cross-cultural issues, and global organizational systems. This journal aims to provide a platform for exchanging ideas in new emerging trends that needs more focus and exposure and will attempt to publish proposals that strengthen our goals.
International Journal of Business Information Systems Strategies (IJBISS)ijbiss
International Journal of Business Information Systems Strategies (IJBISS) is a Quarterly peer-reviewed and refereed open access journal that publishes articles which contribute new results in all areas of the Business Information Systems Strategies. A business information system is the study of merging new information technology in the field of business management.
International journal of business information systems strategies(ijbiss)ijbiss
International Journal of Business Information Systems Strategies (IJBISS) is a Quarterly peer-reviewed and refereed open access journal that publishes articles which contribute new results in all areas of the Business Information Systems Strategies
International Journal of Business Information Systems Strategies (IJBISS)ijbiss
The International Journal of Business Information Systems Strategies (IJBISS) is a quarterly peer-reviewed journal that publishes articles contributing new results in the field of business information systems strategies. The journal focuses on how new information technology can improve business management effectiveness and efficiency. It publishes research on developing IT-based business strategies and global organizational systems. The journal aims to provide a platform for exchanging ideas on emerging trends and publishes proposals that strengthen its goals related to IT management, knowledge management, e-business, and other topics. Authors are invited to electronically submit original papers by the listed deadlines for review and potential publication.
International Journal of Business Information Systems Strategies (IJBISS)ijbiss
International Journal of Business Information Systems Strategies (IJBISS) is a Quarterly peer-reviewed and refereed open access journal that publishes articles which contribute new results in all areas of the Business Information Systems Strategies. A business information system is the study of merging new information technology in the field of business management. The emphasis of implementing Business Information systems is to improve the effectiveness and efficiency of an organization. This journal publishes research and case study papers related to development of information technology based business strategies, cross-cultural issues, and global organizational systems. This journal aims to provide a platform for exchanging ideas in new emerging trends that needs more focus and exposure and will attempt to publish proposals that strengthen our goals.
Leveraging Generative AI to Drive Nonprofit InnovationTechSoup
In this webinar, participants learned how to utilize Generative AI to streamline operations and elevate member engagement. Amazon Web Service experts provided a customer specific use cases and dived into low/no-code tools that are quick and easy to deploy through Amazon Web Service (AWS.)
Gender and Mental Health - Counselling and Family Therapy Applications and In...PsychoTech Services
A proprietary approach developed by bringing together the best of learning theories from Psychology, design principles from the world of visualization, and pedagogical methods from over a decade of training experience, that enables you to: Learn better, faster!
How Barcodes Can Be Leveraged Within Odoo 17Celine George
In this presentation, we will explore how barcodes can be leveraged within Odoo 17 to streamline our manufacturing processes. We will cover the configuration steps, how to utilize barcodes in different manufacturing scenarios, and the overall benefits of implementing this technology.
Chapter wise All Notes of First year Basic Civil Engineering.pptxDenish Jangid
Chapter wise All Notes of First year Basic Civil Engineering
Syllabus
Chapter-1
Introduction to objective, scope and outcome the subject
Chapter 2
Introduction: Scope and Specialization of Civil Engineering, Role of civil Engineer in Society, Impact of infrastructural development on economy of country.
Chapter 3
Surveying: Object Principles & Types of Surveying; Site Plans, Plans & Maps; Scales & Unit of different Measurements.
Linear Measurements: Instruments used. Linear Measurement by Tape, Ranging out Survey Lines and overcoming Obstructions; Measurements on sloping ground; Tape corrections, conventional symbols. Angular Measurements: Instruments used; Introduction to Compass Surveying, Bearings and Longitude & Latitude of a Line, Introduction to total station.
Levelling: Instrument used Object of levelling, Methods of levelling in brief, and Contour maps.
Chapter 4
Buildings: Selection of site for Buildings, Layout of Building Plan, Types of buildings, Plinth area, carpet area, floor space index, Introduction to building byelaws, concept of sun light & ventilation. Components of Buildings & their functions, Basic concept of R.C.C., Introduction to types of foundation
Chapter 5
Transportation: Introduction to Transportation Engineering; Traffic and Road Safety: Types and Characteristics of Various Modes of Transportation; Various Road Traffic Signs, Causes of Accidents and Road Safety Measures.
Chapter 6
Environmental Engineering: Environmental Pollution, Environmental Acts and Regulations, Functional Concepts of Ecology, Basics of Species, Biodiversity, Ecosystem, Hydrological Cycle; Chemical Cycles: Carbon, Nitrogen & Phosphorus; Energy Flow in Ecosystems.
Water Pollution: Water Quality standards, Introduction to Treatment & Disposal of Waste Water. Reuse and Saving of Water, Rain Water Harvesting. Solid Waste Management: Classification of Solid Waste, Collection, Transportation and Disposal of Solid. Recycling of Solid Waste: Energy Recovery, Sanitary Landfill, On-Site Sanitation. Air & Noise Pollution: Primary and Secondary air pollutants, Harmful effects of Air Pollution, Control of Air Pollution. . Noise Pollution Harmful Effects of noise pollution, control of noise pollution, Global warming & Climate Change, Ozone depletion, Greenhouse effect
Text Books:
1. Palancharmy, Basic Civil Engineering, McGraw Hill publishers.
2. Satheesh Gopi, Basic Civil Engineering, Pearson Publishers.
3. Ketki Rangwala Dalal, Essentials of Civil Engineering, Charotar Publishing House.
4. BCP, Surveying volume 1
This document provides an overview of wound healing, its functions, stages, mechanisms, factors affecting it, and complications.
A wound is a break in the integrity of the skin or tissues, which may be associated with disruption of the structure and function.
Healing is the body’s response to injury in an attempt to restore normal structure and functions.
Healing can occur in two ways: Regeneration and Repair
There are 4 phases of wound healing: hemostasis, inflammation, proliferation, and remodeling. This document also describes the mechanism of wound healing. Factors that affect healing include infection, uncontrolled diabetes, poor nutrition, age, anemia, the presence of foreign bodies, etc.
Complications of wound healing like infection, hyperpigmentation of scar, contractures, and keloid formation.
EMPIRICAL STUDY OF THE EVOLUTION OF AGILE-DEVELOPED SOFTWARE SYSTEM IN JORDANIAN'S TELECOM
1. International Journal of Business Information Systems Strategies (IJBISS) Volume 1, Number 1,November 2012.
11
EMPIRICAL STUDY OF THE EVOLUTION OF
AGILE-DEVELOPED SOFTWARE SYSTEM IN
JORDANIAN'S TELECOM
Dr.Walid Qassim Qwaider
Majmaah University College of Science and Humanities in Ghat
Management Information Systems Dept.
Saudi Arabia
wqwaider74@yahoo.com
ABSTRACT
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 large-
scale 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.
KEYWORDS:
Agile Methodologies, Software Development, Agile method, Jordan Telecom.
1. INTRODUCTION
Approach to software development methods and include both agile and plan-driven. Agile
methods, and the emphasis on flexibility, informal cooperation and labor law. Supporters argue
that agile processes such operations must be able to respond to change and cope with the
pressures driving the ongoing evolution of software better than plan-driven approach. Sustainable
development of the code is a clear goal in teams flexibility, and is seen as something necessary
restructuring and positive [1]. These allegations need to be tested through studies of software
development using agile methods. This requires qualitative and quantitative observations by
collecting and studying is difficult. He proposed to develop the software includes both the
flexibility and plan-driven methods [2].
Agile methods emphasize flexibility, informal cooperation and labor law. Plan-driven approach to
emphasize large-scale planning, and official communications and documents. [2]. Proposed five
2. International Journal of Business Information Systems Strategies (IJBISS) Volume 1, Number 1,November 2012.
12
dimensions of the critical risks (size, forest, and dynamic, and staff and culture) that organizations
should be taken into account when deciding which method to use. While the focus of the Boehm
and Turner seems to be the situation before and during the initial development, and surveys
indicate that the vast majority of the effort the developer is happening in the maintenance and
development [3].
The importance of telecommunications and software development led us to propose a strict
processes traditionally used to some extent, usually using frameworks such as process, or SW-
CMM. As far as we know, no published studies discuss the use of agile methods in the
telecommunications industry. Thus, we believe that this paper some light on the current situation.
Basic questions in the research that motivated this study are:
1.Which agile practices were used in these telecom companies?
2.What experiences were reported on those practices?
2. RELATED WORK
This study was made in a large telecom company as part of a research program, whose goal is to
increase and transfer practical knowledge of achieving agility in software development. Creating
a full-fledged methodology and trying to leverage it in a large organization is not feasible.
However, describing a set of process patterns that promote agility is more feasible. A process
pattern describes a practice considering topics such as which problem it solves, when it is
applicable, how to deploy it etc [4].
Wernick & Hall 2004, argued that pair programming should be beneficial for long-term
evolution. considers the different types of stakeholders and concludes that the effects of agile
methods may be more positive for some than for others. To our knowledge, the findings
presented here forms the first measurement-based study of the evolution of software developed
using an agile approach in an industrial setting [5].
McCormick, 2001, Ideas for creating a methodology for a company also supports the process
patterns approach: “What’s needed is not a single software methodology, but a rich toolkit of
process patterns and ‘methodology components’ (deliverables, techniques, process flows, and so
forth) along with guidelines for how to plug them together to customize a methodology for any
given company.” Of course, the ideal content of an agile toolkit depends on the context, and the
limits of agile practices are still unclear. Before the study, we had collected a tentative of agile
practices that could be applicable in the company. Most of the practices are described in XP and
the rest in other literature [6].
This paper aimed at increasing our understanding of the current level of use of these and
potentially some other agile practices in the company. Based on the results of this study we will
evaluate and improve the practicality and completeness of our tentative agile practice list.
3. International Journal of Business Information Systems Strategies (IJBISS) Volume 1, Number 1,November 2012.
13
3. RESEARCH METHODOLOGY
Use the internal network of the company and personal relations, and we have identified several
telecommunications companies from the company in the case of Finland, which was a conscious
or unconscious use of flexible software development practices. On the other hand, we could not
identify any telecommunications company that was using the full agile methodology such as XP.
Of seven candidates identified we selected three companies for communications, A, B, C, and
that apparently the most active in the use of agile practices. Selected companies and all
communications develop different types of products in different business units, and for different
markets.
3.1 Sampling Design
Samples are collected through the selection of a sufficient number of elements of Jordan
Telecom. We conducted interviews with the director and developer of telecommunications,
communications, B, and C, only a developer of communications and interviews covering all areas
of a typical software company at a general level in order to identify other agile practices in
addition to those which we have already listed.
We quantified the level of use of agile practices in order to answer the research question better
first. It was difficult to estimate because there are several dimensions that should be considered,
for example, the number of people who use the telecommunications companies, and the duration
of use, and discipline to use, and aspects are used. And answered the research question the second
qualitative analysis of the experiences reported.
3.2 Instrumentation
Since the polls are usually evaluative rather than generative, they offer the results of a broad and
that can be companied to the weight. Researchers decided that the survey focused is the best way
to collect data on the use of flexible practices in three companies in the software development
company wide contacts in Jordan. Quantitative measure for telecommunications companies to use
agile practices is:
Weight (0): Description of practically no benefit from this practice.
Weight (1): the use of a minor description, for example, and someone tried to practice for some
time.
Weight (2): Use a mild description, for example uses many of the people for a long time.
Weight (3): description of the use of large, for example, was almost the rule to be used.
4. OVERVIEW OF THE TELECOM COMPANY
Survey includes three companies in the telecommunications sector in Jordan: The company was
one of the companies which is published in a small team working in the largest 40 companies
from a person sub that was part of the further development of a very large legacy system [3]. The
mentality of developers about the company's first two practices, and because the light of the
telecommunications company has grown slowly over time, they have the time to find the natural,
the process is minimal. Allowed for the success of the product and a small number of developers
4. International Journal of Business Information Systems Strategies (IJBISS) Volume 1, Number 1,November 2012.
14
to keep them on the process because she wanted in spite of external pressures to change it to
adhere better to a model of the general process. Developed a communications company B at a
low level embedded software. Director of Communications decided to practices used in the
company based on his past experience. Team tried to improve the current process through the
deployment of some aspects of certain XP practices. Table 1 summarizes the characteristics of
these companies. The company developed a UNIX-based C application.
Table 1. Telecom company characteristics
company A company B company C
company
type
Development
of a part
of a larger
system
Integration
and porting
of
embedded
sw
Development
of an
evolving sw
product
People 2 (of 40) 4 1 (of 6)
Distribu
tion
Co-located
team
Co-located
team
Two teams in
two
countries
Duratio
n
1 years 7 months Duration 4
years
Effort ~4 man years ~5 man
years
~25 man
years
SW Size 50 kLOC 12 kLOC 390 kLOC
5. RESULT
5.1 Adoption of Agile Practices
The use of emerging practices more flexible than planned. Usually, the process of individual
practices or the use of non-specific or non-formally documented, but instead of the director of the
company and developers to use the practices they considered efficient and natural. Have
experimented with XP partly in C Company, but others did not use any agile methodology
documented as the basis for the operation of their own. Table 2 summarizes the motivation for the
use of agile practices and experiences, both with something new, for example some of the
practices XP.
5. International Journal of Business Information Systems Strategies (IJBISS) Volume 1, Number 1,November 2012.
15
Table 2. Presents the adoption level of agile practices and the following Sections describe the experiences
No Practice A B C
1 Continuous integration 2 0 2
2 Incremental delivery 1 0 2
3 Measure progress by working
code
3 3 2
4 Interactive planning 2 0 1
5 Developers estimate task
efforts
3 2 2
6 Visual modeling 2 2 1
7 Use cases 0 0 3
8 Design Patterns 2 0 0
9 Continuously developed
architecture
2 1 1
10 Pair programming 0 0 1
11 Collective code ownership 2 1 2
12 Coding standard 3 1 3
13 Refactoring 1 2 2
14 Write tests first 0 0 0
15 Limited documentation 3 2 1
16 Team in one location 0 3 3
17 Frequent team meetings 2 1 1
18 Customer always available 2 2 0
19 Team develops its processes 1 2 3
20 No continuous overtime 3 2 1
5.2 Evolution of Agile Practices
Continuous integration: in the company, developers integrate their code after a few days of
work. The symbol of the work before the check-in. B in the company, developers and sub-
systems implemented for the first time on the unit, followed by the stage of integration. C in the
company, and checked the new law for the common repository as far as is reasonable, usually
after a few days of development.
0: Practically no use 1: Minor use
2: Moderate use 3: Considerable use
6. International Journal of Business Information Systems Strategies (IJBISS) Volume 1, Number 1,November 2012.
16
A gradual transition: the company and was to launch a cycle for 6 months. Company C had a
release cycle of 6 months. BP plans to first release occurs after 10 months of start-up company,
but was canceled 0due company for commercial reasons before the first version. Later in the
session, were delivered by the weekly bulletins to the customer.
Adaption Level of Agile Practices
0
0.5
1
1.5
2
2.5
3
3.5
Continuous
integration
Incremental
delivery
Measure
progress by
working
code
Interactive
planning
Project
Value
A
B
C
Figure 1. Adoption level of agile practices (1-5).
Measure the progress made by the code work: in a company, and the current version was
delivered weekly to the customer. Users tried to pre-release, and provided valuable information to
replace the need for a detailed specification requirement. Committed users thanks to the feedback
loop are short. Developers are also rewarding to see the results soon. Were divided internally to
company B parameters of the program every 1 to 6 weeks.
Interactive Planning: In the company, and Director of the company constantly discussed with
customer specifications. He considered the presence of developers in the meetings of the relevant
customer is important to gain a common understanding, and give a sense of appreciation for the
developers. Priorities have been identified along with customers at various levels (public
administration, and features) on the technical feasibility of the proposals also.
Developers appreciate the efforts of the task: in the company, and made crude estimates of effort
by the company in the feasibility study, but the developers refine them later. In the estimates of
BP originated from an effort in the technical specifications stage, but the development team re-
estimated prior to implementation. In the performance of the company C, and the best experts in
the field of assessment of the effort. See Figure 1.
Visual Display: In the Company used the scenario and graphics category. The one reason to
avoid the graphs to the lack of a good drawing tool. B in the company, and developers is a picture
of the whole system shows the parts, communications and they are the most important part of the
architectural documentation. Developers and also drew UML scenario diagrams and process sub-
systems. C in the company, including technical documents only a few schemes. See Figure 2.
Use cases: in company B, and use case modeling did not use, because the company was mostly
technical, and the low level of development. C in the company has been documented
requirements using use cases.
7. International Journal of Business Information Systems Strategies (IJBISS) Volume 1, Number 1,November 2012.
17
Design patterns: the company began to use design patterns after the first major restructuring of
the product. In company B, was not considered because of the design patterns applied to coding
on a low level.
AdaptionLevelofAgilePractices
0
0.5
1
1.5
2
2.5
3
3.5
Visual
modeling
Usecases
Design
Patterns
Continuously
developed
architecture
Pair
programming Project
Value
1ﻣﺗﺳﻠﺳﻠﺔ
2ﻣﺗﺳﻠﺳﻠﺔ
3ﻣﺗﺳﻠﺳﻠﺔ
Figure 2. Adoption level of agile practices (6-10).
Architecture is constantly evolving: in a company, has been developed in parallel with the
structure of new features. Submitted a (b) at a higher level design early on the basis of external
standards. Remained largely stable design.
Pair programming: problems in Company C code has been solved in many cases, with a pair, but
during the programming tasks pairing was scarce. However, even spread that amount of pairing at
the correct knowledge of the system among developers. Figure 2.
Collective ownership of code: the company, and allowed the developers to change the code of
others, and even the platform code. B in the company and developers have worked mostly with
their own code. Sometimes read as a symbol of others, but the owner make the changes final. C in
the company, and was allowed a developer to change any part of the law if necessary, but in fact
it was focused on units of their own.
Coding standard: in the company, and followed a general pattern of evidence by the company. B
in the company, and covered the windows instructions only unit. C in the company, and followed
the pattern of evidence in the naming of variables, and structure of the symbol, and symbol in the
organization of files.
Restructuring: the refectories rarely so as not to break the list, and a large code base. However,
not all developers refactor continuously, causing some parts to decay very badly. Kept the senior
people in the best form of code. Company B changed low-level design quite a lot during
encoding. Company C of the company, and was always present architectural decay has also been
adding new features, and was restructuring exercise all the time. See Figure 3.
8. International Journal of Business Information Systems Strategies (IJBISS) Volume 1, Number 1,November 2012.
18
Adaption Level of Agile Practicse
0
0.5
1
1.5
2
2.5
3
3.5
Collectivecode
ownership
Coding
standard
Refactoring
Writetests
first
Limited
documentation
Project
Value
1ﻣﺗﺳﻠﺳﻠﺔ
2ﻣﺗﺳﻠﺳﻠﺔ
3ﻣﺗﺳﻠﺳﻠﺔ
Figure 3. Adoption level of agile practices (11-15).
Write the first tests: not one of the companies studied and wrote unit tests before the code is real.
Documents are limited: in the company, technical documentation and documents received from
the architecture and some short technical guideline documents. These were not usually kept up to
date. And considered it somewhat useful for new people, but vocational training such as hands-on
training was the most successful knowledge transfer. No senior developer does not need the
documents at all. Not developed even in the two sites do not seem to need more documents.
BP had a short technical document for each subsystem and describe the general structure of the
system. The need to design documents low because the size of the program was rather small, and
had a modular structure. Put only one person each subsystem, and only the interfaces of interest
to others. Commenting on the details and the reasons behind the solutions in the source code. The
suspension is important even for the writer because of the new domain. The requirements were
collected in a short document. There was only one condition a real user and some technical
requirements see Figure 3.
Team in one place: in the company and added that the team work in another country for the
company. After several months of vocational training in Jordan, the team members began to work
in their home. Teams held frequent conferences, and some meetings and workshops annually. The
lead developers of the private rooms and the other worked in the Office of the landscape, and that
some developers did not like because of the annoying background noise. The companies B and C,
two adjacent rooms.
Frequent meetings of the Group: Company to hold meetings when necessary, usually 15-30
minutes once or twice a week. BP had a weekly status meeting, where everyone said what he had
done since the last meeting. Company C, ate lunch together, and the Panel did not consider it
necessary to hold formal daily meetings.
Customer is always available: in the company, there was a weekly meeting between the customer
and the Director of the company and some developers. There were also many discussions with the
client. B in the company, played the role of product manager for clients. His room was in another
floor, but he answered questions when asked. C in the company, and played the role of Director
of the company customers. It was difficult to identify the client's real and proper to have the
involvement of the customer.
9. International Journal of Business Information Systems Strategies (IJBISS) Volume 1, Number 1,November 2012.
19
Adaption Level of Agile Practice
0
0.5
1
1.5
2
2.5
3
3.5
Team in one
location
Frequent
team
meetings
Customer
always
available
Team
develops its
processes
No
continuous
overtime
Project
Value
1ﻣﺗﺳﻠﺳﻠﺔ
2ﻣﺗﺳﻠﺳﻠﺔ
3ﻣﺗﺳﻠﺳﻠﺔ
Figure 4. Adoption level of agile practices (16-20).
Development team operations: in the company, the planning team practices, experimenting with
XP, but the process has been defined outside the team. I love the team and the way they worked,
and the lack of clear roles, such as designers, managers and programmers to improve team spirit.
B in the company, and create a director of the process and discussed with the team. The
developers are more interested in software development, and therefore the proposal, the light did
not meet with resistance. C in the company, and create a director of the operation along with the
team. See Figure 4.
No additional constant: people working in the company extra time just before the launch of the
mission. BP used some extra time to speed up the release of the first. Company C increase in
stoppage time at the end of the company, but was not significant.
6. DATA ANALYSIS AND DISCUSSION
6.1 Adoption Level
The most practices often and thoroughly adopted to measure the progress made by the code work,
after the developers appreciate the efforts of the task, using the standard encoding, and not to use
overtime continuous, and a team development process of their own, limited documentation,
having a team in place one. Some practices, such as interactive planning, and writing tests first,
and unit test automation, and customer writes acceptance tests, and used the pair programming
almost anywhere. It may be that familiarity with these practices was low among those who were
interviewed and some very strange practices and difficult for the adoption of practices that cause
not only shows. May be that you must create a systematic process based on some documented
agile or a list of best practices in order to be the adoption of these practices. As often is the
practice test flexibility as a prerequisite for many other practices which are graceful, and the
adoption of these practices is low to indicate that there is a need for more education in this area.
6.2 Success Factors
Helped in the company, and held frequent meetings the details of the design team high initial
level specifications. Correct pairing during exercise was very useful and dissemination of
knowledge between the system developers. The members of one of the strengths of B Company.
Director of the company and developers selected on the basis of their skills and qualities in order
to form a good team for this company. The director of the company, both administratively and
technically competent design and overall architecture. We identified the following success factors