Sciweavers

184 search results - page 2 / 37
» Software Requirements Negotiation: Some Lessons Learned
Sort
View
HICSS
2008
IEEE
235views Biometrics» more  HICSS 2008»
13 years 11 months ago
WikiWinWin: A Wiki Based System for Collaborative Requirements Negotiation
Defining requirements is one of the most critical activities in the development of software intensive systems. The EasyWinWin system has been very good in capturing initial requir...
Da Yang, Di Wu, Supannika Koolmanojwong, A. Winsor...
SOFSEM
2010
Springer
14 years 2 months ago
Lessons in Software Evolution Learned by Listening to Smalltalk
The biggest challenge facing software developers today is how to gracefully evolve complex software systems in the face of changing requirements. We clearly need software systems t...
Oscar Nierstrasz, Tudor Gîrba
RE
2010
Springer
13 years 6 hour ago
Domain Engineering with Event-B: Some Lessons We Learned
Domain modeling is an important aspect of software engineering. This paper presents our experience of modeling land transportation domain in the formal framework of Event-B. The do...
Atif Mashkoor, Jean-Pierre Jacquot
RE
2002
Springer
13 years 4 months ago
Requirements Engineering in the Health Care Domain
There are many different approaches to elicit requirements each having its strengths and weaknesses. Hence, some approaches may be ore suitable to one domain then another. Moreove...
Luiz Marcio Cysneiros
RE
2007
Springer
13 years 11 months ago
Value-Based Requirements Traceability: Lessons Learned
Abstract. Traceability from requirements to code is mandated by numerous software development standards. These standards, however, are not explicit about the appropriate level of q...
Alexander Egyed, Paul Grünbacher, Matthias He...