This is a preview of an assignment submited on our website by a student. If you need help with this question or any assignment help, click on the order button below and get started. We guarantee quality, 100% plagiarism free work or your money back.
Designing and implementing a System
For this project you will be designing and implementing a system, in either C or C++, to determine if it is possible to transform one word into another by repeatedly altering single letters and having all interim strings still be considered words in some language.
Additionally, sample input files will not be uploaded to Canvas, but can instead be found on the CSE machines at ~jeh0289/public/csce2110/su18/proj3/ You can cd into that directory and copy input the files from there.
For the project you may, if you choose, work in small groups of up to three students. I will need the names of all of the group members emailed to me by no later than midnight (6/19). Any student who is not in one of the groups I receive emails for will be assumed to be working on their own. A list of groups and their members will be posted on Canvas, after it is compiled. A group cannot be changed once created, unless it is completely dissolved. All members of a group will receive the same grade, and all members are expected to contribute equally to the programming and report. Only one submission per group will be required, but a group will not be penalized for having multiple members submit the completed project.
Also, as a reminder, all of the code for this assignment must be written by your group. You may not share code or download solutions off the internet, as doing so will be considered cheating.
This assignment has two parts: a design portion and an implementation portion.
Document For the design portion, you must generate documentation, in PDF format, describing your system and design process. The purpose of this is for you to explain not just what your system is doing, and how it is doing it, but why. You will need to justify your design decisions in a concise, informative manner. Justifications such as “I did this because it was easy” are not sufficient, as you should actually explain why a particular data structure or algorithm was more efficient, effective, or optimal. Additionally, commented code, while sometimes helpful in small examples, is not a sufficient explanation in and of itself. Your explanations and justifications are expected to be presented in prose and in paragraph format, i.e. not bulleted lists. Further, part of the evaluation of your design document is the apparent amount of thought and effort that went into its creation.
This document should be divided into four main parts, each with an appropriate header.
In the first part, you should describe your design process. Did you work out the algorithm on paper or a whiteboard before hand? Did you draw UML diagrams of the system? Did you create a small prototype? Did you simply start coding away and then recode once or twice with newfound understanding? In a few paragraphs, describe in detail how you went about designing the system, and be sure to provide sufficient justification of your methodology.
For the second part, you should describe the data structures you used in your system. What, if any, objects or structs did you create to store data? How did you organize and manage them? What types of formal data structures did you make use of (trees, graphs, arrays, hashes, etc)? In a few paragraphs, describe in detail how you stored the various data elements in your system, and be sure to provide sufficient justification of your methodology.
For the third part, you should describe functionality of your system. How is data moved and transformed? How is it read in? How is it output? What are the various major functions you constructed and how do they work? In a few paragraphs, describe in detail how your system works, and be sure to provide sufficient justification of your methodology. You might also consider including diagrams to more easily visualize how all of the pieces fit together.
Your program must provide the following functionality and adhere to the following constraints:
ï‚· Allow the user to choose the file that contains all of the words in the language
o Each word will be on a separate line
o All words will be lowercase and contain no symbols or spaces
o The word list should be stored as a undirected graph, where each word is represented by a single node and two nodes are considered adjacent if they differ by exactly one letter
o The graph should be constructed as either an adjacency list or an adjacency matrix
Allow the user to manually input two words to determine if it is possible to transform one into the other
o The first word is the source word and the second word is the destination word
o You must use the graph to determine if the transformation is possible
o You may not use any of the searching algorithms provided by any C/C++ libraries, the STL, or the Boost libraries. You must write your own searching algorithm
ï‚· Your program should output the in-order list of transformations, starting with the source and ending with the destination, to get from the source to the destination words, along with the total number of interim words required.
o Each subsequent word in the list must differ by only one letter
ï‚· Your code must be well commented.
ï‚· You must provide a short README file which includes your name and explains how to compile and run your program.
ï‚· Additionally, you may write a makefile if you want your code to compile with additional flags
A .zip file containing the following:
1. All files necessary to compile and run your program
2. A README file explaining how to compile and run your program
3. Your design document in PDF format