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: "policy enforcement with proactive libraries"
  Abstract: Software libraries implement APIs that deliver reusable functionalities. To correctly use these functionalities, software applications must satisfy certain correctness policies, for instance policies about the order some API methods can be invoked and about the values that can be used for the parameters. If these policies are violated, applications may produce misbehaviors and failures at runtime. Although this problem is general, applications that incorrectly use API methods are more frequent in certain contexts. For instance, Android provides a rich and rapidly evolving set of APIs that might be used incorrectly by app developers who often implement and publish faulty apps in the marketplaces.   To mitigate this problem, we introduce the novel notion of proactive library, which augments classic libraries with the capability of proactively detecting and healing misuses at runtime. Proactive libraries blend libraries with multiple proactive modules that collect data, check the correctness policies of the libraries, and heal executions as soon as the violation of a correctness policy is detected. The proactive modules can be activated or deactivated at runtime by the users and can be implemented without requiring any change to the original library and any knowledge about the applications that may use the library.   We evaluated proactive libraries in the context of the Android ecosystem. Results show that proactive libraries can automatically overcome several problems related to bad resource usage at the cost of a small overhead.

Connected through hyperedge HE-1 (induced by source paper "controlling interactions with libraries in android apps through runtime enforcement"):
  with members:
    - "a benchmark of data loss bugs for android apps"
    - "increasing the reusability of enforcers with lifecycle events"
    - "in the field monitoring of interactive applications"
    - "verifying policy enforcers"
    - "healing data loss problems in android apps"

Connected through hyperedge HE-2 (induced by source paper "a benchmark of data loss bugs for android apps"):
  with members:
    - "ghera a repository of android app vulnerability benchmarks"
    - "verifying policy enforcers"
    - "healing data loss problems in android apps"

Connected through hyperedge HE-3 (induced by source paper "identifying software components from object oriented apis based on dynamic analysis"):
  with members:
    - "verifying policy enforcers"
    - "mining software components from object oriented apis"
    - "recovering architectural variability of a family of product variants"

Connected through hyperedge HE-4 (induced by source paper "increasing the reusability of enforcers with lifecycle events"):
  with members:
    - "verifying policy enforcers"
    - "healing data loss problems in android apps"

Connected through hyperedge HE-5 (induced by source paper "verifying policy enforcers"):
  with members:
    - "healing data loss problems in android apps"
    - "device centric monitoring for mobile device management"

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)