Istlab - User contributions [en]

Thunderbolt to Gigabit Ethernet Adapter

2013-06-19T13:06:41Z

Stheotok:

* Quantity: 2

[[Category:Equipment]]
[[Category:Equipment STEREO]]
[[Category:Equipment SENSE]]
[[Category:Equipment dds]]
[[Category:Equipment stheotok]]
[[Category:SENSE]]

Stephanos Androutsellis PhD research plan

2008-08-27T06:02:37Z

Stheotok:

Stephanos Androutsellis PhD research plan

2008-07-08T13:43:39Z

Stheotok:

Stephanos Androutsellis PhD research plan

2008-07-04T17:02:45Z

Stheotok:

==Publications Plan==
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

==Non-thesis-related personal plans==
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.

==PhD thesis table of contents==

{| border="1"
! No !! Section !! Comments !! Status !! Target
|-
! 1.
| Introduction
| ...
|
|
|-
! 1.1.
| Overview of my research and motivation
| Use Ptrim S1
|Needs editing and writing
|0.5D
|-
! 1.2.
| Main results and original contributions
| ...
|Needs writing
|0.5D
|-
! 1.3.
| Organisation of thesis
| ...
|Needs writing
|0.3D
|-
! 2.
| Theory and background
| ...
|
|
|-
! 2.1.
| Introduction – big picture
| ...
|Needs writing
|0.3D
|-
! 2.2.
| P2P networks and architectures
| Based on ACM survey
| Almost ready, need some formatting
| 0.2D
|-
! 2.3.
| Transaction processing systems
|
|
|
|-
! 2.3.1
| Online Transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
| Almost ready, need some formatting
| 0.2D
|-
! 2.3.2
| Definitions and requirements analysis
|
| Almost ready, need some formatting
| 0.2D
|-
! 2.4.
| Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! 2.4.1.
| Social behaviour and incentives
|
| Almost ready, need some formatting
| 0.5D
|-
! 2.4.2.
| Trust and reputation
|
| Almost ready, need some formatting
| 0.5D
|-
! 2.4.3.
| Reputation management
|
| Almost ready, need some formatting
| 0.2D
|-
! 2.4.4.
| Distributed reputation management
|
| Almost ready, need some formatting
| 0.2D
|-
! 2.4.5.
| The MoR-Trust system
|
| Needs editing
|0.3D
|-
! 2.5.
| Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|Needs editing
|0.3D
|-
! 2.6.
| Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|Needs writing
|0.3D
|-
! 3.
| Problem definition and proposed solution
| ...
|
|
|-
! 3.1.
| Definition of problem we want to attack: Managing P2P transaction risk
| Includes general and also specific goals
|Needs writing
|0.5D
|-
! 3.2.
| Limits of research scope
| Things that are not our problem ( References to Section 7).
|Needs writing
|0.5D
|-
! 3.3.
| Proposed solution: A Market based approach
| At an abstract level. Use patent literature for ideas.
|
|
|-
! 3.3.1.
| Relation to other approaches
| Complementary to reputation management, explain how the two could cooperate.
|Needs writing
|0.5D
|-
! 3.3.2.
| Abstract description of proposed solution.
| Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
|Needs editing and writing
|0.5D
|-
! 4.
| Methodology
| ...
|
|
|-
! 4.1.
| Description of our overall approach
| We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
| Needs editing and writing
| 0.5D
|-
! 4.2.
| Hypotheses
| What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
| Needs writing
| 1D
|-
! 4.3.
| Prototype system trials
| What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
|
|
|-
! 4.3.1.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc.
| Needs editing and writing
| 0.5D
|-
! 4.3.2.
| Methodology for evaluation
| How will we evaluate the results.
| Needs editing and writing
| 0.5D
|-
! 4.4.
| Composite experimental trials
| Use Ptrim S4.2. Which hypotheses do we address here.
|
|
|-
! 4.4.1.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
| Needs editing and writing
| 1D
|-
! 4.4.2.
| Methodology for evaluation
| How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
| Needs editing and writing
| 1D
|-
! 5.
| Design and implementation
| Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
|
|
|-
! 5.1.
| Design of Ptrim system
| ...
| Needs editing and writing
| 1D
|-
! 5.2.
| Ptrim implementation details
| How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
| Needs editing and writing
| 1D
|-
! 5.3.
| Composite experiment setup
|
|
|
|-
! 5.3.1
| Implementation
| How we implemented this: Perl/CGI/MySQL etc.
| Needs editing and writing
| 1D
|-
! 5.3.2.
| Data crawling
| How we did this
| Needs editing
| 0.5D
|-
! 6.
| Results, evaluation and discussion
| ...
|
|
|-
! 6.1.
| Evaluation of prototype trial outcomes
| Use Ptrim S5.1. Refer to hypotheses
| Needs editing and writing
| 0.5D
|-
! 6.2.
| Evaluation of composite trial outcomes
| Use Ptrim S5.2. Refer to hypotheses
| Needs editing and writing
| 2D
|-
! 6.3.
| Discussion of overall findings and implications for our approach
| ...
| Needs writing
| 0.5D
|-
! 7.
| Future work
| Mention these also in Section 3.b.
|
|
|-
! 7.1.
| Security
| ...
| Needs editing
| 0.5D
|-
! 7.2.
| Collusion detection
| ...
| Needs editing
| 0.5D
|-
! 7.3.
| Insuring insurance transactions
| ...
| Needs editing
| 0.5D
|-
! 7.4.
| Further experiments and simulation studies
| ...
| Needs editing
| 0.5D
|-
! 8.
| Conclusions and synopsis
| ...
| Needs writing
| 1D
|}

==Egg timer==
* On July 4th there were 20.5 days of work left.

==PhD thesis research plan==

* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 30th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-07-04T16:57:38Z

Stheotok:

==Publications Plan==
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

==Non-thesis-related personal plans==
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.

==PhD thesis table of contents==

{| border="1"
! No !! Section !! Comments !! Status !! Target
|-
! 1.
| Introduction
| ...
|
|
|-
! 1.1.
| Overview of my research and motivation
| Use Ptrim S1
|Needs editing and writing
|0.5D
|-
! 1.2.
| Main results and original contributions
| ...
|Needs writing
|0.5D
|-
! 1.3.
| Organisation of thesis
| ...
|Needs writing
|0.3D
|-
! 2.
| Theory and background
| ...
|
|
|-
! 2.1.
| Introduction – big picture
| ...
|Needs writing
|0.3D
|-
! 2.2.
| P2P networks and architectures
| Based on ACM survey
| Almost ready, need some formatting
| 0.2D
|-
! 2.3.
| Transaction processing systems
|
|
|
|-
! 2.3.1
| Online Transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
| Almost ready, need some formatting
| 0.2D
|-
! 2.3.2
| Definitions and requirements analysis
|
| Almost ready, need some formatting
| 0.2D
|-
! 2.4.
| Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! 2.4.1.
| Social behaviour and incentives
|
| Almost ready, need some formatting
| 0.5D
|-
! 2.4.2.
| Trust and reputation
|
| Almost ready, need some formatting
| 0.5D
|-
! 2.4.3.
| Reputation management
|
| Almost ready, need some formatting
| 0.2D
|-
! 2.4.4.
| Distributed reputation management
|
| Almost ready, need some formatting
| 0.2D
|-
! 2.4.5.
| The MoR-Trust system
|
| Needs editing
|0.3D
|-
! 2.5.
| Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|Needs editing
|0.3D
|-
! 2.6.
| Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|Needs writing
|0.3D
|-
! 3.
| Problem definition and proposed solution
| ...
|
|
|-
! 3.1.
| Definition of problem we want to attack: Managing P2P transaction risk
| Includes general and also specific goals
|Needs writing
|0.5D
|-
! 3.2.
| Limits of research scope
| Things that are not our problem ( References to Section 7).
|Needs writing
|0.5D
|-
! 3.3.
| Proposed solution: A Market based approach
| At an abstract level. Use patent literature for ideas.
|
|
|-
! 3.3.1.
| Relation to other approaches
| Complementary to reputation management, explain how the two could cooperate.
|Needs writing
|0.5D
|-
! 3.3.2.
| Abstract description of proposed solution.
| Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
|Needs editing and writing
|0.5D
|-
! 4.
| Methodology
| ...
|
|
|-
! 4.1.
| Description of our overall approach
| We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
| Needs editing and writing
| 0.5D
|-
! 4.2.
| Hypotheses
| What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
| Needs writing
| 1D
|-
! 4.3.
| Prototype system trials
| What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
|
|
|-
! 4.3.1.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc.
| Needs editing and writing
| 0.5D
|-
! 4.3.2.
| Methodology for evaluation
| How will we evaluate the results.
| Needs editing and writing
| 0.5D
|-
! 4.4.
| Composite experimental trials
| Use Ptrim S4.2. Which hypotheses do we address here.
|
|
|-
! 4.4.1.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
| Needs editing and writing
| 1D
|-
! 4.4.2.
| Methodology for evaluation
| How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
| Needs editing and writing
| 1D
|-
! 5.
| Design and implementation
| Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
|
|
|-
! 5.1.
| Design of Ptrim system
| ...
| Needs editing and writing
| 1D
|-
! 5.2.
| Ptrim implementation details
| How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
| Needs editing and writing
| 1D
|-
! 5.3.
| Composite experiment setup
|
|
|
|-
! 5.3.1
| Implementation
| How we implemented this: Perl/CGI/MySQL etc.
| Needs editing and writing
| 1D
|-
! 5.3.2.
| Data crawling
| How we did this
| Needs editing
| 0.5D
|-
! 6.
| Results, evaluation and discussion
| ...
|
|
|-
! 6.1.
| Evaluation of prototype trial outcomes
| Use Ptrim S5.1. Refer to hypotheses
| Needs editing and writing
| 0.5D
|-
! 6.2.
| Evaluation of composite trial outcomes
| Use Ptrim S5.2. Refer to hypotheses
| Needs editing and writing
| 2D
|-
! 6.3.
| Discussion of overall findings and implications for our approach
| ...
| Needs writing
| 0.5D
|-
! 7.
| Future work
| Mention these also in Section 3.b.
|
|
|-
! 7.1.
| Security
| ...
| Needs editing
| 0.5D
|-
! 7.2.
| Collusion detection
| ...
| Needs editing
| 0.5D
|-
! 7.3.
| Insuring insurance transactions
| ...
| Needs editing
| 0.5D
|-
! 7.4.
| Further experiments and simulation studies
| ...
| Needs editing
| 0.5D
|-
! 8.
| Conclusions and synopsis
| ...
| Needs writing
| 1D
|}

==PhD thesis research plan==

* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-07-04T16:50:11Z

Stheotok:

==Publications Plan==
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

==Non-thesis-related personal plans==
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.

==PhD thesis table of contents==

{| border="1"
! No !! Section !! Comments !! Status !! Target
|-
! 1.
| Introduction
| ...
|
|
|-
! 1.1.
| Overview of my research and motivation
| Use Ptrim S1
|
|
|-
! 1.2.
| Main results and original contributions
| ...
|
|
|-
! 1.3.
| Organisation of thesis
| ...
|
|
|-
! 2.
| Theory and background
| ...
|
|
|-
! 2.1.
| Introduction – big picture
| ...
|
|
|-
! 2.2.
| P2P networks and architectures
| Based on ACM survey
| Almost ready, need some formatting
| 0.2D
|-
! 2.3.
| Transaction processing systems
|
|
|
|-
! 2.3.1
| Online Transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
| Almost ready, need some formatting
| 0.2D
|-
! 2.3.2
| Definitions and requirements analysis
|
| Almost ready, need some formatting
| 0.2D
|-
! 2.4.
| Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! 2.4.1.
| Social behaviour and incentives
|
| Almost ready, need some formatting
| 0.5D
|-
! 2.4.2.
| Trust and reputation
|
| Almost ready, need some formatting
| 0.5D
|-
! 2.4.3.
| Reputation management
|
| Almost ready, need some formatting
| 0.2D
|-
! 2.4.4.
| Distributed reputation management
|
| Almost ready, need some formatting
| 0.2D
|-
! 2.4.5.
| The MoR-Trust system
|
|
|0.5D
|-
! 2.5.
| Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|
|
|-
! 2.6.
| Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|
|
|-
! 3.
| Problem definition and proposed solution
| ...
|
|
|-
! 3.1.
| Definition of problem we want to attack: Managing P2P transaction risk
| Includes general and also specific goals
|
|
|-
! 3.2.
| Limits of research scope
| Things that are not our problem ( References to Section 7).
|
|
|-
! 3.3.
| Proposed solution: A Market based approach
| At an abstract level. Use patent literature for ideas.
|
|
|-
! 3.3.1.
| Relation to other approaches
| Complementary to reputation management, explain how the two could cooperate.
|
|
|-
! 3.3.2.
| Abstract description of proposed solution.
| Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
|
|
|-
! 4.
| Methodology
| ...
|
|
|-
! 4.1.
| Description of our overall approach
| We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
|
|
|-
! 4.2.
| Hypotheses
| What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
|
|
|-
! 4.3.
| Prototype system trials
| What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
|
|
|-
! 4.3.1.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc.
|
|
|-
! 4.3.2.
| Methodology for evaluation
| How will we evaluate the results.
|
|
|-
! 4.4.
| Composite experimental trials
| Use Ptrim S4.2. Which hypotheses do we address here.
|
|
|-
! 4.4.1.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
|
|
|-
! 4.4.2.
| Methodology for evaluation
| How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
|
|
|-
! 5.
| Design and implementation
| Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
|
|
|-
! 5.1.
| Design of Ptrim system
| ...
|
|
|-
! 5.2.
| Ptrim implementation details
| How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
|
|
|-
! 5.3.
| Composite experiment setup
|
|
|
|-
! 5.3.1
| Implementation
| How we implemented this: Perl/CGI/MySQL etc.
|
|
|-
! 5.3.2.
| Data crawling
| How we did this
|
|
|-
! 6.
| Results, evaluation and discussion
| ...
|
|
|-
! 6.1.
| Evaluation of prototype trial outcomes
| Use Ptrim S5.1. Refer to hypotheses
|
|
|-
! 6.2.
| Evaluation of composite trial outcomes
| Use Ptrim S5.2. Refer to hypotheses
|
|
|-
! 6.3.
| Discussion of overall findings and implications for our approach
| ...
|
|
|-
! 7.
| Future work
| Mention these also in Section 3.b.
|
|
|-
! 7.1.
| Security
| ...
|
|
|-
! 7.2.
| Collusion detection
| ...
|
|
|-
! 7.3.
| Insuring insurance transactions
| ...
|
|
|-
! 7.4.
| Further experiments and simulation studies
| ...
|
|
|-
! 8.
| Conclusions and synopsis
| ...
|
|
|}

