A

INDUSTRIAL TRAINING REPORT

ON

Institutional ERP
(A WINDOWS APPLICATION)

BY

Shilpi ROLL No- 1003210910 B.Tech Final Year

UNDER THE GUIDANCE OF (MR. SANTOSH CHOUDHARY)

AGILE SOFTECH PVT. LTD. G-127, PATEL NAGAR III, GHAZIABAD,UP

Introduction
Title of the Project: IERP IERP is a windows Application

IERP refers as an Institutional ERP that is completely based on the Windows Application of ERP. The main focus of this application is to provide service to all types of institutes. This application is completely designed to keep all the sectors in mind of an institute. AGILE IERPS is completely Windows Compatible, fully integrated and modular Windows Application, which can run on Window. AGILE IERPS is the technologically advanced software for the implementation. AGILE IERP provides a unique and user-friendly environment, which ensures a smooth & advance searching from any data. AGILE IERPS is the comprehensive modular package, which has been carefully developed to put the search information right at fingertips of User in a logical, predictable, and easy-tounderstand manner. Existing System When the requirement of this system is putted before the team they were willing to know that how the current Application systems are working. Then the study is done it gives the result that all the work is done manually and there is nothing that help the User to save the time and do the work with the system. All the company or individual needs information about the unknown places or unknown objects. Sometimes it is very difficult to know about some special highlights, because the information is stored on the paper and it is not clear that due to human

error or by some other means this paper is lost and the information is now not in the hands of the company or individual. Proposed system: This site is an attempt to make the task of administrator as well as New Enquiry/Users/ staff easier. This project ensures the consistency by enabling the New Enquiry to register themselves and to find the desired information, get them involved with the IERP Windows Application and can access the different services provided by the ERP organization. The administrator has the right to know everything. He has the right to know the details of the New Enquiry, has the right to change any service that the site is currently providing or can add services which are not being provided currently. Even the customers passwords and hidden details are accessible by the administrator. Now New Enquiry/Users are able to apply online also. Through this system all works are done through computer so it results in fast service provider. The New Enquiry can also contact the IERP Windows Application officials through email or his contact numbers but first they have to register themselves as a member by filling up a registration form which can be filled online. Once registered, New Enquiry can access this site and register for any services being provided by sites, that too online by sitting at home within a fraction of a second by a flick of a button. Aim of this project is to provide an environment helpful for administrator and New Enquiry/Users as well, so that, they find it easy to implement it without any harassment for the New Enquiry also. This project is developed after a Through study of the existing manual system & the ERP requirements. Requirement analysis is concerned with identifying the basic function of software component in a hardware & software system.

Acknowledgement
I sincerely record here the valuable help extended to me by the staff of AGILE SOFTECH PVT. LTD Ghaziabad. All of them enthusiastically and cheerfully rendered help in my project and provided me all the necessary details.

I would like to thanks to my Instructor MR. SANTOSH CHOUDHARY who constantly help and encourage me through out of the course of development of project finally.

(Shilpi)

CERTIFICATE
This is to certify that the training report entitled: Institutional ERP done by Shilpi an authentic work carried out by her for the partial fulfillment of the requirement for the training report.

MR. SANTOSH CHOUDHARY (Instructor)

Company Profile

AGILE SOFTECH PVT. LTD. Ghaziabad was incorporated as a Private Limited Company in 2010 with the objective of providing quality service in the field of Information Technology. With registered office in Delhi, Agile Softech private limited provides superior solution and services for managing the implementation of CUSTOMIZED ERP, WINDOWS SITES, PORTAL in the all industry, serving both the domestic and international sectors .Our goal is to exceed the expectations of every client by offering outstanding customer service, increased flexibility, and greater value, thus optimizing system functionality and improving operation efficiency. With our trained professionals we can provide top class service in such areas as Software development, Training, Windows designing & hosting, Search engine optimization, Internet services and other IT enabled services. The Company provides software products, IT services and solutions for a variety of industry verticals including College, School, Insurance, Banking, Capital Markets, Mutual Funds & Asset Management, Wealth Management, Government, Manufacturing and Retail. These solutions and services include Managed IT Services, Application Software Development & Maintenance, Business Intelligence, IT consulting and various Transaction Processing services.

