The role of blogging in generating a software product vision

Authors:
Shelly Park;Frank Maurer
Affiliations:
University of Calgary, Department of Computer Science, Alberta, Canada;University of Calgary, Department of Computer Science, Alberta, Canada
Venue:
CHASE '09 Proceedings of the 2009 ICSE Workshop on Cooperative and Human Aspects on Software Engineering
Year:
2009

Citing 3
Cited 8

Extreme programming explained: embrace change

Extreme programming explained: embrace change
REQUIREMENTS: Requirements and Testing: Seven Missing-Link Myths

IEEE Software
Envisioning the Next Generation of Functional Testing Tools

IEEE Software

Web2SE: First Workshop on Web 2.0 for Software Engineering

Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 2
Workshop report from Web2SE: first workshop on web 2.0 for software engineering

ACM SIGSOFT Software Engineering Notes
The impact of social media on software engineering practices and tools

Proceedings of the FSE/SDP workshop on Future of software engineering research
Smart media: bridging interactions and services for the smart internet

The smart internet
Measuring API documentation on the web

Proceedings of the 2nd International Workshop on Web 2.0 for Software Engineering
Second international workshop on web 2.0 for software engineering (Web2SE 2011)

Proceedings of the 33rd International Conference on Software Engineering
Smart media: bridging interactions and services for the smart internet

The smart internet
Mutual assessment in the social programmer ecosystem: an empirical investigation of developer profile aggregators

Proceedings of the 2013 conference on Computer supported cooperative work

Quantified Score

Hi-index	0.00

Visualization

Abstract

The core problem with requirements engineering is that often even the customers have no clear idea what they need; they don't know how to express it; or even if they express it really well, what they thought they need wasn't what they really need. Despite having the technical skills and being able to speak the domain language, generating requirements for software developers by the developers is found to be quite a difficult task. We discuss four types of strategies for expressing one's desire for requirements. We analyze how stories turn into consensus.