roports gate updated

8/6/2019 Roports Gate Updated

1/92

GATE PASS SYSTEM

SPB LINCH CE - 1-

1. FEASIBILITY STUDY

A feasibility study is an evaluation of a proposal designed to determine thedifficulty in carrying out a designated task. Generally, a feasibility study precedes technical

development and project implementation. In other words, a feasibility study is an evaluation or

analysis of the potential impact of a proposed project.

Before starting the process various parameters must be checked like:

y Estimated finance is there or not?y The man power to operate the system is there or not?y The man power is trained or not?

All the above conditions must be satisfied to start the project. This is why in depth analysis of

feasibility is carried out.

There are different ways feasibility can be tested

1) Technical Feasibility

2) Economical Feasibility

3) Operational Feasibility

4) Schedule feasibility5) Resource feasibility

1.1 Feasibility techniques:

Technology and system feasibility

The assessment is based on an outline design of system requirements in terms of Input,

Processes, Output, Fields, Programs, and Procedures. This can be quantified in terms of volumes

of data, trends, frequency of updating, etc. in order to estimate whether the new system will

perform adequately or not. Technological feasibility is carried out to determine whether the

company has the capability, in terms of software, hardware, personnel and expertise, to handle

the completion of the project.


2/92

GATE PASS SYSTEM

SPB LINCH CE - 2-

y This project is technologically feasible because all the softwares, hardwares andpersonnel were present at the point of time it required.

1.2 Economic feasibility

Economic analysis is the most frequently used method for evaluating the effectiveness of a new

system. More commonly known as cost/benefit analysis, the procedure is to determine the

benefits and savings that are expected from a candidate system and compare them with costs.

If benefits outweigh costs, then the decision is made to design and implement the system. An

entrepreneur must accurately weigh the cost versus benefits before taking an action.

Cost Based Study: It is important to identify cost and benefit factors, which can be categorized as

follows: 1. Development costs; and 2. Operating costs. This is an analysis of the costs to be

incurred in the system and the benefits derivable out of the system.

Time Based Study: This is an analysis of the time required to achieve a return on investments.

The benefits derived from the system. The future value of a project is also a factor.

y This project is made after completion of all cost and time analysis. Its benefits outweighcost and it is completed within the time period which was estimated before and that is why

it is economically feasible.

1.3 Schedule feasibility

A project will fail if it takes too long to be completed before it is useful. Typically this means

estimating how long the system will take to develop, and if it can be completed in a given time

period using some methods like payback period. Schedule feasibility is a measure of how

reasonable the project timetable is. Given our technical expertise, are the project deadlines

reasonable? Some projects are initiated with specific deadlines. You need to determine whether

the deadlines are mandatory or desirable.

y This project is scheduled very well and it contains four modules and for that it requiresround about 4 months for completion. And according to the schedule this project is

completed and that is why it is schedule feasible.


3/92

GATE PASS SYSTEM

SPB LINCH CE - 3-

1.4 Resource feasibility

This involves questions such as how much time is available to build the new system, when it can

be built, whether it interferes with normal business operations, type and amount of resources

required, dependencies, etc. Contingency and mitigation plans should also be stated here.

y All the software, hardware required for this project is available at the point of development.Four months are available to build this project and it is completed without any disturbance.

So we can say that this project is resource feasible.

1.5 Cultural feasibility

In this stage, the project's alternatives are evaluated for their impact on the local and general

culture. For example, environmental factors need to be considered and these factors are to be

well known. Further an enterprise's own culture can clash with the results of the project.

1.6 Implementation Feasibility

Under the study of implementation feasibility, we've got to draw the

figure to the certain issues, like:

yIs it possible to install the software within the given en vironment?yWhether the system which is being developed will run in the

environment available with us?

yWill the system be approved by the management of theOrganization?

yWill the system cause any harm to the operations of theOrganization?

Operationally the system can be installed and it can work according toits functionalities. There would be very little barriers in implementation, if

application will be prepared according to the hardware barriers. Themanagement has already approved the software to be developed and it would in

fact help in user's operation or day-to-day activities.


4/92

GATE PASS SYSTEM

SPB LINCH CE - 4-

2. PROJECT PLAN

2.1 Objectives

Project plan includes description of project tasks, activities and functions, dependencies,

resource requirements and a detailed schedule. This activity results in the software project

management plan for the Annual Maintenance Contract.

Requirement Analysis:The requirement analysis activity takes the problem statement and reviews it in

terms of consistency, completeness and feasibility. During this activity, a set of models of the

proposed system is determined by interacting with the clients resulting in the requirement

Design

Coding

Testing

RequirementAnalysis


5/92

GATE PASS SYSTEM

SPB LINCH CE - 5-

model. The main parts of the requirements model are is: The use case model describing the

complete functionality of the system.

System Design:The purpose of the system design activities is to devices a system

architecture that maps the analysis model to the chosen target environment. The major part of

the system design phase is design of subsystems, that is, the decomposition of the system with

respect to the chosen target platform. The system design activity also refines the Use cases

from the analysis model and describes in terms of interaction diagrams how the objects

interact in each specific Use-case.

Implementation:The focus of this activity is on coding the individual objects described in

the object design document.

Testing Module:At the end of each and every phase is on coding the individual objects

described in the object design document.


6/92

GATE PASS SYSTEM

SPB LINCH CE - 6-

2.2 MILESTONES & DELIVERABLES

Managers need information to do their job. Because software is intangible,

this information can only be provided as reports and documents that describe the state of thesoftware being developed. Without this information, it is impossible to assess how well the work

is progressing, and cost estimates and schedules cannot be updated.When planning a project, you should establish a series of MILESTONES, where a

milestone is a recognizable end-point of a software process activity. At each milestone, thereshould be a formal output, such as a report, that can be presented to management. Milestone

reports need not be large documents. They may simply be a short report of what has beencompleted. Milestones should represent the end of a distinct, logical stage in the project.

Indefinite milestones such as coding 80% complete that cant be checked the useless for projectmanagement. You cant check whether this state has been achieved because the amount of code

that still has to be developed is uncertain.A deliverable is a project result that is delivered to the customer. It is usually

delivered at the end of some major project phase such as specification or design. Deliverables areusually milestones, but milestones need not be deliverable. Milestone may be internal project

result that are used by the project manager to check project progress but which are not deliveredto the customer.

To establish milestones, the software process must be broken down into basicactivities with associated output. For example, Fig. shows possible activities involved in

requirements specification when prototyping is used to help validate requirements. Themilestones in this case are the completion of the output for each activity. The project

deliverables, which are delivered to the customer, are the requirements definition and therequirements specification.


7/92

GATE PASS SYSTEM

SPB LINCH CE - 7-

MILESTONES PHASE-IIn the milestones table, it is mainly divided into two major phases. In first phases, it will be

