Conclusion

Conclusion

The project was about the overall working of a database and its architecture, a web application created in ruby on rails that pulled data to and from a database. How the whole project should be documented and the delivery of it with a presentation. Will this be a multi-user system of a single-user system (for one user at a time)? Are there special business rules and/or calculations that pertain to this industry? How many data entry screens are required? What kind of output do the users require? Will the system produce web pages, printed reports, mail merge files or other types of output? What is the subject of the database and what purpose does the data stored serve?

Well this project I learned how to better manage my time and research skills. I also found I have a better understanding in how a database works with a web application especially how CRUD and restful apps work. But as the project had no specific language that we had to cover I’m delighted I picked Ruby on rails, I found it a great little language for this type of project especially on the smaller scale. I’m not the best for picking up on syntax to easily but found it easy to understand there is very little in terms of brackets and is very English based. Routing to in a web app I picked up easily enough. Minor issues like my environment slowed me down as I had awful issues with windows but found this module or project one of the most interesting as I wasn’t restricted to one subject. One last thing I will keep ruby on my list of languages as a hobby or someday work related.