Description
Software engineers and human computer interaction engineers have come to the understanding that usability is not something that can be “added” to a software product during late stage, since to a certain extent it is determined and restricted by architecture design. Cost effectively developing a usable system must include developing an architecture, which supports usability. Because software engineers in industry lacked support for the early evaluation of usability, we defined a generalized four-step method for software architecture level usability analysis called SALUTA. In this article, we report on a number of experiences and problems we observed when performing architecture analysis of usability at three industrial case studies performed in the domain of Web-based enterprise systems. Suggestions or solutions are provided for solving or avoiding these problems so organizations facing similar problems may learn from our experiences.