Lubomir,
Just a pointer that might interest you regarding writing a brief.
Henrik Artman (at NADA, KTH Royal Institute of Technology in Stockholm) and
Stefan Holmlid (at IDA, Linköping University) are working on a research
project about procurer competence within the area of information systems
(IS) design. Within IS-design the development of design objectives is
usually on the developer's side of the work. Given the structure of the
computer business this may not be ideal, and in the end lead to products
that do not contribute to business goals and has poor quality in use.
I'm sure Stefan (who is a member of the list) can provide more information
if someone is interested.
Here is a reference:
Artman , H. (2002) Procurer Usability Requirements: Negotiations in contract
development. Proceedings of NORDICHI 02. pp 61-70.
http://doi.acm.org/10.1145/572020.572029
Cheers,
// Mattias
--
Mattias Arvola, M.A., Fil. Lic., PhD Student
http://www.ida.liu.se/~matar
Dept. of Computer and Information Science
Linköpings universitet, Sweden
"Lubomir S. Popov" <[log in to unmask]>:
>
> Generally, there is very little awareness about the importance, role, and
> genesis of the design brief/program. This is actually the phase of problem
> formulation. When you take the wrong problem, no matter how good designer you
> are, you will provide the wrong (not adequate I mean) solution. Actually, the
> better designer you are and the better you respond to this (wrong) problem,
> the more inadequate the solution will be.
|