Please provide me with 100% of the source code as well as the report.
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).
For the purposes of
Assignment 3
there are
three
documents that must be submitted and in which the requirements must be captured, as follows.
Report
Source Code
Please Note
Please submit a minimum of 100% of the source code for your project. Please submit your code in text file (e.g., .txt) format.
Assignment 1 CST8333 – ASSIGNMENT 3 – INSTRUCTIONS CST8333 – ASSIGNMENT 3 – INSTRUCTIONS CST8333 Assignment 3 Testing & Deployment: Report & Presentation INSTRUCTIONS All material prepared for this assignment was produced by the author. Material from all third parties has been cited and referenced. CST8333 – ASSIGNMENT 3 – INSTRUCTIONS CST8333 PROGRAMMING LANGUAGE RESEARCH PROJECT – ASSIGNMENT 1 3 Table of Contents 1Instructions2 1.1Introduction2 1.1.1Objective2 1.1.2Pre-assignment Instructions2 1.1.3Submission Guidelines2 1.2Report3 1.3Presentation4 1.4Source Code6 2Assignment 3 Grading Rubric7 3References9 4Module 10 Checklist10 5Module 11 Checklist11 6Module 12 Checklist13 7Module 13 Checklist15 8Frequently Asked “What the . . .?!” Questions17 Instructions Introduction This assignment relates to the following Course Learning Requirements (CLR). CLR 1: Investigate programming languages (not already studied in program) and confirm appropriate choice with course professor. CLR 2: Using an identified software methodology, create a plan to accomplish goals and seek approval from professor. CLR 3: Create prototypes to be reviewed by professor at regular intervals. CLR 4: Construct secure, tested, and documented program code. CLR 5: Manage time and resources to complete planned project on time and according to goals. Objective Complete and submit a report and a presentation documenting the activities completed during the third phase of a programming research project. Pre-assignment Instructions Through week ten through thirteen of this course you used the detailed checklists included in course modules to track your completion of the requirements of Assignment 3. Reminder If a checklist item is not applicable to your project, then please provide a brief explanation as to why. For the purposes of Assignment 3 there are three documents that must be submitted and in which the requirements must be captured, as follows. 1. Report 2. Presentation 3. Source Code Please Note Please submit a minimum of 100% of the source code for your project. Please submit your code in text file (e.g., .txt) format. Please find in the sections below the checklists for each of the Assignment 3 report and presentation. Use the checklists to validate that you have completed the requirements of the assignment. Submission Guidelines 1. Submit your Report in the format prescribed in section 1.2 Report. Please submit your presentation in the format prescribed in section 1.3 Presentation of this document. Please submit your source code in text file (e.g., .txt) format, as illustrate in section 1.4 Source Code. Include the following information on the cover page of your documents. > Your name > Course name > Assignment number > Date submitted > The following statement, “All material prepared for this assignment was produced by the authors, and material from a third parties, including the Internet has been cited and referenced.” 2. Use of External Material Algonquin College has strict policies regarding plagiarism and academic misconduct. While you can research material from the Internet, you cannot use it directly for this assignment. Please ensure that all materials, including external templates, are appropriately cited, and referenced. If unreferenced third-party material is found within your submission, either the offending section will be assessed at zero, or the entire submission will be rejected. The College can impose additional sanctions, if deemed warranted. 3. Late Submissions If a valid reason exists and you cannot submit the assignment on time, you must notify the facilitator at least 24 hours in advance of the due date. Extensions are possible under certain conditions. If an assignment is submitted late without approval, it can be subject to late penalties, as well as being returned with only a grade assessment (without accompanying detailed feedback and comments). 4. Submission Method and File Naming Convention. Electronic submission by uploading your file to Brghtspace by the due date. Please use the following file naming convention. File Naming Convention: FirstName LastName Assignment 3 Report A “Word” document that includes but is not limited to the following high-level sections, status, source code implementation, testing, and deployment. Please Note For reference purposes an outline of the Assignment 3 Report, which includes sample content, is provided separately. Please use the checklist, below, to validate that you have completed the requirements of the Report. Table 1: Report Checklist (see Module 14) Activity Completed If “No” Please Explain Completion of Testing phase. Yes/No Selection of Testing tool to be used to test the project application and submit the testing results to the facilitator. Yes/No Facilitator approves the testing result. Yes/No Completion of Project Deployment Phase. Yes/No Completion of Project Presentation phase. Yes/No Completion of adding references in your project report. Yes/No Submission of final and complete project source code. Yes/No Submission of final Power Point Presentation includes brief information of each project development phase. Yes/No Submission of Project progress Report [word file], having detailed information about all the project development phases. Yes/No Feedback taken from facilitator regarding all your submissions [presentation and report]. Yes/No Discussion between Facilitator and Developer regarding any updates suggested by the facilitator. Yes/No Submit the final presentation and final project report to the facilitator within the given deadline. Yes/No Facilitator approves the final submission. Yes/No Presentation A “Slide Deck” that summarizes the information in your Report and that includes at minimum the following sections, introduction, details, and conclusion. Please Note For reference purposes an outline of the Assignment 3 Presentation, which includes sample content, is provided separately. Please use the checklist, below, to validate that you have completed the requirements of the Presentation. Items applicable to the Assignment 3 Presentation are highlighted in BLUE font. Table 2: Presentation Checklist (see Module 13) Activity Completed If “No” Please Explain Select proper template [should be simple] for your project presentation. Yes/No Your presentation should be separated in three parts: Introduction, Details and Conclusion. Yes/No Is introduction added to the presentation? Yes/No Is project requirement collection information added to the presentation? Yes/No Is feasibility report information added to the presentation? Yes/No Is project design information added to the presentation? Yes/No Graphics, Images, Flowcharts etc. related to your project added to the presentation? Yes/No Are tools and technology related to the project added to the presentation? Yes/No Is the project timeline information added to the presentation? Yes/No Is information regarding project code [You can include a hyperlink in your presentation which opens your code] such as environment and IDE used in project added in the presentation? Yes/No Are workable application screenshots added in the presentation? Yes/No Are advantages of your project added in the presentation? Yes/No Is future possible work for your project added in the presentation? Yes/No Is the conclusion added to the presentation? Yes/No Is your presentation submitted to the facilitator? Yes/No Feedback taken from the facilitator? Yes/No Is the final presentation submitted to the facilitator within the given timeline? Yes/No Source Code A “Text File” that includes 100% of your source code. Please Note For reference purposes an Assignment 3 Text File, which includes sample content, is provided separately. Please use the image, below, as a guideline for submitting your source code. Figure 1: Source Code Text File Assignment 3 Grading Rubric Please find, below, the criteria against which Assignment 3 will be graded. Criteria Excellent 80-100% Good 50-79% Requires Improvement <50% points assignment quality all information offered is accurate all views are clearly expressed and well explained contains original ideas, connections, or applications most information offered is accurate most views are clearly expressed and explained contains mainly original ideas, connections, or applications some or no accurate information offered views are rarely or never clear and require further explanation many non- original ideas, or unclear connections or applications /15 assignment knowledge and skills demonstration clear, concise synthesis of course content to demonstrate understanding of topic all ideas are clearly developed, organized logically, and connected with effective transitions explores ideas, supports points fully using a balance of evidence, and uses effective reasoning to make useful distinctions all relevant course and topic links are made evidence of some synthesis of course content to demonstrate understanding of topic some unified and coherent ideas are developed with effective transitions supports most ideas with effective examples, and/or references, and details, makes key distinctions most relevant course and topic links are made lack of evidence or weakness in the synthesis of course content to demonstrate understanding of topic develops and organizes ideas that are not necessarily connected. some ideas seem illogical and/or unrelated presents ideas in general terms; most ideas are inconsistent/unsupported, and reasoning is flawed or unclear some or no relevant course and topic links are made /20 assignment structure formatted as per assignment details structure and format enhance delivery of the information clear language is used which leads to easy readability correct grammar and spelling are consistently used formatted as per assignment details in most components structure and format fits well with the delivery of the information mostly clear language is used with minor readability issues few or no spelling and/or grammatical errors formatting has not been followed structure and format are unclear and impedes delivery of the information language used is often unclear which impedes readability many spelling and grammatical errors /5 total points /40 references click here to access a helpful citation generator. module 10 checklist please use the checklist, below, to track your completion of assignment requirements. please also note that it is possible that not all the items in the checklist will be applicable to your project. with that said, if you answer “no” in the completed for an item, then please add a brief explanatory note. activity completed if “no” please explain completion of tools & technology phase. yes/no completion of project timeline phase by deciding time frame for project development. yes/no completion of source code implementation phase. yes/no completion of project progress report phase. yes/no submission of power point presentation includes details of tools & technology, project timeline and source code implementation of your project. yes/no submission of project progress report [word file], having detailed information about phases from project requirement analysis to source code implementation. yes/no feedback taken from facilitator regarding all your submissions [presentation and report]. yes/no discussion between facilitator and developer regarding any updates suggested by the facilitator. yes/no submit the final presentation and final project report to the facilitator within the given deadline. yes/no facilitator approved the final submission-2 and allows you to start next phase of your development. yes/no module 11 checklist please use the checklist, below, to track your completion of assignment requirements. please also note that it is possible that not all the items in the checklist will be applicable to your project. with that said, if you answer “no” in the completed for an item, then please add a brief explanatory note. activity completed if “no” please explain review/refine or create the test plan. yes/no determine test tracking tools, defects tracking list, and prepare defect tracking log. yes/no create the test environment and setup automated test procedures, as appropriate. adapt test reporting procedures based on size, complexity, and specific project needs. develop test data management strategy. yes/no validate the system with functional and structural testing. yes/no review the results of the system verifications. yes/no implement “build” procedures, execute smoke tests, and fix any errors that prohibit the build from being tested. yes/no refine the data and load data into the test environment. yes/no develop test scripts based on requirements, design specifications, and code development. yes/no execute test scripts and create a test report. yes/no report results of test scripts and update test issues and defect tracking list. yes/no evaluate test reports to determine accomplishments and report status. update the test log. yes/no develop final test document summarizing all tests, results, defects found, etc. yes/no plan and conduct a test review. gather feedback and approval for the testing from facilitator. yes/no review the system/application support checklist and update support documents, as appropriate. yes/no store the data collected during testing in accordance with configuration management procedures. yes/no module 12 checklist please use the checklist, below, to track your completion of assignment requirements. please also note that it is possible that not all the items in the checklist will be applicable to your project. with that said, if you answer “no” in the completed for an item, then please add a brief explanatory note. activities completed if “no” please explain review/revise software integration process. yes/no define development strategy to build application. yes/no evaluate resources for the development phase. yes/no have environment preparation activities (e.g. correct os, memory etc.) been completed? yes/no have planned data creation/conversion activities been executed or are they on schedule to be completed as planned? yes/no are activities to enable the operation and maintenance of the product on schedule and ready for the planned completion? yes/no review code to ensure it meets specifications. yes/no is the code working properly as a workable application? yes/no add programming code and screenshots of each module of workable application in project report. yes/no prepare for and conduct final development approval. yes/no is project/website defect free? yes/no has the website design been viewed and approved by the facilitator? yes/no submit code and working application screenshots points="" assignment="" quality="" all="" information="" offered="" is="" accurate="" all="" views="" are="" clearly="" expressed="" and="" well="" explained="" contains="" original="" ideas,="" connections,="" or="" applications="" most="" information="" offered="" is="" accurate="" most="" views="" are="" clearly="" expressed="" and="" explained="" contains="" mainly="" original="" ideas,="" connections,="" or="" applications="" some="" or="" no="" accurate="" information="" offered="" views="" are="" rarely="" or="" never="" clear="" and="" require="" further="" explanation="" many="" non-="" original="" ideas,="" or="" unclear="" connections="" or="" applications="" 15="" assignment="" knowledge="" and="" skills="" demonstration="" clear,="" concise="" synthesis="" of="" course="" content="" to="" demonstrate="" understanding="" of="" topic="" all="" ideas="" are="" clearly="" developed,="" organized="" logically,="" and="" connected="" with="" effective="" transitions="" explores="" ideas,="" supports="" points="" fully="" using="" a="" balance="" of="" evidence,="" and="" uses="" effective="" reasoning="" to="" make="" useful="" distinctions="" all="" relevant="" course="" and="" topic="" links="" are="" made="" evidence="" of="" some="" synthesis="" of="" course="" content="" to="" demonstrate="" understanding="" of="" topic="" some="" unified="" and="" coherent="" ideas="" are="" developed="" with="" effective="" transitions="" supports="" most="" ideas="" with="" effective="" examples,="" and/or="" references,="" and="" details,="" makes="" key="" distinctions="" most="" relevant="" course="" and="" topic="" links="" are="" made="" lack="" of="" evidence="" or="" weakness="" in="" the="" synthesis="" of="" course="" content="" to="" demonstrate="" understanding="" of="" topic="" develops="" and="" organizes="" ideas="" that="" are="" not="" necessarily="" connected.="" some="" ideas="" seem="" illogical="" and/or="" unrelated="" presents="" ideas="" in="" general="" terms;="" most="" ideas="" are="" inconsistent/unsupported,="" and="" reasoning="" is="" flawed="" or="" unclear="" some="" or="" no="" relevant="" course="" and="" topic="" links="" are="" made="" 20="" assignment="" structure="" formatted="" as="" per="" assignment="" details="" structure="" and="" format="" enhance="" delivery="" of="" the="" information="" clear="" language="" is="" used="" which="" leads="" to="" easy="" readability="" correct="" grammar="" and="" spelling="" are="" consistently="" used="" formatted="" as="" per="" assignment="" details="" in="" most="" components="" structure="" and="" format="" fits="" well="" with="" the="" delivery="" of="" the="" information="" mostly="" clear="" language="" is="" used="" with="" minor="" readability="" issues="" few="" or="" no="" spelling="" and/or="" grammatical="" errors="" formatting="" has="" not="" been="" followed="" structure="" and="" format="" are="" unclear="" and="" impedes="" delivery="" of="" the="" information="" language="" used="" is="" often="" unclear="" which="" impedes="" readability="" many="" spelling="" and="" grammatical="" errors="" 5="" total="" points="" 40="" references="" click="" here="" to="" access="" a="" helpful="" citation="" generator.="" module="" 10="" checklist="" please="" use="" the="" checklist,="" below,="" to="" track="" your="" completion="" of="" assignment="" requirements.="" please="" also="" note="" that="" it="" is="" possible="" that="" not="" all="" the="" items="" in="" the="" checklist="" will="" be="" applicable="" to="" your="" project.="" with="" that="" said,="" if="" you="" answer="" “no”="" in="" the="" completed="" for="" an="" item,="" then="" please="" add="" a="" brief="" explanatory="" note.="" activity="" completed="" if="" “no”="" please="" explain="" completion="" of="" tools="" &="" technology="" phase.="" yes/no="" completion="" of="" project="" timeline="" phase="" by="" deciding="" time="" frame="" for="" project="" development.="" yes/no="" completion="" of="" source="" code="" implementation="" phase.="" yes/no="" completion="" of="" project="" progress="" report="" phase.="" yes/no="" submission="" of="" power="" point="" presentation="" includes="" details="" of="" tools="" &="" technology,="" project="" timeline="" and="" source="" code="" implementation="" of="" your="" project.="" yes/no="" submission="" of="" project="" progress="" report="" [word="" file],="" having="" detailed="" information="" about="" phases="" from="" project="" requirement="" analysis="" to="" source="" code="" implementation.="" yes/no="" feedback="" taken="" from="" facilitator="" regarding="" all="" your="" submissions="" [presentation="" and="" report].="" yes/no="" discussion="" between="" facilitator="" and="" developer="" regarding="" any="" updates="" suggested="" by="" the="" facilitator.="" yes/no="" submit="" the="" final="" presentation="" and="" final="" project="" report="" to="" the="" facilitator="" within="" the="" given="" deadline.="" yes/no="" facilitator="" approved="" the="" final="" submission-2="" and="" allows="" you="" to="" start="" next="" phase="" of="" your="" development.="" yes/no="" module="" 11="" checklist="" please="" use="" the="" checklist,="" below,="" to="" track="" your="" completion="" of="" assignment="" requirements.="" please="" also="" note="" that="" it="" is="" possible="" that="" not="" all="" the="" items="" in="" the="" checklist="" will="" be="" applicable="" to="" your="" project.="" with="" that="" said,="" if="" you="" answer="" “no”="" in="" the="" completed="" for="" an="" item,="" then="" please="" add="" a="" brief="" explanatory="" note.="" activity="" completed="" if="" “no”="" please="" explain="" review/refine="" or="" create="" the="" test="" plan.="" yes/no="" determine="" test="" tracking="" tools,="" defects="" tracking="" list,="" and="" prepare="" defect="" tracking="" log.="" yes/no="" create="" the="" test="" environment="" and="" setup="" automated="" test="" procedures,="" as="" appropriate.="" adapt="" test="" reporting="" procedures="" based="" on="" size,="" complexity,="" and="" specific="" project="" needs.="" develop="" test="" data="" management="" strategy.="" yes/no="" validate="" the="" system="" with="" functional="" and="" structural="" testing.="" yes/no="" review="" the="" results="" of="" the="" system="" verifications.="" yes/no="" implement="" “build”="" procedures,="" execute="" smoke="" tests,="" and="" fix="" any="" errors="" that="" prohibit="" the="" build="" from="" being="" tested.="" yes/no="" refine="" the="" data="" and="" load="" data="" into="" the="" test="" environment.="" yes/no="" develop="" test="" scripts="" based="" on="" requirements,="" design="" specifications,="" and="" code="" development.="" yes/no="" execute="" test="" scripts="" and="" create="" a="" test="" report.="" yes/no="" report="" results="" of="" test="" scripts="" and="" update="" test="" issues="" and="" defect="" tracking="" list.="" yes/no="" evaluate="" test="" reports="" to="" determine="" accomplishments="" and="" report="" status.="" update="" the="" test="" log.="" yes/no="" develop="" final="" test="" document="" summarizing="" all="" tests,="" results,="" defects="" found,="" etc.="" yes/no="" plan="" and="" conduct="" a="" test="" review.="" gather="" feedback="" and="" approval="" for="" the="" testing="" from="" facilitator.="" yes/no="" review="" the="" system/application="" support="" checklist="" and="" update="" support="" documents,="" as="" appropriate.="" yes/no="" store="" the="" data="" collected="" during="" testing="" in="" accordance="" with="" configuration="" management="" procedures.="" yes/no="" module="" 12="" checklist="" please="" use="" the="" checklist,="" below,="" to="" track="" your="" completion="" of="" assignment="" requirements.="" please="" also="" note="" that="" it="" is="" possible="" that="" not="" all="" the="" items="" in="" the="" checklist="" will="" be="" applicable="" to="" your="" project.="" with="" that="" said,="" if="" you="" answer="" “no”="" in="" the="" completed="" for="" an="" item,="" then="" please="" add="" a="" brief="" explanatory="" note.="" activities="" completed="" if="" “no”="" please="" explain="" review/revise="" software="" integration="" process.="" yes/no="" define="" development="" strategy="" to="" build="" application.="" yes/no="" evaluate="" resources="" for="" the="" development="" phase.="" yes/no="" have="" environment="" preparation="" activities="" (e.g.="" correct="" os,="" memory="" etc.)="" been="" completed?="" yes/no="" have="" planned="" data="" creation/conversion="" activities="" been="" executed="" or="" are="" they="" on="" schedule="" to="" be="" completed="" as="" planned?="" yes/no="" are="" activities="" to="" enable="" the="" operation="" and="" maintenance="" of="" the="" product="" on="" schedule="" and="" ready="" for="" the="" planned="" completion?="" yes/no="" review="" code="" to="" ensure="" it="" meets="" specifications.="" yes/no="" is="" the="" code="" working="" properly="" as="" a="" workable="" application?="" yes/no="" add="" programming="" code="" and="" screenshots="" of="" each="" module="" of="" workable="" application="" in="" project="" report.="" yes/no="" prepare="" for="" and="" conduct="" final="" development="" approval.="" yes/no="" is="" project/website="" defect="" free?="" yes/no="" has="" the="" website="" design="" been="" viewed="" and="" approved="" by="" the="" facilitator?="" yes/no="" submit="" code="" and="" working="" application="">