human: Given a hyperedge-centered hypergraph: <hypergraph>, where the center hyperedge is induced by one source paper and its member nodes are the cited papers.

Details of the hypergraph:
Center hyperedge (induced by source paper "status quo in requirements engineering a theory and a global family of surveys"):
  Abstract: Requirements Engineering (RE) has established itself as a software engineering discipline during the past decades. While researchers have been investigating the RE discipline with a plethora of empirical studies, attempts to systematically derive an empirically-based theory in context of the RE discipline have just recently been started. However, such a theory is needed if we are to define and motivate guidance in performing high quality RE research and practice. We aim at providing an empirical and valid foundation for a theory of RE, which helps software engineers establish effective and efficient RE processes. We designed a survey instrument and theory that has now been replicated in 10 countries world-wide. We evaluate the propositions of the theory with bootstrapped confidence intervals and derive potential explanations for the propositions. We report on the underlying theory and the full results obtained from the replication studies with participants from 228 organisations. Our results represent a substantial step forward towards developing an empirically-based theory of RE giving insights into current practices with RE processes. The results reveal, for example, that there are no strong differences between organisations in different countries and regions, that interviews, facilitated meetings and prototyping are the most used elicitation techniques, that requirements are often documented textually, that traces between requirements and code or design documents is common, requirements specifications themselves are rarely changed and that requirements engineering (process) improvement endeavours are mostly intrinsically motivated. Our study establishes a theory that can be used as starting point for many further studies for more detailed investigations. Practitioners can use the results as theory-supported guidance on selecting suitable RE methods and techniques.

Includes members:
  Member "naming the pain in requirements engineering contemporary problems causes and effects in practice":
    also connected through other hyperedges:
      - Hyperedge HE-1 (induced by source paper "technical debt and waste in non functional requirements documentation an exploratory study")
  Member "preventing incomplete hidden requirements reflections on survey data from austria and brazil":
    also connected through other hyperedges:
      - Hyperedge HE-2 (induced by source paper "technical debt and waste in non functional requirements documentation an exploratory study")
  Member "naming the pain in requirements engineering comparing practices in brazil and germany":
    also connected through other hyperedges:
      - Hyperedge HE-3 (induced by source paper "technical debt and waste in non functional requirements documentation an exploratory study")
  Member "artefact based requirements engineering the amdire approach":
    also connected through other hyperedges:
      - Hyperedge HE-4 (induced by source paper "testing quality requirements of a system of systems in the public sector challenges and potential remedies")
  Member "naming the pain in requirements engineering a design for a global family of surveys and first results from germany":
    also connected through other hyperedges:
      - Hyperedge HE-5 (induced by source paper "why and how to balance alignment and diversity of requirements engineering practices in automotive")
  Member "field study on requirements engineering investigation of artefacts project parameters and execution strategies":
    also connected through other hyperedges:
      - Hyperedge HE-6 (induced by source paper "needs and challenges for a platform to support large scale requirements engineering a multiple case study")

Question: Please tell me which class the source paper 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)