Criterion A: The student describes an appropriate scenario for investigation for an identified client.

Comment: The student described an appropriate scenario, where they described who their client is (in this case, their UK college counselor), why it is appropriate (helping her in doing her job), and why it is being developed (because she struggled to keep track of essays shared on the drive and using manual logging is difficult).

Criterion A: The student provides and describes evidence of consultation for the investigation.

Comment: The student provided an evidence of consultation in the form of a transcript, and for clarity, gave context about some phrases that were translated into English where necessary in the Appendix A in this IA.

Criterion A: The rationale for choosing the proposed product is explained and justified.

Comment: The student provided a proper rationale which is written in extended writing, with reference to the students' consultation that was included in the Appendix. The student also added proper justification for why this is an effective solution. In this case, the student considered the client's lack of familiarity with modern technology and the limited resources that the client had to deal with, hence, creating an application that can run without needing high-performance hardware and ability for the client and her clients (students) to access the application from any school computer, as well as consideration to the frequent power outages and wifi cuts.

Criterion A: The student provides a rationale explaining their choice of the proposed product.

Comment: The student provided a rationale in the technical standpoint as of why the proposed product is the most appropriate, explaining it why the product would benefit the client greatly, as well as the students' technical knowledge and ability.

Criterion A: The student provides a rationale explaining their choice of the proposed product.

Comment: The student provided a rationale in the technical standpoint as of why the proposed product is the most appropriate, explaining it why the product would benefit the client greatly, as well as the students' technical knowledge and ability.

Criterion A: The student proposes a range of appropriate criteria for evaluating the success of their product.

Comment: The student had put in a range of appropriate criteria to properly evaluate the success of their product. This included not just the technical side but also how it should look (GUI) and how it can properly assist the client in the best way possible, drawing from consultations done and the information provided in the definition of the problem as well as the rationale for the proposed solution.

Criterion B: The student provides a complete and detailed record of tasks.

Comment: The student provided a complete and detailed record of tasks, which included a chronology of the key events in the planning, designing, developing, testing and implementing the solution. The student also included the things that may need to be dealt with in the record of tasks, such as if there are things that need to be fixed or improved based on further discussion with the client (task number 44) as well as including what must be done if not all of the success criteria is achieved (task number 55). This showcases the students' ability to plan ahead. It is also important to check in with the teacher to determine if the product is actually feasible and appropriate.

Criterion B: The student provides a complete and detailed record of tasks.

Comment: The student provided a complete and detailed record of tasks, which included a chronology of the key events in the planning, designing, developing, testing and implementing the solution. The student also included the things that may need to be dealt with in the record of tasks, such as if there are things that need to be fixed or improved based on further discussion with the client (task number 44) as well as including what must be done if not all of the success criteria is achieved (task number 55). This showcases the students' ability to plan ahead. It is also important to check in with the teacher to determine if the product is actually feasible and appropriate.

Criterion B: The student provides a complete and detailed record of tasks.

Comment: The student provided a complete and detailed record of tasks, which included a chronology of the key events in the planning, designing, developing, testing and implementing the solution. The student also included the things that may need to be dealt with in the record of tasks, such as if there are things that need to be fixed or improved based on further discussion with the client (task number 44) as well as including what must be done if not all of the success criteria is achieved (task number 55). This showcases the students' ability to plan ahead. It is also important to check in with the teacher to determine if the product is actually feasible and appropriate.

Criterion B: The record of tasks refers to the product proposed in criterion A.

Comment: The student planned in their record of tasks for the proposed solution in criterion A, which is a java application for their client and the record of tasks reflects that well.

Criterion B: The student provides a design overview, which includes an outline test plan.

Comment: The student provided a very extensive design overview, including not just User Interface designs complete with proper explanations for what part of the UI does what and why (not just for input but also appropriate outputs e.g. error messages) but also component diagram, database structure overview to show how the data will be managed, flowcharts for not only the main system but also the subsystems for both counselor and students, data flow diagram to show the how the data flows as the application runs in different scenarios, entity relationship diagram to show the design for the relational database, sequence diagram to show the interactions between related objects within different subsystems, UML diagrams, database schema representation, use case diagram, even going as far as including pseudocodes for key operations. This part is also bolstered by a complete test plan, attributing appropriate test methods for which criteria.

Criterion B: The student provides a design overview, which includes an outline test plan.

