Java Swing Retrieve Image From Database (MySQL) as BLOB - StudyViral

Java Swing Retrieve Image From Database (MySQL) as BLOB - StudyViral


Java Swing Retrieve Image From Database (MySQL) as BLOB (Binary Large Object) i.e. MySQL BLOB to Netbeans JLabel

This Video helps you to retrieve image from MySQL database.
Note: This video is in continuation of the last video Save Image to Database (MySQL) as BLOB
Link : https://youtu.be/DlnePp3Q6j8

Database connectivity with MySQL (Add "mysql-connector-java-5.1.9.jar" to Project Library)

Email :: info@studyviral.in
Or
Email :: studyviral.in@gmail.com
Website:: www.StudyViraL.in
Facebook Page ::  https://www.facebook.com/StudyViral.in/
For Suggestions You Can Email :: info@studyviral.in
http://studyviral.blogspot.in/

Read More

Java Swing - Save Image to Database (MySQL) as BLOB - StudyViral

Java Swing - Save Image to Database (MySQL) as BLOB - StudyViral

This video helps you to learn how to selecte image and display to JLabel and further save image to database as BLOB in Java JFrame (Java Swing - Save Image to Database (MySQL) as BLOB (Binary Large Object)).

Database connectivity with MySQL (Add "mysql-connector-java-5.1.9.jar" to Project Library)

Email :: info@studyviral.in
Or
Email :: studyviral.in@gmail.com 
Website:: www.StudyViraL.in 
Facebook Page ::  https://www.facebook.com/StudyViral.in/
For Suggestions You Can Email :: info@studyviral.in
http://studyviral.blogspot.in/

Read More

UGC NET JULY 2018 (Computer Science And Applications Paper-II) (Question 20)

UGC NET JULY 2018 (Computer Science And Applications Paper-II) (Question 20)

Q20. Which of the following statement is /are TRUE ?

P: Refactoring is the process of changing a software system in such a way that it does not alter the external behavior of the code yet improves the internal architecture.

Q: An example of refactoring is adding new features to satisfy a customer requirement discovered after a project is shipped.

(1). P only                                                                 (2). Q only
(3). Both P and Q only                                              (4). Neither P and Q

Answer : (3). Both P and Q only 

Reason : 

Refactoring is the process of changing a software system in such a way that it does not alter the external behavior of the code yet improves its internal structure. The statement is TRUE and given by MartinFowler in Refactoring Improving The Design Of Existing Code.

Refactoring essentially is cleaning up an existing code base to enable changes to be made more efficiently, or to improve the performance of the existing system.  Refactoring usually involves restructuring or rewriting portions of code which are convoluted, difficult to understand, poorly documented or unnecessarily complex.  Refactoring, the engineers argued, is essential to add future features, so developers should be given time to “refactor” existing code– even if it is the only activity in that sprint or release.

So Both the statements are TRUE. 

Read More

UGC NET JULY 2018 (Computer Science And Applications Paper-II) (Question 19)

 UGC NET JULY 2018 (Computer Science And Applications Paper-II) (Question 19)

Q19. Which of the following in not a key strategy followed by the clean room approach to software development ?

(1). Formal specification                                                        (2). Dynamic verification
(3). Incremental development                                                (4). Statistical testing of the system

Answer :  (2). Dynamic verification

Reason :

Cleanroom software development is a software development philosophy that is based on avoiding software defects by using formal methods of development and a rigorous inspection process. The name ‘Cleanroom’ was derived by analogy with semiconductor fabrication units. In these units (cleanrooms) defects are avoided by manufacturing in an ultra-clean atmosphere. The objective of this approach to software development is zero-defect software.

The Cleanroom approach to software development is based on five key strategies:

• Formal specification The software to be developed is formally specified. A state-transition model which shows system responses to stimuli is used to express the specification.
• Incremental development The software is partitioned into increments which are developed and validated separately using the Cleanroom process. These increments are specified, with customer input, at an early stage in the process.
• Structured programming Only a limited number of control and data abstraction constructs are used. The program development process is a process of stepwise refinement of the specification. A limited number of constructs are used and the aim is to apply correctness-preserving transformations to the specification to create the program code.
• Static verification The developed software is statically verified using rigorous software inspections. There is no unit or module testing process for code components.
• Statistical testing of the system The integrated software increment is tested statistically (see Chapter XX), to determine its reliability. These statistical tests are based on an operational profile which is developed in parallel with the system specification.

