sadat2307/MSciNLI huggingface dataset:
Domain: Software and its engineering
Sentence 1: (mode any/c)) (values (tok symbol?)
Sentence 2: (start (tok end) ...) (end (tok) ...) (new-mode any/c))) #:tester #) contract from: (function less-broken-lexer) blaming multiple parties: (function pick-a-lexer) (function less-broken-lexer) if pick-a-lexer were to specify lexer/c as its co-domain, only less-broken-lexer would have been blamed but at the cost of checking the same contract twice: (define/contract (pick-a-lexer b) (-> boolean?
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Virtual ma­chines already pro.le the application and maintain a rough breakdown of the amount of time spent in the hot meth­ods [1, 11, 21]; this information could be written to the pro­.le repository, and fed into the program the next time it executes.
Sentence 2: most programs have multiple inputs, and these inputs can drastically a.ect the running time of the pro­gram, as well as the distribution of time spent in the var­ious methods of the program.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: It is worth mentioning that in our above example external web services are being invoked by a client, so little remedial action available to the client other than selecting another service.
Sentence 2: the AuDeQAV approach could also be used by service providers as part of a feedback loop to con­trol provisioning levels for services in response to detected violations wrt their QoS requirements.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: INTRODUCTION Cloud computing [3], with its pay-as-you-go pricing model, provides an attractive environment to provision elastic ser­vices as the running cost of such services becomes propor­tional to the amount of resources needed to handle the cur­rent workload.
Sentence 2: sharing the physical resources among Virtual Machines (VMs) running di.erent applications makes it chal­lenging to model and predict the performance of the VMs [5].
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: A spy has only two technical requirements (§3.2): it must even­tually detect crashes of the layer that it is monitoring (and even then, Falcon handles the case that the spy fails in this charge, per §3.4), and it must be reliable, meaning that its LAYER DOWN an­swers are accurate.
Sentence 2: in practice, a spy should be more am­bitious; it should provide guarantees that are broader than the letter of its contract implies.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: A couple of sites though such as amazon.com and recipecenter.com had higher con.dence scores due to the presence of multiple sec­tions that could be erroneously identi.ed using the same set of patterns.
Sentence 2: the average con.dence score was less than 20% with seventeen web clips displaying alert messages within the validity assessment bar asking users to recreate their web clips.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The putShadow method of an AccessEvent e performs an atomic-compare-and-swap operation: if the current value in the shadow location is the same as e.shadow, then this method replaces the shadow location with its argument and returns true.
Sentence 2: if the shadow location is not the same as e.shadow (meaning that it was changed by another thread after the event object e was initialized), then the method fails and returns false.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: For example, a boolean attribute of a CIO can easily be specified as a SFBool field in VRML97 or X3D.
Sentence 2: whereas the colour of an element is specified as an attribute whose type is string in USIXML, the type of that attribute in the toolkit should be SFColor, which is the most appropriate to describe that property in VRML97 and X3D.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The SAME4HPC architecture also adopts many of these industry standard practices as described in the above environments such as OpenStack, Ubuntu, and includes high-performance, mobile­ready JavaScript frameworks such as OpenLayers 3 and ExtJS 5.
Sentence 2: this architecture also satisfies the above needs by applying various collections of next-generation technologies and emerging standards to deliver scalable and mobile environment for HPC including Node.js, PostgreSQL 9.4, ECMAScript 6 (ES6) - next version of JavaScript standard, and HTML5.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The prob­lem is that, in our scenario, disconnections are the norm 1In theory, it is not possible to send a message to a peer that has never been reachable in the past, since there can be no entry present in the registry.
Sentence 2: to overcome this possible limitation, we provide a primitive through which information can be added to the registry without using the normal channels.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Furthermore, this approach is suggested by the authors as suitable for large legacy databases with little or no semantic advice avail­able [29].
Sentence 2: this method is not entirely applicable, mainly due to its focus on relational database systems, as well as due to the large effort required to reverse engineer the database structure, especially since reverse engineering of Mnesia databases is not a central issue for this project.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Obviously, the risks and bene.ts of switching to a COTS component at this time vs. struggling on with the in-house implementation must be assessed very carefully.
Sentence 2: we believe that develop­ers in such a switch or struggle situation cannot simply resort to established COTS requirements engineering [7], risk assessment [6] and candidate selection [3] methods, as the late project stage enforces much tighter constraints than those methods assume.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: [18] Zhang,Y.,Witte,R.,Rilling,J.,andHaarslev,V.Ontologicalapproachforthesemanticrecoveryoftraceabilitylinksbetweensoftwareartefacts.IETSoftware,2,3(2008),185-203.
Sentence 2: supportingDistributedSoftwareDevelopmentthrough ContextAwarenessonSoftwareArtifacts:TheDiSEN- CollaborARApproach  RafaelLeonardoVivianElisaHatsueMoriyaHuzitaGislaineCamilaLapasiniLealDepartmentofComputerScienceDepartmentofComputerScienceDepartmentofProductionEngineeringStateUniversityofMaringá-UEMStateUniversityofMaringá-UEMStateUniversityofMaringá-UEM Maringá-PR,BrazilMaringá-PR,BrazilMaringá-PR,Brazil rlvivian.uem@gmail.comehmhuzita@uem.brgclleal@uem.br ABSTRACT Sourcecodeandclassdiagramareartifactsproducedorupdatedduringsoftwaredevelopment.whenthescenarioinwhichteamsaredistributedisconsidered,thetemporalandgeographicaldistancesamongindividualsaffectcommunication,creatinginconsistenciesandambiguitiesaboutthesoftwareartifacts.Theseproblemscanbeminimizedbysharingcontextualinformationofactionsthatoccuroncooperationobjects.ThispaperpresentstheDiSEN-CollaborAR,anapproachtodealwithcontextawarenessonsoftwareartifacts.Itprovidesresourcestocommunicatewhatindividualshavedoneoverthesoftwareartifacts.Thisispossiblebycapturingcontextualinformationthatisrepresented,stored,processedanddisplayed.So,awarenesselements,artifactcontextandtraceabilityamongsoftwareartifactscontributetoincreasetheunderstandingofthesoftwareartifactsandalsothecollaborationamongdistributedteams.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Our tool 676 358331 396 69 42 42 CP-Miner 582 534202 251 55 13 13 CP-Miner also assumes that inconsistencies among clones indi­cate bugs.
Sentence 2: its de.nition of inconsistencies is local to the Table 7: Comparison with CP-Miner (Linux kernel 2.6.19).
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Thesekindsofproessmodelsinvolvesomeseveredraw­baks:Initially,theustomeroftendoesnotknowall relevantrequirements,annotstatethemadequately, orevenstatesinonsistentrequirements.Consequently, manydeliveredsystemsdonotmeettheustomer'sex­petations.Inaddition,top­downdevelopmentleads tosystemsthatareverybrittlewithrespettohang­ingrequirements,beausethesystemarhitetureand theinvolvedomponentsarespeifallyadjustedtothe initialsetofrequirements.Thisisinsharpontrastto theideaofbuildingasystemfromtrulyreusableom­ponents,astheproessdoesnottakealreadyexisting omponentsintoaount.Beyondthis,softwaremain­tenaneandlife­ylearenotsupported.Thisisex­tremeritialas,forinstane,nowadaysmaintenane takesabout80perentoftheITbudgetofEurope's ompaniesintheaverage,and20perentoftheuser requirementsareobsoletewithinoneyear[21].
Sentence 2: softwareevolutionasabasioneptisur­rentlynotwellsupported.Inouropinion,thisispartly duetothelakofasuitableoverallomponentware methodologywithrespettosoftwareevolution.Suh amethodologyshouldatleastinorporatethefollowing parts[26]:  Theommonsystemmodelprovidesawell­defnedoneptualframeworkforomponentware andsoftwareevolutionisrequiredasareliablefoun­dation.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: We and others have typically claimed that we want to modu­larize feature representations to make features explicit in design and implementation, to reason about their implemen­tation locally, and to compose them .exibly.
Sentence 2: others have repeatedly challenged that many contemporary forms of feature-oriented programming provide merely syn­tactic compositions, lack proper interfaces, and provide only closed-world reasoning.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: It is generally understood that, in order to follow the REST style, URIs should be assigned to anything of interest (re­sources) and a few, well-de.ned operations (e.g., HTTP op­erations) should be used to interact with these resources.
Sentence 2: for example, the state of a purchase order resource can be updated by POSTing (or PATCHing) a new value for the its state .eld.1 as it has been identi.ed by other au­thors [5][7], there are actions that cannot be easily mapped to read or write operations on resources.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: When pointers are interpreted as integers, we see that on the Alpha two adjacent and aligned integers must have appropriate values in order to be interpreted as a pointer.
Sentence 2: thus it is unlikely that integers will be mistaken for pointers on the Alpha) point- ers map to only a single (though large magnitude) integer on the Pentium and SPARC; thus it is more likely that a conservative garbage collector will retain dead objects on these h;rdware plat- forms.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: To sum up, the advantage in chaining PVeStA to DEUS (if this would be possible), would be the possibility to ex­press queries, and to automatize and distribute their evalu­ation.
Sentence 2: the implicit ability of reusing simulations by logging would be lost, leading to a sensible degradation of performance when evaluating several expressions.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Dynamic pointer-tagging wins on pure perfor­mance: a 13% performance improvement compared to semi­tagging s 9% on the 32-bit processor (14%/ 7% on the 64-bit processor).
Sentence 2: semi-tagging wins comprehensively if we consider complexity: the changes to the compiler were small and localised, whereas dynamic pointer-tagging changesthe fundamen­tal representation of pointers and hence requires non-local changes to the compiler and runtime.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Infact,as wewill seelater,inourtranslation,a methodinvocation requires no run-time checkifthe receiver andactualargumenttypes are all dyn-free.Then,a classdef­inition that passes the standard type checking will translate toitself, without run-time checks.
Sentence 2: the problem is more subtle than it might have appeared,duetothepresence of type variables.Ingeneral, type variables should not be considered dyn-free simply because type variables canbeinstantiated with dyn.Infact, the following classes, which are typed under the standard type system ofgenerics class StrCell extends Cell { void set(String x){ ... x.length() ... } } class Foo { void bar(Cell c, Y x) { c.set(x); } } willraise a run-timeerrorwhencombinedwiththefollowing code: new Foo().bar(new StrCell(...), new Object()); Thelast expressionpasses a StrCell and an Object to Foo.bar(), which expects a Cell and dyn, and this is allowed due to the extended compatibility re­lation we have already mentioned.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: If CARE thinks that the user is walking alone, it will show search results or ads of restaurants within the user s walk­ing distance from the current location.
Sentence 2: if it believes that the user is driving with their family, it will provide a list of family restaurants within driving distance.1 CARE relies on (i) a set of extractors equivalent of the pre-processing layer of Fig.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Sys­tems like PIER [16] abstract details of transport protocols, message formats, marshaling, etc., away from the data.ow framework, and operators only deal with fully unmarshaled tuples.
Sentence 2: p2 explicitly uses the data.ow model to chain together separate elements responsible for socket han­dling, packet scheduling, congestion control, reliable trans­mission, data serialization, and dispatch.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: This reor­ganization a.ords several advantages, including improved locality of reference and faster allocation, but comes at a cost: copying objects requires additional time and space, and potentially dirties more pages in the cache.
Sentence 2: non-copying collectors [23] only attempt to reduce fragmen­tation by using unoccupied space to satisfy allocation re­quests.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: With the increase in the number of subscriptions, the number of groups in the hierar­chical organization also increases (to scale with the compu­tational load as mentioned above) and therefore the neigh­borhood information across the groups at the same level degrades, resulting in some loss of cluster quality.
Sentence 2: the quality of clusters obtained by NCut can be enhanced by increasing the percentage of landmark subscriptions.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Proposals for architectural description languages and associated analysis techniques have .ourished [Luc95, Mag95, Tay96, Gar97]; constructive techniques have also been proposed for archi­tectural re.nement [Mor95].
Sentence 2: little work has been devoted to date to techniques for systematically deriving architectural descriptions from requirements speci.cations.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: A common time series processor, whose input is a time series with time stamps and values only, is merely in the position to provide a result which contains no information about the context of the data it processes, and the result needs to be processed again by another processor (typically a so-called Semantic Processor) to add a meaning to the output data.
Sentence 2: a time series processor for processing semantically enriched time series has the ability to provide a result which already contains all necessary information regarding the meaning of the output, and therefore can be directly used in the tar­geted domain.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: However, with the increased popularity of rating systems on the web particularly, sparse datasets become denser by time as ratings build up on the dataset.
Sentence 2: most of the existing reputa­tion models don t consider the distribution of ratings for an Permission to make digital or hard copies of part or all 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 ci­tation on the .rst page.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: This representation is higher-order and supports both re.ection (i.e., to map the representation of an expression to the expression itself) and rei.cation (i.e., to map an expression to the representation of the expression).
Sentence 2: it handles rei.cation for complex values such as functions in a man­ner that seems too limited to support (practical) meta-programming.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: At all times, the network should treat packets of types A and B from untrusted hosts as potential threats (e.g., A and B might capture packets destined for certain administrative servers), and monitor and possibly deny these packets based on an access control policy.
Sentence 2: all packets from hosts attached to ports 3-6 should be allowed to pass through the network unmodi.ed.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Dependent types have emerged in recent years as a promising approach to ensuring the correctness of software, with high level veri.cation tools such as Coq [8] and Agda [25] being used to model and verify a variety of programs including domain-speci.c languages (DSLs) [26], parsers [9], compilers [16] and algorithms [34].
Sentence 2: since these tools operate at a high level of abstraction, it can be dif.cult to map veri.ed programs to ef.cient low level code.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: In particular, architecture-based self-adaptati­on [17, 23, 25] leverages architecture models to enable high­level reasoning about the best way of adapting a system, and is regarded as a promising approach to building resilient soft­ware systems in a cost-e.ective manner.
Sentence 2: although architecture-based self-adaptation has been applied in prac­tice and recent results indicate its potential bene.ts in terms of cost compared to embedded code-based adaptation mech­anisms [8], there is still a lack of evidence supporting the arguments for its bene.cial impact on system resilience [31].
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: In addition, IDEs usually encompass tools to access software dynamics: debuggers to follow the execution .ow of a system, inspectors to study objet state and pro.lers to analyze the ef.ciency of speci.c system executions.
Sentence 2: the ever-increasing complexity of software systems re­quires us to think about novel means to navigate large software spaces.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: However, ODGs ob­tained from the previous parameters are superior to those of the new parameter set, since the previous parameter set was tuned using contemporary music included in the RWC­MDB-G2001 database.
Sentence 2: the SQAM database 10 5 0 27 32 35 40 65 66 69 70 Avg.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: As a .rst observation, we can see that for Zipf 1.2 and 1 fragment (i.e., experiments in Section 4), the load is severely unbalanced.
Sentence 2: as we increase the number of fragments, the load balances itself quite well, and even for Zipf 1.2 remains below 1.3.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: This problem was minimized through the development of content distribution networks, which bring the content to the user through proxies, thus preventing network bottlenecks between users and content servers [21].
Sentence 2: the wide diversity of contents, users, networks and access devices led to the need for on-the-fly adaptations of Internet contents to meet user expectations, device constraints, and improve the use of network resources.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Characterizing Real-Time Reflexion-based Architecture Recovery: An In-vivo Multi-Case Study Nour Ali Jacek Rosik Jim Buckley Lero-The Irish Software Engineering Lero-The Irish Software Engineering Lero-The Irish Software EngineeringResearch Centre, University of Research Centre, University of Research Centre, University ofLimerick, Limerick Ireland Limerick, Limerick Ireland Limerick, Limerick Ireland Nour.Ali@lero.ie Jacek.Rosik@lero.ie Jim.Buckley@ul.ie ABSTRACT Architecting software systems is an integral part of the software development lifecycle.
Sentence 2: often the implementation of the resultant software ends up diverging from the designed architecture due to factors such as time pressures on the development team during implementation/evolution, or the lack of architectural awareness on the part of (possibly new) programmers.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: We further observed that when contrasting two slightly dif­ferent con.gurations of an experiment (conditions), feature models allow to precisely pinpoint the varied con.guration element by comparison of the respective con.gurations on basis of a formal notation.
Sentence 2: the value of the varied element can only be determined by comparing both con.gu­rations in their entirety even though only one element di.ers.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: INTRODUCTION Recently in various information systems the big technology development storage systems of the data (have received hardware drives, a web ± the environment, cloud computing architectures), allowing to store, practically, nothing information limited scope, productivity of the processor systems providing handling of such data has essentially increased.
Sentence 2: in such situation the primary goals solved by information systems in a web ± the environment today, are connected more to handling of characters (data searching, inference).
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: In the case ['current has been mapped with MS', this means using the design criteria and metrics proposed in the paper, we were able to find a valid solution for 65% of the total process graphs considered.
Sentence 2: using AM to map Fcurren t has led to a situation where IMS is able to find schedules which satisfy the deadlines for o~y 27.5% cases.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Given a set of cover images, in principle it should be pos­sible to extend the distortion function to measure distortion in multiple images (perhaps by simple summation, perhaps by a more sophisticated de.nition) and apply Gibbs em­bedding to the entire set of images, performing at a stroke both batch allocation and embedding using a strategy which optimizes distortion.
Sentence 2: this is not straightforward: the de.nition of distortion should not necessarily be simple summation, particularly if the cover images are of di.erent sizes or very heterogeneous; there is the underlying limi­tation that the optimality of the embedding depends on a close relationship between distortion and detectability; .­nally, there is as-yet no available implementation of Gibbs embedding in multiple images.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: As a result, lpWDA-AC consumes more energy than lpWDA.
Sentence 2: in lpWDA-DP,since the lower-priority tasks are usually complete its execution before the preemptions, the unused time of the lower-priority tasks can be utilized by higher-priority tasks, so that the higher­priority tasks can be scheduled with lower clock speeds than in lpWDA.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: On one hand it is straightforward to see that a VPA for XML document validation can be represent as an ASM naturally, ASMs provide the much more expressive computational model.
Sentence 2: the advantage of the ASM approach is that it pro­vides a single speci.cation dealing with any kind of EDTD only an encoding of the EDTD in two input relations element and sib­ling is required.
Relationship: contrasting