Aptech Garden Software Engineer Batch EMS

Aptech Garden Software Engineer Batch : 1510E
October , 23 , 2016
eProject -Page 1
Acknowledgements
We would like to acknowledgeall those who have given moralsupportand
helped us make the project a success.
We wish to express our gratitude to the eProjectTeam at the Head Office,
who guided and helped us in eProject course. Particular thanks to Mr. Dao
Trong Duy (duydt@fpt.com.vn),who suggested Subversion software(SVN) and
guided us throughoutthe process of eProject.
I would also like to express my gratitude to all staff and student of my
center (FPTAptech 3) for not only providing me with the opportunity to work
with them on this project, but also for all supportand encouragement that
really helpful and valuable for us
Aptech Garden Software Engineer
--o0o--
EXPO MANAGEMENT
Application name: EMS
(Expo management System)
Batch: 1510E
Faculty: Sir Iqrar
Group: 1 person
Member:
Faizan Anwer Ali

October , 23 , 2016
eProject -Page 2
Chapter I:
Introduction and Existing Scenario
I. Problem Abstraction
With the increasing growth in the number of industries and the competitive run for the
trophy of perfection and profit, these industries round the globe are in the lookout
for a roof to exhibit their products in the most convenient, profitable and successful means
Queries related to the Expo Management System can be on or more of the
following:
1. How to store all the details are recorded in the respective registers? What details do I
need to provide to register Exhibitor?
2. How to display annual Expo information and history of Exhibitor?
3. What details do in need to provide to register Booth and Product?
4. How to automatically update exhibitor accounts when fees or services are changed for a
booth?
5. How to display report about exhibitor financial list, booth audit trail, cash receipts by
date…?
6. How to produce complete product guide and exhibitor directory is easy?
7. How to create charts and graphs for the Executive Director/Board
II. The Proposed System
Solutions
• Expo Management System manages all information. Data is archived centrally in
database.
• Expo Management System is installed on all manager and accountant's computers
and assigned the access level.
• Expo Management System data systems login with account-level managers or
accountant separately.

October , 23 , 2016
eProject -Page 3
• Expo Management System will limit the right to access data through the access
level.
• Expo Management System allows users to perform operations such as search, add
new, update, etc.
Target users
Expo Management System has 2 modules for 3 types of person:
•Admin
•Manager
•Accountant
The applicationallows:
Application allows Manager to access and modify all information that store in Expo
Management System.
Admin have access to manage all the information and able to set member’s role as well
as member group's role in order to manage system better.
A GUI containing buttons, textboxes, labels…,
GUI containing buttons, textboxes, labels…, which will provide user-friendly interfaces to
the user to work with the application
Particular features:
With using thread in some progress such as loading data, copy file…, all those will run
separately. In addition, coping file contains 2 threads: reading thread and writing thread, which
operate by FIFO mechanics and data synchronization. It makes the application to run
continuously and avoid interruption in working.
Similar to some mail box on internet, the application also provide the same function
with all function as read, sent, forward, reply…. A problem is offered: When user sent message
to one or more another user, they always get a trouble with rememberance all profile of
another user. Because of it, the application accept user to auto-fill some information of

October , 23 , 2016
eProject -Page 4
recipients such as Name, Email ,Phone …. It’s convenient when you want to send message or
suggestion to a lot of user at the same time. The function’s guideline is writen in Help file.
In order to avoid a mistake when user input some informations such as Email, Phone,
Fax..., the system support a function which will check suitability of input data. If input data is
inappropriate, the system will request user to re-input appropriate data. For example,
Faizan1507c@aptechgdn.net is appropriate email and Faizan1507c@aptechgdn.net is
inappropriate data, 03052046205, 03132870236, 03052046205 etc.. is appropriate phone
number and 045634232 or 01545134223 is inappropriate data.
User can change background of application with coping images into folder Background
in application, make sure that image’s size is fit in computer’s screen. The application will
change background randomly when application starts.
Finally, Admintrator can create a lot of group which have a different role. All user may
divide into these group. This function will make company’s groups work separately if your
company want to improve the system in oder to manage a expo management with large extent.
III. Customer Requirements Specification
2.1 Users of the System
Project Objective
• Users are Management, Accountant and Admin
2.1.1 Management should be able to do the following:
•Manager can view and modify records as Exhibitor, Expo, Contract…
• Manager should be able to search some records in various ways.
• Manager can view and edit some personal information.
2.1.2 Accountant should be able to do the following:
• Accountant can create accounting report such as Exhibitor financial list, Cash receipts by
date, accounting summary reports...
• Accountant can view statistics that depend on contract's worth.

