The principles of architecture define general rules and guidelines to use and implement all information technology (IT) resources and assets throughout a company. They must reflect a level of consensus between several corporate components and areas, constituting the basis for future IT decisions. Each architecture principle must focus mainly on business goals and key architecture applications. And remember principle means- “Service Above All”. I might go in to some principle in details and some may be one line, because they all are with valuable to enterprise.
Here’s one of the most important principle -
IT and business alignment
To get success in IT, management should make decisions those are always made under the business alignment perspective in order to generate maximum benefits for the company as a whole. A better alignment between IT and the business must generate a competitive edge for the enterprise. Decisions based on the corporate perspective have greater long-term value than decisions based on a certain perspective of a group with a specific interest. An optimal ROI requires information management decisions to be aligned with the company's priorities and positioning. No single area must affect the benefit of the company. This principle, however, must not prevent anyone from performing tasks and activities. Aligning IT with the business and promoting optimal corporate benefits requires changes in how information is planned and managed. Technology alone is not enough to promote such changes. IT architecture must implement a complete IT vision that is focused on business. Application development priorities must be established by and for the entire company. Application components must be shared among all areas in the enterprise.
Maximum benefits at the lowest costs and risks
Strategic decisions for solutions must always strive to maximize benefits generated for the business at the lowest long-term risks and costs. And Decisions must not be made based solely on reaching lower solution costs. Every strategic decision must be assessed based on cost, risk, and benefit perspectives. Lower costs often represent greater risks and, perhaps, fewer benefits.
I don’t think I have to say anything on this…we all know ..Corporate activities must be maintained, despite system interruptions
Compliance with standards and policies
Corporate information management processes must comply with all applicable internal policies and regulation.
Adoption of the best practices for the market
IT activities must always be aligned with the best practices for the market regarding IT governance, processing, and management.
Information treated as an asset
Information is a valuable asset to the company and is managed based on this concept.
In my view this one is one of the most important principles. Information is protected based on integrity, availability, confidentiality, incontestability, and authenticity. Every piece of information is submitted to a security assessment based on those five factors.
Security must be planned in data elements from the beginning, rather than added later. Systems, data, and technologies must be protected against unauthorized access and handling. The source of information must be protected against unauthorized or accidental modifications, fraud, catastrophes, or disclosure.
Data security can be applied to restrict access to read-only or no-reading statuses. Sensitivity labels must be established for access to temporary, decisive, confidential, sensitive, or proprietary information.
Convergence with the enterprise architecture
The convergence with the enterprise architecture takes place as new applications are built, new technologies are implemented, and older systems are updated or decommissioned. Exceptions to the enterprise architecture might be supported for specific cases if there is a consensus that the benefits of using a solution from a specific technology exceed those arising from the adoption of the enterprise architecture.
Implement Micro services, Low-coupling interfaces are preferable, because when interfaces between independent applications are highly coupled, they are less generic and more susceptible to causing unwanted, secondary effects when they are changed.
You could go on and on this topic…and I think if we all as an Enterprise Architect, stay on top of the enterprise architecture principles we could deliver outstanding result in IT.