The relationship between requirements, testing and the maintenance of a working
version of code.
Requirements are needed for code to be written so that the developers know what they are coding
for and what they can expect to build around testing needs working code to test and maintanance of code needs tested code to fix bugs/ security concerns and development needs maintanance of working code to fix bugs/patch security concerns. They all rely on each other
Under stressed conditions such as management suggesting they release a product early this may cause a conflict of priorities such as whether in the limited time you should complete a requirement; make sure something isn't bugged or fix a security concern
• The order in which you did the work and what you would do differently if you could do it
again. Remember that, in this assessment, you need to prioritise the database architect.
I used the waterfall method This involves doing all of your planning and research at the start then designing the solution then implementing the solution then doing the testing once all functionality has been written then deploying the software (adobe 2022) this was useful in that I could work out what the system needed all at the beginning so that I can now work on my code knowing how everything intertwines with each other However if I used a different method such as agile which prioritises responding to change over following a plan Wambler, S. (2011) I could have altered my requirements as I worked so that it could fit in line with how the development was going which could have led to more efficient software production
• The notion of “batch size” (i.e. how many items are being worked on at the same time).
As this system has 1 developer, the batch size is 1 but batch size can also refer to the scale of each item being worked on. For my sliced user storied I would say they are adequate size but my unsliced use cases are a bit too big. If a batch size (No. of items being worked on) is too small then that could mean that development time could be increased causing delays/ if its too big
however, then some developers may be left waiting for an item to be completed so they can start their item
• Based on your experiences from this assessment and previous projects, what is your
personal preferred process for managing, documenting and communicating
bibliography
Waterfall methodology: Project management | Adobe Workfront (2022). Available at: https://business.adobe.com/blog/basics/waterfall (Accessed: March 22, 2023).
Wambler, S. (2011) Waterfall methodology: Project management | Adobe Workfront, Examining the Agile Manifesto. Available at: http://www.ambysoft.com/essays/agileManifesto.html (Accessed: March 22, 2023).
