Career Question: Architect role
Reply
![]() |
|
From:
![]() sistlavenkat
|
Sathakathulla,
Architecting is the science of gathering experiences, bestpractices and roadmaps in software field. Maybe something like this would go along for becoming a future architect.
1. Identify and conceptualize architecture from following perspectives. 1.1 Developers 1.2 Designers/Analyst 1.3 Architectural levels - Domain, System, Enterprise (this can be at typical beginer lever - that is junior architect level) and most importantly, 1.4 Benifits from business prespective 2. Decide on the strategies 2.1 Beginers problems (architectural decision involved in business proposition stage) 2.2 Architectural models - Domain level and System level (start of with primary models like MVC, Disconnected Vs Connected) 2.3 Implementation models 3. High end strategies 3.1 Move ahead with high end models (like Zachman framework, SOA etc.) |
|
View other groups in this category.
![]() |
To stop getting this e-mail, or change how often it arrives, go to your E-mail Settings.
Need help? If you've forgotten your password, please go to Passport Member Services.
For other questions or feedback, go to our Contact Us page.
If you do not want to receive future e-mail from this MSN group, or if you received this message by mistake, please click the "Remove" link below. On the pre-addressed e-mail message that opens, simply click "Send". Your e-mail address will be deleted from this group's mailing list.
Remove my e-mail address from dotNET User Group Hyd.
|
|
- Re: Career Question: Architect role dotNET User Group Hyd
-