1. Richard Lipka Department of Computer Science and Engineering Faculty of Applied Sciences University of West Bohemia, Pilsen, Czech Republic 1

2. > File Manager – case study > ReproTool and its ouptuts > Scenarios 2

3. > Case study of component- based application > Java, OSGi, Spring DM 3

4. > Method calls > File manipulation > Opening windows > Events > Window control > Finished task 4

5. > Comparison of performance > Java-based FTP client > Own implementation of FTP > Marek Paška > Formal checking of FSM 5

6. > Tool for creating and tagging usecases > Outputs should be used as a basis for automated scenarion creating > Still not finished – version available in the repository cannot be run 6

7. > Description in natural language 7 UseCase: Listing of directory Primary Actor: User Main success scenario specification 1. User select a directory from an available list and confirm his selection 2. System obtains representation of directory 3. Systems notifies the GUI that directory representation is available 4. GUI updates window with new content of directory Extensions: 1a. There is no available list of directories (there is unvalid default directory in the configuration) 1a1. System selects user's root directory. 1a2. Execution continues from point 2 with root directory 2a. Selected directory is not available at the moment 2a1. Warning for user is displayed 2a2. System tries to update list of files in current directory - continues from point 2 with current directory 2a2a. Current directory is not available 2a2a1. System continues from point 1a1

8. 8 <textNodes content="User selects a directory from an available list and confirms his selection "lemmaForm="User select directory from available list and confirm selection" posTag=""/> <textNodes content="System selects user's root directory"/> <action xsi:type="action:Internal" actionName="…steps.0/@textNodes.0"/> <textNodes content="There is no available list of directories (there is unvalid default directory in the configuration)"/> …

9. 9 <allTransitions xsi:type="lts:ActionTransition" source="//@allStates.0" target="//@allStates.2"> <sentence xsi:type="usecase:UseCaseStep" href="uc1.usecase#//@mainScenario/@steps.0"/> <allTransitions xsi:type="lts:ActionTransition“ source="//@allStates.2" target="//@allStates.3"> <sentence xsi:type="usecase:UseCaseStep" href="uc1.usecase#//@mainScenario/@steps.0/@extensions.0/@steps.0"/> <allTransitions xsi:type="lts:ActionTransition" source="//@allStates.2" target="//@allStates.4"> <sentence xsi:type="usecase:UseCaseStep" href="uc1.usecase#//@mainScenario/@steps.1"/> …

10. 10

11. > Scenario should cover all branches described in lts > Problem with identification of actors > Depends on description of usecases and Reprotool – Reprotool contains dictionary of actors > Problem with identification of actions > Desription of usecases is usually not exact enough > Instead of using natural language denote methods and interfaces? 11

12. > Description in XML > Initial state of the simulation > Description of random numbers generators > Simulated events > Name of invoked method > List of parameters 12

13. Questions? 13