October , 23 , 2016
eProject -Page 5
• Accountant can view and edit some personal information.
2.1.3 Admin should be able to do the following:
• Admin can create user account
• Admin can edit user account profile
• Admin should be able to disable user account
• Admin can divide users into one or more group. Each group have a particular role (for
example: whether be able to access to some information or not)
• Admin can set group's role
• Admin can edit group information
2.2 System Functions
2.2.1 General Function
 Login:
Input: User and password.
Process: Check valid data input. Check to be in being of user’s
account in Accounttable in database.
Output: : if entered user and password is correct , create new
account . if it‘s incorrect, input again notification is displayed.
 Change password:
Input: Old user and password, new password.
Process: Check valid data input. Update new password in the
database Account table.
Output: Display notification.
 Retrieve password:
Input: Username, Email, Answer
Process: get account that match for username is inputted (Use
Email and forgot password Answer)

October , 23 , 2016
eProject -Page 6
Output: Account with new password.
 Sent message:
Input: Message’s content (Sender)
Progress: Save Message’s detail into database, and generate
notification to sender and recipients.
Output: Notification to sender, Notification and message’s content
to recipients.
 Read message:
Input: Reading message request.
Progress: access to database and get message’s content.
Output: Message’s content.
 Logout:
Input: Logout request
Process: Set account = null, reload option and remove all current
Internal frame.
Output: Login interface
2.2.2 Admin
 Create account:
Input: account detail.
Process: Check whether or not username, email, role is exist and
appropriate
Output: if entered detail is correct, create new account. if it‘s
inappropriate, input again notification is displayed.
 Disable user account:
Input: user account
Process: Change user account’s role
Output: Display confirmor not request
 Create group:
Input: group detail and its permission

October , 23 , 2016
eProject -Page 7
Process: Check whether or not group’s name is appropriate
Output: if entered detail is correct, create new account. if it‘s
inappropriate, input again notification is displayed.
 Edit group:
Input: group information or permission
Process: update information into group.
2.2.3 Manager
Zone management:
 Add Zone:
Input: Zone detail
Process: Add new Zone into database
 Update Zone:
Input: Zone, new Zone detail
Process: update new detail into Zone
 Sort Zones by request:
Input: sorted manner
Process: sort Zones by sorted manner that is inputted
Output: List of Zones is sorted
Category management:
 Add Category:
Input: Category detail
Process: Add new Category into database

October , 23 , 2016
eProject -Page 8
 Update Category:
Input: Category, new Category detail
Process: update new detail into Category
 Sort Categories by request:
Process: sort Categories by sorted manner that is inputted
Output: List of Categories is sorted
Sponsor management:
 Add Sponsor:
Input: Sponsor detail
Process: Add new Sponsor into database
 Update Sponsor:
Input: Sponsor, new Sponsor detail
Process: update new detail into Sponsor
 Sort Sponsors by request:
Process: sort Sponsors by sorted manner that is inputted
Output: List of Sponsors is sorted
Product management:
 Add Product:
Input: Product detail
Process: Add new Product into database

October , 23 , 2016
eProject -Page 9
 Update Product:
Input: Product , new Product detail
Process: update new detail into Product
 Sort Products by request:
Process: sort Products by sorted manner thatis inputted
Output: List of Products is sorted
 View Product’s information :
Input: Product
Process: Load all Product’s information into new frame.
Output: Display information
Booth management:
 Add Booth:
Input: Booth detail
Process: Add new Booth into database
 Update Booth:
Input: Booth, new Booth detail
Process: Update new detail into Booth
 Sort Booths by request:
Process: sort Booths by sorted manner thatis inputted
Output: List of Booths is sorted

October , 23 , 2016
eProject -Page 10
Exhibitor management
 Add Exhibitor:
Input: Exhibitor detail
Process: Add new Exhibitor into database
 Update Exhibitor:
Input: Exhibitor, new Exhibitor detail
Process: Update new detail into Exhibitor
 Sort Exhibitors by request:
Process: sort Exhibitors by sorted manner thatis inputted
Output: List of Exhibitors is sorted
 View Exhibitor’s information :