sub-divided into five tasks and the completion date for each task is stated as the table below.

No. Tasks Milestone/Date complete

1 Project Identification and Selection 15t Jan, 2011

2 Project Initiation and Planning 1th

Feb, 2011

3 Literature Review 19th Feb, 2011

4 Analysis and Design 26th

March, 2011

5 Prototype and Report 30t

March, 2011

MILESTONES PHASE-II

The second phase of milestones is as shown as below. This second phase is sub-divided into

four tasks and the completion date for each task is as shown.

No. Tasks Milestone/Date complete

1. Review on Preview Project Work 30th

March, 2011

2. Update Plan and Requirements 9th

April, 2011

3.System Design (Database & Software

Architecture)12

thMarch, 2011

4. Final Report 22th

April, 2011


8/92

GATE PASS SYSTEM

SPB LINCH CE - 8-

2.3Time Line Chart

Gate pass System

Week (Tasks) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Activity January February March April

Domain

Understanding

Analysis

Requirements

Learning Process

Design

Coding

Documentation

Final Documentation


9/92

GATE PASS SYSTEM

SPB LINCH CE - 9-

2.4 Risk management

y Evaluates which risks identified in the risk assessment process require management andselects and implements the plans or actions that are required to ensure that those risks arecontrolled.

y Identifying risks and drawing up plans to minimize their effect on the project is called riskmanagement. An important task of a project manager is to anticipate risks, which might affect

the project schedule or the quality of the software being developed, and to take action to avoid

these risks.

y Simplistically, you can think of a risk as a probability that some adverse circumstance willactually occur. Risks may threaten the project, the software that is being developed or the

organization.

These categories of risk can be defined as follows:

1. Project risks are risks that affect the project schedule or resources.

2. Product risks are risks that affect the quality or performance of the software being

developed.

The process of risk management is illustrated in the figure below.

Fig: The Risk Management Process


10/92

GATE PASS SYSTEM

SPB LINCH CE - 10-

y Risk identification: Possible project, product and business risks are identified.y Risk analysis: The likelihood and consequences of these risks are assessed.y Risk planning:Plans to address the risk either by avoiding it or minimizing its effects on the

project are drawn up.

y Risk monitoring:The risk is constantly assessed and plans for risk mitigation are revised asmore information about the risk becomes available.

Risk communicationInvolves an interactive dialogue between stakeholders and risk assessors and risk managerswhich actively informs the other processes.

Risk analysis = risk assessment + risk management + risk communication

Risk IdentificationRisk identification is the first stage of risk management. It is concerned with discovering

possible risks to the project. In principle, these should not be assessed or prioritized at this stage

although, in practice, risks are not usually considered. Risk identification may be carried out as a

team process using a brainstorming approach or may simply be based on a managers

experience. These types of risks include:

y Technology risks:Risks that derive from the software or hardware technologies that arebegun used as part of the system being developed.

y People risks:Risks those are associated with the people in the development team.y Organizational risks: Risks that derive from the organizational environment where the

software is being developed.

y Tools risk: Risks that derive from the CASE tools and other support software used todevelop the system.

y Requirements risk:Risks that derive from changes to the customer requirements and theprocess of managing the requirements change.

y Estimation risk: Risks that derive from the management estimates of the systemcharacteristics and the resources required building the system.


11/92

GATE PASS SYSTEM

SPB LINCH CE - 11-

Risk PlanningThe risk planning process considers each of the key risks that have been identified and identifies

strategies to manage the risk. Again, there is no simple process that can be followed to establish

risk management plans. It relies on the judgment and experience of the project manager.

These strategies fall into three categories:

a) Avoidance strategies

Following these strategies means that the probability that the risk will arise will be reduced.

An example of a risk avoidance strategy is the strategy for dealing with defective

components that follows the strategy Replace potentially defective components with

bought-in components of known reliability.

b) Minimization strategies

Following these strategies means that the impact of the risk will be reduced. An example of a

risk minimization strategy is the strategy for staff illness which follows the strategy

Reorganize team so that there is more overlap of work and people therefore understand each

others jobs.

Risk Monitoringy Risk monitoring involves regularly assessing each of the identified risks to decide whether or

not that risk is becoming more or less probable and whether the effects of the risk have

changed.

y Of course, this cannot usually be observed directly, so you have to look at other factors whichgive you clues about the risk probability and its effects. These factors are obviously dependent

on the types of risk.


12/92

GATE PASS SYSTEM

SPB LINCH CE - 12-

y Risk monitoring should be a continuous process and, at every management progress review,each of the key risks should be considered separately and discussed by the meeting.

2.5 ESTIMATION

Software is the most expensive element of virtually all computer-based systems. For

complex, custom system, a large cost estimation error can make the difference between profitsand lost. Cost overrun can be disastrous for the developer.

Software cost and effort estimation will never be an exact science. Too many variables

human, technical, environment, political can affect the ultimate cost of software and effortapplied to develop it. However, software project estimation can be transformed from a black art

to a series of systematic steps that provide estimate with acceptable risk. To achieve reliable costand effort estimates, a number of options arise:

Software Sizing

Function point sizing

Standard component sizing

Problem-Based Estimation

LOC and FP data are used in two ways during software project Estimation:-

As an estimation variable to size each element of the software and As baseline matrices collected from past projects and used in conjunction with

estimation variables to develop cost and effort projections.

Schedules

Obtain an early view of staffing requirements and constraints, and demonstrate theimpact of changing deadlines, understaffing, and staff loading.

Quality

Quantify the impact on defect rates of building to deadlines or reducing staff.

Risk

Fine tune risk levels for all the major types of risk: size, requirements, technology,

maintenance, systems integration, and defects.


13/92


14/92

GATE PASS SYSTEM

SPB LINCH CE - 14-

3. REQUIREMENT ANALYSIS

3.1 STUDY OF CURRENT SYSTEM

The GATE PASS SYSTEM is a application intended for users of any kind of

company. The motivation of this project comes from our desire to learn the increasingly growing

field of secure and safe sap gate pass system facilities.

3.2 PROBLEMS AND WEAKNESS OF CURRENT SYSTEM

The current system is quite tedious and time consuming thereby involving a great risk

of errors. At the time of getting information if there is a long queue of the users may have to wait

for a long time and this chaos would create additional burden on the receptionist.

3.3 REQUIREMENTS OF NEW SYSTEM

3.3.1 Functional Requirements:-

As the current company scenario, the gate pass system facilities plays important and

necessary roll for the growth of anytime and anywhere capabilities. In this fastest growing world,

Humans have no time for paper work. As scenario, if we want to make request for gate pass for

ant kind of material, we have to go there and have to fill up the details for the request. It takes

more time. So with gate pass Application, user can fill up the request form in his system only.

Admin can accept the different request in his system itself. .


15/92

GATE PASS SYSTEM

SPB LINCH CE - 15-

3.3.2 Non-Functional Requirements:-

The Non-functional requirement specifies the following requirements which are as

follows:

a) Extensibility:-Basic goal of any system is to satisfy the users requirements any time user can request

for an extra updating or refinements in the software and so our system provides extensibility.

b) Flexibility:-Our system can execute on any platform or environment and this is just to help the user to

work easily and efficiently.

c) Security:-Our system helps the clients to provide secure and safe generation of request for material.

And also safe interaction with important database.

d) Maintainability:-It is necessary to maintain our software because it stores the information about the items

stocked. Information can be like the cost of item, purchase date; issue date etc and this

information can be used or required in future also.

1 System should be user friendly.

2 System should be Reliable, Accurate & Specific.

3 System should be extensible & reusable.

3.3.3 Operational Requirements

This Application has been developed with two parts. 1) Bank Agent Application. 2)

Customer or client Application. In first, As per todays scenario, A private banks provide agent

facilities to their client. Suppose if we do daily transaction with our accounts, then we do not

need to go to the bank. A bank agent will come with us. Agent will take details from us for

transaction and agent will do transaction from their cell phone with details of our account. And


16/92

GATE PASS SYSTEM

SPB LINCH CE - 16-

in second application, A customer or client is able to see report of their accounts. Means full

details of account and also particular transaction within particular date.

3.4 REQUIREMENT ENGINEERING PROCESS

The description of the services and constraints are the requirements for the system and

the process of finding out, analyzing, documenting and checking these services and

constraints is called requirement engineering.

As shown in the diagram on the next page, the requirement engineering flows.


17/92

GATE PASS SYSTEM

SPB LINCH CE - 17-

y Domain Understanding

To develop a project for real time users, to help them to make a gate pass request

easily and in efficient manner. User can also see their requests reports also.

USER REQUIREMENT: -

User are login on the system and make a request for a gate pass for the material of his

department .User can also see his reports.

SYSTEM REQUIREMENT: -The developed application must be work on the SAP GUI. The application is user

friendly and also contain the all past reports of all request.

y PRELIMINARY REQUIREMENT ANALYSISThis phase is actually a base for the whole development effort. Here we meet the

prospective users of the system and analyze the features they demand. A

comprehensive understanding of the users needs and writing down features of the

proposed software product are the keys to success in this phase. Different techniques

can be employed for collecting user requirement, which include

User Meeting & Interviews Study of current process Questionnaires

By asking the questions and conducting multiple meetings, we refined our requirements.

Some of the questions were like

1. What would be the way of authenticating the users?2. Who would be administrating the application?


18/92

GATE PASS SYSTEM

SPB LINCH CE - 18-

We gave presentation of proposed system to Project Guide with the purpose of getting

feedback and suggestions that helped us in refining the requirements for the

administration Module.

Software requirement analysis may be divided into five areas of efforts:

i. Problem Recognitionii. Evaluation and Synthesis

iii. Modelingiv. Specificationv. Review

3.5 ROLES AND RESPONSIBILITY.

Task Responsibility

Requirement Analysis Study all the aspects of proposed system

System Design Designing of the Web site

Implementation Coding for all the four modules

Testing Unit Testing, Integral Testing, Loop Testing etc

Requirement Analysis

y As we mentioned, there is only one person in our development team. For properunderstanding the requirements of the end user (Which is the most important part of theproject) I, Jasdeep Singh Bhatia have derived the requirement statement of the end user

by understanding their nature and then asking about what they need by this utility to be

done.


19/92

GATE PASS SYSTEM

SPB LINCH CE - 19-

System Design

y In System design, all the UML diagrams (Class Diagram, Activity Diagram and DFD)are created by me.

Implementation

y My all modules are implemented in abap and implements on client side and server side.Testing

y Testing is the process through which the system is considered as the effectiveness of theoutput that it will generate in different combination of inputs by the end user.

y ROLES & RESPONSIBILITIES

ROLE NAME RESPONSIBILITY

Project Guide Mr. Hitesh Patel

Defining scope

Providing required resources

Project tracking and monitoring.

Analysis and Effort Estimation.

Coordination between teams.

Jasdeep SinghBhatia

Designing

Coding

Reporting to Project Guide

Documentation


20/92

GATE PASS SYSTEM

SPB LINCH CE - 20-

3.6 USER CHARACTERISTICS

Analyzing user characteristics is an important aspect of any project. It allows the team to clearly

define and focus on who the end users are for the project. Also, it allows the team to check the

progress of the project to ensure the team is still writing the product for the correct users.

This Application is mainly used by three users

y Store Adminy Normal membery Gate man

Store AdminStore Admin after login in can easily see all the request for gate pass. Admin

Can make gatepass easily, also he can see the all kind of reports. He can see all past

reports. Also he can edit in request form after material has been received.

Normal member. Normal member after login in can make gate pass request. He can fill the

request form for gatepass for the particular material. Also he can see all reports of his

department.

Gate manGate man can easily do edit in the request form in status field. He can

update the status of the material at every state.


21/92

GATE PASS SYSTEM

SPB LINCH CE - 21-

3.7 Constraints

Identify the project constraints and risks in order to help a team to define the parameters of theapplication deployment project and develop the project plan.

Defining Project ConstraintsTo prioritize and define the scope of the application deployment project, gather informationabout the constraints of your project. Constraints often include:

Resources. Identify the equipment, software, staff, and space that are available for the project.

Time. Identify the date by which the application deployment project must be completed, and

how the application testing process fits into the larger deployment project.

Organizational issues. If the project will not involve the entire organization, identify whichgroups in your organization will be affected by it. Additionally, determine if a particular group in

the organization needs the new operating system sooner than others. If so, you might decide toperform a staged rollout.

Access to developers. Identify applications that were developed in-house or especially for your

organization. Access to the developers of these applications is critical during the testing andissue resolution phases of the project. Such access also can be an invaluable aid with retail

applications.

Technical Constraints

Technical constraints stem from FS relationships. Most often within an IT project, tasks will belogically sequential to get from the start to the end. These constraints are the simplest and most

likely the ones youll find in a project. The technical constraints you may encounter whenbuilding your network diagram fall into two major categories:

y Discretionary constraints These constraints allow the project manager to change therelationship between activities based on educated guesses. Imagine two tasks that arescheduled to run concurrently

y Resource constraints A project manager may elect to schedule two tasks as FS ratherthan SS based on a limitation of a particular resource

Date Constraints

Often in project management, projects have preset deadlines that require project managers towork backward from the assigned completion date. The problem is that the person establishingthe deadline may not realize the work required to complete a project by that given date.


22/92


23/92

GATE PASS SYSTEM

SPB LINCH CE - 23-

3.9 USECASE DIAGRAM

Use case diagram describe functionality of the system and users of the system. This diagram

contain following element.

Actor: It represents users of the system; include human user and other system.

User Cases: It represents functionality or service provided by a system to user.


24/92


25/92

GATE PASS SYSTEM

SPB LINCH CE - 25-

4. SYSTEM DESIGN

4.1 DESIGN STRATEGY

SAP R/3

SAP R/3 is the former name of the main enterprise resource planning software produced by SAP

AG. It is an enterprise-wide information system designed to coordinate all the resources,information, and activities needed to complete business processes such as order fulfillment or

billing.

SAP R/3 Client /Server ArchitectureIn SAP terminology, a service means a service provided by a software component

(software-oriented view) This component can consist of a process(compare work process) or agroup of processes (compare application server) and is then called a server for that service

.Software components that use this service were called clients. at that same time ,clients can alsobe servers for specifics devices.A server often also means a computer (host) on which software

components that provide specific services are running (hardware-oriented view).Every SAP R/3 system consists of one database server and one or more application server. In a

typical SAP R/3 scenario, each user connects to an application server by starting the SAPGUIprogram on his or her local machine.

The resulting 3-tier architecture is shown in figure 2.it requires a pc as a client. Thepresentation layer executes the SAPGUI program, providing users with GUI to access the system

without any built in business logic. The application layer is where application softwareexecution actually takes place.


26/92

GATE PASS SYSTEM

SPB LINCH CE - 26-

Each system can consist of several application servers communicating with the others,

running on UNIX, AS/400, orWindows NT platforms. One centralized database layer .The threelayers can be located on one or several servers .though users can install all layers on one system

usually this is used for demonstration purpose .typically these systems are configured without

terminal server .users run SAPGUI on their workstation using it to connect to the applicationserver .the application server and the database may be distributed on different machines but there

is typically one application servers are added on other machines to increase the performance ofthe R/3 system.

Architecture of SAPGUI:

SAPGUI is the user interface to SAP R/3 .it performs the following functions: Finds and connects to an application server

Provides several windows for the user Displays data sent from the application server Sends user data to the application server Communicates with application running on the local computer

These tasks are implemented by the architecture shown in figure shown below


27/92

GATE PASS SYSTEM

SPB LINCH CE - 27-

SAPGUI implemented in three steps .the user starts a program called SAPLogon.exe.it searchesfor an application server on the desired SAP R/3 system and starts Sapgui.exe.Sapgui.exe

maintains the TCP/IP connection to the R/3 application server.front.exe is then launched .itopens a window called main mode where applications operate. Several windows can be

opened at one time.Sapgui.exe multiplexes the data from each window, sending it to theapplication server using the same TCP/IP connection. SAPGUI is not only used for user input

and displaying data, it is also the interface for the R/3 application server to the usersworkstation. It communications with other process running on the workstations such as

Microsoft Office applications .it is also possible to integrate ActiveX Controls into SAPGUI amodern look and feel .this feature is only available in modern versions of SAPGUI ,which are

only available forWindows 98/95/NT and partially ,for java.

System Requirements for SAPGUI: 64 MB of RAM minimum(128 MB of RAM recommended) 45 MB of available disk space for SAPGUI installer 100 MB of available disk space for SAPGUI softwareNetscape 4.5 or higher (Netscape 4.78 is recommended) MIT Certificates


28/92

GATE PASS SYSTEM

SPB LINCH CE - 28-

4.2 DataFlow Diagram

A data f low diagram (DFD) is a graphical representat ion of the "f low" of data

through an information system. A data f low diagram can also be used for the

visualizat ion of data processing (structured design). I t is common practice for

a designer to draw a contextlevel DFD first which shows the interaction

between the system and outside enti t ies. This contextlevel DFD is then

"exploded" to show more d etai l of the system being modeled.

A data f low diagram il lustrates the processes, data stores, and

external enti t ies in a business or other system and the connecting data f lows.

The four components o f a data f low diagram (DFD) are:

Shapes Description

This symbol is used for dataflow in the

diagram.

This symbol is used for process in the

diagram.

This symbol is used for source and destination

processes.

This symbol is used for data storage in the

diagram.


29/92

GATE PASS SYSTEM

SPB LINCH CE - 29-

CONTEXTLEVEL DFD


30/92

GATE PASS SYSTEM

SPB LINCH CE - 30-

1STLEVEL DFD


31/92

GATE PASS SYSTEM

SPB LINCH CE - 31-

2NDLEVEL DFD

Gate Pass

Details

Gate Pass

Details


32/92

GATE PASS SYSTEM

SPB LINCH CE - 32-

4.3 Data dictionary

As a system data model is derived, many named entities, relationships and so forth will beidentified. The names given to the entities should be chosen to give the reader some clues to their

meaning. However, further description of the named entities is usually to make the modelunderstandable. The description can be informal or formal. Whatever approach is used, it is

always worth collecting al description in a single repository or data dictionary.A data dictionary is simplistically, a list of names used by the system, arranged

alphabetically. As well as the name, the dictionary should include a description of thecomposition. Other information such as the date o creation, the creator and the representation of

the entity may also be included depending on the type of model which is being developed.

Advantages of using data dictionary are: It is a mechanism for name management. Many different people who have to invent

names for entities and relationships may develop a large system model. These names

should be used consistently and should not clash with their meaning. The data dictionarysoftware can check for name uniqueness and tell requirement analysis of nameduplications.

It serves as a store of organizational information, which cans analysis, design,implementation and evolution. As the system is developed, information is taken to informthe development new information is added to it. All information about an entity is one

place.

List of Table:

Login detail

Request details Company detail Department detail Gate pass detail Commara details


33/92

GATE PASS SYSTEM

SPB LINCH CE - 33-

Table Name: Login detailDescription: This table contains all the information about the users

.

Table Name: Request detailsDescription: This table provides all the details of the users request

.


34/92

GATE PASS SYSTEM

SPB LINCH CE - 34-

Table Name: Company detailsDescription: This table provides all the details of the Company.

Table Name: Department detailsDescription: This table provides all the details of the Department

.


35/92

GATE PASS SYSTEM

SPB LINCH CE - 35-

Table Name: Gate Pass detailsDescription: This table provides all the details of the Gate Pass.

Table Name: Commara detailsDescription: This table provides all the details of the Material number and Company Id.


36/92

GATE PASS SYSTEM

SPB LINCH CE - 36-

4.4 USER INTERFACE DESIGN

Activity Diagram:

Activity diagrams are graphical representations of workflows of stepwise activities and actionswith support for choice, iteration and concurrency. [1] In the Unified Modelling Language, activity

diagrams can be used to describe the business and operational step-by-step workflows ofcomponents in a system. An activity diagram shows the overall flow of control.

