Chapter 8
Review Questions
1. b
2. c
3. a,c
4. b
5. a,b
6. d
7. b
8. b
9. a
10. c
11. b
12. b
13. b
14. d
15. a,c
16. Dependencies on packaged program units are driven by the package specification. Any changes to the header of the packaged program units being referenced will change the status of the dependent object to INVALID. Changes to the body only will not alter the status of dependent objects.
17. BASK_CALC_SP ORDER_TOTAL_SP
18. To be aware of affected objects and the recompilation needs. A developer should test any dependent program units and recompile objects made INVALID manually to avoid this processing at runtime. In addition, remote dependencies will cause a runtime error if objects not recompiled.
19. If a
…show more content…
ARCHAR2) IS
BEGIN
SELECT idstage INTO p_stage FROM bb_basketstatus WHERE idBasket = p_bask; p_desc := lookup_pkg.status_desc_pf(p_stage);
END;
/
SELECT status FROM user_objects WHERE object_name = 'STATUS_CHECK_SP ';
CREATE OR REPLACE PACKAGE BODY lookup_pkg IS
FUNCTION status_desc_pf (p_stage IN NUMBER) RETURN VARCHAR2 IS lv_stage_txt VARCHAR2(30);
BEGIN
IF p_stage = 1 THEN lv_stage_txt := 'Order Submitted '; ELSIF p_stage = 2 THEN lv_stage_txt := 'Accepted, sent to shipping '; ELSIF p_stage = 3 THEN lv_stage_txt := 'Backordered '; ELSIF p_stage = 4 THEN lv_stage_txt := 'Cancelled '; ELSIF p_stage = 5 THEN lv_stage_txt := 'Shipped '; ELSIF p_stage = 6 THEN lv_stage_txt := 'Credit Card Not Approved '; END IF; RETURN lv_stage_txt;
END;
END;
/
SELECT status FROM user_objects WHERE object_name = 'STATUS_CHECK_SP ';
Assignment 8-4
Note: Be sure to use an appropriate connection string reference for the database link
CREATE DATABASE LINK dblink2 USING 'orcl ';
CREATE OR REPLACE FUNCTION status_desc_sf (p_stage NUMBER) RETURN VARCHAR2 IS lv_stage_txt VARCHAR2(30);
BEGIN
IF p_stage = 1 THEN lv_stage_txt := 'Order Submitted '; ELSIF p_stage = 2 THEN lv_stage_txt := 'Accepted, sent to shipping '; ELSIF p_stage = 3 THEN lv_stage_txt := 'Backordered '; ELSIF p_stage = 4 THEN lv_stage_txt := 'Cancelled '; ELSIF p_stage = 5 THEN lv_stage_txt := 'Shipped '; END IF; RETURN
MPI: The fault-tolerance mechanism in MPI depends either on handling failure in the application itself or implementing regular checkpoint files.
Use relationships to manage dependencies. Many assets have dependencies, or requirements that are beyond the asset itself in order to be complete, to work, or to build. For example a Build or an Implementation asset type might have dependencies that are required for the asset to be complete or valid. Assets may require certain binary and jar files that are dependencies for the build or implementation.
This type of failure can only happen on a distributed system. An example of this is: in a distributed system, 1 computer sends a message to another computer either asking the computer if it’s responsive, requesting information from the computer, or replying back to the other computer that asked if it is responsive. This can cause problems when computer A sends computer B a message asking if it’s responsive, however the message never gets to computer B therefore computer B never responds and computer A assumes that computer B is down.
To avoid code errors, software developers while writing code should follow the Single Responsibility Principle, that is they should focus on one main task, keep all the classes with a simple logic if possible. Once the class of any program is developed than perform extensions on that class and use for building other related functionality but should not do any type of modifications, which says the Open/Closed principle. This principle encourages to use composition, interfaces, inheritance- which can generate other class that can be extended without modifying the source code. If necessary, developers should make use of Liskov 's Principle "it means making sure that new derived classes are extending the base classes without changing their
is not fixed or reconstructed, there will be even bigger problems for the future, such as no
dependability, one can neither performproperly in a workspace, and also can not be depended on by there
As for implementing these changes can cause some problems and issues, moreover this is time consuming process.
They proposed an approach for the detection of refused bequest code smell. The approach performs static analysis of the code for the identification of suspicious hierarchies and dynamic unit test execution is done for the determination of subclasses that actually contain the smell. Various characteristics such as number of overridden methods, invocation of super class methods and results from test execution are used to sort the identified smells according to their intensity. The approach has been evaluated on an open source project named “SweetHome3D” containing 76730 LOC. They have implemented their approach as jDeodorant Eclipse plug-in extension.
Dependent: The dependent variable is the time as it will be the aspect being measured and recorded.
3. What considerations should be taken into account when making decisions about the package count?
As with most development AntiPatterns, both architectural and executive viewpoints play hint roles in first banning and ongoing adjustment against them. It's through an architectural opinion that an emerging AntiPattern is often known, and through functional management that it is properly addressed when not prevented
As a result of these problems, the program could cease to exist unless a solution is found.
A change in legislation- A change in legislation normally affects external factors because legislation is all about laws within the project, and if suddenly legislation changes, then it can alter what path the project goes in, who works on the project, and how the project works in terms of rules, and security.
A dependency detection approach may or may not provide a measure of confidence for detected dependencies. To have a confidence level for each dependency detection approach can help the administrators to decide and choose their most important dependencies based on the most reliable information.
An OnDemand system has one library server and one or more object servers. An object server can operate on the same server or node as the library server or on a different server or node than the library server.