Use Guide - Use


1 The Interface of SEE
  1.1 General Description
  1.2 Inputting Data
  1.3 Listing Data
  1.4 Interface Setup
  1.5 Interface Theme
2 Information Manufacturing in SEE
  2.1 The Data Constraints in SEE
  2.2 The Special Strings in SEE
  2.3 Adding Data
  2.4 Inserting Data
  2.5 Modifying Data
  2.6 Copying Data
  2.7 Importing Data
  2.8 Removing Data
  2.9 Querying Data
  2.10 Statistic
  2.11 Batch Modification
3 Data Audit in SEE
  3.1 Querying the Audit Data
  3.2 Showing Audit Records by Data List
  3.3 Showing Audit Records by Time
4 Data Exporting in SEE
5 Show-setup in SEE
6 Condition Setup in SEE
7 Statistic in SEE
  7.1 Count
  7.2 Cross Count
  7.3 Trend
  7.4 Condition Setup for Statistic
  7.5 Saving the Statistic Setup
8 Personal Message

1 The Interface of SEE

1.1 General Description

   SEE is a web application, so you can use the window's functions in the web-browser, such as Forward, Backward, Print, Save As, Open the Link in A New Window, Copy Text, and Paste Text etc. These things are not introduced here.
   To use functions of SEE, your web-browser need:

  • Supports javscript 1.0, cookie 1.0, and css 1.0
  • The ideal display resolution to show interfaces of SEE is: 1024 * 768

       The following are the general functions in the SEE interfaces:

  • Resting your mouse on a field name, you may get some description about the field (If there is the definition in its structure.)
  • Moving your mouse to a link, a button, or a picture, the icon usually becomes a hand, which indicates this is a click-resource. But to the pictures and underlined texts without this character, please try to click them too.
  • In the status bar of the web-browser, some values will be shown: current user, current project, current information-operation, the information description (If defined.)

    1.2 Inputting Data

       When you add or modify data:
  • The red fields are members of key group. They should be unique and can not be same to an existent record. The page script will judge this automatically.
  • The blue fields can not be null. The page script will judge this automatically.
  • To copy data, you should modify at least one red field to save it as a new valid record and not to cover the original data. The page script will judge this automatically.
  • To time or date field, you'd better click the beside button "Format" to get the valid format. If the values are not in valid format of time or date, you may not get reasonable result when you sort, query, or statistic them.

    1.3 Listing Data

       When you execute inserting, copying, modifying, removing, querying, auditing, the system will list all records for you at first. In these pages:
  • If you click a field name in the table head, records will be sorted according to this field. Clicking again will give you the sort result in reverse direction. If there is a ">" or "<" beside a field name, this indicates that data are sorted by this field now.
  • At the bottom of the data list, there is a page-area, which shows the total size of the data and current numbers of the data. In this area, user also can set the page size (This set will continue in effect), move to the last page, move to the next page, or jump to a special page.
  • At the bottom of the data list, there is a show-setup area, which shows the current values of the data style, showing items, sort item and sort direction. When clicking the button "Show Setup", user will enter the show-setup interface to set these parameters. Please refer to Show-setup in SEE.
  • At the bottom of the data list, there is a query-setup area, which shows the current query conditions. When clicking the button "Query Setup", user will enter the query-setup interface to set query conditions. Please refer to Query-setup in SEE.
  • At the top of the data list, there may be a color bar.

       Tip 1: By sorting and querying, you can find your data records conveniently.
       Tip 2: Before do any operation which will changes data, if you sort them at first, the data will be saved in the current sorting order.

    1.4 Interface Setup

       User can click the button "Setup" at the bottom of the interface at any time to set the following parameters, which will go into effect immediately and keep in effect in current login:

    Setup


    Interface Style : Default Style Beautiful Flowers
    Interface Theme : Default Theme
    Data List Style : Table Form
    Page Size :
    Default Project :


    System is installed in English. So it has init accounts and init data in English.
    Language selection is for showing interface in different languages.


       They are:

  • Interface Style. It is the design of the pictures and text attributes, such as size, color, font, for the entire system. There are two sets now. User can design and add some by yourself. Its adding is "Green", that is you need only copy files to the special directory. Please refer to the "Source Code Explanation".
  • Interface Theme. It is how to show the function buttons in the interface in different levels. There is only default one. User can modify and add by yourself. The super manager can click the button "System" on the top of the interface, then select the "Interface Theme" at the left page to manage it. Modifying will go into effect immediately.
  • Data List Style. There are two styles now. They are "Table Style" and "Form Style". The "Table Style" refers to that each line will show one record and each column will show one field. The "Form Style" refers to that records are shown one after another and each line will show a field.
  • Page Size. It is the total number of the records shown in every page.
  • Default Project. It is the default value when you input a field that refers to the "Project". It has little use now.
  • The switch buttons for languages. There are two encodings in SEE. One of them is for data saving and the other is for interface. All data are saved in UTF-8 in SEE now, while user can switch interface into different languages at any time.

       The above parameters can be set in the user's private information too. Two ways have the following differences: the parameters in user's private information will be used at user's every login while parameters in the function "Setup" will be used only at current login, And the modifying in the former will go into effect at user's next login while the modifying in the latter will go into effect immediately.

    1.5 Interface Theme

       It is how to show the function buttons in the interface in different levels:
  • The functions of the first level are shown in the top of the interface.
  • The functions of the second level are shown in the left of the interface.
  • The funcitons of the third level are shown on the top of the middle page.

       The following is the default interface theme:
    The first level (Top)The second level (Left)The third level (Middle top)
    System
    Init Config
    Interface Theme
    User
    Role Definition
    System Role
    Data Role
    Data Privilege
    System Role Acl
    Data Role Acl
    Data User Acl
    Public Data
    Data Audit
    Show Setup
    Condition Setup
    Statsitic Setup
    Upload Manage
    Translation
    Simlified Chinese
    Traditional Chinese
    English
    Speed Testing
    Login
    Project
    Project Planning
    Project Register
    Project Stage
    Project Task
    Project Role
    Risk Analysis
    Project Tracking
    Weekly Report
    Working Log
    Data Collection
    Deviation Handling
    Check List
    Check Item
    Check Result
    Ineligible Item
    Configuration
    Code Register
    Document Register
    Review
    Code Review
    Document Review
    Software
    Software Requirement
    Testing Requirement
    Testing Procedure
    Change Request
    Testing Result
    Problem Report
    Common
    Personal Message
    Meeting Summary
    Contact Way
    Share Resource
    Information
    Manual

       In the middle of interface, pages linked to the function buttons of all levels will be opened. This area is used mainly to show the pages for manufacturing information. On the top of the information manufacturing pages, there is a bar including operation buttons.

       In the bottom of the interface, there are some function buttons used usually. They are: user's private information, interface setup, meeting summary, contact way, problem report, working log, login, use guide, logout, contact to the author.

       Now only the default theme is provided. User can modify or add some by yourself. Please refer to the "Customing SEE".

       Except for the buttons in the top and bottom, user can only see the function buttons which she/he is allowed to use.

    2 Information Manufacturing in SEE

       By selecting the three levels' function menus, user can visit the manufacturing page for some particular information. In the top of the page, there is the following data menu:

    2.1 The Data Constraints in SEE

       "The Data Constraints" is that the user's data should not include some special chars or strings, which will be filtered automatically.

       At present, there is not any data constraint.

    2.2 The Special Strings in SEE

       The special strings are used in SEE to manufacture data.
       User had better not use special strings of SEE in your data.

       At present, all special strings in SEE are listed as following:
    Special StringUsage
    -99999999Null for integer
    :c:e:q-c:e:q:"Equal To" in condition
    :c:n:e-c:n:e:"Not Equal To" in condition
    :c:g:t-c:g:t:"Greater Than" in condition
    :c:l:s-c:l:s:"Less Than" in condition
    :c:s:t-c:s:t:"Start With" in condition
    :c:e:d-c:e:d:"End With" in condition
    :c:i:d-c:i:d:"Include" in condition
    :c:n:i-c:n:i:"Not Include" in condition
    :m:s-m:s:Splitter for several data
    :c:i:s-c:i:s:Splitter in condition
    :c:a:d-c:a:d:"And" in condition
    :a:a:d-a:a:d:Splitter for statistic
    SEE-count-total"Total" in statistic. Do not use this as field name.
    SEE-count-other"Others" in statistic. Do not use this as field name.
    SEE-count-null"Null" in statistic. Do not use this as field name.
    see_password_null"Null" for password. Do not use this as password value.
    see_password_not_modify"Not Modified" for password. Donot use this as password value.
    :-:Splitter for several values
    .h.p-h.p.Splitter for name-value of hash
    :s:m-s:m:Unknown splitter
    :g:t-g:t:">" in data will be saved as this string. When show data, ">" is showed.
    :l:s-l:s:"<" in data will be saved as this string. When show data, "<" is showed.
    :v:h-v:h:Splitter for value
    :a:d-a:d:"&" in data will be saved as this string. When show data, "&" is showed.
    :r:t-r:t:New line in data will be saved as this string. When show data, new line will be added.
    _aaaa_Splitter for the matrix field name. User should not use it in your field name.
    SEE_matrix_valueField name for matrix value. User should not use it as your field name.
    a:m:s-a:m:sSplitter for audit value

    2.3 Adding Data

       In the data management page, when click the "Add" page-tab, you will see the page for adding data.
       New data will always be added at the end of the current data list.
       Refer to
    section 1.2 to see the notice.

    2.4 Inserting Data

       In the data management page, when click the "Insert" page-tab, you will see the page for inserting data.
       New data will be added before the selected data line.
       Refer to
    section 1.2 and section 1.3 to see the notice.

    2.5 Modifying Data

       In the data management page, when click the "Modify" page-tab, you will see the page for modifying data.
       Refer to
    section 1.2 and section 1.3 to see the notice.

    2.6 Copying Data

       In the data management page, when click the "Copy" page-tab, you will see the page for copying data.
       The initial values of the new data are just the copy of the values of selected data line.
       Refer to
    section 1.2 and section 1.3 to see the notice.

    2.7 Importing Data

       In the data management page, when click the "Import" page-tab, you will see the page for importing data.
       In the default privilege model, only the super manager and data managers can execute the importing.
       Refer to
    section 4 of the "Manage".

    2.8 Removing Data

       In the data management page, when click the "Remove" page-tab, you will see the page for removing data.
       When click on one data line or click the Remove button before one data line, you can remove this line directly. User can also select several lines to remove.
       Below the data lines, the buttons "All in Page" and "All Not" are for selecting the data lines in the current page, and the button "Remove All" is for removing all of data lines, not only lines in the current page.
       In the default privilege model, only the super manager and data managers can execute the removing.
       Refer to
    section 1.2 and section 1.3 to see the notice.

    2.9 Querying Data

       In the data management page, when click the "Query" page-tab, you will see the page for querying data.
       In fact, there is also the button "Query Setup" in other pages. The querying page only has the particular button "Export" compared to other pages. And only when there are some data lines, this button will be shown. Refer to
    section 4 to see more about exporting.
       Refer to section 1.2 and section 1.3 to see the notice.
       Refer to section 6 to see more about query-setup.
       When data is matrix table, there will be a selection in the top of the page for user to switch between main data and matrix data.

    2.10 Statistic

       In the data management page, when click the "Statistic" page-tab, you will see the page for statistic.
       Now "Count", "Cross Count" and "Trend" types of statistic methods are provided.
       The produced pictures are in jpg format. They are temporary files and system will delete them after 5 minutes.
       Refer to
    section 7 to see more about statistic.
       The trend tab will be shown only when the information has some date/time field(s) as well as number (integer/float) field(s).

    2.11 Batch Modification

       In the data management page, when click the "Batch Modify" page-tab, you will see the page for batch modifying data.
       Two steps will be needed. The first step is selecting the data to be modified, and the second step is inputing the values to be updated.

       The matrix fileds can be modifed in the batch way.
       Single keyword and password fileds can not be modified in the batch way.
       Below the data lines, the buttons "All in Page" and "All Not" are for selecting the data lines in the current page, and the button "Modify All" is for modifying all of data lines, not only lines in the current page.

       In the default privilege model, only the super manager and data managers can execute the batch modifying.
       Refer to
    section 1.2 and section 1.3 to see the notice.

    3 Data Audit in SEE

    3.1 Querying the Audit Data

       In the default privilege model, all of general users can query the audit records.

       A general user can not access the management page of the audit data, but can visit the audit records of a certain information by clicking the button "Audit" on the top of the management page of the corresponding information. That is the audit querying is context-sensitive.
       For example, in the management page of the "Problem Report", click the button "Audit", then the system will list all audit records about the "Problem Report".

       If the current user is not the super manager, any audit record about the super manager will be filtered automatically.

       In the audit page, user can select to show audit records list "by data" or "by time".

    3.2 Showing Audit Records by Data List

       "By data" to show audit record, is that the system lists information's data and user selects a data to show all audit records about this data. An example is following:

    Problem Report - Audit


    By Data By Time
    Status: Reviewed Fixed Commit Closed Denied Tested Defer Others
    - Project Type Object Status Security Priority Title Assigned to Last Changed Time
    Audit - Bug Code Denied Medium Medium try - May 3, 2004 2:57:23 PM CST
    Audit - Bug Code Commit Medium Medium lulu - May 3, 2004 2:57:46 PM CST

    Total Count : 2     Current Number : 1 - 2 Every Page : Ok Jump to Page : Ok All

    Show Setup Style:Table Item:[Project, Type, Object, Status, Security, Priority, Title, Assigned to, Last Changed Time]

       Click the button "Audit" beside a data line, you will get all audit records about this data:

    Problem Report - Audit


    The following is corresponding audit records:
    Identify : May 3, 2004 2:57:36 PM CST-superseer
    Data : Problem Report
    Operation : Modify
    Keys : {Configuration Code=PR-s}
    Old Values : {Status=Commit, Last Changed Time=May 3, 2004 2:56:22 PM CST}
    New Values : {Status=Denied, Last Changed Time=May 3, 2004 2:57:23 PM CST, Comment=r}
    Who : superseer
    When : May 3, 2004 2:57:36 PM CST
    Where : 127.0.0.1
    Result : Successful

    Identify : May 3, 2004 2:56:51 PM CST-superseer
    Data : Problem Report
    Operation : Add
    Keys : {Configuration Code=PR-s}
    Old Values : {Description=r, Commit Time=May 3, 2004 2:56:22 PM CST, Type=Bug, Reporter=superseer, Last Changed Time=May 3, 2004 2:56:22 PM CST, Configuration Code=PR-s, Priority=Medium, Security=Medium, Title=try, Object=Code, Status=Commit, Last Changed Person=superseer, Commit Person=superseer}
    New Values :
    Who : superseer
    When : May 3, 2004 2:56:51 PM CST
    Where : 127.0.0.1
    Result : Successful


    3.3 Showing Audit Records by Time

       "By time" to show audit record, is that the sytem lists audit records according to time. An example is following:

    Problem Report - Audit


    By Data By Time
    - Data Operation Who When Where Result
    Show Problem Report Remove superseer May 3, 2004 3:07:12 PM CST 127.0.0.1 Successful
    Show Problem Report Add superseer May 3, 2004 2:57:57 PM CST 127.0.0.1 Successful
    Show Problem Report Modify superseer May 3, 2004 2:57:36 PM CST 127.0.0.1 Successful
    Show Problem Report Add superseer May 3, 2004 2:56:51 PM CST 127.0.0.1 Successful

    Total Count : 4     Current Number : 1 - 4 Every Page : Ok Jump to Page : Ok All

    Show Setup Style:Table Item:[Data, Operation, Who, When, Where, Result]

       Click the button "Show" beside a line, you will get all content of this audit record:

    Problem Report - Audit


    The following is corresponding audit records:
    Identify : May 3, 2004 2:57:36 PM CST-superseer
    Data : Problem Report
    Operation : Modify
    Keys : {Configuration Code=PR-s}
    Old Values : {Status=Commit, Last Changed Time=May 3, 2004 2:56:22 PM CST}
    New Values : {Status=Denied, Last Changed Time=May 3, 2004 2:57:23 PM CST, Comment=r}
    Who : superseer
    When : May 3, 2004 2:57:36 PM CST
    Where : 127.0.0.1
    Result : Successful



    4 Data Exporting in SEE

       In the query page of any information, if current information has any record, a "Export" button will be in the top.

       Click the button "Export", the system will pop the following window to let user set the parameters of exporting:

    Problem Report - Export


    The sorting of this exporting will use the same setup of the current page. If html format will be exported, the color and data-style of the current page will be also used.
    If want to store data, please select the All Items
    To html format, UTF-8 is always used and the setup of charset does not work.

    Format
    txt xml html

    Data
    All Current

    Items
    All Current

    Charset
    iso-8859-1 gb2312 big-5 UTF-8


       When txt or xml is selected, the following page will be shown:

    Problem Report - Export


    This is a temporary file. System will delete it in 5 minutes. So please open or save it in time.
    Open

       If the charset is not suitable, an error will happen.
       Save as UTF-8 will always success.

    5 Show-setup in SEE

       In the data list page of any information, there is button "Show-Setup".

       Click the button, the system will return the following page: (This example is about the "Problem Report".)

    Problem Report - Show Setup


    Select or maintain the following saved show-setup: Maintenance Use

    By type By object    


    Set or add new show-setup directly

    Title: Add Current Show Setup:By object Modify Remove
    Show
    Item Configuration Code Project Title Status Type Object Security Priority Description Assigned to Reporter Comment Commit Person Commit Time Last Changed Person Last Changed Time All All Not

    Sort
    Item Configuration Code Project Title Status Type Object Security Priority Description Assigned to Reporter Comment Commit Person Commit Time Last Changed Person Last Changed Time Null
    Order Ascending Descending

    Color
    Configuration Code Project Title Status Type Object Security Priority Description Assigned to Reporter Comment Commit Person Commit Time Last Changed Person Last Changed Time
    Value Color
    Others

    Data List Style
    Table Form

    FFDDDD     
    FFDD99     
    FFFF99     
    DDFFDD     
    DDFFFF     
    DDDDFF     
    FFDDFF     
    EEEEEE     


       In the above page:

  • The titles of the show-setups saved by user and the super manager are listed.
  • If "Maintain" is selected, when click a title, the page will be refreshed to let user modify or remove the corresponding show-setup.(As the above example)
  • If "Use" is selected, when click a title, the original information manufacturing page will be returned with the effect of the corresponding show-setup.
  • If user enter the title and click the button "Add", the current values of the parameters will be saved as the new show-setup. Its title will be shown in the top refreshed list.
  • Only the super manager can modify or remove her/his show-setups. Others can only use them.

       If user click the button "OK" at the bottom of the page, the system will return the original information manufacturing page with the effect of the current values of the parameters. User can use this method to set the show parameters temporarily without saving them.

    6 Condition Setup in SEE

       In the data list page of any information, there is button "Condition".

       Click the button, the system will return the following page: (This example is about the "Problem Report - Audit".)

    Problem Report - Condition Setup


    Use or maintain one of the following saved query-setups: Maintenance Use

    cond1 cond2    


    Set directly or maintain the query-setups

    Title: Current Query Setup:cond2

    Lines in the following tables have the relationship "And", and these tables have the relationship "Or".

    Item operator Value
    Status Equal To Fixed
    Last Changed Time Less Than July 8, 2004 7:41:39 PM CST

    Or

    Item operator Value
    Status Equal To Tested

    The following are current base conditions. Whatever Your new conditions are, they will be checked at first.

    Item operator Value
    Data Equal To Problem Report

       In the top of the page: (If there is no any query-setup saved , these information will not be shown)

  • The titles of the query-setups saved by user and the super manager are listed.
  • If "Maintain" is selected, when click a title, the page will be refreshed to let user modify or remove the corresponding query-setup.(As the above example)
  • If "Use" is selected, when click a title, the original information manufacturing page will be returned with the effect of the corresponding query-setup.
  • If user enter the title and click the button "Add", the current conditions will be saved as the new query-setup. Its title will be shown in the top refreshed list.
  • Only the super manager can modify or remove her/his query-setups. Others can only use them.

       If there is no "base condition" in the original page, the information in the bottom of the page will not be shown.

       In the above page, use can:

  • Input "title" and click "Add" button to save the current query condition.
  • Click "OK" button to make SEE show data lines according to the current query condition.
  • Click "Or" button to make SEE pop out the query-setup window for adding new condition which has the relationship "Or" with the current condition.
  • Click "Clear" button to remove the current condition.
  • Click "Cancel" button to return back to original page.

       When click "Or" button or "Setup" button, SEE will pop out a window for you to setup the new query condition: (This example is about the "Problem Report".)

    Data Audit - Query Setup


    The following conditions have the relationship "And".
    When use the operator "Greater Than" or "Less Than ", data will be compared according to their types, such as date, time, integer, and string.
    Configuration Code
    operator : Equal To Not Equal To Greater Than Less Than Start With End With Include Not Include
    Value :
    Project
    operator : Equal To Not Equal To Greater Than Less Than Start With End With Include Not Include
    Value :
    Title
    operator : Equal To Not Equal To Greater Than Less Than Start With End With Include Not Include
    Value :
    Status
    operator : Equal To Not Equal To Greater Than Less Than Start With End With Include Not Include
    Value : Commit Reviewed Fixed Tested Closed Defer Denied
    Type
    operator : Equal To Not Equal To Greater Than Less Than Start With End With Include Not Include
    Value : Bug Advice User Feedback Enhancement Not Implemented
    Object
    operator : Equal To Not Equal To Greater Than Less Than Start With End With Include Not Include
    Value : Code Database Data Testing Design Requirement Document
    Security
    operator : Equal To Not Equal To Greater Than Less Than Start With End With Include Not Include
    Value : Very Hign High Medium Low Very Low
    Priority
    operator : Equal To Not Equal To Greater Than Less Than Start With End With Include Not Include
    Value : Very Hign High Medium Low Very Low
    Description
    operator : Equal To Not Equal To Greater Than Less Than Start With End With Include Not Include
    Value :
    Assigned to
    operator : Equal To Not Equal To Greater Than Less Than Start With End With Include Not Include
    Value :
    Reporter
    operator : Equal To Not Equal To Greater Than Less Than Start With End With Include Not Include
    Value :
    Comment
    operator : Equal To Not Equal To Greater Than Less Than Start With End With Include Not Include
    Value :
    Attachment
    operator : Equal To Not Equal To Greater Than Less Than Start With End With Include Not Include
    Value :
    Commit Person
    operator : Equal To Not Equal To Greater Than Less Than Start With End With Include Not Include
    Value :
    Commit Time
    operator : Equal To Not Equal To Greater Than Less Than Start With End With Include Not Include
    Value :
    Last Changed Person
    operator : Equal To Not Equal To Greater Than Less Than Start With End With Include Not Include
    Value :
    Last Changed Time
    operator : Equal To Not Equal To Greater Than Less Than Start With End With Include Not Include
    Value :


       In SEE, any comparing or sorting is according to the data type.
       For example, to "123" and "23", if compare them as string type, "23" is greater than "123", and if compare them as integer type, "123" is greater than "23".

    7 Statistic in SEE

    7.1 Count

       "Count" is that gets numbers and rates of different values of the special data item:

  • User can select any data item to make the counting.
  • User can input special value list of the data item for make the counting. If the value of the data item is out of the value list which user defines. it will be counted as the "others".
  • If user does not input the value list of the data item, SEE will count all values of this item automatically.
  • Null values will also be counted.
  • User can select the output chart types which are Pie Chart and Histogram (jpg files). The number of values in the charts is limited, but the larger counts will always shown.

       The following is an example setup page of counting: (Counting all values of "Security" automatically)

    Problem Report - Statistic


    Count Cross Count
    Count
    Item Configuration Code Project Title Status Type Object Security Priority Description Assigned to Reporter Comment Attachment Commit Person Commit Time Last Changed Person Last Changed Time
    Value
    Input values which will be counted, split them by ":-:". If need system count all values automatically, donnot input anything.
    Image Pie Chart Histogram


       The following is the output which is produced automatically:

    Security Count Rate
    Medium 22 28.57 %
    Very High 17 22.07 %
    Low 16 20.77 %
    High 12 15.58 %
    Very Low 10 12.98 %
    Total Count 77 100 %

    7.2 Cross Count

       "Cross Count" is that gets numbers and rates of different values of two special data items:

  • User can select any two data items to make the cross counting.
  • User can input special value list of the two data items for make the cross counting. If the value of the data item is out of the value list which user defines. it will be counted as the "others".
  • If user does not input the value list of the data item, SEE will count all values of this item automatically.
  • Null values will also be counted.
  • User can select the output chart types which are Cross Pie Chart, Cross Histogram, and Rate Histogram (jpg files). The number of values in the charts is limited, but the larger counts will always shown.
  • User can select whether SEE shows data in the histograms or not.

       The following is an example setup page of "Cross Count": (Cross counting all values of "Status" and "Security" automatically)

    Problem Report - Statistic


    Count Cross Count
    Cross Count
    Item Configuration Code Project Title Status Type Object Security Priority Description Assigned to Reporter Comment Attachment Commit Person Commit Time Last Changed Person Last Changed Time
    Value
    Input values which will be counted, split them by ":-:". If need system count all values automatically, do not input anything.
    Cross Item Configuration Code Project Title Status Type Object Security Priority Description Assigned to Reporter Comment Attachment Commit Person Commit Time Last Changed Person Last Changed Time
    Value
    Input values which will be counted, split them by ":-:". If need system count all values automatically, do not input anything.
    Image Cross Pie Chart Cross Histogram Rate Histogram
    Show Value : Yes No


       The following is the output which is produced automatically:

    Security \ Status Fixed Tested Commit Defer Reviewed Denied Total Count Rate
    Low 9 2 2 1 1 1 16 20.77 %
    Medium 8 7 4 0 2 1 22 28.57 %
    Very Hign 4 2 7 1 2 1 17 22.07 %
    High 2 3 4 2 1 0 12 15.58 %
    Very Low 2 1 3 0 2 2 10 12.98 %
    Total Count 25 15 20 4 8 5 77 100.00 %
    Rate 32.46 % 19.48 % 25.97 % 5.19 % 10.38 % 6.49 % 100% 

    7.3 Trend

       "Trend" is that one chart shows the data's changing with time's going.
       So the trend tab will be shown only when the information has some date/time field(s) as well as number (integer/float) field(s).

  • User need select one date/time field.
  • User can select several number fields.
  • User can input the start time or end time. If not input, system will use the earliest/latest time inside the data.

       The following is an example setup page of trend:

    Weekly Report - Statistic


    Count Cross Count Trend
    Trend
    Time Commit Time Last Changed Time
    Plan-Start Date Plan-End Date Actual-Start Date Actual-End Date
    Value
    Plan-Staff Number Plan-Size Plan-Effort Plan-Cost Actual-Staff Number Actual-Size Actual-Effort Actual-Cost
    Start Time
    If want to use the earliest time, please do not input anything.
    End Time
    If want to use the latest time, please do not input anything.


       The following is an example result page of Trend Chart:

    "Actual-Start Date" "Plan-Effort" "Plan-Cost" "Actual-Effort" "Actual-Cost"
    August 23, 2004 50 150 45 150
    August 30, 2004 60 150 70 170
    September 7, 2004 60 150 65 140
    September 14, 2004 50 150 55 160
    September 21, 2004 80 180 77 160
    September 28, 2004 80 180 85 180
    October 3, 2004 110 200 90 180
    October 10, 2004 100 180 95 160
    October 17, 2004 110 180 115 190
    October 21, 2004 120 200 125 220
    October 27, 2004 70 180 75 160

    7.4 Condition Setup for Statistic

       There is always a button "Condition" in the bottom of statistic pages. User can set the conditions to filter data and then make statsitic based on the filtered data.
       Refer to
    section 6 to see how to setup conditions.

    7.5 Saving the Statistic Setup

       User can save the conditions and parameters of the current statistic, so that you can use them directly next time.
       Please refer to
    Show-Setup or Condition Setup. The setups of statistic can also be added, modified and removed.

    8 Personal Message

       The management rules of PM are the following:

  • User can only query the messages sent by and sent to herself/himself. And user can only remove the messages sent to herself/himself.
  • After a user read a message sent to her/him, SEE will mark it as "have_read" automatically.
  • The number of new arrived messages will be shown in the interface.
  • The content of PM will not be record in audit records.

    https://sourceforge.net/projects/chong2see/