dbTalk Databases Forums  

System design

comp.databases.filemaker comp.databases.filemaker


Discuss System design in the comp.databases.filemaker forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Carla
 
Posts: n/a

Default System design - 06-07-2007 , 08:18 AM






(This is not strictly a Filemaker question, BUT, because I intend to
use Filemaker (8.5, PC) for the development, I reckoned it would be a
good place to try.)

I'm about to start a major development for a company-wide information
system. Rather than just dive in and start working on layouts etc., I
need to do some pretty detailed design work - logical design and
physical design etc. Can anyone point me in the right direction for
some guidelines about how to do this? For example, I'd really like
some sample specifications that I could follow as examples. Any
ideas?

Thanks,

Carla.


Reply With Quote
  #2  
Old   
Carla
 
Posts: n/a

Default Re: System design - 06-08-2007 , 02:58 AM






On Jun 8, 8:30 pm, "Ursus" <ursus.k... (AT) wanadoo (DOT) nl> wrote:
Quote:
"Carla" <carla_sl... (AT) yahoo (DOT) co.uk> schreef in berichtnews:1181222280.156860.285370 (AT) m36g2000hse (DOT) googlegroups.com...





(This is not strictly a Filemaker question, BUT, because I intend to
use Filemaker (8.5, PC) for the development, I reckoned it would be a
good place to try.)

I'm about to start a major development for a company-wide information
system. Rather than just dive in and start working on layouts etc., I
need to do some pretty detailed design work - logical design and
physical design etc. Can anyone point me in the right direction for
some guidelines about how to do this? For example, I'd really like
some sample specifications that I could follow as examples. Any
ideas?

Thanks,

Carla.

You might try:http://www.foundationdbs.com/Downloa...FMPNovices.pdf

Ursus- Hide quoted text -

- Show quoted text -
Ursus - thanks for this - I had already seen this paper (I think it
was you that pointed me to it before!), and I think it has some
excellent advice. The section re. design is good, but if you can
think of anything more detailed, please let me know. I do appreciate
your help.

Carla.



Reply With Quote
  #3  
Old   
Ursus
 
Posts: n/a

Default Re: System design - 06-08-2007 , 12:06 PM




"Carla" <carla_sloan (AT) yahoo (DOT) co.uk> schreef in bericht
news:1181289489.211923.324040 (AT) n4g2000hsb (DOT) googlegroups.com...
Quote:
On Jun 8, 8:30 pm, "Ursus" <ursus.k... (AT) wanadoo (DOT) nl> wrote:
"Carla" <carla_sl... (AT) yahoo (DOT) co.uk> schreef in
berichtnews:1181222280.156860.285370 (AT) m36g2000hse (DOT) googlegroups.com...





(This is not strictly a Filemaker question, BUT, because I intend to
use Filemaker (8.5, PC) for the development, I reckoned it would be a
good place to try.)

I'm about to start a major development for a company-wide information
system. Rather than just dive in and start working on layouts etc., I
need to do some pretty detailed design work - logical design and
physical design etc. Can anyone point me in the right direction for
some guidelines about how to do this? For example, I'd really like
some sample specifications that I could follow as examples. Any
ideas?

Thanks,

Carla.

You might
try:http://www.foundationdbs.com/Downloa...FMPNovices.pdf

Ursus- Hide quoted text -

- Show quoted text -

Ursus - thanks for this - I had already seen this paper (I think it
was you that pointed me to it before!), and I think it has some
excellent advice. The section re. design is good, but if you can
think of anything more detailed, please let me know. I do appreciate
your help.

Carla.

Guidelines might be thinking about objects and attributes. Now this is
important and might get sticky.

An object as anything that may be used as seperate record. Like a person.
His name
Date of birth
Address
workplace

these all may belong to one object PersonData. Name, Date of birth etc are
attributes belonging to the PersonData Object. However a person easily may
have more then one address, like home and work. Now address becomes an
object. PersonData gets connected to AddressData. It is very important to
think through the whole process and establish wether information is an
attribute to something or an object. This might seem easy, but the more
complex your solution the more questions to answer.

Don't over use imported graphics
keep all buttons and layout objects the same (muted) color
Look at what others have done. Keep what you like, don't re-invent the
wheel.
And please come back with specific questions.

Ursus




Reply With Quote
  #4  
Old   
Ursus
 
Posts: n/a

Default Re: System design - 06-08-2007 , 02:30 PM




"Carla" <carla_sloan (AT) yahoo (DOT) co.uk> schreef in bericht
news:1181222280.156860.285370 (AT) m36g2000hse (DOT) googlegroups.com...
Quote:
(This is not strictly a Filemaker question, BUT, because I intend to
use Filemaker (8.5, PC) for the development, I reckoned it would be a
good place to try.)

I'm about to start a major development for a company-wide information
system. Rather than just dive in and start working on layouts etc., I
need to do some pretty detailed design work - logical design and
physical design etc. Can anyone point me in the right direction for
some guidelines about how to do this? For example, I'd really like
some sample specifications that I could follow as examples. Any
ideas?

Thanks,

Carla.

You might try:
http://www.foundationdbs.com/Downloa...FMPNovices.pdf

Ursus




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.