MSCS 510 The Small Project 1101 SHORT DOCUMENT CONCORDANCE SYSTEM (SDCS) Your group (henceforth referred to as "you") and I (viz., Stuart Greenfield) are working as a software team! Of course, you realize that I have been selected as the "team leader". As such, I am assigning to you the development of a portion of this small project. Our approach to the development of the system is to be considered rather preliminary and so it will be "rapidly" prototyped. The prototype is to be error-free although limitations on its capabilities will be tolerated. From its development and testing we expect to gain insight as to what the final, production software system should incorporate. As we have previously discussed, this small software project consists of the development of a "Short Document Concordance System". During our discussion I showed you my analysis and design of this small project. I have placed 9 files on a diskette for your group. They are to be used in completing the "Short Document Concordance System". They are: concglob.h queue.h bstree.h concorda.h chset.h chset.obj document.h document.obj conctest.txt Your group is responsible for the development of four source code files, namely, queue.cpp bstree.cpp concorda.cpp sdcsdr.cpp I have made the decision that this prototype system will hold words up to 12 characters in length. This limit is built in as follows. The binary search tree structure underlying the concordance (see bstree.h) effectively consists of tree nodes that include a pointer to a string array that holds up to 12 characters plus the inevitable null character ('\0'). Thus the constant MAX has been set to 13. This limitation impacts your development of file concorda.cpp. You must implement method "entry" of class "concordance" such that it accepts strings of any length (actually up to 80 characters) but only stores the first 12 characters in the concordance. With all of this in place, words such as scintillometer (an instrument for detecting and measuring the scintillations induced by ionizing radiation in a crystal or phosphor) will be truncated to 12 characters. Your file sdcsdr.cpp should allow a user to enter a text file name that will be handled exclusively by protocol found in class document and in turn a concordance for the document will be printed to the screen. Make sure your sdcsdr.cpp is implemented as an "application class" since the "team leader" loves to see such things. Place all appropriate files in a C++ Project named SDCSDR. When your group thinks it has a working project, try it out on an ASCII copy of this document (namely, conctest.txt). Your group's SDCS Project Report will be handed in on a diskette (properly labeled with the project name along with each group member's name) that includes the following complete set of files (19 of them and no others): concglob.h queue.h queue.cpp queue.obj bstree.h bstree.cpp bstree.obj concorda.h concorda.cpp concorda.obj chset.h chset.obj document.h document.obj sdcsdr.cpp sdcsdr.obj sdcsdr.exe conctest.txt comments.txt In addition, your "handed-in" project should include comments (in an ASCII file named comments.txt or a Microsoft Word file named comments.doc) concerning the system's architectural design, its limitations, what your group suggests as future maintenance to be done when preparing the final product.1234567890123456 If your group encounters any really big problems you can always talk to the "team leader" about them.