<?xml version="1.0" encoding="utf-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:dc="http://purl.org/dc/elements/1.1/"
         xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
         xmlns="http://purl.org/rss/1.0/">




    



<channel rdf:about="http://www.ics.hawaii.edu/research/tech-reports/ics-department-tech-reports/RSS">
  <title>ICS Department Tech Reports</title>
  <link>http://www.ics.hawaii.edu</link>
  
  <description>
    
       
       
  </description>
  
  
  
            <syn:updatePeriod>daily</syn:updatePeriod>
            <syn:updateFrequency>1</syn:updateFrequency>
            <syn:updateBase>2007-08-22T02:30:40Z</syn:updateBase>
        
  
  <image rdf:resource="http://www.ics.hawaii.edu/logo.jpg"/>

  <items>
    <rdf:Seq>
        
            <rdf:li rdf:resource="http://www.ics.hawaii.edu/research/tech-reports/terminals.pdf"/>
        
        
            <rdf:li rdf:resource="http://www.ics.hawaii.edu/research/tech-reports/LaneTableMethod.pdf"/>
        
        
            <rdf:li rdf:resource="http://www.ics.hawaii.edu/research/tech-reports/Real%20time%20evaluation%20of%20LR%20contexts.pdf"/>
        
        
            <rdf:li rdf:resource="http://www.ics.hawaii.edu/research/tech-reports/RobertsonVatrapuAbraham.pdf"/>
        
        
            <rdf:li rdf:resource="http://www.ics.hawaii.edu/research/tech-reports/ics2008-09-15.pdf"/>
        
        
            <rdf:li rdf:resource="http://www.ics.hawaii.edu/research/tech-reports/chu-brewer-joseph.pdf"/>
        
        
            <rdf:li rdf:resource="http://www.ics.hawaii.edu/research/tech-reports/ICS2008-05-01.pdf"/>
        
        
            <rdf:li rdf:resource="http://www.ics.hawaii.edu/research/tech-reports/ThesisMarkFinal.pdf"/>
        
        
            <rdf:li rdf:resource="http://www.ics.hawaii.edu/research/tech-reports/Streveler%20Sherlock%20HMIS%20RAP%20Final.pdf"/>
        
        
            <rdf:li rdf:resource="http://www.ics.hawaii.edu/research/tech-reports/ICS2007-11-02.pdf"/>
        
        
            <rdf:li rdf:resource="http://www.ics.hawaii.edu/research/tech-reports/ICS2007-11-01.pdf"/>
        
        
            <rdf:li rdf:resource="http://www.ics.hawaii.edu/research/tech-reports/ICS2006-12-03.pdf"/>
        
        
            <rdf:li rdf:resource="http://www.ics.hawaii.edu/research/tech-reports/ICS2006-12-02.pdf"/>
        
        
            <rdf:li rdf:resource="http://www.ics.hawaii.edu/research/tech-reports/ICS2006-12-01.pdf"/>
        
        
            <rdf:li rdf:resource="http://www.ics.hawaii.edu/research/tech-reports/ICS2005-08-02.pdf"/>
        
    </rdf:Seq>
  </items>

