Results 21 - 30 of 39,718

TABLE IV BUGS FOUND BY THE REDUNDANT CONDITIONALS CHECKER IN LINUX 2.4.5-AC8, OPENBSD 3.2, POSTGRESQL 7.2.

in Using Redundancies to Find Errors
by Yichen Xie , Dawson Engler

Table 4.3. Chronological data for the releases of PostgreSQL examined in this study. Release Date SLOC Total LOC Release Date SLOC Total LOC

in Contents
by Jason W. A. Selby, M. Giesbrecht (advisor, M. Godfrey, S. Macdonald, S. Watt 2007

Table 1: Average execution latencies in milliseconds of different types of transactions in the TPC-C benchmark when executed with/without inter-transaction dependency tracking added by Phoenix. The Trigger and MVCC columns correspond to the trigger- based and the version-based approach, respectively, to dependency tracking, whereas the PostgreSQL column corresponds to the case of no dependency tracking. The Phoenix Overhead column shows the percentage overhead difference between MVCC and PostgreSQL.

in Design, Implementation, and Evaluation of A Repairable Database Management System
by unknown authors
"... In PAGE 9: ...32%. The latency measurements in Table1 demonstrate that the penalty in transaction response time that Phoenix in- troduced for the TPC-C benchmark is less than 5%. Ta- ble 1 also shows that the performance difference between the Trigger approach and the MVCC approach could be up to a factor of five, e.... ..."

Table 1. Groups and allocation to global projects and teams

in Teaching Requirements Engineering in Global Software Development: A report on a three-University collaboration
by Daniela Damian, Ban Al-ani, Davor Cubranic, Lizveth Robles
"... In PAGE 3: ...roject (i.e. in a project team). Box 1. Three distinct projects, each with two in- stances Project A (A1 and A2 in Table1 ): Global software development system. The students were to design a system to facilitate collaboration in GSD by supporting informal communication as well as document exchange in remote teams.... In PAGE 4: ... 4 Table1 shows the number of groups in each country and project. The Canadian students worked on software projects with the Australian and Italian groups as follows: the 12 Canadian students formed three groups of 4 (Gr1- 3), the Australian students formed two groups of 5 (Gr4- 5), and the Italian students formed two groups, of 3 and 7 students respectively (Gr6cl and Gr6dev).... ..."

Table 4.3: Bugs found by the dead code checker on Linux version 2.4.5-ac8, OpenBSD 3.2, and PostgreSQL 7.2.

in AND THE COMMITTEE ON GRADUATE STUDIES
by Yichen Xie, Monica S. Lam 2006

Table 4: Some statistics about the selected developers (Group 1)

in The processes of joining in global distributed software projects. Accepted in Global Software Development for the Practitioner Workshop 2006. Available from the authors at request
by Israel Herraiz, Gregorio Robles, Juan José Amor, Teófilo Romera, Jesús M. González Barahona, Juan Carlos 2006
"... In PAGE 5: ... The first one, composed of 7 developers, includes all who clearly followed the predicted sequence according to the onion model (this group will be referred from now on as Group 1 ). Table4 gives the dates of the first contribution for each developer, and their global contribution to the mailing lists, version control system and bug tracking system. The main contribution of these de- velopers is code (the mean percentage of code commits is 78.... ..."
Cited by 2

Table 1. Groups of clients (C) and developers (D) allocated to course projects

in The Effects of Communication Mode on Distributed Requirements Negotiations
by Teresa Mallardo, Fabio Calefato, Daniela Damian
"... In PAGE 2: ... All the members of each group were, instead, always collocated. As shown in Table1 , each Canadian and Australian group was involved in two different projects, playing the role of client (C) and developer (D), respectively. Instead, each of the two Italian groups was involved in only one project, either as a client (Gr6cl) or as a developer (Gr6dev).... In PAGE 2: ... The study used three distinct projects, each with two instances. Project A (A1 and A2 in Table1 ) was to design a Global software development system to facilitate GSD collaboration. In project B (B1 and B2) the students designed the interface for a iMedia software to allow users to purchase movies online, organize and play their movies.... ..."

Table A1 Summative results of objective parameters Goal Evaluation parameter Group 1 (x) Group 2 (y) Variability

in 1 2 3 4 5 6 7 8
by Federica Cena, Ilaria Torre

Table 1 : The development of the table of global allocations in GP.

in XTPVM : An Extended Threaded Parallel Virtual Machine
by Tarek Abdel-radi, Muhammed Mudawwar

Table 1 shows the results of applying origin analysis of the parser subsystem of version 1.0 of the EGCS variant of GCC. This subsystem does not exist in the previous evolu- tionary ancestor (GCC version 2.7.2.3), yet we were able to determine that approximately 46% of the 848 functions originated from various places within the ancestor. The sec- ond case study, which is not detailed here, examined the incidence of merging and splitting in the PostgreSQL rela- tional database [12].

in Four Interesting Ways in Which History Can Teach Us About Software
by Michael Godfrey Xinyi, Michael Godfrey, Xinyi Dong, Cory Kapser, Lijie Zou 2004
"... In PAGE 2: ... Table1 . Summary of origin analysis results for the (apparently) all new parser subsystem of the EGCS 1.... ..."
Cited by 4
Results 21 - 30 of 39,718