At the beginning of my (still small) IT career, there was that time when I was in college. There, I learned several things with several professors, and one of those things I learned – and I liked quite a bit – was to make scientific articles in SBC¹ standards.
Since the first article elaborated I already felt a certain pleasure in doing them, because they helped me in some points:
Improvement in research – Because it is a scientific article, there would be a check of references. With this, a source of information could not be used that was not another article, publication or academic work. This helps to filter your sources of information well, with grater reliability in the subject you are looking for.
Coherence – Unfortunately one of the things I have always had difficulty with in academic work (ABNT² standards) is to maintain the structural coherence of the document. The document became great that at the time of elaborating the introduction and the conclusion, it ended up that the two things became equal. With scientific articles, it is clearer how to start the document and the own body becomes the conclusion of it.
Straight to the point – In an academic document it often takes a series of chapters that end up leaving the material more massive, extensive and tiring to read. Already in the article scientific purpose is addressed more directly and easily (even with all technical terms), thus making it easier to review by the author or others.
Below I am posting on the blog the first scientific article I wrote. It was an activity of the subject of Software Engineering, which I had in college. As my first, it is very simple and deals with the subject of Software Project Management. I focused on the life stages of the project, as well as on one’s knowledge fields.(more…)