High School Website Design Project

The “The High School “website is a website developed using Three tier architecture having Data Access Layer termed as DAL,Bisuness Logic layer termed as  BLL,Presentation Layer termed as UI.BLL is also called as Business Access Layer and Presentation Layer is also known as User interface. The layer will be shown to the end user is called as Presentation Layer. Data Access layer contains the functions that will connect to the database to fetch the Data from the database to the website. Business Logic layer contains the logic behind the implementation. In addition to this website was developed is using all the available concepts of dot net coding and html such as Master Pages, User controls, Style sheets etc to present a better and neat web application to the students .Standard Stored procedures have been used to communicate will the Database both to insert data or to get data instead of writing the inline queries which is a bad practice. Menu item has been used in this website which will be redirecting each user to different pages as per the provided access

This website development have been split up into two modules known as

  • Administration Module
  • Student Module

Administration Module Design:

This module was mainly intended to insert or update the data into the school database related to student’s profiles, events, learning topics, quiz questions online exams etc.For this module to be accessed we have created a role in the “The High School” called as Administrator .The Administrator is the one who take cares of the complete website maintenance. We assumed that there will be only one Administrator for this website.

Following are the accessible points for the administrator.

Home: The administrator can view the Home page where in which he can understand what actually this site is meant for.

Profile: Create a new profile and insert it into the data base. For example inserting a student profile into the database such that he can access “The School website”

Events: This page is used to create or insert new event into the high school data base that will occur in future in the school which will be visible to the students from their login.

Quiz: This page is used to insert Quiz questions into the High School Database for each course such that the students can write online examinations and test themselves how far they were able to grab the concepts.

Logout: Used to logout of the application. 

 Student Module Design:

This module was developed for the students to use. This module facilitates the student to register himself into the “The High School” website, View his profile update his profile when felt necessary. He can also study the subject online; participate in some online examinations available in the Website to analyze his stuff. The students can also get their registration done with the help of administrator. Administrator from his login can create the students profile when requested.

Following are the accessible points for the Students.

Home: The student can view the Home page where in which he can understand what actually this site is meant for.

Profile: The students who have registered with the website can view their profiles in their own login. If he feels that his profile should be changed then he can do the same.

Events: This page is used to view the events that are happening or happened in their school when given the from data and to date for the events.

Learn: This page is used for eLearning of the students where they can study any topic that has been dumped into the site and enhance their knowledge.

Quiz: This page is used to write some online examinations for the students and submit to get their results, which will be used to test themselves.

Logout: Used to logout of the application.

In addition to this, we have implemented the Master pages such as menu.Master, Learning.Master, Title. Master etc.

Style sheets have been created and have been referenced in each and every  so as to follow same look and feel throughout the website. 

Each and every page implementation and results will be discussed in the coming chapter known as Implementation and Results.

School Website Project Modules

School website project is implemented in asp.net platform using C# programming language. This project consists of two modules administrator module and student module.

Administrator Module:

The Administrator is the owner of this website who maintains this website. He is user who uses this website for the registration of Students updating all the future events into the websites that should be accessible o the students. Administrator is also responsible for creating online quiz and also to dump the eLearning topics in to the “The High School” website. He is provided with a login user ID and Password with which he will be allowed to browse to through the website. Depending upon the role the website will be redirecting to the corresponding pages. Administrator is the whole and sole responsible person of this website and he is the only one who can insert any data into the database. 

 Student Module:

Second role available in our school website is Student. Student role is the end user role of this “The High School” website. The student can register himself into the “The High School” website. Once the registration have been done he will be provide with a user ID and password with which he can login in to the school website. Here the student can view his profile, update his profile, Learn new concepts, and participate in the existing online exams. Apart from all these he can get updated of the events both academic and curricular activities that have been going on in the school such that he can plan accordingly to participate in those events if interested.

The student is restricted to view his own profile and to update his own profile if felt necessary. View of other students profile is completely prohibited as it may lead to security issues and may disturb the main intention of this website. Insertion of data from student login in strictly prohibited other than creation of his profile i.e. registering himself into the school. He is provided access to all the learning courses as well do not want to restrict his leaning interest to one particular group to which he actually belongs. 

Customer Portal for a Mutual Fund Company Project Report

PMS is a mutual fund company with assets under management of over crores. It receives customer transactions and complaints through paper forms, it maintains information about all the schemes on database servers located in its highly secured data centers.

In order to perform various financial and non financial transactions without visiting the branch offices of PMS it is made web based, the financial transactions will be stored in database and are processed overnight in batch mode. The following are the requirements of the portal

