Final Payroll Management System | Feasibility Study | Unit Testing

PAYROLL MANAGEMENT SYSTEM

By [BHAVIK PATEL 06-CEG-31] [BHAVIN PATEL 06-CEG-27]

DEPARTMENT OF COMPUTER ENGINEERING SVIT, Vasad 388306 SARDAR VALLABHABHAI PATEL INSTITUTE OF TECHNOLOGY VASAD- 388306 DEPARTMENT OF COMPUTER ENGINEERING

CERTIFICATE
This is to certify that the project entitled “PAYROLL MANAGMENT SYSTEM” has been carried out by BHAVIK PATEL(06-CEG31) and BHAVIN PATEL(06-CEG-27) under my guidance in partial fulfillment of the degree of Bachelor of Engineering in Computer Engineering of Gujarat University, Ahemdabad the academic year 2008-2009. To the best of my knowledge and belief this work has not been submitted elsewhere for the award of any other degree.

Mrs. Neha Soni

Internal Guide of the Department Prof. B. J. Talati Comp. Engg. Dept.

Head

PAGE INDEX
TOPIC INTRODUCTION TO PROJECT/SYSTEM 1.1 DOMAIN DESCRIPTION 1.2 OBJECTIVES 1.3 LIMITATIONS OF EXISTING SYSTEM FEASIBILITY ANALYSIS 2.1 TECHNICAL FEASIBILITY 2.2 OPERATIONAL FEASIBILITY 2.3 ECONOMIC FEASIBILITY 2.4 SCHEDULE FEASIBILITY DEVELOPMENT MODEL PROJECT PLAN 4.1 TIMELINE CHART REQUIREMENT STUDY/ANALYSIS 5.1 SYSTEM REQUIREMENTS 5.1.1 FUNCTIONAL REQUIREMENT 5.1.2 NON-FUNCTIONAL REQUIREMENT 5.2 USER REQUIREMENTS AND USE CASES SYSTEM DESIGN 6.1 DESIGN METHODOLOGY 6.2 ACTIVITY DIAGRAM 6.3 SEQUENCE DIAGRAM 6.4 STATE CHART DIAGRAM 6.5 E-R DIAGRAM 6.6 DATA FLOW DIAGRAM STANDARD USED FOR CODING TESTING IMPLEMENTATION SCOPE FOR FUTURE ENHANCEMENT ANNEXURE GLOSSARY BIBLIOGRAPHY PAGE NO

1

2

3 4 5

6

7 8 9 10

FIGURE INDEX FIGURE
1 2 3 4 ACTIVITY DIAGRAM SEQUENCE DIAGRAM E-R DIAGRAM DATA FLOW DIAGRAM

PAGE NO.

the project training is very important for the student for selfdevelopment and self-confident. which. E.U. The need for software development today is a competence in a G. tables. As a student of B. The objective of this report is to provide both a conceptual understanding of the system as well as working guide.I based front-end tool as far as the database programming is concerned. will go through the documentation of the project work done by us. and a connection to a database for piping data to controls such as text boxes. it is both necessary and advisable to acquaint the students with the real situation through. Using all the theoretical knowledge and applying into the real application we learns to develop efficient real world application at the time of project training. Surely no other Science as Computer Science is proven as the driving force of the Nation. which helps student to get discipline in all aspects of life.PREFACE It gives us great pleasure in placing in the hands of our esteemed Faculties this individual report. we believe. These applications typically feature reporting functions to provide documentation to teachers and administrative. (3rd Year) when we acquire all the theoretical knowledge. rules and regulations and management in a real sense. Also student learns organizational structure. Computer Science not only decides the present but also the future. So. A typical scenario today involves an application consisting of a visual front end for presenting data and reporting options to the enterprise users. wellplanned project in relevant fields. and list boxes. Aimed for providing the reader with easier and in-depth knowledge of all the basic as well as important aspects related to the systems having the functionality's of there .

respective fields in form of report. ACKNOWLEDGEMENT With great enthusiasm I present this project carried out as a part of Computer semester VI. advised. without whose co-operation and effective guidance I couldn’t have achieved its completion First I would like to thank for giving me the opportunity to work on this project. This project work is an integrated effort of all those persons concerned. The report contains the literature of almost all the things. I am very grateful to I would also like to thank my head of the department Mrs. Bijal Talati for constantly sharing his knowledge and experience with me throughout the project work. Neha Soni for always assisting and helping me in compilation of the project work successfully. I would like to take this opportunity to express my hearty thanks to all those who have guided. I would like to thank my faculty Mrs. inspired & supported me during the project work. . I am very grateful to all others whose names might not appear in this formal acknowledgement but the sense of gratitude will always remain in my heart for them. which I have gone through from the point of view of any system development life cycle.

such as personal details and payment method. Some of this information. however the Payroll system stores basic information about contracts. The industry deducts standard tax rates from payments made to full-time academics. Employees in the Personnel Department will access system via a Windows-based desktop interface. The contract information is maintained by another system called Contracts Management. The system must pay each academic the correct amount. Casual academics can request receiving payment notifications by mail or by email. . the system will also provide a web-based access (called Academic Kiosk)to full-time academics to view their payment details. tax and other deductions. Employees in the Personnel Department will use the system to maintain employee information. on time.1. leave balances.INTRODUCTION TO PROJECT 1. leave balances. As mentioned. The Payroll system can add new employees and delete employees. and make payments to the academics every fortnight. Academic Kiosk can be used to modify personal details and payment method. The Payroll system verifies if the total hours worked so far do not exceed the number of hours agreed in the contract.1 Domain Description Industry employs full-time and casual (contractual) academics. It can manage annual and long-service leave as well as record any sick leave. in particular hourly rate for each contract. can be updated by academics using the web-based interface. and personal information. However. etc. total salaries received year-to-date. and by the payment method requested by an academic. Fulltime academics employees do not receive payment notifications but they can use Academic Kiosk to query the system about fortnightly payments. manage leave.

It doesn’t fulfill many requirement of the administrative department. their management pays a major role in deciding the success of the organization. The record keeping is done manually. employee monitoring. The system is very easy to use and can adjust into any business frame. It keeps the records of the functions performed by the individual employee playing a vital role at the time of performance appraisal. Employee management software can carry out many functions like employee data analysis. Employee information management helps in deciding the future management needs and any changes that has to be made for greater productivity.3 Limitations of the existing system The institute doesn’t have any software application which maintains data of the employees. Alternatively. centralized employee database. The usage of payroll management system would ultimately reduce the overall management costs thus ensuring greater profits and reduced burdens. The institute uses a payroll application which has limited features and doesn’t work efficiently and effectively. etc. .2 Objectives Employees are the backbone of any company. The payments can be mailed (as bank cheques) to academics to the postal address of their choice. This leads to great difficulty when certain needs arrive of looking into employees’ past data. 1.The academics can choose the payment method. management of the time sheet. The application just keeps very trivial information of the employees and doesn’t facilitate with any kind of analytical ability. 1. the payments can be directly deposited into an academic’s bank account.

The technical feasibility is also attributed to the fact that the system does not make use of any additional or external third party components which can lead to increased load on the system. Operational Feasibility 3.2 Operational Feasibility: The Payroll Management System is intended to provide a very user-friendly and easy to use interface which is beneficial for both the visitors as well as the operators who help in providing support for the system. All the tools needed for the development are already available with the organization and the organization does not have to acquire any new resources. This system would also be easily acceptable among the visitor and administrator. as there is no need of any special skill set for using the application. 2. Technical Feasibility 2.2. Economical Feasibility 4. This system also benefits the users as they do not have to download anything on their terminals increasing their efficiency and ease of use. Scheduled Feasibility 2.FEASIBILITY ANALYSIS We have analyzed the feasibility of the system in terms of following spans: 1.1 Technical Feasibility: The development process of Payroll Management System would be advantageous to the organization because we would make use of only the currently available resources of the organization. .

