Author:
Jie Liu
Affiliation:
Western Oregon University, United States
Keyword(s):
Project management, Software engineering, Cost estimations, System requirements, Quality control.
Related
Ontology
Subjects/Areas/Topics:
Application Integration Technologies
;
Applications
;
Architectural Design and Meta Architectures
;
Cross-Feeding between Data and Software Engineering
;
Paradigm Trends
;
Requirements Engineering Frameworks and Models
;
Service-Oriented Software Engineering and Management
;
Software and Systems Development Methodologies
;
Software Engineering
;
Software Process Improvement
Abstract:
In the software industry, many deployed projects suffered one or more of the following: they had fewer features than planned, they were late on their deployment, or they were over budget. We participated in a project that suffered all of these. More significantly, it overran the budget by at least 400%.
Looking back, many wrong decisions were made, such as misjudged users’ expectations and their environments, subscribed over complicated backend architecture, and selected a different programming language that was unable to reuse existing code, etc. In this paper, serving as a case study, we argue that an effective approach to contain the cost of a software project, especially internal software, is to build a system that answer the core requirements with room for improvement, not to build the best system in the market.