Comment: The student provided a very extensive design overview, including not just User Interface designs complete with proper explanations for what part of the UI does what and why (not just for input but also appropriate outputs e.g. error messages) but also component diagram, database structure overview to show how the data will be managed, flowcharts for not only the main system but also the subsystems for both counselor and students, data flow diagram to show the how the data flows as the application runs in different scenarios, entity relationship diagram to show the design for the relational database, sequence diagram to show the interactions between related objects within different subsystems, UML diagrams, database schema representation, use case diagram, even going as far as including pseudocodes for key operations. This part is also bolstered by a complete test plan, attributing appropriate test methods for which criteria.

Criterion B: The student provides a design overview, which includes an outline test plan.

Comment: The student provided a very extensive design overview, including not just User Interface designs complete with proper explanations for what part of the UI does what and why (not just for input but also appropriate outputs e.g. error messages) but also component diagram, database structure overview to show how the data will be managed, flowcharts for not only the main system but also the subsystems for both counselor and students, data flow diagram to show the how the data flows as the application runs in different scenarios, entity relationship diagram to show the design for the relational database, sequence diagram to show the interactions between related objects within different subsystems, UML diagrams, database schema representation, use case diagram, even going as far as including pseudocodes for key operations. This part is also bolstered by a complete test plan, attributing appropriate test methods for which criteria.

Criterion B: The student provides a design overview, which includes an outline test plan.

Comment: The student provided a very extensive design overview, including not just User Interface designs complete with proper explanations for what part of the UI does what and why (not just for input but also appropriate outputs e.g. error messages) but also component diagram, database structure overview to show how the data will be managed, flowcharts for not only the main system but also the subsystems for both counselor and students, data flow diagram to show the how the data flows as the application runs in different scenarios, entity relationship diagram to show the design for the relational database, sequence diagram to show the interactions between related objects within different subsystems, UML diagrams, database schema representation, use case diagram, even going as far as including pseudocodes for key operations. This part is also bolstered by a complete test plan, attributing appropriate test methods for which criteria.

Criterion B: The student provides a design overview, which includes an outline test plan.

Comment: The student provided a very extensive design overview, including not just User Interface designs complete with proper explanations for what part of the UI does what and why (not just for input but also appropriate outputs e.g. error messages) but also component diagram, database structure overview to show how the data will be managed, flowcharts for not only the main system but also the subsystems for both counselor and students, data flow diagram to show the how the data flows as the application runs in different scenarios, entity relationship diagram to show the design for the relational database, sequence diagram to show the interactions between related objects within different subsystems, UML diagrams, database schema representation, use case diagram, even going as far as including pseudocodes for key operations. This part is also bolstered by a complete test plan, attributing appropriate test methods for which criteria.

Criterion B: The student provides a design overview, which includes an outline test plan.

Comment: The student provided a very extensive design overview, including not just User Interface designs complete with proper explanations for what part of the UI does what and why (not just for input but also appropriate outputs e.g. error messages) but also component diagram, database structure overview to show how the data will be managed, flowcharts for not only the main system but also the subsystems for both counselor and students, data flow diagram to show the how the data flows as the application runs in different scenarios, entity relationship diagram to show the design for the relational database, sequence diagram to show the interactions between related objects within different subsystems, UML diagrams, database schema representation, use case diagram, even going as far as including pseudocodes for key operations. This part is also bolstered by a complete test plan, attributing appropriate test methods for which criteria.

Criterion B: The student provides a design overview, which includes an outline test plan.

Comment: The student provided a very extensive design overview, including not just User Interface designs complete with proper explanations for what part of the UI does what and why (not just for input but also appropriate outputs e.g. error messages) but also component diagram, database structure overview to show how the data will be managed, flowcharts for not only the main system but also the subsystems for both counselor and students, data flow diagram to show the how the data flows as the application runs in different scenarios, entity relationship diagram to show the design for the relational database, sequence diagram to show the interactions between related objects within different subsystems, UML diagrams, database schema representation, use case diagram, even going as far as including pseudocodes for key operations. This part is also bolstered by a complete test plan, attributing appropriate test methods for which criteria.

Criterion B: The student provides a design overview, which includes an outline test plan.

Comment: The student provided a very extensive design overview, including not just User Interface designs complete with proper explanations for what part of the UI does what and why (not just for input but also appropriate outputs e.g. error messages) but also component diagram, database structure overview to show how the data will be managed, flowcharts for not only the main system but also the subsystems for both counselor and students, data flow diagram to show the how the data flows as the application runs in different scenarios, entity relationship diagram to show the design for the relational database, sequence diagram to show the interactions between related objects within different subsystems, UML diagrams, database schema representation, use case diagram, even going as far as including pseudocodes for key operations. This part is also bolstered by a complete test plan, attributing appropriate test methods for which criteria.

