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: "naming the pain in requirements engineering a design for a global family of surveys and first results from germany"
  Abstract: Abstract   Context  For many years, we have observed industry struggling in defining a high quality requirements engineering (RE) and researchers trying to understand industrial expectations and problems. Although we are investigating the discipline with a plethora of empirical studies, they still do not allow for empirical generalisations.    Objective  To lay an empirical and externally valid foundation about the state of the practice in RE, we aim at a series of open and reproducible surveys that allow us to steer future research in a problem-driven manner.    Method  We designed a globally distributed family of surveys in joint collaborations with different researchers and completed the first run in Germany. The instrument is based on a theory in the form of a set of hypotheses inferred from our experiences and available studies. We test each hypothesis in our theory and identify further candidates to extend the theory by correlation and Grounded Theory analysis.    Results  In this article, we report on the design of the family of surveys, its underlying theory, and the full results obtained from Germany with participants from 58 companies. The results reveal, for example, a tendency to improve RE via internally defined qualitative methods rather than relying on normative approaches like CMMI. We also discovered various RE problems that are statistically significant in practice. For instance, we could corroborate communication flaws or moving targets as problems in practice. Our results are not yet fully representative but already give first insights into current practices and problems in RE, and they allow us to draw lessons learnt for future replications.    Conclusion  Our results obtained from this first run in Germany make us confident that the survey design and instrument are well-suited to be replicated and, thereby, to create a generalisable empirical basis of RE in practice.

Connected through hyperedge HE-1 (induced by source paper "why and how to balance alignment and diversity of requirements engineering practices in automotive"):
  with members:
    - "boundary objects and their use in agile systems engineering"
    - "what is large in large scale a taxonomy of scale for agile software development"

Connected through hyperedge HE-2 (induced by source paper "technical debt and waste in non functional requirements documentation an exploratory study"):
  with members:
    - "status quo in requirements engineering a theory and a global family of surveys"
    - "requirements engineering practice and problems in agile projects results from an international survey"
    - "non functional requirements documentation in agile software development challenges and solution proposal"
    - "naming the pain in requirements engineering contemporary problems causes and effects in practice"
    - "are non functional requirements really non functional an investigation of non functional requirements in practice"
    - "preventing incomplete hidden requirements reflections on survey data from austria and brazil"
    - "naming the pain in requirements engineering comparing practices in brazil and germany"

Connected through hyperedge HE-3 (induced by source paper "challenges in survey research"):
  with members:
    - "empirical software engineering from discipline to interdiscipline"
    - "survey research in software engineering problems and mitigation strategies"
    - "what happens when software developers are un happy"
    - "on the unhappiness of software developers"
    - "naming the pain in requirements engineering comparing practices in brazil and germany"

Connected through hyperedge HE-4 (induced by source paper "status quo in requirements engineering a theory and a global family of surveys"):
  with members:
    - "naming the pain in requirements engineering contemporary problems causes and effects in practice"
    - "preventing incomplete hidden requirements reflections on survey data from austria and brazil"
    - "naming the pain in requirements engineering comparing practices in brazil and germany"
    - "artefact based requirements engineering the amdire approach"
    - "field study on requirements engineering investigation of artefacts project parameters and execution strategies"

Connected through hyperedge HE-5 (induced by source paper "needs and challenges for a platform to support large scale requirements engineering a multiple case study"):
  with members:
    - "field study on requirements engineering investigation of artefacts project parameters and execution strategies"

Connected through hyperedge HE-6 (induced by source paper "on evidence based risk management in requirements engineering"):
  with members:
    - "a taxonomy of risk based testing"
    - "supporting defect causal analysis in practice with cross company data on causes of requirements engineering problems"
    - "requirements engineering practice and problems in agile projects results from an international survey"
    - "naming the pain in requirements engineering contemporary problems causes and effects in practice"
    - "preventing incomplete hidden requirements reflections on survey data from austria and brazil"
    - "towards guidelines for preventing critical requirements engineering problems"
    - "naming the pain in requirements engineering comparing practices in brazil and germany"

Connected through hyperedge HE-7 (induced by source paper "rapid quality assurance with requirements smells"):
  with members:
    - "does quality of requirements specifications matter combined results of two empirical studies"
    - "can clone detection support quality assessments of requirements specifications"
    - "do code clones matter"
    - "comparing bug finding tools with reviews and tests"

Connected through hyperedge HE-8 (induced by source paper "requirements engineering practice and problems in agile projects results from an international survey"):
  with members:
    - "preventing incomplete hidden requirements reflections on survey data from austria and brazil"
    - "what do practitioners vary in using scrum"
    - "naming the pain in requirements engineering comparing practices in brazil and germany"

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)