Optimization of "/work-the-system" description file

Introduction

This file describe a framework used to work a system.

What's this file ?

It provide an organization methodology to define a system composition and objectives and plan optimal strategies to accomplish objectives, optimize composition and efficiently work the strategies.

For the Esteem8 system, this framework is a layer that apply after the GitHub IT system.

What's new in this file ?

Some points have been clarified and a schema was added.

What's in this file ?

---

Work the system methodology

This document describe the document set used to work the primary ESTEEM8 system.

Introduction

A system is what make it does what it perform.

Vocabulary

• A system is a composition of nested systems composed of functions.
• A function is a composition of process grouped by a type.
• A process is a series of mechanical and chemical operations.

Basicaly these components above are working similary as a program. Comparing to web component framework, a system is a component, a function is a function and a process is a native language function.

Document set

The what

• /definiton
• System composition is the detailed current whole system state.
• System objectives is the detailed current system objectives, goal or destination.

The how

• /strategies
• /optimization strategies is the way to optimize the current system.
• /development strategies is the way to develop the current system.

The how of "what + how"

• /tools
• Organization principles is a tool to plan the way to optimize and develop the current system.
• Process principles is a tool to work the way planned.

Explanations

Organization level

• Objectives are made for a very long term planning.
• Strategies are made for a long term planning and translated from composition & objectives [grouped by output].
• Projects are made for a middle term planning from mixed strategy parts [grouped by work type and strategies].
• Tasks are made for a short term planning from mixed projects parts [grouped by work type].

These 4 point above are organizational (process description) and sorted from a high level to a low level.

• High level -> lowly precise process description, morely grouped by objective and plan type.
• Low level -> highly precise process description, morely grouped by skills and process type.
• Organization principles are tools to write and precise these process descriptions also called objectives, strategies, projects and tasks.
• Process principles are tools to translate process descriptions into mechanical and biological process.

Using "Organization principles" doc [Describe]

• What: [composition & objectives] ->

• How: [composition optimization & objectives development] ->

• Projects (How layer 2): [GitHub projects & GitHub milestone (with the same name)] ->

• Tasks (How layer 3): [GitHub issues filtered by skills(label) & projects(milestone)].

Using "Process principles" doc [Process]

• Tasks: -> Mechanical and biological process [Your process]

Shema visualitation

---

Any thoughts like feedback, ideas and comments on the way to improve this file is greatly appreciate.