Review is "A process or meeting during which artifacts of software product are examined by project stockholders, user representatives, or other interested parties for feedback or approval”. Software Review can be on Technical specifications, designs, source code, user documentation, support and maintenance documentation, test plans, test specifications, standards, and any other type of specific to work product, it can be conducted at any stage of the software development life cycle.

Purpose of conducting review is to minimize the defect ratio as early as possible in Software Development life cycle. As a general principle, the earlier a document is reviewed, the greater will be the impact of its defects on any downstream activities and their work products. Magnitude cost of defect fixing after the release of the product is around 60-100x. Review can be formal or informal. Informal reviews are referred as walkthrough and formal as Inspection.

Walkthrough: Method of conducting informal group/individual review is called walkthrough, in which a designer or programmer leads members of the development team and other interested parties through a software product, and the participants ask questions and make comments about possible errors, violation of development standards, and other problems or may suggest improvement on the article, walkthrough can be pre planned or can be conducted at need basis and generally people working on the work product are involved in the walkthrough process.The Purpose of walkthrough is to:· Find problems· Discuss alternative solutions· Focusing on demonstrating how work product meets all requirements.IEEE 1028 recommends three specialist roles in a walkthrough:Leader: who conducts the walkthrough, handles administrative tasks, and ensures orderly conduct (and who is often the Author)Recorder: who notes all anomalies (potential defects), decisions, and action items identified during the walkthrough meeting, normally generate minutes of meeting at the end of walkthrough session.Author: who presents the software product in step-by-step manner at the walk-through meeting, and is probably responsible for completing most action items.

Walkthrough Process: Author describes the artifact to be reviewed to reviewers during the meeting. Reviewers present comments, possible defects, and improvement suggestions to the author. Recorder records all defect, suggestion during walkthrough meeting. Based on reviewer comments, author performs any necessary rework of the work product if required. Recorder prepares minutes of meeting and sends the relevant stakeholders and leader is normally to monitor overall walkthrough meeting activities as per the defined company process or responsibilities for conducting the reviews, generally performs monitoring activities, commitment against action items etc.

