Sunday, December 30, 2018

NetBean as a Open Source

NetBeans is Open Source


The NetBeans project is an open source project. What this means is:
  • The NetBeans Platform and IDE are free for commercial and non- commercial use.
  • The source code to both are available to anyone to reuse as they see fit under the terms of the license.
  • Development of the Platform and IDE happen in public. Decisions are made on public mailing lists, by consensus.
  • Individuals or companies may contribute code to the project; participation is open to anyone.
With the exception of content that explicitly specifies the license under which it is made available, the software and other content on this site is licensed under the Common Development and Distribution License, which complies with the Open Source Definition. Any third-party binaries included in /external/ directories in the source tree, are licensed under their own terms and conditions.

Why Open Source?


There are many reasons to choose the open source approach to creating software. This approach can be variably described as:
  • A set of best practices for geographically distributed software development.
  • A way of making sure software meets the needs of its users by ensuring those users can participate in its creation.
  • A way of ensuring that users of software are able to modify it to meet their needs, and that no single entity can act against the interests of the project or the community.
  • A way to create software that helps to ensure high quality by peer review and social dynamics (the "many eyeballs" concept).
  • A way to create software that avoids the hierarchy and organizational politics than can make some commercial development efforts less efficient.
There are many more possible descriptions, ranging from the practical to the religious. The more important question is, does it work? Since 1998, with participation from thousands of individuals and hundreds of companies (some of which have built their business on the software created here), we believe that the answer is an unqualified "yes." But the best way to test this answer is to get involved in the NetBeans community and discover the benefits for yourself.

Thursday, December 13, 2018

An Introduction to NetBeans

Most developers recognize the NetBeans IDE as the original free Java IDE. It is that, and much more! The NetBeans IDE provides support for several languages (PHP, JavaFX, C/C++, JavaScript, etc.) and frameworks. 
NetBeans is an open-source project dedicated to providing rock solid software development products (the NetBeans IDE and the NetBeans Platform) that address the needs of developers, users and the businesses who rely on NetBeans as a basis for their products; particularly, to enable them to develop these products quickly, efficiently and easily by leveraging the strengths of the Java platform and other relevant industry standards.
In June 2000, NetBeans was made open source by Sun Microsystems, which remained the project sponsor until January 2010 when Sun Microsystems became a subsidiary of Oracle. Please see our History section for more information.
The two base products, the NetBeans IDE and NetBeans Platform, are free for commercial and non-commercial use. The source code to both is available to anyone to reuse as they see fit, within the terms of use. The legal section contains information regarding licensing, copyright issues, privacy policy and terms of use.
The NetBeans project is also a vibrant community in which people from across the globe can ask questions, give advice, contribute and ultimately share in the success of our products. On the NetBeans mailing lists and forums, you will find posts from students, developers from top companies, and individuals looking to expand their skills.

A Brief History of NetBeans

NetBeans started as a student project (originally called Xelfi) in Czechoslovakia, now the Czech Republic, in 1996. The goal was to write a Delphi-like Java IDE (Integrated Development Environment) in Java. Xelfi was the first Java IDE written in Java, with its first pre-releases in 1997. Xelfi was a fun project to work on, especially since the Java IDE space was uncharted territory at that time.
The project attracted enough interest that the students, once they graduated, decided that they could market it as a commercial product. Soliciting resources from friends and relatives for a website, they formed a company around it.
Soon after, they were contacted by Roman Stanek, an entrepreneur who had already been involved in several startups. He was looking for a good idea to invest in, and discovered Xelfi. He met with the founders; they hit it off, and a business was born. The original business plan was to develop network-enabled JavaBeans components. Jaroslav Tulach, who designed the IDE's basic architecture, came up with the name NetBeans to describe what the components would do. The IDE would be the way to deliver them. When the specification for Enterprise Java Beans came out, it made more sense to work with the standard for such components than to compete with it--but the name stuck.
In the spring of 1999, NetBeans DeveloperX2 was released, supporting Swing. The performance improvements that came in JDK 1.3, released in the fall of 1999, made NetBeans a viable choice for development tools. By the summer of 1999, the team was hard at work re-architecting DeveloperX2 into the more modular NetBeans that forms the basis of the software today.

Tuesday, December 4, 2018

EC05 Application continue


Section 05

Integration Testing:
Index Number: 3405, 3419, 3428

Interface Name
Activity Selection Wizard
Test Data
The calibration window fetching request and response.
Target
Paint Wizard
Assumptions/ Conditions/ Limitations
·         For each level, first activity within, is accessible by default.
·         Activity number 2 of each level will be granted for access, if only first activity within it is completed with a result of more than predefined pass level.

Index Number: 3419, 3428

Interface Name
Login and registration form
Test Data
User details(username, password, name, age, date of birth)
Target
Level Selection Form
Assumptions/ Conditions/ Limitations
·         Valid login data should be provided (username and password)
·         No any field should be submitted without valid data.
·         Valid data with specified format should be submitted in registration.
·         No any repeated usernames will be allowed for a new registration session.

Index Number: 3419, 3271

Interface Name
Level Selection Form
Test Data
Previous activity with its completion status and results obtained.
Target
Activity Selection Form
Assumptions/ Conditions/ Limitations
Activity number two of any level will be made accessible only, if user completed the activity number two (since activity number 1 is accessible by default) with required level of success.

Index Number: 3420, 3428

Interface Name
User Results Generation Wizard
Test Data
User coordinates set (drawn output) and standard data stored.
Target
User Results Wizard
Assumptions/ Conditions/ Limitations
After generating results, and checking the level of success, the status “COMPLETED” will be sent to the field, activitystatus in the useractivity table.
The final result will be also sent to the same table under activityresults.

Index Number: 3405, 3420

Interface Name
Paint Wizard
Test Data
User coordinate set (drawn output)
Target
User Results Wizard
Assumptions/ Conditions/ Limitations
The identified coordinate data will be only considered for highlighted points.
Average result will be calculated using pointwise results. (taken as a percentage)
  
Section 05

Data Management:

iv.                Data retrieval queries:


Ø    SELECT * FROM user
WHERE username=? AND passwordl=?;
Ø    SELECT * FROM useractivity
WHERE activitystatus='Completed';

v.                  Data manipulation queries: 


Ø  INSERT INTO user (username, passwordl)
Ø  VALUES (‘ “ +user+ ”’, ‘“ +pass+ ”’)








Other queries

Ø  CREATE DATABASE virtualdb;

Ø  CREATE TABLE table_user (
   userid integer,
   username varchar,
   passwordl varchar,
   Date_of_birth date
   PRIMARY KEY (userid),
   );

Ø  CREATE TABLE table_useractivity (
   userid integer,
   activityid integer,
   activitystatus varchar,
   activityresult float
   PRIMARY KEY (useractivityid),
   
FOREIGN KEY (activityid) REFERENCES activity (activityid)
   FOREIGN KEY (userid) REFERENCES user (userid)
 );

ØCREATE TABLE table_activity (
   activityid integer,
   activityname varchar,
   description text,
         activitylevel integer
         PRIMARY KEY (activityid),
         );

EC05 Application continue


Section 04

Experimental Setup and Validation Methods on Software/ Research Design/ Hardware Design:


Experimental Setup and Validation Methods on Software Component

Index Number: 3405

Experiment Number
01
Target Experiment
Port identification for Bluetooth connection of glove with the user system
Component/ Module Name
Serial Port communication of the glove
Data collection/ Data Set preparation
List of serial ports with their system’s available port index, taken from the console output.
Method
Change the serial ports index as 1 and 0 and check each port’s indication COM port, then trying out each at a time whether it is working.
Measurement/ Equations used to make the conclusion.
·         Commonly, serial list index (0) is COM6 while serial list index (1) is COM7.
Results
           Error in Bluetooth connection when use 0(COM6)
           Successful in Bluetooth connection when use 1(COM7)
  
Index No: 3405

Experiment Number
02
Target Experiment
Least response time consuming placement of the tracking object.
Component/ Module Name
Tracking object
Data collection/ Data Set preparation/
·         Reaction time taken by the system when the tracking object is placed on the palm of the glove.
·         Reaction time taken by the system when tracking object is placed near the thumb.
Method
Different five people try the two scenarios and take the response times separately. Then the average time of both above responding scenarios, will be calculated.
Measurement/ Equations used to make the conclusion.
Checking what scenario takes more time in responding and what takes less time. The less time taking will be taken.

Results
·         Shorter response time.
·         Contradictory longer response time rather the above. (amount)

Index No: 3271

Experiment Number
03
Target Experiment
Checking the system reads the user input coordinates(x, y) within the paint function only.
Component/ Module Name
Real time user coordinates tracker.
Data collection/ Data Set preparation/
Console data for coordinates displayed only within paint function.
Method
Reading the coordinates of the pointer that is calibrated earlier and make sure that reading is only started when user starts drawing and ends when user stops drawing.
Measurement/ Equations used to make the conclusion.
Console starts displaying x, y data of pointer when user is within paint canvas and starts drawing on top of it.