==PhD thesis research plan==

* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-07-04T16:48:03Z

Stheotok:

==Publications Plan==
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

==Non-thesis-related personal plans==
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.

==PhD thesis table of contents==

{| border="1"
! No !! Section !! Comments !! Status !! Target
|-
! 1.
| Introduction
| ...
|
|
|-
! 1.1.
| Overview of my research and motivation
| Use Ptrim S1
|
|
|-
! 1.2.
| Main results and original contributions
| ...
|
|
|-
! 1.3.
| Organisation of thesis
| ...
|
|
|-
! 2.
| Theory and background
| ...
|
|
|-
! 2.1.
| Introduction – big picture
| ...
|
|
|-
! 2.2.
| P2P networks and architectures
| Based on ACM survey
| Almost ready, need some formatting
| 1D
|-
! 2.3.
| Transaction processing systems
|
|
|
|-
! 2.3.1
| Online Transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
| Almost ready, need some formatting
| 1D
|-
! 2.3.2
| Definitions and requirements analysis
|
| Almost ready, need some formatting
| 1D
|-
! 2.4.
| Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! 2.4.1.
| Social behaviour and incentives
|
| Almost ready, need some formatting
| 1DXXX
|-
! 2.4.2.
| Trust and reputation
|
| Almost ready, need some formatting
| 1DXXX
|-
! 2.4.3.
| Reputation management
|
| Almost ready, need some formatting
| 0.2D
|-
! 2.4.4.
| Distributed reputation management
|
| Almost ready, need some formatting
| 0.2D
|-
! 2.4.5.
| The MoR-Trust system
|
|
|
|-
! 2.5.
| Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|
|
|-
! 2.6.
| Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|
|
|-
! 3.
| Problem definition and proposed solution
| ...
|
|
|-
! 3.1.
| Definition of problem we want to attack: Managing P2P transaction risk
| Includes general and also specific goals
|
|
|-
! 3.2.
| Limits of research scope
| Things that are not our problem ( References to Section 7).
|
|
|-
! 3.3.
| Proposed solution: A Market based approach
| At an abstract level. Use patent literature for ideas.
|
|
|-
! 3.3.1.
| Relation to other approaches
| Complementary to reputation management, explain how the two could cooperate.
|
|
|-
! 3.3.2.
| Abstract description of proposed solution.
| Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
|
|
|-
! 4.
| Methodology
| ...
|
|
|-
! 4.1.
| Description of our overall approach
| We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
|
|
|-
! 4.2.
| Hypotheses
| What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
|
|
|-
! 4.3.
| Prototype system trials
| What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
|
|
|-
! 4.3.1.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc.
|
|
|-
! 4.3.2.
| Methodology for evaluation
| How will we evaluate the results.
|
|
|-
! 4.4.
| Composite experimental trials
| Use Ptrim S4.2. Which hypotheses do we address here.
|
|
|-
! 4.4.1.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
|
|
|-
! 4.4.2.
| Methodology for evaluation
| How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
|
|
|-
! 5.
| Design and implementation
| Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
|
|
|-
! 5.1.
| Design of Ptrim system
| ...
|
|
|-
! 5.2.
| Ptrim implementation details
| How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
|
|
|-
! 5.3.
| Composite experiment setup
|
|
|
|-
! 5.3.1
| Implementation
| How we implemented this: Perl/CGI/MySQL etc.
|
|
|-
! 5.3.2.
| Data crawling
| How we did this
|
|
|-
! 6.
| Results, evaluation and discussion
| ...
|
|
|-
! 6.1.
| Evaluation of prototype trial outcomes
| Use Ptrim S5.1. Refer to hypotheses
|
|
|-
! 6.2.
| Evaluation of composite trial outcomes
| Use Ptrim S5.2. Refer to hypotheses
|
|
|-
! 6.3.
| Discussion of overall findings and implications for our approach
| ...
|
|
|-
! 7.
| Future work
| Mention these also in Section 3.b.
|
|
|-
! 7.1.
| Security
| ...
|
|
|-
! 7.2.
| Collusion detection
| ...
|
|
|-
! 7.3.
| Insuring insurance transactions
| ...
|
|
|-
! 7.4.
| Further experiments and simulation studies
| ...
|
|
|-
! 8.
| Conclusions and synopsis
| ...
|
|
|}

==PhD thesis research plan==

* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-07-04T16:42:00Z

Stheotok:

==Publications Plan==
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

==Non-thesis-related personal plans==
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.

==PhD thesis table of contents==

{| border="1"
! No !! Section !! Comments !! Status !! Target
|-
! 1.
| Introduction
| ...
|
|
|-
! 1.1.
| Overview of my research and motivation
| Use Ptrim S1
|
|
|-
! 1.2.
| Main results and original contributions
| ...
|
|
|-
! 1.3.
| Organisation of thesis
| ...
|
|
|-
! 2.
| Theory and background
| ...
|
|
|-
! 2.1.
| Introduction – big picture
| ...
|
|
|-
! 2.2.
| P2P networks and architectures
| Based on ACM survey
| Almost ready, need some formatting
| 1D
|-
! 2.3.
| Transaction processing systems
|
|
|
|-
! 2.3.1
| Online Transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
| Almost ready, need some formatting
| 1D
|-
! 2.3.2
| Definitions and requirements analysis
|
| Almost ready, need some formatting
| 1D
|-
! 2.4.
| Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! 2.4.1.
| Social behaviour and incentives
|
| Almost ready, need some formatting
| 1DXXX
|-
! 2.4.2.
| Trust and reputation
|
| Almost ready, need some formatting
| 1DXXX
|-
! 2.4.3.
| Reputation management
|
| Almost ready, need some formatting
| 1DXXX
|-
! 2.4.4.
| Distributed reputation management
|
| Almost ready, need some formatting
| 0.2D
|-
! 2.4.5.
| The MoR-Trust system
|
|
|
|-
! 2.5.
| Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|
|
|-
! 2.6.
| Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|
|
|-
! 3.
| Problem definition and proposed solution
| ...
|
|
|-
! 3.1.
| Definition of problem we want to attack: Managing P2P transaction risk
| Includes general and also specific goals
|
|
|-
! 3.2.
| Limits of research scope
| Things that are not our problem ( References to Section 7).
|
|
|-
! 3.3.
| Proposed solution: A Market based approach
| At an abstract level. Use patent literature for ideas.
|
|
|-
! 3.3.1.
| Relation to other approaches
| Complementary to reputation management, explain how the two could cooperate.
|
|
|-
! 3.3.2.
| Abstract description of proposed solution.
| Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
|
|
|-
! 4.
| Methodology
| ...
|
|
|-
! 4.1.
| Description of our overall approach
| We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
|
|
|-
! 4.2.
| Hypotheses
| What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
|
|
|-
! 4.3.
| Prototype system trials
| What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
|
|
|-
! 4.3.1.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc.
|
|
|-
! 4.3.2.
| Methodology for evaluation
| How will we evaluate the results.
|
|
|-
! 4.4.
| Composite experimental trials
| Use Ptrim S4.2. Which hypotheses do we address here.
|
|
|-
! 4.4.1.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
|
|
|-
! 4.4.2.
| Methodology for evaluation
| How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
|
|
|-
! 5.
| Design and implementation
| Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
|
|
|-
! 5.1.
| Design of Ptrim system
| ...
|
|
|-
! 5.2.
| Ptrim implementation details
| How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
|
|
|-
! 5.3.
| Composite experiment setup
|
|
|
|-
! 5.3.1
| Implementation
| How we implemented this: Perl/CGI/MySQL etc.
|
|
|-
! 5.3.2.
| Data crawling
| How we did this
|
|
|-
! 6.
| Results, evaluation and discussion
| ...
|
|
|-
! 6.1.
| Evaluation of prototype trial outcomes
| Use Ptrim S5.1. Refer to hypotheses
|
|
|-
! 6.2.
| Evaluation of composite trial outcomes
| Use Ptrim S5.2. Refer to hypotheses
|
|
|-
! 6.3.
| Discussion of overall findings and implications for our approach
| ...
|
|
|-
! 7.
| Future work
| Mention these also in Section 3.b.
|
|
|-
! 7.1.
| Security
| ...
|
|
|-
! 7.2.
| Collusion detection
| ...
|
|
|-
! 7.3.
| Insuring insurance transactions
| ...
|
|
|-
! 7.4.
| Further experiments and simulation studies
| ...
|
|
|-
! 8.
| Conclusions and synopsis
| ...
|
|
|}

==PhD thesis research plan==

* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-07-04T12:18:51Z

Stheotok:

==Publications Plan==
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

==Non-thesis-related personal plans==
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

==PhD thesis table of contents==

{| border="1"
! No !! Section !! Comments !! Status !! Target
|-
! 1.
| Introduction
| ...
|
|
|-
! 1.1.
| Overview of my research and motivation
| Use Ptrim S1
|
|
|-
! 1.2.
| Main results and original contributions
| ...
|
|
|-
! 1.3.
| Organisation of thesis
| ...
|
|
|-
! 2.
| Theory and background
| ...
|
|
|-
! 2.1.
| Introduction – big picture
| ...
|
|
|-
! 2.2.
| P2P networks and architectures
| Based on ACM survey
| Almost ready, need some formatting
| 1D
|-
! 2.3.
| Transaction processing systems
|
|
|
|-
! 2.3.1
| Online Transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
| Almost ready, need some formatting
| 1D
|-
! 2.3.2
| Definitions and requirements analysis
|
| Almost ready, need some formatting
| 1D
|-
! 2.4.
| Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! 2.4.1.
| Social behaviour and incentives
|
| Almost ready, need some formatting
| 1D
|-
! 2.4.2.
| Trust and reputation
|
| Almost ready, need some formatting
| 1D
|-
! 2.4.3.
| Reputation management
|
| Almost ready, need some formatting
| 1D
|-
! 2.4.4.
| Distributed reputation management
|
| Almost ready, need some formatting
| 1D
|-
! 2.4.5.
| The MoR-Trust system
|
|
|
|-
! 2.5.
| Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|
|
|-
! 2.6.
| Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|
|
|-
! 3.
| Problem definition and proposed solution
| ...
|
|
|-
! 3.1.
| Definition of problem we want to attack: Managing P2P transaction risk
| Includes general and also specific goals
|
|
|-
! 3.2.
| Limits of research scope
| Things that are not our problem ( References to Section 7).
|
|
|-
! 3.3.
| Proposed solution: A Market based approach
| At an abstract level. Use patent literature for ideas.
|
|
|-
! 3.3.1.
| Relation to other approaches
| Complementary to reputation management, explain how the two could cooperate.
|
|
|-
! 3.3.2.
| Abstract description of proposed solution.
| Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
|
|
|-
! 4.
| Methodology
| ...
|
|
|-
! 4.1.
| Description of our overall approach
| We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
|
|
|-
! 4.2.
| Hypotheses
| What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
|
|
|-
! 4.3.
| Prototype system trials
| What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
|
|
|-
! 4.3.1.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc.
|
|
|-
! 4.3.2.
| Methodology for evaluation
| How will we evaluate the results.
|
|
|-
! 4.4.
| Composite experimental trials
| Use Ptrim S4.2. Which hypotheses do we address here.
|
|
|-
! 4.4.1.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
|
|
|-
! 4.4.2.
| Methodology for evaluation
| How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
|
|
|-
! 5.
| Design and implementation
| Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
|
|
|-
! 5.1.
| Design of Ptrim system
| ...
|
|
|-
! 5.2.
| Ptrim implementation details
| How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
|
|
|-
! 5.3.
| Composite experiment setup
|
|
|
|-
! 5.3.1
| Implementation
| How we implemented this: Perl/CGI/MySQL etc.
|
|
|-
! 5.3.2.
| Data crawling
| How we did this
|
|
|-
! 6.
| Results, evaluation and discussion
| ...
|
|
|-
! 6.1.
| Evaluation of prototype trial outcomes
| Use Ptrim S5.1. Refer to hypotheses
|
|
|-
! 6.2.
| Evaluation of composite trial outcomes
| Use Ptrim S5.2. Refer to hypotheses
|
|
|-
! 6.3.
| Discussion of overall findings and implications for our approach
| ...
|
|
|-
! 7.
| Future work
| Mention these also in Section 3.b.
|
|
|-
! 7.1.
| Security
| ...
|
|
|-
! 7.2.
| Collusion detection
| ...
|
|
|-
! 7.3.
| Insuring insurance transactions
| ...
|
|
|-
! 7.4.
| Further experiments and simulation studies
| ...
|
|
|-
! 8.
| Conclusions and synopsis
| ...
|
|
|}

==PhD thesis research plan==

* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-30T13:14:40Z

Stheotok:

==Publications Plan==
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

==Non-thesis-related personal plans==
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

==PhD thesis table of contents==

{| border="1"
! No !! Section !! Comments !! Status !! Target
|-
! 1.
| Introduction
| ...
|
|
|-
! 1.1.
| Overview of my research and motivation
| Use Ptrim S1
|
|
|-
! 1.2.
| Main results and original contributions
| ...
|
|
|-
! 1.3.
| Organisation of thesis
| ...
|
|
|-
! 2.
| Theory and background
| ...
|
|
|-
! 2.1.
| Introduction – big picture
| ...
|
|
|-
! 2.2.
| P2P networks and architectures
| Based on ACM survey
| Almost ready, need some formatting
| 1D
|-
! 2.3.
| Transaction processing systems
|
|
|
|-
! 2.3.1
| Online Transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
| Almost ready, need some formatting
| 1D
|-
! 2.3.2
| Definitions and requirements analysis
|
| Almost ready, need some formatting
| 1D
|-
! 2.4.
| Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! 2.5.
| Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|
|
|-
! 2.6.
| Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|
|
|-
! 3.
| Problem definition and proposed solution
| ...
|
|
|-
! 3.1.
| Definition of problem we want to attack: Managing P2P transaction risk
| Includes general and also specific goals
|
|
|-
! 3.2.
| Limits of research scope
| Things that are not our problem ( References to Section 7).
|
|
|-
! 3.3.
| Proposed solution: A Market based approach
| At an abstract level. Use patent literature for ideas.
|
|
|-
! 3.3.1.
| Relation to other approaches
| Complementary to reputation management, explain how the two could cooperate.
|
|
|-
! 3.3.2.
| Abstract description of proposed solution.
| Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
|
|
|-
! 4.
| Methodology
| ...
|
|
|-
! 4.1.
| Description of our overall approach
| We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
|
|
|-
! 4.2.
| Hypotheses
| What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
|
|
|-
! 4.3.
| Prototype system trials
| What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
|
|
|-
! 4.3.1.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc.
|
|
|-
! 4.3.2.
| Methodology for evaluation
| How will we evaluate the results.
|
|
|-
! 4.4.
| Composite experimental trials
| Use Ptrim S4.2. Which hypotheses do we address here.
|
|
|-
! 4.4.1.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
|
|
|-
! 4.4.2.
| Methodology for evaluation
| How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
|
|
|-
! 5.
| Design and implementation
| Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
|
|
|-
! 5.1.
| Design of Ptrim system
| ...
|
|
|-
! 5.2.
| Ptrim implementation details
| How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
|
|
|-
! 5.3.
| Composite experiment setup
|
|
|
|-
! 5.3.1
| Implementation
| How we implemented this: Perl/CGI/MySQL etc.
|
|
|-
! 5.3.2.
| Data crawling
| How we did this
|
|
|-
! 6.
| Results, evaluation and discussion
| ...
|
|
|-
! 6.1.
| Evaluation of prototype trial outcomes
| Use Ptrim S5.1. Refer to hypotheses
|
|
|-
! 6.2.
| Evaluation of composite trial outcomes
| Use Ptrim S5.2. Refer to hypotheses
|
|
|-
! 6.3.
| Discussion of overall findings and implications for our approach
| ...
|
|
|-
! 7.
| Future work
| Mention these also in Section 3.b.
|
|
|-
! 7.1.
| Security
| ...
|
|
|-
! 7.2.
| Collusion detection
| ...
|
|
|-
! 7.3.
| Insuring insurance transactions
| ...
|
|
|-
! 7.4.
| Further experiments and simulation studies
| ...
|
|
|-
! 8.
| Conclusions and synopsis
| ...
|
|
|}

==PhD thesis research plan==

* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-30T10:44:25Z

Stheotok:

==Publications Plan==
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

==Non-thesis-related personal plans==
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

==PhD thesis table of contents==

{| border="1"
! No !! Section !! Comments !! Status !! Target
|-
! 1.
| Introduction
| ...
|
|
|-
! 1.a.
| Overview of my research and motivation
| Use Ptrim S1
|
|
|-
! 1.b.
| Main results and original contributions
| ...
|
|
|-
! 1.c.
| Organisation of thesis
| ...
|
|
|-
! 2.
| Theory and background
| ...
|
|
|-
! 2.a.
| Introduction – big picture
| ...
|
|
|-
! 2.b.
| P2P networks and architectures
| Based on ACM survey
| Almost ready, need some formatting
| 1D
|-
! 2.c.
| Distributed transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
|
|
|-
! 2.d.
| Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! 2.e.
| Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|
|
|-
! 2.f.
| Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|
|
|-
! 3.
| Problem definition and proposed solution
| ...
|
|
|-
! 3.a.
| Definition of problem we want to attack: Managing P2P transaction risk
| Includes general and also specific goals
|
|
|-
! 3.b.
| Limits of research scope
| Things that are not our problem ( References to Section 7).
|
|
|-
! 3.c.
| Proposed solution: A Market based approach
| At an abstract level. Use patent literature for ideas.
|
|
|-
! 3.c.i.
| Relation to other approaches
| Complementary to reputation management, explain how the two could cooperate.
|
|
|-
! 3.c.ii.
| Abstract description of proposed solution.
| Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
|
|
|-
! 4.
| Methodology
| ...
|
|
|-
! 4.a.
| How we chose this particular approach
| With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
|
|
|-
! 4.b.
| Description of our overall approach
| We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
|
|
|-
! 4.c.
| Hypotheses
| What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
|
|
|-
! 4.d.
| Prototype system trials
| What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
|
|
|-
! 4.d.i.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc.
|
|
|-
! 4.d.ii.
| Methodology for evaluation
| How will we evaluate the results.
|
|
|-
! 4.e.
| Composite experimental trials
| Use Ptrim S4.2. Which hypotheses do we address here.
|
|
|-
! 4.e.i.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
|
|
|-
! 4.e.ii.
| Transaction data
| Where we found the data and what we did with it
|
|
|-
! 4.e.iii.
| Methodology for evaluation
| How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
|
|
|-
! 5.
| Design and implementation
| Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
|
|
|-
! 5.a.
| Design of Ptrim system
| ...
|
|
|-
! 5.b.
| Ptrim implementation details
| How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
|
|
|-
! 5.c.
| Composite experiment setup
| How we implemented this: Perl/CGI/MySQL etc.
|
|
|-
! 5.d.
| Data crawling
| How we did this
|
|
|-
! 6.
| Results, evaluation and discussion
| ...
|
|
|-
! 6.a.
| Evaluation of prototype trial outcomes
| Use Ptrim S5.1. Refer to hypotheses
|
|
|-
! 6.b.
| Evaluation of composite trial outcomes
| Use Ptrim S5.2. Refer to hypotheses
|
|
|-
! 6.c.
| Discussion of overall findings and implications for our approach
| ...
|
|
|-
! 7.
| Future work
| Mention these also in Section 3.b.
|
|
|-
! 7.a.
| Security
| ...
|
|
|-
! 7.b.
| Collusion detection
| ...
|
|
|-
! 7.c.
| Insuring insurance transactions
| ...
|
|
|-
! 7.d.
| Further experiments and simulation studies
| ...
|
|
|-
! 8.
| Conclusions and synopsis
| ...
|
|
|}

==PhD thesis research plan==

* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

SENSE equipment wishlist

2008-06-18T15:35:09Z

Stheotok:

== Equipment ==
* Large format (A0 or A1) printer/plotter for plotting posters and large UML diagrams
** HP DesignJet 130 (A1 - €2000) [http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/18972-18972-3328061-12600-3328079-352387-352389-352390.html (C7791D) 130nr]
* [http://www.batteries.gr/product_info.php?products_id=1262&language=en Universal laptop battery] [http://www.plaisio.gr/product.aspx?catalog=21&category=69981044&product=1104748 Plaisio]
* [http://www.plaisio.gr/product.aspx?catalog=21&category=69977947&product=772003 Notebook PSU]
* [http://www.plaisio.gr/product.aspx?catalog=21&category=69977947&product=911240 Power adapter] or [http://www.plaisio.gr/product.aspx?catalog=21&category=69977947&product=915114]

== Supplies ==
* 5 [http://www.plaisio.gr/product.aspx?catalog=24&category=69978657&product=65145 Magazine boxes] - dds
* 2 [http://www.plaisio.gr/product.aspx?catalog=24&category=69978647&product=200948 Archive storage boxes] - dds
* 1 [http://www.plaisio.gr/product.aspx?catalog=24&category=69978379&product=535702 HP 12A cartridge] (1022) - dds
* 1 [http://www.plaisio.gr/product.aspx?catalog=24&category=69978379&product=236845 HP 4096A cartridge] (2100) - dds
* 1 [http://www.plaisio.gr/product.aspx?catalog=24&category=69978379&product=236845 HP 35A cartridge] (1005) - gousiosg
* 2 [http://www.plaisio.gr/product.aspx?catalog=20&category=69977741&product=1043056 500GB hard disks] - ikaria
* 2 [http://www.plaisio.gr/product.aspx?catalog=24&category=100&product=791733 HP 45+78 cartridge set] - stephanos
* 1 [http://www.plaisio.gr/product.aspx?catalog=23&category=69978202&product=1116819 Transcend 16GB USB stick] - stephanos (only if it can be justified in the budjet, if not don't worry about it)

[[Category:Equipment]]
[[Category:Equipment SENSE]]
[[Category:SENSE]]

SENSE equipment wishlist

2008-06-18T15:29:22Z

Stheotok:

== Equipment ==
* Large format (A0 or A1) printer/plotter for plotting posters and large UML diagrams
** HP DesignJet 130 (A1 - €2000) [http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/18972-18972-3328061-12600-3328079-352387-352389-352390.html (C7791D) 130nr]
* [http://www.batteries.gr/product_info.php?products_id=1262&language=en Universal laptop battery] [http://www.plaisio.gr/product.aspx?catalog=21&category=69981044&product=1104748 Plaisio]
* [http://www.plaisio.gr/product.aspx?catalog=21&category=69977947&product=772003 Notebook PSU]
* [http://www.plaisio.gr/product.aspx?catalog=21&category=69977947&product=911240 Power adapter] or [http://www.plaisio.gr/product.aspx?catalog=21&category=69977947&product=915114]

== Supplies ==
* 5 [http://www.plaisio.gr/product.aspx?catalog=24&category=69978657&product=65145 Magazine boxes] - dds
* 2 [http://www.plaisio.gr/product.aspx?catalog=24&category=69978647&product=200948 Archive storage boxes] - dds
* 1 [http://www.plaisio.gr/product.aspx?catalog=24&category=69978379&product=535702 HP 12A cartridge] (1022) - dds
* 1 [http://www.plaisio.gr/product.aspx?catalog=24&category=69978379&product=236845 HP 4096A cartridge] (2100) - dds
* 1 [http://www.plaisio.gr/product.aspx?catalog=24&category=69978379&product=236845 HP 35A cartridge] (1005) - gousiosg
* 2 [http://www.plaisio.gr/product.aspx?catalog=20&category=69977741&product=1043056 500GB hard disks] - ikaria
* 2 [http://www.plaisio.gr/product.aspx?catalog=24&category=100&product=791733 HP 45+78 cartridge set] - stephanos

[[Category:Equipment]]
[[Category:Equipment SENSE]]
[[Category:SENSE]]

Stephanos Androutsellis PhD research plan

2008-06-03T23:28:50Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:

{| border="1"
! No !! Section !! Comments !! Status !! Target
|-
! 1.
| Introduction
| ...
|
|
|-
! 1.a.
| Overview of my research and motivation
| Use Ptrim S1
|
|
|-
! 1.b.
| Main results and original contributions
| ...
|
|
|-
! 1.c.
| Organisation of thesis
| ...
|
|
|-
! 2.
| Theory and background
| ...
|
|
|-
! 2.a.
| Introduction – big picture
| ...
|
|
|-
! 2.b.
| P2P networks and architectures
| Based on ACM survey
|
|
|-
! 2.c.
| Distributed transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
|
|
|-
! 2.d.
| Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! 2.e.
| Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|
|
|-
! 2.f.
| Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|
|
|-
! 3.
| Problem definition and proposed solution
| ...
|
|
|-
! 3.a.
| Definition of problem we want to attack: Managing P2P transaction risk
| Includes general and also specific goals
|
|
|-
! 3.b.
| Limits of research scope
| Things that are not our problem ( References to Section 7).
|
|
|-
! 3.c.
| Proposed solution: A Market based approach
| At an abstract level. Use patent literature for ideas.
|
|
|-
! 3.c.i.
| Relation to other approaches
| Complementary to reputation management, explain how the two could cooperate.
|
|
|-
! 3.c.ii.
| Abstract description of proposed solution.
| Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
|
|
|-
! 4.
| Methodology
| ...
|
|
|-
! 4.a.
| How we chose this particular approach
| With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
|
|
|-
! 4.b.
| Description of our overall approach
| We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
|
|
|-
! 4.c.
| Hypotheses
| What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
|
|
|-
! 4.d.
| Prototype system trials
| What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
|
|
|-
! 4.d.i.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc.
|
|
|-
! 4.d.ii.
| Methodology for evaluation
| How will we evaluate the results.
|
|
|-
! 4.e.
| Composite experimental trials
| Use Ptrim S4.2. Which hypotheses do we address here.
|
|
|-
! 4.e.i.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
|
|
|-
! 4.e.ii.
| Transaction data
| Where we found the data and what we did with it
|
|
|-
! 4.e.iii.
| Methodology for evaluation
| How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
|
|
|-
! 5.
| Design and implementation
| Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
|
|
|-
! 5.a.
| Design of Ptrim system
| ...
|
|
|-
! 5.b.
| Ptrim implementation details
| How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
|
|
|-
! 5.c.
| Composite experiment setup
| How we implemented this: Perl/CGI/MySQL etc.
|
|
|-
! 5.d.
| Data crawling
| How we did this
|
|
|-
! 6.
| Results, evaluation and discussion
| ...
|
|
|-
! 6.a.
| Evaluation of prototype trial outcomes
| Use Ptrim S5.1. Refer to hypotheses
|
|
|-
! 6.b.
| Evaluation of composite trial outcomes
| Use Ptrim S5.2. Refer to hypotheses
|
|
|-
! 6.c.
| Discussion of overall findings and implications for our approach
| ...
|
|
|-
! 7.
| Future work
| Mention these also in Section 3.b.
|
|
|-
! 7.a.
| Security
| ...
|
|
|-
! 7.b.
| Collusion detection
| ...
|
|
|-
! 7.c.
| Insuring insurance transactions
| ...
|
|
|-
! 7.d.
| Further experiments and simulation studies
| ...
|
|
|-
! 8.
| Conclusions and synopsis
| ...
|
|
|}

PhD thesis research plan:

* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T23:27:27Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:

{| border="1"
! No !! Section !! Comments !! Status !! Target
|-
! 1.
| Introduction
|
|
|
|-
! 1.a.
| Overview of my research and motivation
| Use Ptrim S1
|
|
|-
! 1.b.
| Main results and original contributions
|
|
|
|-
! 1.c.
| Organisation of thesis
|
|
|
|-
! 2.
| Theory and background
|
|
|
|-
! 2.a.
| Introduction – big picture
|
|
|
|-
! 2.b.
| P2P networks and architectures
| Based on ACM survey
|
|
|-
! 2.c.
| Distributed transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
|
|
|-
! 2.d.
| Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! 2.e.
| Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|
|
|-
! 2.f.
| Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|
|
|-
! 3.
| Problem definition and proposed solution
|
|
|
|-
! 3.a.
| Definition of problem we want to attack: Managing P2P transaction risk
| Includes general and also specific goals
|
|
|-
! 3.b.
| Limits of research scope
| Things that are not our problem ( References to Section 7).
|
|
|-
! 3.c.
| Proposed solution: A Market based approach
| At an abstract level. Use patent literature for ideas.
|
|
|-
! 3.c.i.
| Relation to other approaches
| Complementary to reputation management, explain how the two could cooperate.
|
|
|-
! 3.c.ii.
| Abstract description of proposed solution.
| Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
|
|
|-
! 4.
| Methodology
| ...
|
|
|-
! 4.a.
| How we chose this particular approach
| With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
|
|
|-
! 4.b.
| Description of our overall approach
| We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
|
|
|-
! 4.c.
| Hypotheses
| What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
|
|
|-
! 4.d.
| Prototype system trials
| What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
|
|
|-
! 4.d.i.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc.
|
|
|-
! 4.d.ii.
| Methodology for evaluation
| How will we evaluate the results.
|
|
|-
! 4.e.
| Composite experimental trials
| Use Ptrim S4.2. Which hypotheses do we address here.
|
|
|-
! 4.e.i.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
|
|
|-
! 4.e.ii.
| Transaction data
| Where we found the data and what we did with it
|
|
|-
! 4.e.iii.
| Methodology for evaluation
| How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
|
|
|-
! 5.
| Design and implementation
| Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
|
|
|-
! 5.a.
| Design of Ptrim system
| ...
|
|
|-
! 5.b.
| Ptrim implementation details
| How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
|
|
|-
! 5.c.
| Composite experiment setup
| How we implemented this: Perl/CGI/MySQL etc.
|
|
|-
! 5.d.
| Data crawling
| How we did this
|
|
|-
! 6.
| Results, evaluation and discussion
| ...
|
|
|-
! 6.a.
| Evaluation of prototype trial outcomes
| Use Ptrim S5.1. Refer to hypotheses
|
|
|-
! 6.b.
| Evaluation of composite trial outcomes
| Use Ptrim S5.2. Refer to hypotheses
|
|
|-
! 6.c.
| Discussion of overall findings and implications for our approach
| ...
|
|
|-
! 7.
| Future work
| Mention these also in Section 3.b.
|
|
|-
! 7.a.
| Security
| ...
|
|
|-
! 7.b.
| Collusion detection
| ...
|
|
|-
! 7.c.
| Insuring insurance transactions
| ...
|
|
|-
! 7.d.
| Further experiments and simulation studies
| ...
|
|
|-
! 8.
| Conclusions and synopsis
| ...
|
|
|}

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T23:25:56Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:

{| border="1"
! No !! Section !! Comments !! Status !! Target
|-
! 1.
| Introduction
|
|
|
|-
! 1.a.
| Overview of my research and motivation
| Use Ptrim S1
|
|
|-
! 1.b.
| Main results and original contributions
|
|
|
|-
! 1.c.
| Organisation of thesis
|
|
|
|-
! 2.
| Theory and background
|
|
|
|-
! 2.a.
| Introduction – big picture
|
|
|
|-
! 2.b.
| P2P networks and architectures
| Based on ACM survey
|
|
|-
! 2.c.
| Distributed transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
|
|
|-
! 2.d.
| Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! 2.e.
| Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|
|
|-
! 2.f.
| Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|
|
|-
! 3.
| Problem definition and proposed solution
|
|
|
| -
! 3.a.
| Definition of problem we want to attack: Managing P2P transaction risk
| Includes general and also specific goals
|
|
| -
! 3.b.
| Limits of research scope
| Things that are not our problem ( References to Section 7).
|
|
| -
! 3.c.
| Proposed solution: A Market based approach
| At an abstract level. Use patent literature for ideas.
|
|
| -
! 3.c.i.
| Relation to other approaches
| Complementary to reputation management, explain how the two could cooperate.
|
|
| -
! 3.c.ii.
| Abstract description of proposed solution.
| Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
|
|
| -
! 4.
| Methodology
| ...
|
|
| -
! 4.a.
| How we chose this particular approach
| With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
|
|
| -
! 4.b.
| Description of our overall approach
| We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
|
|
| -
! 4.c.
| Hypotheses
| What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
|
|
| -
! 4.d.
| Prototype system trials
| What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
|
|
| -
! 4.d.i.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc.
|
|
| -
! 4.d.ii.
| Methodology for evaluation
| How will we evaluate the results.
|
|
| -
! 4.e.
| Composite experimental trials
| Use Ptrim S4.2. Which hypotheses do we address here.
|
|
| -
! 4.e.i.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
|
|
| -
! 4.e.ii.
| Transaction data
| Where we found the data and what we did with it
|
|
| -
! 4.e.iii.
| Methodology for evaluation
| How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
|
|
| -
! 5.
| Design and implementation
| Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
|
|
| -
! 5.a.
| Design of Ptrim system
| ...
|
|
| -
! 5.b.
| Ptrim implementation details
| How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
|
|
| -
! 5.c.
| Composite experiment setup
| How we implemented this: Perl/CGI/MySQL etc.
|
|
| -
! 5.d.
| Data crawling
| How we did this
|
|
| -
! 6.
| Results, evaluation and discussion
| ...
|
|
| -
! 6.a.
| Evaluation of prototype trial outcomes
| Use Ptrim S5.1. Refer to hypotheses
|
|
| -
! 6.b.
| Evaluation of composite trial outcomes
| Use Ptrim S5.2. Refer to hypotheses
|
|
| -
! 6.c.
| Discussion of overall findings and implications for our approach
| ...
|
|
| -
! 7.
| Future work
| Mention these also in Section 3.b.
|
|
| -
! 7.a.
| Security
| ...
|
|
| -
! 7.b.
| Collusion detection
| ...
|
|
| -
! 7.c.
| Insuring insurance transactions
| ...
|
|
| -
! 7.d.
| Further experiments and simulation studies
| ...
|
|
| -
! 8.
| Conclusions and synopsis
| ...
|
|
|}

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T23:24:53Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:

{| border="1"
! No !! Section !! Comments !! Status !! Target
|-
! 1.
| Introduction
|
|
|
|-
! 1.a.
| Overview of my research and motivation
| Use Ptrim S1
|
|
|-
! 1.b.
| Main results and original contributions
|
|
|
|-
! 1.c.
| Organisation of thesis
|
|
|
|-
! 2.
| Theory and background
|
|
|
|-
! 2.a.
| Introduction – big picture
|
|
|
|-
! 2.b.
| P2P networks and architectures
| Based on ACM survey
|
|
|-
! 2.c.
| Distributed transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
|
|
|-
! 2.d.
| Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! 2.e.
| Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|
|
|-
! 2.f.
| Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|
|
|-
! 3.
| Problem definition and proposed solution
|
|
| -
! 3.a.
| Definition of problem we want to attack: Managing P2P transaction risk
| Includes general and also specific goals
|
|
| -
! 3.b.
| Limits of research scope
| Things that are not our problem ( References to Section 7).
|
|
| -
! 3.c.
| Proposed solution: A Market based approach
| At an abstract level. Use patent literature for ideas.
|
|
| -
! 3.c.i.
| Relation to other approaches
| Complementary to reputation management, explain how the two could cooperate.
|
|
| -
! 3.c.ii.
| Abstract description of proposed solution.
| Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
|
|
| -
! 4.
| Methodology
| ...
|
|
| -
! 4.a.
| How we chose this particular approach
| With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
|
|
| -
! 4.b.
| Description of our overall approach
| We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
|
|
| -
! 4.c.
| Hypotheses
| What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
|
|
| -
! 4.d.
| Prototype system trials
| What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
|
|
| -
! 4.d.i.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc.
|
|
| -
! 4.d.ii.
| Methodology for evaluation
| How will we evaluate the results.
|
|
| -
! 4.e.
| Composite experimental trials
| Use Ptrim S4.2. Which hypotheses do we address here.
|
|
| -
! 4.e.i.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
|
|
| -
! 4.e.ii.
| Transaction data
| Where we found the data and what we did with it
|
|
| -
! 4.e.iii.
| Methodology for evaluation
| How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
|
|
| -
! 5.
| Design and implementation
| Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
|
|
| -
! 5.a.
| Design of Ptrim system
| ...
|
|
| -
! 5.b.
| Ptrim implementation details
| How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
|
|
| -
! 5.c.
| Composite experiment setup
| How we implemented this: Perl/CGI/MySQL etc.
|
|
| -
! 5.d.
| Data crawling
| How we did this
|
|
| -
! 6.
| Results, evaluation and discussion
| ...
|
|
| -
! 6.a.
| Evaluation of prototype trial outcomes
| Use Ptrim S5.1. Refer to hypotheses
|
|
| -
! 6.b.
| Evaluation of composite trial outcomes
| Use Ptrim S5.2. Refer to hypotheses
|
|
| -
! 6.c.
| Discussion of overall findings and implications for our approach
| ...
|
|
| -
! 7.
| Future work
| Mention these also in Section 3.b.
|
|
| -
! 7.a.
| Security
| ...
|
|
| -
! 7.b.
| Collusion detection
| ...
|
|
| -
! 7.c.
| Insuring insurance transactions
| ...
|
|
| -
! 7.d.
| Further experiments and simulation studies
| ...
|
|
| -
! 8.
| Conclusions and synopsis
| ...
|
|
|}

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T23:23:10Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:

{| border="1"
! No !! Section !! Comments !! Status !! Target
|-
! 1.
| Introduction
|
|
|
|-
! 1.a.
| Overview of my research and motivation
| Use Ptrim S1
|
|
|-
! 1.b.
| Main results and original contributions
|
|
|
|-
! 1.c.
| Organisation of thesis
|
|
|
|-
! 2.
| Theory and background
|
|
|
|-
! 2.a.
| Introduction – big picture
|
|
|
|-
! 2.b.
| P2P networks and architectures
| Based on ACM survey
|
|
|-
! 2.c.
| Distributed transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
|
|
|-
! 2.d.
| Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! 2.e.
| Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|
|
|-
! 2.f.
| Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|
|
! 3.
| Problem definition and proposed solution
|
|
|
! 3.a.
| Definition of problem we want to attack: Managing P2P transaction risk
| Includes general and also specific goals
|
|
! 3.b.
| Limits of research scope
| Things that are not our problem ( References to Section 7).
|
|
! 3.c.
| Proposed solution: A Market based approach
| At an abstract level. Use patent literature for ideas.
|
|
! 3.c.i.
| Relation to other approaches
| Complementary to reputation management, explain how the two could cooperate.
|
|
! 3.c.ii.
| Abstract description of proposed solution.
| Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
|
|
! 4.
| Methodology
| ...
|
|
! 4.a.
| How we chose this particular approach
| With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
|
|
! 4.b.
| Description of our overall approach
| We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
|
|
! 4.c.
| Hypotheses
| What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
|
|
! 4.d.
| Prototype system trials
| What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
|
|
! 4.d.i.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc.
|
|
! 4.d.ii.
| Methodology for evaluation
| How will we evaluate the results.
|
|
! 4.e.
| Composite experimental trials
| Use Ptrim S4.2. Which hypotheses do we address here.
|
|
! 4.e.i.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
|
|
! 4.e.ii.
| Transaction data
| Where we found the data and what we did with it
|
|
! 4.e.iii.
| Methodology for evaluation
| How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
|
|
! 5.
| Design and implementation
| Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
|
|
! 5.a.
| Design of Ptrim system
| ...
|
|
! 5.b.
| Ptrim implementation details
| How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
|
|
! 5.c.
| Composite experiment setup
| How we implemented this: Perl/CGI/MySQL etc.
|
|
! 5.d.
| Data crawling
| How we did this
|
|
! 6.
| Results, evaluation and discussion
| ...
|
|
! 6.a.
| Evaluation of prototype trial outcomes
| Use Ptrim S5.1. Refer to hypotheses
|
|
! 6.b.
| Evaluation of composite trial outcomes
| Use Ptrim S5.2. Refer to hypotheses
|
|
! 6.c.
| Discussion of overall findings and implications for our approach
| ...
|
|
! 7.
| Future work
| Mention these also in Section 3.b.
|
|
! 7.a.
| Security
| ...
|
|
! 7.b.
| Collusion detection
| ...
|
|
! 7.c.
| Insuring insurance transactions
| ...
|
|
! 7.d.
| Further experiments and simulation studies
| ...
|
|
! 8.
| Conclusions and synopsis
| ...
|
|
|
|
|}

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T23:22:38Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:

{| border="1"
! No !! Section !! Comments !! Status !! Target
|-
! 1.
| Introduction
|
|
|
|-
! 1.a.
| Overview of my research and motivation
| Use Ptrim S1
|
|
|-
! 1.b.
| Main results and original contributions
|
|
|
|-
! 1.c.
| Organisation of thesis
|
|
|
|-
! 2.
| Theory and background
|
|
|
|-
! 2.a.
| Introduction – big picture
|
|
|
|-
! 2.b.
| P2P networks and architectures
| Based on ACM survey
|
|
|-
! 2.c.
| Distributed transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
|
|
|-
! 2.d.
| Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! 2.e.
| Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|
|
|-
! 2.f.
| Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|
|
|}

! 3.
| Problem definition and proposed solution
|
|
|
! 3.a.
| Definition of problem we want to attack: Managing P2P transaction risk
| Includes general and also specific goals
|
|
! 3.b.
| Limits of research scope
| Things that are not our problem ( References to Section 7).
|
|
! 3.c.
| Proposed solution: A Market based approach
| At an abstract level. Use patent literature for ideas.
|
|
! 3.c.i.
| Relation to other approaches
| Complementary to reputation management, explain how the two could cooperate.
|
|
! 3.c.ii.
| Abstract description of proposed solution.
| Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
|
|
! 4.
| Methodology
| ...
|
|
! 4.a.
| How we chose this particular approach
| With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
|
|
! 4.b.
| Description of our overall approach
| We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
|
|
! 4.c.
| Hypotheses
| What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
|
|
! 4.d.
| Prototype system trials
| What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
|
|
! 4.d.i.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc.
|
|
! 4.d.ii.
| Methodology for evaluation
| How will we evaluate the results.
|
|
! 4.e.
| Composite experimental trials
| Use Ptrim S4.2. Which hypotheses do we address here.
|
|
! 4.e.i.
| Experimental setup
| How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
|
|
! 4.e.ii.
| Transaction data
| Where we found the data and what we did with it
|
|
! 4.e.iii.
| Methodology for evaluation
| How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
|
|
! 5.
| Design and implementation
| Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
|
|
! 5.a.
| Design of Ptrim system
| ...
|
|
! 5.b.
| Ptrim implementation details
| How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
|
|
! 5.c.
| Composite experiment setup
| How we implemented this: Perl/CGI/MySQL etc.
|
|
! 5.d.
| Data crawling
| How we did this
|
|
! 6.
| Results, evaluation and discussion
| ...
|
|
! 6.a.
| Evaluation of prototype trial outcomes
| Use Ptrim S5.1. Refer to hypotheses
|
|
! 6.b.
| Evaluation of composite trial outcomes
| Use Ptrim S5.2. Refer to hypotheses
|
|
! 6.c.
| Discussion of overall findings and implications for our approach
| ...
|
|
! 7.
| Future work
| Mention these also in Section 3.b.
|
|
! 7.a.
| Security
| ...
|
|
! 7.b.
| Collusion detection
| ...
|
|
! 7.c.
| Insuring insurance transactions
| ...
|
|
! 7.d.
| Further experiments and simulation studies
| ...
|
|
! 8.
| Conclusions and synopsis
| ...
|
|
|
|
|}

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T23:02:10Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:

{| border="1"
! No !! Section !! Comments !! Status !! Target
|-
! 1.
| Introduction
|
|
|
|-
! 1.a.
| Overview of my research and motivation (Use Ptrim S1)
|
|
|
|-
! 1.b.
| Main results and original contributions
|
|
|
|-
! 1.c.
| Organisation of thesis
|
|
|
|-
! 2.
| Theory and background
|
|
|
|-
! 2.a.
| Introduction – big picture
|
|
|
|-
! 2.b.
| P2P networks and architectures
| Based on ACM survey
|
|
|-
! 2.c.
| Distributed transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
|
|
|-
! 2.d.
| Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! 2.e.
| Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|
|
|-
! 2.f.
| Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|
|
|}

*3. Problem definition and proposed solution
**a. Definition of problem we want to attack: Managing P2P transaction risk
Includes general and also specific goals
**b. Limits of research scope
Things that are not our problem ( References to Section 7).
**c. Proposed solution: A Market based approach
At an abstract level. Use patent literature for ideas.
***i. Relation to other approaches
Complementary to reputation management, explain how the two could cooperate.
***ii. Abstract description of proposed solution.
Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
*4. Methodology
**a. How we chose this particular approach
With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
**b. Description of our overall approach
We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
**c. Hypotheses
What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
**d. Prototype system trials
What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc.
***ii. Methodology for evaluation
How will we evaluate the results.
**e. Composite experimental trials
Use Ptrim S4.2. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
***ii. Transaction data
Where we found the data and what we did with it
***iii. Methodology for evaluation
How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
*5. Design and implementation
Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
**a. Design of Ptrim system
**b. Ptrim implementation details
How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
**c. Composite experiment setup
How we implemented this: Perl/CGI/MySQL etc.
**d. Data crawling
How we did this
*6. Results, evaluation and discussion
**a. Evaluation of prototype trial outcomes
Use Ptrim S5.1. Refer to hypotheses
**b. Evaluation of composite trial outcomes
Use Ptrim S5.2. Refer to hypotheses
**c. Discussion of overall findings and implications for our approach
*7. Future work
Mention these also in Section 3.b.
**a. Security
**b. Collusion detection
**c. Insuring insurance transactions
**d. Further experiments and simulation studies
*8. Conclusions and synopsis

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T23:01:16Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:

{| border="1"
! No !! Section !! Comments !! Status !! Target
|-
! 1.
| Introduction
|
|
|
|-
! 1.a.|| Overview of my research and motivation (Use Ptrim S1)
|
|
|
|-
! 1.b.|| Main results and original contributions
|
|
|
|-
! 1.c.|| Organisation of thesis
|
|
|
|-
! 2.|| Theory and background
|
|
|
|-
! 2.a.|| Introduction – big picture
|
|
|
|-
! 2.b.|| P2P networks and architectures
| Based on ACM survey
|
|
|-
! 2.c.|| Distributed transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
|
|
|-
! 2.d.|| Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! 2.e.|| Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|
|
|-
! 2.f.|| Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|
|
|}

*3. Problem definition and proposed solution
**a. Definition of problem we want to attack: Managing P2P transaction risk
Includes general and also specific goals
**b. Limits of research scope
Things that are not our problem ( References to Section 7).
**c. Proposed solution: A Market based approach
At an abstract level. Use patent literature for ideas.
***i. Relation to other approaches
Complementary to reputation management, explain how the two could cooperate.
***ii. Abstract description of proposed solution.
Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
*4. Methodology
**a. How we chose this particular approach
With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
**b. Description of our overall approach
We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
**c. Hypotheses
What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
**d. Prototype system trials
What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc.
***ii. Methodology for evaluation
How will we evaluate the results.
**e. Composite experimental trials
Use Ptrim S4.2. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
***ii. Transaction data
Where we found the data and what we did with it
***iii. Methodology for evaluation
How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
*5. Design and implementation
Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
**a. Design of Ptrim system
**b. Ptrim implementation details
How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
**c. Composite experiment setup
How we implemented this: Perl/CGI/MySQL etc.
**d. Data crawling
How we did this
*6. Results, evaluation and discussion
**a. Evaluation of prototype trial outcomes
Use Ptrim S5.1. Refer to hypotheses
**b. Evaluation of composite trial outcomes
Use Ptrim S5.2. Refer to hypotheses
**c. Discussion of overall findings and implications for our approach
*7. Future work
Mention these also in Section 3.b.
**a. Security
**b. Collusion detection
**c. Insuring insurance transactions
**d. Further experiments and simulation studies
*8. Conclusions and synopsis

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T23:00:33Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:

{| border="1"
! No !! Section !! Comments !! Status !! Target
|-
! 1.|| Introduction
|
|
|
|-
! 1.a.|| Overview of my research and motivation (Use Ptrim S1)
|
|
|
|-
! 1.b.|| Main results and original contributions
|
|
|
|-
! 1.c.|| Organisation of thesis
|
|
|
|-
! 2.|| Theory and background
|
|
|
|-
! 2.a.|| Introduction – big picture
|
|
|
|-
! 2.b.|| P2P networks and architectures
| Based on ACM survey
|
|
|-
! 2.c.|| Distributed transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
|
|
|-
! 2.d.|| Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! 2.e.|| Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|
|
|-
! 2.f.|| Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|
|
|}

*3. Problem definition and proposed solution
**a. Definition of problem we want to attack: Managing P2P transaction risk
Includes general and also specific goals
**b. Limits of research scope
Things that are not our problem ( References to Section 7).
**c. Proposed solution: A Market based approach
At an abstract level. Use patent literature for ideas.
***i. Relation to other approaches
Complementary to reputation management, explain how the two could cooperate.
***ii. Abstract description of proposed solution.
Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
*4. Methodology
**a. How we chose this particular approach
With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
**b. Description of our overall approach
We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
**c. Hypotheses
What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
**d. Prototype system trials
What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc.
***ii. Methodology for evaluation
How will we evaluate the results.
**e. Composite experimental trials
Use Ptrim S4.2. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
***ii. Transaction data
Where we found the data and what we did with it
***iii. Methodology for evaluation
How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
*5. Design and implementation
Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
**a. Design of Ptrim system
**b. Ptrim implementation details
How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
**c. Composite experiment setup
How we implemented this: Perl/CGI/MySQL etc.
**d. Data crawling
How we did this
*6. Results, evaluation and discussion
**a. Evaluation of prototype trial outcomes
Use Ptrim S5.1. Refer to hypotheses
**b. Evaluation of composite trial outcomes
Use Ptrim S5.2. Refer to hypotheses
**c. Discussion of overall findings and implications for our approach
*7. Future work
Mention these also in Section 3.b.
**a. Security
**b. Collusion detection
**c. Insuring insurance transactions
**d. Further experiments and simulation studies
*8. Conclusions and synopsis

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T22:58:27Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:

{| border="1"
! Section !! Comments !! Status !! Target
|-
! 1. Introduction
|
|
|
|-
! 1.a. Overview of my research and motivation (Use Ptrim S1)
|
|
|
|-
! 1.b. Main results and original contributions
|
|
|
|-
! 1.c. Organisation of thesis
|
|
|
|-
! 2. Theory and background
|
|
|
|-
! 2.a. Introduction – big picture
|
|
|
|-
! 2.b. P2P networks and architectures
| Based on ACM survey
|
|
|-
! 2.c. Distributed transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
|
|
|-
! 2.d. Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! 2.e. Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|
|
|-
! 2.f. Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|
|
|}

*3. Problem definition and proposed solution
**a. Definition of problem we want to attack: Managing P2P transaction risk
Includes general and also specific goals
**b. Limits of research scope
Things that are not our problem ( References to Section 7).
**c. Proposed solution: A Market based approach
At an abstract level. Use patent literature for ideas.
***i. Relation to other approaches
Complementary to reputation management, explain how the two could cooperate.
***ii. Abstract description of proposed solution.
Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
*4. Methodology
**a. How we chose this particular approach
With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
**b. Description of our overall approach
We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
**c. Hypotheses
What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
**d. Prototype system trials
What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc.
***ii. Methodology for evaluation
How will we evaluate the results.
**e. Composite experimental trials
Use Ptrim S4.2. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
***ii. Transaction data
Where we found the data and what we did with it
***iii. Methodology for evaluation
How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
*5. Design and implementation
Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
**a. Design of Ptrim system
**b. Ptrim implementation details
How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
**c. Composite experiment setup
How we implemented this: Perl/CGI/MySQL etc.
**d. Data crawling
How we did this
*6. Results, evaluation and discussion
**a. Evaluation of prototype trial outcomes
Use Ptrim S5.1. Refer to hypotheses
**b. Evaluation of composite trial outcomes
Use Ptrim S5.2. Refer to hypotheses
**c. Discussion of overall findings and implications for our approach
*7. Future work
Mention these also in Section 3.b.
**a. Security
**b. Collusion detection
**c. Insuring insurance transactions
**d. Further experiments and simulation studies
*8. Conclusions and synopsis

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T22:57:12Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:

{| border="1"
! Section !! Comments !! Status !! Target
|-
! #1. Introduction
|
|
|
|-
! ##a. Overview of my research and motivation (Use Ptrim S1)
|
|
|
|-
! ##b. Main results and original contributions
|
|
|
|-
! ##c. Organisation of thesis
|
|
|
|-
! #2. Theory and background
|
|
|
|-
! ##a. Introduction – big picture
|
|
|
|-
! ##b. P2P networks and architectures
| Based on ACM survey
|
|
|-
! **c. Distributed transaction processing systems
| Compared to centralized, characteristics, requirements (use e-commerce paper)
|
|
|-
! **d. Centralized and distributed reputation management
| Survey of current approaches
|
|
|-
! **e. Market-based risk management
| Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
|
|
|-
! **f. Auxiliary theory and tools used in this research
| Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
|
|
|}

*3. Problem definition and proposed solution
**a. Definition of problem we want to attack: Managing P2P transaction risk
Includes general and also specific goals
**b. Limits of research scope
Things that are not our problem ( References to Section 7).
**c. Proposed solution: A Market based approach
At an abstract level. Use patent literature for ideas.
***i. Relation to other approaches
Complementary to reputation management, explain how the two could cooperate.
***ii. Abstract description of proposed solution.
Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
*4. Methodology
**a. How we chose this particular approach
With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
**b. Description of our overall approach
We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
**c. Hypotheses
What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
**d. Prototype system trials
What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc.
***ii. Methodology for evaluation
How will we evaluate the results.
**e. Composite experimental trials
Use Ptrim S4.2. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
***ii. Transaction data
Where we found the data and what we did with it
***iii. Methodology for evaluation
How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
*5. Design and implementation
Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
**a. Design of Ptrim system
**b. Ptrim implementation details
How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
**c. Composite experiment setup
How we implemented this: Perl/CGI/MySQL etc.
**d. Data crawling
How we did this
*6. Results, evaluation and discussion
**a. Evaluation of prototype trial outcomes
Use Ptrim S5.1. Refer to hypotheses
**b. Evaluation of composite trial outcomes
Use Ptrim S5.2. Refer to hypotheses
**c. Discussion of overall findings and implications for our approach
*7. Future work
Mention these also in Section 3.b.
**a. Security
**b. Collusion detection
**c. Insuring insurance transactions
**d. Further experiments and simulation studies
*8. Conclusions and synopsis

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T22:52:05Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:

{| border="1"
|+ The table's caption
! Column heading 1 !! Column heading 2 !! Column heading 3
|-
! Row heading 1
| Cell 2 || Cell 3
|-
! Row heading A
|Cell B
|Cell C
|}

{| class="wikitable" style="margin: 1em auto 1em auto"
|+Multiplication table
|-
! × !! 1 !! 2 !! 3
|-
! 1
| 1 || 2 || 3
|-
! 2
| 2 || 4 || 6
|-
! 3
| 3 || 6 || 9
|-
! 4
| 4 || 8 || 12
|-
! 5
| 5 || 10 || 15
|}

#1. Introduction
##a. Overview of my research and motivation (Use Ptrim S1)
##b. Main results and original contributions
##c. Organisation of thesis
#2. Theory and background
##a. Introduction – big picture
##b. P2P networks and architectures
Based on ACM survey
**c. Distributed transaction processing systems
Compared to centralized, characteristics, requirements (use e-commerce paper)
**d. Centralized and distributed reputation management
Survey of current approaches
**e. Market-based risk management
Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
**f. Auxiliary theory and tools used in this research
Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
*3. Problem definition and proposed solution
**a. Definition of problem we want to attack: Managing P2P transaction risk
Includes general and also specific goals
**b. Limits of research scope
Things that are not our problem ( References to Section 7).
**c. Proposed solution: A Market based approach
At an abstract level. Use patent literature for ideas.
***i. Relation to other approaches
Complementary to reputation management, explain how the two could cooperate.
***ii. Abstract description of proposed solution.
Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
*4. Methodology
**a. How we chose this particular approach
With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
**b. Description of our overall approach
We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
**c. Hypotheses
What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
**d. Prototype system trials
What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc.
***ii. Methodology for evaluation
How will we evaluate the results.
**e. Composite experimental trials
Use Ptrim S4.2. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
***ii. Transaction data
Where we found the data and what we did with it
***iii. Methodology for evaluation
How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
*5. Design and implementation
Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
**a. Design of Ptrim system
**b. Ptrim implementation details
How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
**c. Composite experiment setup
How we implemented this: Perl/CGI/MySQL etc.
**d. Data crawling
How we did this
*6. Results, evaluation and discussion
**a. Evaluation of prototype trial outcomes
Use Ptrim S5.1. Refer to hypotheses
**b. Evaluation of composite trial outcomes
Use Ptrim S5.2. Refer to hypotheses
**c. Discussion of overall findings and implications for our approach
*7. Future work
Mention these also in Section 3.b.
**a. Security
**b. Collusion detection
**c. Insuring insurance transactions
**d. Further experiments and simulation studies
*8. Conclusions and synopsis

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T22:50:41Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:

{| border="1"
|+ The table's caption
! Column heading 1 !! Column heading 2 !! Column heading 3
|-
! Row heading 1
| Cell 2 || Cell 3
|-
! Row heading A
|Cell B
|Cell C
|}

{| class="wikitable" style="text-align:center"
|+Multiplication table
|-
! × !! 1 !! 2 !! 3
|-
! 1
| 1 || 2 || 3
|-
! 2
| 2 || 4 || 6
|-
! 3
| 3 || 6 || 9
|-
! 4
| 4 || 8 || 12
|-
! 5
| 5 || 10 || 15
|}

#1. Introduction
##a. Overview of my research and motivation (Use Ptrim S1)
##b. Main results and original contributions
##c. Organisation of thesis
#2. Theory and background
##a. Introduction – big picture
##b. P2P networks and architectures
Based on ACM survey
**c. Distributed transaction processing systems
Compared to centralized, characteristics, requirements (use e-commerce paper)
**d. Centralized and distributed reputation management
Survey of current approaches
**e. Market-based risk management
Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
**f. Auxiliary theory and tools used in this research
Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
*3. Problem definition and proposed solution
**a. Definition of problem we want to attack: Managing P2P transaction risk
Includes general and also specific goals
**b. Limits of research scope
Things that are not our problem ( References to Section 7).
**c. Proposed solution: A Market based approach
At an abstract level. Use patent literature for ideas.
***i. Relation to other approaches
Complementary to reputation management, explain how the two could cooperate.
***ii. Abstract description of proposed solution.
Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
*4. Methodology
**a. How we chose this particular approach
With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
**b. Description of our overall approach
We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
**c. Hypotheses
What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
**d. Prototype system trials
What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc.
***ii. Methodology for evaluation
How will we evaluate the results.
**e. Composite experimental trials
Use Ptrim S4.2. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
***ii. Transaction data
Where we found the data and what we did with it
***iii. Methodology for evaluation
How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
*5. Design and implementation
Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
**a. Design of Ptrim system
**b. Ptrim implementation details
How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
**c. Composite experiment setup
How we implemented this: Perl/CGI/MySQL etc.
**d. Data crawling
How we did this
*6. Results, evaluation and discussion
**a. Evaluation of prototype trial outcomes
Use Ptrim S5.1. Refer to hypotheses
**b. Evaluation of composite trial outcomes
Use Ptrim S5.2. Refer to hypotheses
**c. Discussion of overall findings and implications for our approach
*7. Future work
Mention these also in Section 3.b.
**a. Security
**b. Collusion detection
**c. Insuring insurance transactions
**d. Further experiments and simulation studies
*8. Conclusions and synopsis

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T22:50:01Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Follow DIEPTELO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:

{| class="wikitable" style="text-align:center"
|+Multiplication table
|-
! × !! 1 !! 2 !! 3
|-
! 1
| 1 || 2 || 3
|-
! 2
| 2 || 4 || 6
|-
! 3
| 3 || 6 || 9
|-
! 4
| 4 || 8 || 12
|-
! 5
| 5 || 10 || 15
|}

#1. Introduction
##a. Overview of my research and motivation (Use Ptrim S1)
##b. Main results and original contributions
##c. Organisation of thesis
#2. Theory and background
##a. Introduction – big picture
##b. P2P networks and architectures
Based on ACM survey
**c. Distributed transaction processing systems
Compared to centralized, characteristics, requirements (use e-commerce paper)
**d. Centralized and distributed reputation management
Survey of current approaches
**e. Market-based risk management
Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
**f. Auxiliary theory and tools used in this research
Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
*3. Problem definition and proposed solution
**a. Definition of problem we want to attack: Managing P2P transaction risk
Includes general and also specific goals
**b. Limits of research scope
Things that are not our problem ( References to Section 7).
**c. Proposed solution: A Market based approach
At an abstract level. Use patent literature for ideas.
***i. Relation to other approaches
Complementary to reputation management, explain how the two could cooperate.
***ii. Abstract description of proposed solution.
Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
*4. Methodology
**a. How we chose this particular approach
With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
**b. Description of our overall approach
We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
**c. Hypotheses
What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
**d. Prototype system trials
What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc.
***ii. Methodology for evaluation
How will we evaluate the results.
**e. Composite experimental trials
Use Ptrim S4.2. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
***ii. Transaction data
Where we found the data and what we did with it
***iii. Methodology for evaluation
How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
*5. Design and implementation
Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
**a. Design of Ptrim system
**b. Ptrim implementation details
How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
**c. Composite experiment setup
How we implemented this: Perl/CGI/MySQL etc.
**d. Data crawling
How we did this
*6. Results, evaluation and discussion
**a. Evaluation of prototype trial outcomes
Use Ptrim S5.1. Refer to hypotheses
**b. Evaluation of composite trial outcomes
Use Ptrim S5.2. Refer to hypotheses
**c. Discussion of overall findings and implications for our approach
*7. Future work
Mention these also in Section 3.b.
**a. Security
**b. Collusion detection
**c. Insuring insurance transactions
**d. Further experiments and simulation studies
*8. Conclusions and synopsis

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T22:44:24Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:

#1. Introduction
##a. Overview of my research and motivation (Use Ptrim S1)
##b. Main results and original contributions
##c. Organisation of thesis
#2. Theory and background
##a. Introduction – big picture
##b. P2P networks and architectures
Based on ACM survey
**c. Distributed transaction processing systems
Compared to centralized, characteristics, requirements (use e-commerce paper)
**d. Centralized and distributed reputation management
Survey of current approaches
**e. Market-based risk management
Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
**f. Auxiliary theory and tools used in this research
Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
*3. Problem definition and proposed solution
**a. Definition of problem we want to attack: Managing P2P transaction risk
Includes general and also specific goals
**b. Limits of research scope
Things that are not our problem ( References to Section 7).
**c. Proposed solution: A Market based approach
At an abstract level. Use patent literature for ideas.
***i. Relation to other approaches
Complementary to reputation management, explain how the two could cooperate.
***ii. Abstract description of proposed solution.
Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
*4. Methodology
**a. How we chose this particular approach
With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
**b. Description of our overall approach
We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
**c. Hypotheses
What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
**d. Prototype system trials
What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc.
***ii. Methodology for evaluation
How will we evaluate the results.
**e. Composite experimental trials
Use Ptrim S4.2. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
***ii. Transaction data
Where we found the data and what we did with it
***iii. Methodology for evaluation
How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
*5. Design and implementation
Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
**a. Design of Ptrim system
**b. Ptrim implementation details
How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
**c. Composite experiment setup
How we implemented this: Perl/CGI/MySQL etc.
**d. Data crawling
How we did this
*6. Results, evaluation and discussion
**a. Evaluation of prototype trial outcomes
Use Ptrim S5.1. Refer to hypotheses
**b. Evaluation of composite trial outcomes
Use Ptrim S5.2. Refer to hypotheses
**c. Discussion of overall findings and implications for our approach
*7. Future work
Mention these also in Section 3.b.
**a. Security
**b. Collusion detection
**c. Insuring insurance transactions
**d. Further experiments and simulation studies
*8. Conclusions and synopsis

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T22:39:37Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:

{table}
Chapter | Comments | Status | Target
*1. Introduction | | 0 | September
**a. Overview of my research and motivation | Use Ptrim S1 | 0 | September
{table}

**b. Main results and original contributions
**c. Organisation of thesis
*2. Theory and background
**a. Introduction – big picture
**b. P2P networks and architectures
Based on ACM survey
**c. Distributed transaction processing systems
Compared to centralized, characteristics, requirements (use e-commerce paper)
**d. Centralized and distributed reputation management
Survey of current approaches
**e. Market-based risk management
Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
**f. Auxiliary theory and tools used in this research
Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
*3. Problem definition and proposed solution
**a. Definition of problem we want to attack: Managing P2P transaction risk
Includes general and also specific goals
**b. Limits of research scope
Things that are not our problem ( References to Section 7).
**c. Proposed solution: A Market based approach
At an abstract level. Use patent literature for ideas.
***i. Relation to other approaches
Complementary to reputation management, explain how the two could cooperate.
***ii. Abstract description of proposed solution.
Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
*4. Methodology
**a. How we chose this particular approach
With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
**b. Description of our overall approach
We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
**c. Hypotheses
What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
**d. Prototype system trials
What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc.
***ii. Methodology for evaluation
How will we evaluate the results.
**e. Composite experimental trials
Use Ptrim S4.2. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
***ii. Transaction data
Where we found the data and what we did with it
***iii. Methodology for evaluation
How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
*5. Design and implementation
Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
**a. Design of Ptrim system
**b. Ptrim implementation details
How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
**c. Composite experiment setup
How we implemented this: Perl/CGI/MySQL etc.
**d. Data crawling
How we did this
*6. Results, evaluation and discussion
**a. Evaluation of prototype trial outcomes
Use Ptrim S5.1. Refer to hypotheses
**b. Evaluation of composite trial outcomes
Use Ptrim S5.2. Refer to hypotheses
**c. Discussion of overall findings and implications for our approach
*7. Future work
Mention these also in Section 3.b.
**a. Security
**b. Collusion detection
**c. Insuring insurance transactions
**d. Further experiments and simulation studies
*8. Conclusions and synopsis

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T22:38:06Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:
*1. Introduction
**a. Overview of my research and motivation
Use Ptrim S1
**b. Main results and original contributions
**c. Organisation of thesis
*2. Theory and background
**a. Introduction – big picture
**b. P2P networks and architectures
Based on ACM survey
**c. Distributed transaction processing systems
Compared to centralized, characteristics, requirements (use e-commerce paper)
**d. Centralized and distributed reputation management
Survey of current approaches
**e. Market-based risk management
Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
**f. Auxiliary theory and tools used in this research
Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
*3. Problem definition and proposed solution
**a. Definition of problem we want to attack: Managing P2P transaction risk
Includes general and also specific goals
**b. Limits of research scope
Things that are not our problem ( References to Section 7).
**c. Proposed solution: A Market based approach
At an abstract level. Use patent literature for ideas.
***i. Relation to other approaches
Complementary to reputation management, explain how the two could cooperate.
***ii. Abstract description of proposed solution.
Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
*4. Methodology
**a. How we chose this particular approach
With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
**b. Description of our overall approach
We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
**c. Hypotheses
What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
**d. Prototype system trials
What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc.
***ii. Methodology for evaluation
How will we evaluate the results.
**e. Composite experimental trials
Use Ptrim S4.2. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
***ii. Transaction data
Where we found the data and what we did with it
***iii. Methodology for evaluation
How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
*5. Design and implementation
Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
**a. Design of Ptrim system
**b. Ptrim implementation details
How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
**c. Composite experiment setup
How we implemented this: Perl/CGI/MySQL etc.
**d. Data crawling
How we did this
*6. Results, evaluation and discussion
**a. Evaluation of prototype trial outcomes
Use Ptrim S5.1. Refer to hypotheses
**b. Evaluation of composite trial outcomes
Use Ptrim S5.2. Refer to hypotheses
**c. Discussion of overall findings and implications for our approach
*7. Future work
Mention these also in Section 3.b.
**a. Security
**b. Collusion detection
**c. Insuring insurance transactions
**d. Further experiments and simulation studies
*8. Conclusions and synopsis

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T22:37:08Z

Stheotok:

1 Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

2 Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:
*1. Introduction
**a. Overview of my research and motivation
Use Ptrim S1
**b. Main results and original contributions
**c. Organisation of thesis
*2. Theory and background
**a. Introduction – big picture
**b. P2P networks and architectures
Based on ACM survey
**c. Distributed transaction processing systems
Compared to centralized, characteristics, requirements (use e-commerce paper)
**d. Centralized and distributed reputation management
Survey of current approaches
**e. Market-based risk management
Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
**f. Auxiliary theory and tools used in this research
Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
*3. Problem definition and proposed solution
**a. Definition of problem we want to attack: Managing P2P transaction risk
Includes general and also specific goals
**b. Limits of research scope
Things that are not our problem ( References to Section 7).
**c. Proposed solution: A Market based approach
At an abstract level. Use patent literature for ideas.
***i. Relation to other approaches
Complementary to reputation management, explain how the two could cooperate.
***ii. Abstract description of proposed solution.
Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
*4. Methodology
**a. How we chose this particular approach
With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
**b. Description of our overall approach
We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
**c. Hypotheses
What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
**d. Prototype system trials
What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc.
***ii. Methodology for evaluation
How will we evaluate the results.
**e. Composite experimental trials
Use Ptrim S4.2. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
***ii. Transaction data
Where we found the data and what we did with it
***iii. Methodology for evaluation
How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
*5. Design and implementation
Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
**a. Design of Ptrim system
**b. Ptrim implementation details
How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
**c. Composite experiment setup
How we implemented this: Perl/CGI/MySQL etc.
**d. Data crawling
How we did this
*6. Results, evaluation and discussion
**a. Evaluation of prototype trial outcomes
Use Ptrim S5.1. Refer to hypotheses
**b. Evaluation of composite trial outcomes
Use Ptrim S5.2. Refer to hypotheses
**c. Discussion of overall findings and implications for our approach
*7. Future work
Mention these also in Section 3.b.
**a. Security
**b. Collusion detection
**c. Insuring insurance transactions
**d. Further experiments and simulation studies
*8. Conclusions and synopsis

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T22:36:13Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:
*1. Introduction
**a. Overview of my research and motivation
Use Ptrim S1
**b. Main results and original contributions
**c. Organisation of thesis
*2. Theory and background
**a. Introduction – big picture
**b. P2P networks and architectures
Based on ACM survey
**c. Distributed transaction processing systems
Compared to centralized, characteristics, requirements (use e-commerce paper)
**d. Centralized and distributed reputation management
Survey of current approaches
**e. Market-based risk management
Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
**f. Auxiliary theory and tools used in this research
Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
*3. Problem definition and proposed solution
**a. Definition of problem we want to attack: Managing P2P transaction risk
Includes general and also specific goals
**b. Limits of research scope
Things that are not our problem ( References to Section 7).
**c. Proposed solution: A Market based approach
At an abstract level. Use patent literature for ideas.
***i. Relation to other approaches
Complementary to reputation management, explain how the two could cooperate.
***ii. Abstract description of proposed solution.
Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
*4. Methodology
**a. How we chose this particular approach
With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
**b. Description of our overall approach
We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
**c. Hypotheses
What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
**d. Prototype system trials
What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc.
***ii. Methodology for evaluation
How will we evaluate the results.
**e. Composite experimental trials
Use Ptrim S4.2. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
***ii. Transaction data
Where we found the data and what we did with it
***iii. Methodology for evaluation
How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
*5. Design and implementation
Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
**a. Design of Ptrim system
**b. Ptrim implementation details
How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
**c. Composite experiment setup
How we implemented this: Perl/CGI/MySQL etc.
**d. Data crawling
How we did this
*6. Results, evaluation and discussion
**a. Evaluation of prototype trial outcomes
Use Ptrim S5.1. Refer to hypotheses
**b. Evaluation of composite trial outcomes
Use Ptrim S5.2. Refer to hypotheses
**c. Discussion of overall findings and implications for our approach
*7. Future work
Mention these also in Section 3.b.
**a. Security
**b. Collusion detection
**c. Insuring insurance transactions
**d. Further experiments and simulation studies
*8. Conclusions and synopsis

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T22:35:44Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:
*1. Introduction
**a. Overview of my research and motivation
Use Ptrim S1
**b. Main results and original contributions
**c. Organisation of thesis
*2. Theory and background
**a. Introduction – big picture
**b. P2P networks and architectures
Based on ACM survey
**c. Distributed transaction processing systems
Compared to centralized, characteristics, requirements (use e-commerce paper)
**d. Centralized and distributed reputation management
Survey of current approaches
**e. Market-based risk management
Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
**f. Auxiliary theory and tools used in this research
Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
*3. Problem definition and proposed solution
**a. Definition of problem we want to attack: Managing P2P transaction risk
Includes general and also specific goals
**b. Limits of research scope
Things that are not our problem ( References to Section 7).
**c. Proposed solution: A Market based approach
At an abstract level. Use patent literature for ideas.
***i. Relation to other approaches
Complementary to reputation management, explain how the two could cooperate.
***ii. Abstract description of proposed solution.
Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
*4. Methodology
**a. How we chose this particular approach
With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
**b. Description of our overall approach
We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
**c. Hypotheses
What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
**d. Prototype system trials
What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc.
***ii. Methodology for evaluation
How will we evaluate the results.
**e. Composite experimental trials
Use Ptrim S4.2. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
***ii. Transaction data
Where we found the data and what we did with it
***iii. Methodology for evaluation
How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
*5. Design and implementation
Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
**a. Design of Ptrim system
**b. Ptrim implementation details
How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
**c. Composite experiment setup
How we implemented this: Perl/CGI/MySQL etc.
**d. Data crawling
How we did this
*6. Results, evaluation and discussion
**a. Evaluation of prototype trial outcomes
Use Ptrim S5.1. Refer to hypotheses
**b. Evaluation of composite trial outcomes
Use Ptrim S5.2. Refer to hypotheses
**c. Discussion of overall findings and implications for our approach
*7. Future work
Mention these also in Section 3.b.
**a. Security
**b. Collusion detection
**c. Insuring insurance transactions
**d. Further experiments and simulation studies
*8. Conclusions and synopsis

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T22:34:11Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:
*1. Introduction
**a. Overview of my research and motivation
Use Ptrim S1
**b. Main results and original contributions
**c. Organisation of thesis
*2. Theory and background
**a. Introduction – big picture
**b. P2P networks and architectures
Based on ACM survey
**c. Distributed transaction processing systems
Compared to centralized, characteristics, requirements (use e-commerce paper)
**d. Centralized and distributed reputation management
Survey of current approaches
**e. Market-based risk management
Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
**f. Auxiliary theory and tools used in this research
Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
*3. Problem definition and proposed solution
**a. Definition of problem we want to attack: Managing P2P transaction risk
Includes general and also specific goals
**b. Limits of research scope
Things that are not our problem ( References to Section 7).
**c. Proposed solution: A Market based approach
At an abstract level. Use patent literature for ideas.
***i. Relation to other approaches
Complementary to reputation management, explain how the two could cooperate.
***ii. Abstract description of proposed solution.
Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
*4. Methodology
**a. How we chose this particular approach
With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
**b. Description of our overall approach
We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
**c. Hypotheses
What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
**d. Prototype system trials
What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc.
***ii. Methodology for evaluation
How will we evaluate the results.
**e. Composite experimental trials
Use Ptrim S4.2. Which hypotheses do we address here.
***i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
***ii. Transaction data
Where we found the data and what we did with it
***iii. Methodology for evaluation
How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
*5. Design and implementation
Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
**a. Design of Ptrim system
**b. Ptrim implementation details
How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
**c. Composite experiment setup
How we implemented this: Perl/CGI/MySQL etc.
**d. Data crawling
How we did this
*6. Results, evaluation and discussion
**a. Evaluation of prototype trial outcomes
Use Ptrim S5.1. Refer to hypotheses
**b. Evaluation of composite trial outcomes
Use Ptrim S5.2. Refer to hypotheses
**c. Discussion of overall findings and implications for our approach
*7. Future work
Mention these also in Section 3.b.
**a. Security
**b. Collusion detection
**c. Insuring insurance transactions
**d. Further experiments and simulation studies
*8. Conclusions and synopsis

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-06-03T22:27:57Z

Stheotok:

Publications Plan:
* Currently I only focus on thesis write-up. There are no specific goals for other publications.

Non-thesis-related personal plans:
* Follow SENSE/PENED accounting stuff.
* Follow SOPRANO accounting stuff.
* Prepare for SOPRANO Bilbao meeting (June 10-12).

PhD thesis table of contents:
1. Introduction
a. Overview of my research and motivation
Use Ptrim S1
b. Main results and original contributions
c. Organisation of thesis
2. Theory and background
a. Introduction – big picture
b. P2P networks and architectures
Based on ACM survey
c. Distributed transaction processing systems
Compared to centralized, characteristics, requirements (use e-commerce paper)
d. Centralized and distributed reputation management
Survey of current approaches
e. Market-based risk management
Financial derivatives, risk management, market efficiency. Use Ptrim S2.1. S2.4
f. Auxiliary theory and tools used in this research
Mention, with references to Sections, we’ll be talking about crawling utilities, importance sampling, Java/jxta development etc.
3. Problem definition and proposed solution
a. Definition of problem we want to attack: Managing P2P transaction risk
Includes general and also specific goals
b. Limits of research scope
Things that are not our problem ( References to Section 7).
c. Proposed solution: A Market based approach
At an abstract level. Use patent literature for ideas.
i. Relation to other approaches
Complementary to reputation management, explain how the two could cooperate.
ii. Abstract description of proposed solution.
Abstract design and architecture. Description of the market-based insurance layer, and the Ptrim system. Use Ptrim S2.3. Talk about need for efficient, competitive market. Use Ptrim S3.1.
4. Methodology
a. How we chose this particular approach
With particular focus to our evaluation approach. Discuss other possible approaches (e.g. theoretical) that were not selected.
b. Description of our overall approach
We’ll build a prototype and test it, and we’ll also run composite experiments and evaluate the results.
c. Hypotheses
What were our specific hypotheses (H1, H2, H3). We’ll refer to them in d and e below, and also again in Section 6.
d. Prototype system trials
What sort of trials we ran with the prototype. Use Ptrim S4.1. Which hypotheses do we address here.
i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc.
ii. Methodology for evaluation
How will we evaluate the results.
e. Composite experimental trials
Use Ptrim S4.2. Which hypotheses do we address here.
i. Experimental setup
How the experiment will work, software tool, subjects, questionnaires etc. Use Ptrim S
ii. Transaction data
Where we found the data and what we did with it
iii. Methodology for evaluation
How will we evaluate the results (market efficiency, risk reduction, questionnaires etc)
5. Design and implementation
Follows the structure of 3c, but not at an abstract level any more, we refer to design and implementation. Lots of UML diagrams
a. Design of Ptrim system
b. Ptrim implementation details
How we implemented this: Java, jxta, messaging, etc Use Ptrim S3.2.
c. Composite experiment setup
How we implemented this: Perl/CGI/MySQL etc.
d. Data crawling
How we did this
6. Results, evaluation and discussion
a. Evaluation of prototype trial outcomes
Use Ptrim S5.1. Refer to hypotheses
b. Evaluation of composite trial outcomes
Use Ptrim S5.2. Refer to hypotheses
c. Discussion of overall findings and implications for our approach
7. Future work
Mention these also in Section 3.b.
a. Security
b. Collusion detection
c. Insuring insurance transactions
d. Further experiments and simulation studies
8. Conclusions and synopsis

PhD thesis research plan:
* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis personal plan

2008-06-03T22:24:16Z

Stheotok: Replacing page with 'See Stephanos Androutsellis PhD research plan'

See [[Stephanos Androutsellis PhD research plan]]

Stephanos Androutsellis publication plan

2008-06-03T22:23:57Z

Stheotok:

See [[Stephanos Androutsellis PhD research plan]]

Stephanos Androutsellis publication plan

2008-06-03T22:23:45Z

Stheotok:

See [[Stephanos Androutsellis research plan]]

Stephanos Androutsellis PhD research plan

2008-05-29T07:03:01Z

Stheotok:

* May 29th 2008: Draft version of PhD skeleton, official initiation of writeup
* June 10th 2008: Completion of additional composite experiment with uniformly sampled data on undergrads. This will be used for the thesis, or for future Ptrim paper versions.
* September 2008: Expected revision of Ptrim journal paper.
* July 10th 2008: First draft of thesis for overview with dds.
* August 25th 2008: Second draft of thesis for overview with dds.
* September 20th 2008: Thesis version ready for review with dds.
* October 15th 2008: Final thesis version ready for submission.
* November 2008: Thesis presentation and PhD completion.

Stephanos Androutsellis PhD research plan

2008-03-27T08:41:12Z

Stheotok:

* April 5th 2008: Completion of composite experiment and data collection.
* April 10th 2008: Completion of preliminary data analysis. Assuming data is acceptable and backs our theory (1):
* April 10th 2008: Identify group of undergraduate students to re-run experiment. We will do this regardless of the quality of the data obtained in the current experiment.
* April 20th 2008: Completion of first complete draft of Ptrim journal paper, including composite experiment data.
* April 30th 2008: Completion of internal paper review and revisions, submission to Journal (1).
* May 2008-August 2008: Final thesis writeup.
* September 2008: First version of Thesis ready for internal review
* November 2008: Final Thesis presentation and PhD completion.

(1) If current experiment data is unacceptable, the new experiment data will need to be used, which means we'll need another week or so to incorporate it.Perhaps we will do this anyway, depending on the quality of the data.

Stephanos Androutsellis personal plan

2007-12-19T16:29:24Z

Stheotok:

PhD:
* Prepare report on market efficiency evaluation, based on EC literature batch (draft ready)
* Prepare report on risk management system evaluation, based on REP literature batch
* Prepare thesis Toc (draft ready), dds check
* Prepare report on applications of derivatives instruments to our setting
* Prepare report on data sampling methodologies
* Complete development of perl script for experiment.
* Run experiment

Non-PhD:
* Follow IntelligentEnergy proposal progress
* Keep an eye on Thomopoulou about PENED/Singular accounting stuff
* Check that PRAXIS is finally closed and all payments received

[[Category:Private stheotok]]

Stephanos Androutsellis personal plan

2007-11-09T21:52:12Z

Stheotok:

PhD:
* Complete installation of mySQL database on server.
* Complete development and installation of perl script for experiment.
* Complete document describing experiment.

Non-PhD:
* Paper reviewing X2
* Soprano user requirement document processing
* Soprano Eindhoven meeting - probably not, but check about Paschalis attending
* Follow IntelligentEnergy proposal progress
* Ask about Dieptelo progress
* Keep an eye on Thomopoulou about PENED/Singular accounting stuff
* Check that PRAXIS is finally closed and all payments received

[[Category:Private stheotok]]

Stephanos Androutsellis personal plan

2007-11-09T21:49:45Z

Stheotok:

PhD:
* Complete installation of mySQL database on server.
* Complete development and installation of perl script for experiment.
* Complete document describing experiment.

Non-PhD:
* Soprano user requirement document processing
* Soprano Eindhoven meeting - probably not, but check about Paschalis attending
* Follow IntelligentEnergy proposal progress
* Ask about Dieptelo progress
* Keep an eye on Thomopoulou about PENED/Singular accounting stuff
* Check that PRAXIS is finally closed and all payments received

[[Category:Private stheotok]]

FP7: Critical Infrastructure Protection

2007-10-12T04:41:28Z

Stheotok: /* Project Proposals */

== Project Proposals ==
* [[RedZone]]
* [[Mapping Critical IT Infrastructures]]
* [[PROMIS]]
* [[Reliability Evaluation of Free / Open Source / Libre Software]]

== Call ==

* [[CallDetails-ICT-SEC-2007.1.7]]: Call details

== Partners ==

* [[ICT-SEC-2007.1.7 Partners Table]]

Telemonitoring System for Remote Power Plants

2007-10-12T04:40:41Z

Stheotok: Removing all content from page

Stephanos Androutsellis publication plan

2007-02-07T12:08:50Z

Stheotok:

== Under development ==
* (Title confidential) (Diomidis Spinellis; ''7th IEEE International Conference on Peer-to-Peer Computing''; April 22, 2007).

== Pending ==

== To appear ==

[[Category:SENSE]]

SENSE publication plans

2007-02-07T12:06:41Z

Stheotok:

A good publication record doesn't happen by chance. It requires careful planning and execution. Given the fact that publishing to a top journal can take as much as three years, you can't afford to send a publication off, and then wait for a reply. At any time you should have a pipeline filled with publications in three stages of progress.

* Publications under development. These may be new contributions or papers that you improve following review comments.
* Publications under review.
* Publications that have been accepted and are (often slowly) moving toward publication.

Keeping all stages of the pipeline full ensures that publishers, reviewers, and yourself are always busy, with no time being lost in idle waiting. Also, try to have in your pipeline a mix of different paper types: conference papers for rapid dissemination of results; journal articles for advancing your academic career. Publication delays being what they are, your first aim in your plan is to keep reviewers and publishers busy. Don't sit on papers that have been accepted with revisions: revise them as soon as possible. If you ever notice that a stage of your pipeline is empty, you're in trouble. Make it your priority to fill it up, or prepare to cry over an empty hole in your CV's publication record.

== Plans of individual members ==
* [[Publication plan template]]
* [[Diomidis Spinellis publication plan|Diomidis Spinellis]]
* [[Giorgos Gousios publication plan|Giorgos Gousios]]
* [[Vassilios Karakoidas publication plan|Vassilios Karakoidas]]
* [[Panos Louridas publication plan|Panos Louridas]]
* [[Stephanos Androutsellis publication plan|Stephanos Androutsellis]]
[[Category:SENSE]]

Mac ibook G4

2007-02-05T19:11:00Z

Stheotok:

Apple ibook G4

2007-02-05T19:10:28Z

Stheotok:

* Apple iBook G4 14"/1.33GHz/256/6
* [http://www.apple.com/macbook/macbook.html product data]
* Funded from the PRAXIS project
* SN UV44606LS85

[[Category:Equipment]]
[[Category:Equipment PRAXIS]]
[[Category:Equipment SENSE]]
[[Category:SENSE]]

Mac ibook G4

2007-02-05T19:09:46Z

Stheotok: