CSCE 522 Information Security Principles Project Guidelines, Study Guides, Projects, Research of Computer Science

The project requirements for the csce 522 information security principles course in the fall of 2002. Students are required to form research groups, select a topic of interest, identify initial research papers, perform detailed research, develop solutions, and establish contributions. The project consists of several deliverables with different due dates.

Typology: Study Guides, Projects, Research

Pre 2010

Uploaded on 09/02/2009

koofers-user-ph2
koofers-user-ph2 🇺🇸

10 documents

1 / 3

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
CSCE 522 – Information Security Principles
Fall 2002
Project Information
Project requirements:
1. Form research groups of 2-4 students
Organize a research group of 2-4 students with similar interest. Establish strengths of group members
and how their strength may compliment the other’s.
Deliverables: List of group members, their expertise, and how they compliment each other’s skills.
Due date: Sept 22, 2003
2. Select topic of interest
You search current research topics, what are the main security issues that the scientific community is
involved in. Based on the dynamic aspect of the general topic, you need to use resources available on
web, journal, and conference publications. Journal publications are in general the highest quality ones,
on the other hand, they have a long turn around time, thus may miss out on some very recent
achievements. ACM, IEEE conferences are good quality ones, too. At this phase you read a lot, but in
high level.
Deliverables: Short description of one or two topic of interest.
Due date: Oct. 6, 2003
3. Identify initial research papers, define the research problem, and expected contributions of the research
After selecting a general area of interest, you need to settle on a particular problem, e.g., after selecting
the area of security of web-based collaboration, you chose to study access control requirements for a
particular application.
Deliverables: Choose a particular problem within one of the topic of interest, explain the problem in a
greater context and show its importance. Lists of initial publications (3-4 papers) and limitations of
current solutions.
Due date: Oct. 6, 2003
4. Perform detailed research of the chosen topic – Build background information
Gather additional publications on the chosen topic. In general, you’ll read around 5-10 papers,
depending on the technical difficulties of the papers. At the end of this phase you have a clear
understanding of the current state of research on the chosen topic and related issues.
Deliverables: List of extended reference publications, their analysis, and relation to the problem of
your chosen problem. For each publication, list: title, name of authors, where was it published, what
the paper is about (1-2 paragraph), what are the paper’s contributions, what proof the paper gives to
support the claimed contributions, how important the solved problem is, what are the limitations of the
solution, how can we do better…
Due date: October 20, 2003
5. Develop solutions for research problem
This is the phase where you use your resources to develop solution for the research problem. It may be
implementation oriented work based on existing publications, an implementation to solve a particular
problem within a domain, or purely theoretical research. For any of these, you need to:
REPEAT UNTIL SOLUTION=DEVELOPED OR DEADLINE= REACHED
a. Revise research problem and expected contributions
After acquiring extended information in the field of interest, revisit the research problem
description developed in 2. Use your knowledge to refine (focus) the research problem and
give a better estimate of the expected results. In general, implementation oriented works
may be based on applying existing technologies for a particular domain. Theoretical
research requires that you show that it is different (and usually better) than the existing
solutions.
Deliverables: Revised problem formulation and expected results.
Due date: (Draft) Nov 17, 2003
b. Show problem in extended context
Describe the problem from a high level view. This will put the reader into the context,
allows to establish the importance of the work.
Deliverables: Placement of your work in greater context.
Due date: (Draft) Nov 17, 2003
c. Give a representative example of problem
Give a simple, easy to follow example of the targeted problem. This should be
understandable for any reader without additional knowledge of the particular domain.
Deliverables: Write up of an example.
Due date: (Draft) Nov 17, 2003
d. Define related concepts
pf3

Partial preview of the text

Download CSCE 522 Information Security Principles Project Guidelines and more Study Guides, Projects, Research Computer Science in PDF only on Docsity!

CSCE 522 – Information Security Principles Fall 2002 Project Information Project requirements:

