Evaluation of the Component`s Interconnection Impact on the System Security

From its-wiki.no
Revision as of 14:26, 18 August 2016 by Seraj.Fayyad (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Evaluation of the Component`s Interconnection Impact on the System Security

by N.n.
Supervisor(s) Seraj.Fayyad, Josef Noll
Due date 2017/06/05
Status Planned
Problem description: Interconnection between the components for a given system has a good impact on the security level of this system. Reflection of this impact on the evaluated security level of this system is considerably important. Evaluation of this impact is investigated in some research, which reflect that system security level is differentiated based on the interconnection of its components. In this thesis, the student will investigated and apply a proposed solution for the evaluation of interconnection. For applying the proposed solution the student will develop new functionalities for already initiated framework. Before starting with development student will get a session to have the needed technical knowledge to start up the development easy way.
Methods and Tools: The tools and methods in this thesis are based on
  • A set of scenario, describing the challenges
  • A list of requirements being extracted from the scenarios
  • A description and evaluation of technologies and tools being candidates for solutions
  • A functional architecture/description of the envisaged system
  • An implementation of the core concepts
  • A demonstration of the solution
  • An evaluation of the solution, including a critical review of the descisions taken earlier
  • Conclusions
  • References
Time schedule The envisaged time schedule is:
T0+0 starting month, T0+m get an overview about the recommended references and verify from having needed conceptional knowledge to startup working on the thesis.
T0+2 months: get familiar with the needed technologies necessary for the thesis (e.g. Java (J2EE) and Java script) and get familiar with the initiated framework.
T0+4: Establish the table of content (TOC) of the envisaged thesis. Each section shall contain 3-10 keywords describing the content of that section
T0+5: Provide a draft of section 2 (scenario) and 3 (technologies)
T0+6: Deliver the thesis and related functionalities.
Pre-Knowledge This thesis includes a reasonable amount of programming and IT security terminologies. Thus it is expected that the student has the basic knowledge in (java and java script) and IT security.
Approved Pending by
Keywords IoTSec, interconnection evaluation
Depiction

this page was created by Special:FormEdit/Thesis, and can be edited by Special:FormEdit/Thesis/Evaluation of the Component`s Interconnection Impact on the System Security

This page provides hints on what to include in your master thesis.

TOC

Title page, abstract, ...

1. Introduction, containing: short intro into the area, what is happening
1.1 Motivation, containing: what triggered me to write about what I'm writing about
1.2 Methods, containing: which methods are you using, how do you apply them
2. Scenario, optional chapter for explaining some use cases
2.1 user scenario, (bad name, needs something bedre)
2.2 Requirements/Technological challenges
3. State-of-the art/Analysis of technology, structure your content after hardware/SW (or other domains). Describe which technologies might be used to answer the challenges, and how they can answer the challenges
3.1 technology A
3.2 technology B
4. Implementation
4.1 Architecture, functionality
4.2
5. Evaluation
6. Conclusions
References

Comments

Red line

Your thesis should have a "red line", which is visible throughout the whole thesis. This means you should mention in the beginning of each chapter how the chapter contributes to the "goals of the thesis".

Use of scientific methods

A thesis follows a standard method:

  • describe the problem (problemstilling)
  • extract the challenges. These challenges should be measurable, e.g. method is too slow to be useful to voice handover.
  • Analyse technology with respect to challenges. Don't write & repeat "everything" from a certain technology, concentrate on those parts (e.g. protocols) which are of importance for your problem

References

  • Wikipedia is good to use to get an overview on what is happening. But there is not scientific verification of Wikipedia, thus you should use wikipedia only in the introduction of a chapter (if you use text from wikipedia). Use scientific literature for your thesis.
  • Scientific library is "at your hand", you can get there directly from UiO: [[How to get access to IEEE, Springer and other scientific literature -> Unik/UiOLibrary]]
  • I suggest that references to web pages, e.g. OASIS, W3C standards, are given in a footnote. Only if you find white papers or other .pdf documents on a web page then you refer to them in the reference section.

Evaluation of own work

Perform an evaluation of your own work. Revisit the challenges and discuss in how you fulfilled them. Provide alternative solution and discuss what should be done (or what could have been done).