All the requirements from Part 1 must still be met by the program, with the following changes and additions
Operations
In mathematics and computer science, an operation is an event that is carried out to satisfy a given task. Basic operations of a computer system are input, processing, output, storage, and control.
Basic Operators
An operator is a symbol that indicates an operation to be performed. We are familiar with operators in mathematics; operators used in computer programming are—in many ways—similar to mathematical operators.
Division Operator
We all learnt about division—and the division operator—in school. You probably know of both these symbols as representing division:
Modulus Operator
Modulus can be represented either as (mod or modulo) in computing operation. Modulus comes under arithmetic operations. Any number or variable which produces absolute value is modulus functionality. Magnitude of any function is totally changed by modulo operator as it changes even negative value to positive.
Operators
In the realm of programming, operators refer to the symbols that perform some function. They are tasked with instructing the compiler on the type of action that needs to be performed on the values passed as operands. Operators can be used in mathematical formulas and equations. In programming languages like Python, C, and Java, a variety of operators are defined.
Software development C#
The application developed in Part 1 is already useful in terms of functionality, but it has a severe usability flaw: the data is not persisted, forcing the user to capture all the data from scratch if the application is executed again.
For this part, you will continue working on the application you developed in Part 1. Remember to implement any feedback provided by your lecturer on Part 1 before working on Part 2. Marks will be awarded for this (see the rubric for details).
All the requirements from Part 1 must still be met by the program, with the following changes and additions:
1. The software shall persist the data in a SQL
2. The user shall be able to register with a username and password.
3. The software shall store only the hash of the password in the database.
4. The user shall be able to log into the software with their username and password.
5. The user shall only be able to see their own data and never that of other users.
Non‐functional requirements:
1. The application should use the custom class library developed in Part 1. You may update
the class library as necessary for the new functionality.
2. You can choose to access the database using the ADO.NET connected layer or Entity
Framework Core.
3. Regardless of database access technology, the application should use multi‐threading to
ensure that the user interface never becomes unresponsive while retrieving or storing information.
Step by step
Solved in 4 steps with 2 images
