I only need the full report completed.Please provide me with the report. Please see attached100 % of the source code is complete (CST8333 - Cynthia Haddad - Source Code)Please...







I only need the full report completed.


















Please provide me with the report. Please see attached


100 % of the source code is complete (


CST8333 - Cynthia Haddad - Source Code)





































Please continue part three (assignment 3) of assignments 1 and 2. Follow my assignment 1 and 2 reports and presentations (Cynthia Haddad - Assignment 1. Zip file) & (















Cynthia Haddad - Assignment 2. Zip file)














to be able to complete assignment 3 (CST8333_Assignment-3_Instructions) Please find attached assignment 3 with all of the instructions as well as an example (cst8333_assignment-3_student-example) and outline (CST8333_Assignment-3_Outline_2021-03-12).






















Python Flask Code from flask import Flask, render_template, request import sqlite3 app=Flask(__name__) @app.route('/') def index(): return render_template('login.html') @app.route('/ind') def ind(): return render_template('signup.html') @app.route('/hell',methods = ['POST', 'GET']) def hell(): if request.method == 'POST': con = sqlite3.connect('mydatabase.db') uname = request.form['uname'] pwd = request.form['pwd'] cursorObj = con.cursor() cur = con.cursor() cursorObj = con.cursor() login=cursorObj.execute("SELECT * FROM signup WHERE email= ? and pwd= ?;",(uname,pwd)) con.commit() if (len(login.fetchall()) > 0): return render_template("secret.html") else: return render_template("login.html") @app.route('/gol',methods = ['POST', 'GET']) def gol(): if request.method == 'POST': con = sqlite3.connect('mydatabase.db') fname = request.form['fname'] lname = request.form['lname'] email = request.form['email'] pwd = request.form['pwd'] pwdr = request.form['pwdr'] cursorObj = con.cursor() cursorObj = con.cursor() login=cursorObj.execute("SELECT * FROM signup WHERE email= ?;",(email,)) con.commit() if (len(login.fetchall()) > 0): return render_template("signup.html") else: cursorObj.execute("INSERT INTO signup(fname,lname,email,pwd,pwdr) VALUES('"+fname+"','"+lname+"','"+email+"','"+pwd+"','"+pwdr+"')") con.commit() return render_template("thankyou.html") if __name__=='__main__': app.run() # Level 1: Basic user access @app.route('/') def index(): return render_template('login.html') @app.route('/login', methods=['POST']) def login(): email = request.form['email'] password = request.form['password'] conn = sqlite3.connect('mydatabase.db') cursor = conn.cursor() cursor.execute("SELECT * FROM users WHERE email=? AND password=?", (email, password)) user = cursor.fetchone() if user: return redirect(url_for('dashboard')) else: return render_template('login.html', error='Invalid email or password') # Level 2: Admin access @app.route('/dashboard') def dashboard(): # Check if user is an admin if not is_admin(): return redirect(url_for('index')) return render_template('dashboard.html') def is_admin(): email = request.form['email'] conn = sqlite3.connect('mydatabase.db') cursor = conn.cursor() cursor.execute("SELECT * FROM users WHERE email=?", (email,)) user = cursor.fetchone() if user and user[3] == 'admin': return True else: return False # Level 3: Super admin access @app.route('/admin') def admin(): # Check if user is a super admin if not is_super_admin(): return redirect(url_for('index')) return render_template('admin.html') def is_super_admin(): email = request.form['email'] conn = sqlite3.connect('mydatabase.db') cursor = conn.cursor() cursor.execute("SELECT * FROM users WHERE email=?", (email,)) user = cursor.fetchone() if user and user[3] == 'super_admin': return True else: return False if __name__ == '__main__': app.run(debug=True) Login.html Login Form Username Password Login Remember me Don't have an account? Signup Here Secret.html Logout Signup.html Sign Up Please fill in this form to create an account. First Name Last name Email Password Repeat Password Remember me By creating an account you agree to our Terms & Privacy. Cancel Sign Up Thankyou.html Login Assignment 1 CST8333 PROGRAMMING LANGUAGE RESEARCH PROJECT – ASSIGNMENT 3 CST8333 PROGRAMMING LANGUAGE RESEARCH PROJECT – ASSIGNMENT 3 CST8333 Assignment 3 < project="" name=""> < your="" name=""> < date="" submitted=""> All material prepared for this assignment was produced by the author. Material from all third parties has been cited and referenced. CST8333 PROGRAMMING LANGUAGE RESEARCH PROJECT – ASSIGNMENT 3 CST8333 PROGRAMMING LANGUAGE RESEARCH PROJECT – ASSIGNMENT 1 19 Table of Contents 1Introduction3 1.1Objectives3 1.2Scope3 1.3Timeline3 1.3.1Milestones and Deliverables4 1.4Risks4 1.5Assumptions5 1.6Technical Constraints5 1.7Budget5 2Status7 2.1Introduction7 2.2Accomplishments7 2.3Goals7 2.4Roadblocks7 2.5Lessons Learned7 2.6Next Steps7 3Source Code Implementation8 3.1Introduction8 3.2Coding Checklist8 3.3Submit Code9 4Testing10 4.1Introduction10 4.2Requirements Traceability Matrix10 4.3Test Tracking Tools12 4.4Test Environment12 4.5Test Scripts12 4.6Test Log12 4.7Support Checklist12 4.8Final Test Report12 5Deployment14 5.1Introduction14 5.2Software Integration Plan14 6References16 7Appendix A: Module 10 Checklist17 8Appendix B: Module 11 Checklist18 9Appendix C: Module 12 Checklist20 10Appendix D: Module 13 Checklist22 11Appendix E: Assignment Grading Rubric24 Introduction In this section background information on the project is provided, including the reasons for undertaking the project, specifically the business problem to be solved and how the proposed system will solve it, as well as the key stakeholders who will benefit from the project results. Objectives In this section measurable project objectives, business outcomes to be derived from achieving the objectives, and the measurement criteria to be used to confirm that an objective and the outcome have been achieved are listed. Table 1: Objectives and Business Outcomes (example) No. OBJECTIVE BUSINESS OUTCOME MEASUREMENT CRITERIA 1 Solve < state="" the="" problem="">> Users are able to < state="" user="" capabilities="">> Reduction and/or increase in < state="" criteria="">> 2 3 Scope In this section the features and functions that characterize the product, service, or result to be delivered by the project are described. That is, the major activities that must be completed to complete the project are listed. Activities that are out of scope for the project also are listed to reduce ambiguity. Table 2: Project Scope (example) ACTIVITIES IN SCOPE ACTIVITIES OUT OF SCOPE 1. Assignment 1 1. Apply for business financing 2. 2. 3. 3. Timeline In this section the project timeline is illustrated. The project duration is based on the CST8333 course calendar. Tasks included in the timeline are based on checklists included in CST8333 course modules. It is understood that unforeseen events and changes may result in revisions to the project timeline. Table 3: Project Timeline (example) Legend · Purple bars = Level 1 tasks · Blue bars = Level 2 tasks · Green bars = Level 3 tasks Please find, below, a template for a project timeline. Milestones and Deliverables In this section significant events in the project and their associated deliverables are defined. Table 4: Project Milestones and Deliverables (example) MILESTONE DATE DELIVERABLES 1. Assignment 1 complete October 8 2020 Written report and slide presentation 2. 3. Risks Project risks are uncertain events or conditions that, if they occur, have positive effects (opportunities) or negative effects (threats) on one or more project objectives, such as scope, schedule, cost, and/or quality. In this section the principle project risk is identified (e.g., schedule slippage, requirements inflation, conflicting requirements, deliverables quality) the likelihood it will occur is estimated (high, medium, low), its impact if it occurs is estimated (high, medium, low), and mitigation strategies are described (how likelihood and impact will be minimized). Table 5: Project Risks (example) No. RISK DESCRIPTION PROBABILITY (H/M/L) IMPACT (H/M/L) MITIGATION 1. Schedule slippage M H Track project scope and timeline Assumptions Assumptions are factors that you believe to be true, although they are not confirmed to be true. Assumptions add risk to a project since it is possible that they will turn out to be false. Assumptions can impact any part of your project life cycle and resulting solution implementation, so it is important that they be documented.  In this section the principle project assumption is identified. Table 6: Project Assumptions (example) No. THE FOLLOWING IS ASSUMNED 1. Fundamentals of new programming language will be learned and put to use, timely, to complete project Technical Constraints Constraints are fixed boundary conditions or limits on what you can do. They are the things you cannot change but that you need to be aware of and manage to. Technical constraints focus on architecture decisions that may limit your solution design. They tend to be inflexible and unchanging and may impact your solution implementation. They include areas such as development languages, hardware, other infrastructure, and software that must be used for your project. In this section the principle technical constraint is identified. Table 7: Technical Constraints (example) No. TECHNICAL CONSTRAINTS 1. Programming language selected does not accommodate all of the functionality desired in the solution Budget The project budget is a tool that is used to estimate all the costs that are likely to be incurred before the project is completed. In this section a preliminary budget is estimated. Only in-scope items, as identified in section 1.3 above, are included. Out of scope items are excluded. It is understood that unforeseen events and changes may result in revisions to the project budget. Table 8: Project Budget (example) Notes 1. It is not expected that you will incur out of pocket expenses to complete the project. As such, it is acceptable that the budget includes only level of effort estimates. 2. Please find, below, a template for a project budget. Status Introduction Provide a brief overview of the contents of the status report (one or two paragraphs). Consider writing this after the other sections in the status report are complete. Accomplishments Detail what the task completed, when they were completed, and indicate if they were completed early, on time, or late (if late, then how will the task be brought back on rack). Goals List the goals for the period covered by the report (e.g., daily goals, weekly goals, and/or monthly goals) and indicate if they were achieved or not achieved. Roadblocks Explain what, if anything, prevented you from achieving your goals and/or might prevent you from achieving upcoming goals. Lessons Learned Document actions to be taken to build on successes and avoid repeating breakdowns. Next Steps Describe what actions, if any, will be taken to further develop or promote the project post-deployment. Source Code Implementation Introduction During the implementation phase of the software development life cycle (SDLC) the development team creates the agreed upon solution to the business problem identified at the outset of the project. Project developers build the software in the staging or development environment using the programming language that was chosen in the previous phase of the project
Apr 10, 2023
SOLUTION.PDF

Get Answer To This Question

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here