Software requirements: objects, functions, and states
Software requirements: objects, functions, and states
Mastering the requirements process
Mastering the requirements process
Organizing new interactions: internet portals in the instructional computer lab
SIGUCCS '01 Proceedings of the 29th annual ACM SIGUCCS conference on User services
Requirements interaction management in an eXtreme programming environment: a case study
Proceedings of the 27th international conference on Software engineering
Customer relationships and Extreme Programming
HSSE '05 Proceedings of the 2005 workshop on Human and social factors of software engineering
Seeking activity: on the trail of users in open and community source frameworks
Proceedings of the 35th annual ACM SIGUCCS fall conference
Growing an infrastructure: the role of gateway organizations in cultivating new communities of users
Proceedings of the 2007 international ACM conference on Supporting group work
Proceedings of the 38th annual ACM SIGUCCS fall conference: navigation and discovery
Data Mining User Activity in Free and Open Source Software FOSS/ Open Learning Management Systems
International Journal of Open Source Software and Processes
| Hi-index | 0.00 |
Established best practices in software development tend to assume that a product's intended stakeholders (i.e., users, customers, and clients) are fairly well known and generally accessible. This paper outlines specific issues faced by those who conduct requirements analysis in the context of open source projects in which the user communities are widely distributed. The examples described are drawn from the experience of managing tool development within the Sakai Project [1], a higher education effort to build and share a community source framework for supporting on-line collaboration in academic courses and projects. With a far-flung community of users and developers, this project requires new approaches to eliciting, analyzing, and prioritizing user needs. The issues outlined in this paper are currently being met by a preliminary set of solutions that makes use of web-based project management technologies. These technologies along with some planning and communication strategies help improve the decision-making process involved in deciding whether and how to choose among proposed constraints, use cases, and feature requests.