Enterprise Architecture Quarter

Product 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

• Feature. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each feature is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.

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.
   • Datapoint-device architecture.
   • Configuration management.
2. Informational architecture.
   • Graphic design.
   • Usability.
   • UX design.

• 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.

1. • Output. An immediate and direct result of a process.

• Statement of work (SOW). A narrative description of products or services to be supplied under contract.

1. • Statement of work (SOW). A formal document that defines the entire scope of the work that shall be completed in order to implement the proposed change.

• Input. A variable that leads to processes.

Practices

The successor lecture is Project Management Quarter.