Read More

UGC NET JULY 2018 (Computer Science And Applications Paper-II) (Question 18)

UGC NET JULY 2018 (Computer Science And Applications Paper-II) (Question 18)

Q18. Reasons to re-engineer a software include :

P  : Allow legacy software to quickly adapt to the changing requirements.
Q : Upgrade to newer technologies/platform/paradigm (for example, object-oriented).
R : Improve software maintainability.
S  : Allow change in the functionality and architecture of the software.

Code:
(1).  P, R and S only                                                          (2).  P and R only  
(3).  P, Q and S only                                                          (4).  P, Q and R only

Answer : (4).  P, Q and R only

Software Re-engineer is a process of software development which is done to improve the maintainability of a software system. Technical Definition: Software Re-engineering is the examination and alteration of a system to reconstitute it in a new form.

The statement P is true because in re-engineering we can quickly adapt new changes which are required for software.

Q statement is also fine because new technology can be added to software by using software re-engineering. For example, changing function-oriented programs into object-oriented programs.

R statement is also true Refactoring is a re-engineering technique that aims at reorganizing a program without changing its behavior. It seeks to improve a program structure and its maintainability.

The statement Q is not included for Software re-engineering, No new functionality is added to the system but it is restructured and reorganized to facilitate future changes

Read More

UGC NET JULY 2018 (Computer Science And Applications Paper-II) (Question 17)

UGC NET JULY 2018 (Computer Science And Applications Paper-II) (Question 16)

 

Q17. A software design pattern often used to restrict access to an object is ___________ .

(1) Adapter
(2) Decorator
(3) Delegation
(4) Proxy
 
Answer :  (4) Proxy

Reason :

In software engineering, a design pattern is a general repeatable solution to a commonly occurring problem in software design. A design pattern isn't a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations.
Design patterns can speed up the development process by providing tested, proven development paradigms. Effective software design requires considering issues that may not become visible until later in the implementation. Reusing design patterns helps to prevent subtle issues that can cause major problems and improves code readability for coders and architects familiar with the patterns.

These design patterns are all about Class and Object composition. Structural class-creation patterns use inheritance to compose interfaces. Structural object-patterns define ways to compose objects to obtain new functionality.

• Adapter
  Match interfaces of different classes
• Bridge
  Separates an object’s interface from its implementation
• Composite
  A tree structure of simple and composite objects
• Decorator
  Add responsibilities to objects dynamically
• Facade
  A single class that represents an entire subsystem
• Flyweight
  A fine-grained instance used for efficient sharing 
• Private Class Data
  Restricts accessor/mutator access
• Proxy
  An object representing another object 

A Proxy can also be defined as a surrogate. In the real work a cheque or credit card is a proxy for what is in our bank account.  It can be used in place of cash, which is what is needed, and provides a means of accessing that cash when required. And that's exactly what the Proxy pattern does - controls and manage access to the object they are "protecting".

Read More

UGC NET JULY 2018 (Computer Science And Applications Paper-II) (Question 16)

UGC NET JULY 2018 (Computer Science And Applications Paper-II) (Question 16)

Q16. Coupling is a measure of the strength of the interconnections between software modules. Which of the following are correct statements with respect to modules coupling ?

P : Common coupling occurs when one module controls the flow of another module by passing its information on what to do.

Q: In data coupling the complete data structure is passed from one module to another through parameters.

R: Stamp coupling occurs when modules share a composite data structure and use only part of it.

Code:

(1)  P and Q only                                                                  (2)  P and R only
(3)  Q and R only                                                                  (4)  All P, Q and R only

Answer : (3)  Q and R only 

Reason:

