Dear sharepoint users and fellow developers,
I have recently started out to make System Analysis and Design for a project based on Sharepoint. You are aware that normally a typical deliverables for SAD are Use case diagrams, state charts, class diagrams etc.
How should I do my documnetation for a project based on Sharepoint. I doubt this because, Sharepoint has inbuilt templates and classes that we use and more importantly we can make sites on a mouse-click. So now, I don’t have any classes or database that I am making or working with explicitly so these typical deliverables will be difficult for me to deliver.
Can you please advise me how should I go about doing some good and resonable SAD for my project or am I completely wrong.
Any leads will be helpful.
i think you already know that you should not be worry about the interface or clicking or mouse right now,
these all things take about half paper in the documentation,
just start with the requirement , use case (“basic flow, pre-condition, post-condition) , sequence diagram..
don’t think. just write and every thing else will be easy to do in the documentation sequence ..
by: ZERO COOL
on: 6th February 08