sadat2307/MSciNLI huggingface dataset:
Domain: Software and its engineering
Sentence 1: 2.4 Semantic Analysis for Actions The clear separation of concerns and a good coverage of the four orthogonal dimensions of actions is arguably desir­able for complex actions, in particular for complex actions in emergency management.
Sentence 2: the resulting expressive­ness comes at a price, namely the need for a strong semantic analysis capable of rejecting incorrect and faulty programs.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: LiveWide-AreaMigrationofVirtualMachines IncludingLocalPersistentState oberg ¨Robert Bradford, Evangelos Kotsovinos, Anja Feldmann, Harald Schi Deutsche Telekom Laboratories {.rstname.lastname}@telekom.de Abstract So far virtual machine (VM) migration has focused on transferring the run-time memory state of the VMs in local area networks (LAN).
Sentence 2: for wide-area network (WAN) migration it is crucial to not just transfer the VMs image but also transfer its local persistent state (its .le system) and its on-going network connections.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: So far, security and e.ciency of cloud storage have been separately investigated as follows: On one hand, security notions such as Proof of Data Possession (PDP)and Proof of Retrievability (POR) have been introduced for de­tecting that the data stored in the cloud has been tampered with.
Sentence 2: the notion of Proof of Owner­ship (POW) has also been proposed to alleviate the cloud server from storing multiple copies of the same data, which could substantially reduce the consumption of both network bandwidth and server storage space.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: While having achieved remarkably good prediction perfor­mance, most of these approaches predict bugs at the level of source .les (or binaries, modules, Java packages).
Sentence 2: since a .le can be arbitrarily large, a developer needs to in­vest a signi.cant amount of time to examine all methods of a .le in order to locate a particular bug.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: ...).Rememberthatthisdowncontinuationrep­resentsthestateofourownpipelinestage,pluseverythingdown­streamfromus thatis,everythingdownstreamfromu.Whenu hasavaluereadytosendus,itwillcallthisdowncontinuation,passingitthevaluex,andanewupcontinuationu ' forustousethenexttimewewishtoperformaget.Whenthishappens,ourcurrentget iscomplete itshouldreturnvaluex.Sowegobacktorunningourcurrentpipelinestagebycallingk,passingitx,thenewupcontinuationu ' ,andthesamedowncontinuationwehadbeforetheget call,d.Thus,thedowncontinuationwepasstouis(.xu ' .kxu ' d).
Sentence 2: wecanwalkthroughade.nitionofput inthesameway,guidedbythefunctionalitiesortypesofthedifferentvalueswemanipulate.Toput avaluex,wemustpassittothedownstreampipelinestage,whichwedobyapplyingdtox.whenwetransfercontroldownstream,wemustalsopassdanupstreamcontinuationthatpackagesupallthecomputationupstreamfromd thatis,thestateofourownpipelinestage,andeverythingupstreamfromus.AnUpCont hasfunctionalityDownCont .
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: An obvious and viable solution is to create the C-E protocol as a union of all component instance protocols cproti, such that the set L(CEprot) of event traces speci.ed by the C-E protocol is a superset of the set of traces L(cproti) for each Ci.
Sentence 2: if the components are separate en­tities in the architecture, then they are typically used in di.erent ways speci.cally, their component instance pro­tocols di.er to a great degree.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: These are based on de­ductive veri.cation [18], code generation [16], model extrac­ tion [4], re.nement type systems [20], or static information­ .ow analysis [24].
Sentence 2: these techniques focus on source program veri.cation and do not explicitly address executable code, nor side-channel attacks.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: 5.2.4 First polymorphism task Only a portion of method calls in JAVA involve dynamic dispatching, and a much smaller portion of these involve dynamic targets whose documentation adds to or con.icts with that of the overridden static target.
Sentence 2: we sus­pect that when these situations do occur, they present a par­ticularly dif.cult challenge to developers, who are only ex­posed to the documentation for the static type.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Pointers to those ob­jects are sent to Java as ints, so that the programmer can pass them back to the JNI library to manipulate the window com­ponents.
Sentence 2: since the ints are just ordinary integers as far as Java is concerned, the programmer could inadver­tently pass bogus pointer values back to C, thereby poten­tially causing memory corruption.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: This can be done by using UML diagrams: use case diagrams to provide a static process view, by organizing processes hierarchically as use cases and showing which stakeholders are entitled to participate in their realization; activity diagrams to deal with dynamic aspects of the system, rendering processes as actions which transform entities and their state; ob ject dia­grams focus on describing the design space assumption and constraints which in.uence the process.
Sentence 2: uML­based methodologies are not .exible enough to capture and model alternatives.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Our approach makes extensive use of both early and late aspects throughout the software development lifecycle, with aspect-based characterizations of components used in requirements engineering, software architecture and component design, component implementation and at run-time to support dynamic component discovery, integration, and deployed component testing [9], [11], [13].
Sentence 2: as AOCE adds extra complexity to component requirements, designs and implementations, using AOCE without adequate tool support is very difficult [11].
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: When a query aimed for some speci.c .les are raised by the .le requester, the index node will respond with a list of related indices for the .le requester to select.
Sentence 2: due to the lack of central authorities in systems, some peers may perform some malicious behaviors, e.g., a .le provider may insert into the system a lot of polluted .les, and the index node may fabricate the maintained indices.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The program above looks simple because Kerninst provides a mechanism for .nding the address of the entry point of a func­tion.
Sentence 2: if we want to print a log message in the middle of that function, we must manually calculate the address where the hook code is inserted and then we must pass that address to in­sertSnippet() instead of entries[0].
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The problem of determining whether two Fµ types are uni.able may be turned, in a very simple manner, into a nominal uni.cation prob­lem [21], provided nominal uni.cation is extended with support for recursive terms, which appears straightforward.
Sentence 2: neither we nor Urban [personal communication] are currently able to for­mulate a nominal uni.cation algorithm whose time complexity is less than O(n2).
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: To overcome this lack, the OMG released fUML 1.0 (Se­mantics of a Foundational Subset for Executable UML Mod­els) [21], a new standard that precisely de.nes the execution semantics for a subset of UML 2.3 in a form of an Execution Model implemented in a virtual machine.
Sentence 2: in order to ensure the success of the development [14], models need to be veri.ed at early stages of the development lifecycle.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Methodology 6.1 Program-speci.c, true prediction Our purpose is to explore the extent to which micro-patterns can provide program-speci.c prediction to guide pretenur­ing.
Sentence 2: it is important that such program-speci.c prediction nevertheless be true prediction rather than self­prediction [4], that is, the prediction should not be derived simply from a past execution of the same program.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Had these models been used within our sample of 1,652 warn­ings, triaging engineers would have examined hundreds of fewer spurious and non-actionable warnings not an insigni.cant sav­ings when the cost of triaging is estimated at eight minutes per warning (as discussed in Section 2.1).
Sentence 2: this comes at a cost due to the incorrect predictions made by the models.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: So it seems that proofs in their universe do not need the sort of infrastructure we de.ne in this paper.
Sentence 2: the style of programming is very different and a Generic Haskell programmer would not recognize the de.nition of map; moreover, the de.nition of the functor laws isnotasdirect(forexample,aspecial composition operatorneeds tobede.nedfor composition of morphisms over environments).
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: One could say that the latter makes the .rst redundant since sending the response is of course an indirect acknowledgement for the initial request.
Sentence 2: when the computation time on the server for producing the response is considerably longer than the transmission time for a signal (since it for exam­ple could include further communication with other compo­nents), the extra acknowledgement would allow the client to detect communication problems earlier.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: In contrast, when a transformed function is called from an unsafe (third-party) context, unless the call is in tail position, the continuation frame does not contain an unsafety mark, so the safety mark does not override any marks.
Sentence 2: call/cc will fail because when it captures the SAFE?marks with c-c-m, it will extract a list like (list ... false true ...) where the frames between false and true were the third-party context.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: For example, if we know that input I is 0 then we ex­pect the output O to be 0 after the rising edge of CLK.
Sentence 2: considering the execution trace in Figure 5 and assuming solely p2 to behave correctly yields to contradic­tion, since we expect O to be 0 instead of 1 .
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: [2008] and Ré [2009], there are no works focusing speci.cally on stubs and drivers implementation for AO software.
Sentence 2: there are some interesting related papers such as the work of Binder [1999] that analyses several integration strategies and design patterns to test object-oriented software, and the work of Pasternak et al.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Their language Lk involves predicates that contain numeric constants no larger in ab­solute value than k from the constants that already occur in the program.
Sentence 2: the choice of the language used in our implementa­tion places restrictions on the size of the boolean formulas, which is motivated by the fact that most programs are usually correct for simple reasons that can be expressed using some small represen­tation.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: To avoid copying data in or out of small data sections at migration time, we add support for small data sections to the GCC ARM back-end.
Sentence 2: we do not change the compiler to generate ARM code that can take advantage of the small data section by generating code to access data in these sections with fewer instructions so the performance of ARM code is not improved, but is not degraded either.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Background execution of test cases allows the developer to al- Figure 5: Architecture of Cdd implementation ways see the latest state of the test cases.
Sentence 2: in addition to this,thedevelopermaywantto more clearly understandwhyapar­ticulartest casefails.Forthis caseCddallowshimtoexecuteatest caseintheregulardebugger.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Liivi 2, Tartu, Estoniamartti.vasar@ut.ee satish.srirama@ut.ee marlon.dumas@ut.ee ABSTRACT By allowing resources to be acquired on-demand and in vari­able amounts, cloud computing provides an appealing envi­ronment for deploying pilot projects and for performance testing of Web applications and services.
Sentence 2: set­ting up cloud environments for performance testing still re­quires a signi.cant amount of manual e.ort.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: RE L AT E D WO R K In the past, debugging techniques based on formal meth­ods have been proposed in the domain of logic circuit design [16] or the design modelling based on declarative speci.cations such as Alloy [17] and KodKod [18].
Sentence 2: these approaches address languages and problems different from UML/OCL and, thus, do not consider the two-staged approach proposed in this work.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Assessing the Impact of Refactoring Activities on the JHotDraw Project Ishwor Thapa, Harvey Siy Department of Computer Science University of Nebraska at Omaha 6001 Dodge Street, Omaha, Nebraska, USA {ithapa,hsiy}@unomaha.edu  ABSTRACT Refactoring is a well-known technique for improving the maintainability of software products.
Sentence 2: it is not easy to justify the time and e.ort needed to refactor code as thebene.ts are di.cult to quantify, especially theper­ception of improved maintainability.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Our techniques [27] generate unit tests for aspects by feeding the complied aspect classes to existing Java test-generation tools such as Parasoft Jtest [19], JCrasher [7], Rostra [24], and Symstra [25], which can generate tests based on Java bytecode.
Sentence 2: these Unit tests Integration tests Test-input Aspectual behavior JamlUnit [14], AJTE [29] Aspectra [26] generation Aspectual composition AJTE [29], APTE [2] Test oracles Aspectual branch cov [26], data.ow cov [30] data cov [28], Pipa [31], muJava [15] branch cov [26], data.ow cov [30] data cov [28], Pipa [31], muJava [15] Aspectual composition interaction cov [26] data.ow cov [30] pointcut mutation testing [3] Table 1: Classi.cation of automated testing techniques for aspect-oriented programs Java test generation tools based on bytecode are not able to generate meaningful tests for advice methods whose argument types include JoinPoint or AroundClosure.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Testing of this new regridder showed good scaling up to 98K cores at which point there are only one or two patches with 4096 cells per core; at this point scalability be­ginsto breakdown.
Sentence 2: thekeyproblemwasthatwe were notabletorunalargerproblemwith morepatchesper coreasthere was insuf.cient memory to accommodate the larger run.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: An analysis similar to the one done with MultiVeStA, in­cluding the reuse of simulations, can be performed using DEUS alone, by logging the required measures during sim­ulations.
Sentence 2: no CI evaluation facilities are provided, thus it would be necessary to launch the simulations, to compute the CIs, and to launch new simulations if necessary.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: For example, the append operator @ on lists, which is speci.ed by the equations Nil @ ys = ys (Cons x xs) @ ys = Cons x (xs @ ys) will over.ow if the longest representable nonempty list is appended to itself.
Sentence 2: selectors such as hd (head) and tl (tail), which return the .rst and second argument of a Cons, cannot over.ow.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: In this case, the agent discovers that her menu contains too much fat and not enough calcium, so it suggests replacing al kharoof bel roaz with sayyadieh (fish with rice) and suggests nooranoush (pomegranates and yogurt) for dessert.
Sentence 2: fAQIH also warns her not to buy yogurt of a specific brand, because it seems to be causing an outbreak of diarrhea in a close-by locality.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Therefore, we are facing a challenge, in our industrial context, to minimize the test suite for testing a product, whereas at the same time achieving high fault detection capability and functionality coverage.
Sentence 2: the current practice of reducing the number of test cases is manual and not systematic, which often decreases the functionality coverage and fault detection capability in addition to being time consuming as we observed in our previous work [4].
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Code coverage is usually used as a quality metric of software development to measure how thoroughly test programs exercise with the system under test.
Sentence 2: it is also useful to understand how many pa­rameters an experimental system exposes in a speci.c net­work experiment since the number of lines, functions, and branches covered by test programs re.ect the number of di.erent inputs (i.e., parameters) injected into the system under test with the support of ns-3.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Super-linear speedup is predicted and measured in both jacobi and life but only the former had actual super-linear speedup.
Sentence 2: these benchmarks consist mainly of DOALL loops, allowing unrolling to linearly increase the amount ofILP.unstruct also bene.ts from unrolling and serial optimizations,but its loops areDOACROSS, limiting unrolling seffects and limiting scalability.For theremaining benchmarks, aes, fpppp, and sha, unrolling was ineffective as the parallelized regions were functions rather than loops.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: For example, the Locale application automatically adjusts mobile phone behavior based on location [18].
Sentence 2: most current location-aware applications are restricted to Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for pro.t or commercial advantage and that copies bear this notice and the full citation on the .rst page.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Of course, for a static data set and a constant query rate there is no great problem .guring out the number of clusters needed to satisfy a target latency, and from there to calculate the number of machines in each cluster needed to satisfy the overall throughput.
Sentence 2: neither the data set nor the query rate remain constant for most real applications, and the total number of machines cannot normally be changed on short timescales.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: From the perfor­mance perspective, it is best to place each function into a separate region, so that it will not interfere with any other object, but that may increase the code space too much.
Sentence 2: mapping all functions into one region uses the min­imum amount of code space, but incurs too many instruction  Figure 2: Cost between functions depends on where other functions are mapped, and updating the costs as we map the functions can lead to a better mapping.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: A selection of findings from the pilot are discussed below.
Sentence 2: 50% Use of Interface (% of total references to interface types) 40% 30% 20% 10% 0% the presence of an object with a neighborhood covering a substantial proportion of the rest of the program may be indicative of some problem such as too much centralized control or lack of semantic cohesion.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: To this end, we hope to shed light on the applicability of AOP be­yond traditional examples of logging, debugging, authoriza­tion control, and the like.
Sentence 2: by pointing out some of AspectJ s weaknesses and by demonstrating how Caesar, which combines concepts from both AspectJ and FOAs, is more e.ective in this context, we also demonstrate the power of appropriate support for layer modules.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Comments gathered from participants during the study were generally positive  one even complained about not having had access to the environment when initially learning about 3 http://www.bluej.org/ conditionals and loops.
Sentence 2: there were a number of critical comments regarding the Jeliot visualisation, including: -Too much happening at one time often participants had to play the animation several times before understanding it.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: So, observing the speci.cation at a high-level with­out going into its details (this will be done during subse­quent phases), it appears that no redundant classes were added to the speci.cation.
Sentence 2: if the sales system readily includes in its speci.cation the interface operations needed, the class ClsLocalSales would be redundant.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The author pointed out sev­eral cases where automatic completion of work.ows is desirable, such as creating an executable work.ow from a work.ow instance by assigning tasks to resources, completing under-speci.ed work­.ow templates by mapping abstract tasks to speci.c components or adding data conversion steps.
Sentence 2: no speci.c algorithms were discussed.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Partial evaluation has been known for many years, and Futa­mura s paper [16] on interpreter specialisation is now 39 years old.
Sentence 2: the technique is still not widely applied, because sev­eral problems arise when putting it into practice.We have found that these problems are either easily handled or simply do not arise when embeddingDSLsinIDRIS,largelyduetoitstype system.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Even after finding the right form, participants complained it did not have usual input field with labels 'From' and 'To' and instead uses drop-down menu and also there was no clear instruction about how to use it.
Sentence 2: after completing the task on desktop browser, it helped them recognize the right form on mobile browser and didn't get confused with the quick journey planner.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: In terms of the continuation e.ect, y+ precedes x- (i.e., the matching unlock operation).
Sentence 2: if x and y are instantiated with the same lock handle a and z with b, the continuation e.ect of the .rst lock operation becomes [a+, a-, b+, b-, a-] and the future lockset is now correctly calculated as {a, b}: a+ and b+ precede the matching unlock operation, which is the last a-.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Our comparative experiment shows that the choice of coverage type can greatly affect the effectiveness of fault­localization: some faults are best localized by statements, others by branches, and still others by du-pairs.
Sentence 2: in general, it is impossible to know which kinds of faults exist in a program before .nding these faults, and thus, which type of coverage is best (i.e., ideal) for fault local­ization.
Relationship: contrasting