Tool support for systematic class identification in object-oriented software architectures

2002 ◽  
Author(s):  
K.S. Barber ◽  
T.J. Graser
Keyword(s):  
Object Oriented ◽  
Tool Support ◽  
Software Architectures ◽  
Class Identification

Measuring stability of object‐oriented software architectures

IET Software ◽  
2015 ◽  
Vol 9 (3) ◽  
pp. 76-82 ◽  
Author(s):  
Shouki A. Ebad ◽  
Moataz Aly Ahmed
Keyword(s):  
Object Oriented ◽  
Software Architectures

A case-based reasoning approach to derive object-oriented models from software architectures

2010 ◽  
Vol 27 (4) ◽  
pp. 267-290 ◽  
Author(s):  
German L. Vazquez ◽  
J. Andres Díaz-Pace ◽  
Marcelo R. Campo
Keyword(s):  
Object Oriented ◽  
Software Architectures ◽  
Case Based Reasoning ◽  
Case Based

scholarly journals USING UML SCENARIOS IN B2B SYSTEMS

2010 ◽  
Vol 11 (1) ◽  
pp. 1-13 ◽  
Author(s):  
A. Jakimi ◽  
A. Sabraoui ◽  
E. Badidi ◽  
A. Salah ◽  
M. El Koutbi
Keyword(s):  
Unified Modeling Language ◽  
Object Oriented ◽  
Tool Support ◽  
Use Case ◽  
Formal Specifications ◽  
Sequence Diagrams ◽  
Unified Modeling ◽  
Suitable Framework ◽  
Business To Business ◽  
Scenario Approach

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.

Sign in / Sign up

Export Citation Format

Share Document