Abstract
Scenarios has become a popular technique for requirements elicitation and specification building. Since scenarios capture only partial descriptions of the system behavior, an approach for scenario composition and/or integration is needed to produce more complete specifications. The Unified Modeling Language (UML), which has become a standard notation for object-oriented modeling, provides a suitable framework for scenario acquisition using Use Case diagrams and Sequence or Collaboration diagrams. In this paper, we suggest an algorithmic and tool support for composing and integrating scenarios that are represented in form of sequence diagrams. We suggest four operators (;: sequential operator, ||: concurrent operator, ?: conditional operator and * :iteration operator) to compose a set of scenarios that describe a use case of a given system. In this paper, we suggest also to apply the scenario approach to B2B systems (Business to Business). We propose to develop B2B systems as a three activities process deriving formal specifications and code skeletons from UML scenarios. Activities of this proposed process are generally automatic and are supported by a set of developed algorithms and tools.
Highlights
Over the past years, scenarios have received significant attention and have been used for different purposes such as understanding requirements, human computer interaction analysis, specification generation, and object-oriented analysis and design
A use case diagram is more concerned with the interaction between the system and actors
We have considered that the scenario sd1 is represented by one abstract message m sent by the first object of the scenario to itself and all concrete messages will be viewed as are refinement of this message m
Summary
Scenarios have received significant attention and have been used for different purposes such as understanding requirements, human computer interaction analysis, specification generation, and object-oriented analysis and design. They have been identified as a promising technique for requirements engineering. The lifecycle view considers scenarios as artefacts existing and evolving in time through the execution of operations during the requirements engineering process. The UML is an expressive language that can be used for problem conceptualization, software system specification as well as implementation It covers a wide range of issues from use cases and scenarios to state behaviour and operation declarations.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
