a guest Jan 24th, 2019 79 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. Discuss changes in the following characteristics from one stage to another stage during the CSS life cycle model.
  2. • 1.1. Staff expertise
  3. -   During initial development the required expertise from the staff can change drastically due to the software changing itself
  4. -   In the evolution phase there isn’t need for wide range of expertise but rather a deeper understanding of what they’re developing
  5. -   In the servicing phase the expertise shift to servicing and maintenance. In essence, the staff needs to know how to keep the system running for their customers.
  6. -   In the phaseout stage the you need expertise to devise and implement an exit strategy. These involves expertise on legacy systems and data migration.
  7. • 1.2. Software architecture
  8. -   The software architecture should be done in the initial development stage
  9. -   In evolution phase changes are possible but more risky and costly
  10. -   In the servicing stage you would need to reverse engineer the system and make it almost completely new, usually not worth it
  11. -   In the phaseout stage there’s value in analysing the old system but focus should be on the new one.
  12. • 1.3. Software decay
  13. -   Following guidelines during development can reduce future decay
  14. -   Code decay should be visible in the servicing phase making some changes unfeasible
  15. -   High percentage of code decay can be a reason to initiate phaseout stage
  16. • 1.4. Economics
  17. -   Initial development is generally the time of investments and little income. With funding it might be different.
  18. -   Economic reasons might drive design decisions
  19. -   After the release of the software it should start to profit
  20. -   Phaseout stage is generally initiated due to little profit from the system
  22. How would each of the following groups use the information contained in a CR?
  23. • 2.1 Maintainers
  24. -   Identify the actual changes that the code requires
  25. -   CR works as a guide for fixes
  26. -   Communication between teams
  27. • 2.2 Management
  28. -   Keep track of the CRs to better understand the state of the system
  29. -   Classification, statistics and analysis
  30. -   Assign resources and employees
  31. • 2.3 Quality and Test engineers
  32. -   Reproducing the bug
  33. -   Generate tests for the issues
  34. -   Identify issues around the problem in the CR
  35. • 2.4. Customers
  36. -   Gain understanding about the system
  37. -   Track their issues
  38. -   Communication tool
  40. 3. (3-4) What is the difference between change propagation and change impact analysis?
  41. -   Impact analysis focuses on single units and changes to determines what kind of effects it has.
  42. -   Propagation aims to analyse changes throughout the system from a single change.
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand