Loose Coupled Architecture
-
Can anyone give me suggestions on the following I need to put in place an architecture which has the following prime features Assume Company X's IT Team A 1) Team A has many .NET projects lined up, Web, Windows, Services, WPF etc.. 2) For Web based projects... Team A requires the same look and feel for all projects. 3) Requirement : UI elements such as Master pages, js , css etc should not be copied over to every new project(No duplicate copies in each project) 4) Requirement : There should be a central repository kind of project/files/ etc.. which will serve as UI framework for all projects 5) Requirement : Data Access for all projects should also be driven by the same concept. One project drives data to all other projects For Data I can think of a Service. I am just not sure of how to get the architecture for the UI as mentioned above, Can someone recommend me what is the best approach. Thank You
-
Can anyone give me suggestions on the following I need to put in place an architecture which has the following prime features Assume Company X's IT Team A 1) Team A has many .NET projects lined up, Web, Windows, Services, WPF etc.. 2) For Web based projects... Team A requires the same look and feel for all projects. 3) Requirement : UI elements such as Master pages, js , css etc should not be copied over to every new project(No duplicate copies in each project) 4) Requirement : There should be a central repository kind of project/files/ etc.. which will serve as UI framework for all projects 5) Requirement : Data Access for all projects should also be driven by the same concept. One project drives data to all other projects For Data I can think of a Service. I am just not sure of how to get the architecture for the UI as mentioned above, Can someone recommend me what is the best approach. Thank You
-
Can anyone give me suggestions on the following I need to put in place an architecture which has the following prime features Assume Company X's IT Team A 1) Team A has many .NET projects lined up, Web, Windows, Services, WPF etc.. 2) For Web based projects... Team A requires the same look and feel for all projects. 3) Requirement : UI elements such as Master pages, js , css etc should not be copied over to every new project(No duplicate copies in each project) 4) Requirement : There should be a central repository kind of project/files/ etc.. which will serve as UI framework for all projects 5) Requirement : Data Access for all projects should also be driven by the same concept. One project drives data to all other projects For Data I can think of a Service. I am just not sure of how to get the architecture for the UI as mentioned above, Can someone recommend me what is the best approach. Thank You
I would think any source control would serve for this. We use SourceSafe but ut is a dog, many use SVN here. We have exactly that type of environment. A segregation of duties and a set of procedures and roles within the team works resonably well. Not really an architecture question, this is setting up a standard development environment. You can then get into the style of development you want to follow, Agile, waterfall etc.
Never underestimate the power of human stupidity RAH