1. Form research groups of 2-4 students Organize a research group of 2-4 students with similar interest. Establish strengths of group members and how their strength may compliment the other’s. Deliverables : List of group members, their expertise, and how they compliment each other’s skills. Due date : Sept 22, 2003

  1. Select topic of interest You search current research topics, what are the main security issues that the scientific community is involved in. Based on the dynamic aspect of the general topic, you need to use resources available on web, journal, and conference publications. Journal publications are in general the highest quality ones, on the other hand, they have a long turn around time, thus may miss out on some very recent achievements. ACM, IEEE conferences are good quality ones, too. At this phase you read a lot, but in high level. Deliverables : Short description of one or two topic of interest. Due date : Oct. 6, 2003
  2. Identify initial research papers, define the research problem, and expected contributions of the research After selecting a general area of interest, you need to settle on a particular problem, e.g., after selecting the area of security of web-based collaboration, you chose to study access control requirements for a particular application. Deliverables : Choose a particular problem within one of the topic of interest, explain the problem in a greater context and show its importance. Lists of initial publications (3-4 papers) and limitations of current solutions. Due date : Oct. 6, 2003
  3. Perform detailed research of the chosen topic – Build background information Gather additional publications on the chosen topic. In general, you’ll read around 5-10 papers, depending on the technical difficulties of the papers. At the end of this phase you have a clear understanding of the current state of research on the chosen topic and related issues. Deliverables : List of extended reference publications, their analysis, and relation to the problem of your chosen problem. For each publication, list: title, name of authors, where was it published, what the paper is about (1-2 paragraph), what are the paper’s contributions, what proof the paper gives to support the claimed contributions, how important the solved problem is, what are the limitations of the solution, how can we do better… Due date : October 20, 2003
  4. Develop solutions for research problem This is the phase where you use your resources to develop solution for the research problem. It may be implementation oriented work based on existing publications, an implementation to solve a particular problem within a domain, or purely theoretical research. For any of these, you need to: REPEAT UNTIL SOLUTION=DEVELOPED OR DEADLINE= REACHED a. Revise research problem and expected contributions After acquiring extended information in the field of interest, revisit the research problem description developed in 2. Use your knowledge to refine (focus) the research problem and give a better estimate of the expected results. In general, implementation oriented works may be based on applying existing technologies for a particular domain. Theoretical research requires that you show that it is different (and usually better) than the existing solutions. Deliverables : Revised problem formulation and expected results. Due date : (Draft) Nov 17, 2003 b. Show problem in extended context Describe the problem from a high level view. This will put the reader into the context, allows to establish the importance of the work. Deliverables: Placement of your work in greater context. Due date : (Draft) Nov 17, 2003 c. Give a representative example of problem Give a simple, easy to follow example of the targeted problem. This should be understandable for any reader without additional knowledge of the particular domain. Deliverables : Write up of an example. Due date : (Draft) Nov 17, 2003 d. Define related concepts

You may need to define concepts related to the research issue. This may be adapting someone else’s definition (make sure you put the references there) or you may need to develop your own definitions. Deliverables : Definition of related concepts and their definitions. Due date : (Draft) Nov 17, 2003 e. Develop technical solution Provide a technical (implementation oriented or theoretical) solution for the chosen problem. This requires the longest time and may require that you go back to section a. to revise your definitions. Deliverables : Developed and documented technical results of the research. Due date : (Draft) Nov 17, 2003

  1. Establish contributions Define what are the contributions of the research to the field of internet security, give justifications of these contributions, e.g., algorithm and it’s analysis, proofs, experimental results, etc. Deliverables : List of contributions of the paper and their proofs. Due date : (Draft) Nov 17, 2003
  2. Final report Create a final report that contains your previous findings,. Final report format is given bellow. Deliverables : Final document (20-30 pages, double spaced, 12 points) of the format given bellow. Due date : Nov. 24, 2003
  3. Group presentation Group members have to coordinate the presentation, that every member of the group is involved in the presentation (e.g., speech, demo, etc.). Deliverables : 15-20 min presentation at the end of semester. Due date : last week of classes Percentage of final project grade per components
  4. &. 2 : 5%
  5. : 5%
  6. : 25%
  7. & 6. : 20%
  8. : 40%
  9. : 5% How to read scientific publications?  Paper at a glance (10-15 min) : read Abstract, skim Introduction, read Conclusions After this stage you should have a general idea what the paper is about, but do not know in detail the technical content, it’s correctness, supporting arguments. However, you can decide whether the topic is important for you. If still interested in reading the paper, follow next step.  High-level understanding of problem and proposed solutions (30-60 min) : Read Abstract, Introduction, skim “body” of the paper, read Conclusions. When skimming through paper, focus on technical details that are used to establish correctness of presented solutions or show limitations of other works. After this phase you should have a pretty good understanding of the technology being described and being able to evaluate the quality of the paper.  Detailed reading (2-3 hours, days ?): If you’re still interested in the paper, get a pencil and make sure you have plenty of time. Read the paper from beginning to the end, make notes on the margin, and verify correctness of presented concepts (not all published paper are correct, most have some flaws). You may also have to get additional papers, usually listed in the Reference section to fully understand the paper. Questions to keep in mind when reading the paper:  What do the authors claim? - Usually this is some sort of contribution to the field of research.  What supporting evidences the authors give for their claim? – Formal proofs, experimental results, etc. These must be facts.  Is the problem addressed is important? – Do we really need research in this field?  Your comments on the work: Limitations? How to improve it? Final Report format: