Difference: JuliaSchenk (1 vs. 17)

Revision 17
28 Mar 2013 - Main.JuliaSchenk
Line: 1 to 1
 
META TOPICPARENT name="WikiUsers"
js.jpg

Dipl. Inform. Julia Schenk (research associate)

Line: 12 to 12
 

Phone +49 30 838 75242
Email: julia.schenk@fu-berlinxxNOSPAMxx.de
Changed:
<
<		 (don't forget to remove the xxNOSPAMxx)
>
>		 (don't forget to remove the xxNOSPAMxx)
 

Feel free to drop in or to write me an email.
Line: 24 to 24
 

Research

Changed:
<
<		 My research is concerned with the process of Distributed Pair Programming (DPP) compared to Pair Programming (PP).
>
>		 My research is concerned with the process of Distributed Pair Programming (DPP) compared to Pair Programming (PP).
  In particular I am interested in the different process phenomena of DPP compared to PP and their consequences concerning the fitness for use of Distributed Pair Programming.
Changed:
<
<		 In the PP (face-to-face) setting the parties involved perceive social and implicit situative aspects like the emotional state or the focus of attention of their programming mate as well as his explicit behaviour in general and in the shared workspace. These so-called awareness information are perceived intuitively for the most part, constitute the basis for one's own actions, and are fundamental for an efficient collaboration. Furthermore the participants are unrestricted in their verbal and nonverbal communication.
>
>		 In the PP (face-to-face) setting the parties involved perceive social and implicit situative aspects like the emotional state or the focus of attention of their programming mate as well as his explicit behaviour in general and in the shared workspace. These so-called awareness information are perceived intuitively for the most part, constitute the basis for one's own actions, and are fundamental for an efficient collaboration. Furthermore the participants are unrestricted in their verbal and nonverbal communication.
 
Changed:
<
<		 Due to the spacial distribution in DPP the parties are coupled in the workspace via a groupware for real-time editing, but each participant has his own monitor and input devices (mouse and keyboard). As a result on the one hand the participants do not automatically have the same viewport, nor are they necessarily aware of their programming mate's location and actions in the workspace. The natural channels of perception and communication are not available. During their collaboration the participants are restricted to the communication channels and awareness information provided by the collaboration tool.
>
>		 Due to the spacial distribution in DPP the parties are coupled in the workspace via a groupware for real-time editing, but each participant has his own monitor and input devices (mouse and keyboard). As a result on the one hand the participants do not automatically have the same viewport, nor are they necessarily aware of their programming mate's location and actions in the workspace. The natural channels of perception and communication are not available. During their collaboration the participants are restricted to the communication channels and awareness information provided by the collaboration tool.
  On the other hand due to their autarkic workspace the participants are less coupled and therefore more flexible during their collaboration. Whenever necessary they can explore separately in the workspace and find together.
Changed:
<
<		 This leads to the questions to which extend the lack of (nonverbal) communication channels and awareness information has an impact on the DPP process, how one could overcome these difficulties either through appropriate behavioral patterns of the programming mates or through provided information by the collaboration tool, and when it is possible to extract advantages from the increased flexibility of DPP.
>
>		 This leads to the following questions:
  • To which extend the lack of (nonverbal) communication channels and awareness information has an impact on the DPP process?
  • How one could overcome these difficulties either through appropriate behavioral patterns of the programming mates or through provided information by the collaboration tool?
  • When it is possible to extract advantages from the increased flexibility of DPP?

Testbed for my DPP research is Saros (http://www.saros-project.org), an Open Source Eclipse plugin for distributed collaborative software development, which is developed by the Software Engineering Working Group.
 

Publications

Line: 49 to 54
 

Courses 2013

Changed:
<
<
>
>
 

Courses 2012

Changed:
<
<
>
>
 

Courses 2011

Changed:
<
<
>
>
 

Courses 2010

Changed:
<
<
>
>
 

Courses 2009

Changed:
<
<
>
>
 

for more information see Courses of the Software Engineering Working Group

Supervision of Theses

Changed:
<
<
Finished Title pdf
2013-04 Evaluierung einer multimodal bedienbaren und personalisierten Kalenderanwendung auf Basis des mobilen Dialogsystems des DFKI
2012-11 Verbesserung der Usability von Saros unter Verwendung eines User-Centered Design Ansatzes pdf
2012-08 Überarbeitung der Saros Website nach dem User-Centered Design pdf
2012-05 Benutzerzentrierte Entwicklung eines Nutzungskonzepts für das Saros-Whiteboard unter Berücksichtigung der Unterstützung von Grafiktabletts pdf
2012-04 Prüfung und Verbesserung der Usability von Saros im produktiven Einsatz pdf
2011-11 Verbesserung der User Experience in Saros pdf
2011-09 Evaluation von Präsenzverfahren in Saros pdf
2011-05 Verbesserung der Out-Of-Box-Experience in Saros mittels Heuristischer Evaluation und Usability-Tests pdf
2011-02 Ideen und Alternativen zur Gestaltung der Saros-Benutzeroberfläche pdf
2010-07 Analyse und Erweiterung der VoIP-Funktionalität in Saros pdf
2010-03 Die Einführung von Saros in Open-Source-Software-Projekten pdf
>
>
Finished Type Title pdf
2013-XX Diploma Verbesserung der „First Contact Experience“ für angehende Saros-Entwickler
2013-04 Bachelor Evaluierung einer multimodal bedienbaren und personalisierten Kalenderanwendung auf Basis des mobilen Dialogsystems des DFKI
2012-11 Master Verbesserung der Usability von Saros unter Verwendung eines User-Centered Design Ansatzes pdf
2012-08 Bachelor Überarbeitung der Saros Website nach dem User-Centered Design pdf
2012-05 Master Benutzerzentrierte Entwicklung eines Nutzungskonzepts für das Saros-Whiteboard unter Berücksichtigung der Unterstützung von Grafiktabletts pdf
2012-04 Diploma Prüfung und Verbesserung der Usability von Saros im produktiven Einsatz pdf
2011-11 Bachelor Verbesserung der User Experience in Saros pdf
2011-09 Bachelor Evaluation von Präsenzverfahren in Saros pdf
2011-05 Master Verbesserung der Out-Of-Box-Experience in Saros mittels Heuristischer Evaluation und Usability-Tests pdf
2011-02 Bachelor Ideen und Alternativen zur Gestaltung der Saros-Benutzeroberfläche pdf
2010-07 Bachelor Analyse und Erweiterung der VoIP-Funktionalität in Saros pdf
2010-03 Diploma Die Einführung von Saros in Open-Source-Software-Projekten pdf
 

for more information see Thesis topics of the Software Engineering Working Group
Revision 16
27 Mar 2013 - Main.JuliaSchenk
Line: 1 to 1
 
META TOPICPARENT name="WikiUsers"
js.jpg

Dipl. Inform. Julia Schenk (research associate)

Line: 12 to 12
 

Phone +49 30 838 75242
Email: julia.schenk@fu-berlin.de
Changed:
<
<		 (Keep in mind to remove the xxNOSPAMxx)

>
>		 (don't forget to remove the xxNOSPAMxx)

 

Feel free to drop in or to write me an email.
Line: 26 to 27
  My research is concerned with the process of Distributed Pair Programming (DPP) compared to Pair Programming (PP). In particular I am interested in the different process phenomena of DPP compared to PP and their consequences concerning the fitness for use of Distributed Pair Programming.
Changed:
<
<		 During PP (face-to-face) setting the parties involved perceive social and implicit situative aspects like the emotional state or the focus of attention of their programming mate as well as his explicit behaviour in general and in the shared workspace. These so called awareness information are perceived intuitively for the most part, constitue the basis for one's own actions, and are fundamental for an efficient collaboration. Furthermore the participants are unrestricted in their verbal and nonverbal communication.
>
>		 In the PP (face-to-face) setting the parties involved perceive social and implicit situative aspects like the emotional state or the focus of attention of their programming mate as well as his explicit behaviour in general and in the shared workspace. These so-called awareness information are perceived intuitively for the most part, constitute the basis for one's own actions, and are fundamental for an efficient collaboration. Furthermore the participants are unrestricted in their verbal and nonverbal communication.
 
Changed:
<
<		 Due to the spacial distribution in DPP the parties are coupled in the workspace via a groupware for real-time editing, but each mate has its own monitor and input devices (mouse and keyboard). As a result on the one hand the participants do not automatically have the same viewport, nor are they necessarily aware of their programming mate's location and actions in the workspace. The natural channels of perception and communication are not available. During their collaboration the participants are restricted to the communication channels and awareness information provided by the collaboration tool. On the other hand due to their autarkic workspace the participants are less coupled and therefore more flexible during their collaboration. They can explore separately in the workspace and find together as necessary.
>
>		 Due to the spacial distribution in DPP the parties are coupled in the workspace via a groupware for real-time editing, but each participant has his own monitor and input devices (mouse and keyboard). As a result on the one hand the participants do not automatically have the same viewport, nor are they necessarily aware of their programming mate's location and actions in the workspace. The natural channels of perception and communication are not available. During their collaboration the participants are restricted to the communication channels and awareness information provided by the collaboration tool. On the other hand due to their autarkic workspace the participants are less coupled and therefore more flexible during their collaboration. Whenever necessary they can explore separately in the workspace and find together.
 
Changed:
<
<		 This leads to the questions to which extend the lack of (nonverbal) communication channels and awareness information has an impact on the DPP process, how one could overcome these difficulties either through appropriate behavioral patterns of the programming mates or through provided information by the collaboration tool, and when one could extract advantages from the increased flexibility of DPP.
>
>		 This leads to the questions to which extend the lack of (nonverbal) communication channels and awareness information has an impact on the DPP process, how one could overcome these difficulties either through appropriate behavioral patterns of the programming mates or through provided information by the collaboration tool, and when it is possible to extract advantages from the increased flexibility of DPP.
 

Publications

Line: 45 to 46
 

Teaching

Changed:
<
<
>
>
 

Courses 2013

Revision 15
26 Mar 2013 - Main.JuliaSchenk
Line: 1 to 1
 
META TOPICPARENT name="WikiUsers"
js.jpg

Dipl. Inform. Julia Schenk (research associate)

Line: 45 to 45
 

Teaching

Changed:
<
<

2013

2012

2011

2010

2009

>
>

Courses 2013

Courses 2012

Courses 2011

Courses 2010

Courses 2009

 

for more information see Courses of the Software Engineering Working Group

Supervision of Theses

Added:
>
>
Finished Title pdf
2013-04 Evaluierung einer multimodal bedienbaren und personalisierten Kalenderanwendung auf Basis des mobilen Dialogsystems des DFKI
2012-11 Verbesserung der Usability von Saros unter Verwendung eines User-Centered Design Ansatzes pdf
2012-08 Überarbeitung der Saros Website nach dem User-Centered Design pdf
2012-05 Benutzerzentrierte Entwicklung eines Nutzungskonzepts für das Saros-Whiteboard unter Berücksichtigung der Unterstützung von Grafiktabletts pdf
2012-04 Prüfung und Verbesserung der Usability von Saros im produktiven Einsatz pdf
2011-11 Verbesserung der User Experience in Saros pdf
2011-09 Evaluation von Präsenzverfahren in Saros pdf
2011-05 Verbesserung der Out-Of-Box-Experience in Saros mittels Heuristischer Evaluation und Usability-Tests pdf
2011-02 Ideen und Alternativen zur Gestaltung der Saros-Benutzeroberfläche pdf
2010-07 Analyse und Erweiterung der VoIP-Funktionalität in Saros pdf
2010-03 Die Einführung von Saros in Open-Source-Software-Projekten pdf

for more information see Thesis topics of the Software Engineering Working Group
 

META FILEATTACHMENT attachment="js.jpg" attr="h" comment="" date="1364146070" name="js.jpg" path="js.jpg" size="24332" user="schenu" version="1"
Revision 14
25 Mar 2013 - Main.JuliaSchenk
Line: 1 to 1
 
META TOPICPARENT name="WikiUsers"
js.jpg

Dipl. Inform. Julia Schenk (research associate)

Line: 26 to 26
  My research is concerned with the process of Distributed Pair Programming (DPP) compared to Pair Programming (PP). In particular I am interested in the different process phenomena of DPP compared to PP and their consequences concerning the fitness for use of Distributed Pair Programming.
Changed:
<
<		 During PP (face-to-face) setting the parties involved perceive social and implicit situative aspects like the emotional state or the focus of attention of their programming mate as well as his explicit behaviour in general and in the shared workspace. These so called awareness information are perceived intuitively for the most part and constitue the basis for one's own actions. As a consequence they are fundamental for an efficient collaboration.
>
>		 During PP (face-to-face) setting the parties involved perceive social and implicit situative aspects like the emotional state or the focus of attention of their programming mate as well as his explicit behaviour in general and in the shared workspace. These so called awareness information are perceived intuitively for the most part, constitue the basis for one's own actions, and are fundamental for an efficient collaboration. Furthermore the participants are unrestricted in their verbal and nonverbal communication.

Due to the spacial distribution in DPP the parties are coupled in the workspace via a groupware for real-time editing, but each mate has its own monitor and input devices (mouse and keyboard). As a result on the one hand the participants do not automatically have the same viewport, nor are they necessarily aware of their programming mate's location and actions in the workspace. The natural channels of perception and communication are not available. During their collaboration the participants are restricted to the communication channels and awareness information provided by the collaboration tool. On the other hand due to their autarkic workspace the participants are less coupled and therefore more flexible during their collaboration. They can explore separately in the workspace and find together as necessary.

This leads to the questions to which extend the lack of (nonverbal) communication channels and awareness information has an impact on the DPP process, how one could overcome these difficulties either through appropriate behavioral patterns of the programming mates or through provided information by the collaboration tool, and when one could extract advantages from the increased flexibility of DPP.
 
Deleted:
<
<
 

Publications

Line: 54 to 44
 

Teaching

Deleted:
<
<		 see Courses of the Software Engineering Working Group
 
Added:
>
>

2013

2012

2011

2010

2009

for more information see Courses of the Software Engineering Working Group

Supervision of Theses

 

META FILEATTACHMENT attachment="js.jpg" attr="h" comment="" date="1364146070" name="js.jpg" path="js.jpg" size="24332" user="schenu" version="1"
Revision 13
25 Mar 2013 - Main.JuliaSchenk
Line: 1 to 1
 
META TOPICPARENT name="WikiUsers"
js.jpg

Dipl. Inform. Julia Schenk (research associate)

Line: 23 to 23
 

Research

Added:
>
>		 My research is concerned with the process of Distributed Pair Programming (DPP) compared to Pair Programming (PP). In particular I am interested in the different process phenomena of DPP compared to PP and their consequences concerning the fitness for use of Distributed Pair Programming.
 
Added:
>
>		 During PP (face-to-face) setting the parties involved perceive social and implicit situative aspects like the emotional state or the focus of attention of their programming mate as well as his explicit behaviour in general and in the shared workspace. These so called awareness information are perceived intuitively for the most part and constitue the basis for one's own actions. As a consequence they are fundamental for an efficient collaboration. 

<--
Due to the spacial distribution in DPP the parties 
Während der Paarprogrammierung nehmen die Beteiligten jeweils soziale, implizite situative
Informationen sowie explizites Verhalten im allgemeinen und im Arbeitskontext wahr. Dabei sie
sind in ihrer verbalen als auch nonverbalen Kommunikation uneingeschränkt.


Arbeiten die Beteiligten räumlich verteilt zusammen, sind also über ein Softwarewerkzeug zu
synchronen, verteilten Kollaboration miteinander verbunden, so verfügt jeder der Beteiligten
über einen eigenen Monitor und eigene Eingabegeräte, wodurch der andere nicht automatisch
über dessen Sichtbereich und Aktivitäten informiert ist. Die natürlichen und intuitiv genutzen
Kommunikations- und Wahrnehmungskanäle die sich durch den persönlichen Kontakt ergeben
stehen nicht zur Verfügung. Die Beteiligten sind bei ihrer Zusammenarbeit folglich auf die Informationen
und Kommunikationskanäle eingeschränkt, die ihnen von der Kollaborationssoftware
zur Verfügung gestellt werden.


-->
 

Publications

Revision 12
24 Mar 2013 - Main.JuliaSchenk
Line: 1 to 1
 
META TOPICPARENT name="WikiUsers"
Added:
>
>		 js.jpg

Dipl. Inform. Julia Schenk (research associate)

 

Changed:
<
<

Julia Schenk (research associate)

>
>		 Institute of Computer Science
Software Engineering Working Group
 
Changed:
<
<		 Hello and welcome to my page
>
>		 Freie Universität Berlin
Takustr. 9, Room 008
14195 Berlin
 
Changed:
<
<		 I'm a member of the Software Engineering Working Group at the Freie Universität Berlin.
>
>		 Phone +49 30 838 75242
Email: julia.schenk@fu-berlin.de
(Keep in mind to remove the xxNOSPAMxx)

 
Added:
>
>		 Feel free to drop in or to write me an email.

 

Research

Line: 16 to 30
 

Changed:
<
<

Teaching

see Courses of the Software Engineering Working Group

Contact Data

Dipl. Inform. Julia Schenk

Institute of Computer Science

Software Engineering Working Group
>
>
 
Changed:
<
<

Freie Universität Berlin

Takustr. 9, Room 008

14195 Berlin

Phone +49 30 838 75242

Email: julia.schenk@fu-berlinxxNOSPAMxx.de

(Keep in mind to remove the xxNOSPAMxx)
>
>

Teaching

see Courses of the Software Engineering Working Group
 

Changed:
<
<		 Feel free to drop in or to write me an email. smile
>
>
META FILEATTACHMENT attachment="js.jpg" attr="h" comment="" date="1364146070" name="js.jpg" path="js.jpg" size="24332" user="schenu" version="1"
Revision 11
28 Aug 2012 - Main.JuliaSchenk
Line: 1 to 1
 
META TOPICPARENT name="WikiUsers"

Julia Schenk (research associate)

Line: 12 to 12
 

Publications

Changed:
<
<		 Stephan Salinger, Christopher Oezbek, Karl Beecher, Julia Schenk. Saros: An Eclipse Plug-in for Distributed Party Programming. Proceedings of the 2010 ICSE Workshop on Cooperative and Human Aspects of Software Engineering, May, 2010.
>
>

 

Teaching

Changed:
<
<		 see Courses of the AG Software Engineering
>
>		 see Courses of the Software Engineering Working Group
 

Contact Data

Revision 10
10 Mar 2011 - Main.JuliaSchenk
Line: 1 to 1
 
META TOPICPARENT name="WikiUsers"

Julia Schenk (research associate)

Line: 19 to 19
  Proceedings of the 2010 ICSE Workshop on Cooperative and Human Aspects of Software Engineering, May, 2010.

Teaching

Changed:
<
<		 I am, respectively was, in charge of organising the exercise courses accompanying the following lectures as well as conducting some tutorials:

winter semester 2010/2011

summer semester 2010

winter semester 2009/2010

>
>		 see Courses of the AG Software Engineering
 

Contact Data

Line: 53 to 43
 

Email: julia.schenk@fu-berlinxxNOSPAMxx.de
Changed:
<
<		 (Keep in mind to replace the xxNOSPAMxx by an @ sign)
>
>		 (Keep in mind to remove the xxNOSPAMxx)
 

Revision 9
06 Oct 2010 - Main.JuliaSchenk
Line: 1 to 1
 
META TOPICPARENT name="WikiUsers"

Changed:
<
<

Julia Schenk - research associate

>
>

Julia Schenk (research associate)

 

Hello and welcome to my page
Line: 18 to 19
  Proceedings of the 2010 ICSE Workshop on Cooperative and Human Aspects of Software Engineering, May, 2010.

Teaching

Added:
>
>		 I am, respectively was, in charge of organising the exercise courses accompanying the following lectures as well as conducting some tutorials:

winter semester 2010/2011

summer semester 2010

winter semester 2009/2010

 

Contact Data

Line: 40 to 53
 

Email: julia.schenk@fu-berlinxxNOSPAMxx.de
Added:
>
>		 (Keep in mind to replace the xxNOSPAMxx by an @ sign)
 
Changed:
<
<		 Feel free to come along or to write me an email.
>
>		 Feel free to drop in or to write me an email. smile
Revision 8
06 Oct 2010 - Main.JuliaSchenk
Line: 1 to 1
 
META TOPICPARENT name="WikiUsers"
Deleted:
<
<
  \ No newline at end of file
Added:
>
>

Julia Schenk - research associate

Hello and welcome to my page

I'm a member of the Software Engineering Working Group at the Freie Universität Berlin.

Research

Publications

Stephan Salinger, Christopher Oezbek, Karl Beecher, Julia Schenk. Saros: An Eclipse Plug-in for Distributed Party Programming. Proceedings of the 2010 ICSE Workshop on Cooperative and Human Aspects of Software Engineering, May, 2010.

Teaching

Contact Data

Dipl. Inform. Julia Schenk

Institute of Computer Science

Software Engineering Working Group

Freie Universität Berlin

Takustr. 9, Room 008

14195 Berlin

Phone +49 30 838 75242

Email: julia.schenk@fu-berlinxxNOSPAMxx.de

Feel free to come along or to write me an email.
Revision 7
01 Feb 2010 - Main.LutzPrechelt
Line: 1 to 1
 
META TOPICPARENT name="WikiUsers"
  • Name: Julia Schenk
Deleted:
<
<
  \ No newline at end of file
Revision 6
06 Oct 2009 - Main.JuliaSchenk
Line: 1 to 1
 
META TOPICPARENT name="WikiUsers"
Changed:
<
<
>
>
  \ No newline at end of file
Revision 5
05 Oct 2009 - Main.JuliaSchenk
Line: 1 to 1
 
META TOPICPARENT name="WikiUsers"
Changed:
<
<
  • Workgroup: Student
>
>
  \ No newline at end of file
Revision 4
10 Aug 2008 - Main.JuliaSchenk
Line: 1 to 1
 
META TOPICPARENT name="WikiUsers"
Deleted:
<
<

Personal Preferences (details in System.Macros)
  • Horizontal size of text edit box:
    • Set EDITBOXWIDTH = 70
  • Vertical size of text edit box:
    • Set EDITBOXHEIGHT = 17
  • Style of text edit box. width: 99% for full window width (default), width: auto to disable.
    • Set EDITBOXSTYLE = width: 99%
  • Optionally write protect your home page: (set it to your WikiName)
    • Set ALLOWTOPICCHANGE =

Related topics

Code-Inspektion OpenCMS

  • Schwerpunktperspektive 1: Modularisierung, Redundanzen
  • Schwerpunktperspektive 2: Wartbarkeit, Dokumentation, Verständlichkeit
Codefragment:Zeile gefundener 'Defekt' wirklich 'Defekt'? Perspektive(n)
DriverManager.readPathInProject Es wird drei Mal das gleiche Codefragment (cacheKey)nacheinander an verschiedenen Stellen benutzt ganz sicher Modularisierung Redundanz Wartbarkeit
DriverManager Es wird keine Dokumentation zur Beschreibung des Zwecks oder der Funktionalität der Klasse DriverManager geliefert ganz sicher Dokumentation
DriverManager:6257 Funktion der Variable count ist nicht dokumentiert, bzw. nur aus dem Namen zu erschliessen. Jedoch nicht was die Variable zählt oder sonstiges unsicher Dokumentation Wartbarkeit Verständlichkeit
Ort: DriverManager: 77 / 85 extends Objekt bei einer Klasse explizit anzugeben --> SCHLECHT !!. Jedes Objekt erbt implizit von Objekt ganz sicher Redundanz
DriverManager: 6275 starker unverständlicher Slang im Kommentar verwendet wahrscheinlich Dokumentation Verständlichkeit
I_VfsDriver: 403 bei gleichen Methoden mit unterschiedlichen Parametern jedes Mal eine andere Reihenfolge der Parameter ganz sicher Code-Güte
CmsRequestContext.addSiteRoot(): 136 Überprüfung des Parameters auf NULL, wenn ja, dann einfach NULL zurückliefern anstatt eine Ausnahme zu werfen ganz sicher Ausnahme- und Randwertverhalten
ResourceTranslator.translateResource(): 142f Obwohl Loggermechanismus (Log4J) vorhanden ist wird auf einmal einfach eine Lognachricht auf die Standardausgabe geschrieben. Wer soll das lesen ?? ganz sicher Wartbarkeit Code-Güte- und Richtlinien
  • Durchschnittlich gefundene Defekte pro Zeitstunde: 5
 
Revision 3
07 Jun 2004 - schenkPCPOOL.MI.FU-BERLIN.DE
Line: 1 to 1
 
META TOPICPARENT name="WikiUsers"
Line: 25 to 25
 

  • Schwerpunktperspektive 1: Modularisierung, Redundanzen
  • Schwerpunktperspektive 2: Wartbarkeit, Dokumentation, Verständlichkeit
Changed:
<
<
Codefragment:Zeile gefundener 'Defekt' wirklich 'Defekt' ? Perspektive(n)
DriverManager.readPathInProject Es wird drei Mal das gleiche Codefragment (cacheKey) nacheinander an verschiedenen Stellen benutzt. ganz sicher

Modularisierung

Redundanz

Wartbarkeit
DriverManager Es wird keine Dokumentation zur Beschreibung des Zwecks oder der Funktionalität der Klasse DriverManager geliefert. ganz sicher Dokumentation
DriverManager:6257 Funktion der Variable count ist nicht dokumentiert, bzw. nur aus dem Namen zu erschliessen. Jedoch nicht was die Variable zählt oder sonstiges unsicher

Dokumentation

Wartbarkeit

Verständlichkeit
Ort: DriverManager:77/85 extends Objekt bei einer Klasse explizit anzugeben ist äusserst schlechter Javacode. Jedes Objekt erbt implizit von Objekt ganz sicher

Redundanz
DriverManager: 6275 starker unverständlicher Slang im Kommentar verwendet. wahrscheinlich

Dokumentation

Verständlichkeit
I_VfsDriver: 403 bei gleichen Methoden mit unterschiedlichen Parametern jedes Mal eine andere Reihenfolge der Parameter. ganz sicher

Code-Güte
CmsRequestContext.addSiteRoot():136 Überprüfung des Parameters auf NULL, wenn ja, dann einfach NULL zurückliefern anstatt eine Ausnahme zu werfen. ganz sicher

Ausnahme- und Randwertverhalten
ResourceTranslator.translateResource():142f

Obwohl Loggermechanismus (Log4J) vorhanden ist wird auf einmal einfach eine Lognachricht auf die Standardausgabe geschrieben.
Wer soll das lesen ??

ganz sicher

Wartbarkeit

Code-Güte- und Richtlinien

Durchschnittlich gefundene Defekte pro Zeitstunde: 5

 

>
>
Codefragment:Zeile gefundener 'Defekt' wirklich 'Defekt'? Perspektive(n)
DriverManager.readPathInProject Es wird drei Mal das gleiche Codefragment (cacheKey)nacheinander an verschiedenen Stellen benutzt ganz sicher Modularisierung Redundanz Wartbarkeit
DriverManager Es wird keine Dokumentation zur Beschreibung des Zwecks oder der Funktionalität der Klasse DriverManager geliefert ganz sicher Dokumentation
DriverManager:6257 Funktion der Variable count ist nicht dokumentiert, bzw. nur aus dem Namen zu erschliessen. Jedoch nicht was die Variable zählt oder sonstiges unsicher Dokumentation Wartbarkeit Verständlichkeit
Ort: DriverManager: 77 / 85 extends Objekt bei einer Klasse explizit anzugeben --> SCHLECHT !!. Jedes Objekt erbt implizit von Objekt ganz sicher Redundanz
DriverManager: 6275 starker unverständlicher Slang im Kommentar verwendet wahrscheinlich Dokumentation Verständlichkeit
I_VfsDriver: 403 bei gleichen Methoden mit unterschiedlichen Parametern jedes Mal eine andere Reihenfolge der Parameter ganz sicher Code-Güte
CmsRequestContext.addSiteRoot(): 136 Überprüfung des Parameters auf NULL, wenn ja, dann einfach NULL zurückliefern anstatt eine Ausnahme zu werfen ganz sicher Ausnahme- und Randwertverhalten
ResourceTranslator.translateResource(): 142f Obwohl Loggermechanismus (Log4J) vorhanden ist wird auf einmal einfach eine Lognachricht auf die Standardausgabe geschrieben. Wer soll das lesen ?? ganz sicher Wartbarkeit Code-Güte- und Richtlinien
  • Durchschnittlich gefundene Defekte pro Zeitstunde: 5
 
Revision 2
06 Jun 2004 - schenkPCPOOL.MI.FU-BERLIN.DE
Line: 1 to 1
 
META TOPICPARENT name="WikiUsers"
Deleted:
<
<
 
Line: 4 to 3
 
Deleted:
<
<
  • Phone:
 
  • Workgroup: Student
  • Comment: Pr-SWT SoSe04
Line: 22 to 20
 
Added:
>
>

Code-Inspektion OpenCMS

  • Schwerpunktperspektive 1: Modularisierung, Redundanzen
  • Schwerpunktperspektive 2: Wartbarkeit, Dokumentation, Verständlichkeit
    Codefragment:Zeile gefundener 'Defekt' wirklich 'Defekt' ? Perspektive(n)
    DriverManager.readPathInProject Es wird drei Mal das gleiche Codefragment (cacheKey) nacheinander an verschiedenen Stellen benutzt. ganz sicher

    Modularisierung

    Redundanz

    Wartbarkeit
    DriverManager Es wird keine Dokumentation zur Beschreibung des Zwecks oder der Funktionalität der Klasse DriverManager geliefert. ganz sicher Dokumentation
    DriverManager:6257 Funktion der Variable count ist nicht dokumentiert, bzw. nur aus dem Namen zu erschliessen. Jedoch nicht was die Variable zählt oder sonstiges unsicher

    Dokumentation

    Wartbarkeit

    Verständlichkeit
    Ort: DriverManager:77/85 extends Objekt bei einer Klasse explizit anzugeben ist äusserst schlechter Javacode. Jedes Objekt erbt implizit von Objekt ganz sicher

    Redundanz
    DriverManager: 6275 starker unverständlicher Slang im Kommentar verwendet. wahrscheinlich

    Dokumentation

    Verständlichkeit
    I_VfsDriver: 403 bei gleichen Methoden mit unterschiedlichen Parametern jedes Mal eine andere Reihenfolge der Parameter. ganz sicher

    Code-Güte
    CmsRequestContext.addSiteRoot():136 Überprüfung des Parameters auf NULL, wenn ja, dann einfach NULL zurückliefern anstatt eine Ausnahme zu werfen. ganz sicher

    Ausnahme- und Randwertverhalten
    ResourceTranslator.translateResource():142f

    Obwohl Loggermechanismus (Log4J) vorhanden ist wird auf einmal einfach eine Lognachricht auf die Standardausgabe geschrieben.
    Wer soll das lesen ??

    		ganz sicher

    Wartbarkeit

    Code-Güte- und Richtlinien

    Durchschnittlich gefundene Defekte pro Zeitstunde: 5

     

View topic | History: r17 < r16 < r15 < r14 | More topic actions...