Second Review Document

<Title of Project>

Name
Reg. No.
Mobile No.
Mail Id.

Guide Name
Designation
Mobile No.
Mail ID

B.Tech.
in
Computer Science and Engineering

School of Computer Science & Engineering

®
Font – Times New Roman
Font Size – 12
Line Spacing – 1.5

 Abstract: (300 words) (with Key words)

 System Architecture / System Design / System Model with description

 Methodology Adapted

 Expected Results with discussion

 Details of Hardware and Software

 References : (API format)

Eg.

References

Weblinks:
1. https://www.cloudflare.com/under-attack (accessed on December 2014).
2. http://www.thedailybeast.com/articles/2010/12/11/hackers-10-most-famous-attacks-
wormsandddos- takedowns.html (accessed on December 2014).
Journal:
1. G. Zacharia, ‘Trust Management through Reputation Mechanisms’, Workshop in
Deception, Fraud and Trust in Agent Societies, Third International Conference on
Autonomous Agents (Agents’99), ACM, (1999). International Journal of Security and
Its Applications Vol.9, No.9 (2015) 210 Copyright ⓒ 2015 SERSC
2. L. Eschenauer, V. D. Gligor and J. Bara, ‘On Trust Establishment in Mobile Ad Hoc
Networks’, Security Protocols Springer, (2004), pp. 47-66.
3. N.Ch. S.N. Iyengar, Gopinath Ganapathy, P.C. Mogan Kumar, and Ajith Abraham, ‘A
multilevel thrust filtration defending mechanism against DDoS attacks in cloud
computing environment’, International Journal of Grid and Utility Computing, vol. 5,
no. 4, (2014), pp. 236-248.
Book:
1. A.P. Malvino and D.P. Leach – Digital Principles and Applications – Tata McGraw Hill,
2014.
Special Edition – 2009

 Max. No. of pages - 15 Pages

1. Introduction
1.1. Theoretical Background
1.2. Motivation
1.3. Aim of the proposed Work
1.4. Objective(s) of the proposed work
2. Literature Survey
2.1. Survey of the Existing Models/Work
2.2. Summary/Gaps identified in the Survey
3. Overview of the Proposed System
3.1. Introduction and Related Concepts
3.2. Framework, Architecture or Module for the Proposed System(with explanation)
3.3. Proposed System Model(ER Diagram/UML Diagram/Mathematical Modeling)
4. Proposed System Analysis and Design
4.1. Introduction
4.2. Requirement Analysis
4.2.1. Functional Requirements
4.2.1.1. Product Perspective
4.2.1.2. Product features
4.2.1.3. User characteristics
4.2.1.4. Assumption & Dependencies
4.2.1.5. Domain Requirements
4.2.1.6. User Requirements
4.2.2. Non Functional Requirements
4.2.2.1. Product Requirements
4.2.2.1.1. Efficiency (in terms of Time and Space)
4.2.2.1.2. Reliability
4.2.2.1.3. Portability
4.2.2.1.4. Usability
4.2.2.2. Organizational Requirements
4.2.2.2.1. Implementation Requirements (in terms of deployment)
4.2.2.2.2. Engineering Standard Requirements
4.2.2.3. Operational Requirements (Explain the applicability for your work w.r.to
the following operational requirement(s))
 Economic
 Environmental
 Social
 Political
 Ethical
 Health and Safety
 Sustainability
 Legality
 Inspectability
4.2.3. System Requirements
4.2.3.1. H/W Requirements(details about Application Specific Hardware)
4.2.3.2. S/W Requirements(details about Application Specific Software)
5. Results and Discussion
6. References