This action might not be possible to undo. Are you sure you want to continue?
Mr. Chetan Vyas (Senior programmer)
Submitted By: Pragya Jaiswal: 0500818084,05008181430 Kanika Shukla Pratibha Prajapati Ashwani Mishra
UPTEC Computer Consultancy LTD. 56, S P Marg Civil Lines Allahabad.
1. Acknowledgement 2. Preface 3. Certificate of Originality 4. Synopsis of the project 5. Problem Statement A) Existing system Description B) Problem of Existing System 6. Introduction of Project A). what is ASP.NET B). ASP.NET Provides C). Advantages of ASP.NET D). SQL Server 7. Objective and Scope of the Project 8. System Analysis A) Detail of proposed system B) SRS (System Requirement Specification) C) Project Planning D) Feasibility Study E) Database Design F) Structure Chart 9. PERT Chart 10. Software Engineering Methodology (Prototype Model) 11. Hardware and software requirement 12. System Development Life Cycle (SDLC) 13. Logical diagram A) DFD B) ERD C)Flow Chart 14. Input and Output Screen Design 15. Coding 16. Testing A) Type of Testing B) Test Cases C) Level of Testing 17. System Maintenance and Evaluation 18. Users /operations manual
With great esteem & reverence, we wish to express our deep sense of gratitude to our project guide Mr. CHETAN VYAS for valuable guidance & timely suggestions. Our sincere gratitude is expressed for his help, patronage & for going through the manuscript critically. With due regards we present this project to you extending my heart felt gratitude to all those who made this project a success. We owe a great deal to our erstwhile teachers for their inspiration and guidance. We are grateful to our senior Mr. Arun Yadav who had always been a source of inspiration and helped us a lot. This explosion work gives us opportunity to visit on company’s showroom & apply the article as well as practical knowledge. It gives as an opportunity to name a bird’s eye view of the showroom & its environment. Our special thanks to the project supervisor, Mr. CHETAN VYAS for his dedication, diligence and sincerity in making this project a reality. We are very thankful to Mr. ALOK SRIVASTAVA for assigning us the project on “Online Employee Information System & Payroll System”, for “Green Land Motors Allahabad”. Further we shall also want to express our profound thanks to Mr. CHETAN VYAS. We shall also want to thanks to our group member, who providing us the required support in the project.
Information technology has been like a boom in almost every kind of management system. The continuous improvement in the field of technology along with increasing complications in day-to-day life has resulted in the online information system. Computers have reduced all the paper work of any organization but online information provides more flexibility to its customers. Online information provides much more facilities to its employers. Online information not only allows the enhancement in the computation speed but also has brought about a revolution in the organization. Thereby we have made an effort to incorporate all those features in an online information system, which could help users to access & do any type of work without wasting much of his precious time. Computer and its utility has become an indispensable device of our society. Computer is complement to the human efforts. In the present time computers are used in all spheres of life. Computers are used in innumerable fields. Due to these qualities of computer we have decided to make software for managing leaves, as computer are provided to be extremely useful in managing and controlling various activities of Online Employee Information System & Payroll System. The documentation of this project is given along with it. It contains detailed methodology along with required diagrams. Source code is also given with the documentation. In the end of the project, its advantages have been taken up. This software package is developed in the partial requirements for the certificate of BCA degree course examination.
Certificate of Originality
This is certify that the project report entitled ________________ Submitted to UPTEC computer consultancy in partial fulfillment of the requirement for the award of the degree of bachelor of computer Application (BCA),is original work is carried out by Mr/Ms._____________________ with Roll No: ____________ Under our guidance . This report or a similar report on the topic has not been submitted for any other examination and does not from part of Any other course undergoes by the candidate. Pragya jaiswal Signature of student: Date: Name and Address
Signature of Guide: Date: Name, Designation and Of Address of Guide
Problem Statement 1)Existing system description:The “Green Land Motors Showroom” is mainly a franchise given by the “MARUTI”. The showroom is a retail marketer of Maruti four wheelers. In the showroom there are 3 main departments: 1) Employee Information 2) Payroll System 3) Sales Department All these three departments have their head officer who manages & control all the working. But the information or details about the every employee only can access by the Administrator or H. R. Executive. H. R. Executive manages the detail or information about the Employee Information System & Payroll System and he/she also submit all information of monthly detail.. If any new person got a job in the showroom the interview is conduct or taken by the Administrator or H. R. Executive or head of particular department. In the showroom all information about Employee Information System and Payroll System is maintained by the H.R. Executive. The H.R. Executive is only made changes in the database or records. H.R. Executive saw all queries but the employee can see only his/her information.
2)Problem of Existing System:In spite of being the newest showroom “Greenland Motors” in Allahabad this showroom two main departments are still untouched from computerization. But by involving us in this project, computerization process starts. Maintaining crucial data of around 200 employees is difficult in manual process. There are many problems, which are faced by the office member. They are as follows: 1. Functionality: Because there work is done manually, so the there functionality is very low as compared to other department, which are computerized.
2. Time consuming Process: -
Each a single process takes lots of time.
3. Processing Speed: -
The effort done for the progress of the work is done manually, so the processing speed of the existing system is very low & frustratful for employees.
4. Portability: -
The portability of the current existing system is not possible because the information is stored in files, & searching for a piece of information among all those files is very tedious work.
5. Input/Output Interfaces: -
The Input/output Interfaces of the current system are very poor. To work with there current Input/Output Interfaces need deep understanding of their work.
(A )Requirement Analysis: After doing initial investigation the exact need of the user from proposed system is accomplished. Requirements analysis is the most important part of the system development life cycle. The most important phase of requirement analysis is finding information from user. These are the following points, which show what the user requires: 1. Automation of activity. 2. To be totally integrated online system. 3. User interfaces. 4. To develop computerized software. 5. To develop user- friendly software. 6. To create software with error handling capabilities. 7. Less burden of work. 8. Fast and accurate report generation. 9. Paperless Environment. 10. Cost maintenance.
Introduction of Project:-
The Online Employee Information System & Payroll System (OEIPS) deals with the controlling & managing the entire working of Employee Information & Payroll System ,Green Land Motors Allahabad. There are many activities in the department & he/she want to mange all the activities by a single project. “Online Employee Information System “gives some flexibility in the project to add, modify or delete new employee in the showroom or add or modify employee’s entries of the showroom. This project on “Online Employee Information & Payroll System” is basically to help in managing their showroom by converting manually running system to a computerized system & online system. By introducing this current system, that work maintained by the H. R. Executive of that showroom would become easier, convenient & time saving. A project is a complete information regarding employee. Adding new employee entry or maintain only last one year employee record/details, show the Payroll information of employee. Concurrently Administrator or H. R. Executive can see the stored information. The employee can see only his/her information. This project is designed as managing & storing information preparation of details, plan or scheme of any engineering undertaking. Thus the project is schematic, consideration, particular object.
What is ASP.NET?
ASP.NET, similar to desktop applications, we can use variables, define functions & make use of a database, even a connection to a remote database is possible .In a summary we can say that ASP.NET is a programming system, to develop dynamic internet pages. This system provides the necessary technologies, like Classes & Objects. ASP.NET is the platform that we use to create Web Applications & Web services that run under IIS.ASP.NET is not the only way to create a Web application .It is integrated with the Microsoft server, programming, data access, & security tools.
What ASP.NET Provides?
ASP.NET provides a high level of consistency across Web Application development. In a way, this consistency is similar to the level of consistency that Microsoft Office brought to desktop application. ASP.NET is part of the .NET Framework & is made up of several components. ASP.NET is the most complete platform for developing Web Application that run under IIS. It is important to remember that ASP.NET is not platform independent. Because it is hosted under IIS, ASP.NET must run on Windows servers. To create Web Application that runs on non-Windows IIS server, such as Linux/Apache, we must use other tools generally CGI.
Advantages of ASP.NET:-
ASP.NET has many advantages over other platform when it comes to creating Web Applications. Probably the most significant advantages are its integration with the Windows server & programming tools. Web Application created with ASP.NET are easier top create, debug & deploy because those tasks can all be performed within a single development environment – Visual Studio.NET. ASP.NET delivers the following other advantages: Executable portion of a Web Application compiled so they execute more quickly than interpreted script. On-the-fly updates of deployed, Web Applications without restarting the server. Automatic state management for controls on a Web pages so that they behave much more like Windows controls. The ability to create new customized server controls from existing controls. Built-in security through the authentication/authorization methods. Windows server or through other
Integration with ADO.NET to provide database design tools from within Visual Studio.NET. Full support for Extensible Markup Language (XML), cascading style sheet (CSS), & other new & established Web Standards. Built-in-features for caching frequently requested Web pages on the server, localizing content for specific language & cultures & detecting browser capabilities.
How IIS & ASP.NET manage processes:Understanding application boundaries is important because ASP.NET uses these boundaries to determine how the application is run on the server. When IIS receives a request for a resource within a web application, IIS uses aspnet_isapi.dll to call the ASP.NET worker process. The ASP.NET worker process loads the web application’s assembly, allocating one process space, called the application domain, for each application. In this way, ASP.NET maintains process isolation for each web application. This is different from the way IIS provided different isolation levels for older Active Server Pages (ASP) application running under DLL Host.exe.The isolation level setting in IIS have no effect on ASP.NET applications. In IIS version 6.0, you will be configuring multiple application pools, each of which can be served by one or more process instances. In addition, ASP.NET is integrated with the IIS version 6.0 kernel mode HTTP listeners, which will allow request to pass directly from the operating system to the ASP.NET worker process.
SQL Server 2000: SQL server 2000is an RDBMS that uses Transact – SQL to send requests between a client computer and a SQL Server 2000 computer. An RDBMS includes databases, the database engine, and the applications that are necessary to manage the data and the components of the RDBMS. The RDBMS organizes data into related rows and columns within the database. The RDBMS is responsible for enforcing the database structure, including the following tasks: Maintaining the relationships among data in the database. Ensuring the data is stored correctly and that the rules defining data relationships are not violated. Recovery all data to a point of known consistency in case of system failuThe database component of SQL Server 2000 is a Structure Query Language (SQL) compatible, scalable, relational database with integrated XML support for Internet Application. SQL server 2000 builds upon the modern, extensible foundation of SQL Server 7.0.
Objective And Scope
The scope of this project “Online Employee Information & Payroll System” is to manage the detailed information of employee’s i.e. details of field advances, details of various allowances, credited or debited to person’s account. This project is very much versatile satisfying all functions of Employee Information & Payroll System. The main objective of this project is to manage “Employee Information & Payroll System” so that any employee can access all the records or details at any time from anywhere. The primary objective of this project is to reduce time & provide security for maintaining Employee Information System. One of the prime objectives is to equip system with features so that only authentic people can access data. The system can’t be updated by any other person other than who prepared it. Proposed System Objective:1. Automation of activities. 2. To be totally integrated online system. 3. User friendly interface. 4. To develop a computerized software. 5. To develop a user friendly software. 6. To create software with error handling capabilities. 7. To manage all the functions properly. The most important objective of this project is to respond to all queries of all accounts related & all Employee Information related.
A) Description ofProposed System The objective of the proposed system is to manage different information regarding any employee such as his/her verification or general Information & Payroll Information. The proposed system is also managing the internship.
a) Data & Information Security: The stored information can’t be directly retrieved. To run the application you are first authenticated & if you are authorized user then you can see your information.
System Security: The system is secured as well as auditable too.
Same Employee ID: The Employee ID is unique. The same employee code or ID is not allotted to two persons or employee. The employee is uniquely identified by his/her code or ID.
d) Storing Large Amount of Data: The system can handle large amount of data handling large amount of data.
B) Project Planning
Planning of this project incorporates determine the validity of request, evaluating the alternatives and selecting the best one based upon feasibility study. Depending on the results of the initial investigation, it expanded to a more detailed feasibility study. A feasibility study is a test of system proposal according to its workability, impact on the showroom, ability to meet user needs and effective use of resources. The key questions are:-
1. What are the user’s demonstrable needs? 2. Is the problem worth solving? 3. How can the problem be redefined? The objective of feasibility study is not to solve the problem but to acquire range of its scope.
C).System Requirement Specification: Introduction: This document describes the software requirements for the Online Employee Information System & Payroll System (OEIPS) built for “Green Land Motors Maruti Showroom” (GMMS). Scope: The GMMS is proposal to build a prototype of an OEIPS for their current system. The system will be designed to provide an electronic version of the EIPS in Green land. The system will have a user-friendly graphical interface & will be more cost effective compared to the current non-electronic version of the EIPS. The objectives of this development effort are: To provide existing employee with a new environment. To provide an avenue for employee to get their information in a more convenient way. To collect statistics in a more efficient manner for future further development and construction. To increase the efficiency of EIPS. Acronyms and Abbreviations:
OEIPS –Online Employee Information System and Payroll System CASE – Computer Aided Software Engineering PP – Project Plan SDD – Software Design Description
SDS – Software Design Specification SPMP- Software Project Management Plan GUI – graphical user interface
Introduction: - Green land motors Online Employee Information System and Payroll System prototype http://www.greenland motors.com Overview: The SRS is a brief description of the characteristics of the software to be built, its functions, its users, its constraints and its dependencies. It is about specific requirements, such as functional requirements, external interface requirements, performance requirements and also designs constraints and quality characteristics. Finally it includes all the tables of contents, the appendices and the index. General Description: This section describes the general factors that affect the product or software and its requirements. This section consists of 5 subsections. This section doesn’t state specific requirements. Each of the subsection makes those requirements easier to understand; it doesn’t specify design or express specific requirements.
Product or software Perspective:- the OEIPS diagram showing the overview of the
system’s modules and relationship of the system to external interfaces is presented in diagram.
Functions of System Components:Database • Store data • Create reports • Provides access to data • Update information Server • Provides access to the database • Authenticates users • Process of information and payroll system • Perform backups • Produces reports External Interface Terminal • Employee or Administrator use terminals to access the servers.
• Employee and H. R. Executive use terminal to get information about the present employees. • The Administrator use terminals to see the reports generated by the database software. Personal Computer • Administrator, H.R. Executive or employee use PC to obtain a remote to the server and the information and payroll database via the Internet. Cell Phones • Server as a medium of accessing the server and the information and payroll database. • Employee may use cell phones and the latest telecommunication technologies to access the server and the information and payroll database via Internet, or they may use cell phones to call H. R. Executive to inquire about their information. • Computer hardware and peripheral equipment to be used: Workstation, which includes CPU’s, monitor, keyboard and mouse. Printers Network Terminals Cell phones to test connection to the server via remote access. User Characteristics:The main users of the system will be the employees seeing correct information, the H. R. that process updating information for employee, and the administrator that access the reports generated by the system. The GUI provides an easy way of using the Online Employee Information System and Payroll System with minimum of training. Specific Requirement: This section of the SRS should contain all the details needs to create a project. This is typically the largest and most important part of the SRS. Specific requirements should be organized in a logical and readable fashion. Classifying the specific requirements is as follows: 1. Functional Requirements 2. Performance
3. Design 4. Attribute 5. External Interface Requirement 1. Functional Requirements: This subsection of the SRS should specify what is to be done by the project, to what specific requirement, what input should be transformed to what outputs (not how this is done), what specific operation is required. For each function, specific requirements on inputs, processing and outputs. These are usually organized: I. Purpose of the function: - Provide rationale to clarify the intent of the function. II. Input/output: - Source, valid ranges of values, operator requirement, and special
III. Operation to be performed: - Validity checks, responses to abnormal conditions,
type of processing required.
IV. Output: - Destinations, valid ranges of values, handling of illegal values, error
messages. 2. External Interface Requirement: I. User Interfaces: This should specify: a) The characteristics that the software must support for each human interface to the software. The person operates through a display terminal, the following should be specified: I. Required screen formats. II. Page layout and content of any reports or menus. III. Relative timing of Inputs and Outputs. IV. Availability of some form of programmable function keys.
b) All the aspects of optimizing the interface with the person who must use the system. II. Hardware Interface: The logical characteristics of each interface between the software & the hardware component of the system. What devices are to be supported, how they are to be supported? III. Software Interface: Required software & interface with other application system. We define the purpose of the interfacing software as related to this software product and we define the interface in the term of message content and format. 3. Design constraints:Design constraints can be imposing by other standards, hardware limitation, etc. A. Standards compliance: Specify the requirement derived from existing standards or regulations. They might include: Report format Data naming Account procedures Audit tracing B. Hardware limitations: Identify the requirement for the software to operate inside various hardware constraints. Quality Characteristics: There are of following type of Quality Characteristics that can apply to software. • • • • Correctness Efficiency Flexibility Integrity/security
1. 2. 3. 4.
• • • • • • •
Interoperability Maintainability Portability Reliability Reusability Testability Usability
Database: Our requirement for SQL database is to be developed as part of the project. This might include: • • • • • • Types of information. Frequency of use. Accessing capabilities. Data element and file description. Relationship of data elements records and files. Retention requirement for data.
D). Feasibility Study:Feasibility is determination of whether or not a project is worth doing. The project followed in making this determination is called Feasibility Study. The analyst can go ahead and prepare the project specification which finalize project requirement. The preliminary investigations examine project feasibility. These solutions are further evaluated to find out the following: Technical Feasibility Economical Feasibility Operational Feasibility Legal Feasibility Time Feasibility
Technical Feasibility:In this type of Feasibility we describe specifying equipment and software that will successfully satisfy the user requirement. We should be examined to see if the proposed equipment has the technical capacity to hold the data required. The Technical needs of this system are: Ability to process a large volume of data transaction to fulfill this purpose the application is developed using ASP.NET as front end and SQL Server as back end. Economical Feasibility:In this type of Feasibility we determine the project should be economically feasible by every type of user. A Cost-Benefit analysis is necessary to determine Economic Feasibility. The primary objective of Cost-Benefit analysis is to find out whether it is economically worthwhile to invest in the project. Cost-Benefit analysis is performing by first listing all the costs association with the project. Costs consist of both direct cost and indirect cost. Direct costs are those incurred employing people; cost of consumable item, cost of computer, software, cost of system analyst and programmers, cost of material, cost of designing & cost of training analyst and user & indirect costs are phoning charges, land charge.
Benefits can be broadly classified as Tangible benefit & Intangible benefits. Tangible benefits are directly measurable. These are as a: inventories, delays in collecting outstanding payments, wastage. Intangible benefits are better service of production, accurate, reliable and up to date strategic, tactical and operational information. Operational Feasibility:This Feasibility is mainly related to human, organization and political aspects. Our project operationally feasible due to following: The existing manual work of showroom will be computerized Being a ASP.NET GUI & CUI based interface the system developed will be user friendly. Legal Feasibility:The project is legally feasible as it does not violate any law and also provides essential help to the showroom. This project is mainly based on payroll and employee information system. Time Feasibility:This determines that the proposed project can be implemented within the stipulated time frame; in this case it is three months. From the PERT chart of the proposed project it is clear that three months is sufficient enough to complete this project, hence project to be considered. (B )Cost and Benefit Analysis:1) Cost Analysis:Cost plays an important role in deciding the application. Therefore, it must be identified and estimated properly.
I. Tangible Cost: - It refers to the ease with which costs can be measured. It
includes the purpose of new hardware or software, personal training and payment against any bill- related project, compiler, other needed software and secondary disk manual for the user.
II. Intangible Cost: - Cost that may be known to exist but whose financial
values can be measured like the customer and the user or employee specification, already existing set up and the facility costs.
III. Cost of Project: - The cost estimation is none, since the application
development has been undertaken as a project work for academic purpose. 2) Benefit Analysis:Benefits are also of different types and grouped on the basis of advantages they provide to the management.
I. Tangible Costs: - These benefits include job completion within few hours
or producing report more accurately without error. Least paperwork and maintenance of record for longer time are included in this.
II. Intangible Costs: - This include more satisfied employee, improved
corporate image. Faster work initiates employers to work more efficiently. Overall satisfying organization or showroom from the project is the main purpose.
E). DATABASE NAME: GREENLAND.dbf Account (Table: account)
Column Name Employee ID Employee Name Salary Incentive Remark Data Type varchar char numeric char char Size Allow Nulls 10 30 No No
9 Yes 9 Yes 100 No
Daily Attendance (Table: daily)
Column Name Employee ID Employee Name Designation Department Time In Time Out D_date Remark Data Type Varchar Char Char Char Datetime Datetime Datetime Char Size Allow Nulls 10 30 30 30 8 8 8 30 No No No No Yes Yes Yes No
Login (Table: login)
Column Name Employee ID LoginName Password Type Data Type varchar varchar numeric char Size Allow Nulls 10 30 9 20 No No No No
Work Experience (Table: experience)
Column Name Employee ID Employee Name TotalYear Org Post Period of Employement Job Profile Employer Remark Data Type varchar Char Int Char Char Int Char Char Char Size Allow Nulls 10 30 4 30 30 4 30 30 100 No No Yes Yes Yes Yes Yes Yes Yes
Monthly Salary (Table: monthly_sal)
Column Name Employee ID Employee Name Designation Days Gross Salary Amt Payable Advance Mobile Due Remark
Data Type Varchar Char Char Numeric Numeric Numeric Numeric Numeric Char
Size Allow Nulls 10 No 30 30 9 9 9 9 9 100 No No Yes Yes Yes Yes Yes Yes
Monthly Attendance (Table: monthly attendance)
Column Name Employee ID Employee Name Days in Month Days Present Off Availed Paid Holiday Absentees Total Days Payable Date Remark Data Type Varchar Char Numeric Numeric Numeric Numeric Numeric Numeric Numeric Char Size Allow Nulls 10 30 9 9 9 9 9 9 9 100 No No No Yes Yes No Yes No Yes No
Qualification (Table: qualification)
Data Type Employee ID Varchar Employee Name Char Name of Exam Char University/Board Char Year of Passing Numeric Stream Char
Size Allow Nulls 10 30 30 30 9 30 No No Yes Yes Yes Yes
Personal Information (Table: master)
Column Name Employee ID Employee Name Designation Department Salary Date of Birth Date of Joining Allowances Father’s/Husband’s Name Sex Marital Status Blood Group Age Permanent Address Phone no Present Address Phone no. Mobile no Email id Remark Data Type Varchar Char Char Char Numeric Datetime Datetime Numeric Char Char Char Char Numeric Char Numeric Char Numeric Numeric Varchar Char Size Allow Nulls 10 30 30 30 9 8 8 9 30 10 20 20 9 100 9 100 9 9 100 100 No No No No Yes No No Yes No No No Yes No No Yes Yes Yes Yes Yes No
Special information (Table: special)
Column Name Employee ID Employee Name Name Mobile no Address Remark
Data Type varchar char char 9 char char
Size 10 30 30 30 100 100
Allow Nulls No No No Yes No No
Interview (Table: interview)
Column Name Employee Name [Date of Interview] Interviewed By Date of Joining Designation Department
Data Type Char datetime Char datetime Char Char
Size 30 8 30 8 30 30
Allow Nulls No No No No Yes Yes
References (Table: reference)
Column Name Employee ID Employee Name Name1 Name2 Designation1 Designation2 Address1 Address2 Mobile no1 Mobile no2 Remark1 Remark2
Data Type varchr char char char char char char char numeric numeric char char
Size Allow Nulls Description 10 30 30 30 30 30 100 100 9 9 100 100 No No No No No No No No Yes Yes No No Employee ID Employee Name First Reference Name Second Reference Name Designation of reference1 Designation of reference2 Reference address1 Reference address2 Reference mobile no1 Reference mobile no2 Reference remark1 Reference remark2
F).Structure Chart: -
The documentation tool for structure design is the Hierarchy or Structure Chart. It is a graphical tool for representing hierarchy. They are used to specify the high-level design, or architecture of a computer program. As a design tool, they add the programmer in dividing and conquering a large software problem that is recursively breaking a problem down into parts that are small enough to be understood by a human brain. The process is called Topdown Design or Functional Decomposition. The first step in creating a structure is to place Class: Main in the root of an upside-down tree, which forms the structure chart. The next step is to conceptualize the main sub-tasks that must be performed by the program to solve the problem. These sub-tasks are placed in nodes below the roots and connecting lines are drawn from the root to each sub-task. Next, each sub-task is individually focused and conceptualized how each subtask can be broken down into even smaller tasks. Eventually, the program is broken down to a point where the leaves of the tree represent simple methods that can be coded with just a few program statements. Branches of the tree are assigned as Modules, which are then programmed. Often a process called Bottom-up implementation and testing is used to implement each module. Each node in the chart represents a method (in Object Oriented terms, a method). The root node represents the main method of the program. Each connecting lines are labeled with the parameters of the method represented by the lower node.
A structure chart is a high-level design notation and leaves some coding details unspecified. Specifically, control structure for iteration (E.g. for while) and selection (if-then-else-end if) are not depicted in a structure chart. The chart only shows the calling sequence of a program and its parameter information. Rectangle represents a module, connection represented by a line.
Online Employee Information System & Payroll System Login Employee Login Personal Information Work Experience
H. R. Login
Add/Update Information Personal Information Work Experience Special Information Qualification Monthly Salary Leave Salary Detail Daily Attendance
View All Information Master Record Attendance Daily Attendance Monthly Attendance Work Experience Salary Detail Qualification
Special Inform Qualification Salary Detail Attendance
Daily Attenda Monthly Attendance
Structure Chart for Online Employee Information & Payroll System
Project Evaluation & Review Technique:The complexities of the present day management problems and the business competitions have added to the brains of the decision makers. In a large & complex project involving a number of integrated activities, requirement a number of men, machine & materials, it is not possible for the management to take & execute an optimum schedule just by intuition based on the organizational capabilities & work experience. Management, are thus, always on a look out for some methods & technique which may help in planning scheduling & controlling the project. A project may be defined as a combination of integrated activities, which must be executed in a certain order before the entire task can be completed. The aim of planning is to develop a sequence of activities of the project, so that the project completion time & cost are properly balanced & that the excessive demand of key resources is avoided. To meet the object of systematic planning, the management has evolved a number of techniques applying network strategy. PERT is one of the many network techniques, which have been widely used for planning, scheduling & controlling the large & complex projects.
Graph representation of PERT
Serial No. 1 2 4 6 9 10 11 12 13
Activity Information Gathering Analysis of existing System H/W & S/W Requirement Study System Analysis System design Coding Testing & validation Implementation System security
Immediate Processors Compilation Time (Working days) A 15 B D F I J K L M 15 5 15 15 15 15 5 5
D/15 C/5 A/15 1 2 B/15 3 4
E/15 6 F/15 7
Network Diagram of PERT
In prototyping, a prototype or model based on the gathered requirements is prepared. It is then evaluated by the user and is used to define requirements for the software to be developed. Iterations occur as the prototype is tuned to satisfy the needs of the customer, at the same time enabling the developer to better understand what needs to be done. If prototyping is used, the changed requirements are known by the developers at every iteration. Since information collection is done at each iteration, new or changed requirements are updated every time.
When the final prototype is ready, what do we do with it? We can do two things: • The prototype can be used as it is since it is actually a fully working model. • The prototype can be partially or fully reconstructed. This is done to suit the needs of implementing on a specific platform, environment etc.
Identify user requirement
Analyze prototype input, processing, and output
Revise through iterative Process
Phases of Prototype Model
P L A T F O R M REQUIREMENTS :-
• • •
• • •
Microprocessor RAM MEMORY MOUSE KEYBOARD Printer Monitor
: 32 bit, 350 MHz : 256 MB : 600 MB : PS/2/Scroll : 101 key standard. : Dot Matrix Printer. : VGA 15``Colour
FOR DEVELOPMENT WORK:• Microprocessor : 64 bit, 2.66 GB • RAM : 1 GB • MEMORY : 80 BG • MOUSE : Optical • KEYBOARD : 104 key standard. • Printer : Laser Printer. • Monitor : LCD or Compatible SOFTWARE
P L A T F O R M REQUIREMENTS :: : : : : Windows XP ASP.NET VB.NET SQL Server. MS Internet Explorer
• • •
OPERATING SYSTEM PLATEFORM USED FRONT END BACKEND Web Browser
System Development Life Cycle:(SDLC)
The development of an information system is a process with various stages. Actually, the development process is a cycle, which rotates around. System Development Life Cycle has 6 stages:-
1. Problem Definition 2. Feasibility Study 3. System Design 4. Implementation 5. Maintenance 6. Post – implementation One must progress from one stage to another methodically, answering key questions and achieving result in each stage. The life cycle activities are isolated and sequenced, but in real life they overlap and are highly interrelated. They can be an overlap during any phase of the cycle.
Describe detail description Phases of SDLC
1).Problem Definition: One must know what the problem is before it can be solved. Preliminary system survey or initial investigation to determine whether an alternative system can
solve the problem. It entails working into the duplication of efforts, existing procedures, whether parts of existing system would be candidate for computerization. 2). Feasibility Study: Depending on the results of the initial investigation, the survey is expanded to a more detailed feasibility study. A feasibility study is a test of system proposal according to its workability, impact on the organization, ability to meet user needs and effective use of resources. It focuses on three major questions: What are the users’s demonstrated needs and how does a candidate system meet them? What resources are available for a given candidate system? Is the problem worth solving? What are the likely impacts of the candidate system on the organization? How well does it fit within the organization MIS plan? The objective of the feasibility study is not to solve the problem but to acquire a range of its scope. The result of the feasibility study is a formal proposal. This is simply a report – a formal document detailing the nature and scope of the proposed solution. 3). System Design: The most creative and challenging phase of the system life cycle is system design. The term design describes a final system and process by which it is developed. It refers to the technical specifications that will be applied in implementing the candidate system. It also includes the construction of programmes and programme testing. The key question here is: How should the problem is solved? The first step is to determine how the output is to be produced and in which format. Sample of output are also presented. Second, input data and master files (database) have to be designed to meet the requirements of the proposed output. The operational phases are handled through programme construction and testing, including a list of programmes needed to meet the systems objectives and complete documentation. Projected cost must be close to actual cost of implementation.
4). Implementation: The implementation phase isles creative than system design. It is primarily concerned with user training, site preparation and file conversion. When the candidate system is linked to terminal or remote sites, the telecommunication network and tests of network along with the system are also included under implementation. Programming provides a reality test for the assumption made by the analyst. It is therefore a mistake to exclude programmers from the initial investigation design. System testing checks the readiness and accuracy of the system to access update and retrieve data from new files. Once the programmers become available, test data are read into computer and processed against the files provided for testing. In most conversions, a parallel run is conducted where the new system runs simultaneously with the old system. This system provides opportunity to the staff to work with the new system as well as old system. In some cases it is not possible to run parallel systems. After the new system proves itself, the old system is phased out. 5). Maintenance: There is an ageing process in software that requires periodic maintenance of hardware and software. If the new information is inconsistent with design specifications, then changes have to be made. Hardware also requires periodic maintenance to be in tune with design specifications. The important of maintenance is to continue to bring the new system to standards. User priorities, changes in organizational or environmental factors also call for system enhancements. 6). Post – Implementation: Every system requires periodic evaluation after implementation. The post – implementation measures the system’s performance against predefined requirements. Unlike system testing, which determines where the system fails, so the necessary adjustments can be made, post –implementation determines how well the system continues to meet performance specification.
A post- implementation is a review is an evaluation of the system in terms of the extent to which a system accomplishes stated objectives and actual project cost exceeds initial estimates.
A).Entity Relationship Diagram
When we design a database for a system, we should first design the entity relationship diagram. It is a diagrammatic representation of what data can be attributed to an entity and what various relationships may be shared between entities. The Entity-Relationship model for data uses 3 features to describe data, these are:Entity: Entity is anything in a system, which may be attributed by a set of attributes that define the characteristic of the entity and specify distinct real world items in an application.
Relationships:It connects entities and represent meaningful dependencies between them. Entities do not exist independently: they depend on each other. They relate to each other. (Relationship)
Attribute: Attribute, which specify properties of entities and relationship. HR Executive manages details of all employees. For Example: - HR Executive and Employees are the entities. The details such as Attendence details, Master details, Salary details, Account details, Special information is also entities. An employee can access all details. The act of accessing details defines a relationship between an employee and details. An entity set is a collection of similar entities. Each member of an entity set is described by some Attributes. For Example -An employee may be described by the attributes – Employee ID, Employee Name, Department, and Designation, DOJ, Salary etc.n
Login Employee ID
Department Designation DOJ DOB
Employee Takes Information Takes Information Access Net Paid Employee name Employee ID Advance Designation Gross Salary Balance Salary Detail Amount Payable Mobile Due
Total day In Month Emp_ID
Total day Present
Da pa Attendance Detail
LG name Employee ID DOB
LG Address LG Mobile no. Remark Special Information
B ). ata Flow Diagram D
A DFD, also known as a “bubble chart”, serves the purpose of clarifying system requirements and identifying major transformations that will become programmes in system design. So it is the starting point of the design phase that functionally decomposes the requirements specifications down to the level of detail. The DFD is a representation of various processes and the input and output in each process. Further it also represents the various data stores. Symbol Used in DFD’s: A square defines a source or a destination of system data. (External entity)
An arrow identifies data flow – data in motion. It is a pipeline through which information flows. A circle or a bubble (oval bubble) represents process that transforms incoming data flow(s) into outgoing data flow(s).
An open rectangle is a data stores – data at rest – or a temporary repository of data.
Context diagram: - The context diagram is the top level DFD. It represents a system as a single process with only major inputs and outputs to the system represented as data flows. The source and destination of the data as external entities are also represented. Level 1 and Higher Level DFD: - when we explode the context diagram and break the single process into a number of detailed processes, then level 1 DFD is created. The numbering convention in the DFD is as follows:• In the Context diagram, no number is given to processes as only one process exists. • In the level 1 DFD, the processes are numbered as 1, 2, and 3. • In the next level, the processes are numbered depending on which process has been broken. If process 2 of the level 1 DFD is broken, the processes are numbered as 2.1, 2.2 and so on. • The processes are numbered as 3.2.1, 22.214.171.124 and so on as further levels of DFD are created.
First Level DFD for H. R.
H.R. Executive Enter username, Password
2 Master For adding Record
Master Detail Leaved Detail
3 Salary Detail
Maintain daily Attendance
4 Attend ances Detail
5 Logout Logout
2. First Level DFD for Employee
1 Employee Enter username, Password Login
Authorized user Login
Request for access own record
2 Master Record
Retrieve master record Master Detail
3 Access own salary detail Salary
Retrieve account information Accounts Detail
Access own Attendance detail
4 Attenda nce Detail
Only Access his/her record Attendance Detail
Flow chart is a diagrammatic representation of a system with processes specifically. The flow chart is a tool which diagrammatically represents the logic of a procedure. It uses predefined symbols for decision making, flow of process and input, output, etc.
Decision Box Process Start/Stop Box
Off Page Connectors
1 FLOW CHART FOR LOGIN !!1.
START Login Input Login Name, Password,Type
If Tries>2 ?
If Login ? Yes
If Type=HR ? No Display Employee Window
Display HR Window
2. FLOW CHART TO SEARCH RECORD
If Connection Open ? Yes Input Employee ID
If ID found ?
Record Not Found
Display All Records
3. FLOW CHART TO DELETE RECORD
If Connection Open ? Yes Input Employee ID
If ID found ?
Record Not Found
Net Net Payable= Amount Amount Rounded off =Net Mobile Calculate Net Deduction, NET Amount= Net present, Input START 4. FLOW CHARTInputBalance,Payable - Balance AMOUNT TO GS, days CALCULATE GS/days in month*days due -Advance - Amount in month present Deduction + Mobile due Days
5. FLOW CHART TO INSERT RECORD
If Connection Open ? Yes Input Fields
Display Error Message If Validation OK ? Yes Record Successfully Added
Testing:The purpose of testing is to identify and correct errors in the candidate system. As important as this phase is it is one that is frequently compromised. Testing is vital to the success of the system. System testing makes a logical assumption that if all part of the system is correct the goal will be successfully achieved. Inadequate testing or no testing leads to errors that may not appear until months later. A small system error can explode into a much large problem. Effective testing early in the process translate directly into long-term cost saving from a reduce number of errors. This software is tested module by module; the relationship between modules and the software is validated against preset objectives. Black box testing or fundamental testing has been used in testing phase of this project. In this, the structure of the program is considered. Test cases are decided solely on the basis of the requirements or specifications of the program or module and the internals of the modules or the program are considered for selection of the test cases.
Levels of Testing: In this software mainly three types of testing is used: -
S y stem testin g starts b y testing program individually. A program m odule m ay w ork perfectly m ay fail w h en in terfaced w ith o th er m odules.T he approach is to test each entity w ith successively larg system testin g co nsist o f fo llo w ing steps: • • • • U n it testin g In teg ratio n testin g S y stem testin g A ccep tan ce testin g
1 .U n it testin g :
A n in div id u al p ro g ram m ust com pile and test data correctly and also bond w ith other program S atisfacto ry .p ro g ram testin g checks for tw o type oftax logical syn errors: and . A sy n ta x r in p ro g ram occurs w hen a statem ent in a program breaks one or m ore rules of th erro w h itch it is co ded .co m m o n syntax errors include an im properly define field dim ension or om m
A logical errors deal with invalid data fields, out-of-range items and other incorrect data combination. Since logical error is not detected by the system, the programmer must carefully study the output for finding the same. 2.In teg ra tio n testin g : In th is ty p e o f testin g all co nstituent program s should w ork properly.program are invariably an o th er an d in teract w ith th e other system .each program is tested as a com b ined m anner.each S y stem is tested again st th e entire m odule w ith both artificial and real data. 3 .S y stem testin g : S y stem testin g is d o n e to find out those im perfection that w ere not found in tests conduct e T h is inclu d e fo rced system failure and validation of total system as it w ill b e put to use by its In the actu al w o rk in g en v iro n m ent. T h e sy stem is also tested fo r backup and recovery procedure . 4 .A ccep ta n ce testin g :
T h is testin g in v o lv es ru n n in g the system w ith live data by actual user. T his is done to fam ili T h e v alid ity an d reliab ility o f the system .A s user m otivation and know ledge are im portant fo P erfo rm an ce an d im p lem en tation of the system .T he significance of user acceptance testing ca A co m p reh ensiv e test rep o rt is prepred after testing.T his report is tested the system s tolerance ran g e ,erro r rate accu racy .
1) Unit Testing
Test cases: Test case1: Module: Login dialog box Condition: If H. R. Executive login Input data: Login Name, Password, login as and click on Sign in. Output: If correct password is given then continue and all menus are enable for H. R. Executive Result: Successful
Test case2: Module: Login dialog box Condition: If Employee login Input data: Login Name, Password, Login as and click on Sign in. Output: If correct password is given then continue and few menus are disabling for Employee Result: Successful
Test case3: Module: Add Employee (Only for H.R. Executive) Condition: If new Employee Input Data: click on Personal Information and then entered the Employee_ID and filled up correctly other details and clicked on Save. Output: records get saved in Master Record and display message “Record Successfully Added”. Test result: Successful
Test case4: Module: Add Employee (Only for H.R. Executive) Condition: If Repeated Employee Input Data: click on Personal Information and then entered the existing Employee_ID or didn’t fill up mandatory fields and clicked on save. Output: Record will not save in master table and display error message “Record already exists” or “Could not found database”. Test result: Successful
Test case5: Module: Search Employee Information Condition: If record exists Input Data: click on Add/Update Employee and then entered the existing Employee_ID and click on Search. Output: Record Found. Test result: Successful
Test case6: Module: Search Employee Information Condition: If record does not exists Input Data: click on Add/Update Employee and then entered the Employee_ID and click on Search. Output: Record Not Found. Test result: Successful
Test case7: Module: To view all Employee Information in grid (Only for H.R. Executive) Condition: None Input Data: Select all fields from table. Output: Display all information. Test result: Successful
Module: To view a single Employee Information in Textbox (Only for Employee) Condition: If Employee ID matches through a Session only. Input Data: Select all fields from table. Output: Display all information corresponding their ID. Test result: Successful
Test case9: Module: To Update Employee Information (Only for H.R.) Condition: If Employee ID matches. Input Data: Fill those fields to which H.R. wants to change records and click on Update. Output: Records are updates and display message “Record Successfully Updated”. Test result: Successful
Test case10: Module: To Delete Employee Information (Only for H.R.) Condition: If Employee ID matches. Input Data: Click on Delete. Output: Records are deleted and display message “Record Deleted”. Test result: Successful
System Maintenance and Evaluation This project “Online Employee Information System and Payroll System” is developed using concept, logics and analysis of manual working process, which is easy to understand. The data stored using the software package is much more accurate and reliable since it is developed, keeping all security constraint in mind. The software package uses user-friendly interface. A person with only the ability to interact with the computer system, using the Keyboard can easily interact with the system with a little prior explanation. Flexibility of the software has also been kept in mind to provide maintainability. Maintenance Process: To make the maintenance process easy and effective, properly produced and maintained system documentation is provided. These documents are: A document describes the overall system architecture. For each component, specification and design description. Program source code listings are commented. Validation document describing how each program is validated and how the validation information relates to the requirement.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.