Sciweavers

1253 search results - page 16 / 251
» A Case Study of Requirements Elicitation Process with Change...
Sort
View
AINA
2008
IEEE
13 years 9 months ago
A Case Study on Software Evolution towards Service-Oriented Architecture
The evolution of any software product over its lifetime is unavoidable, caused both by bugs to be fixed and by new requirements appearing in the later stages of the product's...
Félix Cuadrado, Boni García, Juan C....
ICSEA
2008
IEEE
14 years 1 months ago
Analyzing Software Evolvability of an Industrial Automation Control System: A Case Study
Evolution of software systems is characterized by inevitable changes of software and increasing software complexity, which in turn may lead to huge maintenance and development cos...
Hongyu Pei Breivold, Ivica Crnkovic, Rikard Land, ...
VL
2008
IEEE
138views Visual Languages» more  VL 2008»
14 years 1 months ago
A case study of API redesign for improved usability
As software grows more complex, software developers’ productivity is increasingly defined by their ability to effectively reuse code. Even APIs (application programming interfac...
Jeffrey Stylos, Benjamin Graf, Daniela K. Busse, C...
RE
2007
Springer
14 years 1 months ago
Specifying Monitoring and Switching Problems in Context
Context-aware applications monitor changes in their operating environment and switch their behaviour to keep satisfying their requirements. Therefore, they must be equipped with th...
Mohammed Salifu, Yijun Yu, Bashar Nuseibeh
RE
1995
Springer
13 years 11 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