3 Economic Feasibility: The Payroll Management System has a very low development cost. I had to complete the project in time and if it is not possible to complete the software in time then I would try our best to fulfill client requirements. there is no need to provide special training to the users of the website. thus saving valuable time and money. The low cost is attributed to the usage of the existing resources of the organization. As the website is very user friendly and easy to use. Every project is completed in a specific duration. 2.2. So i have tried our level best to fulfill each and every requirement.4 Scheduled feasibility: Projects are always given deadlines. . I was the only working on the project and I had the project duration of four months only.

without any overlapping or iterative steps.3. through design. the development proceeds to the next phase and there is no turning back. Development moves from concept. installation. Often considered the classic approach to the systems development life cycle. Once the water has flowed over the edge of the cliff and has begun its journey down the side of the mountain.DEVELOPMENT MODEL The Payroll Management System is a database software application which is developed using a waterfall software developing model. implementation. and theoretically. Each phase of development proceeds in strict order. . troubleshooting. testing. A schedule can be set with deadlines for each stage of development and a product can proceed through the development process like a car in a carwash. Imagine a waterfall on the cliff of a steep mountain. Waterfall development has distinct goals for each phase of development. it cannot turn back. Once a phase of development is completed. the waterfall model describes a development method that is linear and sequential. It is the same with waterfall development. and ends up at operation and maintenance. be delivered on time. The advantage of waterfall development is that it allows for departmentalization and managerial control. The waterfall model is a popular version of the systems development life cycle model for software engineering.

