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 "on representing and eliciting resilience requirements of microservice architecture systems"):
  Abstract: Together with the spread of DevOps practices and container technologies, Microserivce Architecture has become a mainstream architecture style in recent years. Resilience is a key characteristic in Microservice Architecture Systems(MSA Systems), and it shows the ability to cope with various kinds of system disturbances which cause degradations of services. However, due to lack of consensus definition of resilience in the software field, although many works have been done on resilience for MSA Systems, developers still don't have a clear idea on how resilient an MSA System should be, and what resilience mechanisms are needed. In this paper, by referring to existing systematic studies on resilience in other scientific areas, the definition of microservice resilience is provided and a Microservice Resilience Measurement Model is proposed to measure service resilience. And we give a requirement model to represent resilience requirements of MSA Systems. A process framework is also proposed to elicit MSA System resilience requirements. As a proof of concept, a case study is conducted on an MSA System to illustrate how the resilience requirements are elicited and represented.

Includes members:
  Member "multi objective reasoning with constrained goal models":
    also connected through other hyperedges:
      - Hyperedge HE-1 (induced by source paper "from minizinc to optimization modulo theories and back extended version")
  Member "a pattern language for high performance computing resilience":
    also connected through other hyperedges:
      (none)
  Member "about microservices containers and their underestimated impact on network performance":
    also connected through other hyperedges:
      - Hyperedge HE-2 (induced by source paper "a comparative review of microservices and monolithic architectures")
  Member "microservices how to make your application scale":
    also connected through other hyperedges:
      - Hyperedge HE-3 (induced by source paper "devops and its philosophy education matters")
  Member "circuit breakers discovery and api gateways in microservices":
    also connected through other hyperedges:
      - Hyperedge HE-4 (induced by source paper "a comparative review of microservices and monolithic architectures")

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)