Grin logo
en de es fr
Shop
GRIN Website
Publish your texts - enjoy our full service for authors
Go to shop › Computer Science - Software

Role of software requirements management tools in rework & software project success

Title: Role of software requirements management tools in rework & software project success

Master's Thesis , 2015 , 148 Pages , Grade: 1

Autor:in: Faisal Adnan (Author), Dr. Imran Haider Naqvi (Author)

Computer Science - Software
Excerpt & Details   Look inside the ebook
Summary Excerpt Details

This research quantified the role of the different factors of rework including project planning (PP), software requirements specifications document quality (SRSDQ), software testing (ST), software requirements management (SRM), software requirements traceability (SRT), maturity of software development life cycle (SDLC) approach (MSDLCA), changing requirements (CR) & scope creep (SC) with rework & project success (PS) using automated software requirements management tools (UseofSRMT). The underlying associations of the above factors of rework in SDLC and UseofSRMT with rework & PS were quantified through a survey conducted in the software houses. The study quantified the magnitude of rework which was increased/decreased by these factors of rework. The study also quantified the magnitude of PS increased/decreased by these factors of rework. This study concluded that UseofSRMT played a moderating role between factors of rework and PS. The study also quantified the mediating role of rework between the factors of rework & PS. The study contributed that rework was avoidable in SDLC. Major causes of unsuccessful software projects were determined. Most effective features of software requirements management tools (SRMT) were considered to determine their role as an effective methodology for PS. PS could never be guaranteed by just achieving project milestones/goals in terms of the triple constraints of time, budget & schedule.

Excerpt


Inhaltsverzeichnis (Table of Contents)

  • Introduction
    • Problem Statement
    • Research Questions
    • Research Objectives
    • Research Methodology
    • Significance of the Study
    • Scope of the Study
    • Limitations of the Study
  • Literature Review
    • Rework in Software Development
    • Software Requirements Management
    • Software Requirements Management Tools
    • Software Project Success
  • Research Framework
    • Conceptual Framework
    • Research Model
  • Data Collection and Analysis
    • Data Collection Method
    • Data Analysis Techniques
  • Findings and Discussion
    • Role of Software Requirements Management Tools in Rework
    • Impact of Software Requirements Management Tools on Software Project Success
  • Conclusions and Recommendations

Zielsetzung und Themenschwerpunkte (Objectives and Key Themes)

This research aims to quantify the role of different factors related to rework and their impact on software project success. Specifically, the study investigates the moderating role of automated software requirements management tools (SRMT) in mitigating the effects of rework on project success.

  • The impact of rework on software project success
  • The role of software requirements management (SRM) in reducing rework
  • The effectiveness of automated SRMT in achieving project success
  • The factors contributing to rework in software development life cycle (SDLC)
  • The relationship between rework and project success

Zusammenfassung der Kapitel (Chapter Summaries)

  • Introduction: This chapter introduces the research problem, outlines the research questions and objectives, and discusses the significance, scope, and limitations of the study.
  • Literature Review: This chapter provides a comprehensive review of existing literature on rework in software development, software requirements management, software requirements management tools, and software project success.
  • Research Framework: This chapter presents the conceptual framework and research model that guide the study. It outlines the key variables and relationships investigated in the research.
  • Data Collection and Analysis: This chapter describes the data collection method, including the survey instrument used, and the data analysis techniques employed to examine the relationships between the variables of interest.
  • Findings and Discussion: This chapter presents the findings of the study, analyzing the role of SRMT in reducing rework and improving software project success. It discusses the implications of the findings and explores potential explanations for the observed relationships.

Schlüsselwörter (Keywords)

This research focuses on the role of software requirements management tools (SRMT) in mitigating rework and enhancing software project success. Key themes include rework, software requirements management, software development life cycle, project success, and the effectiveness of SRMT in achieving project goals.

Frequently Asked Questions

What is the impact of rework on software project success?

Rework is a significant factor that can decrease the magnitude of project success. This research quantifies how factors like changing requirements and project planning relate to rework and overall success.

How do Software Requirements Management Tools (SRMT) help?

Automated SRMT play a moderating role between the factors that cause rework and project success. They help in managing requirements more effectively to mitigate the risks of failure.

Is rework avoidable in the Software Development Life Cycle (SDLC)?

The study contributes to the field by concluding that rework is indeed avoidable within the SDLC if proper management and tools are utilized.

What are the major causes of unsuccessful software projects?

Major causes determined include poor software requirements specifications document quality (SRSDQ), scope creep (SC), and changing requirements (CR).

Can project success be guaranteed by meeting time and budget constraints?

No, the study suggests that project success can never be guaranteed solely by achieving milestones related to the triple constraints of time, budget, and schedule.

What are the most effective features of SRMT?

The research considers various features of these tools to determine their role as an effective methodology for ensuring software project success (PS).

Excerpt out of 148 pages  - scroll top

Details

Title
Role of software requirements management tools in rework & software project success
Course
MS in Project Management
Grade
1
Authors
Faisal Adnan (Author), Dr. Imran Haider Naqvi (Author)
Publication Year
2015
Pages
148
Catalog Number
V307194
ISBN (eBook)
9783668052505
ISBN (Book)
9783668052512
Language
English
Tags
role
Product Safety
GRIN Publishing GmbH
Quote paper
Faisal Adnan (Author), Dr. Imran Haider Naqvi (Author), 2015, Role of software requirements management tools in rework & software project success, Munich, GRIN Verlag, https://www.grin.com/document/307194
Look inside the ebook
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
  • Depending on your browser, you might see this message in place of the failed image.
Excerpt from  148  pages
Grin logo
  • Grin.com
  • Shipping
  • Imprint
  • Privacy
  • Terms
  • Imprint