Loading...
Please wait, while we are loading the content...
Similar Documents
From Sequence Diagrams to Behaviour Models (2001)
| Content Provider | CiteSeerX |
|---|---|
| Author | Kramer, Jeff Uchitel, Sebastian Magee, Jeff |
| Abstract | INTRODUCTION Sequence Diagrams The software engineering community has long understood the importance of requirements elicitation. Stakeholder involvement in the elicitation process and tools to help build a common ground between stakeholders and developers is essential in order to obtain a good requirements definition. Scenarios have become increasingly popular as a means of articulating stakeholder requirements. Scenarios describe how system components (in the broadest sense) and users interact in order to provide system level functionality. Each scenario is a partial story which, when combined with all other scenarios, should conform to provide a complete system description. Thus stakeholders may develop descriptions independently, contributing their own view of the system to those of other stakeholders. The Unified Modelling Language has a notation for scenarios called Sequence Diagrams [1]. These diagrams, together with their counterpart from the telecomm |
| File Format | |
| Publisher Date | 2001-01-01 |
| Access Restriction | Open |
| Subject Keyword | Stakeholder Requirement System Level Functionality Behaviour Model System Component Stakeholder Involvement Complete System Description Software Engineering Community Common Ground Requirement Elicitation Sequence Diagram Good Requirement Definition Introduction Sequence Diagram Thus Stakeholder Unified Modelling Language Partial Story Elicitation Process |
| Content Type | Text |