Input: Exhibitor
Process: Load all Exhibitor’s information into new frame.
Output: Display information
Contract management:
 Add Contract:
Input: Contract detail
Process: Add new Contract into database
 Update Contract:
Input: Contract, new Contract detail
Process: update new detail into Contract

October , 23 , 2016
eProject -Page 11
 Sort Contracts by request:
Process: sort Contracts by sorted manner that is inputted
Output: List of Contracts is sorted
Expo management:
 Add Expo:
Input: Expo detail
Process: Add new Expo into database
 Update Expo:
Input: Expo , new Expo detail
Process: Update new detail into Expo
 Sort Expos by request:
Process: Sort Expos by sorted manner that is inputted
Output: List of Expos is sorted
 View Expor’s plan :
Input: Expo
Process: Load Expo’s picture into new frame.
Output: Display picture
Annual expo management
 View annual expo information:
Input: View request
Process: Load informations of all Expo.
Output: Display information.

October , 23 , 2016
eProject -Page 12
2.2.4 Accountant
Financial report management:
 Create financial reports :
Input: Statistics such as contract’s worth, sum of fund is
sponsored
Process: Calculate and create financial report
Output: Financial reports
2.3 Hardware and Software Requirements
Minimum Requirements
 4 Gbytes of RAM or higher
 Core Do 2 or higher capability CPU
 Windows 2007 (or higher if possible)
 Java Virtual Machine
Software requirements
 Java SE 8.0
 NetBeans 8.2
 MS SQL Server 2008
 JDBC Driver

October , 23 , 2016
eProject -Page 13
IV. Architecture and design of the Project
The application will have a three-tier architecture:
Layer 1:
Presentation Layer
Layer 2 :
Business Logic Layer
Layer 3:
Data Access Layer
User Interface – GUI
Component
File containing
business logic
Data Access

October , 23 , 2016
eProject -Page 14
Data flow diagram
Define: Data Flows Diagram(DFD) describes the information flow in the system. The next step
of systemanalysis is to consider in detail the information necessary for the implementation for
functions discussed above and the one necessary for the improvement of the functions.
Modeling tool frequently used for this purpose is DFD. DFD will support 4 main activities:
Analysis: DFD is used to determine requirement of users.
Design: DFD is used to map out plan and illustrate solution to analysis and users while designing
a new system.
Communication: one of the strength of DFD is its simplicity and ease to understand to analysts
and users.
Document: DFD is used to provide special description of requirement and system design. DFD
provide an overview of key functional components of the systembut it does not provide any
detail on these components. We have to use other tools like database dictionary, process
specification to get an idea of which information will be exchanged and how. The main
components of Context Diagram:
Process Enternal
Data Flow
Data
Store

October , 23 , 2016
eProject -Page 15
The process: Shows the common function of system
The external: External factors can be a person, a group of persons or an organization that are
sources of information for the systems and are where system products are transferred to.
The data flow: Describe the movement of information from one part of the system to another.
The data store: The Data Store is used to model a collection of data packets at rest. A store is
represented graphically by two parallel lines. The name of a Data Store that identifies the store
is the plural of the name of the packets that are carried by flows into and out of the Data Store
Figure 1: DFD LEVEL 0 - Context Diagram
Management Admin
Accountant
Required Infomations
Request commands
Request commands
Required Infomations
Required
Information
Request
commands
Expo
Management
System

October , 23 , 2016
eProject -Page 16
Figure 2: DFD LEVEL 1 – Application process
Management
Admin Accountant
Personal
Information
Management
Booth
Management
Exhibitor
Management
Annual Expo
Information
Management
Contract
Management
Advanced
Management
Financial
Report
Management
Zone
Management
Sponsor
Managament
Category
Management
Product
Management

October , 23 , 2016
eProject -Page 17
Figure 3: DFD LEVEL 1.1 – Zone management
Manager
Zone
Add new Zone
Report
Staff No
Edit Zone
Zone
Zone detail
is updated
Zone
Zone no. Report
Zone

October , 23 , 2016
eProject -Page 18
Figure 4: DFD LEVEL 1.2 – Booth management
Management
Booth
Add new Booth
Report
New Booth
details
Edit Booth
Booth
New
Booth
Booth
details is
updated
Booth
Booth no. Report
View Booth
infomation
Infomations
Zone ID
Booths
Booth
Booth
details is
required
Booth
Expo ID Infomations

October , 23 , 2016
eProject -Page 19
Figure 5 : DFD LEVEL 1.3 – Exhibitor management
Management
Add new
Exhibitor
Edit Exhibitor
View exhibitor
information
Sort exhibitor
list
Exhibitor
Exhibitor ID
report information
Exhibitor ID
Exhibitor
Exhibitor
Exhibitor
New
Exhibitor
New
Exhibitor
details
report
Exhibitor
details is
updated
Exhibitor
Exhibitor
ID is
invoked
Exhibitor
sorted
manner
information
Exhibitor
IDs are
invoked
Exhibitors

October , 23 , 2016
eProject -Page 20
Figure 6: DFD LEVEL 1.4 - Product Management
Management
Add new
Product
Edit Product
Product ID
Report
Product
Product
Product
details is
updated
Product
New
Product
New
Product
details
report

October , 23 , 2016
eProject -Page 21
Figure 7: DFD LEVEL 1.5 – Financial Report management
Accountant
Contract
Financial Report Management
FundingInfo
Financial Report
Requested manner
Request Information
Information Request

October , 23 , 2016
eProject -Page 22
Figure 8: DFD LEVEL 1.6 – Advanced management
Admin
Account
Management
Group
Management
Requested
manner
Information
Account
Group
infomation
Requested
manner
Result Process
Result Process

October , 23 , 2016
eProject -Page 23
Figure 9: DFD LEVEL 1.7 – Expo management
Manager
Annual expo
information
management
information
Requested manner
Expo
Expo detail
is requested
Expo

October , 23 , 2016
eProject -Page 24
Figure 10: DFD LEVEL 1.8 – Contract management
Manager
Add new
Contract
Edit Contractt
Contract
Contract
Report
New
Contract
detail
New
Contract
Contract
Contract
detail is
update
Contract
ID
Report

October , 23 , 2016
eProject -Page 25
Figure 11: DFD LEVEL 1.9 – Sponsor management
Management
Add
Sponsor
Edit Sponsor
Sponsor ID
Report
Sponsor
Sponsor
New
Sponsor
New Sponsor
detail
Report
Sponsor
Sponsor
detail is
updated

October , 23 , 2016
eProject -Page 26
Figure 12: DFD LEVEL 1.10 – Category management
Management
Add
Category
Edit
Category
Category ID
Report
Category
Category
New
Category
New Category
detail
Report
Category
Category
detail is
updated

October , 23 , 2016
eProject -Page 27
Figure 13: DFD LEVEL 2.1 – Account management
Create new
Account
Admin
Disable Account
Edit member
information
Report
Account ID
Account
Account
Account
Account
Account detail
is updated
New
Account
Report
New Account
detail
Report
Account
ID
Account

October , 23 , 2016
eProject -Page 28
Figure 14: DFD LEVEL 2.2 – Group management
Admin
Edit Group
Add Group
Set Group Role
Group
Group
Permission
Group ID
Report
Report
New Group
detail
Group
Group
detail is
updated
Role
Report Group ID
New Group

October , 23 , 2016
eProject -Page 29
Figure 15: DFD LEVEL 2.3 – Personal information management
Personal
information
management
Admin
Account
Accountant
Management
Report
Requested
manner
Requested manner Report
Process Result
Requested
manner
Report

October , 23 , 2016
eProject -Page 30
Figure 16: DFD LEVEL 2.3.1 –Login
Login
Admin
AccountantManage
Account
Request Result
User and
Password
Notification
User and
Password
Notification
User and
Password
Notification
Figure 17: DFD LEVEL 2.3.2 – Log Out
Log Out
Admin
AccountantManage
Account
Request Result
Logout
request
Notification
Logout
request
Notification
Logout
request
Notification

October , 23 , 2016
eProject -Page 31
Figure 18: DFD LEVEL 2.3.3 – Change Password
Change
Password
Admin
AccountantManage
Account
Notification
Old Password
New Password
Notification
Old Password
New Password
Old Password
New Password
Notification
New
password
Result

October , 23 , 2016
eProject -Page 32
Figure 19:DFD LEVEL 2.3.4 – Retrieve Password
Retrieve
password
Admin
AccountantManage
Account
Notification
Username ,
forgot password
Answer , new
Password
Notification
Notification
New
password
Result
Username ,
forgot password
Answer , new
Password
Username ,
forgot password
Answer , new
Password

