bildy-ga,
This description is that of what is generally referred to as an "asset
tracking" relational database management system (RDBMS). The given
problem is just a fancy way of saying, "We want to know exactly what
we have, how much of each, who's using it for what and when." [And, in
real life: "We also need to know how much it will cost us to develop
and maintain it, how long it will take you to make it, and what kind
of support you will offer for it after we buy it."]
In this example, the "assets" to track are individual pieces of IT
equipment, such as computers and associated peripherals. Additional
program "requirements" as outlined in the question are that the
database will track which software applications are on each computer,
who uses each system and for what.
Keep in mind that there are many different solutions for this same,
general problem, but all of them would involve the same process of
establishing requirements (what the program should do when finished),
designing a solution (i.e. your database schema: table relationships
and field types), creating it (actually building it in the database
application chose in your Design phase, (i.e. MS Access 2000,
FileMaker Pro or Oracle 8i, for example), implementing it (actually
making it happen--deployment, end-user training) and then maintaining
that solution (data back-up, user support, capacity planning, program
enhancements). That's the basic, overall "plan."
Now, it's a little tricky because in real life, people move things
around--a printer that's in Accounting today could be in Admin
tomorrow, so it's important to be able to track each piece of
equipment by itself, regardless of where it is. This is usually done
by assign ID #s, or by using the equipment Serial #.
I propose a general schema with 4 tables in the database: One Table
will be called, "Computers," one "Peripherals," "Software" and
"Personnel."
The primary keys for the Computers and Peripherals tables are the ID
#s. Every computer gets a unique "PC ID" or the like, every printer,
scanner, ZIP drive, etc. also gets a unique ID #, although these ID #s
are independent of the PC IDs.
The Software table uses the PC ID field to reference which computer
the software listed is associated with.
The Computer and Peripherals tables each have a field for Name of
user, which is a foreign key from the Personnel table.
Open MS Access 2000 and create new file, name it "IT Assets". Create
a New Table by clicking the "Table" button under the Objects list on
the left side of the Access window, create the fields as described
above, save, and create the Next table, create its fields, until all 4
tables are created.
Then, Open the Entity-Relationship diagram by clicking the icon with
three tables linked on the toolbar. Select the Tables tab, click OK.
Link the related fields here.
This is the basic process.
Then, you would create queries to extract desired information from
your database, and create Reports to display that information in a
professional manner according to user preference.
Below is a link to a site on database design which you will find
useful:
"Your First Database," by Jay Greenspan,
http://hotwired.lycos.com/webmonkey/backend/databases/tutorials/tutorial3.html
From Xiacon.com, here is a page on a professional asset tracking
database design, so you can get an idea of what to shoot for
eventually, and see how the basic concepts are implemented
professionally:
http://www.xiacon.com/asset-tracking/database.asp
Google search strategy:
keywords: "database design"
://www.google.com/search?hl=en&lr=&ie=ISO-8859-1&q=+database+design&btnG=Google+Search
,
"asset tracking database design"
://www.google.com/search?hl=en&lr=&ie=ISO-8859-1&q=+asset+tracking+database+design&btnG=Google+Search
Good luck in continuing your inquiries!
~omniscientbeing-ga |
Clarification of Answer by
omniscientbeing-ga
on
01 Oct 2002 21:31 PDT
Hi bildy-ga,
I'm sorry, but there is no way to attach or "post" a file to a Google
Research Answer, as you asked for in your request for Clarification.
The table relationships are not easily described in text only format,
but here is what you can do, in lieu of my creating and posting the
file here for you, which will still show you how to do your future
assignments:
Open whichever version of MS Access you are using, and select from the
File menu, New File. In the New dialog box, select the "Databases"
tab. Select the "Asset Tracking" template and click "OK." Name your
new file "IT Assets" and click Save. Follow through the dialogs of the
Database Wizard, which will automatically create for you an Asset
Tracking database which you customize with your own desired fields and
macros/VBA modules, if desired.
Then, just as with any Access .mdb file you make from scratch, you can
open the Entity Relationship Diagram and define/modify relationships
between the different tables and queries. Simply observe how the
Primary Keys are linked from table to table, and then make one on your
own "from scratch." Also, you can view the Tables and Forms in Design
View to see their components and how they are constructed.
This is really the best way to learn, as A) you know the design is
solid because they are standard, widely accpeted templates, and B)
you're going to build it from the ground up afterwards to solidy and
demonstrate your understanding.
Have fun!
~omniscientbeing-ga
~omniscientbeing-ga
|