FIA2 Part BB

FIA2 Part BB

1. Ideation/Processing

   • HTML
     • BootStrap
       • Bootstrap framework(with css) to achieve sophisticated features
         • Linked to HTML from url address
       • Body elements encased within a container class
     • Header with a collapsible navigation bar
       • Navigation bar
       • Collapse
     • Body displaying data and editing capabilities
       • Add data button and pop up message
       • Table with user data
       • Update pop-up box and input areas
       • Insert data pop-up box and input areas
       • Footer with copyright notice
       • Scripts
   • CSS
     • Bootstrap
       • The bootstrap CSS corresponding to the bootstrap HTML to create sophisticated features
     • sticky-footer-navbar
       • Provided styling for the footer
     • Personal
       • The colour changes and backgrounds that have precedence over the other 2 stylesheets
   • SQL
     • Possible Error Messages
       • The card type is entered incorrectly in the card details
         • Create a drop down menu of card types for ease of processing by the database and inputting
       • Dates are entered in the incorrect structure(USA, with / or : ) or incorrect by mistake
         • All dates entered by drop down menus to ensure correct structure, readable for the database
       • If multiple people have the same birthday or card expiration date/type of card or alias or password
         • Using a relative schema instead of a flat file database (single file) will prevent.reduce such errors
     • Tables
       • Validations rules
         • Primary keys
           • cardID, cardexpirationID, userID, dobID
         • Foreign keys
           • cardexpirationID (card table), dobID (user table), cardID (user table)
         • Not null
           • alias, email, password, birthyear, adminflag
         • Unique
           • cardId, userID, dobID, cardexpirationID, email, password, ccv
         • Format
           • Email
             • Contains @ and .com and no space
       • cardexpiration
         • Contains the expiration dates of credit cards
         • Contains cardexpirationID, expirationmonth, expirationyear
       • card
         • Contains credit card details
         • Contains cardID, cardexpirationID, cardtype, ccv
       • user
         • Contains individual user details
         • Contains userID, alias, emaill, password, dobID, cardID, adminflag
       • dob
         • Contains user date of birth/age information
         • Conatins dobID, birthday, birthmonth, birthyear and parentcontrols
       • A relational schema would be the most efficient way to store the data, reducing repeats and redundancies
       • Relationships
         • cardexpiration and card
           • 1 to 1
         • dob to user
           • 1 to 1
         • email to user
           • 1 to 1
         • card to user
           • 1 to 1
     • Managing databases
       • Creating databases
       • Selecting from databases
         • Statements responding to user input through python to display information
       • Inserting into databases
         • Statements responding to user input through python to add to database upon sign up or modification
       • Deletion from databases
         • Statements responding to user input through python to delete user information from database
   • Python: Thonny
     • Flask library
       • Import libraries and attachments
       • Name app
       • Draw data from database and display on HTML template
       • Insert data into database from HTML forms
       • Update existing data in database with information from HTML forms
       • Delete data from database from signal from HTML templates

2. Functional Requirements

   • The user should be able to access their personal information for correction /modification/deletion
     • The website should be able to correctly identify a user's personal information in a database and display it in an understandable format
       • Use of the table, list, etc.
   • Administrators should be able to view/access/modify/add/delete user data
     • The user information in a database should be displayed in an understandable format
       • Table, list, etc.
       • A search could be used to locate user information quickly and efficiently
   • The user should be able to sign up/add their information to the database
     • A sign up/input form should be displayed in an understandable way to the user
       • Use of a variety of input types to ensure the validity of the input
         • Checkboxes, radio, textboxes, etc.

3. Non-functional Requirements

   • Useability Principles
     • See Part A
   • Australian Privacy Principles
     • Open and transparent management of personal information
       • Inclusion of a clearly expressed and up-to-date privacy policy
       • Warnings when personal information is being gathered
     • Anonymity and pseudonymity
       • User can play under an alias
     • Collection of solicited personal information
       • Through use of a formal sign up page
       • Outline in Privacy Policy
     • Dealing with unsolicited personal information
       • Outline in Privacy Policy
     • Notification of the collection of personal information
     • Use or disclosure of personal information
       • Outline in the Privacy Policy
       • Personal information will not be used or disclosed
     • Direct marketing
       • Not applicable. Information will not be disclosed for marketing purposes.
         • Outline in Privacy Policy
     • Cross-border disclosure of personal information
       • Not applicable. Information will not be disclosed overseas.
       • Outline in Privacy Policy
     • Adoption, use or disclosure of government related identifiers
       • No government identifiers implicated
     • Quality of personal information
       • Quality of information collected dependent on the user
       • Could send a verification email
     • Security of personal information
       • Website and database encrypted
       • Data destroyed should there be security risk
     • Access to personal information
       • User personal information produced when required
       • Able to view personal information on personal account page
     • Correction of personal information
       • User may make corrections to personal information if required
       • User may edit personal information on account page
   • Design Elements and Principles
     • See Part A

Imágenes y archivos del mapa