Shilpi ITR

download Shilpi ITR

of 40

Transcript of Shilpi ITR

  • 7/30/2019 Shilpi ITR

    1/40

    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

  • 7/30/2019 Shilpi ITR

    2/40

    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 toall types of institutes. This application is completely designed to keep all thesectors 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 thetechnologically advanced software for the implementation.

    AGILE IERP provides a unique and user-friendly environment, which ensures asmooth & advance searching from any data. AGILE IERPS is the comprehensivemodular package, which has been carefully developed to put the searchinformation right at fingertips of User in a logical, predictable, and easy-to-understand 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

  • 7/30/2019 Shilpi ITR

    3/40

    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 currentlyproviding 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 Enquirycan 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.

  • 7/30/2019 Shilpi ITR

    4/40

    Acknowledgement

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

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

    (Shilpi)

  • 7/30/2019 Shilpi ITR

    5/40

    CERTIFICATE

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

    MR. SANTOSH CHOUDHARY

    (Instructor)

  • 7/30/2019 Shilpi ITR

    6/40

    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 includeManaged IT Services, Application Software Development & Maintenance,

    Business Intelligence, IT consulting and various Transaction Processing

    services.

  • 7/30/2019 Shilpi ITR

    7/40

    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 cost-

    effective manner typically means choosing the right system to meet informationalneeds. Since different managerial levels within an organization are involved in

    different types of decisions, their informational requirements often differ as well.

  • 7/30/2019 Shilpi ITR

    8/40

    Hierarchy of Information Systems

  • 7/30/2019 Shilpi ITR

    9/40

    System Development Life Cycle

  • 7/30/2019 Shilpi ITR

    10/40

    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

  • 7/30/2019 Shilpi ITR

    11/40

    SYSTEM REQUIREMENT SPECIFICATION

    SRS is a document that completely describes what the proposed softwareshould 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 Maintenancedepartment, 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 shouldreview and approve the SRS. This could be done directly by the businessusers or by another interfacing layer who could act as coordinators fromthe Clients side who could be link between the Supplier and thebusiness/end user.

    SCOPE

    This document covers the detailed description of the different assetmanagement and maintenance management process. The details include Description of process. Proposed process model. Assumptions, dependencies and constraints

  • 7/30/2019 Shilpi ITR

    12/40

    EXISTING PROBLEM:

    Todays economy makes investing a top line, revenues producinginitiatives that take time to achieve a return on investment a difficultdecision. Attacking expense reduction solutions that impact below theline 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 significantpart 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 tosearch and filter the specific contact details. It might be the contact informationof 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 theproblems with present DIRECTORIES solution is COST as well as TIME for implementation. So with this project IERPS SYSTEM we are going to developthe customized APPLICATION to cater the need of all the individuals,organization and business that will cost them very less, with less implementationtime.

    OVERALL DESCRIPTION:

    PRODUCT PERSPECTIVE User interfaces:

    User interface (GUI Screens) would be used to provide informationnecessary 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 informationgathered from books and during discussions with team members.

  • 7/30/2019 Shilpi ITR

    13/40

    Client side browser (Window) would be Internet Explorer 5.0 or above. The workflow application would be using some ActiveX controls, whichmay not be compatible with other browsers.

    Since we are trying to build a customizable product, the newrequirement 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.

  • 7/30/2019 Shilpi ITR

    14/40

    SYSTEM REQUIREMENTS

    For installation of the developed software the user should posses at leastthe following Software and Hardware.

    SOFTWARE REQUIREMENTS :

    1. Windows 2000 (or later version) operating system.2. Visual Studio .NET3. ORACLE 10G

    HARDWARE REQUIREMENTS:

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

  • 7/30/2019 Shilpi ITR

    15/40

    SYSTEM DESIGN

    INTRODUCTION:

    System design phase is a transition from user-oriented document (systemproposal) to a document oriented to programmers or database personnel. This isthe pivotal point in system development life cycle. The design is a solution, aHow to approach, compared to analysis, a What is orientation.

    The design phase focuses on the detailed implementation of the systemrecommended in the feasibility study. Emphasis is on translating performancespecifications into design specifications. System design is carried out mainly intwo 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 aformat which meets the user requirements. The Logical system design mainlyconcentrates on the user needs on various levels of detail that determines theinformation flow and the required data resources. The design covers thefollowing:

    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, includingterminal specifications and locations.

    PREPARES INPUT SPECIFICATIONS:

    By this process the input format, content and most of the input functions arespecified. This includes the flow of the documents from the input data source tothe actual input location.

  • 7/30/2019 Shilpi ITR

    16/40

    PREPARES EDIT, SECURITY, AND CONTROL SPECIFICATIONS:

    This includes specifying the rules for edit correction, backup procedures, and thecontrols 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 specificationsthat tell programmers exactly what the system must do, performs the necessarycalculations 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 andimplemented. The following points were kept in mind while designing the newsystem.

    1. The system should be user friendly.2. Data security should be taken care of.3. Reduce the redundancy of data.4. Maintaining and updating the database easily.5. Should be menu driven package with one entry at a time.6. Data entry & on-line data editing through well laid out screen format7. Data validation whenever necessary to ensure correctness of input data.

  • 7/30/2019 Shilpi ITR

    17/40

    CONTEXT ANALYSIS DIAGRAM 0F AGILE IERPS

    IERPS

    STUDENT EMPOLOYEE

    ADMIN

    COURSEACCOUNT

    DATAINFORMATION

    DETAILS

  • 7/30/2019 Shilpi ITR

    18/40

    DATA BASE

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

    1. TBLENQUERY:

    Field Name DataType Width Constraint

    ENQID Varchar2 10 Primary key

    NAME Varchar2 30 Not null

    STREET Varchar2 30 Not nullSTATE Varchar2 20 Not null

    CITY Varchar2 20

    PINCODE NUMBER 6

    DATEOFBIRTH DATE

    COURSEINTRESTED Varchar2 40 Not null

    MOBILENO Varchar2 15 Unique

    EMAILID Varchar2 30 Unique

    TIMINGPREFERRED Varchar2 20

    GENDER Varchar2 6

    COLLEGE Varchar2 30

    QUALIFICATION Varchar2 20

    FINALSTATUS Varchar2 20

    ORGANIZATION Varchar2 20

    PROFESSION Varchar2 20

    E_DATE DATE

  • 7/30/2019 Shilpi ITR

    19/40

  • 7/30/2019 Shilpi ITR

    20/40

    GENDER Varchar2 6 Not null

    COLLEGE Varchar2 30

    QUALIFICATION Varchar2 20

    FINALSTATUS Varchar2 20

    ORGANIZATION Varchar2 20

    PROFESSION Varchar2 20

    R_DATE DATE

    4. TBLINCOME:

    Field Name DataType Width Constraint

    INCOMEID Varchar2 10 Primary key

    SOURCE Varchar2 20 Not null

    AMOUNT NUMBER 10 Not null

    I_DATE DATE Not null

    5. TBLEXPENSE:

    Field Name DataType Width Constraint

    EXPENSEID Varchar2 10 Primary key

    DESCRIPTON Varchar2 50 Not null

    AMOUNT NUMBER 10 Not null

    EXPENSEDATE DATE Not null

    6. TBLASSEST:

    Field Name DataType Width Constraint

    ASSESTID Varchar2 10 Primary key

  • 7/30/2019 Shilpi ITR

    21/40

    ASSESTNAME Varchar2 20 Not null

    TYPES Varchar2 20

    UNITPRICE NUMBER10

    Not null

    QUANTITY NUMBER 10 Not null

    TOTALPRICE NUMBER 10 Not null

    PURCHASINGDATE DATE

    COMPANY Varchar2 50

    VENDORNAME Varchar2 30

    VENDORCONTACTNUMBER Varchar2 15

    GUARANTEEPERIOD Varchar2 10 Not null

    FINALSTATUS Varchar2 20

    7. TBLASSEST:

    Field Name DataType Width Constraint

    SNO Varchar2 10 Primary key

    REGISTRATIONID Varchar2 20 Not null

    INSTALLMENT NUMBER 10

    I_DATE DATE Not null

    AMOUNT NUMBER 10 Not null

    DUEDATE DATE Not null

    8. TBLPAYMENT:

    Field Name DataType Width Constraint

    RECIEPTID NUMBER 10 Primary key

  • 7/30/2019 Shilpi ITR

    22/40

    REGISTRATIONID Varchar2 10 Not null

    NAME Varchar2 40

    PDATE DATE Not null

    TOTALAMOUNT NUMBER 10 Not null

    PAYEDAMOUNT NUMBER 10 Not null

    PMODE Varchar2 20

    TYPES Varchar2 20

    TOTALREMAININGAMOUNT NUMBER 20

    NEXTDEPOSITAMOUNT NUMBER 20

    NEXTDUEDATE DATE Not null

    9. TBLEMPLOYEEPAYROLL:

    SNO VARCHAR2 10 Primary key

    EMPID VARCHAR2 10 UniqueENAME VARCHAR2 30 Not null

    BASICPAY NUMBER 10 Not null

    DA NUMBER 10

    Not null

    HRA NUMBER 10 Not null

    OTHER NUMBER 10 Not null

    TOTALSALARY NUMBER 10 Not null

    10.TBLEMPLOYEEATTENDENCE:

  • 7/30/2019 Shilpi ITR

    23/40

    SNO Varchar2 10 Primary key

    EMPID Varchar2 10 Unique

    ENAME Varchar2 30 Not null

    A_DATE DATE Not null

    INTIME Varchar2 15

    Not null

    OUTTIME Varchar2 15 Not null

    11.TBLSTUDENTATTENDENCE:

    SNO Varchar2 10 Primary key

    REGISTRATIONID Varchar2 10 Unique

    NAME Varchar2 20 Not null

    A_DATE DATE Not null

    INTIME Varchar2 15

    Not null

    OUTTIME Varchar2 15 Not null

    COURSE Varchar2 20

    FACULTY Varchar2 30

  • 7/30/2019 Shilpi ITR

    24/40

    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:

  • 7/30/2019 Shilpi ITR

    25/40

    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.

  • 7/30/2019 Shilpi ITR

    26/40

    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.

  • 7/30/2019 Shilpi ITR

    27/40

    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.

  • 7/30/2019 Shilpi ITR

    28/40

    OUTPUT

  • 7/30/2019 Shilpi ITR

    29/40

  • 7/30/2019 Shilpi ITR

    30/40

  • 7/30/2019 Shilpi ITR

    31/40

  • 7/30/2019 Shilpi ITR

    32/40

  • 7/30/2019 Shilpi ITR

    33/40

  • 7/30/2019 Shilpi ITR

    34/40

  • 7/30/2019 Shilpi ITR

    35/40

  • 7/30/2019 Shilpi ITR

    36/40

  • 7/30/2019 Shilpi ITR

    37/40

  • 7/30/2019 Shilpi ITR

    38/40

  • 7/30/2019 Shilpi ITR

    39/40

    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 theirrequirements.

    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 manualoperation/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.

  • 7/30/2019 Shilpi ITR

    40/40

    Bibliography

    Introduction to System Analysis & Design -Penny A. Kendall

    Software Engineering -Roger S. Pressman

    System Design & Business Application -V.K. Jain

    Introduction to System Analysis & Design I.T. Hawryszkiewyez

    C# Programming - Black Book

    C# Development - Peter Wright

    Database System Concepts - Henry F. Korth

    RDBMS design & PL/SQL - Oracle Press