Subversion Repositories DevTools

Rev

Rev 1293 | Blame | Last modification | View Log | RSS feed 

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Topic Information</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="The Codestriker Guide"
HREF="book1.html"><LINK
REL="UP"
TITLE="User's Guide"
HREF="c333.html"><LINK
REL="PREVIOUS"
TITLE="Topic Properties"
HREF="x624.html"><LINK
REL="NEXT"
TITLE="Topic Search"
HREF="x656.html"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Codestriker Guide: Version 1.9.3</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="x624.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 3. User's Guide</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="x656.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="TOPIC-INFORMATION"
>3.8. Topic Information</A
></H1
><P
>        From the "View Topic" page (see <A
HREF="x504.html#VIEW-TOPIC"
>Section 3.5.1</A
>),
        the "Topic Information" tab can be clicked to view and edit
        topic information.  An example screenshot of this page
            can be seen in <A
HREF="x637.html#FIGURE-TOPIC-INFORMATION"
>Figure 3-12</A
>.
        <DIV
CLASS="FIGURE"
><A
NAME="FIGURE-TOPIC-INFORMATION"
></A
><P
><B
>Figure 3-12. Topic Properties Screenshot</B
></P
><DIV
CLASS="MEDIAOBJECT"
><P
><IMG
SRC="topicinformation.png"></P
></DIV
></DIV
>
      </P
><P
>            This page is divided into four sections.  The "Comment
            Metrics" section provides an aggregate count for the
            number of comment threads with specific comment metric
            values.  The "Total" subsection displays the number of
            comment threads in the topic, followed by the total number
            of comments submitted.  This is followed by the "Topic
            Metrics" and "User Metrics" sections for this topic.  If
            there are additional metrics defined here via the
            Codestriker configuration file, the user will be able to
            update their values here.  The last part of the page is
            the "Activity Log", which provides an audit trail of all
            the important events that occurred in the topic's
            lifetime, such as creation and state changes.
      </P
><P
>         The Codestriker time metric is calculated by keeping
         timestamps of every refresh from the http server for the
         given topic. Now, just because you are not refreshing the
         topic does not mean that you are not looking at the topic.
         Codestriker will assume that you are looking at the topic for
         4 minutes after the last refresh. If you click on a topic,
         and close the browser, it is logged as 4 minutes. The
         situation is unavoidable unless you put a camera on the
         computer and keep track of how long people are sitting at
         their computer, awake, and looking at the browser window. If
         this is not acceptable, users of Codestriker have the option
         to ask the reviewers to directly log the time spent in the
         review. The direct logging can be enabled via
         <CODE
CLASS="VARNAME"
>$metrics_config</CODE
> variable in the
         <TT
CLASS="FILENAME"
>codestriker.conf</TT
> file. The Codestriker time
         metric is "free" metric, being that it does not require any
         extra interactions with the user to operate. The trade off is
         that the accuracy of the data may not be as good as the
         direct logging done by a disciplined team. However, if your
         team is not very disciplined and can't be trusted to put in
         100% accurate data, the Codestriker time metric will be
         better because it will not be biased by the reviewer's
         logging discipline.
      </P
><P
>        The code that deals with all of the this is in
        <TT
CLASS="FILENAME"
>lib/Codestriker/Model/Metrics.pm</TT
>, in
        the <TT
CLASS="FILENAME"
>calculate_topic_view_time</TT
> method.
      </P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="x624.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="book1.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="x656.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Topic Properties</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="c333.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Topic Search</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>