October , 23 , 2016
eProject -Page 33
Figure 20: DFD LEVEL 2.3.5 – Private Message Management
Private Message
Management
Message
Admin Accountant
Manager
Result Request
Request Result
Result Process
Result Request

October , 23 , 2016
eProject -Page 34
Figure 21: DFD LEVEL 2.3.5.1 – Sent Message
Sent Message
Management
Message
Sender
Notìfication
Message
Message
detail
Notification
Recipient
Figure 22: DFD LEVEL 2.3.5.2 – Read Message
Read Message
Management
Message
User
Request
Message
Message’s ID
is requested
Result

October , 23 , 2016
eProject -Page 35
V. Entity Relationships Diagram(ERD)

October , 23 , 2016
eProject -Page 36
VI – DesignDiagram
Sponsor
Field Name Data Type Key Null Description
ID_Spo Int Primary Key No
Spo_Name Nvarchar(50) No
Spo_Address Nvarchar(100) No
Spo_Email Varchar(50) No
Spo_Phone Varchar(15) Yes
Spo_Fax Varchar(15) Yes
Spo_Status Bit Default (1) Yes
Expo
ID_Expo Int Primary Key No
Expo_Name Nvarchar(50)
No
Expo_StartDate Smalldate No
Expo_EndDate Smalldate No
Expo_Description Nvarchar(3000) Yes
Expo_Address Nvarchar(100) Yes
Expo_Image Varchar(30) Yes

October , 23 , 2016
eProject -Page 37
Account
FieldName DataType Key Null Description
ID_Acc Int Primary Key No
ID_Gr Int Foreign Key References No
Acc_FullName Nvarchar(50) No
Acc_Gender Bit Default (1) Yes
Acc_UserName Varchar(32) No
Acc_Password Varchar(32) No
Acc_Email Varchar(50) No
Acc_Phone Varchar(15) Yes
Acc_Question Nvarchar(100) No
Acc_Answer Varchar(50) No
Acc_Status Bit Default (1) Yes
Booth
ID_Boo Int Primary Key No
ID_Zone Int Foreign Key References No
Boo_Name Nvarchar(50) No
Boo_Amout Float No
Boo_Status Bit Default (1) Yes
BoothContract

October , 23 , 2016
eProject -Page 38
Category
FundingInfo
ID_Boo Int Foreign Key References No
ID_Con Int Foreign Key References No
BC_TotalEmp Int Foreign Key References No
BC_Amount Float No
ID_Ca Int Primary key No
Ca_Name Nvarchar(50) No
Ca_Status Bit Default (1) Yes
ID_Spo Int Foreign Key References No
ID_Expo Int Foreign Key References No
FI_Amout Floai No

October , 23 , 2016
eProject -Page 39
Contract
ID_Con Int Primary Key No
ID_Ex Int Foreign Key References No
ID_Expo Int Foreign Key References No
ID_Acc Int Foreign Key References No
Con_Name Nvarchar(50) No
Con_Content Nvarchar(3000) No
Con_Date Smalldatetime No
Con_StartDate Smalldatetime No
Con_EndDate Smalldatetime No
Con_Status Bit Default (0) No
ContractDetail
ID_Boo Int Primary Key,
Foreign Key References
No
ID_Con Int PK,FK No
BC_TotalEmp Int PK,FK No
BC_Amout Int No

October , 23 , 2016
eProject -Page 40
Exhibitor
ID_Ex Int Primary Key No
Ex_Name Nvarchar(50) No
Ex_Description Nvarchar(3000) Yes
Ex_Logo Varchar(30) No
Ex_Address Nvarchar(100) No
Ex_Email Varchar(50) No
Ex_Phone Varchar(15) Yes
Ex_Fax Varchar(15) Yes
Ex_Status Bit Default (1) Yes
Group
ID_Gr Int Primary Key No
Gr_Name Nvarchar(50) No
Gr_Description Nvarchar(100) Yes
Gr_Status Bit Default (1) Yes

