In an MVC or MVP Project the obvious usage reason is to break down tasks among the various aspects of the architect.  In either model view controller or model view presenter there are three specific areas in which tasks need performed.  Depending on team size the breakdowns can occur in various ways.  The example below is one way to break down the tasks.  I hopefully will dredge up some time and list out other scenarios that can be met with this architecture.  This however is the most straight forward and obvious development method usage of MVP and MVC.

Task:  There is a need for a new screen that will contain interfacing to data within the database.  The screen has at least 2-3 buttons and a good number of text boxes, drop downs, and or any other development elements needed.  This screen needs put in place ASAP with validation, logging, and all the plumbing of the pattern that is in use (MVC or MVP).

Team Staff (Medium Size):  Business Analyst, Senior Developer (Patterns Guru), Intermediate or New Developer, and a Database Developer.

• Model – BA & Senior Developer should work on this element.- View – Inter/New Developer.  The view gives the basic overview of business logic and also give a good starting point working with MVC & MVP because any developer knows how to develop a screen.- Controller / Presenter – Database Developer should work on this element.  If a database developer works with the dev team in a scenario like this, he inherently should work on the aspects of development that he is most familiar with, thus the aspects that are closest to the data.

Team Staff (Large Size):  Senior Developer (Patterns Guru), 5 Intermediate Developers ranging from straight out of college to 1-2 years of experience.  These silos that each dev group works in after a short period will make this a very fast method to develop new features with.  Only breaking out developers in such a way and allowing actual specialization of labor to occur can one really get the full benifit of this architecture.  So break the groups up, allow some cross training, but primarily focus on specialization if you need speed of development.

• Model – Senior Developer & 2 Intermediate Developer- View – 1 Intermediate Developer- Controller / Presenter – 2 Intermediate Developers.

Team Staff (Small Size):  Senior Developer (Patterns Guru), 1 Intermediate Developer.  One could say, “We’ll meet in the middle!”

• Model – Senior Developer- View – Intermediate Developer- Controller / Presenter – Senior Developer & Intermediate Developer

So if anybody reads any blogs on .NET then ya know 3.0 is out.  3.0 is really nothing more than additional parts tacked onto 2.0.  So with that I wanted to toss a kewl link up that is relative to learning and knowing 3.0 like we all know and love 2.0.

Windows SDK Blog

The Windows SDK Blog is rather cool and recently Karin Meier posted an entry with a whole BUNCH of samples for .NET 3.0.  Specifically…

• 430 Windows Presentation Foundation samples
• 140 Windows Communication Foundation samples
• 60 Windows Workflow Foundation samples
• 200 New to Vista (Win32/COM-based) samples
• 23 Cross technology samples

…more links to come.

So it’s annoying and seems to pop up regular while working with SmartParts in CAB/SCSF Apps.

If you get this…

…close the SmartParts and rebuild the solution. All will be well when done.

del.icio.us tags: CAB, Composite UI Application Block, SmartPart, WinForms

LiveJournal tags: CAB, Composite UI Application Block, SmartPart, WinForms

Technorati tags: CAB, Composite UI Application Block, SmartPart, WinForms

So some awesome things have been going on the work front.  The major thing is that I’m finally starting to understand certain patterns in our architecture.  Some of them I understood better than I realized.  Because of odd and not particularly straight forward requirements for usage of the patterns I ended up heading down the wrong path on a few scenarios.  Now that I’m back on road I’ve been moving forward rapidly with the rest of the team and will prospecively be able to provide more assistance in the near future.

One of the other awesome things is our team now has an insignia and team name.  It’s odd, a little strange, and not all that normal for a software development team to have such but it’s cool.  Period.

With that I present…

So I setup a basic and quick rendering of the Travel Tracker Application so that I could get some of my initial prospective users to work with the Web Application Version of it.  Post prototype I will get a authenticated roles based version up and running.  One other thing I have decided to do during the creation of this application is to integrate it into the existing Community Server Web Application that I am running for my own website.

The current integration seems to use ASP.NET 2.0 Membership features thus it looks to be an easy integration.  Hopefully I’ll have it up for others to play with and test soon!

Here are some screen shots of what I’ve got working so far.