DETECTING ITEMS HIDDEN INSIDE A BODY | J4R Journal

ISSN (online): 2395 - 7549 | High Impact Factor : 3.654

Author(s):

1. Sanjay Nag, University of Calcutta
2. Prof. Samir Kumar Bandyopadhyay, University of Calcutta
3. Nabanita Basu, University of Calcutta

Keywords:Concealed Weapon Detection, Color image, and IR image

Abstract:

People sometimes hide contraband inside body cavities. For instance, prison inmates and visitors may hide money or cell phones this way. Smugglers may carry drugs, and terrorists may conceal explosives inside the body. The paper proposed a method for detecting hidden item inside human body. It can detect both metal and non-metal objects and display them as images on a video screen.

Preview Article

Other Details:

Manuscript Id : J4RV1I12002
Published in         : Volume : 1, Issue : 12
Publication Date : 01/03/2016
Page(s)                 : 1-6

Download Article

For any Queries, contact us at : editor.j4r@gmail.com
                                        Mobile: 08735049634
Like us: www.facebook.com/Journal4Research
Submit Paper Online : http://journal4research.org/index.php?p=Submit
Visit us on www.journal4research.org

Journal 4 Research :: J4R | High Impact Factor 3.654 (2015)

Good News For All Research Scholar..

‪#‎Journal4Research‬ Got Impact Factor For year 2015

High Impact Factor Journal : 3.654

Submit Paper : http://journal4research.org/index.php?p=Submit
Like us: www.facebook.com/Journal4Research
Visit us www.journal4research.org

J4R Impact Factor

Journal 4 Research (J4R) | Call for Papers 2016

Journal 4 Research (J4R) is an Online Open Access Peer Reviewed Indexed Journal. It is an internationally refereed journal that is dedicated to the publishing of the latest advancements in engineering research.

The Scholars from all relevant academic fields are invited to submit high-quality manuscripts that describe the latest, state-of-the-art research results or innovations.

ISSN (online): 2395 - 7549
Leading E-Journal of INDIA
Useful website for Engineering (M.tech,B.E/M.E/Ph.D) Students....
VOLUME - 1 ISSUE - 11 (January 2016)
Paper Publication Charges : 1050 INR
We published as monthly journal with 12 issues per year.
Indexed in : Academia,ISSUU,Google Scholar,
Scridb, Slideshareand many more
For any Queries, contact us at : editor.j4r@gmail.com
Mobile: 08735049634
Like us: www.facebook.com/Journal4Research
Visit us on www.journal4research.org

Journal 4 Research | J4R | VOLUME - 1, ISSUE - 11

Journal 4 Research | J4R | VOLUME - 1, ISSUE - 11 

DETERMINING THE INFLUENCE OF CUTTING FLUID ON SURFACE ROUGHNESS DURING MACHINING OF EN24 AND EN8 STEEL BY USING CNC MILLING MACHINE

Author(s):

1. N.Gopikrishna, SR Engineering College; M.Shiva Chander, SR Engineering College
2. M.Srikiran, Jayamukhi Institute of Technology & Sciences

Keywords:

Cutting Fluid, Machining Parameters, Tool, Work Specimen, Surface Roughness

Abstract:

Evaluation of the performance of cutting fluid in machining different work materials in order to improve the efficiency of any machining process. The efficiency can be evaluated based on certain process parameters such as flank wear, surface roughness on the work piece, cutting force developed, temperature developed at the tool-chip interface, etc. The main aim of the project is to determine the influence of cutting fluids in metal working. Servo 68 is mainly used for investigation based on surface roughness during milling of EN24 and EN8 steel with carbide tool. Three square pieces of EN 24 material and three round pieces of EN8 material are taken for machining. Different cutting parameters are considered for feed rate, speed and depth of cut. the six pieces are machined with different parameters and surface roughness values are investigated experimentally.

Preview Article

Other Details:

Manuscript Id :         J4RV1I11001

Published in :         Volume : 1, Issue : 11

Publication Date : 01/02/2016

Page(s)       :                 1-4

                                                   Download Article

Task Scheduling using Amalgamation of Metaheuristics Swarm Optimization Algorithm and Cuckoo Search in Cloud Computing Environment

TASK SCHEDULING USING AMALGAMATION OF MET HEURISTICS SWARM OPTIMIZATION ALGORITHM AND CUCKOO SEARCH IN CLOUD COMPUTING ENVIRONMENT

Author(s):P.Durgadevi , R.M.K College of Engineering and Technology; Dr.S.Srinivasan, R.M.D Engineering College 

Keywords:Virtualization, Quality of service, Task scheduling, Swarm Optimisation , Metaheuristics 

Abstract:Cloud Computing is the latest networking technology and also popular archetype for hosting the application and delivering of services over the network. The foremost technology of the cloud computing is virtualization which enables of building the applications, dynamically sharing of resources and providing diverse services to the cloud users. With virtualization, a service provider can guarantee Quality of Service to the user at the same time as achieving higher server consumption and energy competence. One of the most important challenges in the cloud computing environment is the VM placemnt and task scheduling problem. This paper focus on Metaheuristic Swarm Optimisation Algorithms(MSOA) deals with the problem of VM placement and Task scheduling in cloud environment. The MSOA is a simple parallel algorithm that can be applied in different ways to resolve the task scheduling problems. The proposed algorithm is considered an amalgamation of the SO algorithm and the Cuckoo search (CS) algorithm; called MSOACS. The proposed algorithm is evaluated using Cloudsim Simulator. The results proves the reduction of the makespan and increase the utilization ratio of the proposed MSOACS algorithm compared with SOA algorithms and Randomised Allocation Allocation (RA).

Introduction:

Clusters [1] are distributed systems under the supervision of single administrative domain. Grid [1] is a geographically dispersed collection of distributed systems. Cloud is a collection of parallel and distributed system where the nodes are virtualized whereby a single physical server can run multiple virtual servers, thus reducing the resources as well as the cost.

A cloud can be public, private or hybrid [2]. Private clouds are setup by enterprises for their internal use only. Public clouds are setup for public use by the enterprises. The users of a public cloud must agree to the Service Level Agreement (SLA) specified by the cloud provider. Hybrid cloud is a combination of private and public cloud. OpenStack is one the most popular software used to setup a cloud, others being Eucalyptus, OpenNebula, etc.

For full length Article Click Here

Effective Test Case Design: A Review#journal4research

Effective Test Case Design: A Review

Abstract: This paper describes the different techniques of testing the software. This paper explicitly addresses the idea for testability and the important thing is that the testing itself-not just by saying that testability is a desirable goal, but by showing how to do it. Software testing is the process we used to measure the quality of developed software. Software Testing is not just about error finding and their solution but also about checking the client requirements and testing that those requirements are met by the software solution. It is the most important functional phase in the Software Development Life Cycle(SDLC) as it exhibits all mistakes, flaws and errors in the developed software. Without finding these errors, technically termed as ‘bugs,’ software development is not considered to be complete. Hence, software testing becomes an important parameter for assuring quality of the software product. We discuss here about when to start and when to stop the testing of software. How errors or Bugs are formed and rectified. How software testing is done i.e. with the help of Team Work.

Keywords: SDLC, Concepts for Application Test Management, ISO 9126

 I.    INTRODUCTION

Testing is a process used to identify the correctness, completeness and quality of developed computer software. With in mind that , testing can never completely establish the correctness of Computer software . There are many approaches for software testing, but effective testing on complex products is essentially a process of investigation, not merely a matter of creating and following rote procedure. The definition of testing is "the process of questioning a product in order to evaluate it", where the

"questions" are things the checker tries to do with the product, and the product answers with its behaviour in reaction to the probing of the tester. Although most of the intellectual processes of testing are nearly identical to that of review or inspection, the word testing is not to mean the dynamic analysis of the product—putting the product through its paces. The quality of the application can and normally does vary widely from system to system but some of the common quality attributes include reliability, stability, portability, maintainability and usability. Testing helps is verifying and validating if the Software is working as it is intended to be working. Things involve using Static and Dynamic methodologies to Test the application. Because of the fallibility of its human designers and its own abstract, complex nature, software development must be accompanied by quality assurance activities. It is not unusual for developers to spend 40% of the total project time on testing. For life-critical software (e.g. flight control, reactor monitoring), testing can cost 3 to 5 times as much as all other activities combined. The destructive nature of testing requires that the developer discard preconceived notions of the correctness of his/her developed software. The importance of software testing and its impact on software cannot be underestimated. Software testing is a fundamental component of software quality assurance and represents a review of specification, design and coding.

A. Software Testing Fundamentals:

Testing is the one step in the software process that can be seen by the developer as destructive instead of constructive. Software engineers are typically constructive people and testing requires them to overcome the concepts of correctness and deal with conflicts when errors are identified.

B. Testing Objectives Include:

1) It is a process to finding the intent of Error .
2) A test case is called to be a good when it discovered the undiscovered error.
3) A test is successful when all errors are uncovers an as yet undiscovered error.
Testing should systematically uncover different classes of errors in a minimum amount of time and with a minimum amount of effort. One more benefit of testing is that it demonstrates that the software appears to be working as stated in the specifications. The data collected through testing can also provide an indication of the software's reliability and quality. But, testing cannot show the absence of defect . it can only show that software defects are present.

C. When Testing should be started?

Early Testing in life cycle can reduce the error . Test cases are associated with every phase of development. The goal of Software Tester is to find bugs, find them as early as possible, and make them sure they are fixed.The number one cause of Software bugs is the Specification. There are several reasons specifications are the largest bug producer.


In many point or instance the specification isn’t written. Other reasons may be that the spec isn’t thorough enough, it’s constantly changing, or it’s not communicated well to the entire team. Planning software is vitally important. If it’s not done correctly bugs will be created. The next largest source of bugs is the Design, That’s where the programmers lay the plan for their Software. Compare it to an architect creating the blue print for the building, Bugs occur here for the same reason they occur in the specification. It’s rushed, changed, or not well communicated. Coding errors may be more familiar to you if you are a programmer. Typically these can be traced to the Software complexity, poor documentation, schedule pressure or just plain dump mistakes. It’s important to note that many bugs that appear on the surface to be programming errors can really be traced to specification. The other category is the catch-all for what is left. Some bugs can blamed for false positives, conditions that were thought to be bugs but really weren’t. There may be duplicate bugs, multiple ones that resulted from the square root cause. Some bugs can be traced to Testing errors.

For More Information Click Here

Call for Papers: J4R (Journal for Research)

Call for Papers: J4R (Journal for Research)

ISSN (online): 2395 - 7549

Leading E-Journal of INDIA

Useful website for Engineering (M.tech,B.E/M.E/Ph.D) Students....

Paper Publication Charges : 1050 INR

Like us: www.facebook.com/Journal4Research

Visit us on www.journal4research.org