sadat2307/MSciNLI huggingface dataset:
Domain: Software and its engineering
Sentence 1: Communities that discuss topics related to architec­turalknowledgebut neverusethatphraseitself areperde.­nition not included in our analysis.
Sentence 2: given our goal to investigate current de.nitions of architectural knowledge we do not see the exclusion of communities that do not use the literal phrase let alone de.ne it as a shortcoming.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: At the moment of 3bp2 1 being executed, the shadow variable in the current calling context, which is referred to as Sbp1(1), contains the depended predicate instance 11 .
Sentence 2: our experience shows that in practice it is very hard to manipulate the stack pointers for certain functions, especially when those functions are from libraries that may be compiled us­ing various compilers or even written by hands.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: A traversal over the basic blocks using theSSAgraphissuf.cienttoexecutethe associated semantic rules in order to emit the code.
Sentence 2: this approach [7] is not able to deal with complex instruction patterns that have multiple results, i.e.,patternsthat cannotbeexpressedin termsoftreeshapeproduc­tions.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: This immediate consequence ope­rator captures the information concerning possible compositions obtained by the union of signatures and rules, and the correspon­ding semantics is directly compositional by construction with res­pect to the union operation of program modules.
Sentence 2: in or­der to obtain the complementary property of compositionality, the so-called full abstraction property, the adequacyof this semantics must be established with respect to the deletion operation of a sig­nature in a program module, used to delete a whole set of program rules de.ninga function.We de.nea compositional and fully abs­tract semantics for the reduced set of operations on program modu­les de.ned in Section 3, union and deletion, that are suf.cient to express the most extended ways of composing modules and their relationships.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Prior work [21, 6, 3, 7, 8, 19, 10] indicates that this is a feasible solution to a sound reporting of erroneous code.
Sentence 2: our work dodges many of the dif.culties in a proper program analysis, relying in­stead on the type checker to throw out any invalid suggestions on our part.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: After some analysis we concluded that either our tasks are aperiodic with a wide distribution of inter invocation and response times or what is more probable the initial assumption that we adopted from RMA of tasks having a single period and response time does not hold in our case.
Sentence 2: it may be possible to identify a small set of typical ( peak ) periods and response times of a task.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The input buffers and output buffers are sized in the system such that they withstand the asyn­chronous reads and writes from the system and the environments.
Sentence 2: if the system is too slow to consume data from the input buffersorproducedatatotheoutputbuffersinthepre-de.nedrates, the input buffers will eventually be full of data when the environ­ments write (over.ow), or the output buffers will be empty when the environments read (under.ow).
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: For example, in Figure 1, the text attribute is used for frames, buttons, and labels.
Sentence 2: since the wxWidgets Window class provides for a text attribute, we could use inheritance to de.ne the text attribute for any kind of window: text :: Attr (Window a) String this is not such a good de.nition for a library, as user de.ned widgets can no longer support this attribute.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Expressiveness is better than with a TA X O N O M Y, but TH E S AU R I demand more attention to semantics, which can imply more effort during creation and maintenance.
Sentence 2: in practice, maintenance may not actually be harder than with a TA X O N O M Y, because the meaning of each TH E S AU RU S entry is more .ne grained and better de.ned it s easier to improve an entry while being con.dent that the rest of the TH E S AU RUS remains consistent.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Concerning the discovery (Decentralized), iden­ti.cation (Global), and binding (Dynamic) facets, we do not observe any di.erence due to the properties of the HTTP    RESTful HTTP RPC over HTTP WS-*/ESB Discovery Discovery Generated Generated Binding  Binding Code Code Evolution Platform Evolution Platform State Interaction State Interaction Orientation Orientation Model Model Model (a) RESTful HTTP (b) RPC over HTTP (c) WS-*/ESB Figure 3: Measuring the degree of coupling implied by di.erent Web services technologies RESTful HTTP RPC over HTTP WS-*/ESB 4.1 Discovery Referral Referral Registration 4.2 Identi.cation Global Global Context-based 4.3 Binding Late Early/Late Late 4.4 Platform Independent Independent Independent 4.5 Interaction Asynchronous Synchronous Asynchronous 4.6 Interface Orientation Vertical Horizontal Horizontal 4.7 Model Self-Describing Messages Shared Model Self-D. Messages/Shared Model 4.8 Granularity Fine/Coarse Fine/Coarse Fine/Coarse 4.9 State Stateless Stateless/Shared, Stateful Stateless 4.10 Evolution Compatible/Breaking Compatible/Breaking Compatible/Breaking 4.11 Generated Code None/Dynamic Static Static 4.12 Conversation Re.ective Explicit Explicit Table 2: Web Services Technology Evaluation Summary protocol.
Sentence 2: when it comes to the interaction facet, some di.erences become apparent.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: This implies that Java s safety guarantees are not a major factor in performance for this program.
Sentence 2: we do see that Java is indeed slower than C and suspect that this is due to the overall performance degradation from the sum total of all of Java s overheads, including ones we were unable to study in greater detail: for example the Henderson frames used for accurate stack scanning, sync-points, procedure call overheads, etc.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: To en­sure that JML errors that occur in T or C cannot be dis­carded by F , the statement could be transformed according to the following pattern:  try { try { try T catch C } catch (JMLError j) { ... // set flag, store j } finally F } finally { ... // if flag set, rethrow j } This ensures that whatever happens, F will be executed.
Sentence 2: if execution of T or C gave rise to a JML error j, this error will be stored, and the last finally clause ensures that the complete statement ends with abruptly because of the JML error j.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: For instance, SCSI controllers and drivers are optimized to reduce the number of interrupts on the receive path, and to impose very little overhead on the send path [23].
Sentence 2: this requires offtoading storage related pro- ccssing to customized hardware on the storage controller this approach still requires going through the ker- nel and incurs relatively high CPU overheads.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The OMII installer takes care of deploying AHE services, Postgres database management system, WSRF::Lite plus supporting Perl mod­ules in to a Tomcat container, making installation relatively easy.
Sentence 2: a number of users have reported problems with deploying AHE using the OMII installer, due to the relatively limited number of Linux distributions it supports.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Our intention is to demonstrate the advantages of the proposed techniques in their relatively pure forms.6 The performance im­pact in systems that are hybrids of the schemes with which our techniques are being compared (e.g., a generational system with a copying young generation and mark-sweep-compact old gener­ation) may be smaller.
Sentence 2: we believe that the mark-and­sweep old generation can also bene.t from object co-allocation.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: GPP at work (left) Sample code, (right) Computations Removed vs Assertions Placed Note that to prune the backslices, a WAR memory dependence cognizance is exploited.
Sentence 2: this aliasing information may sometimes be easily deduced at the compiler level (especially stack based communication, spill code, callee save and restore memory operations, and absolute address based memory operations).
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The set applAll(G,c,m,c¯), formally de.ned in Figure 6, contains all methods of c (either directly declared or inherited) named m whose parameter types are supertypes of ¯c in G (note that for calculating this set all ancestors of c are needed).
Sentence 2: in general we cannot be sure that this set actually con­tains all the applicable methods, since there could exist some m in c for which we do not have in G the type assumptions stating that the parameter types are supertypes of ¯c.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The JSR-282 Expert Group has responded to the requests from implementers, application developers and researchers to remove some of the limitations of version 1.0.2 and to add some much-memory model outlined here, and the introduction of needed new features.
Sentence 2: we are also mindful a heap-only subset we hope will address some of the of the need for efficiency, particularly in the area on concerns.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Thus traffic from i to j is proportional to the product of the (excess) concentrations as is the case in gravity models.
Sentence 2: in the simplest version of the model there is no analogue for Gij in (2), but we can express the probability in (5) as:  G OAi(t) Pij(t) -~-Z Gi/~Ak(t) k~ k~S sin Ic (9) we use this special form of gravity model, only to determine the destinations.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Static ordering performance is not Benchmark Default OOR Overhead Heap size jess 4.39 4.43 0.84% 15MB 20MB 25MB 30MB 35MB 40MB 45MB 50MB 1.6 jack 5.79 5.82 0.57% 3.8 raytrace 4.63 4.61 -0.59% 1.5 3.6 mtrt 4.95 4.99 0.7% 3.4 1.4 javac 12.83 12.70 -1.05% compress 8.56 8.54 -0.2% 3.21.3    Normalized GC TimeNormalized Mutator L2 MissesNormalized Mutator Time Normalized Time GC Time (sec) Mutator L2 Misses (10^6) Mutator Time (sec) Time (sec) pseudojbb 13.39 13.43 0.36% 3 1.2 db 18.88 18.88 -0.03% 2.8 antlr 0.94 0.91 -2.9% 1.1 2.6 gcold 1.21 1.23 1.49% 1 2.4 hsqldb 160.56 158.46 -1.3% ipsixql 41.62 42.43 1.93% Heap size relative to minimum heap size jython 37.71 37.16 -1.44% (a) Total Time ps-fun 129.24 128.04 -1.03% Heap size mean -0.19% 15MB 20MB 25MB 30MB 35MB 40MB 45MB 50MB 1.5 Table 2: OOR System Overhead  always consistent across architectures.
Sentence 2: oOR consistently attains essentially the same performance as the best static order across these platforms.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Us­ing edge-coverage as their criterion for reduction, and start­ing with randomly selected subsets of the test suites, they achieve a reduction in test suite size of between 87% and 95%.
Sentence 2: after manually injecting between 7 and 41 faults into the programs, they report a signi.cant decrease in the fault detection capability of the reduced suites, in many cases by up to 100%.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: They show that data spreading can provide both performance and power bene.ts, if the working set .ts in the aggregate cache space.
Sentence 2: data spreading does not provide bene.tiftheworkingsetistoolargeorthe programdoesnothavea repetitiveaccess pattern.Inter-core prefetching removes thesetwo limitationsbyprefetchingdataintothenext cache.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: This is due main because QVT tools have still low robustness and its use is not widely disseminated.
Sentence 2: aTL has a framework widely used by an increasing and enthusiast com­munity, with full support to model operations, where, in an integrated way, one can specify and instantiate metamodels as well as specify and execute transformations on them.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: It is well-known that minimizing address space size in WSN message packets can obtain signi.cant energy savings by reducing message sizes, since each bit of transmission is known to consume energy similar to 800 instructions [22].
Sentence 2: wSNs are ad hoc precisely in the sense that positions and densities of nodes in space are unpredictable, so minimal address space is an environmental property, where minimality may need to be determined in situ.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: This is a form of product versioning [9], where there is one global version space for the whole Web project, while in .le-based ver­sioning systems such as CVS [38] or RCS [56], each .le has its own version history.
Sentence 2: the Fluid version model operates at a much .ner internal granularity the versioned slot level to effectively store, retrieve, compare, and construct ver­sions.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The study of how developer interac­tions align with the structure of the technical work being car­ried out, has gained considerable attention of late, inspired by the socio-technical design theory from organizational lit­erature [26].
Sentence 2: the relation between talk and work, and how it in.uences ownership and performance of tasks at the indi­vidual level is far from a settled question.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: A symbolic grammar G. for SimpleCalc replaces the calc concrete productions for letters and numbers with symbolic placeholders: Letters l ::= a Numbers n ::= ß This is a simple renaming change where a and ß are sym­bolic constants.
Sentence 2: with the change, the number of strings of a certain length that can be generated by the gram­mar reduces signi.cantly.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Despite, in the extended TS2PC4RS, the client performs the role of the transaction manager (TM), we could also use a TM apart as described in the references [1, 23], i. e., the client would ask TM to create a transaction that would be identi.ed by the timestamp returned to the client.
Sentence 2: some considerations should be taken to assure that the TM meets the business goal of the client appropriately.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Although we have lots of well-developed tools to help with the graphic design, such as the Adobe Flash Profes­sional development environment [1], these tools are useful to create complicated graphics.
Sentence 2: we are not eas­ily able to use common software engineering approaches or design pattern techniques with these tools to improve the e.ciency and reusability of multimedia applications.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: It is an open question how to de.ne security for prove­nance.Someprevious work(starting with [8,31])has con­sidered access control and other security issues for prove­nanceinformation,butdoes notformalize securitypolicies orprovecorrectnessofimplementations.Chong[14]setsout initial attempts atde.nitionsfor securitypropertiesfor sys­tems in which both data and provenance may be con.den­tial; this workisformulatedin terms ofdetailed operational traces, but seems adaptable to other forms of provenance.
Sentence 2: there are manyissuesthatneedfurther study, such asprivacy and auditin thepresence ofprovenance.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: TECA s judgment Saturn s judgment Final judgment 1 Safe * Safe 2 Unsafe Safe Safe 3 Unsafe Unsafe Unsafe 4 Unsafe No judgment Unsafe This is the case which is expected to add precision while retaining soundness.
Sentence 2: due to this case, in theory, there is a possibility that Saturn may be reporting a false negative due to its unsound behavior and can lead to unsoundness in our approach.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: m (Treeaa kv) brancha kvlr = ina (Branch k v l r)  The leafa and brancha smart constructors can be used to build up annotated binary search trees for an arbitrary annotation type a.
Sentence 2: since the annotation type is associated with a monadic context, we now have to build our example tree in monadic style: myTreea :: In a (TreeF Int Int) m .
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Data Chunking: In a conventional cloud environment the storage node is mounted on the local .le system of the EC2 VM and accessed directly.
Sentence 2: our experiments show S3 is unable to saturate even a small EC2 machine in­stance,achieving a throughputbetween10MB/s to20MB/s for .le transfer, compared to the EC2 s peak capacity of around 30MB/s.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: AC( p) = true In the example of Figure 8, ECC ensures that the path A,L1,L3(t),never_A(t),L2,L3(t + 1), never_A(t + 1) will be activatedat  least once withA=true andA=false.
Sentence 2: thiscriterion still not ensuresthe fault detection (input sequences(true, true) and (false, false) meet ECC but do not detect the replacedoperator).
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: If all the objects accessed in .r-1 are also in .r, i.e., pn accesses them also in fr, then .r = .r-1er.
Sentence 2: the application of er may have the undesirable e.ect (from the perspective of an adversary) of making pr shorter than pr-1: pn may read the information written by per and avoid accessing some other objects that were previously in pr-1.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: for i in 0..(2*n-1) for i in 0..(n-1) data[i] = if even(i) data[2*i] = fst(...) then fst(...) data[2*i+1] = snd(...) else snd(...) When working with Pull arrays, the loop structures to the left in the examples above are obtained.
Sentence 2: the code on the right is preferred.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Financial Services In the financial services industry, the factors that influenced most project success were: Complete and accurate requirements from project start  Good schedule estimates  Enough time for requirements elicitation  Well-defined project scope  Rewarding staff for working long hours Identifying risk before the start of the project was a factor that most successful projects fulfilled in the financial services industry.
Sentence 2: since 40% of failed projects also identified risks before project start, it was not possible to state that risk identification was related to project success.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: We have also considered the ISO/IEC 12119 standard as possible candidate for our work.
Sentence 2: we found some drawbacks that drove us to prefer the ISO/IEC 9126-1 catalogue: 1) lack of balance in the standard (user interface is a clear example); 2) it seems incomplete at some points (e.g., adaptation to user needs); 3) there are not metrics in the proposed requirements; 4) not only non-technical but also technical attributes are considered, but all of them are put together without clear differentiation.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Number of AOP mechanisms and faults in iBATIS.
Sentence 2: iBATIS release Pointcuts Advices ITDs Faults 01 97 94 79 23 01.3 121 118 86 9 01.5 244 240 238 13 02 244 238 237 38  while performing such an analysis based in internal properties of the systems, we should take into account concern­specific characteristics.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Program Total # DP SP Preds Executed % % % (#) .ex-2.5.31 17,895,047 0.26 1.76 0.29 (51,691) grep-2.5.1 160,071 6.10 35.0 5.58 (8,924) make-3.80 1,181,569 6.70 36.2 6.61 (78,065) bc-1.06 3,943,354 8.33 21.1 1.35 (53,102) gzip-1.2.4 1,598,515 6.13 16.7 2.58 (41,305) tar-1.13.25 83,353 5.10 15.8 3.23 (2,696) tidy 9,556,715 7.06 31.4 5.68 (542,540) In our discussion so far we have assumed that the execution of faulty code causes the program to terminate with a wrong output value.
Sentence 2: our approach also applies to situations where the observed erroneous value is not an output value.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: It not only requires the instructor to be a relative expert in STL and run-time veri.cation, but also requires careful observation of traces where the fault is known to be present and not present, and a number of iterations of trial and error.
Sentence 2: instructors can easily come up with a set of reference controllers: a set C+ of positive-labeled controllers that are all known to exhibit the faulty behavior, and a set C- of negative-labeled controllers that are all known to not exhibit the faulty behavior.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: In an email triage study by Pierce et al., moving from dis­playing no preview of an email messages body to displaying one line of previewimproved the accuracyof participants at­tempting to determine the purpose of messages from 51% to 80% [18].
Sentence 2: the addition of more lines resulted in di­minishing returns; using .ve lines of preview only improved accuracy to 88%.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Committing the trans­action at this point will publish both the to-space object contents and the reference values that point to the to-space location of the object, completing the transplantation.
Sentence 2: there is a window between the time the object is marked for transplantation and the point in the transaction where each member of the referrer set has been protected by being writ­ten to within the transaction.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Motivated by dependency provenance, an earlier tech­nical report [10] presented a model of traced evaluation for NRC and proved elementary properties such as .delity.
Sentence 2: it did not investigate slicing techniques, and used nondeterministic label generation instead of our deterministic scheme; our deterministic approach greatly simpli.es several aspects of the system, particu­larly for slicing.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Recently there has been growing interest in the automatic gen­eration of functions from user-provided speci.cations [14, 15, 2], mainly consisting of a type and a set of input-output examples.
Sentence 2: the function generation research above is not directly applicable to the generation of generic functions due to their dif­ferent nature: the approach of Koopman and Plasmeijer [15] does not seem to be able to generate higher-order functions, which is essential for generating generic functions, while Djinn [2] and Katayama s MagicHaskeller [14] generate polymorphic functions but not generic functions.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: With regard to SL(ori-scale), since it adopts the PFS only to store checkpoint .les and uses all the 1 million processes/cores to perform the execution, the checkpoint/recovery overheads would be higher than those in multilevel model.
Sentence 2: the failure rates would also be fairly high because of too many cores being used simultaneously, which will cause an extremely large amount of roll-back loss.
Relationship: contrasting