Coupling can be applied to many things such as methods (in object oriented design), systems (in systems engineering) and modules (in any kind of organized system including software systems). Coupling is defined as the extent to which a system, subsystem, method or module connects with (depends on) others. In other words, it measures interdependency. It can be measured for a single module or other entity (the extent to which the module/entity can function or be understood without the use of other modules/entities). 

Types of Coupling

Various authors have described systems for identifying types of coupling. One of the most widely used for software and systems is Myers’ classification, which defines seven levels of coupling, from tightest to loosest:

• Content coupling - modules rely on each others’ internal data or internal organization
• Common coupling - modules share the same global data
• External coupling - modules share an externally imposed data format, communication protocol or device interface
• Control coupling - one module controls the flow of another, such as by passing it a flag or other information
• Stamp coupling - modules share a composite data structure but use different parts of it
• Data coupling - modules share data through parameters, such as in a subroutine call
• Message coupling - modules communicate by passing messages

Read More

UGC NET JULY 2018 (Computer Science And Applications Paper-II) (Question 15)

UGC NET JULY 2018 (Computer Science And Applications Paper-II) (Question 15)

Q15. Match the 5 CMM Maturity levels/CMMI staged representations in List-I with their characterizations in List-II :

List-I	List-II
(a)  Initial	(i)  Processes are improved quantitatively and continually.
(b)  Repeatable	(ii)  The plan for project comes from a template for plans.
(c)  Defined	(iii) The plan uses processes that can be measured quantitatively.
(d)  Managed	(iv)  There may not exist a plan or it may be abandoned.
(e)  Optimizing	(v)  There's a plan and people stick to it.

Code:

	(a)	(b)	(c)	(d)	(e)
(1)	(iv)	(v)	(i)	(iii)	(ii)

(2)

(i)

(ii)

(iv)

(v)

(iii)

(3)

(v)

(iv)

(ii)

(iii)

(i)

(4)

(iv)

(v)

(ii)

(iii)

(i)

Answer:  (3)

(v)

(iv)

(ii)

(iii)

(i)

Read More

UGC NET JULY 2018 (Computer Science And Applications Paper-II) (Question 14)

UGC NET JULY 2018 (Computer Science And Applications Paper-II) (Question 14)

Q14. A software system crashed 20 times in the year 2017 and for each crash, it took 2 minutes to restart. Approximately, what was the software availability in that year ?

(1).  96.9924%                                                          (2).  97.9924%
(3).  98.9924%                                                          (4).  99.9924%

Answer : (4).  99.9924%

Reason :  We are given with Mean Time To Repair (MTTR) is a basic measure of the maintainability of repairable items. It represents the average time required to repair a failed component or device.
i.e.  MTTR = 2 mins (2 mins to restart after crash)


Mean time between failures (MTBF) is the predicted elapsed time between inherent failures of a mechanical or electronic system, during normal system operation. MTBF can be calculated as the arithmetic mean (average) time between failures of a system.

MTBF  =               Total Running Time in Year                          =        365 x 24 x 60    
                   Number of Times System Crash in a Year                                  20

MTFB  =  26230

Now we need to find Availability of Software in a Year =              MTBF             =         26230      
                                                                                                  MTBF + MTTR               26230 + 2 
                                                                                        
                                                                                         =  0.9999239  =  0.9999239 x 100 %

                                                                                         =  99.99234 %

Read More

UGC NET JULY 2018 (Computer Science And Applications Paper-II) (Question 12)

UGC NET JULY 2018 (Computer Science And Applications Paper-II) (Question 12)

Q12. Match the following in Software Engineering :

List-I	List-II
(a)  Product Complexity	(i)  Software Requirement Definition
(b)  Structure System Analysis	(ii)  Software Design
(c)   Coupling and Cohesion	(iii) Validation Technique
(d)   Symbolic Execution	(iv)  Software Cost Estimation

Code:

	(a)	(b)	(c)	(d)
(1)	(ii)	(iii)	(iv)	(i)

(2)

(iii)

(i)

(iv)

(ii)

(3)

(iv)

(i)

(ii)

(iii)

(4)

(iii)

(iv)

(i)

(ii)

Answer :

(2)

(iii)

(i)

(iv)

(ii)

Reason : 

Read More