Activity diagrams are constructed from a limited repertoire of shapes, connected with arrows. The

most important shape types:

y Rounded rectangles represent activities.y Diamonds represent decisions.y Bars represent the start (split) or end (join) of concurrent activities.y A black circle represents the start (initial state) of the workflow.y An encircled black circle represents the end (final state).

Arrows run from the start towards the end and represent the order in which activities happen.

y Hence they can be regarded as a form of flowchart. Typical flowchart techniques lackconstructs for expressing concurrency. However, the join and split symbols in activity

diagrams only resolve this for simple cases; the meaning of the model is not clear

when they are arbitrarily combined with decisions or loops

.


37/92

GATE PASS SYSTEM

SPB LINCH CE - 37-

y Users:


38/92

GATE PASS SYSTEM

SPB LINCH CE - 38-

y Admin:


39/92

GATE PASS SYSTEM

SPB LINCH CE - 39-

y Normal Member:


40/92

GATE PASS SYSTEM

SPB LINCH CE - 40-

y Gate Man:


41/92

GATE PASS SYSTEM

SPB LINCH CE - 41-

E-RDIAGRAM


42/92

GATE PASS SYSTEM

SPB LINCH CE - 42-

5.IMPLEMENTATION PLANNING AND DETAILS

5.1 IMPLEMENTATION ENVIRONMENT

As the gate pass system System going to be developed is normal(company)

application, at the time of implementation it should be kept in mind that system it will be used

concurrently. So the development approach would remain for the concurrent use.

The system is completely GUI. This is because today customer feels comfortable while

working with images or pictures. It can be used by any end-user. Thus user should feel

convenient while working with the system. Thus system is user-friendly.

5.2 MODULES SPECIFICATION

There are many modules associated with the system and they are as follows:

1. Request entryUser can fill the request form for gate pass of his material of his department and

also can see his reports .

2. Request ReportUser can see all the request made by him for his department and also can check

status of his request.

3. View Request DetailsAdmin can see all the request for gate pass made by normal member of every

department. Admin can see request of all departments.


43/92


44/92

GATE PASS SYSTEM

SPB LINCH CE - 44-

6. TESTING

The aim of the testing process is to identify all defects existing in a software product.

Testing a program consists of subjecting the program to as set of test inputs (or test cases) and

observing if the program behaves as expected. If the program fails to behave as expected, then

the conditions under which failure occurs are noted for later debugging and correction. The

following are some commonly used terms associated with testing.

Testing Principle:-

Testing is a process of executing a program with the intent of finding an error.

A good test case is one that has a high probability of finding an as yet undiscovered error. A successful test is one that uncovers an yet undiscovered error.Principle #1:- All tests should be traceable to customer requirements.

Principle #2:- Tests should be planned long before testing begins.

Principle #3:- The pareto principle applied to software testing.

Principle #4:- Testing should begin in the small and progress toward testing in large.

Principle #5:- Exhaustive testing is not possible

6.1 TESTING PLAN

The testing process is a process that to a great extent runs in parallel with other processes.

During the development phase of Store project, test cases for separate modules has been made to

check whether system is working properly after developing as stated or generate erroneous

output. As the same thing applied to whole system for testing and once the entire module works

perfectly as desired, at later stage test suite are made to test in integrated environment to check

for proper functioning.


45/92

GATE PASS SYSTEM

SPB LINCH CE - 45-

So the software is tested at various levels by various testing techniques like black box,

white box, Unit testing and Integration testing etc. Initially all the operations are tested separately

while development. This is unit testing and as the developer does it, so it is white box testing.

Once the operations are tested separately the leader of the phase integrates it with the other

classes and he performs Integration cum Black box testing. And he gives remarks to the

developer about any error.

After all at the end to test the software at software validation level we performed test case

based testing. In which inherited test cases from the scenarios of the system developed in the

Analysis phase in Dynamic Model.

In unit testing the testing of programs that make the system is done. Unit testing gives

stress on modules independently one another. Module is tested and necessary modification is

made.

The Testing Process

System Test

Use CaseTest

Subsystem Test

Delivere

d System

Designed &

implementati

Requireme

nt model


46/92

GATE PASS SYSTEM

SPB LINCH CE - 46-

Objectives of Testingy The main purpose of testing and information system is to find the errors and correct

them. A successful test is one finds an errors.y To ensure that during the operation the system will perform as per specification.y To make sure that the system meets users requirements during operation.y To verify that the control incorporated in the system function as intended.y To see that the when correct inputs are fed to the system, the outputs are correct.y To make sure that during operations, incorrect inputs, processing and outputs will be

detected.

y Testing is a process of executing a program with the intent of finding an error.y A good test case is one that has a high probability of finding an undiscovered error.y A successful test is one that uncovers an undiscovered error.y To ensure customer satisfaction, enhance business and set a good reputation for the

software developer.

6.2 TESTING SRATEGY

The test strategy is a formal description of how a software product will be tested. A

test strategy is developed for all levels of testing as and when required. The testing team

analysis the requirements, writes the test strategy and reviews the plan with the project team.

The test plan may include test cases, conditions and the test environment, a list of related

tasks, pass/fail criteria and risk assessment.

As we were working in a team it was a bit difficult to check the work done as no

individual was assigned for that particular task or work. Moreover checking the work done

was very important to reduce risk factor. Right from the starting we planned to adopt one

technique called Assessment by rotation. Thus the work done by one member was assessed

by the other for some time and again revolved for other level check reduced the errors.


47/92

GATE PASS SYSTEM

SPB LINCH CE - 47-

6.3 TESTING METHODS

Web based applications need intensive testing, as the applications will always function as

a multi-user system with bandwidth limitations. Some of the testing which should be done are,

Integration testing, Stress testing, Scalability testing, load testing, resolution testing and cross-

browser compatibility testing. Both automated testing and manual testing should be done without

fail. For example it is needed to test fast loading graphics and to calculate their loading time, as

they are very important for any web site.

Testing methods are mainly divided into two parts:

1. Black Box Testing2. While Box Testing

1) lack Box Testing:It is the testing without the knowledge of the internal working of the item

being tested. For this testing test groups are often used. Due to the nature of this

testing the test planning can begin as soon as the specifications are written. This

testing has some advantages like it is more effective on larger units of code than

glass box testing, tester needs no knowledge of implementation, including

specific programming languages, tester and programmer are independent of each

other, tests are done from a users point of view, will help to expose any

ambiguities or inconsistencies in the specifications, test cases can be designed as

soon as the specifications are complete.

2) White Box Testing:It is the testing strategy that deals with the internal logic and structure of the

code. White box testing is also called as the glass testing, structural testing, open

testing or the clear box testing. The advantages of the white box testing are that

as the knowledge of internal coding structure is needed, it becomes easy to find


48/92

GATE PASS SYSTEM

SPB LINCH CE - 48-

out which type of input data can help min testing the application effectively. It

helps in optimizing the code helping in removing the extra code which may cause

hidden defects in the system.

The other sub testing techniques are as follows:

Unit TestingWe have tested our functions of component to check the specification of our components.

We selected input set to test the components like in query process we gave the different kinds of

inputs to examine there output. We test software with sequences that have only a single value.Each Module Leader will do the Unit Testing and list out all the bugs in the Excel sheet.

Integration TestingPerformance testing is designed to test the runtime performance of the system within the

context of the system. These tests were performed as module level as well as system level.Individual modules were tested for required performance. In performance testing we counted the

processing time and response from the server with respect to request.

Interface TestingIn the system, standards tests for GUIs have been performed, which are as follows.

Testing the screen control for its position and size. The position and related labels for all controls were checked. Name of the form in system is given appropriately.

All menu functions and sub functions were verified for correctness. Each menu functions were tested, whether it invokes the corresponding functionality

properly.

Pull down controls was verified for proper functionality.


49/92


50/92

GATE PASS SYSTEM

SPB LINCH CE - 50-

6.4 TEST CASES

In software engineering the most common definition of a test case is set of conditionsor variables under which a tester will determine if a requirement or use case upon an

application is partially or fully satisfied. In the situation each sub requirement must have atleast one test case. A good test should neither be too simple nor too complex. Testing is a

critical element of its quality assurance and represents the ultimate review or specification,design and code generation.

Purpose:

The purpose of the test cases is to test the various input and see the output produce anyerror or not. There are different test cases according to the system. It is tested with different types

of value like single value, multiple values and sees it can generate expected output.

Test Cases are defined to find out whether the functionality is running successfully ornot and some of the test cases are mentioned below in table.

APE = As Per Expected

CaseID Test Case Expected Result Actual

Result

CS1 Check all links to other pages. It should call the concerned

page

APE

CS2 Verify validations

(Live Validation)

It should prompt user for valid

inputs

APE

CS3 Check whether user Interface is

according to requirement or not

User should be required to

give less input and havedetailed output

APE

CS4 Confirm whether theAdministrator is given all the

control over the system or not

Admin should have fullcontrol over the system

APE

CS5 Make sure output is coming as per

given input or not

Output must be correct with

respect to Input

APE

CS6 Try out response time of eachrequest

Requested page should nottake much time to be load

APE

CS7 Check Security of System meansthe user should not be allowed to

visit any restricted page until he isnot authenticated

User must be required toLogin before visiting any

restricted pages

APE

CS8 Check out whether the user isgiven facilities of system

according to his/her role

Admin should have morefacility of the system compare

to normal user

APE


51/92

GATE PASS SYSTEM

-51-

7. USER MANUAL

1. NORMAL DEPARTMENTLOGINWINDOW


52/92

GATE PASS SYSTEM

-52-

2. HOME PAGEOFNORMAL DEPARTMENT


53/92

GATE PASS SYSTEM

-53-

3. NORMAL DEPARTMENTREQUESTFORM


54/92

GATE PASS SYSTEM

-54-

4. NORMAL DEPARTMENTREPORTS


55/92

GATE PASS SYSTEM

-55-

STORE DEPARTMENT

1. STORE DEPARTMENTLOGIN


56/92

GATE PASS SYSTEM

-56-

2. HOME PAGEOFSTORE DEPARTMENT


57/92

GATE PASS SYSTEM

-57-

3. MAKEGATEPASS-VENDERSELECTION


58/92

GATE PASS SYSTEM

-58-

4. GATEPASS-COMPANYWISELIST


59/92

GATE PASS SYSTEM

-59-

5. MAKEGATEPASS-DEVICE


60/92

GATE PASS SYSTEM

-60-

6. FINALGATEPASS-1


61/92


62/92

GATE PASS SYSTEM

-62-

8. ALLREPORTSINPUT


63/92

GATE PASS SYSTEM

-63-

9. RESULTOFGENERAL PARAMETERS


64/92

GATE PASS SYSTEM

-64-

10. SALESREPORTS


65/92


66/92

GATE PASS SYSTEM

-66-

12. STATUS-APPROVED


67/92

GATE PASS SYSTEM

-67-

13. STATUS DISPATCHED


68/92

GATE PASS SYSTEM

-68-

14. STATUS-RECEIVED


69/92

GATE PASS SYSTEM

-69-

15. MATERIALRECEVIED UPDATED


70/92

GATE PASS SYSTEM

-70-

16. RESULTSOFGATENO


71/92

GATE PASS SYSTEM

-71-

17. UPDATE QUANTITY


72/92

GATE PASS SYSTEM

-72-

GATE MAN

1. GATEMANLOGIN


73/92

GATE PASS SYSTEM

-73-

2. GATEPASSREPAIRSORREPALCED


74/92

GATE PASS SYSTEM

-74-

3. REPORTS BASEON GATEID


75/92

GATE PASS SYSTEM

-75-

4. GATEMANDISPATCHMATERIALS


76/92

GATE PASS SYSTEM

-76-

5. GATEMANRECEIVED MATERIALS


77/92

GATE PASS SYSTEM

-77-

8. CONCLUSION AND FUTURE WORK

FUTURE ENHANCEMENT

Every system requires changes to keep up with the time. The design of thesystem and database is flexible enough to ensure that enhancements can beeasily made without any major changes to the application.

Some functionality scope is as follows:

yAdd some more functionality in the system in terms of the need of the USER.yThe maintaince of material quantity can added to the system.CONCLUSION

This system will be very useful for users as they can easily make request for

materials. An Admin can easily make gate pass for the requests and can easily

see all reports.


78/92

GATE PASS SYSTEM

-78-

9. ANNEXURE

9.1Glossary of terms and abbreviations

Term or Abbreviation Definition

Abap Advanced Business Application Programming.

The SAP programming language.

SAP R/3 SAP R/3 is the former name of the main enterprise

resource planning software produced by SAP AG.

SAPGUI The SAPGUI is software on your computer that

you use to access and complete transaction in the

SAP system.

SAP Logon The SAP Logon is the windows program that yousee to log on to sap system on windows posit

mediates between the SAP system and SAP GUI

user interface .

ABAP Editor ABAP Workbench tool for creating ABAP

programs. Is called either directly through

transaction code SE38 or is embedded in other

tools such as Object Navigator, Class Builder, orFunction Builder.

ABAP Dictionary (BC-DWB-DIC) Persistent storage for data types that are visible in

all repository objects. In addition, the database

tables of the central database, views, and lockobjects are managed in the ABAP Dictionary -among other things. The objects of the ABAP

Dictionary are maintained with the same-nametool of the ABAP Workbench. Call through

transaction code SE11.

SAP Smart FormsSAP form tool.

SAP Smart Forms combines previously

separate components such as forms and print

programs into a single unit. To print a form,

you only need a program for data retrieval

and a smart form from which an ABAP

function module is automatically generated.

SAPscriptA tool for text management and form


79/92


80/92


81/92


82/92

GATE PASS SYSTEM

-82-

integrate ActiveX Controls into SAPGUI a modern look and feel .this feature is onlyavailable in modern versions of SAPGUI ,which are only available forWindows 98/95/NT

and partially ,for java.

System Requirements for SAPGUI:

64 MB of RAM minimum(128 MB of RAM recommended)

45 MB of available disk space for SAPGUI installer 100 MB of available disk space for SAPGUI software Netscape 4.5 or higher (Netscape 4.78 is recommended) MIT Certificates

The persons involved in SAP are as follows:

1. Functional Persons.

2. Basis person using SAP basis System application can run on different platforms

with high performance and can be adapted to meet individual user requirements.

3. ABAP Programmer

SAP R/3 Modules:


83/92

GATE PASS SYSTEM

-83-

Startup and Shutdown of the SAP System

Use

Before you can use the SAP System you must log on .when you are finished using

the SAP System, you log off .the first time you log on and at regular intervalsthereafter, you should change you password.

Activities

Regardless of the tasks you will be performing in the Sap System, you willalways be stating up and shutting down the SAP System.

You start the SAP System by the selecting the logon icon on your desktop. You log on to the SAP System. If this is your first time logging on, you w ill have to changes the initialpassword provided by your system administrator .if this is not your first time

logging on, you may have to change your password in accordance with the

security policies at your company.

When you are finished working with the SAP System you log off.The SAP Logon

Definition

The SAP Logon is the windows program that you see to log on to sap system

on windows posit mediates between the SAP system and SAP GUI user interface

the SAP Logon displays a list of available SAP Systems and automatically selects

servers with the best current response times. You can add available systems or

servers to this menu.

UseWhen you log on to the SAP System, You can:

Log on to a specific application server Log on to a group .in this case application server with the best response time

is selected automatically.

When you log on to the SAP Logon icons are displayed in the system try of the

system taskbar (in the bottom right-hand corner of the screen).you can maximize Or

minimize the SAP Logon by clicking the icon using the left mouse button.

If you click the icon using the right mouse button you can display a list of

connections to SAP Systems that are already open.


84/92

GATE PASS SYSTEM

-84-

This enables you to see all the following information:

Description of the SAP System and its system ID The Group or server The System number The Message Server SAP Routers

Logging OnPrerequisites

Before you log on, make sure you know:

Your Client Number Your user ID Youre Password

If you want to work in a language other than English make sure you know the language

key for your desired language .for more information, contact you system administrator.

Logging OffProcedure

You can log off from the SAP System from any screen. from the menu bar, choose

System ->

Logoff.


85/92

GATE PASS SYSTEM

-85-

1.Cli t tt att upper ri t-hand corner ofthe screen (if you only have one

session running).The log off dialog appers (as shown here),informing you that any data you have not

yet saved will be lostif you proceed with logging off.

2. if you are not certain that you have saved all of your data, and you do not wantto log offafter all, choose no you return to the screen in which you were working.If you are certain that you have saved all ofthe data you wantto save, choose yes all of

your SAP System sessions close. You have successfully logged off.THE SAP INDO

UseThe SAP window is the userinterface to the SAP System.


86/92

GATE PASS SYSTEM

-86-

The standard toolbar contains buttons for performing common actions such as save andenter.

BUTTONS NAME FUNCTIONS

Enter Confirms the data you have selected or entered on thescreen. Same function as the enter key. Does not save

your work.

CommandField

Allows you to enter commands such as transaction codes.

Save Saves your works. Same function as save in edit menu.

Back Returns you to the previous screen without saving yourdata.

Exit Exits the current function without saving.

Cancel Exists the current task without saving.

First page Scrolls to the first page

Previouspage

Scrolls to the Previous page

Next page Scrolls to the Next page

Last page Scrolls to the Last page

CreateSession

Create a new SAP session.

CreateShortcut

Allows you to create a desktop shortcut to any SAPReport, transaction, or task.

Layout

Menu

Allows you to customize the display options.

ABAP/4 Programs for SAP

