Learning Journal 3 - Chris Morgan 2166646

/* Apart from the absence of the sources (page number or module name), it's good!
"phase" is more precise than "part" but "part" is a standard name. */

PROCESS

business_process_reengineering
   phase: diagnosis_phase (cm)   redesign_phase (cm)  reconstruction_phase (cm)
          operational_phase (cm);

      diagnosis_phase
         part: analysis_of_current_process (cm)   
               analysis_of_problems_caused_by_current_process (cm);

      redesign_phase
         part: designing_new_process_from_start (cm),
         previous_task: diagnosis_phase (cm);

            designing_new_process_from_start
               informal_definition: "basing a process independent of current 
                                     organisational structure and available 
                                     resources" (cm);

      reconstruction_phase
         part: defining_a_new_process_definition (cm)   
               defining_a_new_IT_system (cm)
               defining_a_new_organisational_structure (cm),
         previous_task: redesign_phase (cm);

      operational_phase
         part: measuring_the_performance_of_a_process (cm)
               identifying_bottlenecks_in_a_process (cm)
               launching_a_new_reengineering_cycle (cm); 
               //"this is not always the case though" (cm)    
         previous_task: operational_phase (cm);

rapid_application_development
   part: evolutionary_development (cm)   incremental_development (cm),
   synonym: RAD (cm),
   phase: requirements_planning_phase (cm)   user_design_phase (cm)
          construction_phase (cm)   delivery_phase (cm);

   evolutionary_development
      tool: prototyping (cm),
      purpose: "improving the communication between developers and users via 
                evolving the specifications and the system into the operational
                system" (cm);

   incremental_development
      part: separating_development_into_stages (cm),   
      purpose: "delivering a new version of the system at each end of the stage
                to simplify development" (cm);

   requirements_planning_phase
      part: identifying_an_intended_project_result (cm)
            setting_guidelines_for_functionality_of_the_system (cm)
            planning_the_development_route (cm);

   user_design_phase
      part: organising_the_systems_functionality (cm)
            conducting_joint_application_design_workshop (cm),
      tool: CASE_tool (cm)   prototyping (cm),
      agent: end_user (cm)   system_developer (cm);   

   construction_phase
      part: validation_of_the_design (cm)
            refining_the_generated_software (cm);

   delivery_phase
      part: acceptance_testing (cm)   user_training (cm)   
            installation_of_system (cm);
  
interactive_process_oriented_system_development
   part: business_process_reengineering (cm)   
         rapid_application_development (cm),
   synonym: IPSD (cm),
   principle: "focus on the business process" (cm)
              "obtain senior management commitment to the project" (cm)
              "decisions should be taken within the development team" (cm)
              "get the developers and the users to work as a team" (cm) 
              "place emphasis upon project targets" (cm)
              "evolve the system's specification during development" (cm)
              "errors are permissible during development" (cm)
              "achieve a tangible result rather than the perfect solution 
               the first time" (cm)
              "update the overall planning at the end of each phase" (cm),
   phase: preparation_phase (cm)  diagnosis_phase (cm)   
          process_redesign_phase (cm)  requirements_phase (cm)   
          architecture_phase (cm)  component_design_phase (cm)
          construction_phase (cm)  integration_phase (cm)   delivery_phase (cm)
          enactment_phase (cm)  monitor_and_improve_phase (cm);    

   preparation_phase
      part: appointing_the_core_project_team (cm)
            drafting_the_project_plan (cm)
            obtaining_approval_for_the_project (cm)
            communicating_the_mission_statement_and_schedule (cm),
      output: overall_project_plan (cm);
   
   diagnosis_phase
      previous_task: preparation_phase (cm),
      part: analysis_of_the_existing_situation (cm)
            identifying_parts_of_the_system_for_the_project (cm)
            focussing_on_possible_direction (cm),
      output: key_performance_indicator (cm)  use_case (cm)
              null_measurement (cm)  boundary_conditions_on_time_and_money (cm)
              ideas_for_improvement (cm)
              intended_process_to_be_reengineered (cm);       
 
      analysis_of_the_existing_situation
         part: analysing_the_reasons_for_change (cm)
               identifying_the_critical_success_factor (cm)
               formulating_the_objectives_to_be_met (cm)
               defining_the_key_performance_indicator (cm)
               determining_the_existing_performance_indicator (cm);

      identifying_parts_of_the_system_for_the_project
         synonym: scoping_the_project (cm),
         part: identifying_parts_of_organisation_under_scope_of_project (cm)
               identifying_parts_of_processes_under_scope_of_project (cm)
               determining_boundary_conditions_on_time_and_money (cm);

      focussing_on_possible_directions
         synonym: envisioning_the_project (cm),
         part: generating_ideas_and_guidelines_for_redesign (cm)
               specifying_targets_for_the_project (cm);
      
   process_redesign_phase
      previous_task: diagnosis_phase (cm),
      part: modelling_the_existing_situation (cm)
            developing_alternatives_for_new_business_process (cm)
            analysing_selected_alternative (cm)
            analysing_key_performance_indicator (cm) 
            describing_consequences_for_the_organisation (cm)
            evaluation_of_design_criteria (cm),
      output: calibrated_model_of_existing_process (cm)  use_case (cm)
              model_for_new_process (cm)  test_results_of_simulation (cm)
              organisational_model (cm);

      evaluation_of_design_criteria
         part: time_evaluation (cm)   quality_evaluation (cm)
               cost_evaluation (cm)   flexibility_evaluation (cm);

         time_evaluation
            specialisation: service_time_evaluation (cm)   
                            transport_time_evaluation (cm)
                            waiting_time_evaluation (cm);
         
         quality_evaluation
            specialisation: internal_quality_evaluation (cm)   
                            external_quality_evaluation (cm);

            internal_quality_evaluation 
               requirement: "evaluating the conditions of work" (cm);

            external_quality_evaluation
               requirement: "evaluating the satisfaction of the customer" (cm);

         cost_evaluation
            specialisation: processing_cost_evaluation (cm)   
                            human_cost_evaluation (cm);          

         flexibility_evaluation
            specialisation: resource_flexibility_evaluation (cm)
                            process_flexibility_evaluation (cm)
                            management_flexibility_evaluation (cm)
                            organisation_flexibility_evaluation (cm);
      
      developing_alternatives_for_new_business_process
         part: analysing_time_constraint (cm)
               analysing_quality_issue (cm)
               analysing_budget_factor (cm)
               assessing_flexibility_of_the_process (cm); 

      analysing_selected_alternative
         part: checking_the_necessity_of_each_task (cm)
               appointing_a_case_manager (cm)
               considering_the_size_of_each_task (cm)
               deciding_on_one_generic_process (cm)
               deciding_on_one_generic_task (cm)
               introducing_parallelism (cm)
               investigating_opportunities_in_IT (cm)
               improving_allocation_of_a_resource (cm)
               improving_communication_structure (cm)
               ordering_tasks_of_a_process (cm); 
   
   requirements_phase
      previous_task: process_redesign_phase (cm),
      part: preparing_requirements_workshop (cm)
            developing_risk_management_measurement (cm)
            developing_the_project_schedule_and_budget (cm)
            detailing_the_project_plan (cm),
      output: draft_data_model (cm)  draft_functional_model (cm)
              detailed_project_plan (cm);

   architecture_phase
      previous_task: requirements_phase (cm),
      part: describing_the_functional_architecture (cm)
            describing_the_technical_architecture (cm)
            illustrating_the_architecture (cm)
            establishing_a_standard (cm)
            developing_a_prototype (cm), 
     output: description_of_architecture (cm)  prototype (cm)
             standards_for_a_component (cm);

   component_design_phase
      previous_task: architecture_phase (cm),
      part: harmonising_data_model_with_user_interface (cm)
            integrating_a_data_component_with_a_workflow_definition (cm) 
            establishing_a_specification_of_a_link_with_an_office_system (cm),
      output: standard_of_user_interface (cm)
              specification_of_workflow (cm)
              specification_of_a_data_component (cm)  finalised_prototype (cm)
              description_of_a_link_for_an_office_system (cm);
  
   construction_phase
      previous_task: component_design_phase (cm),
      part: integrating_workflow_management_system (cm)
            setting_up_the_test_environment (cm)
            completing_the_system_documentation (cm)
            preparing_the_acceptance_test (cm), 
      output: components_for_integration_test (cm)
              system_documentation (cm)  conversion_software (cm)
              acceptance_test_plan (cm);
   
   integration_phase
      previous_task: construction_phase (cm),
      part: testing_the_conversion (cm)
            measuring_performance_of_integration_test (cm)
            rectifying_a_fault (cm)  producing_a_test_report (cm),
      output: environment_for_acceptance_test (cm)  test_script (cm)
              test_report (cm);
  
   delivery_phase  
      previous_task: integration_phase (cm),
      part: measuring_performance_of_acceptance_test (cm)
            rectifying_a_fault (cm)
            producing_an_acceptance_test_report (cm),
     output: production_environment (cm)  formal_acceptance (cm)
             acceptance_test_report (cm);

   enactment_phase
       previous_task: delivery_phase (cm),
       part: communicating_about_the_progress_of_the_project (cm) 
             preparing_enactment_documentation (cm) 
             supervising_training_of_new_system (cm)
             supervising_the_change_process (cm),
       output: enactment_plan (cm)  communications_plan (cm)
               conversion_plan (cm)  organisational_model (cm)
               case_description (cm)  system_manual (cm)
               training_material (cm);

   monitor_and_improve_phase
      previous_task: enactment_phase (cm),
      part: monitoring_measured_key_performance_indicator (cm)
            conducting_continuous_process_improvement (cm);     

TOOL

enterprise_application_integration_software
   synonym: EAI_software (cm),
   purpose: "identifies and links user workflow and application functions" (cm);

petri_net
   part: place (cm)   transition (cm)   arc (cm),
   specialisation: workflow_net (cm),
   purpose: "specify the routing of cases for a particular process" (cm);

   workflow_net
      requirement: "only one input place, one output place and no 
                    dead tasks" (cm);

      free_choice_workflow_net
         requirement: "for every two transitions there is a shared 
                       an input place"(cm);

      well_structured_workflow_net
         requirement: "maintaining consistency with AND connectors 
                       and OR connectors" (cm);

      s_coverable_workflow_net    
         informal_definition: "for any node there exists an S-component  
                               that contains this node" (cm);