Re: Need some suggestions for medium sized application

2006-11-13 Thread francky06l

Hi,

I did something similar in concept but completly different purposes. In
your case you need to define what is the central element there, is it
the tank or the microstation ?
All the other entities are actors around the base element.
Now I my application I have 4 differents roles for the user, and they
do not see the same things. Apart from the admin role, they all see
views starting from the base element.

The essential is to find out what you want to track, what will be kept.
I do not completly understand the tank in your schema, is the tank a
kind of directory of parts, or you want to track each tank
individually ? In this case this would be your central base elements,
the microstation will be the container of the base, and your roles
will have a different view of these containers ..

Hope this help a bit ..


--~--~-~--~~~---~--~~
 You received this message because you are subscribed to the Google Groups 
Cake PHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---



Need some suggestions for medium sized application

2006-11-12 Thread RedShift

Hello

(sorry if I posted twice, it didn't show up the first time :\)

Ok, so, I'm developing a medium sized application. I would appreciate
any suggestions you guys can make.

I need to design a system that traces microstations. What's a
microstation?
Just for reference, a microstation is a septic tank.

A microstation consists out of 2 or 3 tanks. A tank is manufactured by
a
_producer_. Then the tanks are assembled by an _assembler_ to create a
microstation. Now that microstation is then imported by an _importer_,
which
basically assigns a microstation to an _installer_. That same
_installer_
is able to keep a maintenance log (but that's for later).

So we have the following:
* Producer: produces tanks, the system registeres tank number,
production date,
and some other caracteristics.
* Assembler: takes the available tanks and assembles them into a
microstation.
The system registeres which tanks have been used to assemble it, a
production
number, the assembly date, etc...
* Importer: has an overview of available microstations. He assigns a
microstation an installer.
* Installer: has an overview of microstations assigned to him, he
assigns
microstations to a customer (system registeres customer name, address,
etc...)

First of all, the system is seperated in 5 different classes. That's
because
there are 5 types of users. They all have different views when they
login.
You have:

* Businessunit
* Producer
* Assembler
* Importer
* Installer

What's the businessunit? Well he is god. He is able to see
*everything*. That's
the point of the system, it provides tracing of the elements defined
earlier.
He can see for example, which microstation importer x has assigned to
installer
y.

Here's my current database:

* identities
- id (int auto_increment)
- class (set(businessunit, producer, assembler, importer, installer,
customer))
- name (varchar)
- password (varchar(32))
- address
- zip
- region
- country

* tanks
- id (int auto_increment)
- nr varchar(6)
- production (date)
- volume (int)
- identity_id

* microstations
- id (int auto_increment)
- nr (varchar(8))
- assembly (date)
- type (varchar(10))
- loading (date)

* microstations_tanks
- id (int auto_increment)
- microstation_id
- tank_id

* assignments
- id (int auto_increment)
- microstation_id
- identity_id

How does this look like for you guys?

Now my final question; every class of user, has a total different
system.
For example, when a producer logs in, he sees the tanks that he has
produced,
and can add new ones. When an assembler logs in, he sees the
microstations that
he has assembled, and can add new ones. When an importer logs in, he
only sees
available microstations and can assign an installer. When an installer
logs in
he can only see microstations assigned to him.
How would I do this with cakephp? Create a new application for every
class
of user?

If you have any comments, no matter how small, please do post them!
Just about
anything is usefull.

Thanks for your time

Glenn


--~--~-~--~~~---~--~~
 You received this message because you are subscribed to the Google Groups 
Cake PHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---