Placement Information System VB.Net Project

ABSTRACT:

The project entitled “PLACEMENT INFORMATION SYSTEMis developed with vb.net as front end and MS-Acces as back end. This system is developed to assist the placement and training cell of Karpagam Arts and Science College. The main purpose of this project is to store the students details and to find all the eligible candidate from UG and PG, satisfying the specified criteria.

This is a user friendly project that enables all kind of users to work with, even     without any prior knowledge of computer.

ABOUT THE PROJECT

The Placement Information System is a software project developed to assist the placement and training cell of Arts and Science College. The login form in the system checks for the validity of the user name and password. This ensures that only the authorized users are allowed to use the system.

The main modules in this project are student, check and report.

The module ‘student’ consists of two sections, UG and PG. All the academic and personal details of the students are maintained separately in this module. Provision for inserting, updating and deleting the records are made here.

The next is the checking module. Checking is done separately for UG and PG students.   In the checking module, the eligible candidates who can appear for the placement are found. This selection procedure is based on certain criteria, given by the company, like percentage of mark, the course being done by the student and the arrears.

The report module, which is the output module, produces the list of eligible students who can appear for the placement, along with all the necessary details.

ugtable

FIELD NAME DATA TYPE DESCRIPTION
rollno memo Rollnumber
name text Name of the student
gender text Gender
dept text Department
year number Year of study
batch text Batch
homename text Homename
place text Place
city text City
state text State
pin number Pincode
phno number Phone number
tenth number Tenth percentage mark
twelth number Tweth percentage mark
currentsem number Current semester
arrears text Arrears present or not
noarrears number No of Arrears
mark number Mark up to current semester
placed text Placed or not

Placement Information System Login Placement Information System Modules Placement Information System Student details

System Resource Controller VB.Net Project

Prologue

Every system has resources which are very essential to have the designated task performed by the system as intended. Some of these resources are exposed to the outside world and some are not. Of all these only few can be controlled and others are not. This is to protect the system integrity and functionality from the novice and probing hands.

But   in times of technological and information age, there is lot of information   to be shared without having any troubles. The sharing may be with in local intranet or remote internet. In these cases we need look for some issues which place crucial role in the system performance also.

Details

In the above scenario, we may require to monitor and control the resources in a system for protecting as well as enhancing the performance of that system. But  the monitoring and controlling activities if done at local system level, the time and the effort needed are going to be unimaginably huge. In addition, the controlling/monitoring authority is not going to have a clear view of  ‘ what is what’ about the systems.

The solution for this kind of issues is having the controlling and monitoring power at one end. From this terminal or system the other systems/ computers in the local intranet or remote internet can be controlled or monitored as the administrator/ controlling authority wishes to do.

System Resource Controller Home Page

Requirements:

This proposed System Resource Controller solution requires a keen and carefully planned vision. As we are controlling the resources from a remote end, the network resource overloading is going to be a burden. Without causing much traffic the controlling has to be done.

We are proposed to use some nifty components from the Windows Operating System for the effective controlling of the system resources in the network.

At top level the issues that are going to be controlled monitored are…..

  • System Physical Resources
  • Software Resources of a System
  • The Network Resources
  • Finally, Analytical Results of Scrutinization

PRELIMINARY PLANNING / INVESTIGATION

To protect the system integrity and functionality from the novice and probing hands. In times of technological and information age, there is lot of information  to be shared without having any troubles. The sharing may be with in local intranet or remote internet. In these cases we need look for some issues which place crucial role in the system performance also.

The goals of  SRC is protect system integrity and functionality, and to maintain performance

Objectives:

To achieve the above goal we need to achieve the following sub-goals or objectives…

We need some nifty components from the Windows Operating System for the effective controlling of the system resources in the network.

At top level the issues that are going to be controlled monitored are…..

  • System Physical Resources
  • Software Resources of a System
  • The Network Resources
  • Finally, Analytical Results of Scrutinization.

System Resource Controller Find Domains

Module Description:

The System Resource Controller project is designed keeping in view of a Network Administrator’s requirements while administering the LAN.  As per the analysis results, the identified tasks should be achieved under single application in a much collaborative way providing complete required information at the finger tips of the Administrator.

During the module design phase, the first two modules concentrate on user interface design for all tasks and privilege verification and authentications. The remaining modules focuses on the different tasks both designing and techniques.

To recall, the identified tasks from the analysis are …

  1. Gets the list of different domains / sub domains
  2. Gets the list of different system under domains / sub domains
  3. Gets the list of system switched ON
  4. Gets the list of logins (login enumeration)
  5. Gets the list of processes running on each system
  6. Gets list of each system startup time (?)
  7. Get the information about the memory usage of each system
  8. Get the CPU usage / load of an individual system
  9. Get the hardware details of an individual system
  10. Get the software details of an individual system
  11. Broadcasts messages to all systems
  12. Sends messages to all systems under specific domain / sub domain
  13. Sends messages to an individual system
  14. Kills a process in a system
  15. Shuts down, Reboot or logs off a system

Module 1: Interface Design

One of the intrigued things while designing the System Resource Controller project is the interface design. It is some kind of one stop solution for the network administrator to perform most of the general and routine tasks.

System Resource Controller

The SRC has three layers of design …

  • Forms, where carefully placed controls are used to achieve different SRC tasks.
  • MDI form, which links all other forms together at one place for easy access.
  • Dialogs, which help the user / administrator in notifying some key events.

Sample forms are provided in the appendix

Module 2: Privileges & Authentication

In this module, we provide security for monitoring as well as controlling the resources of system under network. Security here is implemented in two stages. Stage one is from the existing Windows Network security policy, and stage two is from the SRC itself.

The Windows Network Security policy will take care of the privileges of different groups identified by the domains. This directly controls the accessibility of the systems under different domains of the same network. These policies can be set by the administrator only once according the organization needs.

The security adopted by the SRC on its own has another authentication system exclusively to access the SRC application itself. Administrator decides the users of the SRC application, along with different levels of access and utilization privileges.

We utilize the System.Web.Security namespace partially here to provide certain level of security.

System Resource Controller Graphical Representation

Module 3: Enumerating Domains & System

One of the preliminary tasks in SRC is to know how many systems are present in the given network. This can be achieved by proper usage of system related API calls in addition to exploiting the.NET network namespaces. Herein this module we are going to enumerate the list of domains present in the network and the systems connected under each domain.

For the purpose of enumerating we are taking the help of system.management namespace, which imbibes the WMI concept. We are concentrating on the following techniques to achieve our targets.

Module 4: Enumerating Users

Similar to the above task, the ‘Enumerating Users’ module also does the similar job. But here we are concentrating on the list of users rather than the systems and domains. This module enumerates the list of users from the Windows Network Authentication. It also gets the details of users and to which groups they belong.

For the purpose of enumerating we are taking the help of system.management namespace, which imbibes the WMI concept. We are concentrating on the following techniques to achieve our targets.

Module 5: Finding the Running Systems & Running Time

This module is little tricky. This module performs two different sub tasks.

  • Finding the working systems: This doesn’t mean that all the systems that are switched on. It goes a step ahead and finds out of all the systems that are on, which system is currently working (using system resources to perform some processes)
  • Finding the running time: This again is very difficult to find out how much time that each system is working. We are following a way round approach to find this. Our System Resource Controller is going to watch all the systems under network in the background. It notes down the time when the system boots up and shuts down, and calculates the difference to find out the approximately running time.

Module 6: Hardware Details

This module completely depends on WMI concepts to find out the hardware details. The GetObject method of the WMI namespace will be used here. Using this technique we can found the key hardware resource details.

These are the details we are trying to find out using the WMI.

  • Motherboard
  • Memory
  • Hard disc & Logical Discs
  • Network card
  • BIOS
  • Monitor
  • Display
  • Removable Drives
  • Processor

Module 7: Software Details

As in the above module, this module also totally relies on WMI.  Similar techniques will be used here to find out the details of software resources. But this doesn’t give accurate results as expected. WMI exposes only the resources that are active. Due to this reason, we can’t list out the software that is not actively running.

In any case, we can find out the OS details, and other software which were running services on OS. The other software information installed on that system can be retrieved as and when that software is running. Another glitch here is not all software products support information exchange through WMI object.

We may use Win32_InstalledSoftwareElement.Software namespace to optimize our search for installed software components.

Module 8: Enumerating Running Processes & Controlling

In this module, we are going to bring out three different things as and when they are running. This doesn’t mean that SRC is going to watch these issues for every second. This certainly adds up the already running processes and becomes extra load on CPU diminishing its performance.

  • Processes
  • Threads
  • Handles

WMI object doesn’t give differentiated list of processes, threads and handles, instead it gives all in a pool. We should programmatically regroup all these. We may even go to the extent of finding the length of each process, or thread in terms of time. The CPU utilization for all these processes will be done in a separate module which will be detailed in

Module 10

We are going to look at these issues, either at pre-defined intervals of time, and results will be logged for future reference or at the administrator click of a mouse button on the corresponding control. Of these the first option is not implemented in the current version, and is planned for the next release.

Module 9: Memory Utilization

This and the next modules are extension of the previous module. These modules use the same objects of WMI along with additional CIMV2 classes and namespaces to find out the memory and its utilization.

Generally, we will display the selected systems memory details under the following heads.

  • Page File
    • Total Size
    • In Use
    • In Use (Max)
    • Free
  • Physical Memory
    • Total
    • Available
  • Virtual Memory
    • Total Size
    • In Use
    • In Use (Max)
    • Free
  • Totals
    • Processes
    • Threads
    • Handles

This detailed structure of memory utilization will help the network administrator to find out the optimum utilization of memory. He can also control the memory leaks when some unnecessary processes, handles or threads are consuming extra chunks of memory by killing those. These killing processes, handles and threads will be dealt in same module but under another sub module.

Module 10: CPU Utilization

To find out the CPU utilization, we don’t require any separate WMI object. As said earlier, we can use the Module 8’s objects with little tweaking. We are going to exploit the CIMV2 sub classing options here.

In general, CPU will be used only to do one or the other kind of processing. All these processes can be listed out using the Module 8’s functionality. If we finds out each process, thread or handle’s CPU utilization along with its memory utilization, we can have total and averages of CPU utilization at any given point of time.

Module 11: Broadcasting & Sending Messages

These are the simplest tasks of the SRC project. There is nothing we need to do great programming to perform broadcasting and sending messages to groups of systems or even individual systems.

We can simply use the system calls (nothing but system network related API calls).

Module 12: Log Off, Reboot, & Shutdown

Module 13: Saving the Results

Module 14: Graph Display (*)

Module 15: Reports (*)

Conclusion

The project undertaken is useful for Controlling of System resources.

Useful for maintaining system integrity, functionality and  to increase performance of the system.

By the Use of VB.net process for execution makes it easier to work with and also it a very user interactive.

Bank Salary System VB & MS Access Project

The Bank Salary System is useful for the employee‟s of the branch and reduce the manual calculation and saves lot of time and will give precise answers for all the fields of earnings. The reports of pay slip, register and loans are also complete and accurate.

Front – end : Microsoft Visual Basic 6.0
Back – end : Microsoft Access 2000
Project duration : 200 hours approximately

Bank Salary System

ABOUT EXISTING SYSTEM
In the existing Bank Salary System the salary of the employee of the SBI branch is calculated manually. The staff of the branch is divided in three categories.
1.) Officers (Management).
2.) Award Staff (Clerical).
3.) Subordinate Staff.

The above-described categories are further divided in the following Designations.

1.) Officers (Management): –

i.) JMG (Joint Manager)
ii.) MM – II (Main Manager – II)
iii.) MM – III (Main Manager – III)
iv.) SMG – IV (Subordinate Manager –IV)
v.) SMG – V (Subordinate Manager – V)
2.) Award Staff (Clerical): –

i.) Clerk
ii.) Sr. Assistant
iii.) Special Assistant
 3.) Subordinate Staff :-

i.) Messenger
ii.) Watch Man
iii.) Record Keeper
In the existing Bank Salary System the calculation of the salary is done on the bases of Basic Pay of an employee according to categories of the employee.
The salary of an employee is mainly based on the Earnings and the Deduction. There are number of fields in the earnings and the deduction from the salary of an employee. The calculation of each and every field is mainly based on the Basic Pay of an employee. And some of the fields of earnings and deduction are maintained with fix amount according to the status, seniority, and post or according to the designation of an employee.

Bank Salary System Module
The Basic Pay of an employee is fixed according to the designation and seniority of an employee working in the bank. And calculations of other fields are done on some fix percentage of Basic Pay of an employee according to the Memoranda of Settlements.
In the existing system the calculation of the fields of the earnings and deduction is calculated manually. So while calculating the amount of each and every field manually the chances of errors and calculation of wrong values are always possible.
In the existing system the salary of an employee is done manually and the person who is doing the salary of the branch fills the amount of each and every field of earnings and deduction. The fields whose amount are fixed are directly written at proper place and the fields whose value is depend on the fix percentage of Basic Pay is calculate and then are written in the Pay Slip. So the person who is doing the salary of the branch has to first of all fill all the information of an employee like employee number, employee name, designation of an employee, grade of an employee, department, date of salary etc. and then has to calculate the value of each and every field and then total the all fields of Earnings and Deduction and by deducting the total of deduction from the total of earnings the net pay is calculated. Now while doing the salary of an employee the person also has to maintain the Register in which all the information of the salary of an employee is noted. Register is maintained for the purpose of keeping the record of each employee for calculation of Income Tax and for the calculation of Provident Fund etc.
As mentioned above the salary of all employee of the branch are calculated with large calculations, manpower and handling of the large documents with chance of having lots of errors and time consumption.

