Feature: The email subscription part of the CarHub website
- Allows users to submit their email into our data base and recive emails from us
- Their data will be stored into our database
- Use a seperate API to figure out how to email the users
This feature interacts with Mati's login and will send emails with data including Taiyo's inventory system
Row 1 - Program Purpose and Function:
My program works to help users input their names into our database. By inputting their names into the database they are able to show their initials onto the website to show they are part of the subscribers list. By clicking onto the text box users will only be able to insert The first and last initial of your name. Due to the formatting of the text box users will only be allowed to use this format or else there will be a warning screen given to the user's input. The users then can click the input button and this adds their names into the database.
Purpose: Allows users to recive emails from our company about new information inputed into our website
Function: Users input their emails into our database
Input: The input is their email, I will have a confirming of a real email system later
Output: The user will recive emails from us
Row 2 - Data Abstraction:
The user inputs their information into the text box/form and when the button is clicked their data is automatically input into the database. Their information is carried from the database into the table in the website. Their initials are then displayed onto the website's table. The initial information in the text box will only allow initials to be input into the table, this is a measure to make sure that the user's information will not be as revealed. The text box also has restrictions which only allows the user to input letters and the "." so then there won't be any numbers input into the "subscriber's initials" table.
First Segment: Show the user emails in the database
Second Segment: The data will be used to create emails to send to users emails in the database
Variable: Will be called the "useremails"
Row 3 - Managing Complexity:
Each of the user information is sorted well,
Lists: The user emails will be stored into a list and will be retrived from the database
Explanation: "userinfo" without the user's email information the program will not be able to email the users and in the end, not work properly
Row 4 - Procedural Abstraction:
Procedure: "user_email" collects the data provided by the user and inserts it into the database
Contribution: "user_email" allows the user to input their data into the database or used for other info for the users
Row 5 - Testing:
Call 1: A wrong email which isn't 'real' --- Result: The API creates a text anouncment which shows that the email isn't valid
Call 2: A right email/ 'real' email --- Result: the email is accepted into the database and shows it is inside of the database
My video will be similar to those with the full points. Using the CSP grading that we did these last two weeks I will be able to identify whether or not my project fulfills the goals. I will input a right and wrong email and show that my API can identify a real email from a fake email. I will also show my API which shows the emails being input into the database.