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: "spreadsheet end user behaviour analysis"
  Abstract: To aid the development of spreadsheet debugging tools, a knowledge of end-users natural behaviour within the Excel environment would be advantageous. This paper details the design and application of a novel data acquisition tool, which can be used for the unobtrusive recording of end-users mouse, keyboard and Excel specific actions during the debugging of Excel spreadsheets. A debugging experiment was conducted using this data acquisition tool, and based on analysis of end-users performance and behaviour data, the authors developed a "spreadsheet cell coverage feedback" debugging tool. Results from the debugging experiment are presented in terms of enduser debugging performance and behaviour, and the outcomes of an evaluation experiment with the debugging tool are detailed.

Connected through hyperedge HE-1 (induced by source paper "effect of range naming conventions on reliability and development time for simple spreadsheet formulas"):
  with members:
    - "an exploratory analysis of the impact of named ranges on the debugging performance of novice users"
    - "the lookup technique to replace nested if formulas in spreadsheet programming"
    - "does an awareness of differing types of spreadsheet errors aid end users in identifying spreadsheets errors"
    - "reducing overconfidence in spreadsheet development"
    - "the importance and criticality of spreadsheets in the city of london"

Connected through hyperedge HE-2 (induced by source paper "the detection of human spreadsheet errors by humans versus inspection auditing software"):
  with members:
    - "spreadsheet auditing software"
    - "an exploratory analysis of the impact of named ranges on the debugging performance of novice users"
    - "spreadsheet assurance by control around is a viable alternative to the traditional approach"
    - "a typical model audit approach spreadsheet audit methodologies in the city of london"
    - "recommended practices for spreadsheet testing"

Connected through hyperedge HE-3 (induced by source paper "from error detection to behaviour observation first results from screen capture analysis"):
  with members:
    - "overview and main results of the didatab project"
    - "classification of spreadsheet errors"

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)