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 "technical debt and waste in non functional requirements documentation an exploratory study"):
  Abstract: Background: To adequately attend to non-functional requirements (NFRs), they must be documented; otherwise, developers would not know about their existence. However, the documentation of NFRs may be subject to Technical Debt and Waste, as any other software artefact. Aims: The goal is to explore indicators of potential Technical Debt and Waste in NFRs documentation. Method: Based on a subset of data acquired from the most recent NaPiRE (Naming the Pain in Requirements Engineering) survey, we calculate, for a standard set of NFR types, how often respondents state they document a specific type of NFR when they also state that it is important. This allows us to quantify the occurrence of potential Technical Debt and Waste. Results: Based on 398 survey responses, four NFR types (Maintainability, Reliability, Usability, and Performance) are labelled as important but they are not documented by more than 22% of the respondents. We interpret that these NFR types have a higher risk of Technical Debt than other NFR types. Regarding Waste, 15% of the respondents state they document NFRs related to Security and they do not consider it important. Conclusions: There is a clear indication that there is a risk of Technical Debt for a fixed set of NFRs since there is a lack of documentation of important NFRs. The potential risk of incurring Waste is also present but to a lesser extent.

Includes members:
  Member "status quo in requirements engineering a theory and a global family of surveys":
    also connected through other hyperedges:
      (none)
  Member "requirements engineering practice and problems in agile projects results from an international survey":
    also connected through other hyperedges:
      - Hyperedge HE-1 (induced by source paper "on evidence based risk management in requirements engineering")
  Member "non functional requirements documentation in agile software development challenges and solution proposal":
    also connected through other hyperedges:
      (none)
  Member "naming the pain in requirements engineering contemporary problems causes and effects in practice":
    also connected through other hyperedges:
      - Hyperedge HE-2 (induced by source paper "status quo in requirements engineering a theory and a global family of surveys")
  Member "are non functional requirements really non functional an investigation of non functional requirements in practice":
    also connected through other hyperedges:
      - Hyperedge HE-3 (induced by source paper "views on quality requirements in academia and practice commonalities differences and context dependent grey areas")
  Member "preventing incomplete hidden requirements reflections on survey data from austria and brazil":
    also connected through other hyperedges:
      - Hyperedge HE-4 (induced by source paper "status quo in requirements engineering a theory and a global family of surveys")
  Member "naming the pain in requirements engineering comparing practices in brazil and germany":
    also connected through other hyperedges:
      - Hyperedge HE-5 (induced by source paper "challenges in survey research")
  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-6 (induced by source paper "why and how to balance alignment and diversity of requirements engineering practices in automotive")

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)