Assessment CRUD Application

Assessment CRUD Application

1. Criteria

   • Prescribed Criteria
     • You must be able to CREATE, READ, UPDATE and DELETE records from your database.
       • Are you able to Create new records in your database?
       • Are you able to Read records in your database?
       • Are you able to Update records in your database?
       • Are you able to Delete records from your database?
     • Your results must be displayed in a Flask Web Application
       • Have you created a Web Application?
       • Are all the different pages of the web application connected through Flask?
       • Can you obtain all your results in the SQL database?
       • Are you able to display your results in the Flask Web Application?
     • You must have a minimum of 5 records in your CRUD application
       • Are all the records visible in your READ page?
       • Do your records visible in your READ page correspond with the records visible in your SQL database?
       • Are all the fields occupied with unique records?
       • Are any deleted records visible with the existing records in the READ page or the SQL database?
       • Do you have a minimum of 5 records in your CRUD Application?
     • You must apply CSS styling to your CRUD application that aligns with your user persona’s requirements
       • Have you used CSS to add a background image?
       • Have you used CSS to change the appearance of the buttons, to suit the user requirements?
       • Have you used CSS to change the font and font colour of different text, for it to stand out more?
       • Have you used CSS to change the table design to be more appropriate with the user persona?
   • Self-Determined Criteria
     • Each row must have the customer’s personal details (email, name, number), order number, description of order and order due date.
       • Do the records save the customers personal details, such as email, name, phone number?
       • Are the customer's order due date and order number saved in the records?
       • Is a description of the order the customer has placed, recorded in the application?

2. Applications

   • Coding Languages
     • HTML
       • Notepad+
         • A code example:
           • <p style=color:#48392A; > Hello Everyone! Welcome to the Bake House! Here you can view all your scheduled <br> appointments and also create new ones! We allow you to create as much columns you <br> need and you can view all of them under one page. This is an accesible application<br> created just for your satisfaction and convenience. We hope you love it!</p>
     • CSS
       • Notepad+
         • <style> body { background-image: url("https://th.bing.com/th/id/OIP.CgDh0S4DC9I8jpEZudr-0wHaHa?rs=1&pid=ImgDetMain"); } h1 { text-align: center; text-shadow: 2px 2px 5px white; background-color: #C06E52; font-size: 50px; font-family: "Times New Roman"; }
     • Python
       • Thonny
         • @app.route("/read") def read(): conn = sqlite3.connect("database.db") cursor = conn.cursor() cursor.execute("SELECT * FROM bakery") records = cursor.fetchall() conn.close() return render_template("read.html", records=records)
     • SQL
       • Sqllite
         • A code example:
           • CREATE TABLE bakery ( id INTEGER PRIMARY KEY AUTOINCREMENT, name TEXT NOT NULL, email TEXT NOT NULL, Phone_number INTEGER NOT NULL, Order_no INTEGER NOT NULL, DescOfOrder TEXT NOT NULL, DueDate DATE NOT NULL );

3. User Persona

   • Goals
     • A way to store all the necessary details and personal details of the customers that have placed orders for the bakery.
   • interests
     • Cooking, Baking (in general), Reading (fluff, adventure, fantasy), listening to music (anything that is popular and suits her taste)
   • Needs&Expectations
     • It should be able to store all the personal information of customers. They should also be able to record the order due date and clearly state what the order is (A description of the order placed).
   • Fustrations
     • Most applications either only save the description of the order placed or have the due date saved in a Calander or only have the personal details of the customers. Using different application for different things gets frustrating and messy. So, she wants everything in one application.
   • User Problem Summary
     • An application that can create, update and delete records of customers with each row having the customer’s personal details (email, name, number), order number, description of order and order due date.

4. Assessment

   • Resources
     • QLearn
     • Teacher's Feedback
     • Teams
     • Classmates / Friends help
   • CRUD Application
     • Sample Data
       • Clara Johns---Johnsons@Glive.com---172893672---81---5 croissants with chocolate and strawberry filling dusted with starwberry sugar on top---2024-11-12
       • 5---Jay Johns---Johnson@Glive.com---172673672---82---A matcha cake with cream filling and strawberry toppings---2024-11-14
     • Planned Modifications
       • CSS
         • Added background image throughout the pages for cohesion and aesthetics of a bakery.
         • Changed fonts and font sizes to fit the user's needs
         • Changes table look to be more organised and aesthetic to the user's requirements of a bakery owner.
       • HTML
         • Added new forms in Update and Create, to adapt to the new columns created for the user's needs as a bakery owner.
       • SQL
         • Deleted old table and created new table to create more columns to store customer's personal details and order details.
       • Python