OBJECTIVE OF PROJECT
WE HAVE TO DEVELOP A WINDOWS BASED APPLICATION WITH SIMPLFY FILTER AND MANAGE ALL INFORMATION OF AN INSTITUTE LIKE AS STUDENTS INFO, ENQUERY INFO, EMPLOYEE INFO, ACCOUNT, AND ETC AGILE IERP WINDOWS BASED APPLICATION

The Agile IERP: A UNIVERSAL WINDOWS APPLICATION A System is simply a set of components that interact to accomplish some purpose Systems are all around us.An AGILE IERP is also a system. Its components Are: Admin, service, finance, inventory, library, student info, employee info etc. All work together to create a profit that benefits the employees & student. Each of these components is itself a system. A College receives inputs, processes them & converts them into outputs. A key objective of an AGILE IERPS information system is to identify what managerial information is useful & to generate this information-not data. Often raw-data can be transformed into useful information. Providing the right information to the right manager at the right time in a costeffective manner typically means choosing the right system to meet informational needs. Since different managerial levels within an organization are involved in different types of decisions, their informational requirements often differ as well.

Hierarchy of Information Systems

System Development Life Cycle

LIFE CYCLE OF THE PROJECT

The methodology adopted is linear sequential model in which the requirement model in which the requirements are fixed Initially as it was fixed during the analysis phase of software to work properly and efficiently are as fallows. During the construction of the project named Institutional ERP I had used the linear sequential model which implementing the SDLC procedure. OVERVIEW OF PHASE OF SDLC Study Phase: - It is consists of four parts Need Recognition. Feasibility Analysis. Detailed System Analysis. I/O Specification and Design. Design Phase: File Design. Program Logic Design. Development Phase: Coding Debugging Testing

SYSTEM REQUIREMENT SPECIFICATION

SRS is a document that completely describes what the proposed software should do. The basic goal of requirement phase is to produce the SRS, which describe the complete behavior of proposed software.

PURPOSE The purpose of this document is to Document the different business processes of Asset and Maintenance department, in detail Document the Business requirements clearly in a concise and easily understood manner to the Business/End user. Establish the basis for agreement between the customer and the supplier Serve as a baseline for validation and verification. Serve as baseline document for development team Serve as a basis for future enhancements. Intended Audience This document is intended for business users/ end users. Users should review and approve the SRS. This could be done directly by the business users or by another interfacing layer who could act as coordinators from the Clients side who could be link between the Supplier and the business/end user. SCOPE This document covers the detailed description of the different asset management and maintenance management process. The details include Description of process. Proposed process model. Assumptions, dependencies and constraints

EXISTING PROBLEM: Todays economy makes investing a top line, revenues producing initiatives that take time to achieve a return on investment a difficult decision. Attacking expense reduction solutions that impact below the line savings are highly sought after and implemented today. Some companies seek to improve their assets uptime and availability while reducing maintenance, repair, and operational (MRO) expenses. MRO expenses are a significant part of the expenses experienced by most heavy asset companies. PROPOSED SYSTEM: IERPS SYSTEM: In modern era WINDOWS DIRECTORIES are the important part of an institute to search and filter the specific contact details. It might be the contact information of students, employee, assets, etc. Every person need contact details of lot of fields in his/her daily life. Their need can be cater through APPLICATION, but the problems with present DIRECTORIES solution is COST as well as TIME for implementation. So with this project IERPS SYSTEM we are going to develop the customized APPLICATION to cater the need of all the individuals, organization and business that will cost them very less, with less implementation time. OVERALL DESCRIPTION: PRODUCT PERSPECTIVE User interfaces: User interface (GUI Screens) would be used to provide information necessary to generate a new claim and also to update information Software interfaces: C#, ORACLE 10G ASSUMPTIONS AND DEPENDENCIES: This SRS document is based on following assumptions: The SRS document has been prepared based on the information gathered from books and during discussions with team members.

 Client side browser (Window) would be Internet Explorer 5.0 or above. The workflow application would be using some ActiveX controls, which may not be compatible with other browsers. Since we are trying to build a customizable product, the new requirement may be introduced during design phase. The outputs screens will be design in design phase Number and type of workflow queues may get further re-fined during the design phase.

SYSTEM REQUIREMENTS
For installation of the developed software the user should posses at least the following Software and Hardware.

SOFTWARE REQUIREMENTS: 1. Windows 2000 (or later version) operating system. 2. Visual Studio .NET 3. ORACLE 10G

HARDWARE REQUIREMENTS: 1. 2. 3. 4. 5. 6. 7. 8. 1GB of RAM for DEVELOPER PC P IV or higher processor. VGA (640*480) or higher resolution screen. 40 GB of hard disk space. Keyboard Printer. 3.5 Floppy Drive. CD-ROM Drive.

SYSTEM DESIGN
INTRODUCTION: System design phase is a transition from user-oriented document (system proposal) to a document oriented to programmers or database personnel. This is the pivotal point in system development life cycle. The design is a solution, a How to approach, compared to analysis, a What is orientation. The design phase focuses on the detailed implementation of the system recommended in the feasibility study. Emphasis is on translating performance specifications into design specifications. System design is carried out mainly in two phases Logical and Physical design. 1. LOGICAL DESIGN: For a candidate system Data Flow Diagram describes the inputs (source), outputs (destination), database (data stores), and procedures (data flows) all in a format which meets the user requirements. The Logical system design mainly concentrates on the user needs on various levels of detail that determines the information flow and the required data resources. The design covers the following: REVIEWS THE CURRENT PHYSICAL SYSTEM: This consists of specifying Data Flows, File Content, Volumes, Frequencies, etc. PREPARES THE OUTPUT SPECIFICATIONS: This process determines the format, content, and frequency of reports, including terminal specifications and locations. PREPARES INPUT SPECIFICATIONS: By this process the input format, content and most of the input functions are specified. This includes the flow of the documents from the input data source to the actual input location.

PREPARES EDIT, SECURITY, AND CONTROL SPECIFICATIONS: This includes specifying the rules for edit correction, backup procedures, and the controls that ensure processing and file integrity. SPECIFIES THE IMPLEMENTATION PLAN AND BENEFITS: This includes cost evaluation process, target dates, benefits from the system, and system constraints 2. PHYSICAL DESIGN: This phase produces the working system by defining the design specifications that tell programmers exactly what the system must do, performs the necessary calculations through the existing file or database, produces the report on hard copy or displays it on a screen. Physical design consists of the following: > Design the physical system 1. Specifying Input Output media. 2. Design the database and specify backup procedures. 3. Design Physical Information flow through the system. >Plan system implementation: 1. Prepare a conversion schedule and a target date. 2. Determine training procedure, courses, and timetable. 3. OBJECTIVES OF THE DESIGN: Whenever an old system fails or dont work up to its specification a new set of objectives has to be achieved and new procedures have to be selected and implemented. The following points were kept in mind while designing the new system. 1. 2. 3. 4. 5. 6. 7. The system should be user friendly. Data security should be taken care of. Reduce the redundancy of data. Maintaining and updating the database easily. Should be menu driven package with one entry at a time. Data entry & on-line data editing through well laid out screen format Data validation whenever necessary to ensure correctness of input data.

CONTEXT ANALYSIS DIAGRAM 0F AGILE IERPS

STUDENT

EMPOLOYEE

IERPS

ACCOUNT ADMIN

COURSE

INFORMATION DETAILS

DATA

DATA BASE

The database and the table that were designed are as follow:

