Product Master Maintenance system
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
seminar presentation
Active In SP
**

Posts: 582
Joined: Apr 2010
#1
31-05-2010, 12:24 AM


Title of the project and implimentation


Development of a Product Master Maintenance system.


Abstract of the project and implimentation


This project and implimentation is aimed at developing an online product master maintenance system used in a manufacturing industry. The Product Master Maintenance (PMM) is a client server based application that can be accessed by a selected group of users. This system can be used for maintaining all the details related to a product like Product hierarchy, product/sub¬components attributes(cost/size/weight etc.) and supplier details. There are additional features like user access control, report generators etc in this system.





Functional components of the project and implimentation

Following is a list of functionalities of the system. More functionalities that you find
appropriate can be added to this list. And, in places where the description of a functionality
is not adequate, you can make appropriate assumptions and proceed.
Following tasks can be performed with the application :
(a) User Maintenance : Granting & Revoking access to users on application
b) Product Maintenance
: A user should be able to :
¢ Create a new product with attributes.
¢ Define the hierarchy of product. The hierarchies can be defined as
- Family
- Class
- Product
¢ Relate a product to another product which is higher / lower in hieararchy
using parent-child relationship. ie. Product is child of Class and Class is child
of Family.
For example an automobile manufacturer can define following hierarchy
Family “ Car
Class “ Hatchback
Product “ Maruti 800
Family “ Car
Class “ Sedan
Product “ Maruti Esteem
Family “ Van
Class “ Delivery
Product “ Maruti Omni
Family “ Van
Class “ Passenger
Product “ Maruti Versa
¢ Add a supplier for the project and implimentation.
¢ Mark the product as active or defunct.
¢ Modify any attribute of the project and implimentation.
© Supplier Maintenance :
Allow the user to Add and Modify a supplier.
(d) Find User :
A search screen to find users and display results.
(e) Find product : A search screen to find products and display results.
(f) Find Suppliers :
A search screen to find suppliers and display results.
(g) Report :
Generate reports on product hierarchies, suppliers etc.
Accordingly there would be following levels of user privileges :
¢ Application admin having all privileges.
¢ Users having privileges for (b),©,(e),(f) & (g).
1. A user should be able to

¢ Login to the system through the first page of the application.
¢ Change the password after logging into system.
¢ Add and/or Modify a product.
¢ Add and Modify details about a Supplier.
¢ Relate a product to a supplier.
¢ Generate product and supplier reports.
2. The Application Admin should be able to do the following tasks
in addition to 1 :
¢ Add a new user.
¢ Remove a user.
Steps to start-off the project and implimentation
There are couple of alternatives to implement such a system.
A. Microsoft platform: The system is developed using ASP.NET \VB.NETas the
front end and SQL Server 2000/2005 as the back end.
B. Unix-based platform: Swing as front end,
EJB / Java programming, any relational database (eg Postgress / Oracle /
My SQL), and tools in Unix
The following steps will be helpful to start off the project and implimentation.
1. Study and be comfortable with technologies
such as
VB.NET/ASP.NET and SQL server 2000/2005.
Unix commands, Shell programming, Java Programming, SQL.
Some links to these technologies are given in the ËœGuidelines and Referencesâ„¢
section of this document.
2. Gather some knowledge of product hierarchies and maintenance before starting the
design. Have a full-fledged example with several products and sub-components etc for
testing the application.
3. Create a user database with different access levels.
4. Start with creating the login screen.
5. Create menus for navigation and group the functionalities as sub menus.
5. Create the help-pages of the application in the form of Q&A. This will help you also
when implementing the application.
Requirements
Hardware requirements
Use Search at http://topicideas.net/search.php wisely To Get Information About Project Topic and Seminar ideas with report/source code along pdf and ppt presenaion
Reply

Important Note..!

If you are not satisfied with above reply ,..Please

ASK HERE

So that we will collect data for you and will made reply to the request....OR try below "QUICK REPLY" box to add a reply to this page

Quick Reply
Message
Type your reply to this message here.


Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)

Possibly Related Threads...
Thread Author Replies Views Last Post
  STOCK MAINTENANCE SYSTEM pdf study tips 1 1,807 10-07-2015, 01:46 PM
Last Post: Guest
  Apartment Maintenance System seminar topics 4 3,139 15-07-2013, 10:03 AM
Last Post: study tips
  Report on Bazaar Master Web Portal study tips 0 410 21-06-2013, 12:52 PM
Last Post: study tips
  online Pharmaceutical Product Distribution System Report study tips 0 423 18-04-2013, 02:57 PM
Last Post: study tips
  ABSTRACT SPINNING MILL MAINTENANCE SYSTEM study tips 0 353 15-02-2013, 02:45 PM
Last Post: study tips
  SMBus protocol master implimentation seminar tips 0 267 30-01-2013, 04:02 PM
Last Post: seminar tips
  DEVELOPMENT OF A PRODUCT MASTER MAINTENANCE SYSTEM ABSTRACT project girl 0 296 28-01-2013, 09:29 AM
Last Post: project girl
  COMPUTER MAINTENANCE seminar tips 0 319 03-01-2013, 03:11 PM
Last Post: seminar tips
  ABSTRACT ON FLEET MANAGEMENT SYSTEM ON CAR RENTALS SYSTEM REPORT project girl 0 741 29-12-2012, 04:44 PM
Last Post: project girl
  Product Distribution System seminar tips 0 334 28-12-2012, 06:16 PM
Last Post: seminar tips