Unit 3, Lesson 4, Task 3


DR QUINN: The P.I.E. cycle is a process for continually improving plans in an organization such as a business. The three steps are shown in this flow diagram.


In the first stage, planning, the improvement objectives are specified, together with the actions needed to achieve them. These action plans are then implemented in the organization. After a suitable period of time, the plans are evaluated by comparing the results of the implementation with the original objectives. This analysis leads to the specification of the next set of objectives and action plans, which brings us back to the beginning of the cycle.


Unit 3, Lesson 5, Task 2 Part 1


DR BELL: The waterfall model describes a process where software development goes down these five steps. You have them on your handout. Water always flows downhill, and this process is called the waterfall model to show that it moves in one direction (see these arrows), like a waterfall. It’s not easy going back to an earlier step to change things. It’s also very expensive. So the emphasis is on getting things right at each step, in particular the first step.


Unit 3, Lesson 5, Task 3 Part 2


DR BELL: In the first stage, the requirements for the system are gathered by talking to the customer and other people who will use it. These requirements are analyzed very carefully and in great detail. Requirements analysis is probably the longest stage in the process. This is to make sure the requirements are fully understood before the system is designed.


In the second stage, the system is designed. This means that the customer requirements are converted into software requirements by describing what the software will do. This involves dividing the system into its component parts so that they can be developed simultaneously by different teams. The design stage specifies what the programmers have to achieve.


Next, the code (the computer program) is written. In other words, the functional description of the system is converted into instructions that computers can follow. This is called the implementation stage, and is often the shortest in the process. At this stage, each programmer’s purpose is to make the program efficient, adaptable and bug-free.


Verification is the next stage. The whole system is installed and tested and evaluated to ensure that it does what it should do and that it’s acceptable to users, for example, by checking compatibility with other systems that the customer uses. It has to meet the requirements identified in the first stage.


Finally, once the customer has taken delivery, there is the maintenance ACCESS EAP: Foundations 205


Key words


continually plans steps stage objectives specified implemented evaluated original the analysis leads to


Key words


the waterfall model development steps downhill in one direction the emphasis in particular


Key words


the requirements in detail are gathered the customer are fully understood can be designed are converted describing dividing component parts simultaneously the programmers the code functional the program efficient adaptable


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142  |  Page 143  |  Page 144  |  Page 145  |  Page 146  |  Page 147  |  Page 148  |  Page 149  |  Page 150  |  Page 151  |  Page 152  |  Page 153  |  Page 154  |  Page 155  |  Page 156  |  Page 157  |  Page 158  |  Page 159  |  Page 160  |  Page 161  |  Page 162  |  Page 163  |  Page 164  |  Page 165  |  Page 166  |  Page 167  |  Page 168  |  Page 169  |  Page 170  |  Page 171  |  Page 172  |  Page 173  |  Page 174  |  Page 175  |  Page 176  |  Page 177  |  Page 178  |  Page 179  |  Page 180  |  Page 181  |  Page 182  |  Page 183  |  Page 184  |  Page 185  |  Page 186  |  Page 187  |  Page 188  |  Page 189  |  Page 190  |  Page 191  |  Page 192  |  Page 193  |  Page 194  |  Page 195  |  Page 196  |  Page 197  |  Page 198  |  Page 199  |  Page 200  |  Page 201  |  Page 202  |  Page 203  |  Page 204  |  Page 205  |  Page 206  |  Page 207  |  Page 208  |  Page 209  |  Page 210  |  Page 211  |  Page 212  |  Page 213  |  Page 214  |  Page 215  |  Page 216  |  Page 217  |  Page 218  |  Page 219  |  Page 220  |  Page 221  |  Page 222  |  Page 223  |  Page 224  |  Page 225  |  Page 226  |  Page 227  |  Page 228  |  Page 229  |  Page 230  |  Page 231  |  Page 232