Difference between revisions of "Bookkeeping Quarter"
(→Concepts) |
(→Concepts) |
||
| Line 13: | Line 13: | ||
#*[[Lessons learned]]. The learning gained from the process of performing the project. Lessons learned may be identified at any point. | #*[[Lessons learned]]. The learning gained from the process of performing the project. Lessons learned may be identified at any point. | ||
#*[[Lessons learned process]]. A process improvement technique used to learn about and improve on a process or project. A lessons learned session involves a special meeting in which the team explores what worked, what didn't work, what could be learned from the just-completed iteration, and how to adapt processes and techniques before continuing or starting anew. | #*[[Lessons learned process]]. A process improvement technique used to learn about and improve on a process or project. A lessons learned session involves a special meeting in which the team explores what worked, what didn't work, what could be learned from the just-completed iteration, and how to adapt processes and techniques before continuing or starting anew. | ||
| + | #'''[[Reporting]]'''. | ||
| + | #*[[Internal reporting]]. | ||
| + | #'''[[Reporting principle]]'''. | ||
| + | #'''[[Public relations]]'''. | ||
#'''[[Data research]]'''. | #'''[[Data research]]'''. | ||
#*[[Qualitative research]]. | #*[[Qualitative research]]. | ||
| Line 32: | Line 36: | ||
#*[[Glossary]]. A list and definition of the business terms and concepts relevant to the solution being built or enhanced. | #*[[Glossary]]. A list and definition of the business terms and concepts relevant to the solution being built or enhanced. | ||
#*[[Jargon]]. Specialized terminology or technical language that members of a group use to communicate among themselves. | #*[[Jargon]]. Specialized terminology or technical language that members of a group use to communicate among themselves. | ||
| − | #'''[[ | + | #'''[[Data manipulation]]'''. |
#*[[Filtering]]. A sender's manipulation of information so that it will be seen more favorably by the receiver. | #*[[Filtering]]. A sender's manipulation of information so that it will be seen more favorably by the receiver. | ||
#*[[Filtering]]. The deliberate manipulation of information to make it appear more favorable to the receiver. | #*[[Filtering]]. The deliberate manipulation of information to make it appear more favorable to the receiver. | ||
| − | |||
| − | |||
| − | |||
| − | |||
#'''[[Categorization]]'''. | #'''[[Categorization]]'''. | ||
#*[[Structural rule]]. Structural rules determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time. | #*[[Structural rule]]. Structural rules determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time. | ||
Revision as of 16:13, 5 April 2018
Organizational Learning Quarter (hereinafter, the Quarter) is the first of four lectures of Operations Quadrivium (hereinafter, the Quadrivium):
- The Quarter is designed to introduce its learners to enterprise discovery, or, in other words, to concepts related to obtaining data needed to administer the enterprise effort; 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.
Contents
Outline
The predecessor lecture is Workteam Leadership Quarter.
Concepts
- Learning. Any relatively permanent change in behavior that occurs as a result of experience.
- Lessons learned. The learning gained from the process of performing the project. Lessons learned may be identified at any point.
- Lessons learned process. A process improvement technique used to learn about and improve on a process or project. A lessons learned session involves a special meeting in which the team explores what worked, what didn't work, what could be learned from the just-completed iteration, and how to adapt processes and techniques before continuing or starting anew.
- Reporting.
- Reporting principle.
- Public relations.
- Data research.
- Data structure.
- Data model. An analysis model that depicts the logical structure of data, independent of the data design or data storage mechanisms.
- Optionality. Defining whether or not a relationship between entities in a data model is mandatory. Optionality is shown on a data model with a special notation.
- Cardinality. The number of occurrences of one entity in a data model that are linked to a second entity. Cardinality is shown on a data model with a special notation, number (e.g., 1), or letter (e.g., M for many).
- Data flow diagram (DFD). An analysis model that illustrates processes that occur, along with the flows of data to and from those processes.
- State diagram. An analysis model showing the life cycle of a data entity or class.
- Sequence diagram. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
- Class model. A type of data model that depicts information groups as classes.
- Data dictionary. An analysis model describing the data structures and attributes needed by the system.
- Data entity. A group of related information to be stored by the system. Entities can be people, roles, places, things, organizations, occurrences in time, concepts, or documents.
- Attribute. A data element with a specified data type that describes information associated with a concept or entity.
- Glossary. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
- Jargon. Specialized terminology or technical language that members of a group use to communicate among themselves.
- Data manipulation.
- Categorization.
- Structural rule. Structural rules determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
- Knowledge area. A group of related tasks that support a key function of business analysis.
- Repository. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
- Interoperability. Ability of systems to communicate by exchanging data or services.
Methods
Instruments
Results
Practices
The successor lecture is Business Intelligence Quarter.
