Write-Ups on Enterprise Architecture.

…What is an Enterprise?
  • An enterprise is a group of interacting, interrelated, or interdependent elements or parts(divisions, departments, units) that function together as a whole to accomplish a  given goal.  So, an Enterprise is a typical System which contains an orderly and complex arrangement of the following four key elements:
  1. Input
  2. Throughput (…the rate at which the organization reaches its goals)
  3. Output
  4. Feedback
  • It should be noted that within the enterprise, the above elements are always (continuously)  in interaction.  This is to say that every Enterprise (which may be a company or an organization) always has these FOUR things interacting with each other within in its divisions, departments as subsystems, and within itself as a whole system; therefore the principles of Systems Theory hold true for ALL Enterprises (companies and organizations).
  • An enterprise may be private, non-profit, governmental, or public .
…What is Enterprise Architecture?
  • Enterprise Architecture can be simply defined as an effort by the Software engineer, Enterprise architect, Business analyst or an IT expert to link a company’s Strategic plan, Business process and Technology…
  • This effort can be empirically summarized as follows:
  • enterprise architecture = S+B+T

  • WHERE…S = Strategic plan (Veer of the Company/Organization); B =  Business Process; TTechnology & Infrastructure Plan (Envisaged)
…The Fundamental  system theory Principles that govern enterprises
  1. An  enterprise  is greater than the sum of its parts ( divisions, departments, units).
  2. Though each division or department may be in itself  a self-contained unit, it must remain part of a wider and higher order …of the whole enterprise.
  3. The central objective of the entire enterprise can be identified by the fact that other sub-objectives are usually sacrificed in order to attain the central (higher order objective of the enterprise.
  4. The enterprise and its enterprise-level environment plus division-level micro-environments must be  OPEN, highly interrelated and permeable…..otherwise Entropy (disorganization, dis-integration or Decay) will set in.
  5. A highly complex enterprise organization may have to be broken into parts or  subsystems in order for us to be able to see, properly analyze, monitor and manage the boundaries.
  6. A change in only one of the parts (units, divisions or departments) of the enterprise usually would eventually produce a change in all the others. When divisions or departments  are arranged in a series, the output of one is the input for another; therefore, process alterations in one would require alterations in others.
  7. Every enterprise always tend towards equilibrium; the state of Equilibrium is a balance of various forces within and outside of the enterprise.
  8. To be viable and survive, an enterprise must be strongly goal-directed, governed by feedback, and have the agility, capacity plus  ability to adapt to changing circumstances…..its boundaries must be kept permeable and open.
  9. In other words, it MUST remain an OPEN system.

Software Engineering – Basic Blocks

  • Urgency to Start Discussing the Ethical Issues Involved with Computer Applications Engineering in Nigeria. [Open Challenge to Systems Analysts, Software Engineers, Programmers, Application Developers and IT Experts]. BY PROF. ARTHUR U. UME

For more than two decades now,  Nigeria is witnessing a continuous improvement and boom in the application of Information and Communications Technology (ICT) in all its vital sectors of the economy. Thus, there is an increasing dependency on ICT for critical infrastructures, business processes and operations. This boom is not abating; rather it is resulting in a corresponding increase in the number of individuals who join an increasing population of systems analysts, software engineers, enterprise application developers, programmers  and creators.

But regrettably, the boom has given rise to a host of ethical issues.  The ability to make sound ethical judgement and decision is becoming very important as “half-baked” systems analysts and software developers produce critical information systems that are supposed to run critical business functions and operations in the society.  To compound this problem the few technical schools or colleges that produce the very needed programmers and web designers do not have a clue that something negative is slowly creeping in unnoticed from another angle; they do not have qualified, versed or knowledgeable instructors to arm their students and graduates with the basic foundation knowledge in software professional ethics which is needed to effectively practise the art of software engineering and applications development in the society at large.

This section of the Blog handle will start looking at this “sorry” state of  in the face of the country’s up-welling Information and Communications Technology, and its intention to produce and use locally designed and implemented information systems. The author will be highlighting how adherence to sound ethics at all levels of systems design and applications development in the society at large can be introduced.

 

  •  Understanding of How to Craft and Model Implementable & Testable Software Requirements [Tit-Bits for Systems Analysts, Software Engineers, Programmers, Application Developers and IT Experts]. BY PROF. ARTHUR U. UME

….to be populated!

 

  •  The Nuts & Bolts of Software Configuration Management (SCM)  [Nuggets for Systems Analysts, Software Engineers, Programmers, Application Developers and IT Experts]. BY PROF. ARTHUR U. UME

….to be populated!

 

  •  The Key to Successful Software (Systems) Project Ousourcing  [Nuggets for Systems Analysts, Software Engineers, Programmers, Application Developers and IT Experts]. BY PROF. ARTHUR U. UME

….to be populated!