1. TBLENQUERY: Field Name ENQID NAME STREET STATE CITY PINCODE DATEOFBIRTH COURSEINTRESTED MOBILENO EMAILID TIMINGPREFERRED GENDER COLLEGE QUALIFICATION FINALSTATUS ORGANIZATION PROFESSION E_DATE DataType Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 NUMBER DATE Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 DATE 40 Not null 15 30 20 6 30 20 20 20 20 Unique Unique Width Constraint

10 Primary key 30 Not null 30 Not null 20 Not null 20 6

2. TBLCOURSE: Field Name COURSEID NAME FEE DURATION 3. TBLREGISTRATION: Field Name REGISTRATIONID NAME FATHERSNAME L_STREET DataType Varchar2 Varchar2 Varchar2 Varchar2 30 L_STATE L_CITY DATEOFBIRTH COURSEENROLLED COURSESTDATE COURSEFINISHDATE MOBILENO EMAILID P_STREET P_STATE P_CITY PINCODE Varchar2 Varchar2 DATE Varchar2 DATE DATE Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 NUMBER 30 30 20 20 6 20 Not null UNIQUE 20 20 20 Not null Width Constraint 10 Primary key 30 Not null 30 Not null DataType Varchar2 Varchar2 NUMBER Varchar2 Width Constraint

10 Primary key 20 Not null 10 Not null 10 Not null

GENDER COLLEGE QUALIFICATION FINALSTATUS ORGANIZATION PROFESSION R_DATE

Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 DATE

6 Not null 30 20 20 20 20

4. TBLINCOME: Field Name INCOMEID SOURCE AMOUNT I_DATE DataType Varchar2 Varchar2 NUMBER DATE Width Constraint

10 Primary key 20 Not null 10 Not null Not null

5. TBLEXPENSE: Field Name EXPENSEID DESCRIPTON AMOUNT EXPENSEDATE DataType Varchar2 Varchar2 NUMBER DATE Width Constraint

10 Primary key 50 Not null 10 Not null Not null

6. TBLASSEST: Field Name ASSESTID DataType Varchar2 Width Constraint 10 Primary key

ASSESTNAME TYPES UNITPRICE

Varchar2 Varchar2 NUMBER 10

20 Not null 20 Not null

QUANTITY TOTALPRICE PURCHASINGDATE COMPANY VENDORNAME VENDORCONTACTNUMBER GUARANTEEPERIOD FINALSTATUS

NUMBER NUMBER DATE Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 20 30

10 Not null 10 Not null

50

15 10 Not null

7. TBLASSEST: Field Name SNO REGISTRATIONID INSTALLMENT I_DATE AMOUNT DUEDATE DataType Varchar2 Varchar2 NUMBER DATE NUMBER DATE Width Constraint 10 Primary key 20 Not null 10 Not null 10 Not null Not null

8. TBLPAYMENT: Field Name RECIEPTID DataType NUMBER Width Constraint 10 Primary key

REGISTRATIONID NAME PDATE TOTALAMOUNT PAYEDAMOUNT PMODE TYPES TOTALREMAININGAMOUNT NEXTDEPOSITAMOUNT NEXTDUEDATE

Varchar2 Varchar2 DATE NUMBER NUMBER Varchar2 Varchar2 NUMBER NUMBER DATE 20

10 Not null 40 Not null 10 Not null 10 20 20 Not null

20 Not null

9. TBLEMPLOYEEPAYROLL: SNO EMPID ENAME BASICPAY DA VARCHAR2 VARCHAR2 VARCHAR2 NUMBER NUMBER 10 HRA OTHER TOTALSALARY NUMBER NUMBER NUMBER 10 Not null 10 Not null 10 Primary key 10 Unique 30 Not null 10 Not null Not null

10 Not null

10. TBLEMPLOYEEATTENDENCE:

SNO EMPID ENAME A_DATE INTIME

Varchar2 Varchar2 Varchar2 DATE Varchar2 15

10 Primary key 10 Unique 30 Not null Not null Not null

OUTTIME

Varchar2

15 Not null

