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: "can clone detection support quality assessments of requirements specifications"
  Abstract: Due to their pivotal role in software engineering, considerable effort is spent on the quality assurance of software requirements specifications. As they are mainly described in natural language, relatively few means of automated quality assessment exist. However, we found that clone detection, a technique widely applied to source code, is promising to assess one important quality aspect in an automated way, namely redundancy that stems from copy & paste operations. This paper describes a large-scale case study that applied clone detection to 28 requirements specifications with a total of 8,667 pages. We report on the amount of redundancy found in real-world specifications, discuss its nature as well as its consequences and evaluate in how far existing code clone detection approaches can be applied to assess the quality of requirements specifications in practice.

Connected through hyperedge HE-1 (induced by source paper "interactive duplicate search in software documentation"):
  with members:
    - "detecting near duplicates in software documentation"

Connected through hyperedge HE-2 (induced by source paper "detecting near duplicates in software documentation"):
  with members:
    - "sourcerercc scaling code clone detection to big code"

Connected through hyperedge HE-3 (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"
    - "do code clones matter"
    - "comparing bug finding tools with reviews and tests"

Connected through hyperedge HE-4 (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"
    - "do code clones matter"

Connected through hyperedge HE-5 (induced by source paper "on the relationship of inconsistent software clones and faults an empirical study"):
  with members:
    - "do code clones matter"
    - "tool support for continuous quality control"

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)