Sciweavers

3216 search results - page 220 / 644
» The Oregon Software Development Process
Sort
View
ECIS
2003
15 years 7 months ago
E-negotiations: towards engineering of technology-based social processes
Traditionally, negotiation support was based on normative and prescriptive research; its users were analysts and experts. The purpose of the recently developed e-negotiation syste...
Gregory E. Kersten
WSC
1997
15 years 7 months ago
Automating the Metamodeling Process
Model abstraction using metamodeling has demonstrated the capability to facilitate software reuse, large scale model integration, verification, and validation. Once restricted to...
Don Caughlin
ICSE
2000
IEEE-ACM
15 years 10 months ago
Software engineering and performance: a road-map
Software engineering has traditionally focussed on functional requirements and how to build software that has few bugs and can be easily maintained. Most design approaches include...
Rob Pooley
RE
1995
Springer
15 years 10 months ago
Using non-functional requirements to systematically support change
Non-Functional requirements (or quality requirements, NFRs) such as confidentiality, performance and timeliness are often crucial to a software system. Our NFRFramework treats NF...
Lawrence Chung, Brian A. Nixon, Eric S. K. Yu
CSCW
2011
ACM
15 years 1 months ago
"Not my bug!" and other reasons for software bug report reassignments
Bug reporting/fixing is an important social part of the software development process. The bug-fixing process inherently has strong inter-personal dynamics at play, especially in h...
Philip J. Guo, Thomas Zimmermann, Nachiappan Nagap...