Share This Author
A Diagrammatic Tool for Representing User Interaction in UML
This paper presents a diagrammatic tool to represent the users/system interaction called User Interaction Diagram (UID), and shows how UIDs can be incorporated into the requirements and analysis workflows of the Unified Process for software development.
Modeling Interactions and Navigation in Web Applications
This paper presents a method that bridges the gap between requirements elicitation and conceptual, interaction and navigation design for Web applications. This method is based on user scenarios, use…
Improving the Web Application Design Process with UIDs
- Patrícia Vilain
- Computer Science
In this paper, we present a diagrammatic technique to represent the information exchange during the interaction between the user and the application called User Interaction Diagram (UID). UIDs have…
Software Estimation Based on Use Case Size
- Gustavo Bestetti Ibarra, Patrícia Vilain
- Computer ScienceBrazilian Symposium on Software Engineering
- 27 September 2010
This paper proposes a new method for estimating software based on the size of each use case that was utilized in the Labor Court of Santa Catarina - Brazil to provide support to the negotiation process with third party companies that outsource software development.
Reactive Variability Realization with Test Driven Development and Refactoring
This paper investigates the use of test-driven development (TDD) and refactoring techniques for performing reactive variability in APLE and chooses the configuration file that allows achieving more than one platform, an important problem in mobile application development.
SolUnit: a framework for reducing execution time of smart contract unit tests
Selecting Agile Practices for Developing Software Product Lines (S)
Creating User Scenarios through User Interaction Diagrams by Non-Technical Customers
This paper investigates the applicability of User Interaction Diagrams (UIDs) as user scenarios for specifying requirements of software built by non-technical customers and demonstrates that the regressive method requires significantly less effort as compared to the progressive method.
Automated Acceptance Tests as Software Requirements: An Experiment to Compare the Applicability of Fit Tables and Gherkin Language
The results show that there is no sufficient evidence to affirm that one technique is easier to specify test scenarios or better to communicate software requirements, and two acceptance testing techniques (Fit tables and Gherkin language) as software requirements specification.
Fixture Setup through Object Notation for Implicit Test Fixtures
- D. Longo, B. Wilges, Patrícia Vilain, Renato Cislaghi
- Computer ScienceJ. Comput. Sci.
- 16 September 2015
This work is to enable the reuse of fixtures across multiple test classes avoiding the management and the creation of fixtures within the test itself, with significant test code volume reduction.