| Program |
 |
|
|
|
| Find in Program |
|
|
|
|
| Page |
|
|
|
|
| Basket |
|
|
view, help
"Comparison of UML and Text Based Requirements Engineering"
|
|
|
|
Comparison of UML and Text Based Requirements Engineering
Meeting Rooms 11-12
Tuesday, 11:30, 30 minutes | 7 | · | 8 | · | 9 | · | 10 | · | 11 | · | 12 | · | 13 | · | 14 | · | 15 | · | 16 | · | 17 | · | 18 | · | 19 | · | 20 | · | 21 |
Brian Berenbach, Siemens Corporate Research, Inc.
There appears to be a real dichotomy in the use of UML vs. text based Use Case development for requirements elicitation and documentation, that is, on those projects where use cases were work products. Not only are there different processes in place for text and graphical use case modeling, but also there are a variety of approaches and philosophies in each camp. This paper will discuss the prose vs. graphical approaches to requirements elicitation, observed advantages and disadvantages of each, and suggest best practices for improving and/or creating effective processes for requirements elicitation.
|
