Elements of Structure in Articles on Information Technology

The organization and presentation of information is reasonably formulaic in academic writing, and each discipline has its method for arranging a coherent document, as well as reasons for designing conformity. Information technology articles present both research and a recommendation, which is part of a conversation between the writer and the reader. The writer's relationship with the speaker will determine the level of specialized language, the complexity of information systems, and the formality of language. These variables work into a larger structure that is quite standard in information technology and science article writings. After the title and author note, which directs the reader initially in the subject material, an abstract is presented, summarizing the main ideas of the article and suggesting the recommendation which will later be filled out by supporting examples from references within the body of the article. The information is all organized under appropriate headings and subheadings to better orient the reader and prepare them for the main themes that are to be discussed. Developing a paper logically assists the reader's ability to understand, which is why a coherent, homogenous structure is important in relaying information clearly and quickly.

The aim of most academic articles, and especially in the field of information technology, is to offer an opinion supported by research, which the author hopes the reader will find agreement with and will value its contribution to the field. Siani Pearson's Taking Account of Privacy when Designing Cloud Services (2009), is an excellent example for analyzing the success of an article's basic structure, adeptness at presenting information clearly and succinctly while demonstrating appropriate language use for the intended reader and providing a recommendation that follows from the research. This article also contains areas for critique, which will enhance the current discussion on the importance and proper use of the academic article structure.

Taking Account of Privacy when Designing Cloud Computing Services carefully inserts the main discussion topic, identifies the problem area (privacy), and locates it (cloud computing services), and details the process (design). The abstract then develops the title further by stating the problem and hinting at solutions that will be offered in design principles ( p. 1). Within the abstract is the essence of the writer/reader relationship. The level of discussion already insinuates a level of technological savviness, and the argument that follows is consistent in this. The introduction follows with a topic sentence that relates to the abstract, forming a clear picture of the topic under discussion very quickly. The fourth sentence presents the importance and relevance of the paper, validating the project. In this article, the author states that neglecting to consider privacy issues at the level of the initial design, could prove fatal to the cloud service itself. This point is reiterated in the introduction and then evaluated based on a brief example from research. This establishes right away the approach the author will take (case studies and evaluations), and demonstrates the ability to suggest relevant solutions, as evinced in the final paragraph of the introduction.

If the abstract serves as a microcosm for the article, the introduction opens one step further, offering background information on the field of study, describing, in this case, by example, the methodology used, and drawing conclusions from presented data. The author does this mostly by using complex sentences that link together an idea, and an explanation of that idea in the context of the topic. Conjunctive verbs are used frequently to not only guide the reader toward a particular state of mind (i.e. in perceiving a conclusion or a furthering of an idea, as in the use of “hence,” or “however”), but also simplifies the linguistic structure by signaling transitional moments. Emphasis is given to Pearson's evaluation or explanation using these conjunctive verbs.

Similarly, subheadings designate emphasis and act as a guiding principle for the reader and situates the argument in smaller topics, highlighting an area of discussion. For example, in asking “What is Privacy?” in the subheading, the reader knows they will read an answer, and Pearson delivers a definition that is consistent with the recommendation she will later offer. Just for a moment, in this section, the academic neutrality is somewhat broken, as Pearson's definition demands an acknowledgment of the “fundamental human right” that is privacy. She then sub-defines privacy, allowing for different forms, as in “the right to be left alone,” and “control of information about ourselves” (p. 1). This appeal to emotion positions computing privacy at the level of privacy denoted by the United Nations Universal Declaration of Human Rights and the European Convention on Human Rights. Though the paper largely relies on empirical data, this moment is unique in exposing Pearson's “pitch.”

The following discussion exhibits the philosophy of integrated design and shows how it will impact the reader. In this sense, the article speaks both to those with specialized cloud technology knowledge and to the public at large, whose safety is the concern of the article. In the opening sections of the data surveys and case studies, the language formality is toned down, and Pearson repeatedly defines terms. Later in the article, the technological language will amp up, and definitions will become sparser, suggesting that the main aim of the paper is to speak to those who can use the knowledge in expanding the field of information technology and computer privacy.

Each paragraph introduces a topic, followed by an expansion of the introduction. Pearson carefully outlines the risks for both public consumers and businesses, succinctly and briefly covering intended topics. The flow of the paper works to promote the urgency and necessity of the problem. Negative adjectives and adverbs fill the paper, especially in the opening pages (p. 2-3). This repetition drives home the intent and gives emphasis to the problem addressed. For a paper whose recommendation section is the main contributing factor to the field, this rhetorical method is targeted at bringing around an emotional response embedded in the display of empirical data and logically drawn conclusions. Other forms of supporting credibility are made possible by using only the most current sources, which, in the field of information technology, is increasingly important due to rapidly evolving issues and practices.

In describing new ideas, Pearson, who was so thorough at creating definitions at the start of the article, loses the layperson to increased usage of technical jargon, and to descriptions of ideas and design principles that are not clear or illustrative of how they work, limiting general understanding. However, because of the paper's consistent construction, it is possible to reach conclusions based upon the less technical elements, as in the subheadings and conclusion. The subheadings reach a point of clear explanation in the surrounding context of the paper. In issuing design strategies to maximize user protection, Pearson's subheadings quickly detail the necessary steps. They read, for example: “Protect personal information in the cloud:,” “Maximize user control:,” “Allow user choice:” (p. 48). Simple, declarative constructs whereby the details to follow will address the subheadings make it easy for a reader to follow without needing to get into the technically expanded detail.

The overall article has a smooth flow, transitions from each topic clearly and logically, and addresses all new information presented, even if it is sometimes hazily defined. Pearson's conclusion is relatively simple, she stresses the importance of designing privacy into cloud computing at the outset, and her examples and scenarios clearly show why this is important. The conclusion essentially backs up the body of the paper and ropes the control back into the hands of the author who has pulled references in and out of the conversation. It marks a return to the formal structure of the article and promotes the sense of a well-articulated argument.

Reference

Pearson, Siani. (2009). Taking account of privacy when designing cloud computing. In Software Engineering Challenges of Cloud Computing (pp. 44-52). Washington D.C.: IEEE Computer Society.