Non-functional System Requirements Research Articles

Architectural Design for Data Security in Cloud-based Big Data Systems

Architecture design of system is creative process after all. Non-functional requirements and software architecture have a strong relationship. Security of system is one of great concern and it is a non-functional need and requirement. The architectural style and structure chosen for a system should be based on the non-functional system requirements. Big Data technologies are used to store handles huge amounts of operational data in the public domain. Structure and behavior diagrams of the system is proposed that use a secure architectural design for a system that works over the cloud. Different components of Big Data have been investigated in this research work due to the seriousness of security issues focus on privacy and confidentiality. The security of data over the cloud being outsourced is a growing concern. There are outsider and insider malicious database administrators who can gain access and modify private and sensitive data therefore database service provider can be deceitful. Security mechanisms are necessarily required to protect sensitive data residing on public clouds. At the application level, the proposed solution ensures privacy and confidentiality of data at rest over the cloud. Extensive tests have been carried out, and the results of this research work are as follows that the recorded results revealed statistically significant variations in plaintext and multimedia contents (i.e., audio and video) with time measured in milliseconds for small, medium, and large datasets..

Analysis of non-functional requirements of the speech recognition system

Analysis of non-functional requirements of the speech recognition system

Making Applications for Midwives' Independent Practice Using the Waterfall Method

The patient's medical records at the Independent Midwife Practice (PMB) must be stored and kept confidential in order to provide good, quality, and responsive health services to patients. Nuning Midwife Independent Practice Nuning, S.ST,. Tanah Bumbu was founded in 2012. During its 11 years of existence, patients still have to queue in the waiting room for a long time. This is because the service process and medical records used are still manual. This study aims to make a special application on PMB. Researchers use the research and development method to facilitate the research process and the waterfall method as a reference for the PMB application development process. The resulting development product is a PMB application that can provide convenience to midwives in providing services to patients and reduce the long queue of patients in the waiting room. Data collection used interviews with 2 respondents from PMB owners and midwives. The results of the research are in the form of functional and non-functional system requirements for PMB applications. These needs are translated in the form of system design in the form of system flowcharts, use case diagrams, class diagrams, activity diagrams, entity relationship diagrams, and data flow diagrams. The design is then translated into a programming language using PHP programming and MySQL database. From the results of this study, it has several features, namely login features, patient visit report features, patient referral letter features, detailed identity data features for patients and midwives, notification features, patient registration/registration features independently, and patient examination results record features. Features that are not yet available in the PMB application are the automatic payment feature and the distance between the PMB and the referred hospital.

A systematic review of non-functional requirements mapping into architectural styles

Fortunately, the software attracted enough businesses to the market, allowing them to earn money in less time with less work and more accurate results. Software development life cycle (SDLC) is used for software development as it is responsible for system functionality, efficiency, maintainability, and any other non-functional system requirements. Each stage of the SDLC process is critical. However, software requirements and software architecture are both fundamental activities that play a vital role in all other SDLC stages. Non-functional requirements are critical to the success of any software because they explain all system quality attributes such as complexity, reliability, security, and maintainability, among others. The architectural styles assist you in determining which architecture may be best for your project requirements. This paper discusses several of the most important architectural styles that are best suited for mapping desired non-functional requirements for software development, as well as their comparison based on various quality attributes (non-functional requirements).

Implementation of Forward Chaining for Diagnosis of Dengue Hemorrhagic Fever

Insects in the form of mosquitoes are transmitting vectors of several types of diseases that are quite dangerous and need to be watched out for because they can be deadly, such as dengue fever mosquitoes, malaria, elephantiasis and the like. Patients suffering from mosquito-borne diseases must be treated immediately to find out the type of disease they are suffering from and their treatment solutions. The era of digitalization that is growing rapidly, including in the field of medical science, makes the use of information technology to help improve quality services for the community. The analysis used in this research is using the forward chaining method, as a comparison of the overall process of the problems obtained in the investigation and developed using the waterfall paradigm. Forward chaining is optimized because the disease diagnosis process begins by observing the symptoms experienced by a patient and then continues with a tracing process that results in conclusions about the dengue fever suffered. While the waterfall method is used in the development of this expert system because the method can accommodate all stages of the system starting from the analysis of functional and non-functional system requirements, system design, coding, expert system testing and the last stage is expert system maintenance. The data used in this study used data at the Maos Health Center, Cilacap Regency. Testing is carried out using the black box testing method where the expert system is tested on end-users to determine the level of success and usability of the developed system. The questionnaire was given to 76 respondents with the results of the questionnaire: 91.9% indicating the level of user satisfaction, 89.6% indicating the level of effectiveness and 92.2% indicating the level of efficiency of the expert system. The output of this study is the conclusion of the disease suffered by the patient and the solution for handling it.

Quantitative verification with adaptive uncertainty reduction

Stochastic models are widely used to verify whether systems satisfy their reliability, performance and other nonfunctional requirements. However, the validity of the verification depends on how accurately the parameters of these models can be estimated using data from component unit testing, monitoring, system logs, etc. When insufficient data are available, the models are affected by epistemic parametric uncertainty, the verification results are inaccurate, and any engineering decisions based on them may be invalid. To address these problems, we introduce VERACITY, a tool-supported iterative approach for the efficient and accurate verification of nonfunctional requirements under epistemic parameter uncertainty. VERACITY integrates confidence-interval quantitative verification with a new adaptive uncertainty reduction heuristic that collects additional data about the parameters of the verified model by unit-testing specific system components over a series of verification iterations. VERACITY supports the quantitative verification of discrete-time Markov chains, deciding which components are to be tested in each iteration based on factors that include the sensitivity of the model to variations in the parameters of different components, and the overheads (e.g., time or cost) of unit-testing each of these components. We show the effectiveness and efficiency of VERACITY by using it for the verification of the nonfunctional requirements of a tele-assistance service-based system and an online shopping web application.

Perancangan dan Pembuatan Aplikasi Retensi dan Pemusnahan Berkas Rekam Medis Di Rsud Dr. H. Moch. Ansari Saleh Banjarmasin

One of the hospitals that have carried out retention and destruction activities is Dr. H. Moch. Ansari Saleh Banjarmasin. The retention and destruction of medical records are still done manually. This research’s purpose by design and create a retention and extermination application of medical records file. This type of research uses qualitative research with the development of the waterfall model system. Data collection includes interviews, observation, FGD, and documentation. The results of the study are functional and non-functional system requirements for making retention and destruction applications, based on the results of the FGD to the medical record filling staff and the head of the medical record unit. The results of the requirements that have been obtained are interpreted in the design of systems and software made through flowchart systems, context diagrams, data flow diagrams (DFD), and entity-relationship diagrams (ERD). The implementation process and unit test use the MySQL database and the PHP programming language and the interface design uses the Codeigniter Framework. The application system integration test uses the functional test of the Black Box Test method with a 100% system trial success rate. . The results of this functional test indicate that the retention and destruction applications can be integrated and function properly with innovations in the form of an annual import database feature, a feature for retention and destruction reports, and storage of scanned files in pdf format. The existence of this application can help the implementation of retention and destruction of medical record files at Dr. H. Moch. Ansari Saleh Banjarmasin has become more effective and efficient in terms of time, use value, and data security.

Smart Factory Web—A Blueprint Architecture for Open Marketplaces for Industrial Production

