Member Avatar for Andrew Minus

Hi there,
I was thinking about which program design methods is better than any other methods.But, i am interesting Jason's Structure Diagram more than others . !!

  • 4 Contributors
  • 3 Replies
  • 124 Views
  • 15 Hours Discussion Span
  • Latest Post Latest Post by jwenting

Dani AI

Generated

If the choice is between Jackson-style structure diagrams and a more object-oriented/UML approach, pick the tool that matches the problem, not personal preference. is right that Jackson-style diagrams give a clear, testable mapping when the program is driven by fixed input/output records (batch transforms, file processors). They make the flow explicit and reduce accidental complexity for that class of problems. They are less natural for typical Java apps where the domain is better expressed as interacting objects, services, or UI events.

Decide by the primary source of complexity. If your system is mainly about transforming well-structured data, Jackson-style design can shorten the path from spec to code. If the system is about behaviors, identities, relationships, or reactive flows, use OO modeling (UML, domain modeling, or DDD patterns), plus small, focused diagrams. Also weigh team skill and maintenance: a heavy process nobody understands will slow you down, as warned.

A simple, practical workflow: (1) write a one-paragraph context and the top 3 use cases; (2) identify whether complexity lives in data shape or behavior; (3) sketch a single-page architecture (data-flow or component/class view as appropriate); (4) turn key decisions into a short ADR and tests; (5) iterate and keep diagrams small and current. For larger teams, agree on boundaries and use automation (build checks, tests, CI) so diagrams stay useful rather than dusty.

This ties and together: tailor the structure to your project, but make it explicit and maintainable. In short: use Jackson where data structure dictates control, use OO/UML for behavior-rich Java systems, and avoid any method you or your team cannot apply consistently.

Recommended Answers

All 3 Replies

Member Avatar for server_crash

I think it's better to follow your own design structure. However, for bigger projects you probably need a detailed diagram of how things work and stuff like that, because it's hard to sit down and code something big. I'd say the most important thing is making a layout of all the clasess you want, and the functions, members that are in those classes.

Member Avatar for freesoft_2000

Hi everyone,

I think it's better to follow your own design structure.

I agree a 100%

Richard West
*****************************************************

Member Avatar for jwenting

Any process is better than no process with the exception that using a process you don't understand is a sure way to disaster.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.