TÉCNICO VS. USUÁRIO: UMA ANÁLISE DO PROCESSO COMUNICACIONAL NA ENGENHARIA DE REQUISITOS DE SOFTWARE
AUTOR(ES)
Carlos Eduardo Marquioni
DATA DE PUBLICAÇÃO
2008
RESUMO
This research analyzes a practical and a communicational problem associated to software development which takes place before the program begins to be created: the software industry professionals say that the user does not know what he wants, due to frequent change requests associated to the software requirements that originate volatile requirements. This work considers requirements as the functionalities offered by the software; the user is the source of requirements, not only a product end user; and a volatile requirement changes constantly. The analysis is based on the premise that automation requires integrated knowledge to happen: a hypothesis concerning this volatility is related to the users fragmented knowledge of the business process. It can generate unsatisfactory software products, and eventually affect a large part of world populations daily. The first part of this work presents the Requirements Engineering process (Kotonya, Sommerville), that drives the research. The second part proposes some probable original historical reasons to knowledge fragmentation (Smith, Babbage, Taylor, Fayol, Marx, Engels, Adorno, Horkheimer, Marcuse). The third part presents software notations used by technical professionals for diagrams creation (Gane, Yourdon, Jacobson, Booch, Rumbaugh), since 1970s until the 2000s. The last part of this work does a semiotic analysis of these notations (Peirce) in order to show that the repertory required to read them may be an obstacle for the communication process between software professionals and users at the time of defining the requirements. An analytical reflection is proposed which is based on the simultaneous use of technical notation and interface design (Nadin, Galitz, Stone, Jarrett, Woodroffe, Minocha), as a way to minimize these communication problems.
ASSUNTO(S)
design de interface communication interface design semiótica software semiotic comunicacao comunicação comunicação e linguagens software
ACESSO AO ARTIGO
http://tede.utp.br/tde_busca/arquivo.php?codArquivo=212Documentos Relacionados
- Uma ontologia para engenharia de requisitos de software
- Uma ontologia para engenharia de requisitos de software
- Interface de usuário: uma avaliação do projetista.
- Um processo ágil de engenharia de requisitos com apoio de padrões de software
- Um modelo de processo de engenharia de requisitos para ambientes de desenvolvimento distribuído de software