Registration: while opening a mutual fund account PMS issues a  personal identification number PIN for the folio number mentioned in the application. A user can invest in mutual fund schemes of PMS and each will have a separate folio number

Mapping facilities: User can either update his or her portfolio or create a family portfolio

Own portfolio: System will automatically create own portfolio for the user using folio number and PIN entered during registration.

Family portfolio: A user can create a family portfolio, he or she can map several folio numbers. But each folio should contain a valid PIN number.

Download Customer Portal for a Mutual Fund Company Project Report.

Corporate Recruitment System

Corporate recruitment system is a web based tool that has come into existence to reduce the gap between job seeker and job provider. It makes the recruitment of required skilled employees easy and faster as especially in fast growing IT companies that grown on trend technologies the recruitment should be done fast. The existing recruitment procedure is time consuming so there is a need for efficient recruitment process such a process is our corporate recruitment system. The corporate recruitment system is designed using java web technologies like servlets, JSP, JDBC, JavaBeans, Java Scripts, HTML and windows XP server with a hard disk of Intel Pentium III , RAM of 128MB and a CD drive

This system is designed on a number of different modules

  1. Registration of job seekers and job providers: Both parties should register in the system .Separate forms are provided for both the job seekers and job providers.
  2. Advanced search option for  job providers: System provides a database to the job providers that contains all the data about suitable candidates
  3. Job provider’s module: Administrator maintains all site users.
  4. Listing jobs for job seekers: new jobs are updated by the job providers
  5. Sending mails to job seekers: When any of the job provider selects a job seekers profile that particular person will be intimated by the administrator.
  6. Conducts online tests: CRS also conducts online tests as designed by the organization that recruits the job seekers. Here the job provider provides a password to job seeker
  7. Generation of reports: CRS allows job providers to generate reports based on tests or on any of their requirements.

Through this corporate recruitment system process certain business requirements are also met they are

  1. Search capabilities
  2. User friendly
  3. Tracking management
  4. Value added service
  5. Security

In CRS structured analysis is also carried out that allows user to understand a newly designed system. It is a detailed step by step investigation of related procedures to see what must be done and to determine the best way.

Download Corporate Recruitment System  Report.

Constructing And Testing Of Polynomials Predicting Software Maintainability Abstract

Introduction to Constructing And Testing Of Polynomials Predicting Software Maintainability:

In non object oriented software system module modularization quality is calculated based on modules without using classes. Theoretical validation implies conformance to a set of agreed principles. Re-organization of millions of  lines of code residing in thousands of files in hundred of directories into modules , where each module is formed by grouping a set of entities such as files , data structures, functions and variables.

In this project we set design principles for code modularization and produce set of metrics that characterize software in relation to those principles. Some metrics are structural, architectural and notions. The structural metrics refer to inter module coupling based notions. The architectural metrics refer to horizontal layering of modules in large software systems.

This project makes use of three types of contributions cohesion, coupling and complexity of metrics to modularize the software. Modularization algorithm is based on the combination of coupling and cohesion metrics .Finally two types of experiments are made to validate the metrics using open source software system they are                                                                       

 1. Apply metrics to two different versions of the same software system

 2. Experimental validation consists of randomizing a well-modularized body of software and seeing how the value of the metrics changed. Our project thus provides metrics that seek to characterize a body of software according to the enunciated principles. 

Download Constructing And Testing Of Polynomials Predicting Software Maintainability Abstract.

Container Terminal Management System CTMS Project Report

Introduction to Container Terminal Management System CTMS Project:

The aim of the project is to develop a Container Terminal Management System for a larger container port terminal having one of the biggest container handling facilities in the country. The terminal occupies a strategic partnership with major shipping lines to provide customers in the country and the regions with links to more than 100 ports around the world.

CTMS has two major modules they are

1. Containers module.

2. In-Yard operations module.

Containers module: The containers modules handles the following areas they are

Export Containers: The voyage call has been registered container port through system with reference by shipping agent. The shipping agent will assign the hauler to handle the container to port. The customs clearance will be handled forwarding agent appointed by shipping agent. After clearance the container enters into hauler and is then accepted by port terminal and is stacked in yard location. On arrival of vessel the container will be loaded in the vessel and necessary bill will be generated by the system.

Import Containers: The voyage call has been registered by the container terminal through the system with reference to shipping agent. On the arrival of vessel containers are discharged from vessel and stack is allocated in yard location.

Empty containers: Empty containers are same as import and export containers

Reefer container handling: Refrigerators are stored in the yard as it requires necessary cooling before loading the ship or delivery to the customer.