October , 23 , 2016
eProject -Page 41
Permission
ID_Gr Int PK , FK No
Per_ItemZone Bit Default (0) Yes
Per_ItemBooth Bit Default (0) Yes
Per_ItemCategory Bit Default (0) Yes
Per_ItemProduct Bit Default (0) Yes
Per_ItemSponser Bit Default (0) Yes
Per_ItemExhibitor Bit Default (0) Yes
Per_ItemExpo Bit Default (0) Yes
Per_ItemContract Bit Default (0) Yes
Per_ItemGroup Bit Default (0) Yes
Per_ItemAccount Bit Default (0) Yes
Per_ItemStatistic Bit Default (0) Yes
Message
ID_Mess Int Primary Key No
Mess_From Int Foreign Key References No
Mess_To Int Foreign Key References No
Mess_Title Nvarchar(100) No
Mess_Content Nvarchar(500) No
Mess_Date SmallDateTime No
Mess_Status Bit Default(1) Yes

October , 23 , 2016
eProject -Page 42
Product
ID_Pro Int Primary key No
ID_Ca Int Foreign Key References No
Pro_Name Nvarchar()50 No
Pro_Price Float No
Pro_Description Nvarchar(1000) Yes
Pro_Image Varchar(30) Yes
Status Bit Default(1) Yes
Zone
Field Name Type Name Key Null Description
ID_Zone Nvarchar(50) Primary Key No
Zone_Name Int No
Zone_Width Int No
Zone_Height Int No
Zone_ Percent Int Yes
Zone_Status Bit Yes

October , 23 , 2016
eProject -Page 43
Chapter VII: FlowChart
1. Login
- Actor: Admin, Manager and Accountant.
- Description: Input email and password will connected to database.
Check entry of Email and Password. If correct display management page,
else display Error message.
2. Insert

October , 23 , 2016
eProject -Page 44
- Actor: Admin, Manager and Accountant
- Have functions into Account, Contract, Product, Booth, Sponsor… (it depend on actor’s
role)
- Description:
+ Select Employee.
+ Check exist Contract, Product, Booth, Sponsor…
+ Display current data in form. Input new information.
+ If data is existed, appear dialog message “Duplicated data”, if valid insert into
database and appear dialog message “Add Successful”.
3. Update

October , 23 , 2016
eProject -Page 45
- Actor: Admin, Manager and Accountant.
- Have functions into Account, Contract, Booth, Sponsor … ( it depend on actor’s role)
- Description:
+ Input information.
+ If data invalid, appear a error message. If data valid will be updated to database,
appear a dialog message “Update successful”.

October , 23 , 2016
eProject -Page 46
4. Forgot Password
- Description:
+ Retrieve password.
+ If all information that you input is valid, you should be able to change password.

October , 23 , 2016
eProject -Page 47
5. Disable Account
- Actor: Admin
- Description:Disable user account

October , 23 , 2016
eProject -Page 48
6. Log Out
- Description:Close all current internal frame in main frame and display login internal
frame

October , 23 , 2016
eProject -Page 49
Chapter VIII: Interface.
1. Config:
2. Main

October , 23 , 2016
eProject -Page 50
3. Login:
4. Forgot Password:

October , 23 , 2016
eProject -Page 51

October , 23 , 2016
eProject -Page 52
5. Zone Management:

October , 23 , 2016
eProject -Page 53
6. Booth Management:

October , 23 , 2016
eProject -Page 54
7. Category Management:

October , 23 , 2016
eProject -Page 55

October , 23 , 2016
eProject -Page 56
8. Product Management:
9. Sponsor Management:

October , 23 , 2016
eProject -Page 57
10. Exhibitor Management:

October , 23 , 2016
eProject -Page 58
11. Expo Management:

October , 23 , 2016
eProject -Page 59
12. Contract Management:

October , 23 , 2016
eProject -Page 60
13. Statistics:

October , 23 , 2016
eProject -Page 61
14. Group Management:

October , 23 , 2016
eProject -Page 62
15. Account Management:

October , 23 , 2016
eProject -Page 63
16. Information:

October , 23 , 2016
eProject -Page 64

October , 23 , 2016
eProject -Page 65
17. Message:

October , 23 , 2016
eProject -Page 66

October , 23 , 2016
eProject -Page 67
18. About Us:

Aptech Garden Software Engineer Batch EMS

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (20)

Similar to Aptech Garden Software Engineer Batch EMS

Similar to Aptech Garden Software Engineer Batch EMS (20)

Aptech Garden Software Engineer Batch EMS