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 contemporary problems causes and effects in practice"
  Abstract: Requirements Engineering (RE) has received much attention in research and practice due to its importance to software project success. Its interdisciplinary nature, the dependency to the customer, and its inherent uncertainty still render the discipline difficult to investigate. This results in a lack of empirical data. These are necessary, however, to demonstrate which practically relevant RE problems exist and to what extent they matter. Motivated by this situation, we initiated the Naming the Pain in Requirements Engineering (NaPiRE) initiative which constitutes a globally distributed, bi-yearly replicated family of surveys on the status quo and problems in practical RE. In this article, we report on the qualitative analysis of data obtained from 228 companies working in 10 countries in various domains and we reveal which contemporary problems practitioners encounter. To this end, we analyse 21 problems derived from the literature with respect to their relevance and criticality in dependency to their context, and we complement this picture with a cause-effect analysis showing the causes and effects surrounding the most critical problems. Our results give us a better understanding of which problems exist and how they manifest themselves in practical environments. Thus, we provide a first step to ground contributions to RE on empirical observations which, until now, were dominated by conventional wisdom only.

Connected through hyperedge HE-1 (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"
    - "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"
    - "naming the pain in requirements engineering a design for a global family of surveys and first results from germany"

Connected through hyperedge HE-2 (induced by source paper "status quo in requirements engineering a theory and a global family of surveys"):
  with members:
    - "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"
    - "naming the pain in requirements engineering a design for a global family of surveys and first results from germany"
    - "field study on requirements engineering investigation of artefacts project parameters and execution strategies"

Connected through hyperedge HE-3 (induced by source paper "digitalization of swedish government agencies a perspective through the lens of a software development census"):
  with members:
    - "testing quality requirements of a system of systems in the public sector challenges and potential remedies"

Connected through hyperedge HE-4 (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"
    - "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"
    - "naming the pain in requirements engineering a design for a global family of surveys and first results from 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)