In-yard operation module: The following activities take place in this module they are

  1. Packing or unpacking
  2. In-yard movement
  3. Yard planning

Packing or unpacking: The forwarding agent may request the port terminal to pack their cargo into the container empty container which is stacked in the yard. The port terminal will pack all the cargo into specified container and convert this into export.

In-yard movement: All the containers inside the yard are handled by private carriers. The necessary data to move the container by the carrier are communicated through wireless system called RDT. The CTMS application will communicate with RDT system to receive and send data based the VMT/HMT requests.

Yard planning: The location for stack import or export containers is planned prior to container arrival. In turn the yard planning is controlled by CTMS.

 Download Container Terminal Management System CTMS Project Report.

Complaint Management System DFD Diagram

The Complaint Management system has following modules they are as follows

1. Login and session management.

2. Registration module.

3. Operation module.

4. User activity module.

5. Search module.

6. Report generation module.

7. Database administration module.

8. Feedback module.

9. Discussion forum module.

10. Help module. 

When a user Logon to CRMS website he can see a home page. The homepage collects information about name and details of user from him .User writes complaint about the difficulties faced by him. On entering the complaint a complaint ID is generated by which he can access the status of complaint made by him. User can also go through a list of pages to get the required information that he needed to register the complaint successfully.

dfd diagram for complaint management system:

customer management system dfd diagram

 Download Complaint Management System DFD Diagram and project report.

Complaint Management System Asp.Net Project Report

Introduction to Complaint Management System:

The Indian railways are the fourth largest rail network in the world and the largest civilian organization under a single management. It is crossing the vast geographical area of our country .It’s covering almost one lakh kilometers with a work force of 1.65 million across the country.

In most of the cases the railways are the cheapest means of transportation in the developing country like India approximately 12000 trains run all over the India daily. 

The complaint registration management is web enabled, centralized information and management application to build good relations among the railway department and   its customer community by providing faster mechanism to track the deficiencies and customer grievances .

The CRM is an implementation towards easy registration of complaints for railways. It is designed using ASP.NET as front end and MYSQL as backend.

Any user can access the CRM website by logging into it. The user can simply enter the station name or code and click on submit for logging on .It also invites topics for discussion through web forum irrespective of the language as it has a multi language support .So people from any part of India can participate in the discussion forums, they also have a freedom of making suggestions to the management .CRM is mainly designed for the railway customer satisfaction. 

 Download Complaint Management System Asp.Net Project Report.

Credit Card Fraud Detection Using Hidden Markov Model Project Report

Introduction to Credit Card Fraud Detection Using Hidden Markov Model Project:

Credit card based purchases are of two types they are

  1. Physical card
  2. Virtual card

Physical card based purchase: The card holder contains a card and in order to purchase a good or make any transaction the card holder should carry the card. 

Virtual card based purchase: Here the card holder need not carry the card, just a few details about the card are enough to carry out the transactions. It is generally done in online shopping.

In physical card based purchase the fraudulent transactions can be done only if the attacker was able to steal the card from cardholder and if the cardholder doesn’t notice the loss of credit card it may lead to financial loss.

At present the fraud is detected after the fraud is done that when the card holder complaints. The online purchases are more so we don’t know how the person is using the card online we just capture IP address for verification. So there an urgent need to investigate about the fraud. Fraud detection based on analysis of existing purchase data of cardholder is a promising way to reduce the rate of successful credit card frauds. As humans tend to exhibit various behavioral profiles, each cardholder can be represented by a set of patterns containing information about typical purchase category, the time since last purchase, amount paid etc. This process is known as HMM Hidden Markov Model. The details of items purchased are not known at FDS running at the bank that issues credit cards to cardholders.

The modules present in this project are as follows

  1. New card: The customer provides their contact and personal information to obtain a credit card. They can create their own login and password.
  2. Login:  With the valid usernames and passwords the users can visit the website
  3. Security information: When the user looses the card security information module arises. In order to move to the transaction section he has to answer a set of questions.
  4. Transaction: The credit card owner or authorized person can only make the transactions
  5. Verification: In this process the card number is verified to ensure that the  transaction is made by card holder itself.

 Download Credit Card Fraud Detection Using Hidden Markov Model Project Report.

Asp.Net Projects For MCA on Text File Hiding In Audio Files Using Low Bit Encoding Steganography

Main aim of this project is to provide security for data using steganography technology where data is encrypted and transmitted in audio file. In this method it is hard to decrypt data without using decryption algorithm. Algorithms used in this application are secure and provide high security. 

Here we provide class diagram which will be useful for implementing this application. Students can download project report and source code on same topic from this site.

class diagram text file hiding