sadat2307/MSciNLI huggingface dataset:
Domain: Software and its engineering
Sentence 1: That is mainly because the techno­logical platforms existing in the telemedicine ecosystem are not telemedical platforms per se.
Sentence 2: we argue for the use of software ecosystem theories in analysing the tele­medicine ecosystem for two reasons: (i) the actor structure commits to a SECO actor structure both in terms of sym­biotic relationships, business models motivating them and having as products software and services and (ii) we iden­tify that part of the problems in the telemedicine ecosystem is due to the lack of a common and widely used technologic platform.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The tightened en­ergy constraint forces ADAE to activate the Degraded mode which causes the sampling frequency to drop signi.cantly, as can be seen in the top of the .gure.
Sentence 2: even in this Degraded mode, the diurnal tem­perature pattern and two rain events are clearly distinguish­able in the remaining measurements.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The x86-32 architecture was not designed to support full vir­tualization in the sense that Popek and Goldberg described [13], hence the VMM implementations solved this by trapping privi­leged instructions with low-level complex solutions.
Sentence 2: the recent Intel s x86-32 and Itanium architectures support virtualiza­tion through extensions called VT-x for x86-32 and VT-i for Ita­nium [20] and AMD procesor s extensions through its virtualiza­tion solution Paci.ca [1].
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Accurate in­terface identi.cation is fundamental for many of these tech­niques, as the components of a web application communicate extensively via implicitly-de.ned interfaces to generate cus­tomized and dynamic content.
Sentence 2: current techniques for identifying web application interfaces can be incomplete or imprecise, which hinders the e.ectiveness of quality assur­ance techniques.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Figure 8 shows that the modi.ed compiler, using a pressure threshold value of 5, produces lower execution time overheads relative to the baseline.
Sentence 2: the dif­ferences are not large; while the baseline compiler yielded runtime overheads of roughly 9-16%, the modi.ed compiler reduces these overheads to 9-13% only a modest 3% re­duction at the high end.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: This violates Assumption 1 because applying the same substitution to the old result does not yield the new result.
Sentence 2: it is easy to recover this problem by expanding the pattern matching of plus2: plus2 : (Plus Zero n) --+ n Given this rule, the rewrite function would fail for the input term (Plus x Zero), which is consistent with Assumption 1.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: INTRODUCTION With the rapid technological advancements in computer networks, video streaming services are gaining more popu­larity among users and content providers [16].
Sentence 2: due to the inadequacy of infrastructural support, IP-multicast Permission to make digital or hard copies of all or part of this work forpersonal or classroom use is granted without fee provided that copies arenot made or distributed for pro.t or commercial advantage and that copiesbear this notice and the full citation on the .rst page.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Reflex: Using Low-Power Processors in Smartphones without Knowing Them Felix Xiaozhu Lin, Zhen Wang, Robert LiKamWa, and Lin Zhong Rice University {xzl, zhen.wang, roblkw, lzhong}@rice.edu   Abstract To accomplish frequent, simple tasks with high efficiency, it is necessary to leverage low-power, microcontroller-like processors that are increasingly available on mobile systems.
Sentence 2: exist-ing solutions require developers to directly program the low-power processors and carefully manage inter-processor communi-cation.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: In order to be trustworthy, mitigation techniques should given the ingenuity of would-be attackers and the wealth of current and undiscovered software vulnerabilities be simple to comprehend and to enforce, yet provide strong guar­antees against powerful adversaries.
Sentence 2: in order to be deployable in practice, mitigation techniques should be applica­ble to existing code (preferably even to legacy binaries) and incur low overhead.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The edges selected during this walk, designates what execution paths are taken in the actual CFG.
Sentence 2: in order to estimate the dynamic execution time, we need pro.le information of regions of code that correspond to edges in the ECG H. We acquire this by generating a collapsed control .ow graph G. =(V ,E) from the control-.ow graph G =(V, E) of the program.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: For lack of suitable notations, methodologies, and integration between abstraction levels, more abstract system descriptions typically take a back seat in the design process.
Sentence 2: working at higher levels of abstraction will be a key factor in tackling the prevalent complexity issues in automotive software engineering: increasing functional complexity stemming from software being the implementation technology of choice for new innovative functionality as well as for functionality being traditionally implemented in mechanics etc.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Comparing to grid computing, grid system disintegrates a huge task into many tiny tasks and operates them paralleled in different groups and servers emphasizing on the operation of scientific computing application systems.
Sentence 2: cloud computing is a computing platform with broader implications, sustaining the non­grid application, such as sustaining the three-layer application architecture model of foreground network server, application server and database server in network service program as well as sustaining the present network service program of Web 2.0 model.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: General percolation [8] speculatively hoists instructions  9 Proceedings of the International Symposium on Code Generation and Optimization (CGO 05) 0-7695-2298-X/05 $ 20.00 IEEE including loads beyond conditional branches in order to ex­ploit instruction level parallelism.
Sentence 2: it does not en­sure correct semantics when a speculatively hoisted load causes an exception.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: ** (BZ2_bzCompressInit; BZ2_bzCompress ; BZ2_bzCompressEnd ) A speci.cation mining tool is expected to learn it from run­ning trace.
Sentence 2: if the trace is noisy, e.g., containing some unrelated function BZ2_bzDecompress, the resulting automaton would be imprecise [25].
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Limiting the buffer length allows BULLET ' to quickly react to changing network conditions and application re­quests,sincebuffered messagescannotbecancelled.
Sentence 2: bULLET ' ac­tively detects when message blocks will not .t in the queue, and schedulesatimertosend themlater.Diff messages,or thosethatinform apeer aboutblocks a nodepossesses, are also sent overthedatatransport, and are not similarlyprotected against afull buffer.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Our approach is closely related to [20] in that both approaches try to identify failure causes from failing test cases.
Sentence 2: our approach identi.es and investigates a suf.cient set of failing testing cases by decomposing failing test cases based on their grammatical structures, and eventually identi.es a set of common failing input patterns, which can be used to understand fault causes in a compre­hensive way.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The links are con.gured in two logical interfaces, referred to asInput/OutputInterfaces(IOIF).Eachlink operates at 5GHz andtheIOIFprovides rawbandwidthof35GB/s out­bound and 25 GB/s inbound.
Sentence 2: the actual data and commands are transmitted as packets, which incur an over­head due to presence of metadata such as command identi­.er,datatags, anddatasize[45].
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: A server system execution is often composed of many concur­rent requests.
Sentence 2: speci.cally, we de.ne a request or a request exe­cution as the set of server activities to service a user call, like a request for retrieving a web object, or a request for processing an e-commercetransaction.The execution of a single requesttypically consumes afraction of a secondinCPU time.there may exist large variation of hardware characteristics during its course.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: R3 together with this set of open-methods: R1* foo(virtual A&#38;, virtual A&#38;); R2* foo(virtual A&#38;, virtual B&#38;); R3* foo(virtual B&#38;, virtual A&#38;); A call foo(b,b) appears to be ambiguous and the rules out­lined so far would indeed make it an error.
Sentence 2: choosing R2* foo(A&#38;,B&#38;) would throw away information compared to us­ing R3* foo(B&#38;,A&#38;): An R3 can be used wherever an R2 can, but R2 cannot be used wherever an R3 can.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: endfm and the set of pairs P = {H(f(X)) -> H(g(X))}.
Sentence 2: note that there is an in.nite minimal (R, P)-chain if we consider the OS­substitution s(X)= a: H(f(a)) .P H(g(a)) .R H(g(b)) .R H(f(a)) .P ··· since H(g(X)) is not OS-narrowable, we would obtain P ' = Ø in Theorem 6, thus making the previous in.nite chain unfeasible as an (R, P ' )-chain.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Of course, given the wide-spread use of Java, and the constraints on backwards compatibility of Java bytecode, such a change to the Java semantics is possibly not a viable solution, and the concrete problem at hand would better be solved by changing the implementation of the JML run-time checker.
Sentence 2: we believe that for future language designs, it is important to consider the issues discussed in this paper.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Much work has been done and many solutions have been proposed based on Service Oriented Architecture (SoA) and using varying technologies like business process management, AI planning, semantic and ontology, context­aware, etc.
Sentence 2: most of the currently proposed frameworks or systems for composing service are static or semi­automatic; even some famous user­centric solutions like YahooPipe [5], MashMaker [6], and MARGMASH [7] still need human intervention for completing a service creation.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: They can formalize in­dustrial patterns and practices while increasing the scalabil­ity of veri.cation, because input programs are written at a higher level of abstraction.
Sentence 2: engineering new DSLs with custom veri.cation is a non-trivial task in its own right, and usually requires programming language, formal meth­ods, and automated theorem proving expertise.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The browser used for the tests is Mozilla Firefox 3, except for kb since the smltojs version made Firefox completely hang for some unknown reason, so we used Opera 9.5. test ocamlc JS ocamljs smltojs O Browser ack 160ms 1.6s 5s 3s 1m20s kb 1s - fails10 > 1h30 9m15s queens 75ms fails11 2s 3s 21s nucleic 800ms - 2m8s 32s 5m15s If we look at the raw data, the performance is poor.
Sentence 2: we chose these examples because they show three common cases and allow us to put these bad results into perspective: ack is a computation intensive task, with a unique recursive function over integers, so is a function quite easily optimizable by the JavaScript interpreters (integers unboxing, etc.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The application team recently widened key integer variables to 64 bit to support matrix indices that grow with scale.
Sentence 2: they overlooked the de.nition of Table 3: STAT sample and merge times for a 256 task job in sec­onds Trace Type Sample Time Merge Time Function Name Only Function Name and Line Number 0.74 6.57 .004 .004 this function, causing the type coercion.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: It can be implemented using continuations, thus: type IO a = FailCont -> SuccCont a -> Behaviour  (The reader may like to write implementations of return, (>>=), catch and so on, using this de.nition of IO.)
Sentence 2: it is also possible to implement the IO monad in a completely different style, without any recourse to a stream of requests and responses.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Conversely, if the network connectivity is at least 2F +1,then there exists strategies for the normal nodes to use that ensure con­sensus is reached [20, 23, 29].
Sentence 2: these methods either re­quire that normal nodes have at least some nonlocal information or assume that the network is complete, i.e., all-to-all communica­tion or sensing [1, 3, 8, 15, 16].
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: If we apply push schedule to the entire stream graph, it makes a signi.cant di.erence from single appear­ ance schedule in bu.er space requirement as shown in [16].
Sentence 2: when we target 16 cores, the application is already partitioned into 16 pieces; and it does not make a big di.er­ence using either scheduling method on each small piece.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: A Qualitative Assessment of the Efficacy of UML Diagrams as a Form of Graphical Documentation in Aiding Program Understanding Scott Tilley Department of Computer Sciences Florida Institute of Technology stilley@cs.fit.edu  ABSTRACT Graphical documentation is often characterized as an effective aid in program understanding.
Sentence 2: it is an open question exactly which types of graphical documentation are most suitable for which types of program understanding tasks (and in which specific usage contexts).
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Third, Address Space Layout Ran­domization [4, 5, 18] (ASLR) is a probabilistic protection that randomizes the locations of code, stack, heap, and other data.
Sentence 2: return Oriented Programming [20] (ROP) and Jump Oriented Programming [7] (JOP) are two modern attack techniques that no longer rely on injected ex­ecutable code but reuse existing application code.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Vec a (Succ n) We declare two empty datatypes, Zero and Succ, to serve as type-level values , and use a generalized algebraic datatype (GADT) [24] to de.ne a type Vec whose .rst argument is the type of its elements and whose second argument is a type-level natural number re.ecting the length of its values.
Sentence 2: for a language like Haskell with a strong, static type system, this example is rather embarrassing: it is untyped!
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: class Data Size a => Size a where gsize :: a -> Int data Exists :: * where Ex :: a -> Exists instance Size Exists where --Does not type check gsize (Ex (ex :: b))=1+ gsize ex Here, in order to de.ne an instance of Size for Exists, we need to call gsize on the existentially packaged value ex.However, calling gsize requires that there exist an instance of Size for type b.
Sentence 2: because b could be anything there is no way of determining whether such an instance exists.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Non­governmental organizations (NGOs), with their history of activism and involvement in the local development programs, are often the most trustworthy citizens to broker ICT4D research, but rarely incorporate formal informed consent processes into their interactions with communities.
Sentence 2: by leveraging the transitive rapport established with the NGO, researchers may better engage in discussions about the iterative, formative nature of ICT4D research with the target community.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: OCaml partially solves this problem by automati­cally adding a type equation pointing from the internal de.­nition to the external de.nition, when typechecking the body of a recursive module.
Sentence 2: in OCaml, a type de.nition has at most one type equation and therefore this approach is only applicable to datatype de.nitions, but not to type abbreviations or datatype de.nitions with equations.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The sub­sections below describe how RAMCloud divides its work among all of these resources and how it coordinates the resources to re­coverin1-2seconds.
Sentence 2: 3.2 Scattering Log Segments Forfastest recoverythelog segments for each RAMCloud mas­tershouldbedistributeduniformly acrossallofthebackupsinthe cluster.thereare severalfactorsthatcomplicatethisap­proach: Segmentplacementmustre.ectfailuremodes.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: For example, the I/O function al write con in the ttsprk816 benchmark has a coverage of 17.25% (the benchmark ttsprk816 has very low (< 1%) in­nermost loop coverage; due to this we do not list it in Table 6).
Sentence 2: there do not exist any loops in the function (see below).
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Definition: A set P of event-sequences satisfies the event coverage criterion if and only if for all events v E V, there is at least one event-sequence p C P such that event v is in p. 3.1.2 Event-interaction Coverage Another important aspect of GUI testing is to check the interactions among all possible pairs of events in the com- ponent.
Sentence 2: we want to restrict the checks to pairs of events that may be performed in a sequence.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Introduction Refactoringistheprocess ofimprovingthe structure ofsoft­wareby applyingbehavior-preservingprogramtransforma­tions[9], andhasbecomeanintegralpartof currentsoftware developmentmethodologies[4].Theseprogramtransforma­tions,themselves called refactorings, are typicallyidenti.ed by a name, such as RENAME FIELD, and characterized by a set of preconditions under which they are applicable and a set of algorithmic steps for transforming the program s source code.Checkingthesepreconditions and applyingthe transformations manually is tedious and error-prone, so in­terest in automated tool support for refactorings has been growing.Currently,popularIDEs such asEclipse,1Visual­Studio,2 and IntelliJ IDEA3 provide automated support for many common refactorings on various programming lan­guages.In addition,thereis much recentresearchliterature on soundlyperforming a variety of refactorings(seeSec­tion7for an overview).
Sentence 2: most research on refactoring has focused on statically typedlanguages, such as Java, for which express­ing the preconditions and source code transformations can take advantage of static type information and name resolu­tion.Refactoringfordynamiclanguagessuch asJavaScript is complicatedbecauseidenti.ersare resolvedatruntime.Of thefewpreviousapproachesto refactoringfordynamically typedlanguages, the most well-developed one canbefound intheSmalltalkRefactoringBrowser[24], whichrelies on a combination of runtimeinstrumentation andthe existence of a test suite to ensurethatbehaviorispreserved.By contrast, we aimfor a sound technique thatdoes not require compre­hensivetest suites.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: (A new type tintroduces a family F, tEiF, iff no other type was a member of F.) Observe that the dispatching result for such a newly introduced family and every other type is always hn ul l. Therefore, we extend the row of tand place the entries for these new fami­lies at the end.
Sentence 2: instead of extending all the other rows with hn nl lentries, we perform a range-check before accessing any given row.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: One way to support atomicity when making a change to a number of different domain entities is to take the system off-line, evolve the metadata and all the affected domain objects, and then perform a clean restart of the system.
Sentence 2: when a system must keep running, or when the system cannot be taken offline for the long period of time required for performing system-wide changes, then dynamic model evolution is a viable option: the incremental evolution of the metadata and the domain objects can be done when objects are loaded into memory.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Hard to see overall design 94 Hard to understand behavior of system 94 Code becomes of poorer quality over time 92 Too difficult to restructure system when needed 93 Difficult to change code without adding bugs 93 Changing code takes too much time 94 Our programming language leads to complex code 94 More skill is required than is available to develop high 91 quality code Programming languages are not expressive enough 91 Organization culture does not like the code-centric approach 92 Our programming language is likely to become obsolete 93 Overall, most developers clearly see the value of the modeling approach, even though they practice it only to a limited degree.
Sentence 2: there remains a hard core of code-centric zealots who seem dead set against modeling.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The resulting prevailing procedural pro­gramming style, which provides very little room for higher abstractions, also results in a high level of conservative at­titude when choosing the language for implementation for simulationsoftware,still making FortranandCtheprevail­ing languages in, e.g., the area of physics or engineering.
Sentence 2: the low level of abstraction used in these codes increases the amount of code which has to be written, as reusability, which is not commonly a goal in this setting, is usually low.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: 2006) and, in the Scala community, the encoding of type classes using im­plicits is folklore.
Sentence 2: as so often with folklore, it was never written down coherently, while the more advanced fea­tures have not been documented at all: later sections of this paper describe Scala s answer to overlapping instances (Pey­ton Jones et al.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: As with our approach, van Delft treats the zero quantity as having polymorphic dimen­sion.
Sentence 2: van Delft does not provide a speci.cation for the semantics of dimension types, does not encode dimen­sions as part of a class hierarchy, does not allow for the de.nition of new methods speci.c to a particular dimen­sion, and does not include parametric polymorphism over dimension types or separate types for units.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Strict referential equality, which is the default in the OCL language and is written simply _ = _ in the standard, is an overloaded concept and has to be de.ned for each OCL type individually; for ob jects resulting from class de.nitions, it is implemented by simply comparing the references to the objects.
Sentence 2: strong logical equality is a polymorphic concept which is de.ned once and for all by: I[X " Y ]t = LLI[X]t = I[Y ]t JJ It enjoys nearly the laws of a congruence: t |= (x " x) t |= (x " y) =.
Relationship: contrasting