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: "spreadsheets the good the bad and the downright ugly"
  Abstract: Spreadsheets are ubiquitous, heavily relied on throughout vast swathes of finance, commerce, industry, academia and Government. They are also acknowledged to be extraordinarily and unacceptably prone to error. If these two points are accepted, it has to follow that their uncontrolled use has the potential to inflict considerable damage. One approach to controlling such error should be to define as "good practice" a set of characteristics that a spreadsheet must possess and as "bad practice" another set that it must avoid. Defining such characteristics should, in principle, perfectly do-able. However, being able to say with authority at a definite moment that any particular spreadsheet complies with these characteristics is very much more difficult. The author asserts that the use of automated spreadsheet development could markedly help in ensuring and demonstrating such compliance.

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"
    - "the role of spreadsheets in the allied irish bank allfirst currency trading fraud"
    - "documenting problem solving knowledge proposed annotation design guidelines and their application to spreadsheet tools"
    - "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 "leveraging user profile and behaviour to design practical spreadsheet controls for the finance function"):
  with members:
    - "transforming critical spreadsheets into web applications at zurich financial"
    - "changing user attitudes to reduce spreadsheet risk"
    - "a practical approach to managing spreadsheet risk in a global business"
    - "controlling end user computing applications a case study"

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)