To follow the waterfall model. System Engineering Analysis Design Code Testing Maintenance . an implementation of that design is made by coders. build and fix. separate software components produced are combined to introduce new functionality and remove errors. there are various modified waterfall models (including Royce's final model) that may include slight or major variations upon this process. Thus the waterfall model maintains that one should move to a phase only when its preceding phase is completed and perfected. The software in question is designed and a blueprint is drawn for implementers (coders) to follow — this design should be a plan for implementing the requirements given. one proceeds from one phase to the next in a purely sequential manner. synch and stabilize. When the design is fully completed. However. For example. Towards the later stages of this implementation phase. Once an application is in the testing stage. one first completes requirements specification. it is very difficult to go back and change something that was not well-thought out in the concept stage. which are set in stone. and the spiral model. When the requirements are fully completed.The disadvantage of waterfall development is that it does not allow for much reflection or revision. one proceeds to design. rapid application development (RAD). Alternatives to the waterfall model include joint application development (JAD).

CD: Control Decentralized 3. The problems are being recognized by them and are solved by us.2 TEAM ORGANISATION january february march april 1/1 8/1 15/1 22/1 5/2 12/2 19/2 26/2 5/3 12/3 19/3 26/3 2/4 9/4 16/4 23/4 There are three types of team organizations: 1. DD: Democratic Decentralized 2.1 TIME LINE CHART month task DOMAIN DISCRIPTION REQUIREMENT ANALYSIS DESIGN CODING TESTING DOCUMENTATION FINAL DOCUMENTATION 4.4.PROJECT PLAN 4. CC: Control Centralized For our project the team organization is Control Decentralized because here we are having the lecturers as our guide. .

Initially the work of project management was done manually and the data was kept in files but now the technology is such that each employee who is part of project management team has all the projects. . Function Inputs Create User: .REQUIREMENT ANALYSIS Nowadays. Password. Milin Patel And Ms.V. 5. Due to which user can quickly know regarding the status of any project and its progress. This system has been made so. reports all at hand.Neha Soni. It is advancing each and every day. that user can work faster and in a much better environment. 5. the world is moving at a lightening swiftness and so is computer field.I. Such is the technology which is increasing at a very fast pace. – Computer department) The project was undertaken under the guidance of Mrs. their phases. Mr. Full Name.The software project team for member: “Payroll Management System” consists of 2 Bhavin Patel and Bhavik Patel (S. Jignya Seth.User name.1 SYSTEM REQUIREMENTS  FUNCTIONAL REQUIREMENTS:  Function 1: Administration of the Application Function Purpose and Priority Administrator can create new roles/rights/users and edit the existing roles/rights/users.T.

Experience Profile : Worked As. Nos. Grade .Give rights to the user Function Operations Create User: . Scale . qualification profile. Sex etc. Function Inputs Personal Details : Name . Function Outputs Create User: .New user is created and assigned to the selected rights and then added in the database. Date of Birth . Working Category Basic Salary Information : Designation . Function Outputs The user authentication is checked against the operation used by the user. Passing Year . Contact .Changes made to the user information are saved. Function Operations The employee details can be added . Applicable allowances and deduction and bank information etc. experience profile and basic salary information. Institute. If user is not allowed to access the asked operation he/she is reported by the application  Function 3: Designation History . Date of Joining.The admin fills the information about the user and selects rights to be given to the user clicks on the “Save” button. Qualification Profile : Qualification . Address . Department .  Function 2: Manage Employee Data Function Purpose and Priority It stores detailed employee profile including his/her personal information. Working Years. Edit User: . edited and deleted by the users who have enough authority for the functions.Create Rights :.

Reason for new designation etc. Function Outputs The current basic is upgraded according to the given increment/incentives based on the employee’s scales. Function Inputs Date. Function Outputs The current designation is upgraded.  Function 5: Scale Prediction Function Purpose and Priority This is the analytical tool which allows to generated data showing the normal progress of any employee in future . Function Inputs Designation. Type. Function Operations The user can add increment/incentives records. month of increment is changed.  Function 4: Increment and Incentive Detail Function Purpose and Priority The functions allows to keep track of the increments/incentives given to the employee. Reason.Function Purpose and Priority The past data of the employee designation and his/her progress throughout career is maintained. Function Operations The user fills the input details save. New scale is assigned and joining date . Date of Joining. Nos of increment/incentives.

The years after which the scales should be upgraded. Current date) . Starting Date ( Joining date .2 USE-CASE DIAGRAM: USER .0 3) Database Tool – Oracle 5. Function Operations Generates the data including year and basic of the employee according to the given inputs. Function Outputs Shows graphical view of the generated prediction. Ending date.Function Inputs Selects employee .  NON-FUNCTIONAL REQUIREMENTS: Hardware Requirements : 233 MHz Pentium processor or other compatible Intel Chipset Motherboard 512 MB SD-RAM 4 GB hard disk Software Requirements : 1) Operating System -Windows 98 onwards 2) Application Software –Microsoft Visual Basic 6.

In the structure-oriented approach.System Design 6. Depat ADMINISTRATOR View the Time & Date for Joinig EMPLOYEE View Reports Exit 6.1 DESIGN METHODOLOGY The method that we have used for designing this system is “Structural Design”. the problem is viewed as a sequence of things to be done.Login Registration Process Selection of different Categories Diff. The primary focus is on functions. A number of functions are written to accomplish these tasks. A typical program structure for structural programming is as follows: .

Each function may have its own local data. Data move openly around the system from functions to function. Some of the striking features that encouraged us for using structural design are: 1. This provides an opportunity for bugs to creep in. Global data are more vulnerable to an inadvertent change by a function. which encouraged us to use the structural approach.2 ACTIVITY DIAGRAM MAIN FLOW . 6. 3. Functions transform data from one form to another. Emphasis is on doing things (algorithms). 5. Most of the functions share global data. Employs top-down approach in program design. many important data items are placed as global so that they may be accessed by all the functions. 4. 2. Another serious drawback with the structural approach is that it does not model real world problems very well.5 Function – 7 Function – 8 In a multi-function program.Main Program Function – 1 Function – 4 Function – 6 Function – 2 Function – 3 Function . 6. Large programs are divided into smaller programs known as functions. Along with the disadvantages the structural design has various advantageous features.

Diagrams For Each Operation : 1) Add Employee: .

It is a construct of a Message Sequence Chart. .Check Access [Not Allowed] Return Error Message [Allowed] Add Employee Record Return Success Message 2)Delete Employee: Check Access [Not Allowed] Return Error Message [Allowed] Delete Employee Record Return Success Message 3)Update Employee: Check Access [Not Allowed] Return Error Message [Allowed] Update Employee Record Return Success Message 6. event scenarios. Sequence diagrams are sometimes called Event-trace diagrams.3 SEQUENCE DIAGRAM A sequence diagram in Unified Modelling Language (UML) is a kind of interaction diagram that shows how processes operate with one another and in what order. and timing diagrams.

4 STSTE CHART DIAGRAM A state diagram is a type of diagram used to describe the behavior of systems.State diagrams can describe the possible states of an object as events occur. State diagrams require that the system described is composed of a finite number of states. Each diagram usually represents objects of a single class and track the different states of its objects through the system. State diagrams can be used to graphically represent finite state machines .USER USER DB Enter password SERVER Verify password Open admin screen Password OK User Functions Verify functions Acknowledge functions Perform functions Display result 6.

Login Employee Data Authentication Scale Prediction Incentive/Increment Backup/Restore 6.5 E-R DIAGRAM .

6 DATA FLOW DIAGRAM 0th Level DFD .M L e a v e C C a n T a k e 1 M 1 L o a M n a t e g a r y C a n T a k e C H M C H a n a v e 1 M 1 1 a n a v e E m p 1 l o y e e 1 1 C a n T a k e 1 D e p a r t m e n C H t a n a v e 1 C H 1 a n a v e A M d v a n c e A l l o M w a n c e s C a t e g a r y M D M e d u c t i o n C A u m t t C H a n a v e M M o n t h l y M S a l a r y 6.

L E s t a l m e n D e t a i l S a l a r y S l i p P a y E m p l o y eM e a n m p l o y e e S y s D e t a i l L D e a v e e t a i l o a n I n t M a P n a g e m o l i c My R e n a n t a g e m r o lO l t h e r a g e m e n t t e m S a l a r y S e p o r t s R e p o r t s L e a v e t a t e m e n t A c c o u n t 1st Level DFD .

E A E m C p a l o m y e e E D p l o y e e e t a i l D e t a i l m p l o y e e l l o w a n c e s A l l o w a n t e g C a a r ty e g a r 1 y . 2 r o c e s o f D e d u c t D c e a t al c i ul l a p l o y e e e d u c t i o sG i n r go i o n s t i o n n s s S a l 1 a . 1 D e t a i lP r o c e s s i n g P r o c e s s i n g o f o f L e a v e L D e e a t va e i l S a l a r yS a l a r y A l l o w a n c e s D e t a i l i n f o r m Ia n t if oo nr m c a a t il oc un l a t i o n O v e r T i m e O v e r t i m e D e t a i l P r e s e n t D e t a i l P r e s e n t D e t a i l G r o s s S a l a r y A d v a A d v a n c e D e t a L o a E n n c e P i l L o a n 1 . 0 1 . r3 y N e t S a l a r y m D R S a e p o r t s t m e D e d u c t i o n l a r y S t a o r R e p o r t s 2nd Level DFD .

E E m p l o y e e m D D p l o y e e e t a i l e t a i l s L D e a v e e t a i l L e a v e C a C t e g a t e g a r y P r y D e t a i l a 2 . 0 r o c e s s i n g O f S a l a r y i n f o r m a t i o n t O v e r t i m D e t a i l D e p a D e p a r m r t m e n t D e t a i l e n O E P m l o y e e r e s e n t s P r e s e n p v e r t i m t s D e 2nd Level DFD .

