A rational design process: How and why to fake it
IEEE Transactions on Software Engineering
System development methods—a comparative investigation
MIS Quarterly
Communication breakdowns and boundary spanning activities on large programming projects
Empirical studies of programmers: second workshop
Successful application of communication techniques to improve the systems development process
Information and Management
Software requirements: objects, functions, and states
Software requirements: objects, functions, and states
Technology—process fit: perspectives on achieving prototyping effectiveness
Journal of Management Information Systems - Special issue on management support systems
Managing I/S design teams: a control theories perspective
Management Science
Coordination in software development
Communications of the ACM
A process model of application software package acquisition and implementation
Journal of Systems and Software
On human cognition and the design of information systems
Information and Management
Software projects: evolutionary vs. big-bang delivery
Software projects: evolutionary vs. big-bang delivery
The effects of development process modeling and task uncertainty on development quality performance
Information and Management
An assessment of the prototyping approach to information systems development
Communications of the ACM
Learning to specify information requirements: the relationship between application and methodology
Journal of Management Information Systems - Special section: Strategic and competitive information systems
Performance Evaluation of Software Development Teams: a Practical Case Study
Electronic Notes in Theoretical Computer Science (ENTCS)
Hi-index | 0.00 |
The quality of software is a real concern that can be seen in almost any organization where software results contribute to success. However, a gap is perceived in the efforts that have being carried out to improve the software quality. System requirements are recognized as a critical step in the development of quality software. Being the first step in the process of software engineering, the effort has potential to shape the direction for all subsequent software development project activities. In this paper, the researcher analyzes the effects of requirements uncertainty and task uncertainty on outcomes in software development projects, limiting the attention to quality of software product. A cross-sectional survey of one hundred and twenty-three participants in thirty-four organizations was employed to prove the research model. The findings were drawn from an examination of the research propositions. Analyzed data provided evidence of a significant negative association between requirements uncertainty and software product quality. Moreover, the data provided evidence of a negative significant association between task uncertainty and software product quality. Furthermore, requirements uncertainty and task uncertainty do not interact with one another to influence the software development outcomes. This means that requirements uncertainty and task uncertainty act independently of each other.