</channel>

    <item rdf:about="http://www.ics.hawaii.edu/research/tech-reports/terminals.pdf">        <title>ICS2009-06-03:  Evaluating Terminal Heads Of Length K - D. Pager</title>        <link>http://www.ics.hawaii.edu/research/tech-reports/terminals.pdf</link>        <description>ABSTRACT.  This paper presents an alternative algorithm for finding the terminal heads of length k of a given string in a given context-free grammar for given k.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>pager</dc:creator>        <dc:rights></dc:rights>                <dc:date>2009-06-25T06:03:29Z</dc:date>        <dc:type>File</dc:type>    </item>
    <item rdf:about="http://www.ics.hawaii.edu/research/tech-reports/LaneTableMethod.pdf">        <title>ICS2009-06-02:  The Lane Table Method Of Constructing LR(1) Parsers - D. Pager</title>        <link>http://www.ics.hawaii.edu/research/tech-reports/LaneTableMethod.pdf</link>        <description>ABSTRACT.   The first practical application of the LR algorithm was by [1] for the LALR(1) subset of LR(1) grammars.  In [2] an efficient method of producing an LR(1) parser for all LR(1) grammars was described which involves resolving conflicts at states of the LR(0) parsing machine, employing two phases.  In Phase 1 the contexts of the productions involved in conflicts are evaluated by a process described there called “lane tracing”.   If conflicts cannot be resolved by these means, then in Phase 2 the parts of the machine involved in lane tracing are regenerated, avoiding the combination of states that potentially lead to conflicts.   Other works along the same lines include [4, 5].  The criterion employed in [2] for determining whether or not states may be combined was that of weak compatibility, as defined in [3].  In this paper we describe an alternative method for determining whether states can be combined.  According to testing by [6] this method requires less computation.  It is also more efficient. when extending the method from LR(1) to LR(k) parsing as described in [7] where very large grammars may be used for the purposes of natural language translation.   Taken together with Phase 1, this new method of Phase 2 will, as before, produce a conflict-free LR(1) parser for all LR(1) grammars.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>pager</dc:creator>        <dc:rights></dc:rights>                <dc:date>2009-07-03T22:46:53Z</dc:date>        <dc:type>File</dc:type>    </item>
    <item rdf:about="http://www.ics.hawaii.edu/research/tech-reports/Real%20time%20evaluation%20of%20LR%20contexts.pdf">        <title>ICS2009-06-01: Resolving LR Type Conflicts at Translation or Compile Time - D. Pager</title>        <link>http://www.ics.hawaii.edu/research/tech-reports/Real%20time%20evaluation%20of%20LR%20contexts.pdf</link>        <description>ABSTRACT.  The paper considers circumstances in which it is advantageous to resolve reduce-reduce conflicts at compile time, rather than at compiler-construction time.  The application considered is that of translating English to one of the Romance languages, such as Italian, where adjectives and nouns have distinctive forms depending on their gender.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>pager</dc:creator>        <dc:rights></dc:rights>                <dc:date>2009-07-03T22:49:17Z</dc:date>        <dc:type>File</dc:type>    </item>
    <item rdf:about="http://www.ics.hawaii.edu/research/tech-reports/RobertsonVatrapuAbraham.pdf">        <title>ICS2008-12-01: Note Taking and Note Sharing While Browsing Campaign Information - S. Robertson, R. Vatrapu, G. Abraham</title>        <link>http://www.ics.hawaii.edu/research/tech-reports/RobertsonVatrapuAbraham.pdf</link>        <description>Abstract: Participants were observed while searching and browsing the internet for campaign information in a mock-voting situation in three online note-taking conditions: No Notes, Private Notes, and Shared Notes.  Note taking significantly influenced the manner in which participants browsed for information about candidates. Note taking competed for time and cognitive resources and resulted in less thorough browsing. Effects were strongest when participants thought that their notes would be seen by others. Think-aloud comments indicated that participants were more evaluative when taking notes, especially shared notes. Our results suggest that there could be design trade-offs between e-Democracy and e-Participation technologies.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>scottpr</dc:creator>        <dc:rights></dc:rights>                <dc:date>2009-06-22T08:10:20Z</dc:date>        <dc:type>File</dc:type>    </item>
    <item rdf:about="http://www.ics.hawaii.edu/research/tech-reports/ics2008-09-15.pdf">        <title>ICS2008-09-01: Resource Allocation using Virtual Clusters - M. Stillwell, D. Schanzenbach, F. Vivien, H. Casanova</title>        <link>http://www.ics.hawaii.edu/research/tech-reports/ics2008-09-15.pdf</link>        <description>In this report we demonstrate the utility of resource allocations that use virtual machine technology for sharing parallel computing resources among competing users. We formalize the resource allocation problem with a number of underlying assumptions, determine its complexity, propose several heuristic algorithms to find near-optimal solutions, and evaluate these algorithms in simulation. We find that among our algorithms one is very efficient and also leads to the best resource allocations. We then describe how our approach can be made more general by removing several of the underlying assumptions.
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>casanova</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-09-30T01:27:13Z</dc:date>        <dc:type>File</dc:type>    </item>
    <item rdf:about="http://www.ics.hawaii.edu/research/tech-reports/chu-brewer-joseph.pdf">        <title>ICS2008-05-02: Traffic and Navigation Support through an Automobile Heads Up Display (A-HUD) - K. Chu, R. Brewer, S. Joseph</title>        <link>http://www.ics.hawaii.edu/research/tech-reports/chu-brewer-joseph.pdf</link>        <description>Abstract: The automobile industry has produced many cars with new features over the past decade. Taking advantage of advances in technology, cars today have fuel-efficient hybrid engines, proximately sensors, windshield wipers that can detect rain, built-in multimedia entertainment, and all-wheel drive systems that adjust power in real-time. However, the interaction between the driver and the car has not changed significantly. The information being delivered – both in quantity and method – from the car to the driver has not seen the same improvements as there has been “under the hood.” This is a position paper that proposes immersing the driver inside an additional layer of traffic and navigation data, and presenting that data to the driver by embedding display systems into the automobile windows and mirrors. We have developed the initial concepts and ideas for this type of virtual display. Through gaze tracking the digital information is superimposed and registered with real world entities such as street signs and traffic intersections.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>karhai</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-05-22T16:05:53Z</dc:date>        <dc:type>File</dc:type>    </item>
    <item rdf:about="http://www.ics.hawaii.edu/research/tech-reports/ICS2008-05-01.pdf">        <title>ICS2008-05-01: Accuracy and Responsiveness of CPU Sharing Using Xen's Cap Values - D. Schanzenbach, H. Casanova</title>        <link>http://www.ics.hawaii.edu/research/tech-reports/ICS2008-05-01.pdf</link>        <description>Abstract: The accuracy and responsiveness of the Xen CPU Scheduler is evaluated using the "cap value" mechanism provided by Xen. The goal of the evaluation is to determine whether state-of-the-art virtualization technology, and in particular Xen, enables CPU sharing that is sufficiently accurate and responsive for the purpose of enabling "flexible resource allocations" in virtualized cluster environments.
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>casanova</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-05-22T16:05:53Z</dc:date>        <dc:type>File</dc:type>    </item>
    <item rdf:about="http://www.ics.hawaii.edu/research/tech-reports/ThesisMarkFinal.pdf">        <title>ICS2008-1-01: Multiple-Genome Annotation of Genome Fragments Using Hidden Markov Model Profiles - M.Menor, K.Baek, G.Poisson</title>        <link>http://www.ics.hawaii.edu/research/tech-reports/ThesisMarkFinal.pdf</link>        <description>Abstract: To learn more about microbes and overcome the limitations of standard cultured
