Urgent Help Needed
Chris Soong
Greenhorn
Posts: 6
posted 13 years ago
I need help in developing a java application. I'm supposed to develop a management system for a country club as an assignment. This system should include the usual add/delete/update functions for member's information. A booking module should also be included, to enable members to book their favourite sporting facilities online. This will be linked to the member's account in the database.
The problem is, I don't know where to start and I've only got a few days to complete it. Is it very difficult to do?
The problem is, I don't know where to start and I've only got a few days to complete it. Is it very difficult to do?
Gary Joehlin
Greenhorn
Posts: 16
posted 13 years ago
When did you commit to having it done?
Do you have a database with information already? (Or, does it need to be developed/designed?) What database are you going to use?
What platform are you going to run this application on?
What tools do you have to develop the application code?
Let's start there.
Regards,
Gary Joehlin
Do you have a database with information already? (Or, does it need to be developed/designed?) What database are you going to use?
What platform are you going to run this application on?
What tools do you have to develop the application code?
Let's start there.
Regards,
Gary Joehlin
Chris Soong
Greenhorn
Posts: 6
posted 13 years ago
When did you commit to having it done?
A month ago
Do you have a database with information already? (Or, does it need to be developed/designed?) What database are you going to use?
Information can be added later. Just need the shell of the database. SQL is the preferred choice.
What platform are you going to run this application on?
Windows
What tools do you have to develop the application code?
I currently have netbeans and realj.
A month ago
Do you have a database with information already? (Or, does it need to be developed/designed?) What database are you going to use?
Information can be added later. Just need the shell of the database. SQL is the preferred choice.
What platform are you going to run this application on?
Windows
What tools do you have to develop the application code?
I currently have netbeans and realj.
Gary Joehlin
Greenhorn
Posts: 16
posted 13 years ago
What is the target date to have the project finished?
You can't have a shell of a database, you must design it to account for all the user requirements, now, otherwise you'll have a design and implementation mess in the future.
SQL is a language, not a database, to extract and work with data in a realtional database.
What is the name of the database that you will be using, windows is not a database. Are you saying you are going to use MS-Access? Or some other, be specific.
Regards,
Gary J.
You can't have a shell of a database, you must design it to account for all the user requirements, now, otherwise you'll have a design and implementation mess in the future.
SQL is a language, not a database, to extract and work with data in a realtional database.
What is the name of the database that you will be using, windows is not a database. Are you saying you are going to use MS-Access? Or some other, be specific.
Regards,
Gary J.
Chris Soong
Greenhorn
Posts: 6
posted 13 years ago
What is the target date to have the project finished?
Target date is 30th of September.
You can't have a shell of a database, you must design it to account for all the user requirements, now, otherwise you'll have a design and implementation mess in the future.
I'm not really worried about the future of this system, just need to show it for the time being.
MS-Access
Target date is 30th of September.
You can't have a shell of a database, you must design it to account for all the user requirements, now, otherwise you'll have a design and implementation mess in the future.
I'm not really worried about the future of this system, just need to show it for the time being.
MS-Access
posted 13 years ago
Well, since the only question you have asked is
Is it very difficult to do?
That all depends on your skill level.
I am assuming this is going to be a SWING Desktop application? Or is it going to be a Web Based application?
Either way, it will not only take knowledge of the JDBC API but also either the SWING API or the J2EE (JSP/Servlets).
I would say that at this point if you aren't even sure where to begin, you are in trouble. That is unless you already know how to use the technoogies you need and just aren't sure where to start. If that is the case, I would recommend setting up your database schema. Get all your tables together with all the columns you think you will need.
Next, decide on the relationships between all your tables so that your aren't storing redundent information all over the place.
Next, define all the forms you will need. This will help you build the user interface (whether it is SWING or J2EE).
Next, start writing the code.
[ September 24, 2003: Message edited by: Gregg Bolinger ]
Is it very difficult to do?
That all depends on your skill level.
I am assuming this is going to be a SWING Desktop application? Or is it going to be a Web Based application?
Either way, it will not only take knowledge of the JDBC API but also either the SWING API or the J2EE (JSP/Servlets).
I would say that at this point if you aren't even sure where to begin, you are in trouble. That is unless you already know how to use the technoogies you need and just aren't sure where to start. If that is the case, I would recommend setting up your database schema. Get all your tables together with all the columns you think you will need.
Next, decide on the relationships between all your tables so that your aren't storing redundent information all over the place.
Next, define all the forms you will need. This will help you build the user interface (whether it is SWING or J2EE).
Next, start writing the code.
[ September 24, 2003: Message edited by: Gregg Bolinger ]
Gary Joehlin
Greenhorn
Posts: 16
posted 13 years ago
MS-Access, is rather limited in its ability to do certain things, however to its credit you can do some things with it by using the wizards to design forms (the output from a query), desing queries (although i find that more confusing than writing the SQL manually) and you have tools (wizards) that can help you load, very slowly, record by record manually, the database.
Yes, you could write application code to interface with that, however, you don't have the time, dude.
This quickie plan will allow you to have a single user the one that the database is located on. And for heaven's sake, make back ups of all your work, even the data. ANd when it's 'production', make sure that they, or you, back up their data, on a regular basis, dude.
Don't code anything yet!!! (Now is the time to plan and understand your data) DESIGN FIRST BEFORE CODING OTHERWISE, YOU"LL BE CODING TO CORRECT A Y 10K problem.
I.Design the database, if it isn't already:
What elements do you need? (What fields of information) (One important thing to keep in mind: Arrays are NOT our friend in a relational database, so don't design them in put them in another table and have a key that ties the two tables together so that you can find the info between them when needed) This also means, no group occurs "X" number of times either, it's the same (bad) design.
II. associate these elements into their respective tables (and give these tables a short but meaningful name. Oh, don't put everything in a single table, depending on the number of elements, you may want several tables. PUt the data in their respective tables, ie. MEMBERS (only membership information, name, addresses, phone numbers, membership number, expiration of membership, etc.), FACILITY (name of facility, days that it's available (to make it simple, plan 7 pairs of time (open / close) one for each day of the week.), a key (to identify the facility- simple numeric is ok), location (address or other identifiers), telephone number, cost, etc., SCHEDULE (this table is the cross between the MEMBERS and FACILITY table), it will contain entries when a member schedules a facility, but only if the request is within the date/time when the facility is available.
Other issues to consider: What is the maximum number of users to a Facility at any given time? (that's a design consideration), Delete and reschedule, Blocking holidays, etc.
== review design with user ==
II. Determine what functions you want to provide and what reports and screens you want to have.
II a. Do all the functions and reports and screens have all the data elements in part I defined or are any missing? Then, put them in the right place.
== review with user ==
III. Use the MS-Access wizard to define the tables.
User proper data types (use 'date' for things that are dates, don't use char types in any realtional database
IV. Use the wizard to create the relationships and reports and screens.
== review with user ==
V. Load starting data into the tables.
VI. MAKE A BACK UP OF DATA AND DEFINITIONS.
== review with user ==
VII. TEST and TRAIN USER
VIII. MAKE BACK UPs a regular thing.
Hope this helps.
Gary Joehlin
Yes, you could write application code to interface with that, however, you don't have the time, dude.
This quickie plan will allow you to have a single user the one that the database is located on. And for heaven's sake, make back ups of all your work, even the data. ANd when it's 'production', make sure that they, or you, back up their data, on a regular basis, dude.
Don't code anything yet!!! (Now is the time to plan and understand your data) DESIGN FIRST BEFORE CODING OTHERWISE, YOU"LL BE CODING TO CORRECT A Y 10K problem.
I.Design the database, if it isn't already:
What elements do you need? (What fields of information) (One important thing to keep in mind: Arrays are NOT our friend in a relational database, so don't design them in put them in another table and have a key that ties the two tables together so that you can find the info between them when needed) This also means, no group occurs "X" number of times either, it's the same (bad) design.
II. associate these elements into their respective tables (and give these tables a short but meaningful name. Oh, don't put everything in a single table, depending on the number of elements, you may want several tables. PUt the data in their respective tables, ie. MEMBERS (only membership information, name, addresses, phone numbers, membership number, expiration of membership, etc.), FACILITY (name of facility, days that it's available (to make it simple, plan 7 pairs of time (open / close) one for each day of the week.), a key (to identify the facility- simple numeric is ok), location (address or other identifiers), telephone number, cost, etc., SCHEDULE (this table is the cross between the MEMBERS and FACILITY table), it will contain entries when a member schedules a facility, but only if the request is within the date/time when the facility is available.
Other issues to consider: What is the maximum number of users to a Facility at any given time? (that's a design consideration), Delete and reschedule, Blocking holidays, etc.
== review design with user ==
II. Determine what functions you want to provide and what reports and screens you want to have.
II a. Do all the functions and reports and screens have all the data elements in part I defined or are any missing? Then, put them in the right place.
== review with user ==
III. Use the MS-Access wizard to define the tables.
User proper data types (use 'date' for things that are dates, don't use char types in any realtional database
IV. Use the wizard to create the relationships and reports and screens.
== review with user ==
V. Load starting data into the tables.
VI. MAKE A BACK UP OF DATA AND DEFINITIONS.
== review with user ==
VII. TEST and TRAIN USER
VIII. MAKE BACK UPs a regular thing.
Hope this helps.
Gary Joehlin
Chris Soong
Greenhorn
Posts: 6
posted 13 years ago
Thanks guys, your advice really helps alot. At least now I know where to start first.
