Steps to develop a s/w Project

Hi,

Am developing a project using netbeans4.1 and tomcat 5.5.9. It is website with Oracle9i but i dont know from where to start about project. Some say abt SCM(Software configuration management) some say abtFactory Methods other say first make UML. Plz tell mewhat are the steps to develop a website or java project. Is there any guidelines that we have to follow. I got totally confused any suggestion would be helpfull.

Thanks in advance....

[479 byte] By [vikramjitsingha] at [2007-10-2 1:48:07]
# 1

It depends on what you would like to achive - you first need to clear up your requirements. I guess you don't have some deeper knowledge about what these words (UML, Factory Methods, etc.) mean, do you? So, you better start reading yourself through some papers about Java Server Pages (JSP), Struts, Web Services, Servlets. Then you will get an idea how can start. Read this:

[url=http://java.sun.com/webservices/docs/1.5/tutorial/doc/index.html]The Java Web Services Tutorial[/url]

MartinHilperta at 2007-7-15 19:29:20 > top of Java-index,Other Topics,Patterns & OO Design...
# 2
Hi,Yours requirements.Your JSP.Your Database model.At this moment you could think in JSF, etc
barbywarea at 2007-7-15 19:29:20 > top of Java-index,Other Topics,Patterns & OO Design...
# 3
http://www.google.com/search?hl=en&q=software+design+methodology&btnG=Google+Search- Saish
Saisha at 2007-7-15 19:29:20 > top of Java-index,Other Topics,Patterns & OO Design...
# 4

Hi,

Now i got the idea how to start with project development....this is given by Scott i wanna share with you...

few suggestions:

1. Keep your modeling efforts simple. See Agile Requirements Best Practices.

2. If you think you'll have a lot of pages, then you should consider a UI flow fiagram to "map out" what your site will look like.

3. I'd consider drawing UI screen sketches to design your pages.

4. Some sort of understanding of how people are going to use your system is critical to your success. Consider informal use cases for this. Many people get hung up on use cases because they go into bureaucratic documentation mode and create overly detailed formal use cases.

5. Implement your system in URL=http://www.agilemodeling.com/essays/changeManagement.htm]priority order[/URL].

6. You don't need to identify all the details up front. Get the high level idea in the beginning and then model storm the details on an as needed basis.

- Scott

vikramjitsingha at 2007-7-15 19:29:20 > top of Java-index,Other Topics,Patterns & OO Design...
# 5

A) Get hello world application working for your target platform.

B) Write a test that shows application doesn't solve your problem.

C) Make test pass.

D) Goto B)

Writing tests first helps developing classes with clean interfaces.

Clean interfaces improves design.

jhhdka at 2007-7-15 19:29:20 > top of Java-index,Other Topics,Patterns & OO Design...