Over the past few years the real importance of requirements engineering has surfaced; hence, much research is now being directed towards generating quality requirements. However, the existing requirements generation models do not sufficiently stress the importance of identifying intermediate requirements documents. In addition, the models rarely specify how those documents support the objectives of the related activities. Moreover, the current models fail to depict how requirements are transformed, in terms of content and format, as we transition through the requirements engineering process. To address these concerns, we propose a comprehensive requirements generation model consisting of two main parts - (1) a refined set of activities (of the model) with explicitly enunciated objectives, and (2) a detailed characterization of requirements documents generated throughout the requirements engineering process. The proposed model refines the Requirements Generations Model (RGM) into detailed activities to reflect an appropriate level of abstraction, so that we can more accurately represent the intermediate development of the requirements documents. Furthermore, the objectives of the activities are identified, and subsequently, synchronized with the content and format of the documents produced by each activity. The evolution of the requirements is described, in terms of content and format, as the requirements documents pass through the successive activities of the requirements engineering process. / Master of Science

Made available in DSpace on 2014-06-12T15:52:27Z (GMT). No. of bitstreams: 2 arquivo3299_1.pdf: 8413271 bytes, checksum: f7e2f7602fa26d4744d748c1d3ff2002 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2009 / Conselho Nacional de Desenvolvimento Científico e Tecnológico / Documentos de requisitos tendem a ser inundados por requisitos tais como: descrições sem semântica, desnecessariamente longas e confusas, informações duplicadas, entre outros problemas. Estes problemas sintáticos diminuem a facilidade de entendimento de todo o documento de requisitos e podem prejudicar outras fases do processo de desenvolvimento do software. Avaliações de qualidade não ajudam muito se somente são baseadas em listas com qualidades desejadas. Elas devem também incorporar diretrizes para auxiliar na avaliação e melhoria dos documentos de requisitos. O processo AIRDoc surge como uma solução para avaliar e melhorar documentos de requisitos que foram descritos usando casos de uso. O processo proposto é baseado na definição de objetivos e questões que devem ser avaliadas por métricas. A qualidade dos modelos de casos de uso é melhorada com a utilização de refatorações