Linus Fernandes

Posts Tagged ‘architecture’

A THOUGHT FOR TODAY

In thought for today on January 3, 2011 at 00:30

Every man’s work, whether it be literature, or music or pictures or architecture or anything else, is always a portrait of himself. -Samuel Butler, poet (1612-1680)

Architecture Quote

In thought for today on May 24, 2010 at 10:36

Architecture is music in space, as it were a frozen music.

- Friedrich W Schelling, philosopher.

The Social Impact of Technology | The Coherency Press

In architecture, Enterprise Architecture, IT, Leadership, Management, Professional, social networking, software, Software Architecture, technology on May 6, 2010 at 10:44

Leadership face the problems of how to manage the different resources / assets the company has in their sphere. The problem the focus group reports about deals with how to handle the human resources and information flow so the employees are informed about the current situations in the company: * Making connections. Employees working from home might feel that they don’t contribute to the business success. Therefor it is the managers duty to make connections to the tele employees and inform them by e-mail or other way about the news (development in the headquarter). Thereto the managers are in the dilemma that they might favor those workers that are placed at the office or they might favor the tele workers. The employees need to be trained in how to collaborate with tele workers so bottle necks of information doesn’t occur and work can be done more effective. * Leading and modeling. HR – policies must include a commitment to make alternative working arrangement successful. Because of the social implications of the technological impact the company should give the employees some time to consider the choice for being a tele worker. * Communicating. Managers have a tendency to only communicating about tasks to the tele workers; however the managers should focus on how to improve the communication on all levels of the organization to cope with the needs of the environment of the organization e.g., tele workers working at different times at the day and on different locations. Thereto the managers and the organization needs to introduce to the employees that digital information is “okay” to make use of; however the organizational culture is hard to change and it is hard to implement tele working from a top – down approach. * Building trust. Employees needs to build two kinds of trust. The first one is personal trust which deals with people trusting their co – workers and managers. The second one is competency trust that is build when the employees solve the problem situations together. It is the managers responsibility to make both competencies grow within the organization. * Relationship building. Relationship building is best constructed via face – to – face communication and it is the responsibilities of the manager to help the employees to construct the relationship among the project teams and since the future will lead to more virtual teams then it is up to the managers to create the face – to – face relationships. The chapter refer to that some companies have a weekly meeting with the project teams where the members of the virtual teams needs to come into the organization for coordination and socializing. Other methods such as video conferencing and tele communications such as phone calls, chat and personal websites2⁠ can also be made use of.

The Social Impact of Technology | The Coherency Press

Blogged with the Flock Browser

Tech.ed 2009 :: Contest – Winners

In cloud computing, Enterprise Architecture, India, Innovation, IT, Professional, software, Software Architecture, technology on April 22, 2010 at 10:14

Tech.ed 2009 :: Contest – Winners

Winners of the Microsoft Top Architect Contest!

Blogged with the Flock Browser

Architecture – Understanding the criteria – II

In architecture, IT, Management, Professional, Thought on February 14, 2010 at 10:48
Principle of a public key infrastructure. Roug...

Image via Wikipedia

Continuing with Understanding the criteria….

Security:

When we refer to IT security, we usually look at access management i.e. authentication and authorization.

Authentication simply means you are who you say you are. It is also referred to as identity management.

Authorization means are you authorized to use the given service / application / system i.e. are you allowed access? Do you have the rights to use the resource? Authorization is usually a group / role specific policy. Rarely is authorization set at the individual level. Authorization can be also implemented , in a charging system, as do you have credits to be allowed to use the resource? This, of course, would be at the level of the individual or an entity such as an organization. Examples of this would be encountered in a utility computing model say cloud computing or even for mobile phone services. In the latter, the services are degraded once the credit limit is reached and are restored once the customer tops up his account with the required minimum amount. Authorization is also referred to as access management.

A robust access management system includes verifying identity and entitlement, granting access to services, logging and tracking access, and removing or modifying rights when status or roles change.

ITIL talks about information security as being effectively managed if

  • information is available and usable when required (availability)
  • information is observed by or disclosed to only those who have a right to know (confidentiality)
  • information is complete, accurate and protected against unauthorized modification (integrity)
  • business transactions, as well as information exchanges, can be trusted (authenticity and non-repudiation).

In cases where information is to be protected , use of cryptography and methods such as symmetric encryption, Public Key Infrastructure (PKI) (asymmetric encryption algorithms) and digital signatures (ensures non-repudiation). For more, read http://en.wikipedia.org/wiki/Public_key_encryption

A strategy referred to as ‘defense in depth’ is used to secure computer systems from outsider attack. Here, the premise is that even if the outer wall is breached, the inner sanctum is still secure and it is also time-consuming for the attacker, by which time, a breach may be detected and flagged by a good audit trail system.

You may be more familiar with this when building systems that access the internet and are accessible from it. Here, a De-militiarized Zone (DMZ) adds another layer of security to the firm’s LAN. For more see http://en.wikipedia.org/wiki/DMZ_(computing)

 Usability:

This is the most overlooked aspect of a solution / application. However clever your system may be, however ingenious the engineers developing the system, if the user does not find the application easy to use, then you have a hit a brick wall. Resistance from the users can sound the death knell of any application. A good application should be intuitive to use and leverage existing habits of users. Forcing users to change their ingrained habits is always difficult. Especially with reference to transactional systems and customer facing applications, where responsiveness is key, a non-intuitive interface coupled with inadequate training on a new system can lead to frustrated users. In my experience, at British Telecom, when a GUI was introduced to the customer service representatives replacing the old mainframe UI, the sluggish responsiveness of the new UI led to experienced users switching over to the old system so that they could finish their quota of calls to be attended to. CSRs are very stressed individuals and you do not want a system to add to their discomfort.

These , in my opinion , are the most relevant criterion in evaluating an architecture. Their importance may vary from system to system. But a good and simple way of evaluating a software architecture to assign weights to each criteria and a range of values from 1 – 10 for each criteria. This will give you a rough and ready estimate as to how well your architecture stands up to scrutiny.

Have a good day!

To be continued ……


Share this post :

Reblog this post [with Zemanta]

Business Rules and EA

In architecture, Enterprise Architecture, IT, Management, Professional, prose, Thought on January 28, 2010 at 11:34

The Principles of Rule Independence

as outlined by the business rules group manifesto!

Have a dekko!

Good day!

EA is focused on strategy

In architecture, Enterprise Architecture, IT, Management, Professional, Thought on January 26, 2010 at 19:26

An interesting post on EA and strategy.

Have a good day!

Follow

Get every new post delivered to your Inbox.

Join 44 other followers