|
Sponsored Links
Resources
.NET Research Library
Get .NET related white papers, case studies and webcasts
|
News
News
News
|
Messages: 57
Messages: 57
Messages: 57
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
Ask TheServerSide: What Skills Should a .NET Architect Possess?
Lately it seems like every developer to ever code a Singleton pattern has donned the title of "Architect". What skills and experience make up a real .NET architect? How much should they know about competitive technologies? What does an architect do? We want to know what you think!
Can Microsoft, or any other company for that matter, really determine what an architect is; ala their Certified Architect Program? How technical should an architect be?
Tell us what you think about what is, and isn't, an architect.
|
|
|
Message #168043
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
The ability to write PRODUCTION CODE....
;-)
Serious, informed answer to follow.
|
|
|
Message #168046
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Enterprise Application Design skills
If you ask me, it'd seem that a person that would be an Enterprise Architect candidate would require a good broad knowlege of different technologies, along with experience.
It seems to me that an architect would be to the design work, developers would handle the finishing details... so I'd expect an architect to be good at organization, familliar with design patters (GOF etc), Possible knowlege of UML and ORM (or other relational modeling)... Experience with quality of service requirements. Things along those lines.
|
|
|
Message #168061
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
A good architect in my opinion should have the following characteristics regardless of technology:
1. The ability to take a complex problem and break it down into simple well defined manageable subcomponents that are loosely coupled. This reduces tight dependences, whereby, the architect can farm out subcomponents. Thus, allowing for true parallel development across a large team.
2. Architect and design a solid base application framework that allows for extensibility and ease of maintainability. In essence, design a system that can withstand the test of time, as well as meet other tenets of industrial-strength software.
3. Ensure that the application scales, and meet or exceed SLA commitments (i.e. security, performance, durability, robustness, etc)
4. Use best practices and architectural design patterns within reasons: DON’T over-engineering the system to death.
5. Do more with less: Use proven technologies and reusable library frameworks
6. Ensure that the system is highly automated, requiring little to no operator intervention, thus, reducing the Total Cost of Ownership (TCO)
7. Has a lot of real experience in truly distributed architectures. Someone who can talk-the-talk and walk-the-walk.
I know there’s more, but for now, this is what immediately sticks out of my mind ;)
Ross Pellegrino
Chief Architect
|
|
|
Message #168062
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: What Skills Should a .NET Architect Possess?
A .NET Architect should AT LEAST be familiar with
1. OODA
2. ORM
3. Design Pattern
4. Refactoring
5. COM+ (to deal with enterprise stuff)
|
|
|
Message #168074
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
forgotten?
I am missing one important area where enterprise architects really make the difference over 'regular' software architects, and that is the business area.
Enterprise architects should be very much able to defend, promote and sell the business case for the architecture to be of true value for the customer/company implementing their architecture. Unfortunately this comes with political skills as well, and these are normally obtained through years of experience in the field. Somehow I doubt that microsoft will want to put that up as a requirement for their exams.....
Jan.
|
|
|
Message #168076
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
"Enterprise Architects"
FYI: Just semenatics, but an Enterprise Architect is much different than a Solutions Architect. Enterprise Architect is an individual that can walk into a business and model the business processes, lead the development of a strategic plan, etc. i.e. if you are familiar with the zachman framework (as an example, I know others exist) and have experience in that arena, you'll understand what an EA is. A solutions Architect can take a describe box or boxes and put together a solution. They can also provide guidance on standards, technology choices, etc. Finally, they help lead the development efforts with the technical team and provide a liason between the business and technical side. The sometimes work at a level similiar to a PM on a project, but not always.
In my opinion, a Solutions Architect is not just someone who understands technology. An SA understand people, understands the business, understands the technology, and has the experience necessary to meet the requirements on time, on budget, with customer satisfaction.
|
|
|
Message #168077
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
"Enterprise Architects"
P.S. Please disregard the poor grammatical errors in the previous reply as it's midnight and it's been a long two days thus far (with 3 more to go!) on an intensive BizTalk 2004 "deep dive" course.
|
|
|
Message #168081
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
As someone already mentioned, I share the opinion of having to types (stereotypes, huh?) of architects.
- The software architect (solution architect, whatever)
- The enterprise architect (binding business needs into the overall system/software architecture.
Now, being an software architect for quite some years now in an J2EE environment and the past couple of years as a developer in .NET, I found that my past J2EE experience helped me a lot. Actually many of the same ideas (views, goals, whatever) of a Enterprise System goes for both "camps".
Please do not start the usual flame-war on the two environments.
So, for the original question:
Yes, it is a very good thing to have knowledge (especially deep knowledge) on other (competing, complementing) platforms.
Yes...My view of an enterprise architect is one, that has been a solution architect for some time, and is now focusing on "building a bridge" between the business needs of the customer and the software architecture.
Regards
Henrik
http://websolver.blogspot.com
|
|
|
Message #168091
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Can you say stuff like that at an event like TechEd or DevDays?
Hmmmm, me wonders if one were to ever say those words at an TechEd or DevDays event in front of some "rock star" speakers, would all *$%#^#$ break loose?
The ability to write PRODUCTION CODE....;-)Serious, informed answer to follow.
.
|
|
|
Message #168112
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
1)He should be idle but should look busy.
2)He has able to couple, decouple given a system.
3)He should be able elaborate and expolore a non sense thing and has to prove it has value addition.
4)He should be able organize team meetings for every silly thing
|
|
|
Message #168115
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
No idea, but...
The ability to jump on the next bandwagon regardless of its credibility
The ability to solve any given problem with XML
oh...
And of course the ability to write PRODUCTION CODE (that guy's a joker isnt he!!)
|
|
|
Message #168117
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Only one
While there *might* appear to be a set of techincal skills or expereiences that matter, it turns out there is only one skill that an architect must possess -- the ability to sell themselves as an architect to a potential employer or customer.
Anything else is too techie, like anything else, the business of software is business.
|
|
|
Message #168119
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Only one
He should be able to demonstrate in a code-off that rh cannot code his way out of a wet production paper bag ...
|
|
|
Message #168126
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
Tough day at the office?
:-)
|
|
|
Message #168129
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Isn't that obvious
Sell, sell, sell. Nothing else is gonna matter if you can't sell. Well unless someone else does the selling for the architect. As much as I'd like to saying have X experience with X technology, businesses don't work that way.
peter
|
|
|
Message #168132
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
1. Common Sense
2. Real Programming Experience (No Visual Basic Please)
3. Expereince other than MS platform
And then every one can be an architect.
|
|
|
Message #168155
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
I would like to stick to the term "architect" instead of any stereotyping because most projects are just lucky to have one (and if they do, mostly the Software Architect ends up donning the extra responsibilities ideally suited for an Enterprise Architect). However, for this discussion, the more important question is whether (and if yes, how) these skills can be measured from a certification point of view.
Having theoretical knowledge of all Design Patterns (GOF and others), though very important, doesn't mean much if you haven't successfully implemented any of them in a real life project. A properly crafted technical exam may be able to test the basic design skills of a person, but you need to be careful with what your certification portrays the person to be - someone with good basic design skills or an expert with an ability to adapt to any design situation.
Other important factors to be considered are:
1. People skills - A design, no matter how good, in a person's head is worthless unless he/she can successfully communicate it to the team who actually have to convert it into running code. The architect also needs to constantly motivate, help and oversee the team to keep them disciplined enough to stick (as closely as possible) to the original design throughout the development process.
2. Knowledge of competitive technologies - Although a definite plus, it is debatable if it should be a criterion. Lets face it ... there are many people with good design skills who have only worked with Microsoft technologies, or Java for that matter, just by the virtue of the projects they were associated with.
3. Process - Architects of teams following agile processes might want to start with a basic initial design and refactor it later to get the final design as the project progresses.
All the above factors make it very difficult to come up with an exam to objectively evaluate all the necessary skills needed for a person to be certified as an expert architect. Any such exam should be followed by an interview with a qualified panel of architects who should question the candidates on the answers they chose in the exam and their past experience.
Last, but not the least, it is important to keep in mind that most of the people opting for this certification would be developers aspiring to be architects. Many (not all) people who are already working as architects (no offense) might consider themselves to be good architects by their own standards and might not like the idea of Microsoft, or any other company, judging them :)
|
|
|
Message #168172
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Isn't that obvious
Sell, sell, sell. Nothing else is gonna matter if you can't sell. Well unless someone else does the selling for the architect. As much as I'd like to saying have X experience with X technology, businesses don't work that way.peter
Yeah, unfortunately this is true, which sucks rocks if you hate, hate, hate being involved in the sales process. The advent of the "Technical Sales Engineer" was supposed to help alleviate this a little bit (i.e., getting sales people that actually UNDERSTOOD solution development and technology issues surrounding it), but in every situation I was in it never amounted to anything. After all, how many technical folks do you know that really enjoy selling enough to make it a sizeable part of their job description?
Mike
|
|
|
Message #168176
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
What Skills Should a .NET Architect Possess?
1) He should be familiar with all the latest fashion in software production with a rock solid discernment to shift out the gold from the fluff. In other words, able to choose the right path into the future.
2) Strive for KISS in all situation. He always keep "well-meaning impractical theorists" out of the project.
3) He is a good programmer (takes one to know one) but do not compete with his staff in the project.
4) He has experience before of the businessdomain of the project.
Regards
Rolf Tollerud
|
|
|
Message #168179
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
Having theoretical knowledge of all Design Patterns (GOF and others), though very important, doesn't mean much if you haven't successfully implemented any of them in a real life project.
I am amazed how people think knowing Design patterns make you an architect. It is a very narrow thought(no offense to you Sudeep, may be that is the perception in the industry spreaded by Academia). I can argue hours the cons of Design patterns, but even if they are good it defies your own creativity. Besides that, how you write your code has very little to do with how you architect your system. For me the real challenge of an architect is to understand the issues related to performance and scalabilty as well as how to resolve these issues effectively. And trust me the issues of performance and scalability are very tricky and even the knowledge of all the design patterns in this world can not bail you out once you hit the bottle neck.
Many (not all) people who are already working as architects (no offense) might consider themselves to be good architects by their own standards and might not like the idea of Microsoft, or any other company, judging them :)
Couldn't agree more. I some time laugh when MS and SUN also teaches you the definition of an architect in their exam crams books... As always I tell them back "We don't need no education; we don't need no mind control"
|
|
|
Message #168183
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
A good architect is just an experienced developer willing to take responsibility for their own mistakes.
Jim
ThoughtWorks
|
|
|
Message #168278
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
"Enterprise Architects"
FYI: Just semenatics, but an Enterprise Architect is much different than a Solutions Architect. Enterprise Architect is an individual that can walk into a business and model the business processes, lead the development of a strategic plan, etc. i.e. if you are familiar with the zachman framework (as an example, I know others exist) and have experience in that arena, you'll understand what an EA is. A solutions Architect can take a describe box or boxes and put together a solution. They can also provide guidance on standards, technology choices, etc. Finally, they help lead the development efforts with the technical team and provide a liason between the business and technical side. The sometimes work at a level similiar to a PM on a project, but not always.In my opinion, a Solutions Architect is not just someone who understands technology. An SA understand people, understands the business, understands the technology, and has the experience necessary to meet the requirements on time, on budget, with customer satisfaction.
+1
|
|
|
Message #168292
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
I am amazed how people think knowing Design patterns make you an architect. It is a very narrow thought.
I never said that just the knowledge of patterns would make a person a good architect. I was only trying to emphasize the importance of experience of implementing designs in live project situations vis-a-vis pure theoretical knowledge.
I can argue hours the cons of Design patterns, but even if they are good it defies your own creativity. Besides that, how you write your code has very little to do with how you architect your system.
I do feel that a good architect should know about most commonly used (and abused) patterns and more importantly should know when to use and when not to use them. I do not believe that using patterns defies your creativity (this way, the whole concept of reuse goes out of the window). And unless one has the luxury of providing a group with a top level design and moving on to the next project, at some point of time the architect has to get involved with some of the coding aspects. No matter how well a system is designed initially, some problems would only surface at the coding time. In these situations, architects should be willing to accept the responsibility and refactor the design if needed.
For me the real challenge of an architect is to understand the issues related to performance and scalability as well as how to resolve these issues effectively. And trust me the issues of performance and scalability are very tricky and even the knowledge of all the design patterns in this world can not bail you out once you hit the bottle neck.
Reliability, scalability, maintainability and performance are traits of any well designed system (the end goal). And patterns are just some tools at your disposal while you are working towards achieving your end goal. To use or not to use them is entirely your call.
|
|
|
Message #168319
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Not half bad...
A good architect is just an experienced developer willing to take responsibility for their own mistakes.
This is pretty good - very Zen-like...I'll be adapting this for my own use.
:-)
Mike
|
|
|
Message #168387
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
the difference was Not half bad...
What does the architect do? What is the difference between an architect compared with a senior developer? These are some of the common questions asked. The designer is concerned with what happens when a user presses a button and the architect is concerned with what happens when ten thousand users press a button. An architect mitigates the technical risks associated with a system. A technical risk is something that is unknown, unproven, or untested. Risks are usually associated with the service-level requirements and can occasionally be associated with a business requirement. Regardless of the type of risk, it is easier to address the risks early in the project while creating an architecture, then to wait until construction when you have a large developer base that could potentially be waiting while risks are solved.
An architect must lead the development team to ensure the designers and developers build the system according to the architecture. As the leader, difficult decisions must be made about trade-offs in the system and the architect is the person who must make those decisions. To lead, the architect must be a good written and oral communicator. It is up to the architect to communicate the system to the designers and developers who will build it. This is typically done with visual models and group discussions. If the architect cannot communicate effectively, then the designers and developers will probably not build the system correctly.
|
|
|
Message #168431
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
only one leads to ZERO references
Selling is important...
But if hiring managers start wising up and start asking for PRODUCTION CODE..this person who CAN'T production will only har ZERO references because the last job didn't work.....sort of like an architect that build a bridge only to have it fall down.
ha ha ha ha
While there *might* appear to be a set of techincal skills or expereiences that matter, it turns out there is only one skill that an architect must possess -- the ability to sell themselves as an architect to a potential employer or customer.Anything else is too techie, like anything else, the business of software is business.
|
|
|
Message #168435
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ever see those who SPOUT design patterns as IVY LEAGUE?
Those who endlessly talk about design patterns have almost no PRODUCTION CODE to show for themselves.
They cite books and books and books. Theory after theory after theory....
These people spend more time reading instead of implementing what they just read in a production environment yet somehow thinks it's good.
PRODUCTION CODER PATTERNS WORK in a PRODUCT ENVIRONMENT and are by PRODUCTION CODERS....
Production Code has so many things going on, stuff that you learned in Design patterns are either second nature to those who PRODUCTION CODE in the FIRST PLACE or irrelevant because the problems in the production world have become so complex to begin with no design pattern book could even cover a drop of production code.
Lot of the "architects" who spout off Design Patterns as the end all and be all to architecting a system are clearly not production coders.... and have nothing to show for themselves except the design pattern they got use...
Whoop dee do!!!
I am amazed how people think knowing Design patterns make you an architect. It is a very narrow thought(no offense to you Sudeep, may be that is the perception in the industry spreaded by Academia). I can argue hours the cons of Design patterns, but even if they are good it defies your own creativity. Besides that, how you write your code has very little to do with how you architect your system. For me the real challenge of an architect is to understand the issues related to performance and scalabilty as well as how to resolve these issues effectively. And trust me the issues of performance and scalability are very tricky and even the knowledge of all the design patterns in this world can not bail you out once you hit the bottle neck. Many (not all) people who are already working as architects (no offense) might consider themselves to be good architects by their own standards and might not like the idea of Microsoft, or any other company, judging them :) Couldn't agree more. I some time laugh when MS and SUN also teaches you the definition of an architect in their exam crams books... As always I tell them back "We don't need no education; we don't need no mind control"
|
|
|
Message #168464
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ever see those who SPOUT design patterns as IVY LEAGUE?
the differentiator of an architect is that they can *recognize* emerging patterns, not simply apply them.
|
|
|
Message #168502
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
production production production
Hey rh, didn't you miss to capitalize PRODUCTION a couple times? Better proofread the next time before posting.
|
|
|
Message #168695
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
Any decent .NET architect MUST know Java/J2EE.
|
|
|
Message #168837
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
Any decent .NET architect MUST know Java/J2EE.
Does that mean any decent J2EE architect needs to (or MUST) know .NET?
BTW, which MCP exam did you sit? Thanks.
|
|
|
Message #168842
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
Any decent .NET architect MUST know Java/J2EE. Does that mean any decent J2EE architect needs to (or MUST) know .NET?BTW, which MCP exam did you sit? Thanks.
Absolutely!!! and all decent Java Architects I know have sound knowledge of what .NET can and cannot do. (Something which I still have to see in the MS guys)
I sat the SQL Server examinations for a MSCDBA cert.
What Java cert do you have?
|
|
|
Message #168859
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Enterprise Architecture
still he right about politics!
IMO, Enterprise architecture is build from business, information, system and technology architecture. therefore EA should also have knowledge with Information architecture as well as infrastructure knowledge.
|
|
|
Message #168977
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
An architect should be able to produce and effect a business solution using whatever tools are reasonably and readily made available.
If all you have is cardboard, you should be able to construct the best possible solution out of cardboard; the same would apply given blocks of polished granite.
A true architect is resourceful enough to look at the problem, find and gain a knowledge of the basic resources (technologies and people) necessary to construct a solution that meets the immediate business need.
Anything more is over architecture.
|
|
|
Message #168986
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Amen
1. Common Sense2. Real Programming Experience (No Visual Basic Please)3. Expereince other than MS platformAnd then every one can be an architect.
1. Of course
2. Thanks for recognizing that VB is worthless.
3. Definitely a plus.
|
|
|
Message #168997
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
Most of the foregoing applies, but I believe the most important personal trait is intellectual flexibility.
An architect with an ideology is a dangerous thing, ill-suited to adapt to diverse technology environments.
|
|
|
Message #169009
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Is VB Worthless
I always love it when people talk about how worthless VB is. Generally these are the people who would spend 3 weeks putting together a user interface they should have done in 3 days in VB. I hope this is not the case here.
Bad or difficult to maintain code is not the fault of the language. Well structured, easy to maintain code can be written in any language.
Some languages are better suited to tasks than others. I use VB, C, C++, VB.Net, and C#. I have worked with code done in C++ that is poor as often as VB code that is poor. VB does an excellent job with user interface code, whereas I will use C++ for any code that does any degree of work or application of business rules. In .Net I do everything in C# (or VB.Net if it is asked for).
Knowing the right tool for the job is part of an architect's job. I would not consider any person senior level unless they know a variety of development languages (often including VB). The best tool is a matter of what you are trying to do and what the skill sets of the developers who will be maintaining the system. Recommending using C++ for a project when you know that the developer staff is 95% VB is just silly even if it will add to the scalability of the application.
Experience in a variety of platforms and how they can interact is useful for an architect. In general I've found that most places have already made decisions on their infrastructure. Bringing in Linux into an environment where the staff is only familiar with Windows usually isn't required. Experience with different platforms, and how to make them work together is essential to determining when it is the right time to incorporate other platforms into the mix and worth the training required.
Everything listed above I would normally attribute to common sense, but what is common sense to one person is knowledge to another.
|
|
|
Message #169015
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
Real Architects code.
An Architect should be able to design and build applications for any given framework using any given language. J2EE and .NET are just the tip of the software iceberg in the real world. Adaptability is the Key.
All an Architect needs to know about any language / framework / methodology / technology is what it's capable of doing. After that, it's just a question of learning the necessary syntax / technique as and when required to achieve the desired result.
Steve's Postulate: "Design Patterns" are like Sex. Every new Generation thinks they invented it.
|
|
|
Message #169017
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
.NET Architect or any Architect for that matter should be able to design and model the best feasible solution based on the "Requirements", making sure that solution is scalable, maintainable and performs well upto the client expectations.
|
|
|
Message #169042
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
SCWCD (don't tell anyone :-)).
|
|
|
Message #169054
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Seeing the big picture
The most important aspect of an architects job, is to be able to see the big picture and the big blocks/modules of the system. As programmer designing an application is designing your module or part of the application. The architect has to be able see the big picture and also how the smaller parts will interact and connect to create the whole.
And the other important thing is to be able to convert the business need into techinical/implementable components/modules. Map the needs to actual technical pieces that the developers can work on.
|
|
|
Message #169128
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
To me its "what" vs "why"
>> What is the difference between an architect compared with a senior developer?
I've had to deal with managers that thought their Dev Leads were Architects.
I like this definition: "The designer is concerned with what happens when a user presses a button and the architect is concerned with what happens when ten thousand users press a button"
I guess I would add: "The designer asks what they are being asked to build. The architect asks 'why are we building it'".
While it may be ok for a developer to "architect" something according to the set of usecases they are presented with, an architect is held to a higher standard - they need to make sure not just that the application scales, but that the design scales.
What's the difference? An architect is trying to make sure that the design not only meets this set of usecases, but can apply their experience to see future challenges. A major part of this is about being a proactive "partner" to the business, taking an active interest (involvement, even) in their roadmap.
I guess you could characterize it as: "The developer wants to win the battle. The architect provides tools to help the developer win the battle, but is equally (or more) focused (and measured) on the war overall"
|
|
|
Message #169149
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
Architect : Able to Design the System as per the Customer Requirement without biasing on any technology. If the Business compels to use .NET then use it. Otherwise, dont get biased on the Technology.
Sankar Balu
Wipro Technologies, Chennai, India.
http://jinishans.blogspot.com/
|
|
|
Message #169221
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
SCWCD (don't tell anyone :-)).
Try the Architect certification. IMHO SCWCD is worthless...
|
|
|
Message #173329
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
I a beginer, but with all i've learn from .net I think that .net easy to programming if company or organization have good System "Analysis" and "Designer",else i think that it is difficult for a programmer to solve a problem which is not his professional knowledge and it must be long to Analysis and Design stage
|
|
|
Message #175138
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
Sat a 70-315 today and passed comfortably with a score of 905 (out of 1000). The MS passing score of 700 seems also too low.
|
|
|
Message #176439
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
What about daily tasks such as:
1) Reviewing developer code in order to ensure the project is maintainable
2) Ensuring the project has all the custom tools needed to implement the code quickly, like test harnesses, code validators, a project web site where all reports/docs can be easily found, etc.
3) Fine tune the development processes, like source control/config managment/versioning, migration between environments, quality assurance, etc
4) Check that the system being developed is as automated as possible to reduce maintenance costs. So for example, the architect might define the error handling process, like making a system write to the event log which is monitored by an HA framework.
5) Reviewing requirements and UAT tests to ensure the system matches the requirements and will fulfil the tests. Customers often need help with these aspects!
So generally speaking, take all the steps to ensure that the project is successful in a technical sense. The project manager is in charge of making sure the project is a success in a cost/time/functionality sense. Without the architect that wouldnt happen.
|
|
|
Message #179433
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
What about daily tasks such as:1) Reviewing developer code in order to ensure the project is maintainable That's for the Senior Programmer in the team or the peer assigned to one. This is like asking the Building Architect to make sure the bricklayer is placing the bricks properly.
2) Ensuring the project has all the custom tools needed to implement the code quickly, like test harnesses, code validators, a project web site where all reports/docs can be easily found, etc. This is more for the configuration manager guy or whoever makes sure your development environment is up to date.
3) Fine tune the development processes, like source control/config managment/versioning, migration between environments, quality assurance, etc Another one for the configuration manager guy.
4) Check that the system being developed is as automated as possible to reduce maintenance costs. So for example, the architect might define the error handling process, like making a system write to the event log which is monitored by an HA framework. Close but not enough. The actual role of the architect is to define the overall architecture enterprise wide and make sure any solution implemented follows and abides by this architecture. Stuff like "as much automated as possible" is not for the architect but the designer.
5) Reviewing requirements and UAT tests to ensure the system matches the requirements and will fulfil the tests. Customers often need help with these aspects! ??? This looks like something for the guy doing the QA (QA manager, QA analyst, etc). The architect is not the application designer from the requirements point of view.
So generally speaking, take all the steps to ensure that the project is successful in a technical sense.
What is success in a technical sense??
The project manager is in charge of making sure the project is a success in a cost/time/functionality sense. Without the architect that wouldnt happen. mmm... actually that can happen. No need for architects in order to have a "succesful" project in terms of cost/time/functionality.
Remember, the designer is the one concerned about functionality i.e what happens when a user clicks on this button? the architect is the one concerned with providing the infrastructure for having an scalable application i.e what happens when 10,000 users click on this button?
|
|
|
Message #182778
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
Sat another exam last Friday: 70-320: .NET Web Services and Server Compnonents with C#. Passed easily with 888 (out of 1000).
However, don't think the exam contents as relevant as 70-315. What's your thoughts?
|
|
|
Message #205576
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ask TheServerSide: What Skills Should a .NET Architect Possess?
914/1000 on 70-340: Implementing Security for Applications with Microsoft Visual C# .NET (on 22nd February 2006).
|
|
|
| |
|
| New content on TheServerSide.NETNew content on TheServerSide.NETNew content on TheServerSide.NET |
|
|
Language "mashups" will become more prominent, and developers will become polyglots, one programmer suggests.
SearchWinDevelopment.com offers an introduction to the language, performance, testing and data management improvements in VS 2008.
VBCode.com code snippets cover all aspects of application development, from data binding to security to the user interface.
Get up to date on XAML best practices with a variety of articles, tutorials and webcasts. [SearchWinDevelopment.com]
One team's experience with the VSTS DB edition suggests that it can improve workflow for dev teams. It also enhanced Agile efforts.
(June 24, Article)
Microsoft has begun to include DSL tools in the VSTS kit. A new book by Steve Cook and other VSTS team members helps set the stage.
(June 24, Article)
Cartoon: Be it ever so humble there is no place like your home after you get a Microsoft Home Server .
(June 18, Cartoon)
Microsoft's Thom Robbins says new technology to highlight in NET 3.5 includes AJAX, LINQ for both C# and VB, as well as tooling enhancements intended to ease the task of building WPF, WF and WCF apps.
(June 29, Podcast)
Venkat Subramaniam discusses AJAX bottlenecks, the tenets of Agile development and more. He spoke at the Ajax Experience.
(June 25, Tech Talk)
In the second of a two-part series, Michele Leroux Bustamente discusses design decisions related to the claims-based security model. Read the story and walk through the process for creating a set of claims-based utilities to encapsulate claims authorization at the service tier.
(May 24, Article)
Understanding why the Entity Framework exists and learning where it can fit into your projects can get you prepared for the eventual release early next year.
(May 10, Article)
Resource: This learning guide gives you quick access to useful links on Windows Communication Foundation security information.
(April 24, Article)
TSS.NET's Jack Vaughan spoke recently spoke with Microsoft's Brad Abrams to find out what he is seeing in the field and what the chefs in Redmond are cooking. Along the way he discusses patterns of AJAX frameworks.
(April 11, Article)
In a two-part series, Michele Leroux Bustamente explains how claims-based security is supported by WCF, and how you can implement a claims-based security model for your services.
(March 29, Article)
Windows Workflow Foundation is a new technology that many developers will need to get their heads around. In a brief excerpt adapted from Programming Windows Workflow Foundation: Practical WF Techniques and Examples using XAML and C#, K.Scott Allen considers aspects of workflow definition.
(March 22, Chapter Excerpt)
|
|