D i n D a i l y A l l o w f o a r m n A a c e s t i o n B a s i c S a l a r y B a s i c S a T T A r a l l o v e l l i i nn f g o r m w a n c e s A a t i o P A c n 2 . 1 r o c e s s i n g o f l l o w a n c e s a l c u l a t i o n H H R A i n f o r m R A a t i o n i n M f o e d r m M e d i c a l a t i o n i c a l 2nd Level DFD .

2 . 1 o a n e t a i l E A A d m p l o y e e d v a n c e v a n c e L o a a s t e L o a n r e t a i l T r a n s e c t i o D e t a i l n _ M a s t L o a n _ T 7. 0 A d v a n c e D e t a i l 2 .P i n P r o v i d e n t f o F r m u n F a d t i in o f n o P r m T a P t i o n r o f e s s i o n a l G r o s s G S 2 .Standard Used For Coding CONTROL PREFIX SR NO 1 CONTROL TYPE Checkbox PREFIX Chk . 2 P r o c e s s i n g o f D e d u c t i o n s c a l c u l a t i o n a l a r y r o s s S a l A D . 2 d v a n c e e t a i l L D o a n e t a i l 2 L D L M D o a n .

Testing is one of the critical phases. . After system is ready it should go for testing. The system Developer has to undergo and which one should not avoid before final system implementation.dropdown list box Command button Common Dialog Control Directory listbox Drive listbox Form Image Horizontal scroll bar Image combo Image list Label Line List box List view Menu Option button Picture box Rich text box Shape Timer Textbox Toolbar Treeview Vertical scroll bar Cmb Cmd Dlg Ctr Dir Drv Frm Img Hsb Imgcbo Ils Lbl Lin Lst Lvw Mnu Opt Pic Rtf Shp Tmr Txt Tlb Tre Vsb 8.TESTING • Testing plan is one of the modules of the system analysis and the design.2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 24 25 Combo box. which has greater importance.

In addition. testing demonstrates that software functions appear to be working according to specification and that performance requirements appear to have been met. Test planning can begin as soon as the coding phase is complete. it will never cover errors in the software. Secondly. • done. During system testing the system is used experimentally to ensure that software does not fail special test data are input and result examined and likewise corrections are VARIOUS TESTING METHODS ARE: • Unit Testing • Integration Testing • System Testing • Acceptance Testing . data collected as testing is conducted provides a good indication of software reliability and some indication of software quality as a whole. it can only show that software errors are present. But there is one thing that testing cannot do: • Testing cannot show the absence of defects. Testing should be planned before testing begins.• If testing is conducted successfully.

we tested whether the system is accepted for operational use or not. we tested individual components like each controls for their validations to ensure that they operate correctly. This testing activity can be considered testing the design. In this employee management system I have used unit testing & integration Testing . we tested whether system elements have been properly integrated and perform allocated functions to detect the errors that may result from unanticipated interactions between sub-system and system components. in Acceptance Testing.Unit Testing Integration Testing System Testing Acceptance Testing • In Unit Testing. • In System Testing. which are then tested. • The next level is called Integration Testing. • Finally. In this many unit tested modules are combined into subsystems. The goal here is to see if the modules can be integrated properly.

Checked and OK Test Description: Testing for Authentication Module Action To Be Performed Expected Result Case 1: Operate functions in the Employee Form If the user have enough rights to perform function Take further action Actual Result Click on the function(e.Search). Click on the user menu Checked and OK Selects user Checked and OK . Checked and OK If user doesn’t assigned the rights to perform particular function show error message Case 2: Change user rights If the user is administrator then allow him to change user rights and information.Edit. Checks remember my name Check box Actual Result If username is valid then ask Checked and OK for password If it is checked already directly jump to password page.g Add.TEST CASES: Following test cases were carried out: Test Description: Testing for Login Module Action To Be Performed Expected Result Case 1: To Login Into Application Double Click on the user. If the user is encoder the menu should be disabled Display all the information of the selected user.Delete.

