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: "recommended practices for spreadsheet testing"
  Abstract: This paper presents the authors recommended practices for spreadsheet testing. Documented spreadsheet error rates are unacceptable in corporations today. Although improvements are needed throughout the systems development life cycle, credible improvement programs must include comprehensive testing. Several forms of testing are possible, but logic inspection is recommended for module testing. Logic inspection appears to be feasible for spreadsheet developers to do, and logic inspection appears to be safe and effective.

Connected through hyperedge HE-1 (induced by source paper "the reification of an incorrect and inappropriate spreadsheet model"):
  with members:
    - "what s the point of documentation"
    - "evaluating financial model performance an empirical analysis of some north sea investments"
    - "reducing overconfidence in spreadsheet development"
    - "when why and how to test spreadsheets"

Connected through hyperedge HE-2 (induced by source paper "development and experimentation of a software tool for identifying high risk spreadsheets for auditing"):
  with members:
    - "spreadsheet good practice is there any such thing"
    - "risk assessment for spreadsheet developments choosing which models to audit"
    - "controlling end user computing applications a case study"
    - "ensuring spreadsheet integrity with model master"
    - "rapid spreadsheet reshaping with excelsior multiple drastic changes to content and layout are easy when you represent enough structure"
    - "a paradigm for spreadsheet engineering methodologies"
    - "considering functional spreadsheet operator usage suggests the value of example driven modelling for decision support systems"
    - "the importance and criticality of spreadsheets in the city of london"

Connected through hyperedge HE-3 (induced by source paper "defending the future an msc module in end user computing risk management"):
  with members:
    - "milestones for teaching the spreadsheet program"
    - "eusprig team work tools education audit management"
    - "reducing overconfidence in spreadsheet development"
    - "controlling end user computing applications a case study"
    - "when why and how to test spreadsheets"
    - "investigating the potential of test driven development for spreadsheet engineering"
    - "the importance and criticality of spreadsheets in the city of london"
    - "spreadsheet engineering a research framework"

Connected through hyperedge HE-4 (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 end user behaviour analysis"
    - "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"

Connected through hyperedge HE-5 (induced by source paper "establishing and measuring standard spreadsheet practices for end users"):
  with members:
    - "establishing a minimum generic skill set for risk management teaching in a spreadsheet training course"
    - "spreadsheet errors what we know what we think we can do"
    - "stop that subversive spreadsheet"
    - "the importance and criticality of spreadsheets in the city of london"

Connected through hyperedge HE-6 (induced by source paper "in pursuit of spreadsheet excellence"):
  with members:
    - "spreadsheet errors what we know what we think we can do"
    - "sarbanes oxley what about all the spreadsheets"
    - "thinking is bad implications of human error research for spreadsheet research and practice"
    - "the importance and criticality of spreadsheets in the city of london"

Connected through hyperedge HE-7 (induced by source paper "towards a spreadsheet engineering"):
  with members:
    - "when why and how to test spreadsheets"
    - "a paradigm for spreadsheet engineering methodologies"
    - "spreadsheet engineering a research framework"

Connected through hyperedge HE-8 (induced by source paper "facing the facts"):
  with members:
    - "a software development methodology for research and prototyping in financial markets"

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)