Mission and Proposal

The proposal requires diagrams.

What sort of diagrams do we want?
Bryce - do you have ideas about the architecture that we should show in a sequence diagram?

Pamazon wrote:The proposal requires diagrams.

What sort of diagrams do we want?
Bryce - do you have ideas about the architecture that we should show in a sequence diagram?

Well, a use case might be helpful. I take it they didn't have any examples of reports or code right?

The sequence diagram would be the perfect place to show how we plan to architect our system.
I was thinking we should use the Model View Presenter framework, since that's particularly well suited to .NET programming.
We should show how the user enters information through the View (Code Behind), which is then passed to the Presenter which gets and sets data via the Controller.
I'm not sure if you used this pattern in your coop Pam but its basically that the Controller is the closest link to the data layer, while the Presenter handles most of the coding logic, and the View is the basic pathway of information from the UI to the presenter.

Let me know what you think!

Bryce,

I am not familiar with Model View Presenter framework. It sounds similar to what I did, but I think is slightly different ( or maybe not).
It sounds like a 3 tier model. Is the view layer an interface?

The pattern we used:
Presentation Layer(UI and asp codebehind),
Business Logic Layer (validation, applies logic, error handling),
Data Access Layer (talks to the database, loads datasets)

After reading further, I believe they are pretty much the same thing, different buzz-words

Pamazon wrote:Bryce,

I am not familiar with Model View Presenter framework. It sounds similar to what I did, but I think is slightly different ( or maybe not).
It sounds like a 3 tier model. Is the view layer an interface?

The pattern we used:
Presentation Layer(UI and asp codebehind),
Business Logic Layer (validation, applies logic, error handling),
Data Access Layer (talks to the database, loads datasets)

After reading further, I believe they are pretty much the same thing, different buzz-words

lol! Yes I believe you caught me using buzzwords again!
While they are basically the same thing, I believe the MVP works slightly different in that the Presenter actually calls methods in the code behind and the Controller. I think it tends to make the finished product a bit more extensible, but it is not a requirement for us.

I will feel happy sticking to the 3-tier idea if that's something everyone can easily grasp.

On another note, I'm about half way through writing up our team charter for Docus (ORGB). It will need some editing and input from the rest of the group though. I'll post an update in my section and send it out in an email when I'm done.

ttyl!

I've gone through it and made some edits. Sending an email to Pam with them now.

I used the comment feature, so just use mine as a reference and update a master copy. I find thats the easier way to work, not sure how it will work for you.


Dinner! So late.....