The paper describes a reference architecture for open marketplaces to be used for networked stakeholders in industrial production ecosystems. The motivation for such an endeavor comes from the idea to apply the basic principle of the platform economy to offer functions of an asset “as a service” to industrial production, including the associated supply chain networks. Currently, commercial offers of “production as a service” usually lead to proprietary systems with the risk of platform vendor lock-ins. Hence, there is a need for an open approach that relies upon international (emerging) standards, especially those from IETF, IEC, the Plattform Industrie 4.0 and the International Data Spaces Association (IDSA). The presented approach enables federation of marketplaces according to well-defined interfaces. This article proposes a technology-independent open architecture derived from functional and non-functional system requirements and driven by the idea of the Smart Factory Web, a testbed of the Industrial Internet Consortium (IIC). Furthermore, the architecture of the Smart Factory Web (SFW) platform is presented and assessed against the current and future demands of open federated marketplaces for industrial production ecosystems.

System performance requirements: A standards-based model for early identification, allocation to software functions and size measurement

Background: In practice, the developers focus is on early identification of the functional requirements (FR) allocated to software, while the system non-functional requirements (NFRs) are left to be specified and detailed much later in the development lifecycle. Aim: A standards-based model of system performance NFRs for early identification and measurement of FR-related performance of software functions. Method: 1) Analysis of performance NFR in IEEE and ECSS standards and the modeling of the identified system/software performance functions using Softgoal Interdependency Graphs. 2) Application of the COSMIC-FSM method (e.g., ISO 19761) to measure the functional size of the performance requirements allocated to software functions. 3) Use of the COSMIC-SOA guideline to tailor this framework to service-oriented architecture (SOA) for performance requirements specification and measurement. 4) Illustration of the applicability of the proposed approach for specification and measurement of system performance NFR allocated to the software for an automated teller machine (ATM) in an SOA context. Results: A standards-based framework for identifying, specifying and measuring NFR system performance of software functions. Conclusion: Such a standards-based system performance reference framework at the function and service levels can be used early in the lifecycle by software developers to identify, specify and measure performance NFR.

A PROCESS MODEL FOR THE FORMALISATION OF QUALITY ATTRIBUTES OF SERVICE-BASED SOFTWARE SYSTEMS

The benefits offered by software architectures include providing an improved understanding of high-level relationships amongst systems components and facilitating in making principled decisions between alternatives. A vast majority of architectural decisions are focused on realising functional requirements and often ignore the nonfunctional requirements (quality attributes) altogether or include them as an afterthought. This has a negative impact on the overall acceptance of the software system by its intended users. Moreover, these architectures are specified using diagrammatic notations such as boxes and lines as connectors between them. As a result, such semiformal representations lack precision in their definitions and may lead to misinterpretations of the architecture resulting in errors being introduced at later stages of development. Although several Architectural Description Languages (ADLs) exist for the formalisation of systems architectures, few are designed for formalising nonfunctional requirements. Since ADLs concentrate on component-level representations and not on the system as a whole, their support of non-functional requirements is limited. Additionally, as each ADL normally supports one quality attribute, multiple ADLs are required to cater for various quality attributes. This articles aims to address the challenges of inadequacies of specifying quality attributes in software systems in a manner that is both formal and applicable to a wider range of quality attributes. To achieve this goal, this paper present a process model that assists in formalising the non-functional requirements of a service-based software system and eliminates the need for multiple ADLs. It demonstrates the practicability of the proposed model by applying it to one quality attribute, namely “availability”, using the general purpose Z specification language.

Using GORE in Big Data: A Systematic Mapping Study

Big Data has developed rapidly into a hot topic that generates great attention in academia, industry and governments around the world because of its ability to process large volumes of data at a reasonable speed. The real value of Big Data lies in the help to business decision making, so it requires appropriate methods and techniques to find the requirements of the system to be developed. However, the Big Data community has focused mainly on technologies to obtain information, and not on the goal of the business. The objective of this paper is to offer an overview of how some Goal Oriented Requirements Engineering (GORE) proposals are used to obtain the requirements of the Big Data system, serving as a starting point for future research. The methodology used is the Systematic Mapping. The goal models identified it is used as conceptual models for different situations: understanding the nature of business and analyzing the technical aspects for purposes of functional and non-functional requirements of Big Data system.

Research on Target Detection Methods under the Concept of Deep Learning

As a classic subject in the field of image processing and computer vision, target detection has a wide range of applications in traffic monitoring, image retrieval, human-computer interaction and so on. It aims at detecting objects of interest in a static image. In view of the strong expressive ability of convolutional neural networks in deep learning, this paper presents the classical detection framework R-CNN of deep learning. Based on the above detection framework, the functional requirements, such as data pre-processing, training model and image prediction, as well as the non-functional requirements of the target detection system are analysed. According to the above requirements, a target detection system based on deep learning is developed. Practice has proved that the system has good performance in terms of hardware and performance.

The Most Important Functional and Non-Functional Requirements of Knowledge Sharing System at Public Academic Institutions: A Case Study

The Most Important Functional and Non-Functional Requirements of Knowledge Sharing System at Public Academic Institutions: A Case Study

Dynamic Modular Architecture for Product Lifecycle

A module is a set of components with interfaces selected in order to help designers address ilities or non-functional system requirements. Consequently, the boundaries of a module do not necessarily coincide with those dictated by functional decomposition. Modularization usually makes the architecture more complex due to additional interfaces and redundancies that have negative consequences on system performance. As a result, modularization is accompanied by a trade-off between non-functional and functional requirements. Additionally the system lifecycle consists of several phases, each characterized by different activities and goals. Systems may benefit from different modular architectures in the different lifecycle phases. This paper presents a dynamic modular architecture methodology, where the modular architecture changes over the different product lifecycle phases. An example of a relatively simple mechanical system - a bicycle – is presented to illustrate the implementation of the methodology.

Addressing the non-functional requirements of computer vision systems: a case study

Computer vision plays a major role in most autonomous systems and is particularly fundamental within the robotics industry, where vision data are the main input to all navigation and high-level decision making. Although there is significant research into developing and optimising algorithms for feature detection and environment reconstruction, there is a comparative lack of emphasis on how best to map these abstract concepts onto an appropriate software architecture. In this study, we distinguish between functional and non-functional requirements of a computer vision system. Using a RoboCup humanoid robot system as a case study, we propose and develop a software architecture that fulfills the latter criteria. To demonstrate the modifiability of the proposed architecture, we detail a number of examples of feature detection algorithms that were modified to capture the rapidly evolving RoboCup requirements, with emphasis on which aspects of the underlying framework required modification to support their integration. To demonstrate portability, we port our vision system (designed for an application-specific DARwIn-OP humanoid robot) to a general-purpose, Raspberry Pi computer. We evaluate the processing time on both hardware platforms for several image streams under different conditions and compare relative to a vision system optimised for functional requirements only. The architecture and implementation presented in this study provide a highly generalisable framework for computer vision system design that is of particular benefit in research and development, competition and other environments in which rapid system evolution is necessary to adapt to domain-specific requirements.

A Case Study upon Non-functional Requirements of Online Banking System

The proper working of online banking is essential for development and advancement over the world and influencing organizations, society and individuals. Online banking, a vital activity within the financial markets is experiencing real change fuelled by advances in information systems techniques. Non functional requirements (NFRs) are important software requirements that have been evaluated and specified right from the beginning of software development cycle while specifying the functional software requirements (FRs). Nfrs could be thought of as additional requirements that must be fulfilled by the functional requirements. The dissatisfaction of Nfrs is one of the indispensable purposes behind the failure of software projects. Nonfunctional requirements for instance accuracy, usability, performance and security are often crucial to online banking system. Accordingly the nonfunctional requirements or Nfrs should be given attention as early as possible in a software lifecycle and must be shown in the software design before conferring to the detailed design. The inspiration driving this paper is to examine how the assessment of Nfrs of online banking system serves to systematically make choice among different alternatives.

Presenting an Excusable Model of Enterprise Architecture for Evaluation of Reliability using Colored Petri Nets

Upon increasing application of unified modeling language diagrams for description of enterprise architecture and importance of evaluating the non-functional requirements in the enterprise architecture, establishing an executable model of these diagrams is necessary. On the other side, unified modeling language diagrams have not the capability of evaluating the non-functional requirements of system directly. The simplicity and characteristics of these diagrams must be reserved and the capability of evaluating these requirements to be incorporated thereto. To achieve this goal, an executable model of these diagrams to be Created. In this paper, it is assumed that architecture of a system has been described by two use case and collaboration diagrams of unified modeling language. The role of these diagrams in evaluation of reliability and annotations related thereto has been examined and extended by a algorithm to an executable model means colored Petri net. In this study, the procedure of establishing an executable model that can analyze the reliability of artifacts in C4ISR framework. According to the results obtained from simulation of this model and their analysis, we could identify the problems in planning phase and improve out artifacts in order to avoid the extreme time and economic costs of implementation.

An executable software architecture model for response time and reliability assessment

Article history: Received January 20, 2014 Accepted 5 July 2014 Available online August 16 2014 With the increasing use of the Unified Modeling Language (UML) diagrams to describe the software’s architecture and the importance of evaluating nonfunctional requirements at the level of software architecture, creating an executable model from these diagrams is essential. On the other hand, the UML diagrams do not directly provide features to evaluate nonfunctional system requirements. Thus, these capabilities can be added to UML diagrams by applying efficiency and reliability stereotypes. Because the techniques used in the UML is able to deal with certain matters, we develop uncertain UML, stereotypes and tags. In this paper, the architecture of a software system is described by using use case diagram, sequence and deployment of unified modeling language diagrams with annotations fuzzy stereotypes related to response time and reliability. The proposed method for calculating the response time and reliability based on fuzzy rules are introduced, and the algorithm is implemented for an executable model based on colored fuzzy Petri net. © 2014 Growing Science Ltd. All rights reserved. Turnover intentions Key Software Architecture Performance Evaluation Reliability Fuzzy stereotypes Fuzzy colored Petri net

Aspect-Oriented Model-Driven Engineering for Embedded Systems Applied to Automation Systems

Automation and control systems include many “intelligent” automation devices, which are usually implemented as complex embedded systems. New methods and tools are demanded to cope with the increasing design complexity, while keeping the project on schedule. Proper handling of nonfunctional system requirements is a key factor during the design of industrial automation systems, since in some application domains they are as important as (sometimes, more important than) functional requirements. This paper presents a model-driven engineering approach, which combines Unified Modeling Language (UML) and aspect-oriented software development (AOSD) to design real-time and embedded automation systems. The proposed approach allows a smooth transition from the initial phases to implementation by using software tools, comprising the system specification and the automatic generation of source code. By combining UML with model-level aspects and a script-base code generation tool, it enables the use of AOSD during system design and implementation, even though the target platform does not natively support such concepts. Experimental results on using this approach to design real-world examples of automation systems are presented. The results indicate a positive impact on the design of automation systems. The encapsulation of nonfunctional requirements was improved, increasing the reuse of developed artifacts. Generated source code statistics indicate that the proposed approach can generated a fair amount of code per model element.

Design Patterns to Implement Safety and Fault Tolerance

This paper discusses an object orient approach based on design pattern and computational reflection concept to implement nonfunctional requirements of complex control system. Firstly we brief about software architecture design, followed by control-monitor safety pattern, Tri-Modular redundancy (TMR) pattern, reflective state pattern and fault tolerance redundancy patterns that are use for safety and fault management. Reflection state pattern is a refinement of the state design pattern based on reflection architectural pattern. With variation in reflective design pattern we can develop a well structured fault tolerant system. The main goal of this paper is to separate control and safety aspect from the application logic. It details its intent, motivation, participants, consequences and implementation of safety design pattern. General Terms Design pattern, Safety pattern, Fault tolerance.