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 "characterizing and understanding software developer networks in security development"):
  Abstract: To build secure software, developers often work together during software development and maintenance to find, fix, and prevent security vulnerabilities. Examining the nature of developer interactions during their security activities regarding security introducing and fixing activities can provide insights for improving current practices. #R##N#In this work, we conduct a large-scale empirical study to characterize and understand developers' interactions during their security activities regarding security introducing and fixing, which involves more than 16K security fixing commits and over 28K security introducing commits from nine large-scale open-source software projects. For our analysis, we first examine whether a project is a hero-centric project when assessing developers' contribution in their security activities. Then we study the interaction patterns between developers, explore how the distribution of the patterns changes over time, and study the impact of developers' interactions on the quality of projects. In addition, we also characterize the nature of developer interaction in security activities in comparison to developer interaction in non-security activities (i.e., introducing and fixing non-security bugs). Among our findings we identify that: most of the experimental projects are non hero-centric projects when evaluating developers' contribution by using their security activities; there exist common dominating interaction patterns across our experimental projects; the distribution of interaction patterns has correlation with the quality of software projects. We believe the findings from this study can help developers understand how vulnerabilitiesoriginate and fix under the interactions of software developers.

Includes members:
  Member "a manually curated dataset of fixes to vulnerabilities of open source software":
    also connected through other hyperedges:
      - Hyperedge HE-1 (induced by source paper "learning to catch security patches")
  Member "why software projects need heroes lessons learned from 1100 projects":
    also connected through other hyperedges:
      - Hyperedge HE-2 (induced by source paper "the changing nature of computational science software")
  Member "we don t need another hero the impact of heroes on software development":
    also connected through other hyperedges:
      - Hyperedge HE-3 (induced by source paper "the changing nature of computational science software")
  Member "developer prioritization in bug repositories":
    also connected through other hyperedges:
      - Hyperedge HE-4 (induced by source paper "a systematic mapping study of developer social network research")
  Member "classifying developers into core and peripheral an empirical study on count and network metrics":
    also connected through other hyperedges:
      - Hyperedge HE-5 (induced by source paper "a systematic mapping study of developer social network research")
  Member "evolutionary trends of developer coordination a network approach":
    also connected through other hyperedges:
      - Hyperedge HE-6 (induced by source paper "a systematic mapping study of developer social network research")
  Member "categorizing bugs with social networks a case study on four open source software communities":
    also connected through other hyperedges:
      - Hyperedge HE-7 (induced by source paper "assessing the quality of the steps to reproduce in bug reports")
  Member "the rise and fall of a central contributor dynamics of social organization and performance in the gentoo community":
    also connected through other hyperedges:
      - Hyperedge HE-8 (induced by source paper "analysing time stamped co editing networks in software development teams using git2net")

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)