PROBLEM IDENTIFICATION

Drawbacks of existing system.

1.) Register Maintenance.
2.) Time Consumption.
3.) Pay Slip Preparation.
4.) Problem In Calculating Income Tax.
5.) Problem In Calculating the amount of Loans.
6.) Calculating the field amount.

1.) Register Maintenance: –

At the time of calculating the salary of the branch the register is also maintained and a person who is doing the salary has to copy all the amounts of fields in the pay slip from the register.
A register is maintained for whole year and the salary of each employee is noted in the register. So if an employee wants to know his salary of previous month he/she has to refer the whole register and find his/her employee number from the register, the particular month he/she wants etc. and then he/she will be able to get the salary record. Now if he/she wants the copy of the salary slip he/she has to manually write the whole pay slip. Now there is also problem of storage of all the registers, because there are so many factors by which the registers can be destroyed like fire, water, stolen, etc.

2.) Time Consumption: –

The process of calculating the amount of each field whose value is depend on the basis of percentage of basic pay is very much time consuming and it is having lots of calculations.
If an employee wants more than one copy of the pay slip then also it will take lots of time for preparing another copies of the pay slip. The process of calculating the salary of an employee is very much time consuming and boring for a person who is doing the salary of the whole branch.

3.) Pay Slip Preparation: –

As mentioned above the process of register maintenance, and then the pay slip is prepared from the register is very much time consuming and the chances of errors and mistakes is always present.

4.) Problem In Calculating Income Tax: –

The employer is required to deduct income tax from the salary paid to an employee. The income tax is calculated based on gross salary paid to the employee during a year, if it exceeds a limit. Because of the manual system the calculation the income tax amount become very difficult and time consuming.

5.) Problem in calculating the amount of Loans: –

The handling of the loan amount and the calculation of loan amount is very difficult and time consuming in the existing bank salary system. The problems with the handling of loan amount is that sometimes the amount is wrongly written by the person who is doing the salary, the employee has to pay more amount from his/her salary.

6.) Calculating the field amount: –

The calculation of the field amount of the earnings and deduction is very hard and time consuming when the field amount is based on the basis of the fix percentage of the Basic Pay of the employee. The chances of errors and mistake are very much in the existing bank salary system.The above described are the drawbacks of the manual bank salary system with makes the process difficult, time consuming and very hard for the person who is doing the salary of the branch and is also not beneficial to the employees of the branch

Multi Chain Market Monitoring in VB

PROJECT SPECIFICATION:

Multi Chain Market Monitoring deals with the processing of accessories rates and product maintenance with the three data files to store data permanently. The user should maintain two databases about the customer and products. The customer database consist of customer code, customer name, address, city are the fields. In product database product code, product name, quantity in hand, price of item are the fields. It has a capability to display all the details in a tabular format.

VALIDATIONS:

–    Customer number shouldn’t repeat.
–    Make sure to save the details of customer after input.
–    Supply customer code to modify the customer records.
–    Restrict unauthorized usage of product details.
–    Make ensure that update the stock when it is purchased.
–    Confirm update of product details.
–    Make sure that customer code is registered.
–    Make ensure the product code is valid while selling product.
–    Allow the user to get discount if he is valid.
–    Discount criteria

PROJECT DESCRIPTION

Sales automation system deals with the purchase, billing system of sales and stock availability information. In this system we have maintain three files, which will store information permanently. The three files consist of customer, stock, transaction information. We can retrieve data when we need of those files. When the purchase transaction done by the user, automatically this information will adds to stock data file. If the sales transaction made by the user then the stock and customer data will get updated. According to the transaction in the sales the stock record should be updated. It doesn’t mean that it should obey the business rules, which are standard. Simultaneously the transaction data file gets updated according to the transaction.

Customer information is maintained with all details about name, address, and customer number. Product information maintains details about product code, product name, quantity available, and amount of product. Transaction information consists of sales and bill of product. Each and every screen has an option to come back to previous screen from where the screen came.

