• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Opting for a domain-specific approach versus data-driven design with code igniter

#11
[eluser]Randy Casburn[/eluser]
You can chain controllers too. But lest there be blasphemy in the air I dare not say further words nigh.

:gulp:

#12
[eluser]beemr[/eluser]
[quote author="beemr" date="1219278840"]So, what are the big frameworks behind domain design? It's my understanding that .NET is trying to release its own MVC pattern. Are they giving up on domain-based design? Is there an Open Source community that pushes the domain approach?[/quote]

According to Wikipedia, Coldfusion Markup Language is a Domain Specific Language. Egads.

#13
[eluser]meovino[/eluser]
[quote author="Jay Callicott" date="1219219312"]I wish we mocked up everything at my full time job like we do in my part-time job. The 2 approaches are very different. At work we rarely get any mockups but often get pretty detailed specs from the PM with sometimes a UML diagram which is certainly helpful. I think visually so I prefer PSD mockups like we do consistently with my part-time business.[/quote]

Mockups are always worth the time spent doing. If your full-time employer doesn't mind spending some money, look into a tool like Axure. I'm still in our demo period, but we are already writing up the PO to buy five licenses of it. The amount of time it's saving us farther downstream is well worth $539/seat. There's nothing like putting a client in front of a wireframe they can interact with. All those hidden requirements start surfacing quickly (instead of coming up during user acceptance testing).

For large projects, use cases are worth the time and effort. We've never been able to get decent requirements out of our clients without them.


Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2019 MyBB Group.