hf

Workshop 11 - Week 13

1. Generalization and specialization in a class diagram relates to the concept of inheritance. When Several classes have a lot of attributes/methods in common, these can be generalized into a super class (or parent class) that contains the comment elements. Specialized class (sub classes or child classes) can then be created that inherits all the attributes and methods from the super class and has its own methods and/or attributes that are more specialized.

2. Change control is the act of coordinating a program as it changes throughout the construction process. One technique associated with change control is a program log, which has programmers indicating ‘signing out’ module of code to work on, then ‘signing in’ modules of code when complete. This aids not only in understanding where in the construction process a module lies, but also ensuring duplicate efforts are not being made, that the code is complete before testing.

3. The cost associated with finding and fixing a major software bug after a system has been implemented is very high. Therefore thorough testing of the system is imperative. It is not enough to have written program; it also needs to be tested completely to verify it performs as specified.

4. A testy is a particular aspect of the system that needs to be evaluated. The test plan outlines all of the tests that need to be performed on the system. Test cases are the sample data that will be run through or entered into the system. A test will state its objective, list the test cases that will check the desired feature or function, and define the expected result. Actual test results will also be recorded on the test.

5. A unit test checks a single program or program module to ensure that it performs the function designated in the program specification.

6. Integration testing evaluates whether a set of modules or programs work together successfully. The span of an integration test is more broad than unit testing, but not as broad as system testing.

7. System testing evaluates the entire system, not only to verify that it runs without error or breakdown, but also that it fulfills the business requirements of the system.
Acceptance testing is performed with the system users to confirm that the system is complete, that it meets the needs of the business area, and that it is acceptable to the users.

8. System documentation is created for the system developers, in order to document what was done during the development process, and to help them maintain the system after its installation. User documentatoin is designed specifically for the system users to help them work successfully with the system.

9. Both conversion strategies focus on the way in which users are switched over to the new system. Direct conversion is an abrupt change: the old system is ‘unplugged’ and the new system is turned on. The users have no choice but to work with the new system. In the parallel conversion strategy, the new system is turned on, but the old system is used simultaneously for a time. Clearly, the direct strategy is more risky because there is no fall-back if significant system bugs are discovered. With parallel conversion the old system will still be available if there is a major bug discovered in the new system. However, the cost and extra work of using both systems simultaneously must be considered.