high and low level design

[ragnarok]

I have searched a lot and I haven't found anything. I want to do high level and low level designs so I can create a web site working cooperatively with a large number of people. I have already succeeded making applications using the structured paradigm and the object-oriented programming, using diagrams defined in the UML and some more, nevertheless I've never faced the web design and I don't know what sort of diagrams and design should I do.

I don't mean text color nor font face but a formal way to tell the others what must they do, what's expected of their code to do and what can they use to get that, also a way to divide huge sites in smaller portions of code that work together.

Sorry for my bad english and thank you.

[islanding]

Ragnarok Welcome,
   I am not sure what you are looking for? Although the work flow maybe a little different for the web good programming practices stay the same. First develop coding standards to cover these ares.

• Indenting
• Control Structures
• Function Calls
• Function Declarations
• Comments
• Including Code
• Code Tags
• Header Comment Blocks
• Using CVS
• Example URLs
• Naming Conventions

Have you decided what language you will use?

[ragnarok]

I have decided to use php and HTML. The coding standard isn't developed yet, but I have found several on the web that cover some of the areas you listed, also I have a java coding standard and I was planning to fit it to php in someway. Nevertheless I'm not very sure of how would be a coding standard for HTML and php mixed as they use to be.

What I'm looking for is the way to design a web from the client's requirements to a formal way to tell a group of people what they must do, for example in object oriented programming when you design a class, with it's attributes and methods, you can tell someone to make that class and that person should have a clear idea of the code that has to write.

If I'm right what I should do are the following steps:

• Client requirement analysis
• Software requirements schema (validation, inspection and approbation)
• High level design
• Software design specification (inspection and validation too)
• Integration plan
• Detailed design
• Unitary testing plan
• Detailed design inspection
• Testing development
• Coding, etc.

The names may differ as they are translated but I hope they are similar, I have also grouped some steps with parenthesis as they are related. The steps I find more difficult are high level design and detailed design.

Thank you.

[johnhask]

ragnarok:
As you pointed out, software programmers created the original workflow standard. Manipulate the tasks to accommodate the team members expertise and client's strict requirements.