Nt1310 Unit 3 Assignment Of Module Analysis

1512 Words4 Pages

1. State why it is a good idea to test a module in isolation from other modules. During unit testing, each module is unit tested to determine the correct working of all the individual modules. It involves testing each module in isolation as this is the most efficient way to debug the errors identified at this stage. So it is always a good idea to test a module in isolation from other modules. Why different modules making up a software product are almost never integrated simultaneously. Integration of different modules is undertaken once they have been coded and unit tested. During the integration and system testing phase, the modules are integrated in a planned manner. The different modules making up a software product are almost never …show more content…

Firstly, these types of systems are installed in an environment which instantly adapts to the complex system and starts generating new requirements from the very moment it starts using it. These new requirements may occur because only after a process of trial and error can one truly see what functions with a system and what does not; and these things may not have been evident before the installment of the complex system. As a part of evolution, the user's own requirements will also change and, in a way, become more demanding. As business policies and goals evolve and transform, new requirements will be generated for complex systems as well. It is this evolution and demand that will prompt the changes that also have to affect the complex system for it to match with what is being asked and expected of it. Change is essential for a complex system to preserve its usefulness. As long as a system is in accordance with the definition of "complex”, change will occur naturally and automatically in order to increase efficiency and effectiveness (Kirshbaum, 2002). Although change is accepted as a natural occurrence in complex systems, there are certain ways in which this change can be …show more content…

Another process activity useful for the prediction of changes is requirements-driven impact analysis or RIDA, for short. This analysis is used to pinpoint which software entities need to be altered in order to be able to implement a certain requirement (Lindvall, 1998). RIDA, which is conducted during the release planning phase, takes two variables into consideration. Firstly, there is the input, which refers to the existing complex system and the set of requirements. Secondly, there is the output, which represents the specific software entities that have to be changed to meet each requirement. The main idea one has to understand is that change is not an exception, but rather, the only constant in life (Brooks, 1975). To some extent, changes in complex systems can be predicted and the system can be altered in such a way that it becomes resilient to these transformations. Nonetheless, change in complex systems has to be accepted as an invariable constant and a natural component in evolution.

More about Nt1310 Unit 3 Assignment Of Module Analysis

Open Document