Criterion B: The student provides a design overview, which includes an outline test plan.

Comment: The student provided a very extensive design overview, including not just User Interface designs complete with proper explanations for what part of the UI does what and why (not just for input but also appropriate outputs e.g. error messages) but also component diagram, database structure overview to show how the data will be managed, flowcharts for not only the main system but also the subsystems for both counselor and students, data flow diagram to show the how the data flows as the application runs in different scenarios, entity relationship diagram to show the design for the relational database, sequence diagram to show the interactions between related objects within different subsystems, UML diagrams, database schema representation, use case diagram, even going as far as including pseudocodes for key operations. This part is also bolstered by a complete test plan, attributing appropriate test methods for which criteria.

Criterion B: The student provides a design overview, which includes an outline test plan.

Comment: The student provided a very extensive design overview, including not just User Interface designs complete with proper explanations for what part of the UI does what and why (not just for input but also appropriate outputs e.g. error messages) but also component diagram, database structure overview to show how the data will be managed, flowcharts for not only the main system but also the subsystems for both counselor and students, data flow diagram to show the how the data flows as the application runs in different scenarios, entity relationship diagram to show the design for the relational database, sequence diagram to show the interactions between related objects within different subsystems, UML diagrams, database schema representation, use case diagram, even going as far as including pseudocodes for key operations. This part is also bolstered by a complete test plan, attributing appropriate test methods for which criteria.

Criterion B: The student provides a design overview, which includes an outline test plan.

Comment: The student provided a very extensive design overview, including not just User Interface designs complete with proper explanations for what part of the UI does what and why (not just for input but also appropriate outputs e.g. error messages) but also component diagram, database structure overview to show how the data will be managed, flowcharts for not only the main system but also the subsystems for both counselor and students, data flow diagram to show the how the data flows as the application runs in different scenarios, entity relationship diagram to show the design for the relational database, sequence diagram to show the interactions between related objects within different subsystems, UML diagrams, database schema representation, use case diagram, even going as far as including pseudocodes for key operations. This part is also bolstered by a complete test plan, attributing appropriate test methods for which criteria.

Criterion B: The student provides a design overview, which includes an outline test plan.

Comment: The student provided a very extensive design overview, including not just User Interface designs complete with proper explanations for what part of the UI does what and why (not just for input but also appropriate outputs e.g. error messages) but also component diagram, database structure overview to show how the data will be managed, flowcharts for not only the main system but also the subsystems for both counselor and students, data flow diagram to show the how the data flows as the application runs in different scenarios, entity relationship diagram to show the design for the relational database, sequence diagram to show the interactions between related objects within different subsystems, UML diagrams, database schema representation, use case diagram, even going as far as including pseudocodes for key operations. This part is also bolstered by a complete test plan, attributing appropriate test methods for which criteria.

Criterion B: The student provides a design overview, which includes an outline test plan.

Comment: The student provided a very extensive design overview, including not just User Interface designs complete with proper explanations for what part of the UI does what and why (not just for input but also appropriate outputs e.g. error messages) but also component diagram, database structure overview to show how the data will be managed, flowcharts for not only the main system but also the subsystems for both counselor and students, data flow diagram to show the how the data flows as the application runs in different scenarios, entity relationship diagram to show the design for the relational database, sequence diagram to show the interactions between related objects within different subsystems, UML diagrams, database schema representation, use case diagram, even going as far as including pseudocodes for key operations. This part is also bolstered by a complete test plan, attributing appropriate test methods for which criteria.

Criterion B: The design overview refers to the product proposed in criterion A.

Comment: The student referred to the product proposed in criterion A, showing proper planning and continuity in the design process.

Criterion B: Overall, it is clear to the reader how the product was developed from the student’s descriptions.

Comment: It may seem excessive to include so many diagrams, alongside a detailed test plan and record of tasks, but this gives a lot of clarity of how the product was developed and showcases the student's own ability and skills to have developed this product.

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion C:

Criterion E:

Criterion E:

Criterion E:

Criterion E:

Criterion E:

Criterion E:

Criterion E:

Criterion E:

Criterion E:

Other:

Other:

Other:

Other:

Other:

Other:

Other:

Other:

Other:

Other:

Other:

Other:

Other:

Other:

Other:

Other:

Other:

Other:

Other:

Other:

Other:

Other:

Other:

Other:

Other: