Abstract
Interactive systems development is a complex process, because many requirements must be considered. Traditionally, functional requirements capture the intended behavior of the system which may be expressed as tasks or functions the system is required to perform. On the other hand, non-functional requirements are concerned with how the application provides the required functionality rather than defining what the application does. Both kinds of requirements are equally important for the final product, but designers try to achieve them by using different mechanisms. This paper introduces ATRIUM, a methodology for developing interactive systems where functional and not functional requirements are considered in a unified and systematically manner by using documented experience in different level of abstraction: interaction, design and architecture. This methodology is standard compliance as the ISO/IEC 25010 is one of the inputs for the process.
Users
Please
log in to take part in the discussion (add own reviews or comments).