Inspection: An inspection is a formal, rigorous, in-depth group review designed to identify problems as close to their point of origin as possible., Inspection is a recognized industry best practice to improve the quality of a product and to improve productivity, Inspections is a formal review and generally need is predefined at the start of the product planning, The objectives of the inspection process are to· Find problems at the earliest possible point in the software development process· Verify that the work product meets its requirement· Ensure that work product has been presented according to predefined standards· Provide data on product quality and process effectiveness· Inspection advantages are to build technical knowledge and skill among team members by reviewing the output of other people· Increase the effectiveness of software testing. IEEE 1028 recommends three following roles in an Inspection:Inspector Leader: The inspection leader shall be responsible for administrative tasks pertaining to the inspection, shall be responsible for planning and preparation, shall ensure that the inspection is conducted in an orderly manner and meets its objectives, should be responsible for collecting inspection dataRecorder: The recorder should record inspection data required for process analysis. The inspection leader may be the recorder.Reader: The reader shall lead the inspection team through the software product in a comprehensive and logical fashion, interpreting sections of the work product and highlighting important aspectsAuthor: The author shall be responsible for the software product meeting its inspection entry criteria, for contributing to the inspection based on special understanding of the software product, and for performing any rework required to make the software product meet its inspection exit criteria.Inspector: Inspectors shall identify and describe anomalies in the software product. Inspectors shall be chosen to represent different viewpoints at the meeting (for example, sponsor, requirements, design, code, safety, test, independent test, project management, quality management, and hardware engineering). Only those viewpoints pertinent to the inspection of the product should be present. Some inspectors should be assigned specific review topics to ensure effective coverage. For example, one inspector may focus on conformance with a specific standard or standards, another on syntax, and another for overall coherence. These roles should be assigned by the inspection leader when planning the inspection.All participants in the review are inspectors. The author shall not act as inspection leader and should not act as reader or recorder. Other roles may be shared among the team members. Individual participants may act in more than one role. Individuals holding management positions over any member of the inspection team shall not participate in the inspectionInspection Process: Following are review phases:· Planning· Overview· Preparation· Examination meetingPlanning:· Inspection Leader perform following task in planning phase· Determine which work products need to be inspected· Determine if a work product that needs to be inspected is ready to be inspected· Identify the inspection team· Determine if an overview meeting is needed. The moderator ensures that all inspection team members have had inspection process training. The moderator obtains a commitment from each team member to participate. This commitment means the person agrees to spend the time required to perform his or her assigned role on the team. Identify the review materials required for the inspection, and distribute materials to relevant stake holdersOverview: Purpose of the overview meeting is to educate inspectors; meeting is lead by Inspector lead and is presented by author, overview is presented for the inspection, this meeting normally acts as optional meeting, purpose to sync the entire participant and the area to be inspected.Preparation: Objective of the preparation phase is to prepare for the inspection meeting by critically reviewing the review materials and the work product, participant drill down on the document distributed by the lead inspector and identify the defect before the meetingExamination meeting: The objective of the inspection meeting is to identify final defect list in the work product being inspected, based on the initial list of defects prepared by the inspectors [identified at preparation phase and the new one found during the inspection meeting. The Lead Auditor opens the meeting and describes the review objectives and area to be inspected. Identify that all participants are well familiar with the content material, Reader reads the meeting material and inspector finds out any inconsistence, possible defects, and improvement suggestions to the author. Recorder records all the discussion during the inspection meeting, and mark actions against the relevant stake holders. Lead Inspector may take decision that if there is need of follow up meeting. Author updates the relevant document if required on the basis of the inspection meeting discussionRework and Follow-up: Objective is to ensure that corrective action has been taken to correct problems found during an inspection.

Friday, 21 March 2014

Creates a new image window or stack. A dialog box allows you to
specify the image title, type, dimensions and initial content.

Name is the title that will be used for the Window. Type is the image type: 8-bit grayscale, 16-bit grayscale (unsigned), 32-bit (float) grayscale or RGB color. Fill With (White, Black or Ramp) specifies how the image is initialized. Width and Height specify the image dimensions in pixels. Set Slices to a value greater than one to create a stack.

Thursday, 13 March 2014

1. I assume you have these in DICOM format. In ImageJ it is simple to
import a single DICOM image and the calibration is done for you (the
DICOM header contains fields for slope and intercept (usually 1 and
-1024)). Since you have a stack this is probably not much good. For
importing tomographic studies I use the "Import Dicom sequence" plugin
available here: http://www.iftm.de/telemedizin/dcmimex.htm

From
what I remember it is not the most straight-forward plugin to install
but will nicely import a sequence of DICOM images as a stack. It does
not, however, seem to calibrate the gray levels into hounsfield units.
To do this choose Analyse->Calibrate. Choose "Straight line" as the
function, type -1024 in the left box and 0 in the right box. When you
press OK you get a straight-line graph of the calibration and a label
with straight line formula y = a + bx. a should be -1024 and b should be
1. If they are then we have a calibration to HU.

To demonstrate the HU calibration, move the cursor around the
image and observe the "value" in the IJ status bar. The value is in HU
and the gray level appears in brackets.

2. Images typically only contain 256 gray levels when displayed,
even though the image may contain values of any number (eg CT from
-1024 to ~32k). So gray levels have to be "binned" in an image, just
like in a histogram. So the column labelled "level" is the gray level
displayed in the image and the "bins" are demonstrated in the second
column. The size of the bin is dictated by the min and max pixel levels.

According to
Wikipedia,
the Hounsfield scale was invented in 1972 by Godfrey Newbold
Hounsfield. His scale is a quantitative measure of radiodensity and is
used to evaluate CAT scans. Pixels in an image obtained by CT scanning
are displayed in terms of relative radiodensity.

The pixel value is
displayed according to the mean attenuation of the tissue that it
corresponds to on a scale from -1024 to +3071 on the Hounsfield scale.
Water has an attenuation of 0 Hounsfield units (HU) while air is -1000
HU, bone is typically +400 HU or greater and metallic implants are
usually +1000 HU.

To convert from the normal units found in CT data (a typical data set ranges from 0 to 4000 or so) you have
to apply a linear transformation of the data. The equation is:

hu = pixel_value * slope + intercept

The real question is where do you find the slope and intercept used in the conversion?

Normally, these values are stored in the DICOM file itself.
The tags are generally called the Rescale Slope and Rescale Intercept, and typically
have values of 1 and -1024, respectively.

To show you how to obtain these values, I downloaded a sample CT data set, named CT-MONO2-16-ankle.dcm. This file was created on a GE
Medical Systems scanner. After unpacking the compressed file, and adding a dcm file extension to the name (a convenience), I opened the file and dumped the elements to the display.

Monday, 27 January 2014

Java programming language enum types
are much more powerful than their
counterparts in other languages. The
enum declaration defines a class
(called an enum type). The enum class
body can include methods and other
fields.

In order to see the actual size of each enum, let's make an actual enum and examine the contents of the class file it creates.

The disassembly shows that that each field of an enum is an instance of the Constantsenum class. (Further analysis with javap will reveal that each field is initialized by creating a new object by calling the new Constants(String) constructor in the static initialization block.)

Therefore, we can tell that each enum field that we create will be at least as much as the overhead of creating an object in the JVM.

Zip and Unzip are a very common activities for a computer user. A
user normally uses the zip utility to compress a directory to create a
zip file. There are many ready-made software such as winzip,7zip, and
winrar that are available to achieve this.

However, it is also possible
to protect the zip file with a password so that the end user has to
provide the password to unzip the zip file. This is the very common
scenario that can be achieved by a zip utility tool. The significant
part of my article is to provide you with the solution to achieve this
using a Java program. While developing the project you may encounter a
scenario in which you have to create a password-protected zip file that
can be unzipped by any zip tool like winzip. Let me provide a complete
scenario for your understanding.

In a system, some files are generated for a user and all the files
are zipped with a password. The generated password protected zip file is
sent to the user through email and the password for the zip file to
open is sent to the particular user as an SMS to the user's mobile.

Similarly the end-user creates a password protected zip file and uploads
to a online system with the user's password in a text field. In this
case we have to develop a system where the system will be able to create
a password protected zip file and should be able to extract all the
files from a password protected zip file. Let me show you how you can
achieve it.

Technicalities
However,
Java provides the feature of creating a zip file and also provides the
feature to unzip or decompress a zip file. But there is no default java
API to create a password protected zip file and also there is no default
java API to unzip a password protected zip file. To facilitate this
feature of zip utility some developers have developed java API in this
regard. We have to use their API to achieve this. We have to look into
the following aspects of zip utility.

Java-enabled system should be able to generate a password protected
zip file and that password protected zip file can be unzipped by any
zip utility like winzip and others

Java-enabled system should be able to decompress or unzip a password
protected zip file created by any zip utility like winzip and others.

The followings are the APIs you have to use for this objective:

1.To create a password protected zip file in java, you have to use
“winzipaes”. It is avilable in Google code. You can download the .jar
file and the source code from the following link.

This
API helps to add a password to a already created zip file. It means
that if you want to create a password protected zip file, first you have
to create a zip file and then you can add a password that zip file. It
is a pure java API works with any operating system. You have to download
the following jar file from the above URL.

passwordcompressor.jar

2.To unzip or decompress a password protected zip file, you have to
use “sevenzipjbind”. It is available in sourceforge.net site. You can
download the .jar files from the following link: http://sourceforge.net/projects/sevenzipjbind/files/.
This API helps to extract all the files and folders from password
protected zip file created by any zip utility tool. You have to download
the following .jar files from the above URL.

sevenzipjbinding-AllPlatforms.jarsevenzipjbinding.jar

3.For password protection, you have to use Bouncecastle cryptographic
API. You can download the .jar file from the following link.http://www.bouncycastle.org/
You have to download the following .jar files from the above URL.bcprov-jdk15-145.jar

After downloading all the .jar files, put all the .jar files in your
classpath. I have written a java program by using all these APIs to
achieve all the above mentioned functionalities.

DicomImageReadParam param1 = (DicomImageReadParam) readers.getDefaultReadParam();//return DicomImageReadParam // Adjust the values of Rows and Columns in it and add a Pixel Data attribute with the byte array from the DataBuffer of the scaled Raster

ImageInputStream iis = ImageIO.createImageInputStream(file);

readers.setInput(iis, false);//sets the input source to use the given ImageInputSteam or other Object

DicomImageReadParam param1= (DicomImageReadParam) readers.getDefaultReadParam();//return DicomImageReadParam // Adjust the values of Rows and Columns in it and add a Pixel Data attribute with the byte array from the DataBuffer of the scaled Raster

After searching for what seems like hours to find a simple solution to this problem...and yes I know that AffineTransform can do this, but I knew there was a lot simpler/faster solution and one that doesn’t require creating new Objects.

The trick is to cache the angle and distance of each point from the center point. After doing so, the points can be rotated and the center point can be moved.

Here is the code...the angles are adjusted to 360 degrees...due north is zero.