How to prepare a major .Net development

[Dan]

Hi,

The company I work for is planning to modify a large financial application
running on the mainframe. The modifications include switching from IMS to DB2
and make the business logic accessible from web-based applications. The main
orientations for that project are to rely on .Net and to use web services as
much as possible to achieve the goal.

Since our company is new to .Net developments, I'm looking for guidelines,
best practices and/or a checklist of all the important topics to cover in the
technical architecture ot that new project (presentation layer standards,
user authentication, web services and UDDI principles, communication
protocols, reporting, etc. ).

If you have good references that could lead me to interesting documents,
please let me know.

Thanks in advance.

Dan

[Cowboy (Gregory A. Beamer) - MVP]

Dan:

I would consider talking to a .NET architect to help design the initial
specs. It would also be good to get a trainer in for your devs to get them up
to speed (both may or may not be the same person).

As far as best practices, look at http://msdn.microsoft.com/architecture and
look at the patterns and practices sections. There are numerous books on a
variety of topics.
---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

"Dan" wrote:

Hi,

The company I work for is planning to modify a large financial application
running on the mainframe. The modifications include switching from IMS to DB2
and make the business logic accessible from web-based applications. The main
orientations for that project are to rely on .Net and to use web services as
much as possible to achieve the goal.

Since our company is new to .Net developments, I'm looking for guidelines,
best practices and/or a checklist of all the important topics to cover in the
technical architecture ot that new project (presentation layer standards,
user authentication, web services and UDDI principles, communication
protocols, reporting, etc. ).

If you have good references that could lead me to interesting documents,
please let me know.

Thanks in advance.

Dan

[Dan]

Thanks for the advice.

I already looked at the content published in the architecture center. There
is a lot of things in there. To speed up the work, I try to find an
exhaustive list of topics that need to be covered before doing more extensive
search in MSDN.

"Cowboy (Gregory A. Beamer) - MVP" wrote:

Dan:

I would consider talking to a .NET architect to help design the initial
specs. It would also be good to get a trainer in for your devs to get them up
to speed (both may or may not be the same person).

As far as best practices, look at http://msdn.microsoft.com/architecture and
look at the patterns and practices sections. There are numerous books on a
variety of topics.
---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

"Dan" wrote:

Hi,

The company I work for is planning to modify a large financial application
running on the mainframe. The modifications include switching from IMS to DB2
and make the business logic accessible from web-based applications. The main
orientations for that project are to rely on .Net and to use web services as
much as possible to achieve the goal.

Since our company is new to .Net developments, I'm looking for guidelines,
best practices and/or a checklist of all the important topics to cover in the
technical architecture ot that new project (presentation layer standards,
user authentication, web services and UDDI principles, communication
protocols, reporting, etc. ).

If you have good references that could lead me to interesting documents,
please let me know.

Thanks in advance.

Dan

[pm]

Microsoft has a book about project management now that might be of help check
out your favorite online bookstore.

"Dan" wrote:

Thanks for the advice.

I already looked at the content published in the architecture center. There
is a lot of things in there. To speed up the work, I try to find an
exhaustive list of topics that need to be covered before doing more extensive
search in MSDN.

"Cowboy (Gregory A. Beamer) - MVP" wrote:

Dan:

I would consider talking to a .NET architect to help design the initial
specs. It would also be good to get a trainer in for your devs to get them up
to speed (both may or may not be the same person).

As far as best practices, look at http://msdn.microsoft.com/architecture and
look at the patterns and practices sections. There are numerous books on a
variety of topics.
---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

"Dan" wrote:

Hi,

The company I work for is planning to modify a large financial application
running on the mainframe. The modifications include switching from IMS to DB2
and make the business logic accessible from web-based applications. The main
orientations for that project are to rely on .Net and to use web services as
much as possible to achieve the goal.

Since our company is new to .Net developments, I'm looking for guidelines,
best practices and/or a checklist of all the important topics to cover in the
technical architecture ot that new project (presentation layer standards,
user authentication, web services and UDDI principles, communication
protocols, reporting, etc. ).

If you have good references that could lead me to interesting documents,
please let me know.

Thanks in advance.

Dan

[Nick Malik]

Hi Dan,

Gregory Beamer is right... you need an architect. Building this without
experienced advice, "on the cheap" will cost you a LOT more in the long run
than getting a little help up front.

What you are doing is "extending" your mainframe app. There are a number of
companies that specialize in products that can help, depending on the type
of mainframe app you have.

Check out products from WRQ, Attachmate, and (my favorite) HostBridge.
Also, consider calling up IBM to discuss the use of WebSphere MQ to create a
messaging platform.

This is an expensive and time consuming process. A mistake now will cost
you dearly. Doing this by reading text documents is like trying to perform
major surgery after reading a basic anatomy textbook.

Get an architect, preferable someone familiar with both .NET and your kind
of environment.

--- Nick

"Dan" <Da*@discussions.microsoft.com> wrote in message
news:F0**********************************@microsof t.com...

Thanks for the advice.

I already looked at the content published in the architecture center. There is a lot of things in there. To speed up the work, I try to find an
exhaustive list of topics that need to be covered before doing more extensive search in MSDN.

"Cowboy (Gregory A. Beamer) - MVP" wrote:

Dan:

I would consider talking to a .NET architect to help design the initial
specs. It would also be good to get a trainer in for your devs to get them up to speed (both may or may not be the same person).

As far as best practices, look at http://msdn.microsoft.com/architecture and look at the patterns and practices sections. There are numerous books on a variety of topics.
---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

"Dan" wrote:

Hi,

The company I work for is planning to modify a large financial application running on the mainframe. The modifications include switching from IMS to DB2 and make the business logic accessible from web-based applications. The main orientations for that project are to rely on .Net and to use web services as much as possible to achieve the goal.

Since our company is new to .Net developments, I'm looking for guidelines, best practices and/or a checklist of all the important topics to cover in the technical architecture ot that new project (presentation layer standards, user authentication, web services and UDDI principles, communication
protocols, reporting, etc. ).

If you have good references that could lead me to interesting documents, please let me know.

Thanks in advance.

Dan