Nonfunctional Requirements in Systems Analysis and Design

One of the primary responsibilities of requirement engineer is the elicitation of non-functional and functional requirements. Functional requirements sketch out the functionality, the system has to be performed while non-functional requirements compel the restrictions on this functionality. Software industry is raising its demand for not only the required functionality but the necessity of non-functional requirements too such as performance, security, usability, security, privacy etc. The current practice in the industry is to deal with functional requirements as first class requirements while non-functional requirements are only catered at design and implementation level. This approach leaves a serious flaw in the system design towards user satisfaction and often results in the failure of projects such as the classic example of London Ambulance System[1]. The chances of software success can be maximized when dealing with NFR at the requirements level. This literature survey is a first effort of its kind to seek key NFR challenges and issues while elicitation level of requirement engineering. It also find-outs the approaches and methods that are suggested in literature to deal with these issues.

The integration of ‘‘real options’’ analysis will radically change the design of public and private systems. It will change the processes of system design, the way planners deal with uncertainly and risk. It will also change the outcomes, the kinds of elements designers build into the system as they develop it. This paper explains this coming evolution, and presents cases documenting the changes in attitude and the results already occurring. To think in terms of options alters the way one deals with uncertainty. Conventionally, good design minimizes risk. It focuses on increasing reliability and making the best decisions in risky situations. In short, it is reactive to risk. The framework of options thinking, however, recognizes that uncertainty adds value to options. In this context, uncertainty is a driver of value and can be viewed as a positive element. Correspondingly, systems design from this perspective is proactive towards risk. It seeks out opportunities to add value and commits to ongoing processes of information gathering to ensure that options can be exploited at the correct time. Thinking in terms of real options leads designers to build much more flexibility into a system than is common in current practice. For example, they may build duplicate combustion facilities that allow a plant to burn both natural gas and oil, or deliberately develop products that they may never launch. These investments that may be unused are ‘‘options’’; they give the system managers the capability to change the design or product mix, without requiring them to do so. The analysis of real options involves a set of procedures that adapt and extend the options analysis that won a Nobel in economics for its developers. Options analysis is now widely used for contracts on all kinds of widely traded financial instruments (stocks and bonds), commodities (oil, grain, and foreign exchange) and services (electric power, communications bandwidth). The analysis of real options applies the same basic principles, but adapts them to the particular circumstances of systems design, which generally deals with unique projects that lack historical statistics on risk. The analysis of real options enables managers and designers to estimate the value of system flexibility. As this has not been practical before, designers have previously not considered the value of flexibility. Incorporating this capability into systems analyses adds two significant dimensions to design. Public and private operators of major systems will come to recognize: - Large classes of projects as much more valuable than they now seem to be – these include all those that enable further development without committing to it prematurely, such as research, product development, system modularity, exploratory mining, etc.; and - New classes of design alternatives, specifically those enabling managers to adjust the system as needed when relevant information becomes available, that is design alternatives that involve deferral, acceleration and closure of facilities. The paper illustrates the wide range of applications of for the analysis of real options, using documented cases in many fields of engineering. It also refers to the extent possible to companies changing their procedures for system design and management to capitalize on the promise of real options.

Technical system design processes are typically based on systems engineering vee models where designers move between functional and physical domains as they develop detailed designs of the overall system and its sub-systems and component parts. The movements between the functional and physical domains are informed by the core activities of any design process: synthesis, description, analysis and simulation, and decision-making. However, delivering socio-technical systems design mindsets, such as those needed to design multi-team systems, requires a new branch of systems science that integrates human behavior into system behavior. Design processes built on such a science would allow system designers to compare alternative solutions in terms of their anticipated performance and consider different options with respect to functions carried out by humans and machines. In this chapter we use a systems design process vee model and apply it to a case study that involves the design of a multi-team customer service system. Both the application of the vee model (i.e., the proposed design process) and the results of its application (i.e., the multi-team customer service system) can be regarded as socio-technical systems and are used to illustrate and elaborate on Clegg’s (Appl Ergon 31(5):463–477, 2000) socio-technical principles for system design. On this basis, we provide a practical framework for designing socio-technical systems and identify requirements for developing future methods and tools to support this process.

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.

