/* The C-like comments, such as this one, are my (Philippe MARTIN's) comments.
Despite the errors, this is a good first structured learning journal.
Consider this document as complementary to the 3 other documents illustrating
what to do and what not to do when creating a structured learning journal. */
workflow_management part: optimizing_a_work_assignment (cm) sustaining_documentation_flow (cm) reviewing_the_status_of_work (cm); optimizing_a_work_assignment previous_task: collecting_who_or_what_is_available_to_perform_a_work (cm), part: assigning_the_most_effective_person_for_a_work (cm); //"not necessarily the most nominally qualified since this person may be sick"(cm) collecting_who_or_what_is_available_to_perform_a_work part: establishing_a_profile_of_each_resource (cm); sustaining_documentation_flow part: follow_up_processing_when_information_does_not_arrive_on_time (cm) keeping_an_auditable_trail (cm), synonym: generating_a_rendezvous (cm); /* is generating_a_rendezvous identical to sustaining_documentation_flow or actually a subprocess of it? */ keeping_an_auditable_trail part: documenting_work_and_its_process (cm) logging_each_task_in_the_process (cm), purpose: "improving privacy and security" (cm), example: "medical records" (cm); /* a record is not an example of a process */ reviewing_the_status_of_work object: status (cm), part: accommodating_for_changes_in_the_process (cm); accommodating_changes_in_the_process part: passing_the_work_for_consultation (cm) resuming_the_normal_workflow (cm); workflow_technology object: workflow (cm), /* "synonym:", not "object:" */ synonym: workflow_category (cm), specialisation: adhoc_workflow (cm) production_workflow (cm) administrative_workflow (cm) autonomous_workflow (cm) horizontal_workflow (cm) vertical_workflow (cm); /* good! */ adhoc_workflow synonym: collaborative (cm), /* should be collaborative_workflow */ /* is it true that an adhoc_workflow is always a collaborative_workflow, and conversely? */ part: negotiation_step (cm) acceptance_step (cm) assignment_step (cm) review_step (cm), /* parts of something like creating_an_adhoc_workflow, not of adhoc_workflow */ usage: "smaller amounts of work" (cm), /* an adhoc_workflow may have for usage "smaller amounts of work" ??? */ delivery: mail_message (cm); negotiation_step example: "a contractor requesting a review of work with a deadline" (cm); acceptance_step example: "an actor submitting to do a work task that has been requested" (cm); assignment_step example: "a principal delegating the work to their contractors" (cm); review_step part: approving_the_completion_of_work (cm) handling_incomplete_work (cm), example: "a principal approving the work of their contractors" (cm); production_workflow /* same notes as for adhoc_workflow */ part: creating_a_general_procedure (cm) additional_steps_as_required (cm) predefined_work (cm) prioritized_work (cm), example: "settling a claim following an auto accident" (cm), usage: "larger amounts of work" (cm), delivery: dedicated_work_channel (cm); administrative_workflow part: adhoc_workflow (cm) production_workflow (cm), delivery: mail_message (cm) dedicated_work_channel (cm); vertical_workflow part: directing_workflow_through_the_processes (cm), purpose: "checking that all the tasks are completed" (cm); directing_workflow_through_the_processes part: providing_guidance_for_each_step_of_the_process (cm), example: "dynamically invoke a computer program" (cm); horizontal_workflow synonym: routing (cm), /* case_routing_process? routine_structure? is any of these identical to horizontal_workflow? */ part: movement_of_work_through_the_organization (cm); autonomous_workflow part: separate_workflow_application (cm) application_integrator (cm), synonym: stand-alone (cm), /* stand-alone_workflow */ antonym: embedded (cm), /* embedded_workflow */ example: "workflow installed on desktops for order processing may also be useful for personnel records work" (cm); application_integrator usage: "system with many applications" (cm); business_process_engineering synonym: BPE (cm), part: identifying_a_critical_success_factor (cm) employing_a_work_system_framework (cm) process_evaluation (cm) business_process_reengineering (cm); identifying_a_critical_success_factor object: critical_success_factor (cm), part: identifying_organisations_primary_mission (cm) defining_CSF (cm) identifying_the_pertinent_indicators_of_performance_for_each_CSF (cm) deciding_on_a_critical_measurement (cm), agent: senior_manager (cm); defining_CSF previous_task: identifying_organisations_primary_mission (cm), part: defining_factors_that_must_go_right_for_the_business_to_succeed (cm) defining_3_or_4_business_processes (cm); deciding_on_a_critical_measurement previous_task: identifying_organisations_primary_mission (cm) defining_CSF (cm) identifying_the_pertinent_indicators_of_performance_for_each_CSF (cm), part: generating_IS_that_can_collect_each_measurement (cm); employing_a_work_system_framework object: work_system (cm), purpose: "promoting an organised approach for understanding IT systems from a business viewpoint" (cm), part: analysing_customers (cm) investigating_products_and_services (cm) reviewing_business_processes (cm) defining_participants (cm) assessing_the_information_for_processes (cm) identifying_technologies (cm) addressing_the_context_of_the_system (cm) utilising_infrastructure (cm) defining_performance_variable (cm); work_system /* a collection/description cannot have process has parts */ informal_definition: "a collection of interactive components that work together to achieve a defined outcome" (cm), part: defining_a_purpose_of_the_system (cm) //"eg payroll system" (cm) identifying_who_is_involved_with_the_system (cm) //"eg employees" (cm) discovering_the_processes_involved (cm) //"eg calculate pay" (cm) identifying_what_information_is_involved (cm) //"eg hours worked" (cm) defining_the_forms_of_technology_involved (cm) //"eg spreadsheet" (cm); process_evaluation synonym: process_improvement (cm), /* improvement follows evaluation */ part: understanding_the_current_system (cm) redefining_a_new_process (cm); understanding_current_system part: describing_a_business_process (cm) assessing_the_performance_of_a_process (cm); redefining_a_new_process part: describing_a_business_process (cm) assessing_the_performance_of_a_process (cm); describing_a_business_process part: defining_the_degree_of_structure (cm) assessing_the_range_of_involvement (cm) investigating_the_level_of_integration (cm) defining_the_rhythm (cm) understanding_the_complexity (cm) identifying_the_reliance_on_machines (cm) reviewing_the_prominence_of_planning_and_control (cm) measuring_the_attention_to_errors_and_exceptions (cm); defining_the_degree_of_structure specialisation: highly_structured (cm) semi_structured (cm) unstructured (cm); assessing_the_range_of_involvement scope: too_many_people (cm) too_few_people (cm); /* assessing_the_range_of_involvement may have for scope too_many_people ??? */ investigating_the_level_of_integration level: common_culture (cm) common_standard (cm) information_sharing (cm) coordination (cm) collaboration (cm); /* investigating_the_level_of_integration may have for level common_culture ??? */ defining_the_rhythm informal_definition: "the frequency and predictability of the process" (cm), example: "how quickly can the system adjust to changes in its transaction processing load" (cm); understanding_the_complexity part: defining_the_simplicity_of_a_process (cm); //"simple processes may not meet processing requirements while too complex are harder to maintain" (cm) identifying_the_reliance_on_machines part: identifying_the_critical_nature_on_the_technology (cm); reviewing_the_prominence_of_planning_and_control part: checking_planned_output_rates_are_being_achieved (cm); measuring_the_attention_to_errors_and_exceptions part: timing_the_resolution_of_a_problem (cm); assessing_the_performance_of_a_process purpose: "determining if the process is a candidate for improvement" (cm), part: developing_a_table_matrix (cm) defining_a_performance_variable (cm) recording_the_measurement (cm); recording_the_measurement part: collecting_metrics_that_are_necessary_to_provide_a_realistic_assessment (cm) collecting_metrics_that_provide_analysis_to_the_complexity_of_the_business_process (cm), tool: spreadsheet_package (cm); defining_performance_variable purpose: "providing objectively based measurements for more effective analysis" (cm), part: analysing_activity_rate (cm) analysing_output_rate (cm) analysing_consistency (cm) analysing_productivity (cm) analysing_cycle_time (cm) analysing_downtime (cm) analysing_security (cm); analysing_activity_rate part: defining_the_number_of_interim_work_steps_that_are_performed_in_a_given_timeframe (cm); analysing_output_rate part: assessing_the_quality_produced_in_a_timeframe (cm); analysing_consistency part: recognising_a_processes_ability_to_operate_within_set_guidelines (cm); analysing_productivity part: contrasting_the_product_to_the_resources_spent (cm); analysing_cycle_time part: recording_the_time_from_process_start_to_process_finish (cm); analysing_downtime part: reviewing_the_percentage_of_time_that_the_process_is_not_available (cm); analysing_security part: assessing_how_secure_the_system_is_against_contributing_factors (cm);
pi_calculus purpose: "analysing communicating systems" (cm); //"not suitable to be applied as a standard" (cm)
dedicated_work_channel example: "clerks in procurements who complete the same work processes all day" (cm); status informal_definition: "the workflow product's unique way to move the work to the next step in the process" (cm); critical_success_factor synonym: CSF (cm), informal_definition: "an approach for identifying those factors that are critical to a business operation's success" (cm);