Among other things, this week we learned about the software lifecycle. First of all, there is a difference between patches, updates and upgrades. Until this week I have not been aware of the fact that these three have different characteristics. But this week it became clear that where a patch corrects bugs and mistakes of a software and performs only minor updates, an update goes a step further by adding new minor features to a software. An upgrade adds even major new features and functionality.
Furthermore, for using a particular software, people might need to be trained. This can happen with the help of different methods. There is e.g. the hands-on method, where people are trained in a practical way, in contrast to the in person, classroom-style. Additionally training can be delivered via the internet or community based, through forums, blogs and web pages.
Last but not least, we learned about different conversion strategies. There are mainly four of them, namely:
1) Parallel
2) Pilot
3) Phased
4) Direct (Cutover)
In the parallel method a new software is run parallel to the old, known one, which minimizes the risk of adopting the new software. By using the pilot strategy, there is firstly a small group using the new software before a whole company might addict to the new software. The phased strategy means that the new software is adopted step by step, whereas the direct/cutover strategy means that you adopt the new software all at once. In this last strategy the risk of failure is biggest, but of course, at the same time, this one is the fastest of all methods.
To further illustrate the differences between these three methods I included some pictures below.
No comments:
Post a Comment