José Ferreiro's ホセ フェレイロ (Хосе Ферреиро) research, analysis, management experiences, Information Technology trends, competitive intelligence and life stories...
Showing posts with label software. Show all posts
Showing posts with label software. Show all posts
Saturday, November 12, 2011
What is the difference between Architecture and Design in ICT?
Architecture is the software components that a software needs to have, based on the specifications, to perform as required. Design is the construction of the software components, and may be Logical Design which is the source coding of the components, and may be Physical Design which is the organization adaptation of the Logical Design into a functioning software.
Monday, April 11, 2011
As an IT Architect how do you measure success (II)?
In respect to what KPI your organization follows or not, The simplest way for IT architect (matters any Architect) to measure his/her success is:
1) Develop your growth plan for short term and long term, what and where you want to be.
2) Knowledge Acquisition in changing business demands.
3) Build a design or solutions were all business elements (People process and Technology) are met and bridge all the gaps.
4) Achieve excellency in your work to gain buy-in for all your plans and designs.
5) Request Testimonial/Recommendations for your work (efforts are useless if you're not appreciated).
If you are done with above, you are on TOP success list, rest will follow :)
1) Develop your growth plan for short term and long term, what and where you want to be.
2) Knowledge Acquisition in changing business demands.
3) Build a design or solutions were all business elements (People process and Technology) are met and bridge all the gaps.
4) Achieve excellency in your work to gain buy-in for all your plans and designs.
5) Request Testimonial/Recommendations for your work (efforts are useless if you're not appreciated).
If you are done with above, you are on TOP success list, rest will follow :)
Labels:
achievement,
project management,
software,
success
Thursday, April 7, 2011
As an IT Architect how do you measure success (I)?
In my opinion the success is measured by:
Was the solution implemented?
Did it provide the expected results?
and finally, Is the solution flexible enough to withstand change?
I mention the last one because IT is built on top of change. Any IT Architect (of any vertical) must incorporate the change aspect on its solutions. Please do not reduce the support for change just to the upgrades and additions to the solution. The end-of-life, disposal and deployment of new solutions also counts as change.
Was the solution implemented?
Did it provide the expected results?
and finally, Is the solution flexible enough to withstand change?
I mention the last one because IT is built on top of change. Any IT Architect (of any vertical) must incorporate the change aspect on its solutions. Please do not reduce the support for change just to the upgrades and additions to the solution. The end-of-life, disposal and deployment of new solutions also counts as change.
Labels:
achievement,
project management,
software,
success
Subscribe to:
Comments (Atom)
