Difference between revisions of "Enterprise Architecture Quarter"

From CNM Wiki
Jump to: navigation, search
(Practices)
(Concepts)
Line 10: Line 10:
  
 
===Concepts===
 
===Concepts===
 +
#'''[[Product]]'''. A solution or component of a solution that is the result of a project.
 +
#*[[Product vision statement]]. A brief statement or paragraph that describes the why, what, and who of the desired software product from a business point of view.
 +
#*[[Product backlog]]. A set of user stories, requirements or features that have been identified as candidates for potential implementation, prioritized, and estimated.
 +
#*[[Product scope]]. The features and functions that characterize a product, service or result.
 
*Agile
 
*Agile
 
*[[System]]. A set of interrelated and interdependent parts arranged in a manner that produces a unified whole.
 
*[[System]]. A set of interrelated and interdependent parts arranged in a manner that produces a unified whole.

Revision as of 11:41, 28 March 2018

Solution Design Quarter (hereinafter, the Quarter) is the third of four lectures of Project Quadrivium (hereinafter, the Quadrivium):

  • The Quarter is designed to introduce its learners to enterprise design, or, in other words, to concepts related to creating architecture for achieving enterprise goals; and
  • The Quadrivium examines concepts of administering various types of enterprises known as enterprise administration as a whole.

The Quadrivium is the first of seven modules of Septem Artes Administrativi, which is a course designed to introduce its learners to general concepts in business administration, management, and organizational behavior.


Lecture outline

The predecessor lecture is Business Analysis Quarter.

Concepts

  1. Product. A solution or component of a solution that is the result of a project.
    • Product vision statement. A brief statement or paragraph that describes the why, what, and who of the desired software product from a business point of view.
    • Product backlog. A set of user stories, requirements or features that have been identified as candidates for potential implementation, prioritized, and estimated.
    • Product scope. The features and functions that characterize a product, service or result.
  • Agile
  • System. A set of interrelated and interdependent parts arranged in a manner that produces a unified whole.
  • Open system. A system that interacts with its environment.
  • Closed system. A system that is not influenced by and does not interact with its environment.
  1. Systems engineering.
  2. Informational architecture.
  • Action design. A change process based on systematic collection of data and then selection of a change action based on what the analyzed data indicate.
  • Commitment concept. Plans should extend for enough to meet those commitments made when the plans were developed.
  • Load chart. A modified Gantt chart that schedules capacity by entire departments or specific resources.
  • Organizational development. A collection of planned change interventions, built on humanistic-democratic values, that seeks to improve organizational effectiveness and employee well-being.
  • Organizational development. Change methods that focus on people and the nature and quality of interpersonal work relationships.
  • Process. An action that individuals, groups, and organizations engage in as a result of inputs and that leads to certain outputs.
  • Statement of work (SOW). A narrative description of products or services to be supplied under contract.

Methods

Instruments

Practices

The successor lecture is Project Management Quarter.