- •The structure of a research paper.
- •Remember: the title should consist of 6-10 words, the relevant key words included.
- •Abstract
- •1 Introduction
- •1. Introduction
- •1. Introduction
- •1. Introduction
- •1. Introduction
- •1,2 Computer Sc. & Engineering
- •3Department of Information Technology
- •The Structure of the Main Body of the Paper.
- •The structure of the Conclusions
- •6. Conclusions
- •8. Conclusions
- •Acknowledgements
- •Appendix Grammar References
The Structure of the Main Body of the Paper.
The main body of the paper presents procedures and theoretical basis of the research. It usually consists of several sections. The question which is answered is: What did you do? The main body can be structured in the following way:
Detailed description of the problem under study and its analysis.
Related work (optional)
Solution to the problem
Results (the findings: positive and negative if there are some)
Taking into account a large amount of information given in this part of the paper, independent work of students is implied. The master students have already known the field of their research and the subject matter of their Master thesis has been chosen. Consequently, they have got a lot of literature sources to read on their major.
Exercise I
Task 1. Take the main body of any paper on your major and give a detailed description of
the problem under study
Solution to the problem
Results
Task 2. Retell the main body of the paper using the appropriate link words.
Exercise II
Translate the sentences from Russian into English using the Participle:
Большинство разработчиков, например, не знакомы с платформой разработки Android и в их приложениях появляются новые ошибки.
Хотя Android приложения разрабатываются с использованием Java технологии, они отличаются от стандартных клиент-серверных Java приложений и традиционных , основанных на событиях, компьютерных приложений.
Структура AndroidRipper нацелена на определенные компоненты программного обеспечения, предложенные фреймворком Android разработки, такие как Activity, Service, Content Provider и т.д.,что требует определенных правил управления и особого жизненного цикла.
Описание типичных ошибок, встречающихся в доступных Android приложениях, показывает, что часто ошибки происходят из-за неправильного управления жизненным циклом компонента Activity.
Компонент Activity предоставляет важные функции для пользовательского интерфейса приложения и реагирует на события, создаваемые пользователем и другими компонентами системы.
Мы представляем AndroidRipper ( автоматизированная технология), реализованную как инструмент, который тестирует Android приложения через их графический пользовательский интерфейс.
AndroidRipper использует риппер, который автоматически и систематически просматривает пользовательский интерфейс приложения, игнорируя или выполняя прецеденты (test cases) по мере того, как появляются новые события.
Технология тестирования для Android – это технология, предложенная авторами классификации ошибок (7).
AndroidRipper, при исследовании ГИП, определяет сбои приложения во время исполнения.
Некоторые, характерные для Android ошибки приводятся в классификации Хью и др. (7)
The structure of the Conclusions
One should keep in mind that the Conclusion section is not the repetition of the Abstract or some other part of the paper. As a matter of fact, this section consists of one or two paragraphs. The items one might find are as follows:
A brief description of the most essential finding
Improvements that can be done
Suggestions for further work
Tips for policy modification
Exercise I
A Cross-Cultural Comparative Study of Users’ Perceptions
of a Webpage: With a Focus on the Cognitive Styles of
Chinese, Koreans and Americans
Ying Dong * and Kun-Pyo Lee
É Ê8Ë_ÌÎÍ!ÏIÐ Ñ_Ò6ÌVÓ¾Ï_Ë
Conclusion
Nisbett (2001, 2002, 2003) proposed that the thought patterns of East Asians and Westerners differ greatly/great and classified these differences as holistic/ holistically and analytic/analytically. Holistically/holistic -minded people have a tendency to perceive a scene globally/global, in other words, to perceive the context and the field as a whole. They also tend to focus on the relationships between objects and the field, meaning that they are more field-dependent/dependently. On the other hand, analytically/analytical - minded people have a tendency to perceive an object separately/separate from the scene and tend to assign objects into categories. Analytically/analytical-minded people are more field-independent/independently. In this study, Chinese, Koreans (both holistic thinkers), and Americans (analytic thinkers) were recruited for the experiment. Findings from the analysis suggest that the Chinese, Korean, and American participants employed different viewing patterns when viewing a webpage. The Chinese and Korean subjects showed more similarities to holistic thought patterns, while the American subjects showed more similarities to analytic thought patterns. The present findings indicate that holistically/holistic-minded people and analytically/analytical-minded people have unique/uniquely ways of perceiving a webpage. These characteristics of perception reflect some aspects of Nisbett’s (2001, 2002, 2003) proposition about cognition. It is suggested that webpage designers should be aware of the cognitive differences existing among holistically/holistically-minded people and analytically/analytical-minded people, and that webpage design should be carried out according to the target audience’s specific/specifically cognitive style in order to enhance perception and usage of the webpage.
Task 1. Analyze the Conclusion. Focus on the most essential findings described in the section.
Task 2. Choose the correct highlighted word (either adjective or adverb)
Task 3. What do in other words, on the other hand, while mean in this text?
Task 4. Define the function of should in the last sentence.
Task 5. Retell the Conclusion.
Exercise II
Detecting Defects in Object Oriented Designs:
Using Reading Techniques to Increase Software Quality
Guilherme H. Travassos1,o Forrest Shull Michael Fredericks Victor R. Basiliw
Experimental Software Engineering Group and Institute for Advanced Computer Studies
University of Maryland at College Park
A. V. Williams Building, Bldg#115
College Park , MD, 20742
Fax 301 405 3691
{travassos, fshull, fred, basili}@cs.umd.edu
oCOPPE/UFRJ
C.P. 68511 - Ilha do Fundão
Rio de Janeiro – RJ – 21945-180
Brazil
wFraunhofer Center --Maryland
3115 AgLife Science Surge Bldg
College Park, MD 20742
ABSTRACT
Inspections can be used to identify defects in software artifacts. In this way, inspection methods help to improve software quality, especially when used early in software development. Inspections of software design may be especially crucial since design defects (problems of correctness and completeness with respect to the requirements, internal consistency, or other quality attributes) can directly affect the quality of, and effort required for, the implementation.
We have created a set of “reading techniques” (so called because they help a reviewer to “read” a design artifact for the purpose of finding relevant information) that gives specific and practical guidance for identifying defects in Object-Oriented designs. Each reading technique in the family focuses the reviewer on some aspect of the design, with the goal that an inspection team applying the entire family should achieve a high degree of coverage of the design defects. In this paper, we present an overview of this new set of reading techniques. We discuss how some elements of these techniques are based on empirical results concerning an analogous set of reading techniques that supports defect detection in requirements documents. We present an initial empirical study that was run to assess the feasibility of these new techniques, and discuss the changes made to the latest version of the techniques based on the results of this study.
Keywords: Software Engineering Practices, Object Testing and
Metrics, Object Oriented Software Quality, Software Inspection.