Checks if the selected employee is regular typed. Show directory viewer Copy database on the choosen Directory Save log into database Show error report is file is not copied correctly Case 2: Restore Database Click on Database utility menu Selects any previously taken Backup from log Checks if the the user is allowed to restore If not then show error message. If yes then generate scale records Test Description: Testing for Backup Restore Module Case 1: Backup Database Action To Be Performed Expected Result Click on Database utility menu Selects backup directory Checks if the the user is allowed to take backup If not then show error message.Change user information Update rights of the selected user. Click Generate Scale If not then show error message.Scale change yrs) Checks if the ending year is valid.If not then shows error.Ending Year. Checked and OK Test Description: Testing for Scale Prediction Module Action To Be Performed Expected Result Enter inputs(Start Year. Restore the database to the original path If there is something wrong Actual Result Checked and OK Checked and OK Actual Result Checked and OK Checked and OK Click on start backup Checked and OK Checked and OK Checked and OK .

the implementation method used is the Big Bang Adoption. • • Phased adoption :The adoption will happen in several phases. so after each phase the system is a little nearer to be fully adopted. and meanwhile do their work using the old system. the so called instant changeover of the system. because the new system is all there is. Since our system is completely independent from the existing system and makes no use of the existing system. so all the users can get used to the new system. • Parallel adoption: The old and the new system are running parallel. . Everybody starts to use the new system at the same date and the old system will not be used anymore from that moment on. because it happens in such a short period. there are three different ways to adopt this new system: The big bang adoption. There are no special interfaces needed to be able to get used to the new system. User documentation does not need to be updated during the implementation process. phased adoption and parallel adoption.with restoration show error message 9.IMPLEMENTATION When a new system needs to be implemented in an organization. Big bang adoption: The switch between using the old system and using the new system happens at one single date.

SCOPE OF THE FURTHER ENHANCEMENT This application can be further enhanced to cover each aspect of the institutes. . The following are some of the important enhancement that can take place into the current working software application : 1) This includes management of employees salary . Employee management system will be extended towards a complete management package for the institute.10. 2) In Our System an Administor easily Modify and Update the any Emplyee’s information. The application will prove itself as a powerful tool which enhance the working power of the administration department and can help in improving overall management of the institute. 3) Easily add new user in database. leave status and each kind of financial features which helps the institute as a financial tool. It will really help to manage and organize the employees’ detail very efficiently and effectively.

External entity: A source or destination of data which is external to the system. pay slip. . 4. 2. Association: It represents the relationship between the entities 7. 3.ANNEXURE 1. For example prepare attendance report. 5. Process: A process done in the system is denoted by this symbol. Data store: Any store data but with no reference to the physical method of storing. It may be in the form of document or letter. Multiplicity: Use to represent one to many relationship between the entities * 6. A data flow: it is packet or data. etc. State: It represents current state of system that is being designed.

.

response time. throughput and efficiency. System: an organized collection of components that interact with each other. Function: it describe in the statement of scope are evaluated and in some Cases refined to provide more detail prior to the beginning of estimation. during which high-level decisions are made about the overall structure of the system.GLOSSARY This part shows the terms used in my project. Data Table: the connection between the output of one object or process and The Input to another. It processes input data and generates Requirement analysis: requirement analysis categorizes requirement and organizes them into related subsets. resource consumption. . and data sources/destination. System Design: the first stage of design. Requirement specification: it is the final work product produced by the system and requirements engineer. data stores. Performance: Performance is measured by processing speed. data processes. Process: something that transfers the data value. Data Flow Diagram: a means of representing a system at any level of detail with a graphic network of symbols showing data flows.

com .google.Ivan Bayross • www.BIBLIOGRAPHY • VB Black Book • Mastering VB • Visual Basic in 21 Days • SQL/PLSQL .vbtutor.wikipedia.co.net • www.in • www.

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master Your Semester with a Special Offer from Scribd & The New York Times

Cancel anytime.