Book a Demo

Author Topic: Systems Development Methodology  (Read 3117 times)

rescobar

  • EA User
  • **
  • Posts: 69
  • Karma: +0/-0
  • Viva Bolivia
    • View Profile
Systems Development Methodology
« on: April 09, 2003, 01:50:42 pm »
How do you think about a VS.NET IDE software design and
modeling all objects?
Where do you think is the "mid-point" between a good modeling
practices and rapid development?
What do you think is the "correct" methodology?

I do the following:

Vision
Requirements
Architecture
Use Cases
Analysis Diagramas for Use Cases
DataBase modeling (using SQLServer 2000 diagrams)
Reverse database into Model
Programming using IDE
Reverse programs into Model
Refine code and model in a iterative manner.
Every relevant Use case should have at least: Analysis Diagram,
Sequence Diagram and Class Diagram
What do you think?
Thanks in advance
Sergio Escobar
[email protected]