Kirk Samuda, Java Reusability
Java Reusability
Reusability
Introduction
This week’s team project asked that the team demonstrate reusability within Java. Java has been classified as an object oriented language that promotes polymorphism. Polymorphism is the act of reusing an object or code that has previously existed to make Java codes easier to write, modify and re- use. This week’s task requires each team to replace a group of codes or module of one team members program, with another team member’s code. This paper will address some of the challenges of this task, to include how the two programs were selected, the process of identifying the classes or functions for replacement, and the changes needed to make the final Java application program work properly, by highlighting the impact of modular concatenation in this exercise.
Program 1 selected
(************ – Array.java)
Program 2 selected
(Kirk Samuda’s – SalesearningArray.java)
Final Products
Reusability.java and Reusability. Class
Programs Selected
The first program that was chosen was (Michael Spears – Array.java). The second program chosen was (Kirk Samuda’s – SalesearningArray.java). These programs were chosen because the other team members’ codes would not offer the transitional simplicity desired, or the reusability required. Bear in mind, that all other programs did exercise satisfactory parameters for the task at hand; however only two satisfied the criteria that made the concatenation of two modules simple, and none time consuming.
The two programs selected as outlined above, were created by Mike and Kirk and display codes that permitted easier merger, and minimal cosmetic changes. Array names were changed to permit the smooth transition of the concatenation, and optimal functionality. These codes were selected by all team members, and placed into NET-Beans to ensure the task objective is satisfied. Each team member contributed to the type of layout that was relevant and most appropriate for the
Reusability
Introduction
This week’s team project asked that the team demonstrate reusability within Java. Java has been classified as an object oriented language that promotes polymorphism. Polymorphism is the act of reusing an object or code that has previously existed to make Java codes easier to write, modify and re- use. This week’s task requires each team to replace a group of codes or module of one team members program, with another team member’s code. This paper will address some of the challenges of this task, to include how the two programs were selected, the process of identifying the classes or functions for replacement, and the changes needed to make the final Java application program work properly, by highlighting the impact of modular concatenation in this exercise.
Program 1 selected
(************ – Array.java)
Program 2 selected
(Kirk Samuda’s – SalesearningArray.java)
Final Products
Reusability.java and Reusability. Class
Programs Selected
The first program that was chosen was (Michael Spears – Array.java). The second program chosen was (Kirk Samuda’s – SalesearningArray.java). These programs were chosen because the other team members’ codes would not offer the transitional simplicity desired, or the reusability required. Bear in mind, that all other programs did exercise satisfactory parameters for the task at hand; however only two satisfied the criteria that made the concatenation of two modules simple, and none time consuming.
The two programs selected as outlined above, were created by Mike and Kirk and display codes that permitted easier merger, and minimal cosmetic changes. Array names were changed to permit the smooth transition of the concatenation, and optimal functionality. These codes were selected by all team members, and placed into NET-Beans to ensure the task objective is satisfied. Each team member contributed to the type of layout that was relevant and most appropriate for the