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: "task interruptions in requirements engineering reality versus perceptions"
  Abstract: Task switching and interruptions are a daily reality in software development projects: developers switch between Requirements Engineering (RE), coding, testing, daily meetings, and other tasks. Task switching may increase productivity through increased information flow and effective time management. However, it might also cause a cognitive load to reorient the primary task, which accounts for the decrease in developers' productivity and increases in errors. This cognitive load is even greater in cases of cognitively demanding tasks as the ones typical for RE activities. In this paper, to compare the reality of task switching in RE with the perception of developers, we conducted two studies: (i) a case study analysis on 5,076 recorded tasks of 19 developers and (ii) a survey of 25 developers. The results of our retrospective analysis show that in ALL of the cases that the disruptiveness of RE interruptions is statistically different from other software development tasks, RE related tasks are more vulnerable to interruptions compared to other task types. Moreover, we found that context switching, the priority of the interrupting task, and the interruption source and timing are key factors that impact RE interruptions. We also provided a set of RE task switching patterns along with recommendations for both practitioners and researchers. While the results of our retrospective analysis show that self-interruptions are more disruptive than external interruptions, developers have different perceptions about the disruptiveness of various sources of interruptions.

Connected through hyperedge HE-1 (induced by source paper "elica an automated tool for dynamic extraction of requirements relevant information"):
  with members:
    - "dynamic visual analytics for elicitation meetings with elica"
    - "task interruption in software development projects what makes some interruptions more disruptive than others"
    - "what works better a study of classifying requirements"
    - "let s hear it from retta a requirements elicitation tool for traffic management systems"

Connected through hyperedge HE-2 (induced by source paper "dynamic visual analytics for elicitation meetings with elica"):
  with members:
    - "task interruption in software development projects what makes some interruptions more disruptive than others"
    - "let s hear it from retta a requirements elicitation tool for traffic management systems"

Connected through hyperedge HE-3 (induced by source paper "task interruption in software development projects what makes some interruptions more disruptive than others"):
  with members:
    - "two sides of the same coin software developers perceptions of task switching and task interruption"
    - "a visual narrative path from switching to resuming a requirements engineering task"

Connected through hyperedge HE-4 (induced by source paper "two sides of the same coin software developers perceptions of task switching and task interruption"):
  with members:
    - "task interruption in software development projects what makes some interruptions more disruptive than others"
    - "a visual narrative path from switching to resuming a requirements engineering task"

Connected through hyperedge HE-5 (induced by source paper "a visual narrative path from switching to resuming a requirements engineering task"):
  with members:
    - "what works better a study of classifying requirements"
    - "choosing requirements for experimentation with user interfaces of requirements modeling tools"

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)