leonardo-minora
commented
6 years ago contexto e justificativa pode ser montada com os seguintes documentos Google drive
- ./referências/publicações_EVG/Artigo_CLAD_EscolaVirtualGov.pdf : entender o que é escola virtual enap
- ./proposta inicial/Plano_de_trabalho_v1 : ver seção de justificativa e diminuir/ajustar para contexto, problema e justificativa do TCC
escrever o resumo (contexto, problema, justificativa, solução/objetivos) e os objetivos do tcc
resumo estruturado, consultar
Abstract
A concise and factual abstract is required of no more than 300 words, including headings. To support this, the journal has started using (July 1, 2009) "structured abstracts". A structured abstract should contain the following headings (as in-line or run-in headings in bold): Context, Objective, Method, Results and Conclusions. An abstract is often presented separately from the article, so it must be able to stand alone. For this reason, references should be avoided, but if essential, then cite the author(s) and year(s). Also, non-standard or uncommon abbreviations should be avoided, but if essential they must be defined at their first mention in the abstract itself. Please see below for an example of a structured abstract:
Context: Throughout an organisation, people have different responsibilities and worktasks, hence, it is probable that different roles have different priorities when it comes to what should be improved within a company. This has been found in previous studies in marketing, but is this true for software improvement as well?
Objective: This paper evaluates how different roles in a software development organization view different issues in software process improvement and if such differences could be used in order to provide more tailor-made process improvements within an organization and uses this as a working hypothesis.
Method: A quantitative questionnaire containing five different weighted questions related to software process improvement was developed. 84 employees from all levels of a Swedish telecommunication company were then approached, of which 63 responded.
Results (standby): The different roles disagreed in three of the questions while they agreed in two of the questions. The disagreement was related to issues about importance of improvement, urgency of problems, and threat against successful process management, while the questions where the roles agreed focused on communication of the processes (documentation and teaching).
Conclusion (standby): It is concluded that it is important to be aware and take into account the different needs of different roles. This will make it possible to provide improvements tailored to specific roles which will probably help to overcome resistance to process improvements. It is also important to look into other areas and companies (for example, marketing) where it could be beneficial when conducting process improvements.