RUP, XP, Waterfall play great roal in large software projects, and we must choose the right process and modify it correctly in a certain project. But is it important when design or develop website? Or there is no cooperative work need to do when designning or developing website?

Reply

for small website, there don't need software process, for large website, I think it need, but RUD,XP or waterfall may not suitable, web site need its own website process, I have this idea form year 2000. new technology is emerging, the process may chenge, a process will not always right.
what do you think?

Reply

What is a software process? Never heard of it...

Reply

Software process is a set of methods, standard, procedure and framework used in software development. The goal of software process is to deliver the software products in time with high quality and reasonable cost.

The website for Extreme Programming:
www.extremeprogramming.org
www.xprogramming.com

The website for Rational Unified Process(RUP):
http://www-306.ibm.com/software/rational

The CMM (model used to improve the software process):
http://www.sei.cmu.edu/cmm/

Reply

I totally agree with you:
First, new technology drives the process. When waterfall model came out, the project managers lead the projects in confidence. With the innovation of network, the processes such as PSP, TSP, XP, RUP or others are used. When I joined the computer conferences, I found that many people are now conducting the research of automatic coding: the customer could then use UML or similar entity to build their own business. I wonder if the process currently should consider such tendency.
Second, no process is always right. Normally the process should be modified to be used in a specific project. Sometimes there will be several processes model used in one project.

I haven't been involved in a website/webservice project, and I want to know the real world in projects. If possible, would you tell me something in your development.

 

 

 

Reply

In the real world applications, usually there will be a requirement gathering stage. After gathering the requirement, the architect will transform the requirement into a set of use cases for the entire system. From each of the use cases, he will built a sequence diagram and/or state diagram if needed. Then based on these diagram the architect will build the component diagram using the some well known design patterns, such as session facade, command pattern, DAO (data access object) pattern, and maybe O/R mapping also. Usually those diagrams and the entire architecture will be discussed with team members for knowledge transfer and maybe further tuning based on feedback from the teammates. A class diagram will then be created from the architecture and code development will then be started. Further refinement will be needed usually in the implementation phase, because usually the first iteration of requirement gathering stage is not enough.

Reply