辅导 BISM7255 CREATE CHANGE讲解 Java程序

UQPLAY Individual Assignment – Reflection Journal

This assignment is the second part of the UQPLAY Toy Library project. Building on the team- based system analysis and UML design completed earlier in the semester, each student is now required to develop a working prototype of the UQPLAY app using GlideApps and to submit an individual reflective journal about their learning process.

The aim of the reflective journal is to provide an opportunity for you to critically evaluate your experience learning GlideApps and developing a no-code application that meets business requirements. Your reflection should move beyond describing what you did and instead focus on analysing how and why these learning experiences were meaningful and what they mean for your personal development and future career.

What You Need to Submit

1. GlideApps Prototype: A functioning app that aligns with the requirements from your Assignment  1.  You  must  share  access  with  the  assessment  team  (instructions provided below).

2. Individual   Reflective Journal: A  Word  document  containing  your  personal reflections, structured into the two sections described below.

A. GlideApps Prototype Application

You must submit your functioning Glide application:

1.  Go to your app on the GlideApps platform.

2.  Click “Members” then “Send Invite” to the following email addresses as Admin:

o  [email protected]

3.  Ensure your app name includes your Subject Code and full name using this format:

o  BISM7255_Emily_Lee

Requirements for Your UQPLAY Toy Library Application

Your task is to build a working prototype of the UQPLAY Toy Library application using GlideApps. The app must demonstrate the core functional requirements of the system as identified in Assignment 1 and reflect thoughtful design, data structure, and user interaction. This prototype must include both customer-facing features and administrative functions (e.g., toy management, maintenance logs). You are required to demonstrate an understanding of Glide's layout, logic, data relations, and user roles.

1. Application Functionality – Minimum Features to Include

1.1. Toy Browsing and Booking

Your application must begin with a homepage or welcome screen that provides clear navigation options such as Browse Toys, My Bookings, Submit Feedback. The home screen should be simple and intuitive, enabling a first-time user to quickly locate where to browse or manage their bookings.

From the homepage, users should be able to access a toy catalogue page that displays key details for each toy, including toy name, image, age group (e.g., 0–2, 3–5, 6–8, etc.), Genre  (e.g.,  pretend  play,  physical  activity,  puzzles),  and  availability  status.  The catalogues should be easy to scan, with filters and search functions that allow users to narrow results by age group or genre.

When viewing the catalogue, users must also be able to open a toy detail view that presents more information about the selected toy and are able to filter/search by genre or age group. From here, customers should have the ability to book a toy with a specified loan duration provided it does not exceed the maximum allowed. A clear confirmation screen should be shown at the end of the booking process, summarising the selected toy and loan period before the booking is finalised.

1.2. Maintenance and Return Handling

Your application must include a return form that allows the user to complete the return process in a straightforward way. The form should enable customers to confirm return, provide a rating for the toy, leave optional written feedback, and report a missing part or damage (e.g., checkbox or free text).

In addition, the system must provide an administrative page for maintenance staff. This page should present toy condition reports log completed by customers and allow staff to log completed repairs or cleaning tasks. Staff should also be able to update the toy’s status to indicate whether it is ready or not ready for loan. For baby toys in particular, the interface should make it easy to track and update cleaning status, ensuring safety and hygiene before toys are returned to circulation.

1.3. Deposits and Special Cases

Some toys, such as console games or other high-value items, may require a deposit before they can be borrowed. Your application must be able to recognise toys flagged as “deposit required.” When a customer attempts to book one of these toys, the system should display a clear warning message along with the required deposit amount.

1.4. Lifecycle & Toy Retirement

The appIication shouId aIso support toy IifecycIe management through an administrative screen or section. This feature must aIIow staff to view a toy’s usage history, incIuding the number of Ioans it has been through, and any condition reports associated with it. Based on this history, staff shouId be abIe to update the toy’s status to indicate whether it is Active, Retired, or For SaIe. If toys are moved to the For SaIe category, the interface shouId aIso aIIow customers to view a Iist of toys avaiIabIe for purchase.

2. Layout Pages

To ensure consistency and usabiIity, your appIication must contain a set of core screens that cover both customer-facing and administrative functions.  Each  page  shouId  be designed with cIarity and ease of navigation in mind, so that users can intuitiveIy move between browsing, booking, returning, and managing toys. At a minimum, the foIIowing pages shouId be impIemented:

•      Homepage / Landing screen

•      Toy cataIogue / Iisting screen

•      Toy detaiI page (with booking option)

•       My Bookings / My Loans page

• Submit Return/Feedback page

•      Admin dashboard or menu (restricted to admin users)

•      Toy management screen (create, update, retire toys 一 admin users)

• Maintenance Iog screen

•       Retired toys for saIe (optionaI“Buy”interaction or contact prompt)

3. Data Domain Model

You are expected to define and manage your own data structure to support the required appIication functionaIity. The modeI shouId capture the key entities in the toy Iibrary system and cIearIy define how they reIate to one another. Each tabIe shouId incIude meaningfuI attributes, with appropriate data types and vaIidation ruIes to ensure reIiabIe operation. At a minimum, your modeI must incIude the foIIowing tabIes:

