Nonfunctional Requirements with Data Mining

INTRODUCTION

The use of software has invaded our daily lives as it permit us to perform many responsibilities especially those that are associated in doing various business techniques and in dealing with different business systems. It allows the utilization of knowledge on both processing and computer systems to have the ability to help solve various problems which confront everyday situations. The often most encountered problems experienced in neuro-scientific software engineering handles computers and processing although its fundamental causes aren't actually on such measurements, and oftentimes go beyond such. To be able to recognize a good software anatomist program, the following standards must be accordingly observed: there exists quality in what we can recognize but we can not define; there is certainly fitness of purpose; there is an presence of conformance relative to technical specs; it is linked with inherent product characteristics; and it can be assumed to be reliant on the amount at which the client is willing to pay (Pfleeger & Atlee, 2006).

With all the complexities and the complications confronting the businesses nowadays, certain requirements for system engineering has been seen to offer a solution. The requirements are the ones which form the foundation for planning the introduction of a system and accepting it on the completion. They are able to form a basis for job planning, risk management, acceptance assessment, trade-off, and change control (Hull et al, 2005). Requirements are designed to specify the precise packages of features which are crucial to the software or program. They can either be practical or non-functional. Useful requirements can be explained as the specification of a function that the system must support while non-functional requirements refer to the constraints associated on the operation of the system that is not directly related to a function of the machine (Bruegge & Duttoit, 2010).

In simpler terms, non-functional requirements consider not what the software can do but the way the software can do it. It really is geared towards a much wider range as it discounts more with certain requirements for process rather than just the various tools which are necessary for operation. The researcher agrees to the fact that non-functional requirements are indeed important because they are able to dwelling address various problems which are essential in the success of quality. They are very vital for the success of the machine and if they're not properly resolved, the result can be damaged and they can be inconsistent and low quality, users and customers would end up being dissatisfied, and additionally, it may influence time and cost that happen to be associated with jogging the machine.

LITERATURE REVIEW

One of the most recognized need for non-functional requirements in software executive is its capacity to establish system properties and constraints. Non-functional requirements can be classified as product requirements, organizational requirements, and external requirements. Product requirements refer to specifications which package with what sort of particular product which is shipped should react in a particular way such as those related to execution swiftness and trustworthiness. Furthermore, organizational requirements make reference to the consequences of the insurance policies and steps of the organization including the variety of process specifications which are sued as certain requirements undergo implementation. Finally, external requirements are those that arise because of the various factors which can be external to the development process and system. The primary reason on why non-functional requirements come up as a result of needs from the users, budget constraints, and existing policies of the organizations, there is a dependence on interoperability with other hardware or software systems, and as a result of presence of exterior factors such as expectations for protection (Puntambekar, n. d. ).

Matching to Chung et al (n. d. ), software executive illustrates both pragmatic and systematic alternatives in which we are provided with the ability to to determine software systems of the best specifications and quality in relation to its consumption and operation. It demands the need of software manufactured systems to be modifiable, accurate, and secured that happen to be some of the signs of a higher performing software system. However, they are extremely subjective making them a difficult subject for the purpose of evaluation. The machine typically interacts with the other person making their functions have an impact on the general system and for that reason it also impacts the complete system.

Non-functional requirements are also being characterized for being hard to cope with in comparison with useful requirements generally because their impact is not generally localized to only a specific area of the system. Instead, it will involve the entire system. The various changes with practical requirements in software will also inevitably have an impact on the non-functional requirements. An effective software architecture evaluation is often the tool which is utilized to have the ability to deal with the many impacts of non-functional requirements (Aurum & Wohlin, 2005).

Data mining can be considered among the important aspect of software system and of software executive. Data mining consists of solving data problems which already can be found in the software particularly discussing the process of discovering habits in the info. The process should be either automatic or semi-automatic and it should be present in substantial quantities to have the ability to reap the utmost benefits out of these existing data (Witten & Frank, 2005). It could be aptly thought as "extracting or mining knowledge from huge amounts of data" (Han & Kamber, 2006). It can be actually cared for as the procedure of mining knowledge from existing data and not the other way around. The process of data mining could include the following steps: data cleaning, data integration, data selection, data change, data mining, design analysis, and knowledge demonstration.

Data mining activities are some of the practices performed by organizations, especially among software designers, to be able to improve software quality and output. Data mining in neuro-scientific software anatomist ahs recently surfaced since it ahs been known among establishments that such is needed in order to raise the great quantity of data and they are also helpful in solving different kinds of real-world problems. Data mining algorithms are by being increasingly used in various software engineering duties to be able to improve the productivity of the machine or the program. These algorithms can be able to help engineers to what code locations must be improved when another code location is changed. Data mining in neuro-scientific software engineering can be carried out in the series of the following techniques: collection or research of software anatomist data; determining software engineering duties; pre-processing of data; adapting or producing algorithm which will be performed for mining; and post handling or software of mining results (Xie 1t al, 2009).

The non-functional requirements in data mining could result from the operating environment, the users, and the competitive products. Inside the operating environment, data can be influenced by the machine which is used in supporting the procedure. It poses problem on how the software will work towards establishing vibrant data structures. Furthermore, users are also behind the non-functional requirements for data mining in software engineering mainly because they control a large fraction of the complete program and they are the ones who completely understand the qualities of the machine. Lastly, the existence of competitive alternatives affects the non-functional requirements because of their features which generally influence the quality of the system (Malan & Bredemeyer, n. d. )

RESEARCH QUESTIONS:

In order to properly carry out the goal of the study, that is to offer an insight on the many non-functional requirements which can be found with regards to data mining, the study will attempt to answer various research questions that will form groundwork of the study and which will form the backbone of the study. The research questions which the researcher will try to shed light to includes
  1. What is the type of non-functional requirements in software executive and how they are different with functional requirements based on the extent useful and practice in the overall industry?
  2. What are the examples of non-functional requirements in data mining?
  3. How are these non-functional requirements in data mining tackled by the software technicians of today? Are they tackled effectively?
  4. What does the continuing future of requirements analysis in the field of software engineering keep for the non-functional requirements in software engineering?

RESEARCH METHODOLOGY

To have the ability to successfully carry out the purpose of this research, the researcher will use an exploratory research design wherein the principal objective of the analysis will be the provision of insights into and understanding of the topic at hand. The study will be qualitative in aspect, which will take into account significant data and previous researches that are related to the topic rather than interacting with quantitative techniques of research.

In carrying out a qualitative research, the researcher will utilize widely available extra data and literature from credible options such as books, scholastic articles, academic journals, credible websites, and other reputable options which will supply the researcher with more information about the non-functional requirements of data mining in the field of software engineering. Due to the very aspect of this issue, first palm information will be quite hard to obtain that is why used information will be preferred for this study. Widely available references will provide significant researches which have been previously done and you will be geared towards dropping light to the topic. It must be however grasped that although this issue is bound to data mining in software engineering, where the researcher confirms its topic against other works, resources and referrals regarding software anatomist in general may also be sued to be able to give a general point of view of this issue accessible.

RESEARCH PLANNING

To successfully finish the newspaper and generate significant findings, you will see a pre-determined time-frame which will include all the activities which will be related to the completion of the research. Inside the first weeks of doing the study, the researcher will focus into redefining or reshaping the basics of the research considering that some alterations can be eyed. However, since the topic appears to be good enough as a location of study in neuro-scientific software engineering, the succeeding weeks of the research will be centered towards extensive research which shall form the big part of the whole paper. Since the researcher decided to utilize secondary sources accessible, much of the time will be spent browsing through catalogs and other reputable sources to get more idea about the topic. Once the information needed has already been enough and sustainable to support the researcher's case and to give answers to the research questions earlier revealed, writing the overall research based on a previously outlined structure will commence which will be followed with succeeding evidence reading and revisions that will ensure that the task is fully equipped before finally submitting the work and the final presentation of the research.

REFERENCES:

Aurum, Aybuke, Wohlin, Claes, (2005). Engineering and Managing Software Requirements. Sweden: Springer

Bruegge, Bernd. , Duttoit, Allen (2010). Object-oriented Software Anatomist. 3rd ed. USA: Pearson Education Inc.

Chung, L. , Nixon, B. , Yu, E. , Mylopoulos, J. (n. d. ). Non-functional Requirements in Software Engineering.

Han, Jiawei. , Kamber, Michelin (2006). Data Mining Ideas and Techniques. Elsevier: USA

Hull, Elizabeth. , Jackson, Ken. , Dick, Jeremy, (2005). Requirements Anatomist. 2nd ed. United Kingdom: Springer

Malan, Ruth, Bredemeyer, Dana, (n. d. ). Defining Non-functional Requirements. Bredemeyer Consulting

Pfleeger, Shari Lawrence. , Atlee, Joanne (2006). Software Executive: Theory and Practuce. 3rd ed. USA: Pearson Prentice Hall

Puntambekar, A. A. (n. d. ). Software Anatomist. Technical Magazines Pune

Witten, Ian. , Frank, Eibe (2005). Data Mining: Practical Machine Learning Tools and Techniques. USA: Elsevier

Xie, Tao. , Thummalapenta, Suresh. , Lo, David. , Liu, Chao (2009). Data Mining for Software Engineering

Also We Can Offer!

Other services that we offer

If you don’t see the necessary subject, paper type, or topic in our list of available services and examples, don’t worry! We have a number of other academic disciplines to suit the needs of anyone who visits this website looking for help.

How to ...

We made your life easier with putting together a big number of articles and guidelines on how to plan and write different types of assignments (Essay, Research Paper, Dissertation etc)