human: Given a node-centered hypergraph: <hypergraph>, where nodes represent papers and hyperedges represent sets of papers co-cited by a source paper.

Details of the hypergraph:
Center node: "do code clones matter"
  Abstract: Code cloning is not only assumed to inflate maintenance costs but also considered defect-prone as inconsistent changes to code duplicates can lead to unexpected behavior. Consequently, the identification of duplicated code, clone detection, has been a very active area of research in recent years. Up to now, however, no substantial investigation of the consequences of code cloning on program correctness has been carried out. To remedy this shortcoming, this paper presents the results of a large-scale case study that was undertaken to find out if inconsistent changes to cloned code can indicate faults. For the analyzed commercial and open source systems we not only found that inconsistent changes to clones are very frequent but also identified a significant number of faults induced by such changes. The clone detection tool used in the case study implements a novel algorithm for the detection of inconsistent clones. It is available as open source to enable other researchers to use it as basis for further investigations.

Connected through hyperedge HE-1 (induced by source paper "harnessing evolution for multi hunk program repair"):
  with members:
    - "automatic software repair a bibliography"
    - "precise condition synthesis for program repair"
    - "automatic repair of real bugs an experience report on the defects4j dataset"

Connected through hyperedge HE-2 (induced by source paper "scalable source code similarity detection in large code repositories"):
  with members:
    - "a survey on learning to hash"
    - "hashing for similarity search a survey"

Connected through hyperedge HE-3 (induced by source paper "an initial step towards organ transplantation based on github repository"):
  with members:
    - "nopol automatic repair of conditional statement bugs in java programs"
    - "dynamic patch generation for null pointer exceptions using metaprogramming"

Connected through hyperedge HE-4 (induced by source paper "are there functionally similar code clones in practice"):
  with members:
    - "challenges of the dynamic detection of functionally similar code fragments"

Connected through hyperedge HE-5 (induced by source paper "rapid quality assurance with requirements smells"):
  with members:
    - "does quality of requirements specifications matter combined results of two empirical studies"
    - "naming the pain in requirements engineering a design for a global family of surveys and first results from germany"
    - "can clone detection support quality assessments of requirements specifications"
    - "comparing bug finding tools with reviews and tests"

Connected through hyperedge HE-6 (induced by source paper "analysing text in software projects"):
  with members:
    - "naming the pain in requirements engineering a design for a global family of surveys and first results from germany"
    - "can clone detection support quality assessments of requirements specifications"

Connected through hyperedge HE-7 (induced by source paper "on the relationship of inconsistent software clones and faults an empirical study"):
  with members:
    - "can clone detection support quality assessments of requirements specifications"
    - "tool support for continuous quality control"

Connected through hyperedge HE-8 (induced by source paper "operationalised product quality models and assessment"):
  with members:
    - "introduction of static quality analysis in small and medium sized software enterprises experiences from technology transfer"
    - "the quamoco product quality modelling and assessment approach"
    - "adapting software quality models practical challenges approach and first empirical results"
    - "a bayesian network approach to assess and predict software quality using activity based quality models"
    - "model based product quality evaluation with multi criteria decision analysis"
    - "a bayesian network approach to assess and predict software quality using activity based quality models"
    - "tool support for continuous quality control"
    - "an activity based quality model for maintainability"

Question: Please tell me which class the center node belongs to. The 40 classes are: cs.NA(Numerical Analysis), cs.MM(Multimedia), cs.LO(Logic in Computer Science), cs.CY(Computers and Society), cs.CR(Cryptography and Security), cs.DC(Distributed, Parallel, and Cluster Computing), cs.HC(Human-Computer Interaction), cs.CE(Computational Engineering, Finance, and Science), cs.NI(Networking and Internet Architecture), cs.CC(Computational Complexity), cs.AI(Artificial Intelligence), cs.MA(Multiagent Systems), cs.GL(General Literature), cs.NE(Neural and Evolutionary Computing), cs.SC(Symbolic Computation), cs.AR(Hardware Architecture), cs.CV(Computer Vision and Pattern Recognition), cs.GR(Graphics), cs.ET(Emerging Technologies), cs.SY(Systems and Control), cs.CG(Computational Geometry), cs.OH(Other Computer Science), cs.PL(Programming Languages), cs.SE(Software Engineering), cs.LG(Machine Learning), cs.SD(Sound), cs.SI(Social and Information Networks), cs.RO(Robotics), cs.IT(Information Theory), cs.PF(Performance), cs.CL(Computation and Language), cs.IR(Information Retrieval), cs.MS(Mathematical Software), cs.FL(Formal Languages and Automata Theory), cs.DS(Data Structures and Algorithms), cs.OS(Operating Systems), cs.GT(Computer Science and Game Theory), cs.DB(Databases), cs.DL(Digital Libraries), cs.DM(Discrete Mathematics). Directly output the class name.

gpt: cs.SE(Software Engineering)