Proceedings ArticleDOI
Requirements Engineering so Things Don't Get Ugly
Deb Jacobs
- pp 159-160
Reads0
Chats0
TLDR
A great start for fixing this long-standing software development crisis is with requirements; the authors must fully understand what they are developing before they can develop the right product for their customers.Abstract:
Regardless of which report you read, the battle cry is loud and clear "Projects are failing more often than they are successful. Something must be done!" But what? That's the million dollar question. A great start for fixing this long-standing software development crisis is with requirements; we must fully understand what we are developing before we can develop the right product for our customers. Readers will probably shake their head and say "Of course we do " but statistics show that even though this seems to be a "no brainer" we still aren't doing it.read more
Citations
More filters
Proceedings ArticleDOI
The Influence of Situational Factors in Software Product Management: An Empirical Study
TL;DR: This research shows that situational factors influence the selection process of method fragments for SPM in two applications: SPM process maintenance - the influence level of SFs on the SPM processes: if the SF changes value the S PM process may need to be changed; and method fragment choice - selecting a method which fits the situational context of the company.
Journal ArticleDOI
Fuzzy Specification in Real Estate Market Decision Making
TL;DR: A software tool designed as a decision aid system for all actors being involved when buying or selling real state, client and realtor, where a main objective for the commercial is to concentrate the client preferences into few alternatives.
Journal ArticleDOI
Factors generating risks during requirement engineering process in global software development environment
TL;DR: A systematic literature review is done for the identification of these factors and the risks which may occur during requirement engineering process in global software development paradigm and the list leads to progressive enhancement for assisting in requirement engineering activities in globalSoftware development paradigm.
Proceedings ArticleDOI
A Traceability Metamodel for Change Management of Non-functional Requirements
TL;DR: This paper proposes a metamodel which explicitly captures NFRs and their relations, and which is independent from any programming paradigm, and presents an implementation using XML-based representations for the metAModel and XQuery queries to represent tracing information.
Proceedings ArticleDOI
A Metamodel for Tracing Non-functional Requirements
TL;DR: The metamodel, which is independent from any programming paradigm, is further transformed into a relational model which facilitates NFRs traceability using tracing queries implemented through "Datalog" expressions.
References
More filters
Book
Mastering the Requirements Process
TL;DR: Through discussions, interaction and demonstrations, you ensure that you have the requirements process that is suitable for your organization.
Journal ArticleDOI
What went wrong? Unsuccessful information technology projects
TL;DR: The results of a survey questionnaire sent to Canada’s 1,450 leading public and private institutions found that the three most common reasons for project failure are poor project planning, a weak business case, and a lack of top management involvement and support.
Journal ArticleDOI
Writing good requirements
TL;DR: This paper will address what makes a good requirement and cover some of the most common problems that are encountered in writing requirements and then describe how to avoid them.
Book
The elements of UML style
TL;DR: Agile modeling for the UML 12 Summary Index is described, which aims to provide real-time information about how the model is implemented and how it is implemented in the rapidly changing environment.