The paper examined the problem of modeling and design of software computer systems. The article briefly describes the content aspects of the various stages of the implementation of software complexes and systems. The methodology of research and analysis of systems, which uses the method of computer simulation modeling, is given. The aim of the work is to create a new universal approach to the design and implementation of software systems of various levels of complexity. During the study, the following general scientific methods were used: system analysis, synthesis, formalization, modeling, decomposition, structuring, description, comparison. The materials used in the study were: computers and software development tools. As a result of the study proposed a universal agent-module approach to the design and implementation of software systems based on simulation agent-based modeling. The study presents the processes of modeling and designing software systems, their stages, and the possibility of their integration within the described approach. Examples of formal model and structure of the software system under design based on the agent-module approach are presented. The proposed approach can be used in the process of software development at the initial stages related to modeling and designing of software systems. Integration of modeling and design stages in the proposed approach will significantly reduce software development time and simplify the design process by making it clearer and more formalized. Materials of the article are of scientific and practical value for a wide range of specialists interested in system analysis, modeling, design and implementation of software systems.

This article is concerned with how to represent in system design the kinds of features of work settings as reported by ethnographic studies of work. Various researchers and practitioners have found that ethnomehodological analyses of work settings can provide useful insights to the work processes and settings in which system design is interested. Previously at Lancaster University, we examined ways in whisk ethnography can be used in h e design process and how the results of ethnographic analyses can be presented in such a way as to be useful components of the design process. This article reflects an effort to approach these methodological issues from a different perspective. It examines how the lessons learned from ethnographic studies can be reflected in the design process itself and in particular how standardized design artifacts (e.g., models, documents) can express the type of information that ethnographic studies produce. The article focuses on how ethnographic analyses can influence the main representational artifact in systems design—the model of the system being developed. We examine how the Unified Modeling Language for object-oriented design can be used to express information about awareness in cooperative systems.

Software architecture design is an important stage in the whole software development lifecycle. Yet non-functional requirements (NFRs) have been afflicted architects for a long time and how to efficiently design and address them also becomes a big headache problem. This paper focuses on the NFRs in architecture and offers a preliminary insight on separating them in a multiple dimensional way. Consequently, it proposes a model named "1+X" for handling NFRs in architecture, including classifying those into 12 dimensions, and then specifying and mapping those into aspects. By this model, architects can easily analyze and handle NFRs during the architecture design for a specific system.

The satisfaction of Non-Functional Requirements (NFRs) has a clear impact in the success of Ambient Intelligence (AmI) Systems. However, existing methods and techniques to engineer these systems lack support in their specific and systematic treatment. In this paper, a Model-Driven Engineering (MDE) method for the design of AmI systems is introduced to deal with NFRs paying special attention to those particularly related to the features of these kind of systems, namely, unobtrusiveness, context-awareness, and self-adaptativeness. The aim is to enable the semi-automatic derivation of quality software design models from an NFRs specification of the system, with special focus on agent-oriented architectures. To this end, Computation Independent Models (CIM) and transformation techniques between them are defined, as well as an evaluation procedure to be applied, which can help developers to make successful solution decisions satisficing the overall quality properties required for AmI systems, and also specific ones for each particular system. The proposal is illustrated by means of a case study of an Ambient Assisted Living (AAL) system for elderly people.

Welcome to the DATE 08 Conference Proceedings. DATE combines the world's favourite electronic systems design conference and Europe's leading international exhibition for electronic design, automation and test, from system level hardware and software implementation right down to integrated circuit design. The DATE 08 event features a technical program with 77 sessions covering the latest developments in system design and embedded software, IC design/test methodologies and EDA tools, together with an exhibition with the leading EDA, silicon and IP providers showing their new products and services. Challenges that you all face or soon will face in your daily practice are the increasing design complexity of highly integrated systems, the introduction of reconfigurability and embedded software, and the control of power and variability in nanometer IC designs. All these issues will be addressed in this year's DATE event. For the 11th successive year DATE has prepared an exciting technical programme, with the help of the more than 400 members of the Technical Programme Committee, who dedicated their time to thoroughly review the 839 submissions in 37 topics, ranging from system level down to circuit design and covering all the most relevant application domains. The submissions are organised in 4 major areas: D --- Design Methods, Tools, Algorithms and Languages A --- Application Design T --- Test Methods, Tools and Innovative Experiences E --- Embedded Software After a thorough review and selection process (with an average of 5 reviews per paper), finally 198 regular papers were selected for presentation at the conference. Additionally, there are 46 Interactive Presentations that are organised in 5 IP sessions. Together with the invited special sessions (panels, embedded tutorials and hot topic sessions), this has resulted in a high-quality technical program. The technical program provides a wide but high-quality coverage of design, design automation and test topics, from the system level to the integrated circuit level. Compared with previous years, submissions in the Embedded Software track has increased by 50%, showing a clear trend towards a comprehensive system design focus with integrated hardware and software solutions. DATE has established itself firmly as a true Electronic System Design Conference. This year the conference is held in Germany, at the ICM in Munich and spans an entire working week from Monday March 10 to Friday March 14. On Monday, eleven pre-conference tutorials will be given. The three-full day tutorials cover topics of great interest for system design. The first tutorial deals with techniques to automatically realising embedded system from high-level functional models. The second tutorial addresses the different issues related to communication based design and architectures in automotive electronic systems. The third tutorial discusses several key concepts on system-level design and application mapping for wireless and multimedia MPSoC architectures. Furthermore, eight half-day tutorials are also given, which cover a wide spectrum of topics on specification, modelling, design and test. The main conference opens on Tuesday March 11, with two very interesting and complementary keynote speeches. Dominique Vernay, Chief Technical Officer for Thales, will talk about the challenges of embedded systems design, and Giovanni de Micheli, Professor at EPFL, will present his views on designing micro/nano systems for a safer and healthier tomorrow. On the same day, the Executive Track offers a series of business panels with executives discussing hot topics in design: the perils of 45 nanometers, the changes in EDA strategies from IDM, to fablite to fabless, and embedded systems level design strategies. DATE 08 will again offer two specific days related to special themes. On Wednesday March 12, a special full-day track is devoted to Automotive Electronics---Software and Architecture. This special-day track will focus on the challenges faced by the automotive supply chain with particular attention to system and software architecture design. It provides a comprehensive analysis of the evolution of automotive architectures, including ECUs, sensors and communication standards and discusses how new methods, tools and standards for interoperability and component-based design can deal with the increasing complexity of software systems and their need for reliability and guaranteed timely behaviour. In addition, it addresses to what degree existing standards, including AUTOSAR and FLEXRAY and model-based development, can support the development of safety and time-critical software. On Thursday March 13, a second special full-day track focuses on Dependable Embedded Systems. This track will address both conceptual and applied issues for design, analysis and validation of dependable embedded systems. The utility of embedded systems and services is based, in large part, on our depending on their sustained functionality in spite of the encountered operational or malicious disruptions. As the number of transient and also permanent disruptions (given the decreasing device geometries, higher device density, lower voltage latching, faster clocks etc) is expected to increase substantially, this will not only be a key issue for the hardware community but also the systems community in general. Solutions using a combination of hardware and software might be more effective than hardware-only or software-only solutions. This track focuses on both conceptual and applied issues for design, analysis and validation of dependable embedded systems. Besides these special tracks, the main conference is organized in six parallel tracks of sessions, three devoted to design methods, tools, algorithms and languages, one to application design, one to test methods, tools and innovative experiences, and finally one to embedded software. The presentations of the selected regular papers in these parallel tracks are complemented by nine Special Sessions and two Invited Industrial Sessions. The special sessions are organized in the form of panels, hot topics, and embedded tutorials. The topics to be covered include quantitative evaluation for embedded systems design, design and manufacturing at 32 and 22nm, software for wireless networked embedded systems, test challenges for low power devices, quantitative productivity measurement in IC design, and 3D Integration. The two invited industrial sessions deal with industrial system designs in transportation and information technologies. To emphasise that DATE is the major event for the designers, DATE 08 features also invited sessions where Europe's famous consumer industry presents their best designs and design practices. Friday March 14 is the day for the DATE workshops. DATE 08 offers workshops on current and emerging important issues in design, test, EDA and software to complement the regular conference. They provide a unique opportunity for the various research and design communities to spend a day discussing the latest and the best, sharing their experiences and visions. This year's workshop program includes eight workshop themes. Four workshops are related to software engineering, ranging from dependable software to modelling, analysis and development tools. Four other workshop themes cover a variety of topics such as the impact of process variations on design and test, the merging world of Nano-Electro-Mechanical Systems, new directions in high level synthesis, and heterogeneous reconfigurable hardware. Each workshop features presentations, invited or submitted, from highly distinguished academic and industrial researchers. Finally, throughout the conference days, DATE offers a comprehensive overview of commercial design and verification tools in its large exhibition hall. Exhibitors include EDA vendors, silicon, FPGA and IP providers showing their new products and services. In addition, there is an Exhibition Theatre featuring talks from engineering managers of the leading electronic manufacturers on first-hand design experiences of commercial EDA tools. New this year is the European projects village where different European and large government funded projects will be able to show their ongoing research and results to the design community and have the opportunity for internal meetings and discussions. The DATE week will be also an opportunity for students and universities to show their research work, through the PhD Forum on Monday evening and the University Booth where hardware and software demonstrations will be shown by different universities on a rotation schedule. The DATE 08 event's program will be particularly attractive to industrial designers, at analog, IC, FPGA and embedded system level, as well as software designers, to researchers and academics as well as to design managers, and an increasing attendance is expected. We therefore invite you to take full advantage of the many opportunities offered to you by DATE 08, to extend your knowledge and/or business in electronic system's design and to exploit the abundant networking possibilities offered to socialise with colleagues, including fringe meetings and a memorable social party with bands and dancing. We hope that you will all enjoy the DATE 08 Conference and Exhibition.