It ends displaying, only when user stops drawing.
Results
·         The console is displaying x, y coordinates of the pointer, only within the paint canvas and when only user starts drawing and it is done until user stops drawing on the paint canvas.

Index Number: 3428 
Experiment Number
04
Target Experiment
Ensuring the connectivity status of database to the system
Component/ Module Name
Database Connectivity test class
Data collection/ Data Set preparation/
·         Console debug output message for the test class.
Method
Implementing all the above mentioned data set providing methods and finding the best that meets the requirement.
Measurement/ Equations used to make the conclusion.
·         If the database is connected, displays the message “MySQL JDBC Driver Registered!”
·         If the table data accessibility granted, “You made it, take control your database now!"
·         Otherwise,” "Where is your MySQL JDBC Driver?" and "Failed to make connection!"
Results
·         Just provides the internal information related with MySQL platform only.
·         Just provides that the connectivity status and information related of the MySQL database with the main developing platform (where the application is built on).
·         Provides the connectivity status of the MySQL database with the application which is developed, class wise.

Index Number: 3419

Experiment Number
05
Target Experiment
Ensuring the interface classes, its functions and their connectivity function properly
Component/ Module Name
Test classes for form interfaces
Data collection/ Data Set preparation/
·         The interface class console output after execution.
Method
Submit each and every form and check by executing test class, whether all the included data items and their methods worked or not as they are supposed to be.
Measurement/ Equations used to make the conclusion.
If performed well, then “All went successfully!”, if not “Something is wrong, check this…..”
Results
·         Message delivered in output console.

Experimental Setup and Validation Methods on Research Design

Index Number: 3405, 3419, 3420, 3428, 3271

Experiment Number
01
Target Experiment
To ensure that their skills are up to the standard that they are expected to be, if not what are the reasons, what are the suggestions for those problems and identifying how important the kindergarten education being laid within a strong and organized basis for the advance
Component/ Module Name
Research design for entire system
Data collection/ Data Set preparation/
Instructors’ feedbacks and shared child thoughts via an organized feedback form (questionnaire) provided and identifying special cases within each and every section. (using data tables and bar charts)
Method
Conducting a survey in Sri Lankan schools with their primary section (Grade 1-5) for different geographical areas.
Measurement/ Equations used to make the conclusion.
The ratio between the average number of children having defects in expected completion of skills and average number of children in a grade. (Grade 1-5)
Results
·         Qualitative and quantitative analysis on the drawbacks of kindergarten education.

Index Number: 3420

Experiment Number
01
Target Experiment
Measure the user performance
Component/ Module Name
User-Measuring Tool
Data collection/ Data Set preparation/
Referencing, predefined coordinate ranges for x and y, for each highlighted point in paint canvas and coordinates of the same identical points.
Method
Draw a sketch along a guided canvas (specially focusing on highlighted points) and proceed for measuring the performance as a percentage using predefined scenario.
Measurement/ Equations used to make the conclusion.
 Pixel coordinates read by the glove to the tool for a certain highlighted point should be around that exact value with a given gap of pixels distance.
Results
·         Coordinates for first point
·         Coordinates for second point…. likewise, up to the predefined number of measuring points.
·         At last, the average result for the whole activity.


Experimental Setup and Validation Methods on Hardware Design:

Index Number: 3405

Experiment Number
01
Target Experiment
Virtual functioning of the glove
Component/ Module Name
Hand Glove with Bluetooth connectivity
Data collection/ Data Set preparation/
·         The maximum time that the glove can read the user output, on top of the paint canvas.
Method
Without breaking the switch interconnection made of two fingers, it has to continuously draw on top of the canvas until it is done. Check the time required taken. Done this with different five people and get their own time slot counted, and then takes the average of it.
Measurement/ Equations used to make the conclusion.
It should be minimally, less than or equal to 60 seconds.
Results
Average maximum time the glove can continuously perform for.


Experimental Setup and Validation Methods on Software, Hardware and Research Design


Experiment Number
01
Target Experiment
Getting user variable feedbacks organized within questionnaire
Component/ Module Name
Whole integrated system
Data collection/ Data Set preparation/
·         Feedback questionnaire results taken and analyzed final rating on whole system.
Method
Twenty different children of age category 3-5 years will be given to test the system with the performance along with their parental and the group members’’ guidance. Then they are provided with questionnaire asking their opinions on each. Then average rating distribution will be calculated.
Measurement/ Equations used to make the conclusion.
6-10 out of 10 = Good
4-5 out of ten = Average
0-3 out of ten = Low
Results
Average rating distribution


How our entire system works