Sciweavers

184 search results - page 1 / 37
» Software Requirements Negotiation: Some Lessons Learned
Sort
View
ICSE
1998
IEEE-ACM
13 years 9 months ago
Software Requirements Negotiation: Some Lessons Learned
Negotiating requirements is one of the first steps in any software system life cycle, but its results have probably the most significant impact on the system's value. However...
Barry W. Boehm, Alexander Egyed
RE
2004
Springer
13 years 10 months ago
Goal-Oriented Requirements Enginering: A Roundtrip from Research to Practice
The software industry is more than ever facing the challenge of delivering WYGIWYW software (What You Get Is What You Want). A well-structured document specifying adequate, comple...
Axel van Lamsweerde
FLAIRS
2001
13 years 6 months ago
On the Technological, Human, and Managerial Issues in Sharing Organizational Lessons
Lessons learned systems (LLS) are systems that support a lessons learned process (LLP) to collect, verify, store, disseminate, and reuse organizational lessons. In this paper we e...
Rosina Weber, Len Breslow, Nabil Sandhu
ESEM
2008
ACM
13 years 6 months ago
Some lessons learned in conducting software engineering surveys in china
Component-Based Software Engineering (CBSE) with Open Source Software and Commercial-Off-the-Shelf (COTS) components, Open Source Software (OSS) based development, and Software Ou...
Junzhong Ji, Jingyue Li, Reidar Conradi, Chunnian ...
ICSE
1994
IEEE-ACM
13 years 8 months ago
Lessons from Using Basic LOTOS
We describe three case studies in the use of Basic LOTOS. The studies cover design recovery, requirements speci cation, and design activities. We also report lessons learned from ...
Mark A. Ardis