Please find attached the assignment instructions as well as examples. Please note: Do NOT copy the...

Question

Please find attached the assignment instructions as well as examples.			Please note: Do NOT copy the examples provided.			List of project ideas:		https://nevonprojects.com/project-ideas/software-project-ideas/				Assignment 1 CST8333 – ASSIGNMENT 1 – INSTRUCTIONS CST8333 – ASSIGNMENT 1 – INSTRUCTIONS CST8333 Assignment 1 Project Initiation: 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 1 – INSTRUCTIONS CST8333 PROGRAMMING LANGUAGE RESEARCH PROJECT – ASSIGNMENT 1 2 Table of Contents 1	Instructions	2 1.1	Introduction	2 1.1.1	Objective	2 1.1.2	Pre-assignment Instructions	2 1.1.3	Submission Guidelines	2 1.2	Report	3 1.3	Presentation	4 2	Assignment 1 Grading Rubric	6 3	References	8 4	Module 2 Checklist	9 5	Module 3 Checklist	12 6	Module 4 Checklist	13 7	Frequently Asked “What the . . .?!” Questions	15 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 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 first phase of a programming research project. Pre-assignment Instructions Through the first weeks of the course you used the detailed checklists included in course modules #2 through #4 to track your completion of the requirements of Assignment 1.  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 1 there are two documents that must be submitted and in which the requirements must be captured, as follows. 1. Report 2. Presentation  Please Note Please do not include any source code in your Assignment 1 documentation. Source code is required only for Assignment 2 (60%) and Assignment 3 (100%) Please find in the sections below the checklists for each of the two Assignment 1 documents. Use the checklists to validate that you have completed the requirements of the assignment. Submission Guidelines 1. Submit your work in the formats prescribed in section 1.2 Report and 1.3 Presentation of this document. 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 1 Report A “Word” document that includes but is not limited to the following high-level sections, requirements, feasibility, and design.  Please Note For reference purposes an outline of the Assignment 1 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 5) 	Activity 	Completed 	If “No” Please Explain 	Completion of Requirement Analysis phase. 	Yes/No 	 	Completion of project related Feasibility Study. 	Yes/No 	 	Completion of Project Design along with your Project Title and definition. 	Yes/No 	 	Submission of Power Point Presentation includes Requirement Analysis, Feasibility Study and Project Design phases of your project. 	Yes/No 	 	Submission of Partially done Project Report [word file], having detailed information about the first three modules of your project. 	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-1 and allow you to start next phase of your development. 	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 1 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 1 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 	 Assignment 1 Grading Rubric Please find, below, the criteria against which Assignment 1 will be graded. 	Criteria 	Excellent 80-100% 	Good 50-79% 	Requires Improvement

Shubham · Accepted Answer

