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: "preventing incomplete hidden requirements reflections on survey data from austria and brazil"
  Abstract: [Context] Many software projects fail due to problems in requirements engineering (RE). [Goal] The goal of this paper is analyzing a specific and relevant RE problem in detail: incomplete/hidden requirements. [Method] We replicated a global family of RE surveys with representatives of software organizations in Austria and Brazil. We used the data to (a) characterize the criticality of the selected RE problem, and to (b) analyze the reported main causes and mitigation actions. Based on the analysis, we discuss how to prevent the problem. [Results] The survey includes 14 different organizations in Austria and 74 in Brazil, including small, medium and large sized companies, conducting both, plan-driven and agile development processes. Respondents from both countries cited the incomplete/hidden requirements problem as one of the most critical RE problems. We identified and graphically represented the main causes and documented solution options to address these causes. Further, we compiled a list of reported mitigation actions. [Conclusions] From a practical point of view, this paper provides further insights into common causes of incomplete/hidden requirements and on how to prevent this problem.

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"
    - "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"
    - "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:
    - "naming the pain in requirements engineering contemporary problems causes and effects in practice"
    - "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 "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"
    - "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"

Connected through hyperedge HE-4 (induced by source paper "requirements engineering practice and problems in agile projects results from an international survey"):
  with members:
    - "what do practitioners vary in using scrum"
    - "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-5 (induced by source paper "supporting defect causal analysis in practice with cross company data on causes of requirements engineering problems"):
  with members:
    - "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-6 (induced by source paper "towards guidelines for preventing critical requirements engineering problems"):
  with members:
    - "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)