This paper presents the result of software requirements practices survey among software practitioners, a study in a city of Jeddah, Saudi Arabia. As software requirements are important and they lead to the successful of a software development project, it becomes interesting to investigate the current software requirements practices in the kingdom of Saudi Arabia. As an initial work, a survey was conducted in
Jeddah as a study before we conduct it in the Kingdom of Saudi Arabia software industry. The survey is conducted by distributing a set of questionnaire to the software practitioners. There are 17 respondents completed the questionnaire out of 50 distributed questionnaire, which is 34% of response rate. The result of this survey is promising and it has shown that requirements management area should be focused for
future improvement. In the future, the survey will focus on software engineering and requirements engineering practices over the entire Kingdom of Saudi Arabia software industry.
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.
INTRODUCING REFINED AGILE MODEL (RAM) IN THE CONTEXT OF BANGLADESH'S SOFTWARE...ijseajournal
The Software Companies of Bangladesh are using different types of agile models for software development. Although theoretically these models are worthy for small and medium projects, in practical case they are not so effective. In doing so, this paper tries to find out why do the agile models not suitable for Bangladesh’s Software Companies and how do the problems that the Software Companies face for using the models can be solved. To reveal the answers, this study is based on survey and interview methods. Findings of this paper show that Bangladesh's Software Companies are facing different problems for implementing traditional agile models, such as, Communicational gap, lack of Documentation, unavailability of Prototype, Customer’s lack of knowledge in the area of IT and many more. The study shows that if the Requirement Engineering Process is perfectly managed and some rules are modified in the traditional agile models, these problems can be solved. In doing so, a new model has been proposed by the study named Refined Agile Model (RAM) which is claimed to be better for Bangladesh rather than the traditional Agile Models. This model proposes a process flow which consists of Prototyping Cycle, Development Iteration Cycle and Additional Development Iteration Cycle. This new model also ensures a Requirement Engineer at Client End, sufficient documentation, preparation of prototype and presentation of frequent Demos. After ensuring these requirements in several real time projects, it was found that those projects were completed more effectively compared to all other old project experiences. Eventually, the paper concludes by mentioning that the Refined Agile Model (RAM) is the best model in the Bangladeshi software environment.
A study of various viewpoints and aspects software quality perspectiveeSAT Journals
Abstract The software quality is very important research of software engineering grown from the last two decades. The software engineering paradigm adopted by many organizations to develop the high quality software at affordable cost. The high quality software is considered as one of the key factor in the rapid growth of Global Software Development. The software metrics computes and evaluates the quality characteristics and used to take quantitative and qualitative decisions for risk assessment and reduction. The multiple stakeholders can view the software quality in multiple angles with various aspects. In this paper we present multiple views of the software quality with respect to various quality aspects. Key Words : Stakeholders, Functional aspect, Structural aspect, Process aspect, Metrics etc.
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.
An Empirical Study of SQA Function Effectiveness in CMMI Certified Companies ...zillesubhan
The most vital component for any software development process is, “quality”, as it ensures the reliability and effectiveness of new software. Software Quality Assurance (SQA) techniques as well as a standardized qualitative metric known as Capability Maturity Model Integration (CMMI) are used to ensure this quality. The purposes of both the practices are same as both make efforts for end product’s quality. In spite of this, CMMI certified organizations have SQA function, but face a lot of issues, which resulted in lowering the quality of the products. Standards usually provide documentation, but SQA consider testing as a chief element and also documentation only for authentication and appraisals. The relationship of the SQA function with CMMI has not attended much in common literatures. This paper is centered on investigation conducted through data collection from diverse CMMI certified software development firm to check the practice of SQA function.
This thesis focuses on assessing, evaluating, and managing risks in software development projects for Indian software companies. It aims to identify project risks, analyze dimensions of specific risks through primary research, and study an existing project to identify risks and mitigation strategies. The document discusses related work, project and software development lifecycles, types of risks, the research methodology used, a case study of a project called ERWINA, and concludes with recommendations for improving risk management practices.
DESQA a Software Quality Assurance FrameworkIJERA Editor
In current software development lifecycles of heterogeneous environments, the pitfalls businesses have to face are that software defect tracking, measurements and quality assurance do not start early enough in the development process. In fact the cost of fixing a defect in a production environment is much higher than in the initial phases of the Software Development Life Cycle (SDLC) which is particularly true for Service Oriented Architecture (SOA). Thus the aim of this study is to develop a new framework for defect tracking and detection and quality estimation for early stages particularly for the design stage of the SDLC. Part of the objectives of this work is to conceptualize, borrow and customize from known frameworks, such as object-oriented programming to build a solid framework using automated rule based intelligent mechanisms to detect and classify defects in software design of SOA. The implementation part demonstrated how the framework can predict the quality level of the designed software. The results showed a good level of quality estimation can be achieved based on the number of design attributes, the number of quality attributes and the number of SOA Design Defects. Assessment shows that metrics provide guidelines to indicate the progress that a software system has made and the quality of design. Using these guidelines, we can develop more usable and maintainable software systems to fulfill the demand of efficient systems for software applications. Another valuable result coming from this study is that developers are trying to keep backwards compatibility when they introduce new functionality. Sometimes, in the same newly-introduced elements developers perform necessary breaking changes in future versions. In that way they give time to their clients to adapt their systems. This is a very valuable practice for the developers because they have more time to assess the quality of their software before releasing it. Other improvements in this research include investigation of other design attributes and SOA Design Defects which can be computed in extending the tests we performed.
ANALYSIS OF SOFTWARE QUALITY USING SOFTWARE METRICSijcsa
Software metrics have a direct link with measurement in software engineering. Correct measurement is the prior condition in any engineering fields, and software engineering is not an exception, as the size and complexity of software increases, manual inspection of software becomes a harder task. Most Software Engineers worry about the quality of software, how to measure and enhance its quality. The overall objective of this study was to asses and analysis’s software metrics used to measure the software product and process.
In this Study, the researcher used a collection of literatures from various electronic databases, available since 2008 to understand and know the software metrics. Finally, in this study, the researcher has been identified software quality is a means of measuring how software is designed and how well the software conforms to that design. Some of the variables that we are looking for software quality are Correctness, Product quality, Scalability, Completeness and Absence of bugs, However the quality standard that was used from one organization is different from others for this reason it is better to apply the software metrics to measure the quality of software and the current most common software metrics tools to reduce the subjectivity of faults during the assessment of software quality. The central contribution of this study is an overview about software metrics that can illustrate us the development in this area, and a critical analysis about the main metrics founded on the various literatures.
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.
INTRODUCING REFINED AGILE MODEL (RAM) IN THE CONTEXT OF BANGLADESH'S SOFTWARE...ijseajournal
The Software Companies of Bangladesh are using different types of agile models for software development. Although theoretically these models are worthy for small and medium projects, in practical case they are not so effective. In doing so, this paper tries to find out why do the agile models not suitable for Bangladesh’s Software Companies and how do the problems that the Software Companies face for using the models can be solved. To reveal the answers, this study is based on survey and interview methods. Findings of this paper show that Bangladesh's Software Companies are facing different problems for implementing traditional agile models, such as, Communicational gap, lack of Documentation, unavailability of Prototype, Customer’s lack of knowledge in the area of IT and many more. The study shows that if the Requirement Engineering Process is perfectly managed and some rules are modified in the traditional agile models, these problems can be solved. In doing so, a new model has been proposed by the study named Refined Agile Model (RAM) which is claimed to be better for Bangladesh rather than the traditional Agile Models. This model proposes a process flow which consists of Prototyping Cycle, Development Iteration Cycle and Additional Development Iteration Cycle. This new model also ensures a Requirement Engineer at Client End, sufficient documentation, preparation of prototype and presentation of frequent Demos. After ensuring these requirements in several real time projects, it was found that those projects were completed more effectively compared to all other old project experiences. Eventually, the paper concludes by mentioning that the Refined Agile Model (RAM) is the best model in the Bangladeshi software environment.
A study of various viewpoints and aspects software quality perspectiveeSAT Journals
Abstract The software quality is very important research of software engineering grown from the last two decades. The software engineering paradigm adopted by many organizations to develop the high quality software at affordable cost. The high quality software is considered as one of the key factor in the rapid growth of Global Software Development. The software metrics computes and evaluates the quality characteristics and used to take quantitative and qualitative decisions for risk assessment and reduction. The multiple stakeholders can view the software quality in multiple angles with various aspects. In this paper we present multiple views of the software quality with respect to various quality aspects. Key Words : Stakeholders, Functional aspect, Structural aspect, Process aspect, Metrics etc.
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.
An Empirical Study of SQA Function Effectiveness in CMMI Certified Companies ...zillesubhan
The most vital component for any software development process is, “quality”, as it ensures the reliability and effectiveness of new software. Software Quality Assurance (SQA) techniques as well as a standardized qualitative metric known as Capability Maturity Model Integration (CMMI) are used to ensure this quality. The purposes of both the practices are same as both make efforts for end product’s quality. In spite of this, CMMI certified organizations have SQA function, but face a lot of issues, which resulted in lowering the quality of the products. Standards usually provide documentation, but SQA consider testing as a chief element and also documentation only for authentication and appraisals. The relationship of the SQA function with CMMI has not attended much in common literatures. This paper is centered on investigation conducted through data collection from diverse CMMI certified software development firm to check the practice of SQA function.
This thesis focuses on assessing, evaluating, and managing risks in software development projects for Indian software companies. It aims to identify project risks, analyze dimensions of specific risks through primary research, and study an existing project to identify risks and mitigation strategies. The document discusses related work, project and software development lifecycles, types of risks, the research methodology used, a case study of a project called ERWINA, and concludes with recommendations for improving risk management practices.
DESQA a Software Quality Assurance FrameworkIJERA Editor
In current software development lifecycles of heterogeneous environments, the pitfalls businesses have to face are that software defect tracking, measurements and quality assurance do not start early enough in the development process. In fact the cost of fixing a defect in a production environment is much higher than in the initial phases of the Software Development Life Cycle (SDLC) which is particularly true for Service Oriented Architecture (SOA). Thus the aim of this study is to develop a new framework for defect tracking and detection and quality estimation for early stages particularly for the design stage of the SDLC. Part of the objectives of this work is to conceptualize, borrow and customize from known frameworks, such as object-oriented programming to build a solid framework using automated rule based intelligent mechanisms to detect and classify defects in software design of SOA. The implementation part demonstrated how the framework can predict the quality level of the designed software. The results showed a good level of quality estimation can be achieved based on the number of design attributes, the number of quality attributes and the number of SOA Design Defects. Assessment shows that metrics provide guidelines to indicate the progress that a software system has made and the quality of design. Using these guidelines, we can develop more usable and maintainable software systems to fulfill the demand of efficient systems for software applications. Another valuable result coming from this study is that developers are trying to keep backwards compatibility when they introduce new functionality. Sometimes, in the same newly-introduced elements developers perform necessary breaking changes in future versions. In that way they give time to their clients to adapt their systems. This is a very valuable practice for the developers because they have more time to assess the quality of their software before releasing it. Other improvements in this research include investigation of other design attributes and SOA Design Defects which can be computed in extending the tests we performed.
ANALYSIS OF SOFTWARE QUALITY USING SOFTWARE METRICSijcsa
Software metrics have a direct link with measurement in software engineering. Correct measurement is the prior condition in any engineering fields, and software engineering is not an exception, as the size and complexity of software increases, manual inspection of software becomes a harder task. Most Software Engineers worry about the quality of software, how to measure and enhance its quality. The overall objective of this study was to asses and analysis’s software metrics used to measure the software product and process.
In this Study, the researcher used a collection of literatures from various electronic databases, available since 2008 to understand and know the software metrics. Finally, in this study, the researcher has been identified software quality is a means of measuring how software is designed and how well the software conforms to that design. Some of the variables that we are looking for software quality are Correctness, Product quality, Scalability, Completeness and Absence of bugs, However the quality standard that was used from one organization is different from others for this reason it is better to apply the software metrics to measure the quality of software and the current most common software metrics tools to reduce the subjectivity of faults during the assessment of software quality. The central contribution of this study is an overview about software metrics that can illustrate us the development in this area, and a critical analysis about the main metrics founded on the various literatures.
STRATEGIES TO REDUCE REWORK IN SOFTWARE DEVELOPMENT ON AN ORGANISATION IN MAU...ijseajournal
Rework is a known vicious circle in software development since it plays a central role in the generation of
delays, extra costs and diverse risks introduced after software delivery. It eventually triggers a negative
impact on the quality of the software developed. In order to cater the rework issue, this paper goes in depth
with the notion of rework in software development as it occurs in practice by analysing a development
process on an organisation in Mauritius where rework is a major issue. Meticulous strategies to reduce
rework are then analysed and discussed. The paper ultimately leads to the recommendation of the best
strategy that is software configuration management to reduce the rework problem in software development
Requirement Engineering Challenges in Development of Software Applications an...Waqas Tariq
Requirement Engineering acts as foundation for any software and is one of the most important tasks. Entire software is supported by four pillars of requirement engineering processes. Functional and non-functional requirements work as bricks to support software edifice. Finally, design, implementation and testing add stories to construct entire software tower on top of this foundation. Thus, the base needs to be well-built to support rest of software tower. For this purpose, requirement engineers come across with numerous challenges to develop successful software. The paper has highlighted requirement engineering challenges encountered in development of software applications and selection of right customer-off-the-shelf components (COTS). Comprehending stakeholder’s needs; incomplete and inconsistent process description; verification and validation of requirements; classification and modeling of extensive data; selection of COTS product with minimum requirement modifications are foremost challenges faced during requirement engineering. Moreover, the paper has discussed and critically evaluated challenges highlighted by various researchers. Besides, the paper presents a model that encapsulates seven major challenges that recur during requirement engineering phase. These challenges have been further categorized into problems. Furthermore, the model has been linked with previous research work to elaborate challenges that have not been specified earlier. Anticipating requirement engineering challenges could assist requirement engineers to prevent software tower from any destruction.
Testing desktop application police station information management systemSalam Shah
The police stations have adequate importance in the society to control the law and order situations of the country. In Pakistan, police stations manage criminal records and information manually. We have previously developed and improved a desktop application for the record keeping of the different registers of the police stations. The data of police stations is sensitive and that need to be handled within secured and fully functional software to avoid any unauthorized access. For the proper utilization of the newly developed software, it is necessary to test and analyze the system before deployment into the real environment. In this paper, we have performed the testing of an application. For this purpose, we have used Ranorex, automated testing tool for the functional and performance testing, and reported the results of test cases as pass or fail.
This document discusses the evolution of software metrics over time to measure quality as software has become more complex. It outlines how metrics have changed from measuring lines of code and function points to object-oriented and agile metrics that measure concepts like inheritance, cohesion, and velocity. The document also examines how process models like waterfall, spiral, and agile have influenced quality standards and the definition of new metrics. In summary, software metrics have evolved from size-based measures to more sophisticated metrics aligned with modern processes in order to more effectively measure quality attributes as software engineering has advanced.
Exploring the Efficiency of the Program using OOAD MetricsIRJET Journal
This document proposes a methodology to analyze the efficiency of object-oriented programs using OOAD (Object Oriented Analysis and Design) metrics. The methodology involves compiling a program successively until it is error-free, recording the error rate at each compilation. These results are then compared to determine how many compilations were needed for the program to be error-free, indicating its efficiency. The methodology is experimentally validated on a sample Java program, with results showing the error rate decreasing with each compilation until the program is error-free after the 8th compilation, demonstrating good efficiency.
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.
Requirements Analysis and Design in the Context of Various Software Developme...zillesubhan
This document provides a comparative analysis of requirements analysis and design phases between traditional and agile software development approaches. It discusses the importance of requirements analysis and outlines the key stages in a traditional software development lifecycle, including requirements analysis, system design, coding, testing, and maintenance. The document also examines requirements engineering processes and sources of requirements. It describes the goals and importance of software design as a key phase for implementing requirements and allowing flexibility for changes.
IRJET- Factors Affecting the Delivery of Quality Software and their Relations...IRJET Journal
This document discusses factors that affect the delivery of quality software and their relationship to the software development process. It identifies key factors such as the amount of testing, costs involved, time spent, and following proper software development life cycle (SDLC) phases. The document presents a literature review on how these factors influence software quality. It then defines variables, hypotheses, and a regression model to analyze the relationship between delivery of quality software and the identified factors. The results of distributing and analyzing questionnaires indicate that amount of testing, costs involved, and time spent have a statistically significant correlation with delivering quality software. Therefore, paying attention to these factors during development can help improve software quality.
Estimating agile development in the Federal Government domain requires more than just defining Story Points and planning Sprints. These estimates must follow the guidance in OMB A-11 Part 7 and other document based management of budget and performance measures.
A User Story Quality Measurement Model for Reducing Agile Software Developmen...ijseajournal
The document discusses a user story quality measurement (USQM) model for reducing risks in agile software development. It proposes that user story quality is key to affecting development efficiency and handling requirements changes. The USQM model analyzes and collects critical user story quality factors, including clarity, complexity, modularity, configuration management, version control, and testability. By quantifying these factors, the USQM aims to identify quality defects and enhance user stories, thereby reducing development risks from requirements changes.
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.
This document provides a review of systematic quality software designing and development practices. It discusses software engineering processes, quality processes, design and development modeling approaches, and related works. The key points are:
1) Software engineering processes aim to ensure quality, meet deadlines, and manage expectations through defined stages and deliverables. Common models include waterfall, spiral, and agile.
2) Software quality processes evaluate and improve aspects like reliability, maintainability, and interoperability. Metrics and techniques are used to measure qualities.
3) Design and development involve life cycles, methods, and notations to systematically model requirements, architecture, and implementation. Waterfall and rapid prototyping are example models.
FISHBONE ANALYSIS ON WASTES IN SOFTWARE DEVELOPMENT USING THE LEAN I.T. PRINC...ecij
The transformative global economy posed challenges to businesses in service management. In this computing age, the perceptual and operational edge of a certain business or organization manifested on the kind of technology it offers in the Service Management. Organizations have long recognized the
importance of managing key resources such as people and information. Information has now moved to its rightful place as a key resource in the organization and therefore management of the same can be instituted by employing methodology. To keep their brand promise, technology has been used;The number of new entrants to every sectors of economy has grown significantly in recent years, and each firm strives to make their daily operation efficient in which demand for business software or application software getting higher and businesses or organizations opted to build or buy this software. Because of
new entrants, it had offered opportunity to software developers to translate business processes into systems. This study investigates waste in the software development by application of Lean principles. Like any conventional projects, software becomes buggy and oftentimes it fails. Software failure is always attributed to the software engineering, not the incompetence of project managers, inadequacy of the
people on the project, or lack of clear goal. The researchers’ contentions are there wastes in the software development and serve as mechanism and evidence to why software fails. Software failure is not attributed to the software itself, it includes however the acceptance of the clients and end-users. Descriptive secondary data analysis, participant observation and Fishbone Analysis were the methodology used in the study. Wastes include unfinished or partially done work, extra features,
relearning, handoffs, delays, task switching, and defects.
Software Development Life Cycle: Traditional and Agile- A Comparative Studyijsrd.com
In the field of software development, software development lifecycle is the most important component. There is a number of software development methodologies used in software industry today. The paper discussed below focuses on the modern SDLC which are traditional methods and the agile methods. It also explains the compensation and shortcomings of the traditional as well as agile methods. Along with this, it suggests some improvements which could help in improving current agile development
International Journal of Business and Management Invention (IJBMI)inventionjournals
International Journal of Business and Management Invention (IJBMI) is an international journal intended for professionals and researchers in all fields of Business and Management. IJBMI publishes research articles and reviews within the whole field Business and Management, new teaching methods, assessment, validation and the impact of new technologies and it will continue to provide information on the latest trends and developments in this ever-expanding subject. The publications of papers are selected through double peer reviewed to ensure originality, relevance, and readability. The articles published in our journal can be accessed online
Defect effort prediction models in software maintenance projectsiaemedu
The document discusses models for predicting defects in software maintenance projects. It describes how data on defects found during testing is recorded and used by reliability models to predict remaining defects. The paper proposes exploring defect data through appropriate statistics and predictive models like decision trees and Naive Bayes classifiers. It outlines steps for analyzing defect data with statistics to gain insights, including using ratios of defects found before and after release to assess quality. Graphs are suggested to examine the impact of previous releases on current release quality.
Modelling Determinants of Software Development Outsourcing for NigeriaIJMTST Journal
Software Development Outsourcing is one of the common practices in global business operations today; a
practice that has to a large extent changed the landscape of IT services in Nigeria. This research predicts a
fitted model using a number of success factors, for software development outsourcing in Nigeria. The
researchers adopted six success factors (Cost Saving and Financial Stability, Effective Communication and
Trust, Technical Expertise and Knowledge Transfer, Understanding Software Development Outsourcing
Industry, Effective Software Privacy and Security, and Overcome Cultural Barrier) for use from a prior study
carried out using factor analysis; and these six success factors were analysed using multiple regression to
determine those that are critical for software development outsourcing. The result of the analysis indicates
that both individually and collectively, the six success factors are all critical to software development
outsourcing in Nigeria. A model was thus derived to predict successful software development outsourcing;
휸 = −ퟏ. ퟏퟎퟗ + ퟎ. ퟐퟏퟏ푿₁ + ퟎ. ퟐퟑퟒ푿₂ + ퟎ. ퟐퟐퟓ푿₃ + ퟎ. ퟐퟓퟐ푿₄ + ퟎ. ퟏퟗퟔ푿₅ + 0.188푿₆, with 휸denoting the predicted
outcome (successful software development outsourcing), and 푋₁ to 푋₆ denotes the six independent predictor
variables. IT Businesses and organizations in Nigeria should therefore pay maximum attention to these
critical success factors in other to achieve a significant stride in outsourcing the development of their
software. In addition, the result of this research can be applied in further studies as well as in literatures.
Software Metrics for Identifying Software Size in Software Development ProjectsVishvi Vidanapathirana
This paper defines the best software metrics that can be used to define the size of the software in the current industry of information technology (IT)
The document discusses several software development life cycle models:
- The phased model segments development into phases like analysis, design, implementation, testing and maintenance.
- The cost model views the life cycle in terms of costs incurred in each phase and modifying previous work.
- Prototyping involves building initial versions to explore technical issues and illustrate requirements for the customer.
- Successive versions refines an initial product skeleton through multiple iterations.
Planning the development process involves choosing a life cycle model and defining documents, milestones and reviews. This provides structure and visibility needed for control and quality.
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.
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.
Modern gadgets and machines such as medical equipments, mobile phones, cars and even military hardware run on software. The operational efficiency and accuracy of these machines are critical to life and the well being of modern civilization. When the software powering these machines fail it exposes life to danger and can cause the failure of businesses. In this paper, software quality measure is presented with the emphasis on improving standard and controlling damages that may result from badly developed application. The research shows various software quality standards and quality metrics and how they can be applied. The application of the metrics in measuring software quality in the research produced results which shows that the code metrics performance is better than the design metrics performance and points to a new way of improving quality by refactoring application code instead of developing new designs. This is believed to ensure reusability and reduced failure rate when software is developed
STRATEGIES TO REDUCE REWORK IN SOFTWARE DEVELOPMENT ON AN ORGANISATION IN MAU...ijseajournal
Rework is a known vicious circle in software development since it plays a central role in the generation of
delays, extra costs and diverse risks introduced after software delivery. It eventually triggers a negative
impact on the quality of the software developed. In order to cater the rework issue, this paper goes in depth
with the notion of rework in software development as it occurs in practice by analysing a development
process on an organisation in Mauritius where rework is a major issue. Meticulous strategies to reduce
rework are then analysed and discussed. The paper ultimately leads to the recommendation of the best
strategy that is software configuration management to reduce the rework problem in software development
Requirement Engineering Challenges in Development of Software Applications an...Waqas Tariq
Requirement Engineering acts as foundation for any software and is one of the most important tasks. Entire software is supported by four pillars of requirement engineering processes. Functional and non-functional requirements work as bricks to support software edifice. Finally, design, implementation and testing add stories to construct entire software tower on top of this foundation. Thus, the base needs to be well-built to support rest of software tower. For this purpose, requirement engineers come across with numerous challenges to develop successful software. The paper has highlighted requirement engineering challenges encountered in development of software applications and selection of right customer-off-the-shelf components (COTS). Comprehending stakeholder’s needs; incomplete and inconsistent process description; verification and validation of requirements; classification and modeling of extensive data; selection of COTS product with minimum requirement modifications are foremost challenges faced during requirement engineering. Moreover, the paper has discussed and critically evaluated challenges highlighted by various researchers. Besides, the paper presents a model that encapsulates seven major challenges that recur during requirement engineering phase. These challenges have been further categorized into problems. Furthermore, the model has been linked with previous research work to elaborate challenges that have not been specified earlier. Anticipating requirement engineering challenges could assist requirement engineers to prevent software tower from any destruction.
Testing desktop application police station information management systemSalam Shah
The police stations have adequate importance in the society to control the law and order situations of the country. In Pakistan, police stations manage criminal records and information manually. We have previously developed and improved a desktop application for the record keeping of the different registers of the police stations. The data of police stations is sensitive and that need to be handled within secured and fully functional software to avoid any unauthorized access. For the proper utilization of the newly developed software, it is necessary to test and analyze the system before deployment into the real environment. In this paper, we have performed the testing of an application. For this purpose, we have used Ranorex, automated testing tool for the functional and performance testing, and reported the results of test cases as pass or fail.
This document discusses the evolution of software metrics over time to measure quality as software has become more complex. It outlines how metrics have changed from measuring lines of code and function points to object-oriented and agile metrics that measure concepts like inheritance, cohesion, and velocity. The document also examines how process models like waterfall, spiral, and agile have influenced quality standards and the definition of new metrics. In summary, software metrics have evolved from size-based measures to more sophisticated metrics aligned with modern processes in order to more effectively measure quality attributes as software engineering has advanced.
Exploring the Efficiency of the Program using OOAD MetricsIRJET Journal
This document proposes a methodology to analyze the efficiency of object-oriented programs using OOAD (Object Oriented Analysis and Design) metrics. The methodology involves compiling a program successively until it is error-free, recording the error rate at each compilation. These results are then compared to determine how many compilations were needed for the program to be error-free, indicating its efficiency. The methodology is experimentally validated on a sample Java program, with results showing the error rate decreasing with each compilation until the program is error-free after the 8th compilation, demonstrating good efficiency.
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.
Requirements Analysis and Design in the Context of Various Software Developme...zillesubhan
This document provides a comparative analysis of requirements analysis and design phases between traditional and agile software development approaches. It discusses the importance of requirements analysis and outlines the key stages in a traditional software development lifecycle, including requirements analysis, system design, coding, testing, and maintenance. The document also examines requirements engineering processes and sources of requirements. It describes the goals and importance of software design as a key phase for implementing requirements and allowing flexibility for changes.
IRJET- Factors Affecting the Delivery of Quality Software and their Relations...IRJET Journal
This document discusses factors that affect the delivery of quality software and their relationship to the software development process. It identifies key factors such as the amount of testing, costs involved, time spent, and following proper software development life cycle (SDLC) phases. The document presents a literature review on how these factors influence software quality. It then defines variables, hypotheses, and a regression model to analyze the relationship between delivery of quality software and the identified factors. The results of distributing and analyzing questionnaires indicate that amount of testing, costs involved, and time spent have a statistically significant correlation with delivering quality software. Therefore, paying attention to these factors during development can help improve software quality.
Estimating agile development in the Federal Government domain requires more than just defining Story Points and planning Sprints. These estimates must follow the guidance in OMB A-11 Part 7 and other document based management of budget and performance measures.
A User Story Quality Measurement Model for Reducing Agile Software Developmen...ijseajournal
The document discusses a user story quality measurement (USQM) model for reducing risks in agile software development. It proposes that user story quality is key to affecting development efficiency and handling requirements changes. The USQM model analyzes and collects critical user story quality factors, including clarity, complexity, modularity, configuration management, version control, and testability. By quantifying these factors, the USQM aims to identify quality defects and enhance user stories, thereby reducing development risks from requirements changes.
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.
This document provides a review of systematic quality software designing and development practices. It discusses software engineering processes, quality processes, design and development modeling approaches, and related works. The key points are:
1) Software engineering processes aim to ensure quality, meet deadlines, and manage expectations through defined stages and deliverables. Common models include waterfall, spiral, and agile.
2) Software quality processes evaluate and improve aspects like reliability, maintainability, and interoperability. Metrics and techniques are used to measure qualities.
3) Design and development involve life cycles, methods, and notations to systematically model requirements, architecture, and implementation. Waterfall and rapid prototyping are example models.
FISHBONE ANALYSIS ON WASTES IN SOFTWARE DEVELOPMENT USING THE LEAN I.T. PRINC...ecij
The transformative global economy posed challenges to businesses in service management. In this computing age, the perceptual and operational edge of a certain business or organization manifested on the kind of technology it offers in the Service Management. Organizations have long recognized the
importance of managing key resources such as people and information. Information has now moved to its rightful place as a key resource in the organization and therefore management of the same can be instituted by employing methodology. To keep their brand promise, technology has been used;The number of new entrants to every sectors of economy has grown significantly in recent years, and each firm strives to make their daily operation efficient in which demand for business software or application software getting higher and businesses or organizations opted to build or buy this software. Because of
new entrants, it had offered opportunity to software developers to translate business processes into systems. This study investigates waste in the software development by application of Lean principles. Like any conventional projects, software becomes buggy and oftentimes it fails. Software failure is always attributed to the software engineering, not the incompetence of project managers, inadequacy of the
people on the project, or lack of clear goal. The researchers’ contentions are there wastes in the software development and serve as mechanism and evidence to why software fails. Software failure is not attributed to the software itself, it includes however the acceptance of the clients and end-users. Descriptive secondary data analysis, participant observation and Fishbone Analysis were the methodology used in the study. Wastes include unfinished or partially done work, extra features,
relearning, handoffs, delays, task switching, and defects.
Software Development Life Cycle: Traditional and Agile- A Comparative Studyijsrd.com
In the field of software development, software development lifecycle is the most important component. There is a number of software development methodologies used in software industry today. The paper discussed below focuses on the modern SDLC which are traditional methods and the agile methods. It also explains the compensation and shortcomings of the traditional as well as agile methods. Along with this, it suggests some improvements which could help in improving current agile development
International Journal of Business and Management Invention (IJBMI)inventionjournals
International Journal of Business and Management Invention (IJBMI) is an international journal intended for professionals and researchers in all fields of Business and Management. IJBMI publishes research articles and reviews within the whole field Business and Management, new teaching methods, assessment, validation and the impact of new technologies and it will continue to provide information on the latest trends and developments in this ever-expanding subject. The publications of papers are selected through double peer reviewed to ensure originality, relevance, and readability. The articles published in our journal can be accessed online
Defect effort prediction models in software maintenance projectsiaemedu
The document discusses models for predicting defects in software maintenance projects. It describes how data on defects found during testing is recorded and used by reliability models to predict remaining defects. The paper proposes exploring defect data through appropriate statistics and predictive models like decision trees and Naive Bayes classifiers. It outlines steps for analyzing defect data with statistics to gain insights, including using ratios of defects found before and after release to assess quality. Graphs are suggested to examine the impact of previous releases on current release quality.
Modelling Determinants of Software Development Outsourcing for NigeriaIJMTST Journal
Software Development Outsourcing is one of the common practices in global business operations today; a
practice that has to a large extent changed the landscape of IT services in Nigeria. This research predicts a
fitted model using a number of success factors, for software development outsourcing in Nigeria. The
researchers adopted six success factors (Cost Saving and Financial Stability, Effective Communication and
Trust, Technical Expertise and Knowledge Transfer, Understanding Software Development Outsourcing
Industry, Effective Software Privacy and Security, and Overcome Cultural Barrier) for use from a prior study
carried out using factor analysis; and these six success factors were analysed using multiple regression to
determine those that are critical for software development outsourcing. The result of the analysis indicates
that both individually and collectively, the six success factors are all critical to software development
outsourcing in Nigeria. A model was thus derived to predict successful software development outsourcing;
휸 = −ퟏ. ퟏퟎퟗ + ퟎ. ퟐퟏퟏ푿₁ + ퟎ. ퟐퟑퟒ푿₂ + ퟎ. ퟐퟐퟓ푿₃ + ퟎ. ퟐퟓퟐ푿₄ + ퟎ. ퟏퟗퟔ푿₅ + 0.188푿₆, with 휸denoting the predicted
outcome (successful software development outsourcing), and 푋₁ to 푋₆ denotes the six independent predictor
variables. IT Businesses and organizations in Nigeria should therefore pay maximum attention to these
critical success factors in other to achieve a significant stride in outsourcing the development of their
software. In addition, the result of this research can be applied in further studies as well as in literatures.
Software Metrics for Identifying Software Size in Software Development ProjectsVishvi Vidanapathirana
This paper defines the best software metrics that can be used to define the size of the software in the current industry of information technology (IT)
The document discusses several software development life cycle models:
- The phased model segments development into phases like analysis, design, implementation, testing and maintenance.
- The cost model views the life cycle in terms of costs incurred in each phase and modifying previous work.
- Prototyping involves building initial versions to explore technical issues and illustrate requirements for the customer.
- Successive versions refines an initial product skeleton through multiple iterations.
Planning the development process involves choosing a life cycle model and defining documents, milestones and reviews. This provides structure and visibility needed for control and quality.
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.
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.
Modern gadgets and machines such as medical equipments, mobile phones, cars and even military hardware run on software. The operational efficiency and accuracy of these machines are critical to life and the well being of modern civilization. When the software powering these machines fail it exposes life to danger and can cause the failure of businesses. In this paper, software quality measure is presented with the emphasis on improving standard and controlling damages that may result from badly developed application. The research shows various software quality standards and quality metrics and how they can be applied. The application of the metrics in measuring software quality in the research produced results which shows that the code metrics performance is better than the design metrics performance and points to a new way of improving quality by refactoring application code instead of developing new designs. This is believed to ensure reusability and reduced failure rate when software is developed
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
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.
Software Requirements Prioritization: What, Why, and How?IRJET Journal
This document discusses software requirements prioritization, including what it is, why it is needed, and the typical process. Software requirements prioritization is the process of identifying and ranking software requirements based on their importance, urgency, feasibility and their impact on project objectives. It ensures the most critical requirements are addressed first. Requirements prioritization is necessary due to limited resources and the fact that not all requirements can be implemented. The document outlines the typical steps in requirements prioritization process and discusses factors that must be considered, such as perspectives of customers, business needs, and technical constraints. Finally, it provides an overview of different techniques used for prioritizing requirements.
ANALYSIS OF SOFTWARE QUALITY USING SOFTWARE METRICSijcsa
Software metrics have a direct link with measurement in software engineering. Correct measurement is the prior condition in any engineering fields, and software engineering is not an exception, as the size and complexity of software increases, manual inspection of software becomes a harder task. Most Software Engineers worry about the quality of software, how to measure and enhance its quality. The overall objective of this study was to asses and analysis’s software metrics used to measure the software product and process.
In this Study, the researcher used a collection of literatures from various electronic databases, available since 2008 to understand and know the software metrics. Finally, in this study, the researcher has been identified software quality is a means of measuring how software is designed and how well the software conforms to that design. Some of the variables that we are looking for software quality are Correctness, Product quality, Scalability, Completeness and Absence of bugs, However the quality standard that was used from one organization is different from others for this reason it is better to apply the software metrics to measure the quality of software and the current most common software metrics tools to reduce the subjectivity of faults during the assessment of software quality. The central contribution of this study is an overview about software metrics that can illustrate us the development in this area, and a critical analysis about the main metrics founded on the various literatures.
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.
Software quality model based on development team characteristicsIJECEIAES
Many factors have a significant impact on producing high-quality software products. Development team members are among the most important factors. Paying attention to the quality from this perspective will be a good innovation in the software development industry. Given that team members play a very important role in software products, this study tries to focus specifically on team characteristics in software product quality and provide a qualitative model based on this. The required data were collected through observations and interviews with project managers and development team members in several companies under study. Then, data were analyzed through hierarchical analysis. According to the results, the use of this model led to the improvement of the software development process so that the team members were satisfied with it. Also, time management was improved, and the customer expressed his satisfaction with the use of this model. Finally, data analysis showed that this model may lead to faster product delivery.
A Review and Analysis on Mobile Application Development Processes using Agile...IJORCS
This document provides a review and analysis of mobile application development processes using agile methodologies. It begins with an introduction to agile software development and discusses how agile principles are a natural fit for mobile application development given the dynamic environment. The document then reviews several proposed mobile application development processes that combine agile and non-agile techniques, including Mobile-D, RaPiD7, a hybrid methodology, MASAM, and a Scrum and Lean Six Sigma integration approach. It concludes by noting that while agile methodologies show promise for mobile development, further empirical validation is still needed.
Productivity Factors in Software Development for PC PlatformIJERA Editor
Identifying the most relevant factors influencing project performance is essential for implementing business strategies by selecting and adjusting proper improvement activities. The two major classification algorithms CRT and ANN that were recommended by the Auto Classifier tool in SPSS Modeler used for determining the most important variables (attributes) of software development in PC environment. While the accuracy of classification of productive versus non-productive cases are relatively close (72% vs 69%), their ranking of important variables are different. CRT ranks the Programming Language as the most important variable and Function Points as the least important. On the other hand, ANN ranks the Function Points as the most important followed by team size and Programming Language.
Software metric analysis methods for product development maintenance projectsIAEME Publication
This document discusses various software metrics and methods for analyzing metrics to improve the software development process. It begins with an introduction to software metrics and their importance for project management. It then describes common software development phases and associated metrics that can be collected at each phase. The remainder of the document focuses on different methods for analyzing metrics, including pie charts, Pareto diagrams, bar charts, line charts, scatter diagrams, radar diagrams, and control charts. These analysis methods help identify areas for process improvement and determine if changes have led to desired outcomes.
Software metric analysis methods for product developmentiaemedu
This document discusses various software metrics and methods for analyzing metrics to improve the software development process. It begins with an introduction to software metrics and their importance for project management. It then describes common software development phases and associated metrics that can be collected at each phase, such as lines of code, defects, and staff hours. The document proceeds to explain different types of charts and diagrams that can be used to analyze and visualize metrics data, including pie charts, Pareto diagrams, histograms, line charts, scatter plots, radar diagrams, and control charts. These various analysis methods help identify areas for process improvement and determine whether changes have resulted in desired outcomes.
Software metric analysis methods for product developmentiaemedu
This document discusses various software metrics and methods for analyzing metrics to improve the software development process. It begins with an introduction to software metrics and their importance for project management. It then describes common software development phases and associated metrics that can be collected at each phase, such as lines of code, defects, and staff hours. The document proceeds to explain different types of charts and diagrams that can be used to analyze and visualize metrics data, including pie charts, Pareto diagrams, histograms, line charts, scatter plots, radar diagrams, and control charts. These various analysis methods help identify problems, determine correlations, and track performance over time in order to control and improve the software development process.
An Empirical Investigation Of Critical Challenges In Outsourcing Projects A ...Aaron Anyaakuu
This document describes a survey conducted to validate challenges identified in offshore software development outsourcing projects. The survey received responses from 28 experts, including 5 foreigners. It found that challenges around poor coordination/communication, outsourcing relationships, opportunistic behavior, cultural differences, and project management were most strongly agreed with, receiving over 75% positive responses. The results showed 90% resemblance to findings from previous literature, validating critical challenges in offshore outsourcing projects.
A sustainable procedural method of software design process improvementsnooriasukmaningtyas
In practice, the software process is an intermediate phase for enhancement and improvements the design for different types of software products and help developers to converts the specified requirements into prototypes that implement the design into reality. The objective of this paper is to provide software developers, designers and software engineers who work in small companies with a standards-based process improvement using a procedural method technique including detailed steps for designing the small software systems into their companies. The method used in this paper includes 1) analysis four different types of commonly design processes used by industry such as CMMI, conventional or software process in ISO 19759, generic and engineering design processes. 2) mapping between those four design processes. 3) collect the dispersed design concepts proposed by those four processes. 4) proposed a sustainable procedural method of software design process improvements 5) Illustration of the applicability of the proposed approach using A template-based implementation. The primary result of this study is a guideline procedure with detailed steps for software design process improvements to help and guide developers in small companies to analyze and design a small software scales with limited cost and duration. In conclusion, this paper proposed a method to improve the design process for different kinds of the software systems using a templatebased implementation to reduce the cost, effort and time needed in the implementation phase in small companies. The scientific implication behind a template-based implementation helps the system and software engineering to use this template easily in their small companies; because most of the time those engineering developers are responsible for analyzing, designing, implementing and testing their software systems during the whole software life cycle.
IT PROJECT SHOWSTOPPER FRAMEWORK: THE VIEW OF PRACTITIONERSijseajournal
This document summarizes a study that investigated factors affecting requirements adherence to business processes in agile projects. The study conducted a cross-case analysis of seven companies, collecting data through interviews, observations, and document analysis. The analysis identified that customer business knowledge by the development team and customer availability during requirements elicitation and validation are essential for requirements to align with business needs in agile projects. This allows developed systems to better meet the needs of an organization's business processes.
Software testing is a key part of software engineering used to evaluate software quality and identify errors. There are various software testing techniques and methods, but thoroughly investigating a complex software is more important than following a specific procedure. Testing complex software cannot discover all errors, but can help improve quality. Software engineering involves defining requirements, design, development, testing, and maintenance of software using methodologies like agile development.
Communication, culture, competency, and stakeholder that contribute to requi...IJECEIAES
In the context of software development, requirement engineering is one of the crucial phases that leads to software project success or failure. According to several disruptive changes in the software engineering landscape as well as the world’s challenge of virus pandemic, the provision of practical and innovative software applications is required. Therefore, issues resolution in requirement elicitation is potentially one of the key success factors resulting in enhanced quality of system requirement. The authors have striven to create new ways of requirement elicitation according to factor effects of communication, culture, competency, and stakeholder, by incorporating tools, processes, methods, and techniques to solve the problems comprehensively, and then proposed an adaptive and applicable conceptual framework. To illustrate these effects, the authors performed a literature review from the past 8 years, and then data analysis from interviews of 27 practitioners, observations and focus groups of software development in real-life projects.
Assessment Of Requirement Elicitation Tools And Techniques By Various ParametersKelly Lipiec
The document discusses requirement elicitation tools and techniques. It provides an overview of common requirement elicitation techniques such as interviews, surveys, questionnaires, domain analysis, and prototyping. It also summarizes and compares several popular requirement management tools, including RequisitePro, Objectiver, CaseComplete, RMTrak, Optimal Trace, DOORS, Analyst Pro, and GMARC. The comparison is based on parameters like glossary, templates, and traceability. The paper aims to help select effective tools and techniques for eliciting software requirements.
Similar to AN INVESTIGATION OF SOFTWARE REQUIREMENTS PRACTICES AMONG SOFTWARE PRACTITIONERS: A STUDY IN JEDDAH (20)
How to Make a Field Mandatory in Odoo 17Celine George
In Odoo, making a field required can be done through both Python code and XML views. When you set the required attribute to True in Python code, it makes the field required across all views where it's used. Conversely, when you set the required attribute in XML views, it makes the field required only in the context of that particular view.
How to Fix the Import Error in the Odoo 17Celine George
An import error occurs when a program fails to import a module or library, disrupting its execution. In languages like Python, this issue arises when the specified module cannot be found or accessed, hindering the program's functionality. Resolving import errors is crucial for maintaining smooth software operation and uninterrupted development processes.
How to Setup Warehouse & Location in Odoo 17 InventoryCeline George
In this slide, we'll explore how to set up warehouses and locations in Odoo 17 Inventory. This will help us manage our stock effectively, track inventory levels, and streamline warehouse operations.
How to Manage Your Lost Opportunities in Odoo 17 CRMCeline George
Odoo 17 CRM allows us to track why we lose sales opportunities with "Lost Reasons." This helps analyze our sales process and identify areas for improvement. Here's how to configure lost reasons in Odoo 17 CRM
Walmart Business+ and Spark Good for Nonprofits.pdfTechSoup
"Learn about all the ways Walmart supports nonprofit organizations.
You will hear from Liz Willett, the Head of Nonprofits, and hear about what Walmart is doing to help nonprofits, including Walmart Business and Spark Good. Walmart Business+ is a new offer for nonprofits that offers discounts and also streamlines nonprofits order and expense tracking, saving time and money.
The webinar may also give some examples on how nonprofits can best leverage Walmart Business+.
The event will cover the following::
Walmart Business + (https://business.walmart.com/plus) is a new shopping experience for nonprofits, schools, and local business customers that connects an exclusive online shopping experience to stores. Benefits include free delivery and shipping, a 'Spend Analytics” feature, special discounts, deals and tax-exempt shopping.
Special TechSoup offer for a free 180 days membership, and up to $150 in discounts on eligible orders.
Spark Good (walmart.com/sparkgood) is a charitable platform that enables nonprofits to receive donations directly from customers and associates.
Answers about how you can do more with Walmart!"
Beyond Degrees - Empowering the Workforce in the Context of Skills-First.pptxEduSkills OECD
Iván Bornacelly, Policy Analyst at the OECD Centre for Skills, OECD, presents at the webinar 'Tackling job market gaps with a skills-first approach' on 12 June 2024
हिंदी वर्णमाला पीपीटी, hindi alphabet PPT presentation, hindi varnamala PPT, Hindi Varnamala pdf, हिंदी स्वर, हिंदी व्यंजन, sikhiye hindi varnmala, dr. mulla adam ali, hindi language and literature, hindi alphabet with drawing, hindi alphabet pdf, hindi varnamala for childrens, hindi language, hindi varnamala practice for kids, https://www.drmullaadamali.com
This presentation includes basic of PCOS their pathology and treatment and also Ayurveda correlation of PCOS and Ayurvedic line of treatment mentioned in classics.
ISO/IEC 27001, ISO/IEC 42001, and GDPR: Best Practices for Implementation and...PECB
Denis is a dynamic and results-driven Chief Information Officer (CIO) with a distinguished career spanning information systems analysis and technical project management. With a proven track record of spearheading the design and delivery of cutting-edge Information Management solutions, he has consistently elevated business operations, streamlined reporting functions, and maximized process efficiency.
Certified as an ISO/IEC 27001: Information Security Management Systems (ISMS) Lead Implementer, Data Protection Officer, and Cyber Risks Analyst, Denis brings a heightened focus on data security, privacy, and cyber resilience to every endeavor.
His expertise extends across a diverse spectrum of reporting, database, and web development applications, underpinned by an exceptional grasp of data storage and virtualization technologies. His proficiency in application testing, database administration, and data cleansing ensures seamless execution of complex projects.
What sets Denis apart is his comprehensive understanding of Business and Systems Analysis technologies, honed through involvement in all phases of the Software Development Lifecycle (SDLC). From meticulous requirements gathering to precise analysis, innovative design, rigorous development, thorough testing, and successful implementation, he has consistently delivered exceptional results.
Throughout his career, he has taken on multifaceted roles, from leading technical project management teams to owning solutions that drive operational excellence. His conscientious and proactive approach is unwavering, whether he is working independently or collaboratively within a team. His ability to connect with colleagues on a personal level underscores his commitment to fostering a harmonious and productive workplace environment.
Date: May 29, 2024
Tags: Information Security, ISO/IEC 27001, ISO/IEC 42001, Artificial Intelligence, GDPR
-------------------------------------------------------------------------------
Find out more about ISO training and certification services
Training: ISO/IEC 27001 Information Security Management System - EN | PECB
ISO/IEC 42001 Artificial Intelligence Management System - EN | PECB
General Data Protection Regulation (GDPR) - Training Courses - EN | PECB
Webinars: https://pecb.com/webinars
Article: https://pecb.com/article
-------------------------------------------------------------------------------
For more information about PECB:
Website: https://pecb.com/
LinkedIn: https://www.linkedin.com/company/pecb/
Facebook: https://www.facebook.com/PECBInternational/
Slideshare: http://www.slideshare.net/PECBCERTIFICATION
ISO/IEC 27001, ISO/IEC 42001, and GDPR: Best Practices for Implementation and...
AN INVESTIGATION OF SOFTWARE REQUIREMENTS PRACTICES AMONG SOFTWARE PRACTITIONERS: A STUDY IN JEDDAH
1. International Journal of Software Engineering & Applications (IJSEA), Vol.8, No.3, May 2017
DOI: 10.5121/ijsea.2017.8301 1
AN INVESTIGATION OF SOFTWARE REQUIREMENTS
PRACTICES AMONG SOFTWARE PRACTITIONERS: A
STUDY IN JEDDAH
Azida Zainol1
and Haneen Hassan Al-Ahmadi2
Department of Computer Science, King Abdulaziz University, Jeddah, Kingdom of Saudi
Arabia
ABSTRACT
This paper presents the result of software requirements practices survey among software practitioners, a
study in a city of Jeddah, Saudi Arabia. As software requirements are important and they lead to the
successful of a software development project, it becomes interesting to investigate the current software
requirements practices in the kingdom of Saudi Arabia. As an initial work, a survey was conducted in
Jeddah as a study before we conduct it in the Kingdom of Saudi Arabia software industry. The survey is
conducted by distributing a set of questionnaire to the software practitioners. There are 17 respondents
completed the questionnaire out of 50 distributed questionnaire, which is 34% of response rate. The result
of this survey is promising and it has shown that requirements management area should be focused for
future improvement. In the future, the survey will focus on software engineering and requirements
engineering practices over the entire Kingdom of Saudi Arabia software industry.
KEYWORDS
Software engineering practice, Requirements engineering practice, Software Requirements practice,
Requirements management
1. INTRODUCTION
Nowadays software plays an important role in our lives. Software can be found anywhere across
variety of domain, such as in education, banking, medical and many others. Thus, developing
high quality software is becoming increasing and demanding in these days [1]. In order to ensure
producing high quality software, it is essential to have and manage requirements appropriately
over the entire software development. Hence, it is important to understand how the software
practitioners conducting software requirements during the software development. It has been a
huge issue over a decade in the industry that many organizations are struggling to understand,
document and manage the software requirements [2].
This paper presents the state of the art software requirements practices in the city of Jeddah.
Although this paper presents only a city, it helps us to understand and benchmark how we
practice software requirements against the current state of the art in the software requirements
research area. It shows areas that software practitioners have adequately performed as well as it
shows certain areas that need improvement urgently. Thus, it aids in identifying the energy and
resources to the targeted areas for improvement efficiently.
A survey was conducted in order to understand how the software practitioners conducted the
software requirements and at the same time to get their consent regarding employing an open
source tool during software development. The result of this survey is very promising and it has
shown the software engineering domains that have been conducted comprehensively as well as
domains that need urgent improvement in the future.
2. International Journal of Software Engineering & Applications (IJSEA), Vol.8, No.3, May 2017
2
2. REVIEW
Requirements is defined as a statement of what the system must do or what characteristic it must
have [3]. A complete definition from the IEEE software engineering glossary [4] stated that a
requirements is defined as :
“(1) A condition or capability needed by a user to solve a problem or achieve an
objective; (2) a condition or capability that must be met or possessed by a system
or system component to satisfy a contract, standard, specification, or other
formally imposed documents; (3) a documented representation of a condition or
capability as in (1) or (2).”
Moreover, the Guide to the Software Engineering Body of Knowledge – SWEBOK [5] has
defined software requirements as:
"A property that must be exhibited by something in order to solve some problem in
the real world. It may aim to automate part of a task for someone to support the
business processes of an organization, to correct shortcomings of existing
software, or to control a device—to name just a few of the many problems for
which software solutions are possible."
Theorically, requirements are important during software development because they describe what
the user needs and why the user needs it [6], [7]. It is essential to identify the correct requirements
in the early stage of software development because the cost of correcting a defect that is found
late in the project is far more than to fix it shortly after its creation [8]. One of the major
consequences of requirements problem is rework, rework can consume 30 to 50 percent of total
development cost [9] and requirements error account for 79 to 85 percent of the rework cost [10].
Preventing requirements errors and catching them early therefore has a huge effect on reducing
rework. These days, developing software projects is becoming difficult and challenging. The
majority of software development projects in the USA will take longer, cost more than planned
and result in "out of specification" products that fail to meet user requirements [11]. Moreover, a
report on a survey of over 3800 organizations in 17 European countries concluded that more than
50% of the perceived software problems were in the area of requirements specification and
requirements management [12]. Based on this evidence, it can be stated that requirements are
very important and it should be given extra attention because it leads to the successful of a
software development project.
As software requirements are related to software engineering and requirements engineering, we
reviewed several surveys regarding software engineering and requirements engineering in the
literature. During this literature reviews, we collected the related variables that have been used to
measure the software engineering and requirements management practices.
A survey was conducted among Australian software practitioners regarding their software
development practices during recent software project and the survey helped them to understand
the requirements issues and their relationship with project success [13].
Moreover, a survey of requirements management practices in the Malaysian software industry
was conducted in 2008 [14]. The result of this survey helped them to understand how the
software practitioners conducted their requirements management practices and therefore the areas
which were lack of practices have been identified for improvement.
3. International Journal of Software Engineering & Applications (IJSEA), Vol.8, No.3, May 2017
3
In 2015, a survey of software engineering practices has been conducted in Turkey [15]. The result
of this survey became interested to software engineering professional in Turkey and world-wide.
It has shown the areas of strength and weakness that would encourage the industry and academia
to collaborate in those areas.
Based on these related survey of software engineering generally and specifically for software
requirements, we can constructed the survey based on the measured variables as discuss in
section 3. We also confident that the software engineering practices survey is able to be
conducted in the kingdom of Saudi Arabia software industry in order for us to continue with
empirical study. As an initial work, we focus on a survey in a city of Jeddah in order to
understand the process of investigation in the larger area.
3. METHOD
In this investigation we used a survey to collect the software requirements practices among the
software practitioners who involved in small and medium software development projects in
Jeddah, Kingdom of Saudi Arabia. In this survey, we used questionnaire that contains 19
questions. The questionnaire has two objectives which are to collect the current practices during
software development process and to study how they are dealing with their software requirement.
The questionnaire is designed based on CMMI that focus on requirements management process
area (REQM) [16].
The questionnaire takes about 15 minutes to complete and should be completed by software
engineers or someone who has software development background purposely for small and
medium software projects. It is divided into three main sections, namely demographic profile,
software development process and software requirements practices.
In the demographic section, we are interested to know the background of the respondents so that
the results collected are promising. Hence, we collected the following variables; type of
organization, how many years of experience in software development and the numbers of
employees that involved in software development.
Moreover, in software development section, we are interested to investigate how the software
practitioners conducted software development. Thus, we gathered these variables [1], [13] ,[14],
[15],:
• The frequency of employing a methodology in every software development project
• The use of specific methodology in software development. The methodologies are :
object-oriented development, structured development, information engineering,
prototyping, formal specification or others.
• The use of any requirements management tools that help the respondents in managing
their requirements. The tools are : Rational RequisitePro, RaQuest, Cradle, PACE,
SpeedReq, Caliber-RM, AnalystPro, Tracer, others or never used any tools.
• The need to employ open source requirement management tool that is freely available in
the market.
• The features that the respondents are looking for in a requirements management tool. The
features are [17], [18], [19] :
o The tool should be easy to use. Not too much training and administration needed.
The tool should not create additional tasks and deployment should not require
extensive customization
o The tool must have access control whereby each participants as appropriate
access to the data. (role-based project-based and task based access control)
4. International Journal of Software Engineering & Applications (IJSEA), Vol.8, No.3, May 2017
4
o The tool must be adaptable and extensible to need of the organization or project
o The tool should be free licencing that allow the user to use the tool in full version
without limitation
o The tool should be database centric, but also support document management
o Others, please specify
The questionnaire is designed to collect the software requirements management practices. Thus,
the following variables are designed based on CMMI – Requirements Management (REQM)
process area [16] :
• Do you uniquely identify each requirements?
• Do you defined policies for requirements management?
• Do you record requirements traceability from original sources?
• Do you define traceability policies?
• Do you maintain a traceability manual?
• Do you use a database to manage requirements?
• Do you define change management policies?
• Do you identify global system requirements?
• Do you identify volatile requirements?
• Do you record rejected requirements?
• Do you reuse requirements over different projects?
The questionnaire was administered and distributed using SurveyMonkey. The respondents are
contacted via email and WhatsApp application to take part in the survey by clicking the link
provided.
4. RESULT AND DISCUSSIONS
This section describes the finding of this survey arranging as demographic profile, software
development process and software requirements practices. We distributed the questionnaire to 50
respondents and we managed to collect the complete responses from 17 respondents, given as
34% of complete responses. Although the responses are low, yet, it can show to us the actual
current state of software requirements practices.
4.1. Demographic profile
The first section of the survey is about collecting the demographic profile of the respondents. The
respondents were asked to identify the type of company, namely government, semi government,
private and small and medium enterprise. The result has revealed that majority of the respondents
are working in the private sector with 52.54%, government with 23.53%, small and medium
enterprise 17.65% and semi government with 5.88% as shown in Figure 1.
5. International Journal of Software Engineering & Applications (IJSEA), Vol.8, No.3, May 2017
5
Figure 1. Type of organizations
Subsequently, Figure 2 below presents the experience of the respondents in software
development. Most of the respondents have 3 to 5 year experience (29.41%), 5 to 10 years
(23.41%), more than 10 years (17.65%), less than 1 year (17.65%) and 1 to 3 years (11.76%).
Moreover, Figure 3 depicts the number of employees that involved during software development.
The result shows that 41.18% of the respondents claimed that 11 to 25 employees are involved in
the software development, 17.65% claimed 1 to 5 employees and 26 to 50 employees. In addition,
11.76% of the respondents claimed that 5 to 10 employees and more than 100 employees are
involved in software development. Thus, we can ascertained that all of the respondents have
experienced working in a team during software development.
6. International Journal of Software Engineering & Applications (IJSEA), Vol.8, No.3, May 2017
6
Figure 2. Experience
Figure 3. The number of employees
7. International Journal of Software Engineering & Applications (IJSEA), Vol.8, No.3, May 2017
7
4.2. Software development process
In this survey, we are interested to understand the methodology involved during software
development and what the respondents need toward open source tools. In this survey, we asked
the respondents if they always use proper methodology during software development process.
The result has shown that respondents are equally use and sometime use the proper methodology
during software development (41.18%) and 17.65% never use any proper methodology as shown
in Figure 4. Thus, we can suggest that there is a need to encourage the software practitioners to
use proper methodology in the future.
Furthermore, the survey asked the respondents to identify the most commonly used methodology
during software development. The result has shown that most of the respondents always used
structured development and object oriented is regularly used during software development as
presented in Figure 5.
Figure 4. Proper methodology used
8. International Journal of Software Engineering & Applications (IJSEA), Vol.8, No.3, May 2017
8
Figure 5. Methodology
In this survey, we also interested to know the requirements management tool that the respondents
used in managing their requirements during software development. The result has revealed that
most of the respondents never used any requirements management tool. However, during
software development 5 respondents used Tracer to manager their requirements as shown in
Figure 6.
Figure 6. Requirements management tool
Furthermore, the respondents are asked to give their consent regarding the use of an open source
requirements management tool in the market. The result has shown that 16 out of 17 respondents
agree to use the open source requirements management tool as presented in Figure 7. This is a
9. International Journal of Software Engineering & Applications (IJSEA), Vol.8, No.3, May 2017
9
good indicator to affirm that an open source requirements management tool is needed in the
market. Moreover, the respondents are asked to select features that they are looking forward in
an open source requirements management tool. The features are:
A. The tool should be easy to use. Not too much training and administration needed.
The tool should not create additional tasks and deployment should not require
extensive customization.
B. The tool must have tight access control whereby each participant has appropriate
access to the data. (Role-based, project-based and task based access control.)
C. The tool must be adaptable and extensible to the needs of the organization or
project.
D. The tool should be free licensing that allows the user to use the tool in full
version without limitation.
E. The tool should be database centric, but also support document management.
The result is very promising (Figure 8) as all the respondents decided that the tool should have
the above features in order for the respondents to employ the tool during software development in
the future.
Figure 7. The use of open source requirements management tool
10. International Journal of Software Engineering & Applications (IJSEA), Vol.8, No.3, May 2017
10
Figure 8. Open source requirements management tool features
4.3. Software requirements practices
In this survey we would like to investigate how the respondents practices their requirements over
the entire software development. Thus, we constructed the questionnaire based on the following
practices, as described in Table 1.
The result as described in Figure 9 shown that most of the respondents highly practiced the
following:
• Uniquely identify each requirements
• Record requirements traceability from original sources
• Define traceability policies
• Maintain traceability manual
• Use a database to manage requirements
• Define change management policies
• Identify global system requirements
• Identify volatile requirements
• Record rejected requirements
• Reuse requirements over different projects
However, the respondents claimed that they are low in defining policies for requirements
management policies practice. Thus, it can be seen that the respondents are practising software
requirements partially and there is a room for improvement in this area. It is important to
encourage the respondents to perform software requirements practices entirely over the software
development in order to produce high quality software within the allocation budget and time.
11. International Journal of Software Engineering & Applications (IJSEA), Vol.8, No.3, May 2017
11
Table 1. Software requirements practices.
No Questions
NotApplicable
Unknown
VeryLow
Low
Average
High
VeryHigh
1 Do you uniquely identify each requirement?
1 2 0 0 0 10 4
2 Do you have defined policies for
requirements management?
0 3 0 6 2 1 5
3 Do you record requirements traceability from
original sources?
1 1 0 4 5 6 0
4 Do you define traceability policies?
0 1 6 0 3 7 0
5 Do you maintain a traceability manual?
0 0 5 4 1 7 0
6 Do you use a database to manage
requirements?
0 4 0 1 2 5 4
7 Do you define change management policies?
0 3 3 2 0 7 0
8 Do you identify global system requirements?
0 2 3 0 3 7 2
9 Do you identify volatile requirements?
0 2 0 1 4 5 5
10 Do you record rejected requirements?
0 2 4 0 5 6 0
11 Do you reuse requirements over different
projects?
0 2 2 2 4 7 0
12. International Journal of Software Engineering & Applications (IJSEA), Vol.8, No.3, May 2017
12
Figure 9. Software requirements practices
3. CONCLUSIONS
As a conclusion, this paper has described the software requirements practices among the software
engineers in a study of a city. The result is very promising and it shows that software
practitioners are aware as well as practicing good software requirements partially. We have
identified that extra attention should be given to requirements management area. The software
practitioners are willing to employ open source tool during software development. We are also
able to determine the features of an open source tool.
This survey was conducted only in a city of Jeddah and therefore the result of this survey cannot
be generalized to represent the current software requirements practices in the Kingdom of Saudi
Arabia. However, the result is promising and it is a good indicator for us to conduct a survey in
the Kingdom of Saudi Arabia in the future.
In the future, we will conduct a survey of software engineering and requirements engineering
practices as well as the software projects success factors in the Kingdom of Saudi Arabia. Thus,
this work is an initial work towards the survey of software engineering practices. Generally, this
work has contributed to the software engineering body of knowledge and specifically contributed
to the requirements engineering research area.
ACKNOWLEDGEMENTS
The authors would like to thank King Abdulaziz University for giving us the chances to complete
this work and all the person who have help us to complete this work.
13. International Journal of Software Engineering & Applications (IJSEA), Vol.8, No.3, May 2017
13
REFERENCES
[1] A. Zainol and S. Mansoor, “A Survey of Software Engineering Practices in the Software Industry,” in
Proceeding of The IASTED International Conference on Software Engineering, 2009.
[2] K. Wiegers and J. Beatty, Software Requirements. Pearson Eduction, 2013.
[3] A. Dennis, H. B. Wixom, and D. Tegarden, System Analysis and Design with UML Version 2.0: An
Object Oriented Approach, Third. USA: John Wiley & Sons Ltd., 2005.
[4] IEEE, “IEEE Standard Glosary of Software Engineering Terminology (ANSI),” (1-55937-
0([SH13748-NYF]), 1990.
[5] A. Abran, P. Bourque, R. Dupuis, and J. W. Moore, Guide to the Software Engineering Body of
Knowledge - SWEBOK. Piscataway, NJ, USA: IEEE Press, 2001.
[6] P. Roger and B. Maxim, Software Engineering: A Practitioner’s Approach, 8th Editio. McGraw Hill
Education, 2015.
[7] I. Sommerville, Software Engineering, 10th Editi. Edinburgh: Pearson Eduction, 2015.
[8] R. B. Grady, “An economic release decision model: Insights into software project management.,” in
Proceedings of the Applications of Software measurement Conference, 1999.
[9] B. W. Boehm and P. N. Papaccio, “Understanding and Controlling Software Cost,” IEEE Trans.
Softw. Eng., vol. 14, no. 10, pp. 1462–1476, 1988.
[10] D. Leffingwell, “Calculating your return on investment from more effective requirements
management,” Am. Program., vol. 10, no. 4, pp. 13–16, 1997.
[11] L. J. May, “Major causes of software project failures,” CrossTalk J. Def. Softw. Eng., vol. 11, no. 6,
pp. 9–12, 1998.
[12] Javed, Talha, and Q. S. Durrani, “A study to investigate the impact of requirements instability on
software defects,” ACM SIGSOFT Softw. Eng. Notes, vol. 29, no. 3, pp. 1–7, 2004.
[13] J. Verner, A. Park, K. Cox, A. Park, S. Bleistein, C. Science, and N. Cerpa, “AJIS Vol 13, No. 1
September 2005 REQUIREMENTS ENGINEERING AND SOFTWARE PROJECT SUCCESS: AN
INDUSTRIAL SURVEY IN AUSTRALIA AND THE U.S.,” Australas. J. Inf. Syst., vol. 13, no. 1,
pp. 225–238, 2005.
[14] A. Zainol and S. Mansoor, “Investigation into requirements management practices in the malaysian
software industry,” in Proceedings - International Conference on Computer Science and Software
Engineering, CSSE 2008, 2008, vol. 2, pp. 292–295.
[15] V. Garousi, A. Co, A. Betin-can, and O. Demirörs, “A Survey of Software Engineering Practices in
Turkey,” J. Syst. Softw., vol. 108, pp. 148–177, 2015.
[16] C. P. Team, “CMMI ® for Development , Version 1 . 2,” no. August, 2006.
[17] M. Hoffmann, N. Kuhn, M. Weber, and M. Bittner, “Requirements for requirements management
tools,” in Proceedings. 12th Requirements Engineering IEEE International, 2004.
[18] D. M. Alghazzawi, S. T. Sidddiqui, M. U. Bokhari, and H. S. A. Hamatta, “Selecting Appropriate
Requirements Management Tool for Developing Secure Enterprises Software,” Int. J. Inf. Technol.
Comput. Sci., vol. 4, no. March, pp. 49–55, 2014.
[19] M. Lang and J. Duggan, “A Tool to Support Collaborative Software Requirements Management,”
Requir. Eng., vol. 6, no. 3, pp. 161–172, 2001.
14. International Journal of Software Engineering & Applications (IJSEA), Vol.8, No.3, May 2017
14
Authors
Azida Zainol is an Assistant Professor at Department of Computer Science, King
Abdulaziz University, Jeddah. Her research interests are software engineering,
requirements engineering, and software modelling and software quality assurance.
Haneen Hassan Al-Ahmadi graduated from Universiti Putra Malaysia in year 2005
with a Master's Degree and PhD in 2016. Her research interests are software engineering
and software quality