CST8333 Programming Language Research Project – Assignment 1
CST8333
Assignment 1
Three-level password authentication system
Student’s Name
Date
Algonquin College
Table of Contents
Introduction	2
Objectives	2
Scope	2
Timeline	3
Risks	3
Assumptions	4
Technical Constraints	4
Budget	5
Requirements	5
Introduction	5
List of Requirements	6
Use Case Diagram	7
Traceability Matrix	10
Feasibility	11
Introduction	11
Alternative Solutions	11
Recommendation	12
Conclusion	13
Design	13
Introduction	13
System Architecture	14
Package Diagram	14
Class Diagram	15
Entity-Relationship Diagram	16
UI Prototype Models	17
References	18
Checklists	19
Module 2	19
Module 3	21
Module 4	22
Introduction
Three-level password authentication system is a system that uses three different levels of authentication to verify a user's identity. The three levels typically include something the user knows like the user's password, something the user has (such as a security token or a fingerprint, and something the user have biometric features like a face or voice. This type of system is often considered more secure than systems that use only one or two levels of authentication, as it makes it more difficult for an attacker to gain unauthorized access.
Objectives
The objective of a three-level password authentication system is to provide a higher level of security for the system or service that it is protecting. This requires multiple forms of authentication, such as something the user knows and something the user has, and something the user is, the system makes it more difficult for an unauthorized person to gain access. It can help in reducing the risk of identity theft, financial fraud, and other types of cybercrime (Singh & Singh, 2019). The three-level password authentication system may also be used to comply with industry regulations or to meet the security requirements of a particular organization.
Scope
	The scope includes use of a three-level password authentication system in computer and network that can be used to secure access to computers, servers, and other networked devices. This can include protecting access to individual workstations, as well as to sensitive areas of the network such as the corporate intranet or the data center. This system can also be used to secure access to online services, such as email, cloud storage, and social media (Joseph et al. 2021). The system can be implemented for controlling access to physical locations, such as buildings, rooms, and other secure areas. It provides a high level of security for any system or service that requires authentication and access control.
Timeline
Risks
	The risk with a three-level password authentication system is weak password and it can make it easier for an attacker to gain unauthorized access, even with the added security of the other two levels of authentication. The next risk is that phishing attacks can be used to trick users into giving away their password or security token, which can then be used to gain unauthorized access to the system (Minh & Nguyen, 2019). Another risk is biometric data breach in which biometric data used in the system is compromised; it can be used by an attacker to gain unauthorized access to the system.
Assumptions
	It is assumed that a three-level password authentication system can help in increasing security by multiple forms of authentication, such as something the user knows, something the user has, and something the user is, the system makes it more difficult for an unauthorized person to gain access. It can help in reducing the risk of identity theft, financial fraud, and other types of cybercrime. Users can authenticate themselves in a variety of ways, such as by using a password, a security token, or a biometric feature, which can make the authentication process more convenient and user-friendly.
Technical Constraints
	Technical constraints include complexity, hardware and software compatibility, scalability, user acceptance and privacy concerns. The implementation of a three-level password authentication system can be complex and may require specialized knowledge and expertise. In the process, if the hardware and software used in the system are not compatible with each other, it can cause errors or system failure (Kumacheva & Orlov, 2022). The number of users or the size of the system increases, it can become more difficult to manage and maintain the system. It may happen that users do not understand the importance of the three-level authentication system.
Budget
Requirements
Introduction
	Three-level password authentication system is the type of authentication system that can help in validating users for accessing the system and it can be done with the use of correct input. The three level of authentication includes varieties of password systems. It contains three login from three different password systems.  The difficulty of authentication increases with each level and the user can provide input with the correct password fro successful login. It can help in creating technology that emphasizes on creating a simple user interface for providing best possible comfort in solving the level of authentication. 
List of Requirements
The list of requirements that is required for implementing three-level password authentication system includes:
Secure storage: It includes use of a system that can be used for storing the authentication data. It includes ensuring that the data is encrypted and it can be protected from unauthorized access. 
Authentication method: It includes the use of a system that can be used for supporting multiple forms of authentication. It includes use of password, security token and biometric data.
User Management: The system can be used for user management and it includes components like deletion, creation and management of user accounts (Yang et al. 2022). 
Access Control: In this the system should have the access for components that allows it to restrict the access to specific resources that are based on permission and roles.
Auditing and reporting: In this the system can have the capability to log and record user activity and it can provide with the ability for generating reports on access attempts and user activity.
Secure communication: The system required regular update and maintenance for ensuring it is effective and secure to use. 
Use Case Diagram
Use Case Scenarios
Use Case Scenario 1
Title: Identification 
Primary Actor: User
Brief Description: User provide username 
Trigger: Identifies in the system
Relationships: Association – User, Database
Pre-Conditions: User has to provide username 
Post-Conditions: The information provided has been identified by the system
Main Flow:
The user provides with user ID
The system verifies with the database
Use Case Scenario 2
Title: Authentication factor 1
Primary Actor: Database
Brief Description: Check password
Trigger: Authenticate with database
Relationships: Association – User,

Assignment 1CST8333 – ASSIGNMENT 1 – INSTRUCTIONSCST8333 – ASSIGNMENT 1 – INSTRUCTIONSCST8333Assignment 1Project Initiation: Report & PresentationINSTRUCTIONSAll material prepared for...

Answer To: Assignment 1CST8333 – ASSIGNMENT 1 – INSTRUCTIONSCST8333 – ASSIGNMENT 1 –...

Answer To This Question Is Available To Download

Related Questions & Answers

Submit New Assignment