The development of information systems is no longer limited to a few locations throughout the world. They are developed in countries whose business environment and culture are very different. Culture, we suggest, is therefore an important variable in the development process and may introduce its own set of problems, the consequences of which may range from project failure to delayed delivery of working systems. But culture’s influence may be indirect, difficult to isolate, and difficult to measure. For these reasons, perhaps, there has been no research that directly addresses culture’s role in the systems analysis and design process. This paper is an attempt to fill that void. It identifies the stages in the systems analysis and design process likely to be influenced by culture and the pattern which these influences are likely to take. The benefit of such a framework is that it draws attention to the issue of culture at the beginning of the development cycle and may reduce the chances of failure or costly delays.

Web personalization facilitate customizing a web site as per users preferences by using the various data mining techniques, taking advantage of the knowledge acquired from the analysis of the user’s navigational usage data. The web personalization reduces the searching time of the user and serves the purchasing interest of the user. In this paper, we have proposed the Analysis and design of the E-Commerce Systems. On the basis of the proposed Software specification Requirements ,for analysis of the systems, we proposed the class diagram for Preprocessing Systems, Knowledge Discovery Systems and Recommendation Subsystems and then provided workflow of the systems by proposing the required functional model of the systems. In the design of the systems we proposed the data structure design and Dynamic Web Systems architecture and implemented the systems. Lastly we have shown the results of the navigational behavior of the user during particular transaction.

Design of a quality software system is a complex and challenging task. This complexity arises due to negligence of non-functional requirements (NFRs) during development process. Model-Driven Development helps in reducing design complexity in the form of a continuous transformation of models of the desired system by providing abstraction at earlier phases of development and code generation. However, non-functional requirements which are important for building correctness in the design of the system are not adequately considered in current model driven development methods. This paper discusses the challenges in dealing non-functional requirements in model-driven development of systems and provides an approach based on architecture design decisions and technical decisions for the integration of nonfunctional properties in model-driven architecture.

Purpose: This study aims to design the flow of the e-budgeting system to develop the village financial system, as well as to increase transparency and accountability of the web-based budget system and minimize the occurrence of corruption loopholes in the village. Method: The design system uses the waterfall method to analyze a model systematically. The model development step starts with the design of the system, database, menu structure, and interface. The design of the e-budget information system is built using PHP and MySQL programming in the form of web-based applications. Results: This study developed a web-based e-budgeting application using the waterfall method to manage village finances. The online system increases flexibility, allowing access from any device. It runs smoothly on computers, with all menus functioning as designed, and is expected to simplify village financial management. Limitations: The researchers’ capability in designing the system is not optimal, as the researchers do not have the basis of informatics engineering, so the results obtained and delivered are not too detailed. Contributions: This system is expected to be useful to facilitate the process of financial management at the village government level. Novelty: The novelty of this study lies in the design of a village e-budgeting system with features like automatic Standard Unit Price calculation, automated tax management, and tracking of village income (PADes) for transparency. This application aims to enhance financial management, ensuring transparency and accountability in the village.

In the early stages of the systems engineering process, an important focus is to create an understanding of the stakeholder needs. This is primarily done to prepare the system specification that forms the basis for the system’s design. By extension, example steps in this process include surveying stakeholders to better capture their intent, deriving and documenting requirements, and then using those requirements for subsequent activities, such as developing a functional baseline and candidate design alternatives. During this process, it is important to consider the full system lifecycle. As such, one major objective of a systems engineer is to translate the stakeholder’s needs into functional and nonfunctional requirements (NFRs). Despite this important role, early system designs are often faulty because important NFRs are poorly prioritized or not prioritized at all. While the prioritization of all requirements can be useful, this work focuses specifically on NFRs. It has been identified that the inability to identify the most useful NFRs can lead to system failure. Furthermore, the lack of NFR prioritization is considered one of the most expensive and difficult errors to correct, as well as one of the ten most significant risks in engineering. Systems need more emphasis on the relationships between the system’s elements, rather than on the individual elements or the whole system. Relationships among elements in a system can illustrate more than just the behavior of each element. The illustration can include the purpose for the system and the implications of changing how the NFRs associated with those elements are prioritized. This emphasis requires quantifiable tools and rigor to inform the decision makers. This research’s objective is to contribute to quantifiable decision-making methods and prioritization of NFRs in three ways: the development of a process to determine unique random index; the use of a continuous ranking scale; and the development of a universal decision-making heuristic to accompany prioritization of NFRs.

The ‘top‐down’ system design process of functional decomposition is increasingly being criticised as simplistic, outmoded, and (in particular) too ‘reductionist’. Its use on large, complex systems is frequently portrayed as naive and impractical. There is much comment on the need to concentrate, instead, on the ‘emergent behaviours’ of systems, and to adopt a ‘holistic’ design approach in which a system solution is ‘evolved’ through a process of system design synthesis.This paper presents a counter‐argument that top‐down design decomposition can, in fact, be a highly efficient way to produce good (optimal) system solutions .Many of the fundamentals of function based system design are addressed: the central role of system function in the design process; the characterisation of system complexity and complication; the identification and specification of component requirements; and the determination of optimal design solutions.An established mathematical theory of systems design, using formal constructs and set‐theory notation, is used as the basis for the presentation of ideas.