Term
click below
click below
Term
Normal Size Small Size show me how
procedurally
2.1 - thinking procedurally
Term | Definition |
---|---|
identifying components of problems benefits | allows the solver to break the problem down into smaller/more manageable chunks, making the solution easier to make and reducing the waste of resources |
representing the components of a problem | using a top-down modular design/structure diagram and using stepwise refinement to break down 1 task into multiple parts that can be broken down themselves if needed |
benefits of using a structure diagram | since each sub-problem is represented visually, they can easily be allocated to different people if needed for a more efficient process |
producing a solution | producing a solution to each sub-problem often individually (can be done via visually representing the final output and working backwards), before combining them to solve the problem (along with debugging iteratively and terminally) |
identifying the steps to a solution | since most programs are event driven, flowcharts or pseudocode can be used to decide the order of events and its linearity |
identifying sub-routines | each sub-problem can be addressed with a function (or similar), with the parameters (and/or return values) known. this can also be used to identify when code can be reused, repurposed or remade to make the process more efficient across sub-problems |