11. TBLSTUDENTATTENDENCE: SNO REGISTRATIONID NAME A_DATE INTIME Varchar2 Varchar2 Varchar2 DATE Varchar2 15 OUTTIME COURSE FACULTY Varchar2 Varchar2 Varchar2 15 Not null 20 30 10 Primary key 10 Unique 20 Not null Not null Not null

SYSTEM TESTING

INTRODUCTION: System testing is a very much essential before actual implementation of the system. All kinds of errors and incompatibility must be removed before it is ready for user acceptance testing. If all parts of the system is correct, then only the system objectives is successfully achieved. First test of the system is to see whether it produces correct output or not. No other test can be more crucial than this. Some of the tests, which have been performed, are given below. 1.VOLUME TESTING: In this test, we create as many records as would normally be required to verify the proper functioning of the hardware and software. The user is asked to provide test data for volume testing. In the system, a huge amount of records were being tested and the test output shows that the system can hold an amount of data required by the firm. 2.STRESS TESTING: The stress testing is to provide that the system does not malfunction under peak loads. 3.RECOVERY TESTING:

A forced system failure is induced to test back-up recovery procedure for the integrating files. Inaccurate data are entered to see the system responses in terms of error deduction and production, related to file integrity. 4.UNIT TESTING: Unit testing focuses on verification efforts on the smallest unit of software designed i.e. the modules. Using the detail design description as a guide, important control paths are tested to uncover the error within the scope of the modules. The relative complexity of the test and uncovered error is limited by the constraint scope established for unit testing. The user tested each data entry screen by entering test data. Few errors and faults that were found at the time of data entry were removed. 5.INTEGRATION TESTING: Integration testing is technique for constructing the program structure while at the same time conducting the test error associated with it. The objective is to take unit-tested module and build a program structure that has been dictated by design. In this phase the user enters series of test data and tests the entire software module. As there are some relation between module the user tests the software to see whether all the relations were satisfied or not.

6.USABILITY DOCUMENTATION AND PROCEDURE: The usability test verifies the friendly nature of the system. It also tests whether an unknown user can handle the system failure or not. The crucial phase of the system life cycle is the successful implementation of the new system design into operation. This involves creating computer compatible files, training of the staff who will operate the system and installing hardware before the system is set up for running. 7. TESTING OF INDIVIDUAL PROGRAMS: Each programs completed during the programming development stage were tested at the time of coding, and necessary changes were made to make sure that the program is working properly. For example the procedure developed in the authorization module for testing user is as follows which is fired as soon as the user enters his password in the login screen of IERPs. CREATING TEST DATA Though some test data created during individual program development were not sufficient for testing the system as a whole, during the time of system testing all types of checking has been done depending upon situation by considering different sets of data.

After successful completion of the individual forms the whole system was run through a series of test, to ensure the proper working of the system as a whole. The effects of testing the entire program is to verify that the programs are working properly and according to the users need and specification that were made during the system study. USER TRAINING: No Need of user training because Windows sites is very simple and user friendly.

OUTPUT

CONCLUSION AND FUTURE SCOPES

This system is made in such a way that any organization or company, customer, Individuals can search or filter it according to their requirements. In Today scenario it is the requirements for all to get the things quickly and properly. On the basis of work: 1. This project has achieved the objective of replacing/augmenting the conventional system of arranging information as could be conducted by a typical company / customer / individuals. 2. The development of this package has been achieved by using C#, which is very conductive to develop the package with regard to time and specific need to the user. 3. This package is highly user friendly, required an optimal minimal input from user while providing highly relevant and focused outputs. 4. Fully automated, avoiding human intervention. Hence it provides a very rapid cost effective alternative to the conventional manual operation/procedures; the visual outputs are more reliable than the audio forms of manual communication. 5. The system can further extended as per user and administrative requirements.

Bibliography
Introduction to System Analysis & Design -Penny A. Kendall Software Engineering System Design & Business Application -Roger S. Pressman -V.K. Jain

Introduction to System Analysis & Design I.T. Hawryszkiewyez C# Programming C# Development Database System Concepts RDBMS design & PL/SQL - Black Book - Peter Wright - Henry F. Korth - Oracle Press