Download VPC Web Based Application-Computer Sciences-Project Report and more Study Guides, Projects, Research Applications of Computer Sciences in PDF only on Docsity!
i
Table of Contents
Table of Contents _________________________________________________ i List of Figures ____________________________________________________ii Abstract ________________________________________________________ iii Schedule _________________________________________________________ v
Chapter 1 Introduction _____________________________________ 1
1.1 Purpose_______________________________________________________ 1 1.2 Previous work done_____________________________________________ 1
Chapter 2 Amendments in UI and Database ____________________ 4
2.1 User Interface Amendments _____________________________________ 4 2.2 Database Amendments __________________________________________ 7
Chapter 3 UI Implementation ________________________________ 8
3.1 Users’ Authentication ___________________________________________ 8 3.2 Accounts Creation _____________________________________________ 11 3.3 Project Registration ___________________________________________ 12 3.4 Entrance of Evaluation Schedules ________________________________ 15 3.5 Uploading Artifacts____________________________________________ 16 3.6 Viewing (downloading) Artifacts _________________________________ 18
References_______________________________________________ 20
ii
- Figure 1.1 Database Diagram showing the complete Physical Database Design List of Figures
- Figure 2.1 Welcome Screen for all users
- Figure 2.2 Static Tree View vs. Dynamic Tree View (from left to right)
- Figure 2.3 New EVASCHED table (left) and previous Evaluation table (right)................
- Figure 3.1 Authentication page
- Figure 3.2 Authentication Workflow
- Figure 3.3 Creation of Faculty Account
- Figure 3.4 Accounts Creation Workflow
- Figure 3.5 Project Registration Page
- Figure 3.6 Project Registration Workflow
- Figure 3.7 Entrance of Evaluation Schedule Page
- Figure 3.8 Entrance of Evaluation Schedule Workflow
- Figure 3.9 Upload Artifact Page
- Figure 3.10 Upload Artifact Workflow
- Figure 3.11 Download Artifact page
- Figure 3.12 View Artifact Workflow................................................................................
iv
The goal is to provide the Faculty Members and Students with an easy to use system that automatically coordinates their projects and helps them interact in a more efficient and reliable manner. The work of managing Artifacts, Evaluation Schedules and Comments will become a whole lot headache free for both Students and Faculty Members, with the advent of Artifact management, Evaluation Schedules management and preservation of Comments History and generation of automatic notifications through email.
v
Schedule
The Project work was divided into several different phases and each task was scheduled to be completed in a certain specific time as specified in SMPM. The following Gantt chart depicts the whole schedule of the project execution.
The following tasks were completed before the start of summer vacations. Project Idea Exploration Software Requirements The following tasks were completed by the end of 7th semester. Proof of concept prototype Premature Architectural Design Logical Database Design Business Logic Design. Relational Model of VPC Database Physical database Design Physical Database Implementation
Tasks to be done in period of 7th^ semester final and 8th^ semester midterm are User interface design and implementation
relational schema was further Normalized. Normalization involves techniques of identifying and removing flaws in the Database Design, which result in redundancy and several insert, update and delete anomalies. Normalization was been done upto Boyce-Codd Normal Form.
1.2.3 Physical Database Design
A database is required to handle all the data manipulations involved with the VPC. The development of Database for VPC was divided into two parts; Logical Database Design [2]^ and Physical Database Design [3]. Following figure shows the complete Physical Database Design of VPC Database in the form of a Database diagram.
Figure 1.1 Database Diagram showing the complete Physical Database Design
Physical database design has been implemented in Microsoft SQL Server 2005 [4]^ in the previous stage. This was done with help of executing the SQL scripts for creation of Database and its tables. Physical implementation was ready to be used by a software application.
The mere purpose of this page is to make the system more informative for the users and help them in any possible way. Similarly, Modifications are to be made in welcome pages for each authenticated user which will serve as a notice board for the users.
Figure 2.1 Welcome Screen for All Users
2.1.2 Tree View Modification
Previously, in the prototype of the system, the tree view on the left hand side was static i.e. it was same for all the users. It contained links to all the pages present in system. A fundamental feature of the system is authentication, which makes sure only an authorized user views a specific page. This was implemented for the static tree view thus disallowing the unconcerned users to open specific pages. However, one flaw still remained and that was, although unauthorized users could not access all the pages; they were still able to see the links to those pages. Apart from being wrong from an ethical point of view, it is also a dangerous thing because it can be really thought provoking for a potential hacker.
After modification, the tree view is generated dynamically on the basis of role of the logged in user and contains links only related to that particular user. The following diagram further explains it. On the left, a static tree view is shown for a user with role as Student who, although cannot access all of the pages whose links are visible to him but can still see what functionalities other type of users can avail. On the right side is a dynamically generated tree view, generated at the time of a user login and it contains only those links in the tree view, which are related to currently logged in user (Student in this case).
Figure 2.2 Static Tree View vs. Dynamic Tree View (from left to right)
Chapter 3 UI Implementation
UI implementation involves the coding and programming behind the pages. This includes the programming of business logic in collaboration with the database with which the data transactions occur. A user interface which was not properly functional was developed in a previous stage (proof of concept prototype). It provided the basis for the development of UI implementation. According to the project schedule, the UI Design and Implementation is to be done in a period of 15 weeks and we have been able to implement a part of the UI, which includes the following. Users’ Authentication Users’ Accounts Creation Projects’ Registration Projects’ Modification Entrance of Evaluation Schedules Uploading Artifacts Uploading Comments Viewing (Downloading) Artifacts
3.1 Users’ Authentication
One of the key features for this system is authentication of users. Not everyone is allowed to access the system so authentication is implemented thus allowing only those who have got the rights. The users need to log in to the system by providing a valid User Name and Password. This ensures authentication. Among three major types of authentication techniques, Forms Authentication has been used. Forms Authentication is a system in which unauthenticated requests are redirected to a Web form where users are required to provide their credentials. Upon submitting the form, and being properly verified by the application, an authorization ticket is issued by the application. A web form for authentication has been developed. This Web form submits the user's credentials to business logic that determines their authorization level. Upon successful authentication, the application then submits a ticket in the form of a session variable and the user is authenticated [5]. As the authentication ticket is issued in the form of a session variable, session creation and management also needs to be done.
The Login Page for users’ authentication is shown below.
Figure 3.1 Authentication page
3.1.1 Pseudo Code
Following is the Pseudo Code for authentication of users.
- On page load event of every page, check if user has got the authentication ticket for the requested page.
- If authentication ticket is valid, send the page to the user.
- If authentication ticket is invalid, redirect user to login page.
- On Login Page, read user name and password from user.
- Validate user name and password against the records in the database.
3.2 Accounts Creation
Accounts creation is an important feature and is only available for the users with administrative rights. Administrator can create accounts by entering the user Details. The user details are entered into the database records. Moreover a unique username and password are generated for the user and saved into the same user record. Account creation is notified to the user via email. The following figure shows the account creation page for a faculty member.
Figure 3.3 Creation of Faculty Account
3.2.1 Pseudo Code
The Pseudo Code for User’s account creation is as follows.
- If user is logged in a administrator, read the user details
- Create a connection with database.
- Generate a unique User ID
- Generate a random Password
- Add entries in the database record
- Notify the concerned user via email.
3.2.2 Workflow
Following diagram shows the accounts creation workflow.
Figure 3.4 Accounts Creation Workflow
3.3 Project Registration
Project registration is done by the administrator by selecting the details of already existing users and entering the project related details. This is implemented by reading the student and faculty records from the database which gives the administrator the options to select the users and the related personnel i.e. selecting students and related faculty members for a certain project. These names are retrieved from the database. Then administrator enters the details relating the project such as project title, project description and project type.
3.3.2 Workflow
Following diagram shows the project registration workflow.
Figure 3.6 Project Registration Workflow
3.4 Entrance of Evaluation Schedules
Evaluation schedules are entered by administrator by entering date, time, location of evaluation of a certain project. This is implemented by selecting the project title from the projects list, location from the locations list, semester from semester list and entering date and time for the evaluation. Following diagram shows the implemented Evaluation Entrance page.
Figure 3.7 Entrance of Evaluation Schedule Page
3.4.1 Pseudo Code
The Pseudo Code for Entrance of Evaluation schedule is as follows.
- Fill project list by selecting values from project table.
- Fill location list.
- Fill semester list.
- Generate a unique Evaluation id.
- Insert these values in EVASCHED table.
