30 citations · 71 across the 7 of their papers we have counts for
10 papers · 1 filter
A Case Study of Building Shared Understanding of Non-Functional Requirements in a Remote Software Organization
Laura Okpara, Colin Werner, Adam Murray +1
Building a shared understanding of non-functional requirements (NFRs) is a known but understudied challenge in requirements engineering, especially in organizations that adopt cont…
Continuously Managing NFRs: Opportunities and Challenges in Practice
Colin Werner, Ze Shi Li, Derek Lowlind +3
Non-functional requirements (NFR), which include performance, availability, and maintainability, are vitally important to overall software quality. However, research has shown NFRs…
How angry are your customers? Sentiment analysis of support tickets that escalate
Colin Werner, Lloyd Montgomery, Sanja Dodos +3
Software support ticket escalations can be an extremely costly burden for software organizations all over the world. Consequently, there exists an interest in researching how to be…
Customer Support Ticket Escalation Prediction using Feature Engineering
Lloyd Montgomery, Daniela Damian, Tyson Bulmer +1
Understanding and keeping the customer happy is a central tenet of requirements engineering. Strategies to gather, analyze, and negotiate requirements are complemented by efforts t…
Predicting Developers' IDE Commands with Machine Learning
Tyson Bulmer, Lloyd Montgomery, Daniela Damian
When a developer is writing code they are usually focused and in a state-of-mind which some refer to as flow. Breaking out of this flow can cause the developer to lose their train…
The Lack of Shared Understanding of Non-Functional Requirements in Continuous Software Engineering: Accidental or Essential?
Colin Werner, Ze Shi Li, Neil Ernst +1
Building shared understanding of requirements is key to ensuring downstream software activities are efficient and effective. However, in continuous software engineering (CSE) some…