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: "documenting problem solving knowledge proposed annotation design guidelines and their application to spreadsheet tools"
  Abstract: End-user programmers create software to solve problems, yet the problem-solving knowledge generated in the process often remains tacit within the software artifact. One approach to exposing this knowledge is to enable the end-user to annotate the artifact as they create and use it. A 3-level model of annotation is presented and guidelines are proposed for the design of end-user programming environments supporting the explicit and literate annotation levels. These guidelines are then applied to the spreadsheet end-user programming paradigm.

Connected through hyperedge HE-1 (induced by source paper "introducing morphit a new type of spreadsheet technology"):
  with members:
    - "in search of a taxonomy for classifying qualitative spreadsheet errors"
    - "spreadsheets the good the bad and the downright ugly"
    - "the role of spreadsheets in the allied irish bank allfirst currency trading fraud"
    - "spreadsheets and the financial collapse"
    - "eusprig team work tools education audit management"
    - "reducing overconfidence in spreadsheet development"
    - "training gamble leads to corporate grumble"
    - "protecting spreadsheets against fraud"

Connected through hyperedge HE-2 (induced by source paper "on the interpretation of spreadsheets within their environment"):
  with members:
    - "towards evaluating the quality of a spreadsheet the case of the analytical spreadsheet model"
    - "what s the point of documentation"
    - "changing user attitudes to reduce spreadsheet risk"
    - "interpretation as a factor in understanding flawed spreadsheets"
    - "correctness is not enough"

Connected through hyperedge HE-3 (induced by source paper "what we understand is what we get assessment in spreadsheets"):
  with members:
    - "spreadsheet validation and analysis through content visualization"
    - "metrics based spreadsheet visualization support for focused maintenance"
    - "spreadsheet errors what we know what we think we can do"
    - "interpretation as a factor in understanding flawed spreadsheets"

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)