Web Development
by pdhutch
by solrak29
It seems to me that the approach mentioned in the article is a means to define how you should architect a design...not nessisarilly a process. Though, there are fine steps explained for each layer in the architecture.
I've come from one sectorof the industry to another which brought me from a SEI Level 5 project where processes are the best practices and well defined to where (what I would say) SEI Level 0 process. In working in such a environment (the SEI Level 0 process) one would have to define some order out of the chaos. And its no fault of Software Engineers as the drive for "time to market" seems to push things. So this is what I do...
First, I try to voice my opinoin and advise people the purpose and benefits of a process.
Second, I document as much as possible as the documentation of such design process leads you to really think about what your about to develop or developing. But there is a delicate balance that has to be achieved so you are productive in thelight of management. So here are my steps:
1. Create a directory with the project or major functional name.
2. Create my Concept document which defines what is required from the busniness point of view. Any question are directed at the rightpersonel.
2. Create my Function Spec (SRS) the defines what I have to do.
3. Architect the approach (this is where this articles process comes in handy ) if applicable.
Architecture document...
4. Design my approach. Design document. with documentation on how I would test what I am building.
5. Implement and test code.
Nothing formal here though I try to keep my layout of documents consistent and using diagrams from a specified standard (i.e. UML).....and sometimes everything can fit within one document.
This also helps when questions arrise about something I developed a year ago. I can just review the documentation and jog my memory.
by watermt
This discussion is closed to new replies.
Sort by Trending