Build Website

1. Project scope and client requirements This section will need to include an introduction to the project and the chosen scenario. You will also be expected to consider the possible requirements the client will have for your system – together with a discussion of how you would (in an ideal environment) gather the requirements. You must not engage in any requirements gathering activities. You will need to include: · The requirements listed above (applied to your specific case study) – do not just copy and paste the requirements · Additional requirements which may not have been covered by the assignment brief (applied to your specific case study) Your module leader will act as the client if you want to discuss possible requirements. 2. User interface diagrams You will need to include wireframe versions of your user interface. Each screen should be represented as a wireframe. In addition to the diagrams you will need to consider the accessibility and usability of your interface, especially in relation to Sustainable Development Goal 10: Reduced Inequalities. 3. Class diagrams You will need to use UML to demonstrate how your classes interact with each other. In addition, you will want to include a database design diagram. It would also be expected that you will provide some additional information relating to the diagrams. In the class diagram, make sure that you demonstrate good use of object-oriented programming principles and evidence of inheritance. This section should also include a discussion of the relevant design patterns you have incorporated within your design. If you have not included any design patterns, you must discuss your justification for this decision. 4. Testing documentation Your testing documentation will have two elements: · Testing plan · Evidence of testing results It would be expected that your testing plan covers data validation to ensure that your inputs and outputs are both correct. Additionally, when a test fails, it is anticipated that you will demonstrate how you resolved the problem as well as the evidence of re-testing to ensure accuracy. 2.2. Source Code For this assignment, you will need to submit your source code. You will be required to submit your .java files. You must also include a README file which explains to the marker how to implement your program so that the functionality can be verified. The source code must implement object-oriented programming techniques and must be in the Java programming language – no other languages will be accepted. When developing your program, you need to consider the quality of the code you are producing. The code quality of your submission will be considered during the marking process. 2.3. Project Demonstration The final part of your summative assignment will be to present your system to an audience, through the use of a live demonstration. The demonstration should include: an overview of the system itself (including the client requirements) and all the features of the system. You should assume that the audience do not have any technical knowledge, so your presentation should be appropriate for the layman. You will lose marks if you present a demonstration which contains too much information which would not be understood by a non-technical audience.