Last post Jun 15, 2011 12:44 PM by ajitsunny
Jun 13, 2011 02:50 PM|pzn3xq|LINK
Can someone provide a list of areas that need to be discussed/planned for an ASP.net enterprise application? In planning tasks for building such an application, I imagine things such as Database Access layer/templates, exception handeling/writing to event
viewer, login/security are all examples of rough-plumbing that needs to occur for such an application. Can you help me list others?
Jun 13, 2011 03:29 PM|AZMatt|LINK
I recommend that you start your searches with the three major tiers of a large-scale application. The User Interface Layer, the Business Logic Layer, and the Data Access Layer.
If you have not already done so, I would also look into Microsoft Team Foundation Server to help you organize, analyze, and share your projects throughout your development team.
Jun 15, 2011 05:38 AM|nizam133|LINK
Check this link
Jun 15, 2011 12:44 PM|ajitsunny|LINK
When you are designing an enterprise architecture, first step is that you should have list of two types of requirements:
1. Functional Requirements
- Described in SRS / FRS / FSD document
2. Non-Functional Requirements
Your architecture should solve all non-functional as well as function requirements of projects.
Also go through following links, before jumping into coding part:
- Develop Use Case diagrams before doing coding for your architecture implementation. [http://www.bredemeyer.com/pdf_files/functreq.pdf]
- Identification of most suitable architecture, proper class structures, communication among objects & data object & format is most important part of any architecture.
However, this link will cover your all requirements: