Bug severity is assessed by using the summary description of a reported bug.. A large number of summary information is available of bugs for any open source project.
In my opinion summary of particular "bug/error" in source code alone cannot be considered as "big data". But in case you will combine your idea with stackoverflow/quora comments, commits on github/bitbucket, and may be also "static code analizers" together with language specific linters (https://en.wikipedia.org/wiki/Lint_(software)) you may try to call it "big data" to some extent.
One of the main properties of Big Data analysis is that the process typically deals with unstructured data, which is the case of your project. Taking into consideration that you have a large number of bug reports, I think it might be considered Big Data.
Thanks to both experts...Very true thatswhy I was thinking...it is unstructured hetrogeneous it has velocity may be not have that amount of volume....Big data technologies can be used to solve the contemprary problems of SE arises due to OSS movement.....
Hi!
Let's take for discussion only two of the Big Data V's
see details here http://www.ibmbigdatahub.com/infographic/four-vs-big-data
volume - How many records do you have?
velocity - at which rate (speed) your data is acquired?
I would say at least a few millions records, each record consisting of a few attributes at least. How many do you have?
i have around fifty thousand records...for classification if we apply neural net it takes more thantwo days for results....big data technologies can help..i think so...
I think you don't have enough Vs!
You can use another name for your data, like huge data or something like that. ..
- Badges
- Science topic
- Similar topics
- Mathematics
- Statistics
- Statistical Analysis
- Data Analysis
- Dataset
- Big Data