• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • salvin francis
  • fred rosenberger

Tell me the truth please.

 
Ranch Hand
Posts: 60
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Do you guys design all the class diagrams and sequence diagrams before coding? or just like me, get a general idea of class and then coding quickly?
 
Bartender
Posts: 2292
3
Eclipse IDE Spring Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hehehe I like the title of your topic!

Well champion, honestly, I just started coding without creating any diagram first. I see that sometimes it is a "must" (due to the policy of the company you work for, for instance)... or you may want to come up with a class/sequence diagram before coding in order to guide your development. Although most of the time it is a good idea to have a class diagram (to document your design and help future maintenances), it isn't really necessary to create one for the assignment. I myself didn't create any diagram, but if you feel more comfortable creating a diagram before coding, feel free!
 
Sheriff
Posts: 11604
178
Hibernate jQuery Eclipse IDE Spring MySQL Database AngularJS Tomcat Server Chrome Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No diagrams for me, just a whole lot of thinking and discussing, resulting in the design I wanted to implement. And then: just do it
 
Jianping Wang
Ranch Hand
Posts: 60
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Recently I am running into a trouble for my company projects: I have 12 Dao, and every Dao has an interface, so 24 classes/interface. That's just persistence layer. In my present layer, Struts, I have to create 12 Forms and 12 domain classes. And what's more there is one class has 32 variables, all have to be validated and converted!!
So that's why I want a clear plan before coding. I read this article http://www.ibm.com/developerworks/java/library/j-genericdao.html to reduce number of classes. And still looking some other design solutions for my situation. And begin draw UML because of the trouble I just mentioned.
 
Roel De Nijs
Sheriff
Posts: 11604
178
Hibernate jQuery Eclipse IDE Spring MySQL Database AngularJS Tomcat Server Chrome Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Jianping Wang wrote:Recently I am running into a trouble for my company projects: I have 12 Dao, and every Dao has an interface, so 24 classes/interface. That's just persistence layer. In my present layer, Struts, I have to create 12 Forms and 12 domain classes. And what's more there is one class has 32 variables, all have to be validated and converted!!


The SCJD assignment certainly will not be that huge: 1 dao will result in 2 files (1 class and 1 interface). And your model class (if you create one) will have 6-7 properties. If you just work with the String[] you won't have a model class.
 
incandescent light gives off an efficient form of heat. You must be THIS smart to ride this ride. Tiny ad:
Devious Experiments for a Truly Passive Greenhouse!
https://www.kickstarter.com/projects/paulwheaton/greenhouse-1
    Bookmark Topic Watch Topic
  • New Topic