ABAP (Advanced Business Application Programming, originally Allgemeiner Berichts-

Aufbereitungs-Prozessor, German for "general report creation processor), pronounced as

'ah-bop', is a high-level programming language created by the German software companySAP. It is currently positioned, alongside the more recently introduced Java, as the language

for programming the SAP Application Server, part of its Net Weaver platform for buildingbusiness applications. The syntax of ABAP is somewhat similar to COBOL.

ABAP is one of the many application-specific fourth-generation languages (4GLs) firstdeveloped in the 1980s. It was originally the report language for SAP R/2, a platform that

enabled large corporations to build mainframe business applications for materialsmanagement and financial and management accounting

ABAP used to be an abbreviation of Allgemeiner Berichtsaufbereitungsprozessor, the

German meaning of "generic report preparation processor, but was later renamed toAdvanced Business Application Programming. ABAP was one of the first languages to

include the concept of Logical Databases (LDBs), which provides a high level of abstraction

from the basic database level(s).

The ABAP programming language was originally used by developers to develop the SAP

R/3 platform. It was also intended to be used by SAP customers to enhance SAP

applications customers can develop custom reports and interfaces with ABAP

programming. The language is fairly easy to learn for programmers but it is not a tool for


87/92


88/92

GATE PASS SYSTEM

-88-

Apply and modify built-in functions. Add a response to a user-action like double-clicking on a display line. Prints lists or export them to other application. Apply and modify built in function. Define and save custom output settings then select and change from pull-down menu

ALV Grid Control is SAPs graphical List-viewing tool and is similar in look and feel to

Microsoft Excel.ALV functionality lets SAP end-users.

Perform common list operations such as summing and filtering. Perform graphical functions such as typeface and paragraph formatting. Crate, share and maintain a library of output templates. Customize data output on the fly.

MATERIAL MANAGEMANT (MM) MODULEIntroductions:

Materials management is the branch of logistics that deals with the tangible

components of a supply chain. Specifically, this covers the acquisition of spare parts and

replacements, quality control of purchasing and ordering such parts, and the standards

involved in ordering, shipping, and warehousing the said parts.

Goals The goal of materials management is to provide an unbroken chain of componentsfor production to manufacture goods on time for the customer base. The materials

department is charged with releasing materials to a supply base, ensuring that thematerials are delivered on time to the company using the correct carrier. Materials is

generally measured by accomplishing on time delivery to the customer, on timedelivery from the supply base, attaining a freight budget, inventory shrink

management, and inventory accuracy. The materials department is also charged with

the responsibility of managing new launches.

In some companies materials management is also charged with the procurement of

materials by establishing and managing a supply base. In other companies the

procurement and management of the supply base is the responsibility of a separatepurchasing department. The purchasing department is then responsible for the

purchased price variances from the supply base.

In large companies with multitudes of customer changes to the final product over

the course of a year, there may be a separate logistics department that is responsible

for all new acquisition launches and customer changes. This logistics department

ensures that the launch materials are procured for production and then transfers theresponsibility to the plant materials management to manage


89/92

GATE PASS SYSTEM

-89-

Materials Management Challenges

The major challenge that materials managers face is maintaining a consistent flow of

materials for production. There are many factors that inhibit the accuracy of inventory

which results in production shortages, premium freight, and often inventory adjustments.

The major issues that all materials managers face are incorrect bills of materials, inaccurate

cycle counts, un-reported scrap, shipping errors, receiving errors, and production reporting

errors. Materials managers have strived to determine how to manage these issues in the

business sectors of manufacturing since the beginning of the industrial revolution. Although

there are no known methods that eliminate the afore mentioned inventory accuracy

inhibitors, there are best methods available to eliminate the impact upon maintaining an

interrupted flow of materials for production.

One challenge for materials managers is to provide timely releases to the supplybase. On the scale of worst to best practices, sending releases via facsimile or PDF file is the

worst practice and transmitting releases to the supplier based web site is the best practice.Why? The flaw in transmitting releases via facsimile or email is that they can get lost or

even interpreted incorrectly into the suppliers system resulting in a stock out. The problemwith transmitting EDI releases is that not all suppliers have EDI systems capable of

receiving the release information. The best practice is to transmit the releases to a commonsupplier web base site where the suppliers can view (for free) the releases. The other

advantage is that the supplier is required to use the carrier listed in the web site, must

transmit an ASN (advanced shipping notification), and review the accumulative balances of

the order

THE effective materials management plan builds from and enhances an

institutional master plan by filling in the gaps and producing an environmentally responsible

and efficient outcome. An institutional campus, office, or housing complex can expect a

myriad of benefits from an effective materials management plan. For starters, there are long-

term cost savings, as consolidating, reconfiguring, and better managing a campus core

infrastructure reduces annual operating costs. An institutional campus, office, or housingcomplex will also get the highest and best use out of campus real estate

Benefits

An effective materials management plan also means a more holistic approach tomanaging vehicle use and emissions, solid waste, hazardous waste, recycling, and utility

services. As a result, this means a greener, more sustainable environment and amanifestation of the many demands today for institutions to become more environmentally

friendly. In fact, thanks to such environmental advantages, creative materials managementplans may qualify for LEED Innovation in Design credits.

And finally, an effective materials management plan can improve aesthetics.

Removing unsafe and unsightly conditions, placing core services out of sight, and creating amore pedestrian-friendly environment will improve the visual and physical sense of place

for those who live and work there.


90/92

GATE PASS SYSTEM

-90-

9.4 About the organization

COMPANY PROFILE

AJD INFOTECH was started in May 2004. It was founded by Mr. SUNILDOSANI looking into growing needs of support and training for various ERPs. The CEO of

the company Mr. SUNIL DOSANI is having a very reach exposure of around 20 years inIT Industry. He has worked in vertical industries like textiles, Engineering and

pharmaceuticals. He was a project manager for SAP implementation and has been working

with SAP since year 1999. He has also provided training to the various types of groups liketop management, departmental heads, key users and operational uses in SAP. He has design,

developed and implemented the integrated applications company wide using oracle and

various development tools.

AJD INFOTECHAbout Company

AJD INFOTECH was started in May 2004. It was founded by Mr. SUNIL DOSANI

looking into growing needs of support and training for SAP in Gujarat. We are providing

quality and cost effective services on SAP on AMC basis or on call basis. We have a team

of four people including BASIS / ABAP / SD / MM consultant and freelancers working on

sap projects. Our area of services is

1. SAP Onsite / Offsite Helpdesk and Post implementation support2. Corporate Training (Groups of IT Users/Key Users/End Users)

3. Project Management and Co-ordination (Acting as coordinator for any project related toSAP with the external service providers/Vendors to ensure optimum utilization of services)

4. Process Improvement and Functional Consultancy in SAP / ERP5. Application Development in SAP using ABAP and Advance ABAP Tools

6. Providing Training in Management institutes like NIRMA / ICFAI on ERP.

Supporting on Modules

y BASIS/ABAPy MM (Material Management)y SD (Sales & Distribution)y PP (Production Planning)y QM (Quality Management)


91/92

GATE PASS SYSTEM

-91-

y FI (Financial Accounting)y CO (Controlling)y PM (Plant Maintenance)

Projects/Assignments undertaken AJD INFOTECH Ahmadabad.A MNC engineering company using sap version 4.7 With Country India Modules.

From: May 2004 to Till Date

y SAP Helpdesk and Supporty Process Improvementy Customization and Configuration in SAP related to process Improvementy Project coordination for up gradation from SAP version 4.0B to 4.7y CIN upgrading from 2.2A to SAP 4.7 CIN( Country India Version)y Post Upgrade support on all core modules and CINy Project coordination for the implementation of Six Sigma being conducted by

NCQM (National Council for Quality Management)

y Application development/ABAP programmingy Training of IT users/Key Users/End Users

Providing other non SAP IT services like Setting up of leased lines, procurement of servers,upgrading of hardware etc


92/92

GATE PASS SYSTEM

9.5 INSTIT TE PROFILE

9.5.1 Introduction

Saffrony institute oftechnology is developed with an aim To continuouslystrive forthe

total development of students by educating them in state-of-the-arttechnologies and helping

them imbibe professional ethics and social commitment, so thatthey emerge as competent

professionals to meet global challenges.

Saffrony Institute of Technology aims to continuously strive to make it a center of

excellence in providing professional education and allied services, redefining quality

standards far above the aspirations ofthe society.

The Saffrony Institute of Technology is committed to inculcate discipline and perseverancein students and faculty to ensure thatthey meet and exceed the highest academic standards

and expectations ofthe society, in general and Industry in particular.

In pursuance ofthe quality goals, the Management, Faculty and Students of SIT affirm their

commitmentto the policy of continuous improvementin their endeavours.

9.5.2 Programms

SPBPatelEngineering College offers four yearBachelor of Engineering degree

programmes in five streams at undergraduate level vi .1. Electronics & Communication Engineering (60 seats)2. Computer Engineering (60 seats)

3. Information Technology (60 seats)4. Mechanical Engineering (90 seats)

5. Civil Engineering (60 seats)

Master ofBusiness Administration (MBA) Two Years (60 seats)

roports gate updated

Documents