Analysis and design

HI

I am not sure if I am in the right section, but could someone
please refer me to a practical example with documentation to SDLC, which includes DFD and ERD etc ...please


Thanks in advance
Diddy

There are many software develeopment models. For eg. Waterfall model, rapid prototype, Agile/XP model etc. Can you tell me which SDLC model you prefer or planning to use?

Hi

The Waterfall model please.....

Thanks

I am not sure how much you will find a whole single document the SDLC of the Waterfall model.

Waterfall is devided into main sections

- Analysis
- Design
- Implmentation
- Testing
- Maintenance

Now usually you can find documents and templates for each of these sections individually.

Here is a page from google that will help you understand better the concept of the Waterfall model. It is simple but to the point.

http://scitec.uwichill.edu.bb/cmp/online/cs22l/waterfall_model.htm

Regarding documents. As much as I know, different stages contain different documentation. In the Analysis section I would place a lot of Use Case Models, while in the Design Stage I would place a lot of Class Diagrams. On google you can find a lot of example on how these can be made.

Use Case Diagrams UML2.0
http://www.developer.com/design/article.php/2109801

Class Diagrams UML2.0
http://pigseye.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/class.htm

hope the above helps,

regards,
sim085

Apart from the excellent infos from sim085 you can also look at IBM's Developerworks site, which has a lot of infos about use case diagrams and software engineering (thanks to Rational software ), see Use cases, an introduction and Getting from use cases to code Hope this helps

If this is for an academic assignment then google should be able to dig up something suitable. However if you are planning on running a waterfall project then I would urge you to think again. The waterfall process will generally result in a project that is late, expensive, error prone and ends up with a product that does not do what the users need. It is based on a fantasy that you can specify everything up front and plan out the development in detail. This is simply untrue. Managers like it because it gives the illusion of control so there are still huge numbers of projects that use some variation of it, often with disasterous results.

I suggest you look into alternative agile methodologies such as Extreme Programming (XP), Scrum, DSDM, adaptive development etc. You can find a wealth of articles on the Agile Alliance website, including some that explain in detail why the waterfall process is so bad.

Dave

Thanks to everyone that commented...I appreciate it

Diddy