Behavioral properties discovery of the systems is a difficult task since it has two important dimensions to address namely- static and dynamic. The Static behavior in UML is addressed by Use Cases. It can be noted that the Use Cases are efficient and effective in addressing the functional requirements only. It does not address the non-functional requirements or the abilities of the system. The other significant point about the Use Cases is that their derivation is based on the structure of the functional requirements meaning that if structure exists for functional requirements then the structuring capabilities can be effectively mapped to Use Cases. Based on Use Cases the Product Development Life Cycle can continue till a diagnosis report of Use Case realization is received in terms of correct Test Cases. It should be noted that the use Cases are capable of addressing Static behavior only. The claim is made due to the reason that the dynamic behavior happens due to message-orientation, event-orientation or action-orientation. Other related analysis diagrams such as State, Sequence and Activity diagrams address the dynamic aspects. This paper focuses on important issues that are required to be observed while addressing the behavioral properties of the system under construction. It also indicates the dependencies and interaction between Use Cases that are legitimate and beyond the scope of traditional Use Case relationships.
[1]
Klaus Pohl,et al.
Communicating the variability of a software-product family to customers
,
2004,
Informatik Forschung und Entwicklung.
[2]
Jan Bosch,et al.
Variability Issues in Software Product Lines
,
2001,
PFE.
[3]
Ivar Jacobson,et al.
Object-oriented software engineering - a use case driven approach
,
1993,
TOOLS.
[4]
Alistair Cockburn,et al.
Writing Effective Use Cases
,
2000
.
[5]
Paul Clements,et al.
Software product lines - practices and patterns
,
2001,
SEI series in software engineering.