In the first screen we have three options of customer, product, transactions options with the input cursor, which is waiting for any one of these four. Where the fourth option is to come out of the project.
When you get into the customer option it will take to select the options to register a new customer. When you select it, the user has to fill up all the details about the customer. The user can continue this process up to

when the user gives input as no to continue. The second option is to list all the customers in a tabular format who are all registered early. It gives with all information about customer. Third option can be used to modify the customer record. The user should know the customer number to modify his details. When the customer is not available with the given number, it gives a message that the customer is not available. Next option deals to delete the unwanted customer details to reduce the size of the data file. If it doesn’t find the details about the customer, it gives a not found message. At last we return to the main screen when the user selected the corresponding option.

When you get into the customer option it will take to select the options to register a new customer. When you selected this option, the user has fill up all the detail about the customer. The user can continue this process up to when the user gives input as no to add user.  The second option is to list all the customers in a tabular format who are all registered early. It gives with all information about customer.

Third option can be used to modify the customer record. The user should know the customer number to modify his details. When the customer is not available with the given number, it gives a message that the customer is not available. Next option deals to delete the unwanted customer details to reduce the size of the data file. If it doesn’t find the details about the customer, it gives a not found message. When user want to turn back after fulfillment of requirements he has to tap enter key.

If user wants to get into the details about products he has to select product maintenance option from main menu. But it’s restricted. By giving password the user can enter into options available about products. Product menu consist of five options. To add a new product details we have an option called new product details. The user has to input for product code, product name, and quantity on hand, price of individual item.

The user should take care not to repeat the Product code. Is it so, the cursor won’t allow filling the next field information. This option allows storing data about product. It allows adding many products continuously. The next option gives the list of products available in the store in a tabular format. To modify any details of products select ‘Modify the Product details’ option from the main menu of products.

The user should enter the product code, which he wants to edit. When the user gives conformation about the modified information the data will be stored in the disk permanently. To delete an unnecessary product details the user has to select ‘Delete Product details’ from menu of product. User should supply the product code. The deletion will be confirmed when the ‘deletion completed’ message displays else ‘product not found’ message will be followed. To get back to the screens where the user came from, select ‘Back’ option. When user want to turn back after fulfillment of requirements he has to tap enter key.

The third option in main menu is transactions. It consists sales and bills. The members of the Multi Chain Market only can purchase products. The non-member of market is trying to purchase the goods it gives a message to register you. This menu allows the user to buy several products. If the product is out of stock the user may know by ‘quantity on hand’ option. It displays availability of stock.

To get total bill of purchased products get back to transaction menu and select bill option. It gives the total amount. If the customer is allowed to give discount that amount will be subtracted from total amount and net amount be on the screen.  When user want to turn back after fulfillment of requirements he has to tap enter key.
Conclusion:
The automation of Multi Chain Market monitoring is very helpful to maintain data and reduce the time while comparing to manual operations. It improves accuracy. It’s compatible and platform independence. The program can be executed at minimum system requirements also. The project consists of user-friendly a screen that is helpful to the user with out taking any assistance of skilled person.  I hope that this project will help the users and benefit from it immensely.

House Allotments System in VB

ABSTRACT:

The allotment of houses for various people is due for automation. There are various data that are maintained. One of them is the employee detail. The various details include the code, the dress, the designation, name the confirmation data and the retirement date etc. there are also details like the various grades and designation that are maintained.

The employee has to request forma quarters and the various details are maintained. The details of allotment of the quarters are also maintained. The details of the persons occupying the quarters are also maintained. Once the above details are automated then the allotment is considered to be completed.

House Allotments System in VB

SYNOPSIS

The system provides an easy way to perform computer based testing for small computer firms. It also helps to allotment  of  houses to the employees. This system will be customized according to the clients requirements and will be installed for them. This also focus on to allot the houses depending upon their grades quickly and efficiently.

Managing the activities while allotting the houses is not an easy task to allot the houses if  the no.of  employees is more and the no.of houses is less. if the no.of employees is more and the no.of houses is also more, then it is tougher to allot houses and maintain records manually.

In case of employee details , many activities such as collecting the employee name , employee id , address, grade ….etc. by using this employee details we can allocate houses to them quickly and fastly.

Thus the project house allotments was successfully completed.this software is fully functional and operational. since, this project is implemented using VB 6.0, it provides a more direct and easier way to allotment of houses. This project is very flexible and that are lot of provisions made for the future enhancement of this project.