Project Application:

---------------------------------------------------------------------------------------------------------------------------------

To
The Academic Director,
Daffodil Institute of IT.,
Dhanmondi, Dhaka.

Through: Chief Course Coordinator

Sub: proposal to develop customized system

Dear Sir,

With due respect we would like to inform you that, we are students of IADCS at
DIIT in Dhanmondi. We have to complete a practical project as per our IADCS
course. We are interested in developing a generic system for small to large
business complexes (i.e. multistoried business centers).

We hope that you would be kind enough to permit us to develop this software
and issue us a work order.

Yours truly,

Md. Sanaul Kabir Rozen, IADCS - 25th Batch, ID-11.

Kazi Saifur Rahman, IADCS - 25th Batch, ID-13.

DPIS 1
 DAFFODIL INSTITUTE OF IT
DEPARTMENT OF CIS, NCC, UK,
UNDER LONDON METROPOLITAN UNIVERSITY.

PROJECT PROPOSAL:

Project Title: Dynamic Product Information System (DPIS).

Group Members & ID:

 Md. Sanaul Kabir Rozen (IADCS, 25th)

ID: 2-25-09-05-011

 Kazi Saifur Rahman (IADCS, 25th)

ID: 2-25-09-05- 013

Project Advisor:
Mr.Shamsuddin Ahammad (Faculty of Java, DIIT)

Date of submission:
28-10-2006 (approx)

DPIS 2
Introduction:

From the beginning since a time when peoples started gathering information, processed
it into somewhat they were looking for their own needs or others and the current status
of gathering the same information and storing it into some places and let people have
access on it. We must have to say there’s some massive change occurred during these
all years due to the way now people wants to store a piece of information and accessing
or changing anytime in terms of their requirements . As we know “Information is power”.
So as much as information we have and within a shorter time scale. It must put us into
steering first.
And that’s striving us to develop a project based on:
 Preserving bundles of information into one place,
 Processing it into more realistic information that final user’s are looking for,
 And retrieving that piece’s of information’s from one place.
That can make a huge difference in our daily life and that’s where this idea comes in.
Now this simulator is intending to serve a group of organizations and community
people’s in such places where people requiring very complete and updated information
instantly from a central place instead of running behind it.
------------------------------------------------------------------------------------------

DPIS 3
Background of the Project:

So now more specifically, our project is to provide a mechanism to the customer

through which s/he can acquire information and hence knowledge about a
product. There are two types of user panel in our system, one's type is “narrow
and deep” and the other's type is “shallow and wide”. The first categories of the
users are the business owners and the second categories of the users are the
clients who are going to enquire about many products.

Let us first come to the client's side of the system, whose simple purpose is to
use the software system to dynamically search about products that s/he is
looking for. Because in today’s multistoried, always busy shops and markets are
sometimes failing to adequately serve many customers enquiries at the same
time. Say for example someone wants to buy a ”Titan” wrist watch within a price
range of 5000 Tk but also wants to see what other watches are available in the
shop or market, s/he would have to search a lot of Stores to find that watch . But
if there’s a computerized product enquiry system was available to them, then it
would take minutes not hours to find the right product. So, these kinds of user we
have categorized as "shallow and wide". The client will be able to search on
product name, manufacturer, price, type, warranty, by shop/company ownership.
After searching for the products the customer can print out the result and then go
on to the respective shops/company premises to make further inquiry or a final
purchase. The reason we have called it shallow is because the users (i.e. the
customers) won’t be able to get much deeper information about a product. And
the reason we have called this types of users as wide is because they will be
able to run their searches on a wide range of shops and business.

Now lets us talk about the other kind of user of the system. This user has
"narrow and deep" access to the system. Through which s/he can get detailed
product information (deep) but only from places s/he is allowed to do so (narrow).

DPIS 4
These users are business owners, customer representatives/executives, sales
person/executives etc. When a customer wants detailed information about a
product, they can supply the information from here.

The types of information they can get here are related to all aspects of a product.
Such as - Product name, type, manufacturer, country of origin, manufacture date,
warranty, warranty conditions, price, discount, special offer, service offer,
originality, return policy, replacement policy, quality, likely lifespan of the product,
parts availability and other issues.

These users can also search another company’s database if they have been
given prior access permission. The interface would be the same as like the client
user interface, only the access permissions need to be set-up by the other
company before the inquiry can be made. This would be a B2B relationship,
where one company searches for a product at another company.

Now, there are two administrative sides in the whole system.

Through the 1st administrative side which serves the business owners, where
information about products can be inserted, updated, deleted, and changed. The
business owner’s premise would have this part of the software installed and
ready for use.

The second administrative side would be on the client computer. Here the
administrator (i.e. admin) would add/configure the different database server ip,
store/company name, database backend type (MySQL, MSSql, Oracle) and
UserID and Password.

So, finally there will be two types’ of users in the system:

1 Business User and
2 Client User.

DPIS 5
And, there are also two administrative parts to the system:
1One part deals with management of product information (i.e. business
owners)
2The other part with user rights (database access) management.
So this concludes the basic background details of “Dynamic Product Information
& Enquiry System (DPI&ES).”

Figure: Simulating “Dynamic Product Information & Enquiry System”

-----------------------------------------------------------------------------------------------------------
-

DPIS 6
 Aims of this project:

Simulating a live product information searching base system;

Providing a dynamic products information system to business

organizations;

Helping customers of the business to search their products more

quickly;

Providing most updated products information to customers

instantly from one single place;

So helping extending the businesses image and probably

extending more customers for the business;

Reducing products searching time between shops for the

customers;

Helping business organization’s in the shop to facilitate their

customers by remote products searching;

Simulating to deal with many customers remotely while they are

too busy with other customers in the shop;

Providing a mechanism for busy persons to have a quicker

shopping experience.

Providing both C2B and B2B relationship simultaneously by one

system;

And finally implementing a system that makes change in people

lives;

-------------------------------------------------------------------------------------------------------------------------

DPIS 7
Milestone of the project:

We have planned the project to be completed between the following days -

Duration Starting Ending

Phase
(Approx.) Date Date
1. Initial study 3 days 16-09-2006 19-09-2006
2. Feasibility study 2 days 19-09-2006 21-09-2006
3. Requirements analysis 3 days 21-09-2006 24-09-2006
4. System Analysis 4 days 25-09-2006 28-09-2006
5. Specification 2 days 29-09-2006 30-09-2006
6. Designing 4 days 1-10-2006 4-10-2006
7. Development 18 days 5-10-2006 22-10-2006
8. Testing Phase 1 2 days 23-10-2006 24-10-2006
9. Testing Phase 2 2 days 25-10-2006 26-10-2006
10. Implementation 1 days 27-10-2006 27-10-2006
11. System Review 1 days 28-10-2006 28-10-2006
Total days: 42 days

Delivery date of the project: 28th October 2006 (approx, if not on government
holiday).

---------------------------------------------------------------------------------------------------------------------------------

DPIS 8