Detailed Design Format
Detailed Design Format
Introduction
(1 to 2 pages)
This is a general introduction to what the Project is all about and also about the research area it is
not just a description of the contents of each section. Briefly summarize the question (you will be
stating the question in detail later), some of the reasons why it is a worthwhile question, and
perhaps give an overview of your main results. This is a birds-eye view of the answers to the
main questions answered in the Project. A brief section giving background information may be
necessary, especially if your work spans two or more traditional fields. That means that your
readers may not have any experience with some of the material needed to follow your Project, so
you need to give it to them. A different title than that given above is usually better; e.g., "A Brief
Review of Mutation Testing."
Chapter 2
Literature Review
(2 to 3 pages)
Here you review the state of the art relevant to your Project. Again, a different title is probably
appropriate; e.g., "State of the Art in Mutation Testing." The idea is to present (critical analysis
comes a little bit later) the major ideas in the state of the art right up to, but not including, your
own personal brilliant ideas. You organize this section by idea, and not by author or by
publication.
Chapter 3
Problem Statement
(1 Page)
Engineering theses tend to refer to a "problem" to be solved where other disciplines talk in terms
of a "question" to be answered. In either case, this section has three main parts:
1. A Gap Analysis between the existing work with the desired/ targeted work
2. A concise statement of the problem that your Project tackles
3. Justification, by direct reference to section 3, that your question is previously unanswered
4. Discussion of why it is worthwhile to answer this question.
Item 3 above is where you analyze the information which you presented in Section 3. For
example, maybe your problem is to "Developing Mutation Test Cases Using GAs " (you would
further describe what you mean by "Mutation Test Cases" and "Criteria to Kill Mutants" in the
problem statement). Now in your analysis of the state of the art you would show how each class
of current approaches fails (i.e. can handle only small problems, or takes too much time).
1
Since this is one of the sections that the readers are definitely looking for, highlight it by using
the word "problem" or "question" in the title: e.g. "Research Question" or "Problem Statement".
Chapter 4
Problem Solution
(1 or 2 pages)
This part of the Project is much more free form. It may have one or several sections and
subsections. But it all has only one purpose: to convince the examiners that you answered the
question or solved the problem that you set for yourself in Section 4. So show what you did that
is relevant to answering the question or solving the problem. This section of Project report
should mainly deal with Design and Implementation of the research problem.
Chapter 5
(1 page)
This part of the Project is to mainly discuss about the testing done on the implementation of your
research problem and also show the result derived from it .
Chapter 6
Conclusions
(1 page)
You generally cover three things in the Conclusions section, and each of these usually merits a
separate subsection:
1. Conclusions
2. Summary of Contributions
3. Future Research
Conclusions are not a rambling summary of the Project: they are short, concise statements of the
inferences that you have made because of your work. It helps to organize these as short
numbered paragraphs, ordered from most to least important. All conclusions should be directly
related to the research question stated in Section 4. Examples:
1. The problem stated in Section 4 has been solved: as shown in Sections? to ??, an
algorithm capable of handling Test Case Generation problem in reasonable time has
been developed.
2. The principal mechanism needed to improve the Mutation Testing using GAs.
3. Etc.
The Summary of Contributions will be much sought and carefully read by the examiners. Here
you list the contributions of new knowledge that your Project makes. Of course, the Project itself
2
must substantiate any claims made here. There is often some overlap with the Conclusions, but
that's okay. Concise numbered paragraphs are again best. Organize from most to least important.
Examples:
1. Developed a much quicker algorithm.
2. Demonstrated the first use.
3. Etc.
The Future Research subsection is included so that researchers picking up this work in future
have the benefit of the ideas that you generated while you were working on the project. Again,
concise numbered paragraphs are usually best.
References
(min. 22 references)
The list of references is closely tied to the review of the state of the art given in section 3. Most
examiners scan your list of references looking for the important works in the field, so make sure
they are listed and referred to in section 3. All references given must be referred to in the main
body of the Project. Note the difference from a Bibliography, which may include works that are
not directly referenced in the Project. Organize the list of references either alphabetically by
author surname (preferred), or by order of citation in the Project.
Appendices
What goes in the appendices? Any material which impedes the smooth development of your
presentation, but which is important to justify the results of a Project. Generally it is material that
is of too nitty-gritty a level of detail for inclusion in the main body of the Project, but which
should be available for perusal by the examiners to convince them sufficiently. Examples include
immense tables of data, lengthy mathematical proofs or derivations, etc.
Reference:
Few examples to how to write references
1. S. Grinstein, J.Huth and J.Schopf. Resource Predictors in HEP Applications.
Computing in High Energy Physics,Interlaken, Switzerland, Sep. 2004. pp. 69.
2. R. Braun, H. Siegel, N. Beck, L. Boloni, M. Maheswaran, A. Reuther, J. Robertson, M.
Theys, B. Yao, D. Hensgen and R. Freund, A Comparison of Eleven Static Heuristics for
Mapping a Class of Independent Tasks onto Heterogeneous DistributedComputing
Systems, in J. of Parallel and Distributed Computing, vol.61, No. 6, pp.810-837, 2001.
1. Type Style and Spacing: Same type style and font should be used throughout the Project
and should be justified. All printing should be single side. As per following
specifications:
CHAPTER 1
INTRODUCTION
CHAPTER 2
LITERATURE REVIEW
community in general.
awareness of cryptography soon made it a very useful tool of modern day technology. A large
number of cryptographic papers laid to the rebirth of the science. Horst Fiestel began the
development of the Data Encryption Standard (DES) (which is a private key algorithm) and laid
the foundation of Fiestel Networks in general. Martin Hellman and Whitefield Diffie developed
the public key cryptography in 1975.
CHAPTER 3
PROBLEM STATEMENT
In this chapter, we shall analyze the properties of the CMEA which cause its weakness.
The recovery of all the 256 values of the T-Box is equivalent to breaking of the cipher, so the
strength of the T-Box requires special attention and has been treated subsequently in details in
this and the next chapter.
CHAPTER 4
PROBLEM SOLUTION
In this section the weaknesses that are given in Chapter 2 will be removed by elimination
their causes as identified in Chapter 3. Each property that causes a dent in the CMEAs weakness
will be dealt with so that none of the attacks that have been described in Chapter 3 work against
the algorithm. In addition, ways to deal with some of the properties that could be weak points in
the CMEA but are not used explicitly in the two attacks are also covered in this chapter.
CHAPTER 5
TESTING AND RESULT
10
CHAPTER 6
CONCLUSIONS
6.1 SUMMARY
CMEA consists of three layers. The first layer performs one non-linear pass on the block,
this effects left-to-right diffusion [38]. The second layer is a purely linear, unkeyed operation
intended to make changes propagate in the opposite direction. One can think of the second step
as (roughly speaking) XORing the right half of the block onto the left half. The third layer
performs a final nonlinear pass on the block from left to right; in fact, it is the inverse of the first
layer.
11
REFERENCES
[1]
[2]
[3]
[4]
[5]
12