Epack Report MANI

Embed Size (px)

Citation preview

  • 8/3/2019 Epack Report MANI

    1/21

    PROJECT REPORT

    ON

    E-PACK

    INTERACTIVE NAVIGATIONS online services pvt ltd.

    Submitted By:-

    MANISHA MANI

    Registration no:-10803747

    Programme &Section :- B.Tech (IT) K38T2A11

    Under The Guidance Of

    External Faculty Coordinator Internal Faculty Coordinator

    Mr. Kanhaiya Miss.Neha Tewari

    Department of

    Lovely Institute Technology

  • 8/3/2019 Epack Report MANI

    2/21

    JulyDecember2011

  • 8/3/2019 Epack Report MANI

    3/21

    DECLARATION

    I hereby declare that the project work entitled (E-pack) is an authentic record of my own

    work carried out at Interactive navigations online services Pvt. Ltd. as requirements of

    Industry Internship project for the award of degree of B.Tech(IT) from Lovely Professional

    University, Phagwara, under the guidance of Mr.Kanhaiya (Industry Co-Ordinator) and Miss

    Neha Tewari (Internal Faculty Co-Ordinator), during July to December 2011).

    (Signature of student) Name of Student

    Registration no:

    Date:

    Certified that the above statement made by the student is correct to the best of our

    knowledge and belief.

    (Name & Designation) (Name & Designation)

    Faculty Coordinator Industry Coordinator

  • 8/3/2019 Epack Report MANI

    4/21

    INDEX

    1. Organization Overview..

    2. Profile of the Problem

    3. Existing System

    3.1 Introduction

    3.2 Existing Software

    3.3 DFD for present system

    3.4 Whats new in the system to be developed

    4. Problem Analysis..

    4.1 Product definition

    4.2 Feasibility Analysis

    4.3 Project Plan

    5. Software Requirement Analysis

    5.1 Introduction

    5.2 General Description

    5.3 Specific Requirements

    6. Design

    6.1 System Design

    6.2 Design Notations

    6.3 Detailed Design

    6.4 Flowcharts

    6.5 Pseudo code

  • 8/3/2019 Epack Report MANI

    5/21

    1. Organization Overview

    ABOUT COMPANY

    Interactive navigations Online services pvt ltd, is a successful 21st century

    business is a customer centered institution, unconstrained by time and place, that

    operates simultaneously, in a local and global context, constantly measuring and

    communicating its progress, and continually renewing its commitment to

    customers, community, and the economic competitiveness of the country.

    InOnline is a wholly owned subsidiary of Interactive Navigations Online Services

    Pvt .Ltd., the company is headquartered in Noida. In online helps organizations

    large and small, corporate and public, Indian and global to thrive through the

    provision of IT services. IN also operates in the residential and Internet portalmarkets, offering a full suite of innovative services to consumers, from Domain

    name registration, Web-hosting, Web Architect, to Online shopping and consultancy

    services.

    COMPANY TECHNOLOGIES

    OPEN SOURCE

    PHP

    MY SQL

    HTML/ CSS

    WEB 2.0

    JAVASCRIPT

    DHTML

    GRAPHIC DESIGN

    ADOBE PHOTOSHOP

    ADOBE FLASH DESIGN

  • 8/3/2019 Epack Report MANI

    6/21

    2. Profile of the Problem

    E-PACKis a project of polymer company enterprise. The goal of this project is to automate the syste

    for the users to understand and anticipate the needs of current customers as well as new customers.

    E-pack is a strategy to connect to the customers and learn more about the needs of the custome

    to develop stronger relationships with them. After all, good customer relationships are the heart

    business success. E-pack is a way to know deeply about the company and its products. It is away

    register and look after the further processing of the needs of the current customers. E-pack keeps th

    database and records of the customer.

    3. Existing System

    3.1) Introduction:- The existing system is about the E-pack that is the all the records are maintaine

    in the excel sheets. The orders placed are manually and are handled manually. It is as a process that w

    help bring together lots of pieces of information about customers, sales, marketing effectivene

    responsiveness and market trends.

    3.2) Existing Software:- There is no existing software for the present system.Everything

    maintained in the excel sheet and manual work is being carried out.To bring efficiency and productiv

    for the organizations business process the new software is to be developed and the process is bei

    Computerized.Draw backs of the present system are as follows:

    Low Functionality

    Erroneous Input/Output

    Manual Errors

    Portability

    Security

    Speed

  • 8/3/2019 Epack Report MANI

    7/21

    3.3) DFD for present system

    There is no DFD for the Present System.The DFD is made for the New System.

    3.4) Whats new in the system to be developed

    The whole system will be new and computerized version of the Customer Relationship Management whic

    is till now carried out manually and all the transactions and other records are maintained on the exc

    sheets.The new system will be :

    User-Friendly

    Secured

    Free from errors

    Portable

    Cost-Efficient

    4. Problem Analysis

    4.1) Product definition

    E-pack, is a large class of software programs essentially designed to help businesses manage their custom

    information and for making it easier for the customers to connect.

    This program also track sales opportunities, review all related correspondence and events, and report on t

    sales pipeline and related data. E-pack makes up the third group and provides all the abilities for tracki

    invoices, integrating accounting, organizing order information, and more.

    Also,E-pack Software typically provides the ability to track and organize every aspect of a relationsh

    with a customer from the point of first identification as a lead through and beyond the point that they are

  • 8/3/2019 Epack Report MANI

    8/21

    ongoing customer.

    4.2) Feasibility Analysis

    In the world there exists both the problem and solution. There exist one or many solutions to a single

    many problems. One solution may be given for many problems or there may be many solution of

    problem. Here we have to make a choice. Choice is to get the most practical solution to a given proble

    domain. One solution may be cost effective but it may not be feasible with respect to technicalities or

    may raise some legal difficulties or it may be unethical and cause social problems. Therefore befo

    choosing a solution there must be a complete study of the problem and the given solutions.

    The feasibility study seeks to cover all the aspects of choosing a proper solution to a given proble

    domain. This study explores all the economic, technical as well as legal domains to find the best possib

    solution.

    Feasibility study is broadly divided into four categories. The main categories are:

    Economic Feasibility

    Technical Feasibility

    Legal Feasibility

    Social Feasibility

    Economic Feasibility

    The first and foremost for any project undertaking is that it should be economically feasible for any proje

    undertaking is that it should be economically feasible. Any project primarily, is undertaken to improefficiency and to bring down the cost. If the new project promises to be economically feasible and satisfi

    other feasibility criteria, then the given solution can be implemented and further steps may be initiated.

    Facts:-

  • 8/3/2019 Epack Report MANI

    9/21

    In this project after considering different alternative we have come to the conclusion that providing

    effective GUI with automated database management system will be ideal and lead to great savings in co

    and improving efficiency.In case of E-pack the company has to maintain large amount of manpowe

    money and time resources. Huge amount of money can be saved if this system is automated.

    Technical Feasibility

    This type of feasibility study is under taken to find whether the given solution is possible to implement in

    given geological knowledge, technical knowledge and the available skilled manpower. In this study first

    all technical information and equipment must be available. Then there must be skilled manpower to hand

    the technical aspect and the physical location where the equipment will be installed and from where t

    manpower will work.

    Facts:-

    Manpower is available to handle these. This solution can be provided from any since it does not cause a

    water or noise pollution. Also there is no huge machinery to be permanently fixed.

    Social Feasibility

    This feasibility study is carried out to find whether the given solution will give rise to any social unrest

    is it unnecessarily creates problems to others in the same business.It may give rise to monopolistic situatio

    then given solution may not be implemented.

    Facts:-

    The given solution does not raise such social problems. Our solution will lead to hiring of more persons

    complete the job and it does not raise any monopolistic solutions, since technology is available to all.

    Legal Feasibility

    The feasibility study is undertaken to find out whether the given solution breaches any law of the land fro

    whether it will be controlled. This study tries to find out any given solution or the transaction through th

    solution may not arise any legal breaches.

    Facts:-

  • 8/3/2019 Epack Report MANI

    10/21

    Our solution does not breach legal law of land.

    5. Software Requirement Analysis

    5.1) Introduction

    The introduction of the Software Requirements Specification (SRS) provides an overview of the entire SR

    with purpose, scope, definitions, acronyms, abbreviations, references and overview of the SRS. The aim

    this document is to gather and analyze and give an in-depth insight of the complete E-packby defining t

    problem statement in detail.

    It also concentrates on the capabilities required by stakeholders and their needs while defining high-lev

    product features.

    Purpose

    The purpose of the document is to collect and analyze all assorted ideas that have come up to define th

    system, its requirements with respect to consumers. Also, we shall predict and sort out how we hope th

    product will be used in order to gain a better understanding of the project, outline concepts that may b

    developed later, and document ideas that are being considered, but may be discarded as the produ

    develops. The purpose of this SRS document is to provide a detailed overview of our software product,

    parameters and goals.

    .The purpose of this project is to develop a system, which will helpful in management of customer, sale

    and complaint data effectively to manage relationship with customer effectively. Proper management

    sales data can be used for performing various type of analysis, which can be used for planning marketin

    strategies and sales planning in effective way.

    Scope

    The software is accessible by different employees of the organization with different access to data. Th

    data should be very secure because as organization is developing this system to manage good custom

    relation, this data is high confidential in development of business strategy and marketing plans. Data

    customer, product and salesman once enter in the database cannot be deleted as other tables are related

    them. Complaint should be resolve as per date of complaint and their priority. Performance Evaluation

  • 8/3/2019 Epack Report MANI

    11/21

    marketing strategy should be done time-to-time.

    5.2)General Description

    SOFTWARE ENGINEERING PARADIGM APPLIED

    Software Engineering is the establishment and use of sound engineering principles in order to

    obtain economically software that is both reliable and works efficiently on real systems. To solve actu

    problems in an industry / organizations setting We apply a development strategy that encompasses t

    process, methods, tools layers, and the generic phases. This strategy is referred to as a Process Model or

    Software Engineering Paradigm. The development model that is applied in this project is The Water F

    Model

    The WATER FALL MODEL

    This is the oldest model. It has sequence of stages output of one stage becomes input of other. Followi

    are the stages in Waterfall model: -

    System Requirement:This is initial stage of the project where end user requirements are gather

    and documented.

    System Design: In this stage detail requirements, screen layout, business rules, process diagram

    pseudo code and other documentations are prepared. This is first step in technical phase.

    Implementation:Depending on the design document actual code is written here.

    Integration and Testing:All pieces are brought together and tested. Bugs are removed in thphase.

    Acceptance, Installation and Deployment: This is final stage where Software is put

    production and runs actual business.

  • 8/3/2019 Epack Report MANI

    12/21

    Maintenance:This is least glamorous phase which runs forever. Code Changes, correction, additi

    etc are done in this phase. Waterfall is suited for low risk in areas of User Interface and performan

    requirements, but high risk in budget and schedule predictability and control. Waterfall assumes that a

    requirements can be specified in advance. But unfortunately requirement grows and changes throu

    various stages, so it needs feedback from one stage to other.

  • 8/3/2019 Epack Report MANI

    13/21

  • 8/3/2019 Epack Report MANI

    14/21

    MODULES:-

    THIS PROJECT WILL BE MADE BY DIFFERENT MODULES i.e

    Homepage:-

    In this you will find the details of the company and its profile.

    GROUP PROFILE: The detailed profile of the company and its products.

    COMPANY POLICIES: Here the vision, values and environment policy and quality policies are

    mentioned.

    PRODUCT CATALOG: Details of the product what it manufactures.

    CLIENTS: The clients of the company will be provided.

    LOGIN FORM: Here the users will login and can get access to the company details that what

    products it manufactures and record its contents into its database.

    Login page: Here one may use its email address and password to enter into the session.

    Registration page: Here user may register themselves for requesting the orders and reviewing

    orders etc.

    Register orders: one may place orders for the products.

    Review previous orders: Here the orders placed may be edited or deleted according to the need

    of the customer.

    Change passwords: The user can change password here.

    CONTACT US:- Contact Details.

    SEARCH BOX :-You can search the here and get their details throughsearch box . It is displayed in the header .

    VISITORS COUNTER: This counts the total no. of vistor visited on the site

    from last reviewed.

    ONLINE USERS: This counts the total number of users online at present.

    SCOPE OF THE PROJECT:

  • 8/3/2019 Epack Report MANI

    15/21

    The scope of the project is that it is user friendly to any non-technical and technical persons. It

    provide detailed description of the panels and the products of the company being manufactured.

    TOOLS USED IN THE PROJECT:

    1. FRONT END: Xhtml, xml, php, JavaScript, jquery slider.2. BACK END: My sql.

    5.3) Specific Requirements

    SOFTWARE REQUIREMENT

    Operating System

    Window XP.Window 7

    Platform

    php

    Front-End ->php

    Database

    Back-End--> my sql

    HARDWARE REQUIREMENTS

  • 8/3/2019 Epack Report MANI

    16/21

    The hardware requirement of the E-pack is as follows:

    Minimum RAM (Random Access Memory) should 256MB.

    Minimum Hard Disk should 40GB.

    LAN should be configured to work in a TCP/IP environment.

    The Processor speed should greater than or equal to 2.0 GHz.

    6. Design

    6.1) System Design

    Data Flow Diagram

  • 8/3/2019 Epack Report MANI

    17/21

  • 8/3/2019 Epack Report MANI

    18/21

  • 8/3/2019 Epack Report MANI

    19/21

    System Design

    High Level Design Low

    Level

    Design

    Logical Physical Class

    Design Design Diagram

    a) Logical Design

  • 8/3/2019 Epack Report MANI

    20/21

    D

    O

    MA

    I

    N

    E

    X

    CE

    P

    T

    I

    S

    E

    CU

    R

    I

    T

    b) Physical Design

  • 8/3/2019 Epack Report MANI

    21/21

    Design Notations

    The notations used in system design are as follows:-

    1.DFD NOTATIONS