Reference no: EM133673030
Being a small charity, Walton MakerShed cannot afford to use outside development companies, or online hosted data storage. So, they will be developing the software themselves - which inevitably means several volunteers working part-time on distinct parts of the system over an extended period of time. In this case, they estimate a year for all parts of the system to be working but hope to have the client record part ready in two months. It's common for volunteers to commit only to short periods of work with MakerShed so they may not be around for the whole duration of the project. The plan is to divide the overall records system into parts which can be used independently - equipment records, client records, training records, materials records, for example. These parts will be developed separately and then integrated when each part of the system has been tested.
Briefly explain what requirements documentation is, and why the MakerShed team are going to need good requirements documentation for this project.
The training director of Walton MakerShed believes that spreadsheets would be adequate to record data for the charity, as this is what they have used since the charity was first formed.
Briefly present an argument to the training director to support the move from the existing spreadsheets to a database management system.
Explain the features a good DBMS will have for an organisation like MakerShed, that has multiple users of the data, will store some confidential information, and will develop new applications as the need arises.