Object-oriented software engineering
Object-oriented software engineering
The unified software development process
The unified software development process
Refactoring: improving the design of existing code
Refactoring: improving the design of existing code
Web Modeling Language (WebML): a modeling language for designing Web sites
Proceedings of the 9th international World Wide Web conference on Computer networks : the international journal of computer and telecommunications netowrking
Extreme Programming Installed
Test Driven Development: By Example
Test Driven Development: By Example
The Top Risks of Requirements Engineering
IEEE Software
Introducing XP into Greenfield Projects: Lessons Learned
IEEE Software
Assessing test-driven development at IBM
Proceedings of the 25th International Conference on Software Engineering
Usability Requirements in a Tender Process
OZCHI '98 Proceedings of the Australasian Conference on Computer Human Interaction
Towards Modeling and Reasoning Support for Early-Phase Requirements Engineering
RE '97 Proceedings of the 3rd IEEE International Symposium on Requirements Engineering
Linking usability to software architecture patterns through general scenarios
Journal of Systems and Software - Special issue on: Software architecture - Engineering quality attributes
Bringing Usability to the Early Stages of Software Development
RE '03 Proceedings of the 11th IEEE International Conference on Requirements Engineering
OO-H Method: extending UML to model web interfaces
Information modeling for internet applications
Test-Driven Modeling for Model-Driven Development
IEEE Software
Automatic generation of high coverage usability tests
CHI '05 Extended Abstracts on Human Factors in Computing Systems
Model-driven development: the good, the bad, and the ugly
IBM Systems Journal - Model-driven software development
A Systematic Approach to Generate Inputs to Test UML Design Models
ISSRE '06 Proceedings of the 17th International Symposium on Software Reliability Engineering
Designing Interfaces
Model-Driven Architecture in Practice: A Software Production Environment Based on Conceptual Modeling
Guidelines for Eliciting Usability Functionalities
IEEE Transactions on Software Engineering
Enhancing Test Driven Development with Model Based Testing and Performance Analysis
TAIC-PART '08 Proceedings of the Testing: Academic & Industrial Conference - Practice and Research Techniques
Dealing with Usability in Model Transformation Technologies
ER '08 Proceedings of the 27th International Conference on Conceptual Modeling
Bridging Test and Model-Driven Approaches in Web Engineering
ICWE '9 Proceedings of the 9th International Conference on Web Engineering
An empirical evaluation of the i* framework in a model-based software generation environment
CAiSE'06 Proceedings of the 18th international conference on Advanced Information Systems Engineering
Architecting for usability: a survey
Journal of Systems and Software
Using spring Roo for the test-driven development of Web applications
Proceedings of the 27th Annual ACM Symposium on Applied Computing
Proceedings of the 11th Brazilian Symposium on Human Factors in Computing Systems
Hi-index | 0.00 |
The success of Web applications is constrained by two key features: fast evolution and usability. Current Web engineering approaches follow a "unified" development style which tends to be unsuitable for applications that need to evolve fast. Moreover, according to the quality standard ISO 9126-1, usability is a key factor to obtain quality systems. In this paper, we show how to address usability requirements in a test-driven and model-based Web engineering approach. More specifically, we focus on usability requirements with functional implications, which do not only concern the visual appearance, but also the architecture design. Usability requirements are contemplated from the very beginning of each cycle, by creating a set of meaningful tests that drive the development of the application and ensure that no functionality related to usability is altered unintentionally through development cycles. Dealing with those usability requirements in the very early steps of the software development process avoids future hard changes in the system architecture to support them. The approach is illustrated with an example in the context of the OOWS suite.