Medical data is very sensitive and vital in form of Electronic Health Record (EHR) for healthcare sector, storage of this data is one of an important challenge. Cloud is providing storage services with cost and energy efficiency, data over the cloud is secure but not much over the public cloud. EHR require more security and there is strict compliance of HIPAA and HL7 over the security of patient’s medical record. Sensitive EHR over the public cloud where the urgent verification is required is also great challenge. Different cryptography techniques are proposed to secure the data but there are much chances to compromise the keys. Our proposed technique for secure verification of data store locally with the use of blockchain technology that make information immutable and distributed, so that the medical record could be verify from different offices and authorities using blockchain technology. As a model we have taken an important hospital of the city (working under the Government of the Punjab, Health Department) where all medical examination record (MER) is maintained and Medical Fitness Certificate (MFC) issues to Govt. employee. We shall use Hyperledger Fabric to develop the Private/Consortium network of all Tertiary Care Hospital in the city, headed by Office of Secretary Specialized Healthcare and Medical Education (SSHC&ME). Hash of the medical fitness certificate store in Hyperledger Fabric (HLF) blockchain with report id, timestamp patient’s id, and digital signature of Medical Superintendent (MS). Blockchain digital ledger will distributed between high level authorities (offices of Secretaries’ Health, TCH). Office SSHC&ME work as admin of whole HLF network. For verification, verifier (user/Government department) get the hash of medical fitness report and verify it from HLF blockchain network using HLF SDK
{"title":"Blockchain Based System for the Verification and Safekeeping of Medical Examination Record of Government Employees","authors":"A. Tariq, Mudasir Qazi, Muhammad Burhan","doi":"10.56536/jicet.v1i2.14","DOIUrl":"https://doi.org/10.56536/jicet.v1i2.14","url":null,"abstract":"Medical data is very sensitive and vital in form of Electronic Health Record (EHR) for healthcare sector, storage of this data is one of an important challenge. Cloud is providing storage services with cost and energy efficiency, data over the cloud is secure but not much over the public cloud. EHR require more security and there is strict compliance of HIPAA and HL7 over the security of patient’s medical record. Sensitive EHR over the public cloud where the urgent verification is required is also great challenge. Different cryptography techniques are proposed to secure the data but there are much chances to compromise the keys. Our proposed technique for secure verification of data store locally with the use of blockchain technology that make information immutable and distributed, so that the medical record could be verify from different offices and authorities using blockchain technology. As a model we have taken an important hospital of the city (working under the Government of the Punjab, Health Department) where all medical examination record (MER) is maintained and Medical Fitness Certificate (MFC) issues to Govt. employee. We shall use Hyperledger Fabric to develop the Private/Consortium network of all Tertiary Care Hospital in the city, headed by Office of Secretary Specialized Healthcare and Medical Education (SSHC&ME). Hash of the medical fitness certificate store in Hyperledger Fabric (HLF) blockchain with report id, timestamp patient’s id, and digital signature of Medical Superintendent (MS). Blockchain digital ledger will distributed between high level authorities (offices of Secretaries’ Health, TCH). Office SSHC&ME work as admin of whole HLF network. For verification, verifier (user/Government department) get the hash of medical fitness report and verify it from HLF blockchain network using HLF SDK","PeriodicalId":145637,"journal":{"name":"Journal of Innovative Computing and Emerging Technologies","volume":"17 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-09-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126695319","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Tissues in human brain become dead to allow new tissues to born at their expiry time but sometime they do not die. The undead tissues cause to form a solid mass in human brain which is known as Brain tumor. Manually the brain tumor detection is considered to be a challenging and time consuming task by analyzing the MRI images. The main objective of this research is to detect and analyze the tumorous part of human brain by using image processing and machine learning approaches. The main objective is further divided into number of tasks: (1) an automated system will be developed to detect the tumorous part in the MRI images of the human brain, (2) the location of the tumor will be identified by highlighting the affected area, and (3) will try to implement practically in the real clinical environment. In this study we will work on a standard BRATS dataset which contains the MRI images with different modalities.
{"title":"Brain Tumor Segmentation & Detection using MRI","authors":"Saleem Butt, Fahad Sabah","doi":"10.56536/jicet.v1i2.12","DOIUrl":"https://doi.org/10.56536/jicet.v1i2.12","url":null,"abstract":"Tissues in human brain become dead to allow new tissues to born at their expiry time but sometime they do not die. The undead tissues cause to form a solid mass in human brain which is known as Brain tumor. Manually the brain tumor detection is considered to be a challenging and time consuming task by analyzing the MRI images. The main objective of this research is to detect and analyze the tumorous part of human brain by using image processing and machine learning approaches. The main objective is further divided into number of tasks: (1) an automated system will be developed to detect the tumorous part in the MRI images of the human brain, (2) the location of the tumor will be identified by highlighting the affected area, and (3) will try to implement practically in the real clinical environment. In this study we will work on a standard BRATS dataset which contains the MRI images with different modalities.","PeriodicalId":145637,"journal":{"name":"Journal of Innovative Computing and Emerging Technologies","volume":"130 ","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-01-09","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134162571","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
We have presented our findings about the momentousness of the UI (User Interface) , also GEx (Gameplay Experience) in addition to UEx (User Experience) on a Computerized game. As in for finding out how a video game gains players attention for hours without knowing, we arranged a fast survey with the help of Google Form for almost 100 partakers but at most 54 responders answered the form, where 83.3% along with 16.7% answerers are gents and ladies separately. These 54 answerers belong to 4 age groups pointing 44.4%, 53.7%, 1.9%and 0% responders to age groups 13 to 20, 21 to 30, 31 to 40 and above 41 years discretely. Only 17.3% answerers have ever tried playing PUBG on console . 25 % and 26.9% responders grade 5 and 4 for Main Menu of PUBG game, 20% and 34% responders grade 5 and 4 on behalf of PUBG game Character, 25% and 30.8% responders grade 5 and 4 on behalf of PUBG Customization Of Characters, 34.6% and 25% responders grade 5 and 4 on behalf of PUBG arcade User Interface. There is likelihood for following projects, in order to figure out which video game possesses best UI, UEx in addition to GEx grades from it’s players all over the world.
{"title":"THE IMPORTANCE OF UI, UEx AND GEx IN VIDEO GAMES 2020","authors":"","doi":"10.56536/jicet.v1i1.4","DOIUrl":"https://doi.org/10.56536/jicet.v1i1.4","url":null,"abstract":"We have presented our findings about the momentousness of the UI (User Interface) , also GEx (Gameplay Experience) in addition to UEx (User Experience) on a Computerized game. As in for finding out how a video game gains players attention for hours without knowing, we arranged a fast survey with the help of Google Form for almost 100 partakers but at most 54 responders answered the form, where 83.3% along with 16.7% answerers are gents and ladies separately. These 54 answerers belong to 4 age groups pointing 44.4%, 53.7%, 1.9%and 0% responders to age groups 13 to 20, 21 to 30, 31 to 40 and above 41 years discretely. Only 17.3% answerers have ever tried playing PUBG on console . 25 % and 26.9% responders grade 5 and 4 for Main Menu of PUBG game, 20% and 34% responders grade 5 and 4 on behalf of PUBG game Character, 25% and 30.8% responders grade 5 and 4 on behalf of PUBG Customization Of Characters, 34.6% and 25% responders grade 5 and 4 on behalf of PUBG arcade User Interface. There is likelihood for following projects, in order to figure out which video game possesses best UI, UEx in addition to GEx grades from it’s players all over the world. \u0000 ","PeriodicalId":145637,"journal":{"name":"Journal of Innovative Computing and Emerging Technologies","volume":"96 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127512707","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Requirements elicitation technique is the main and important part of any software project. There are hundreds of requirement elicitation techniques, and each technique has its unique characteristics and importance but the point is which to use and which do not use. There are some conditions and scenarios in which particular elicitation technique will be suitable. There are some technique which you not known. We are here to introduce some other elicitation technique. Combination of several technique can result in the clear and collect almost all requirement from the customer, user and stakeholder. The purpose of this paper is to know about these elicitation technique and might be these techniques are best for requirement gathering. In this paper we will discuss the 3 requirement elicitation techniques, their detail, advantages, disadvantages and comparison among the techniques. The three techniques are QFD, Focus Group and Ontology.
{"title":"Comparison of Focus Group, QFD and Ontology on the bases of Implementation, Applications and benefits in Requirement Engineering","authors":"","doi":"10.56536/jicet.v1i1.1","DOIUrl":"https://doi.org/10.56536/jicet.v1i1.1","url":null,"abstract":"Requirements elicitation technique is the main and important part of any software project. There are hundreds of requirement elicitation techniques, and each technique has its unique characteristics and importance but the point is which to use and which do not use. There are some conditions and scenarios in which particular elicitation technique will be suitable. There are some technique which you not known. We are here to introduce some other elicitation technique. Combination of several technique can result in the clear and collect almost all requirement from the customer, user and stakeholder. The purpose of this paper is to know about these elicitation technique and might be these techniques are best for requirement gathering. In this paper we will discuss the 3 requirement elicitation techniques, their detail, advantages, disadvantages and comparison among the techniques. The three techniques are QFD, Focus Group and Ontology. \u0000 ","PeriodicalId":145637,"journal":{"name":"Journal of Innovative Computing and Emerging Technologies","volume":"12 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116752713","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Elicitation technique is very important part in the field of requirement engineering, which it is very necessary for software process. Questionnaire is lead to success in our projects. Questionnaire makes us how to avoid confusion in the project. Misguided is very big failure in the software process. Questionnaire makes the right way to successful in every field. Questionnaire is the basics need to correct the design. This paper helps us that using with questionnaire we reduce specially time and cost. Finally we present a article that tells us using questionnaire we reached to succeed in the field of software requirement engineering .
{"title":"Using Questionnaire for Avoid Confusion in Requirement Elicitation Technique","authors":"","doi":"10.56536/jicet.v1i1.9","DOIUrl":"https://doi.org/10.56536/jicet.v1i1.9","url":null,"abstract":"Elicitation technique is very important part in the field of requirement engineering, which it is very necessary for software process. Questionnaire is lead to success in our projects. Questionnaire makes us how to avoid confusion in the project. Misguided is very big failure in the software process. Questionnaire makes the right way to successful in every field. Questionnaire is the basics need to correct the design. This paper helps us that using with questionnaire we reduce specially time and cost. Finally we present a article that tells us using questionnaire we reached to succeed in the field of software requirement engineering . ","PeriodicalId":145637,"journal":{"name":"Journal of Innovative Computing and Emerging Technologies","volume":"37 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131586888","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
As we all know that the requirement traceability is a bigger and important part of software engineering. We here are going to try our best to explain the importance of requirement traceability in the respective field. Our paper is basically consisting on the reasons by which traceability is considered as a very first step of any kind of project. There is a specific team to trace the requirements of any project before the implementation is started. If there is a problem in this team or the team is not working according to the main and important principles of this very field, there will be errors in the project. A traceability matrix allows a requirement engineer to represent the relationship between requirement and work product. Requirement traceability increases with the increase of the steps, working and complexity of the project. Mostly it is the part in which organizations invest most to get the requirement crystal clear. All of the main steps and methods of traceability are discussed in this paper.
{"title":"REQUIREMNET TRACEABILITY IN GREAT DETAIL","authors":"","doi":"10.56536/jicet.v2i1.23","DOIUrl":"https://doi.org/10.56536/jicet.v2i1.23","url":null,"abstract":"As we all know that the requirement traceability is a bigger and important part of software engineering. We here are going to try our best to explain the importance of requirement traceability in the respective field. Our paper is basically consisting on the reasons by which traceability is considered as a very first step of any kind of project. There is a specific team to trace the requirements of any project before the implementation is started. If there is a problem in this team or the team is not working according to the main and important principles of this very field, there will be errors in the project. A traceability matrix allows a requirement engineer to represent the relationship between requirement and work product. Requirement traceability increases with the increase of the steps, working and complexity of the project. Mostly it is the part in which organizations invest most to get the requirement crystal clear. All of the main steps and methods of traceability are discussed in this paper.","PeriodicalId":145637,"journal":{"name":"Journal of Innovative Computing and Emerging Technologies","volume":"58 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122473889","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Changes in the requirements can be proposed by the clients continuously during the whole development cycle of the software. Those changes in requirements causes very major errors on development, cost and time etc. Because at very initial level, requirements are engineers before actual implementation. The effective approach is to handle these changes very efficiently by keeping all things and effects of that change in mind. There are different process models that tells how to handle these changes. This paper suggests different process models to handle those requirements changes. The difference between the process models and also suggest the good approach and good model to handle all these changes. Because its very important to understand, thousands of projects are flopped due to changes. In every system, a stage must come, at which you have to update your software. Some changes are come with the passage of time, and some will come immediately by the customer.
{"title":"Requirement Change Management with respect to Different Models","authors":"","doi":"10.56536/jicet.v1i1.10","DOIUrl":"https://doi.org/10.56536/jicet.v1i1.10","url":null,"abstract":"Changes in the requirements can be proposed by the clients continuously during the whole development cycle of the software. Those changes in requirements causes very major errors on development, cost and time etc. Because at very initial level, requirements are engineers before actual implementation. The effective approach is to handle these changes very efficiently by keeping all things and effects of that change in mind. There are different process models that tells how to handle these changes. This paper suggests different process models to handle those requirements changes. The difference between the process models and also suggest the good approach and good model to handle all these changes. Because its very important to understand, thousands of projects are flopped due to changes. In every system, a stage must come, at which you have to update your software. Some changes are come with the passage of time, and some will come immediately by the customer.","PeriodicalId":145637,"journal":{"name":"Journal of Innovative Computing and Emerging Technologies","volume":"171 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134382306","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Summary of the Research Research goal is better understanding and learning by using old and new techniques for resolve problems and empty blank spaces which are mostly facing during requirement gathering phase to development phase. This paper mainly purpose gathering research on Software requirements gathering and their effect on all incoming challenges and cost, benefits. Requirements is one in technology application style and development. . Most of the projects are fail due to gathering the poor requirement gathering. Many of the software based projects acquired by one to one the interview for requirement gathering. During last few years new software development approaches were introduced for increase software product which are helpful for reduce cost, time, and effort. For all procedure Software Requirement gathering is the one of the special key. Requirement gathering is the most important area in Software Engineering and project management.
{"title":"REQUIREMENTS GATHERINGS AND IMPLEMENT ISSUES","authors":"","doi":"10.56536/jicet.v1i1.7","DOIUrl":"https://doi.org/10.56536/jicet.v1i1.7","url":null,"abstract":"Summary of the Research Research goal is better understanding and learning by using old and new techniques for resolve problems and empty blank spaces which are mostly facing during requirement gathering phase to development phase. This paper mainly purpose gathering research on Software requirements gathering and their effect on all incoming challenges and cost, benefits. Requirements is one in technology application style and development. . Most of the projects are fail due to gathering the poor requirement gathering. Many of the software based projects acquired by one to one the interview for requirement gathering. During last few years new software development approaches were introduced for increase software product which are helpful for reduce cost, time, and effort. For all procedure Software Requirement gathering is the one of the special key. Requirement gathering is the most important area in Software Engineering and project management.","PeriodicalId":145637,"journal":{"name":"Journal of Innovative Computing and Emerging Technologies","volume":"85 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115623119","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Now a day’s project management is play very important part in our software industries. It is a very big deal to handle the project to became a success. There are some phases in the project management process. Number one is requirement gathering it is to get the right the requirements, as so far the most important one to done our projects successfully. Requirements is describe in planned phases then these requirements are used in the projects when it doesn’t end. Here is few technique for getting the requirement. Interview, questionnaires, prototyping, brainstorming and storyboard. When we gathering requirements, many problems are going to faced which are not good or better for completing the project. Will discuss in this paper about these techniques and problems and also find our there proper solution.
{"title":"Requirements Gathering Techniques and Issues","authors":"","doi":"10.56536/jicet.v1i1.6","DOIUrl":"https://doi.org/10.56536/jicet.v1i1.6","url":null,"abstract":"Now a day’s project management is play very important part in our software industries. It is a very big deal to handle the project to became a success. There are some phases in the project management process. Number one is requirement gathering it is to get the right the requirements, as so far the most important one to done our projects successfully. Requirements is describe in planned phases then these requirements are used in the projects when it doesn’t end. Here is few technique for getting the requirement. Interview, questionnaires, prototyping, brainstorming and storyboard. When we gathering requirements, many problems are going to faced which are not good or better for completing the project. Will discuss in this paper about these techniques and problems and also find our there proper solution.","PeriodicalId":145637,"journal":{"name":"Journal of Innovative Computing and Emerging Technologies","volume":"95 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"117297167","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
In a period of one year, we study software requirement as a subject over couple of semester. We do experiment in different software houses in Lahore Pakistan. Our Four team member goes to the different software houses for our team project .we noticed that our 80% of software houses don’t get requirement from their employee if they get requirement they don’t known about the processes for requirement. After some time we does some experiments on software houses with our team, we noticed that 90 percent project are not completed because of incorrect requirement and required processes for the project and 80 percent software houses is in loss .client will change their requirement when they want to change .Many software houses want improvement that will only happened to improve their process improvement. Different software want different process improvement and process models. In this paper we identifies some improvement in requirement and in processes. We also noticed continues improvement in the processes are required to achieve a good result. The supportive culture of any organization is helpful to achieve the goals of the organization .we study in this paper about the continuous improvement and how to get requirement from our client.
{"title":"Process Improvement Required for Software Requirement","authors":"","doi":"10.56536/jicet.v1i1.3","DOIUrl":"https://doi.org/10.56536/jicet.v1i1.3","url":null,"abstract":"In a period of one year, we study software requirement as a subject over couple of semester. We do experiment in different software houses in Lahore Pakistan. Our Four team member goes to the different software houses for our team project .we noticed that our 80% of software houses don’t get requirement from their employee if they get requirement they don’t known about the processes for requirement. After some time we does some experiments on software houses with our team, we noticed that 90 percent project are not completed because of incorrect requirement and required processes for the project and 80 percent software houses is in loss .client will change their requirement when they want to change .Many software houses want improvement that will only happened to improve their process improvement. Different software want different process improvement and process models. In this paper we identifies some improvement in requirement and in processes. We also noticed continues improvement in the processes are required to achieve a good result. The supportive culture of any organization is helpful to achieve the goals of the organization .we study in this paper about the continuous improvement and how to get requirement from our client.","PeriodicalId":145637,"journal":{"name":"Journal of Innovative Computing and Emerging Technologies","volume":"244 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133445994","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：