•     Users 一 managed for you by GIide

•    Toys

• Bookings

•     Returns / Feedback

•     Maintenance Logs

•     SuppIiers

• Purchase Orders

•     SaIes / Retired Toys

Your domain modeI wiII be assessed based on the overaII appropriateness of the entities and  their  attributes,  the  correctness  of  the  associations  between them  (for  exampIe, ensuring that toys are properIy Iinked to bookings and feedback), and the suitabiIity of fieId types and visibiIity  Iogic, such as the  use of dropdowns,  reIations,  or  BooIeans where appropriate.

4. User Roles / Navigation

To meet the minimum expectations, your application must demonstrate role-based access, clear navigation, and basic interaction functionality. These requirements ensure that users can move seamlessly between different parts of the app and that actions such as saving, submitting, or cancelling are consistently available where needed. At a minimum, your app must include:

•    At  least two  user roles: Standard Customer and Admin (you can use Glide’s role features)

•     Navigation menu or buttons for moving between major app sections •    All screens should be accessible based on the user’s role

•     Pages with Save, Cancel, or Submit options where appropriate

5. Actions and Logic

Your application must demonstrate interactive functionality through the implementation of at least   five   meaningful   actions.   These   actions   should   support   both   customer   and administrative workflows, showing how users can engage with the system beyond simply viewing data. Use visibility rules and action buttons to ensure that actions are dynamic, context-sensitive, and only available to the relevant user roles. At a minimum, the following actions must be implemented:

•     Booking a toy

•     Returning a toy

•     Submitting a condition or maintenance report

•     Logging a maintenance task

•     Marking a toy as retired

6. Test Data and Demonstration

To showcase the full functionality of your application, you must populate it with sufficient and varied test data. This data should reflect realistic use cases and demonstrate how different features  of the  system  work  together. Your  submission will  be  assessed  not  only  on functionality but also on how clearly the test data illustrates the intended workflows. At a minimum, your app must include:

•    At least 10 toys across different genres and age groups

•    At least 3 bookings made by a test user

•    At least 2 return reports with associated feedback

•    At least 3 toys with maintenance logs

•    At least 1 toy marked as retired

7. User Interface and Design

The usability and presentation of your application will be assessed alongside its functionality. A clear and consistent interface ensures that users can navigate easily and interact with the system without confusion. Pay attention to layout, readability, and overall visual appeal, and ensure design choices support the app’s purpose rather than distract from it. The UI must:

•     Be clean and consistent

•     Use a sensible colour scheme (buttons, headers, forms)

B. Reflective Journal Requirements

Your reflective journal is an important part of the assessment. It should demonstrate critical thinking, self-awareness, and the ability to connect your experiences with broader ideas about app development and digital solution design. Please use the headings provided below and structure you’re writing accordingly. Your  reflection should go  beyond  description, offering personal and thoughtful insights into your learning journey.

1. Two Significant Learning Experiences

Reflect  on  two  distinct  and  specific  learning  experiences  you  encountered  during  the development of your GlideApps prototype. These should be unique turning points rather than ongoing tasks. Each should be:

• A clearly defined moment or event, not a vague summary of activity.

•    Explained in terms of what happened and why it was meaningful.

•   Connected to your growth in understanding no-code app development, system thinking, interface design, or digital solution delivery.

For each learning experience, discuss:

• What happened? What triggered the learning?

• Why was it significant to your progress?

•    How did it challenge or change your thinking?

• What skills, knowledge, or confidence did you gain?

Avoid  simply  describing  technical  features;  instead,  explain  what  you  realised  about yourself, your abilities, or your assumptions as a result of these moments.

2. Three Implications for Your Career

In this section of your reflective journal, you are asked to think ahead and consider how your experience  with   GlideApps   and   this   project   connects   to   your  future   professional development. The focus is on career relevance, how what you learned here informs your aspirations, your view of digital innovation, and the kinds of roles you might pursue. You should discuss three specific ways in which this project and your experience learning GlideApps has impacted your thinking about your future career.

For each career implication, reflect on:

•   What  kind  of  professional   role   (e.g.,  business  analyst,   product  owner,  digital consultant) this learning supports.

• What skills you now see as important for your career.

•    How this experience has shaped your understanding of technology in business.

•    How this learning positions you better in the job market or changes your approach to digital innovation.

This section is about forward thinking. Consider how you will apply the insights gained from this project in your future workplace or study.

Submission Guidelines

To ensure all parts of your assessment are submitted correctly and consistently, please follow the requirements below.

•     Submit your journal as a Word document or PDF file via Blackboard

•     File name format:  [StudentID_Firstname_Lastname_Reflection.docx or pdf]

•    Your journal should include:

o  Title Page with Assignment Title, Name, Student ID

o  Section Headings as outlined above

o  Proper grammar, spelling, and paragraph structure

o  APA referencing if any external sources are used (not required)

Marking Focus

The reflection will be assessed based on:

•    Depth and insightfulness of reflection (not just description)

• Clarity and relevance of the learning experiences

•   Connection to professional development and future careers

•   Structure, coherence, and professionalism of writing

• Authentic linkage between the reflection and the app submitted

Marking Rubric – 20 Marks