methods, microbial communities are being studied in an uncultured state. In such
metagenomic studies, genetic material is sampled from the environment and sequenced
using the whole-genome shotgun sequencing technique. This results in thousands of DNA
fragments that need to be identified, so that the composition and inner workings of the
microbial community can begin to be understood. Those fragments are then assembled into
longer portions of sequences. However the high diversity present in an environment and the
often low level of genome coverage achieved by the sequencing technology result in a low
number of assembled fragments (contigs) and many unassembled fragments (singletons).
The identification of contigs and singletons is usually done using BLAST, which finds
sequences similar to the contigs and singletons in a database. An expert may then manually
read these results and determine if the function and taxonomic origins of each fragment can
be determined.

In this report, an automated system called Anacle is developed to annotate, following a
taxonomy, the unassembled fragments before the assembly process. Knowledge of what
proteins can be found in each taxon is built into Anacle by clustering all known proteins of
that taxon. The annotation performances from using Markov clustering (MCL) and Self-
Organizing Maps (SOM) are investigated and compared. The resulting protein clusters can
each be represented by a Hidden Markov Model (HMM) profile. Thus a “skeleton” of the
taxon is generated with the profile HMMs providing a summary of the taxon’s genetic
content. The experiments show that (1) MCL is superior to SOMs in annotation and in 
running time performance, (2) Anacle achieves good performance in taxonomic annotation,
and (3) Anacle has the ability to generalize since it can correctly annotate fragments from
genomes not present in the training dataset. These results indicate that Anacle can be very
useful to metagenomics projects.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>poisson</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-05-22T16:05:53Z</dc:date>        <dc:type>File</dc:type>    </item>
    <item rdf:about="http://www.ics.hawaii.edu/research/tech-reports/Streveler%20Sherlock%20HMIS%20RAP%20Final.pdf">        <title>ICS2007-12-01: Health Management Information Systems for Resource Allocation and Purchasing in Developing Countries - D.Streveler, S.Sherlock</title>        <link>http://www.ics.hawaii.edu/research/tech-reports/Streveler%20Sherlock%20HMIS%20RAP%20Final.pdf</link>        <description>World Bank, Health Nutrition and Population, Discussion Paper: The paper begins with the premise that it is not possible to implement an efficient, modern
RAP strategy today without the effective use of information technology. The paper then leads the
architect through the functionality of the systems components and environment needed to support RAP,
pausing to justify them at each step. The paper can be used as a long-term guide through the systems
development process as it is not necessary (and likely not possible) to implement all functions at once.
The paper’s intended audience is those members of a planning and strategy body, working in conjunction
with technical experts, who are charged with designing and implementing a RAP strategy in a developing
country.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>streveler</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-05-22T16:05:53Z</dc:date>        <dc:type>File</dc:type>    </item>
    <item rdf:about="http://www.ics.hawaii.edu/research/tech-reports/ICS2007-11-02.pdf">        <title>ICS2007-11-02: On the NP-Hardness of the RedundantTaskAlloc Problem - J. Wingstrom, H. Casanova</title>        <link>http://www.ics.hawaii.edu/research/tech-reports/ICS2007-11-02.pdf</link>        <description>Consider an application that consists of n independent identical tasks to
be executed on m computers, with m &gt; n. Assume that each computer can
execute a task with a given probability of success (typically &lt;1). One
can use redundancy to execute replicas of some of the tasks on the
m-n computers. The problem is to determine how many replicas should be
created for each task, or more precisely the number of task instances that
should be created for each task and to which computers these instances
should be allocated in order to maximize the probability of successful
application completion. We formally define this problem, which we call
RedundantTaskAlloc, and prove that it is NP-hard.
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>casanova</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-05-22T16:05:48Z</dc:date>        <dc:type>File</dc:type>    </item>
    <item rdf:about="http://www.ics.hawaii.edu/research/tech-reports/ICS2007-11-01.pdf">        <title>ICS2007-11-01: Statistical Modeling of Resource Availability in Desktop Grids - J. Wingstrom, H. Casanova</title>        <link>http://www.ics.hawaii.edu/research/tech-reports/ICS2007-11-01.pdf</link>        <description>Desktop grids are compute platforms that aggregate and harvest the idle
CPU cycles of individually owned personal computers and workstations.
A challenge for using these platforms is that the compute resources
are volatile. Due to this volatility the vast majority of desktop grid
applications are embarrassingly parallel and high-throughput. Deeper
understanding of the nature of resource availability is needed to enable
the use of desktop grids for a broader class of applications. In this document
we further this understanding thanks to statistical analysis of
availability traces collected on real-world desktop grid platforms.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>casanova</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-05-22T16:05:48Z</dc:date>        <dc:type>File</dc:type>    </item>
    <item rdf:about="http://www.ics.hawaii.edu/research/tech-reports/ICS2006-12-03.pdf">        <title>ICS2006-12-03: Improving Software Development Process and Product Management with Software Project Telemetry, Q. Zhang</title>        <link>http://www.ics.hawaii.edu/research/tech-reports/ICS2006-12-03.pdf</link>        <description> Software development is slow, expensive and error prone, often resulting in products with a large number of defects which cause serious problems in usability, reliability, and performance. To combat this problem, software measurement provides a systematic and empirically-guided approach to control and improve software development processes and final products. However, due to the high cost associated with "metrics collection" and difficulties in "metrics decision-making," measurement is not widely adopted by software organizations.
This dissertation proposes a novel metrics-based program called "software project telemetry" to address the problems. It uses software sensors to collect metrics automatically and unobtrusively. It employs a domain-specific language to represent telemetry trends in software product and process metrics. Project management and process improvement decisions are made by detecting changes in telemetry trends and comparing trends between different periods of the same project. Software project telemetry avoids many problems inherent in traditional metrics models, such as the need to accumulate a historical project database and ensure that the historical data remain comparable to current and future projects.
The claim of this dissertation is that software project telemetry provides an effective approach to (1) automated metrics collection and analysis, and (2) in-process, empirically-guided software development process problem detection and diagnosis. Two empirical studies were carried out to evaluate the claim: one in software engineering classes, and the other in the Collaborative Software Development Lab. The results suggested that software project telemetry had acceptably-low metrics collection and analysis overhead, and that it provided decision-making value at least in the exploratory context of the two studies.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>casanova</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-05-22T16:05:52Z</dc:date>        <dc:type>File</dc:type>    </item>
    <item rdf:about="http://www.ics.hawaii.edu/research/tech-reports/ICS2006-12-02.pdf">        <title>ICS2006-12-02: Evaluation of Jupiter: A Lightweight Code Review Framework - T. Yamashita</title>        <link>http://www.ics.hawaii.edu/research/tech-reports/ICS2006-12-02.pdf</link>        <description>Software engineers generally agree that code reviews reduce development costs and improve software quality by finding defects in the early stages of software development. In addition, code review software tools help the code review process by providing a more efficient means of collecting and analyzing code review data. On the other hand, software organizations that conduct code reviews often do not utilize these review tools. Instead, most organizations simply use paper or text editors to support their code review processes. Using paper or a text editor is potentially less useful than using a review tool for collecting and analyzing code review data.
In this research, I attempted to address the problems of previous code review tools by creating a lightweight and flexible review tool. This review tool that I have developed, called "Jupiter", is an Eclipse IDE Plug-In. I believe the Jupiter Code Review Tool is more efficient at collecting and analyzing code review data than the text-based approaches.
To investigate this hypothesis, I have constructed a methodology to compare the Jupiter Review Tool to the text-based review approaches. I carried out a case study using both approaches in a software engineering course with 19 students.
The results provide some supporting evidence that Jupiter is more useful and more usable than the text-based code review, requires less overhead than the text-based review, and appears to support long-term adoption.
The major contributions of this research are the Jupiter design philosophy, the Jupiter Code Review Tool, and the insights from the case study comparing the text-based review to the Jupiter-based review.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>casanova</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-05-22T16:05:52Z</dc:date>        <dc:type>File</dc:type>    </item>
    <item rdf:about="http://www.ics.hawaii.edu/research/tech-reports/ICS2006-12-01.pdf">        <title>ICS2006-12-01: Results from the 2006 Classroom Evaluation of Hackystat-UH - P. Johnson</title>        <link>http://www.ics.hawaii.edu/research/tech-reports/ICS2006-12-01.pdf</link>        <description>his report presents the results from a classroom evaluation of Hackystat by ICS 413 and ICS 613 students at the end of Fall, 2006. The students had used Hackystat-UH for approximately six weeks at the time of the evaluation. The survey requests their feedback regarding the installation, configuration, overhead of use, usability, utility, and future use of the Hackystat-UH configuration. This classroom evaluation is a semi-replication of an evaluation performed on Hackystat by ICS 413 and 613 students at the end of Fall, 2003, which is reported in "Results from the 2003 Classroom Evaluation of Hackystat-UH". As the Hackystat system has changed significantly since 2003, some of the evaluation questions were changed.  The data from this evaluation, in combination with the data from the 2003 evaluation, provide an interesting perspective on the past, present, and possible future of Hackystat. Hackystat has increased significantly in functionality since 2003, which has enabled the 2006 usage to more closely reflect industrial application, and which has resulted in significantly less overhead with respect to client-side installation. On the other hand, results appear to indicate that this increase in functionality has resulted in a decrease in the usability and utility of the system, due to inadequacies in the server-side user interface. Based upon the data, the report proposes a set of user interface enhancements to address the problems raised by the students, including Ajax-based menus and parameters, workflow based organization of the user interface, real-time display for ongoing project monitoring, annotations, and simplified data exploration facilities.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>casanova</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-05-22T16:05:52Z</dc:date>        <dc:type>File</dc:type>    </item>
    <item rdf:about="http://www.ics.hawaii.edu/research/tech-reports/ICS2005-08-02.pdf">        <title>ICS2005-08-02: Priority Ranked Inspection: Supporting Effective Inspection in Resource-limited Organizations - A. Kagawa</title>        <link>http://www.ics.hawaii.edu/research/tech-reports/ICS2005-08-02.pdf</link>        <description>Imagine that your project manager has budgeted 200 person-hours for the next month to inspect newly created source code. Unfortunately, in order to inspect all of the documents adequately, you estimate that it will take 400 person-hours. However, your manager refuses to increase the budgeted resources for the inspections. How do you decide which documents to inspect and which documents to skip? Unfortunately, the classic definition of inspection does not provide any advice on how to handle this situation. For example, the notion of entry criteria used in Software Inspection determines when documents are ready for inspection rather than if it is needed at all.
My research has investigated how to prioritize inspection resources and apply them to areas of the system that need them more. It is commonly assumed that defects are not uniformly distributed across all documents in a system, a relatively small subset of a system accounts for a relatively large proportion of defects. If inspection resources are limited, then it will be more effective to identify and inspect the defect-prone areas.
To accomplish this research, I have created an inspection process called Priority Ranked Inspection (PRI). PRI uses software product and development process measures to distinguish documents that are "more in need of inspection" (MINI) from those ``less in need of inspection'' (LINI). Some of the product and process measures include: user-reported defects, unit test coverage, active time, and number of changes. I hypothesize that the inspection of MINI documents will generate more defects with a higher severity than inspecting LINI documents.
My research employed a very simple exploratory study, which includes inspecting MINI and LINI software code and checking to see if MINI code inspections generate more defects than LINI code inspections. The results of the study provide supporting evidence that MINI documents do contain more high-severity defects than LINI documents. In addition, there is some evidence that PRI can provide developers with more information to help determine what documents they should select for inspection.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>casanova</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-05-22T16:05:52Z</dc:date>        <dc:type>File</dc:type>    </item>




</rdf:RDF>
