scholarly journals EVALUATION OF CAPTURING ARCHITECTURALLY SIGNIFICANT REQUIREMENTS

2017 ◽  
Vol 10 (13) ◽  
pp. 122
Author(s):  
B Sathis Kumar

Every software development organization strives for customer satisfaction. It is universally accepted that the success of software development lies in the clear understanding of the client requirements. During requirement elicitation and analysis stage, the system analyst identifies the functional and non-functional requirements from the customer. Security, usability, reliability, performance, scalability and supportability are the significant quality attributes of a software system. These quality attributes are also referred as non-functional requirements. Only a few functional and quality attributes requirement help to identify and shape the software architecture. A software system’s architecture is the set of prime design decisions made about the system. If the requirement influences the architectural design decision then, it is referred as Architecturally Significant Requirement (ASR). Identifying and specifying all the possible ASR are important tasks in the requirement elicitation and analysis stage.In this research, general problems that are faced while capturing and specifying ASR in requirement elicitation and analysis is studied. Among the different requirement elicitation techniques, use case diagram has been identified and enhanced to solve the problem of capturing and specifying ASR during the requirement elicitation and analysis phase 

2015 ◽  
Vol 25 (09n10) ◽  
pp. 1677-1692 ◽  
Author(s):  
Meiru Che ◽  
Dewayne E. Perry ◽  
Guowei Yang

Global software development (GSD) is considered as the coordinated activities of software development that are geographically and temporally distributed. The management of architectural knowledge, specifically, architectural design decisions (ADDs), becomes important in GSD due to the geographical, temporal, and cultural challenges in global environments. Based on our previous work on ADD management in localized software development, we present five ADD paradigms for GSD projects with different organizational structures. We also investigate the benefits and the challenges of these ADD paradigms by conducting an evaluation of the paradigms using extensive archived semi-structured interview data from industrial GSD projects. We aim to provide a fundamental framework for managing ADD documentation and evolution in GSD, as well as offer useful insights into managing architectural knowledge in a global setting.


Author(s):  
Ibrahim Mohammad Ba’abbad ◽  
M. Rizwan Jameel Qureshi

The quality of a product is one of the major interests of the manufacturing process in all industries. The software industry imposes to construct a project with several phases to ensure producing high-quality software. A software development company estimates time, effort and cost of the project during planning phase. It is important to have accurate estimations to reduce the risks of project failure. Several cost estimation methods are practiced in the software development companies such as Function Point (FP), Use Case Points (UCP), Constructive Cost Model I and II and Story Points (SP). UCP cost estimation method is taken in this research to improve the accuracy of its estimation. UCP estimation depends on the use case diagram of the proposed system. A use case diagram describes the main functional requirements of the proposed system. UCP partially considers non-functional requirements through the technical and environmental factors. There is a lacking in the UCP method to consider the importance of quality attributes in the estimating process. This paper proposes an extended version of the existing UCP method named Quality Extended Use Case Point (QUCP) method in which quality attributes are included to improve the accuracy of cost estimation. A questionnaire is used to validate the proposed QUCP method. It is found after data analysis that seventy five percentages of the participants are agreed that the proposed method will not only help to improve the accuracy of cost estimation but it will also enable a software development company to deliver high-quality products.


Author(s):  
HONGYU ZHANG ◽  
STAN JARZABEK

In software architecture design, we explore design alternatives and make decisions about adoption or rejection of a design from a web of complex and often uncertain information. Different architectural design decisions may lead to systems that satisfy the same set of functional requirements but differ in certain quality attributes. In this paper, we propose a Bayesian Network based approach to rational architectural design. Our Bayesian Network helps software architects record and make design decisions. We can perform both qualitative and quantitative analysis over the Bayesian Network to understand how the design decisions influence system quality attributes, and to reason about rational design decisions. We use the KWIC (Key Word In Context) example to illustrate the principles of our approach.


Author(s):  
Santirak Prasertsuk ◽  
Patana Rattananavathong

This research presents the architectural research-design process of learning spaces that utilized performance-based design techniques. It is the exploration of creating new learning and research environments on the rooftop of the Faculty of Architecture and Planning building. It consists of a co-research lab for faculty members, active-learning classrooms, and semi-outdoor community spaces. To achieve the design goals, the research process consists of surveys of functional requirements from the users, student participation in a design competition, building’s structure inspection, development of performance-based architectural design, and construction document preparation. The whole building energy and computational fluid dynamics (CFD) simulations were used to simulate microclimate maps and conditions that used to informed design-decision making. The final design proposes a new architectural expression in contrast to the monotony of horizontal elements of the existing building. A sustainable design approach as a response to the tropical climate of Thailand, as the human comfort, is generally achieved through HVAC system. The south-facing facade is equipped with vertical sunshades, some are automatically adjustable to optimize the daylight efficiency, corresponding to the daily sun’s movement. The solar panels are installed on the roofs to supply electricity and to reduce carbon emissions. Due to the site’s very strict regulatory issues and budget, the steel structural system and dry-wall construction are selected to reduce additional dead-loaded weight and limited construction time.


Author(s):  
S. A. Golovin ◽  
S. V. Zykov ◽  
Yu. P. Korablin ◽  
D. A. Kryukov

In most software engineering approaches, software design begins with defining functional requirements, which is well suited to web-based software development projects. When designing high-critical large-scale software intended for industrial use, accounting for non-functional software requirements is also required. The main idea of the proposed document-oriented approach is to design a stable architectural solution as early as possible, taking into account the nonfunctional characteristics of the software: reliability, security, maintainability and performance (quality attributes). At the same time, the key issue is the coordination of functional requirements, taking into account technical limitations and business requirements achieved during the steady interaction of customer and developer teams. To increase the flexibility of the designed solutions and prevent crisis situations when developing highly critical large-scale software, it is proposed to use the approach integrating the architecture-centric design method (ACDM), the architecture-tradeoff analysis method (ATAM) with a matrix enterprise architecture matrix (EAM). This allows getting a result that is adequate to the required level of responsibility and reliability. Consideration of quality attributes within the framework of the method of compromise analysis makes it possible to select and make certain decisions in software design taking into account the scale of the software and its scope. The main attributes of product quality are highlighted (ISO 25010 standard), critical scenarios are defined for each of them (templates and use cases). The use of these templates for detailed software design with the necessary parameters of functional requirements, business conditions and technological limitations reduces the risk of developing unpredictable and uncertain system behavior. Based on the proposed approach, an architectural solution is presented for highly critical, responsible, large-scale software for managing autonomous robotic open-pit mining of minerals. Critical attributes for creating the specified software were identified and ranked, and the architecture of the solution according to the SWEBOK software development standard was described. Further, taking into account the nature, scale and scope of the software solution, recommendations are given on high-level architectural templates for the system design, including layers, pipelines and microservices. The proposed architecture-oriented development method is suitable for industrial-level software in various subject areas.


2020 ◽  
Vol 49 (2) ◽  
pp. 206-223
Author(s):  
Mario Dudjak ◽  
Goran Martinović

Over the last several years, cloud computing has imposed as a major paradigm in software development by providing computer resources over the Internet. Among various cloud service models, Backend as a Service (BaaS) stands out as a model that targets the specific needs of web and mobile developers. By providing the backend for applications, it facilitates and expedites the software development process. In order to prevent major problems with the use of third-party BaaS providers, this paper advocates building your own BaaS platform, as well as several works ahead of it. However, the development of a BaaS platform carries various challenges regarding architecture and design. This paper strives to define the core service offerings of a BaaS platform and propose a method for providing an architectural design of a BaaS platform based on a microservice architecture. Microservice architecture is the preferred architectural style for cloud solutions since it promotes loose coupling, ease of scaling and integration with third-party services, which are fundamental stipulations of BaaS platforms. The methodology adopted in designing a microservice-based BaaS platform was formed in accordance with an Application Programming Interface (API)-first approach, which strives to design a suitable, representative API of the platform. To the best of authors’ knowledge, this paper proposes the lowest-level design of a BaaS platform so far, describing the entity relations, integration patterns, and communication styles. Ultimately, the proposed design was implemented and tested for its functional requirements. In that regard, specific test cases that mirror the actual workflow of the BaaS platform were constructed.


2019 ◽  
Vol 8 (2S11) ◽  
pp. 2129-2132

Non-Functional requirements elicitation is one of the most important activity in requirements engineering. Non-functional requirements define the quality attributes of software system. If this analysis is not done properly, it may cause for problems in further phases that in turn may lead to failure of the software. Hence the non-functional requirements analysis has to be given at most priority in software development. This paper presents survey on different approaches proposed for Non-Functional requirements analysis


Buildings ◽  
2021 ◽  
Vol 11 (2) ◽  
pp. 59
Author(s):  
Abraham Yezioro ◽  
Isaac Guedi Capeluto

Improving the energy efficiency of existing and new buildings is an important step towards achieving more sustainable environments. There are various methods for grading buildings that are required according to regulations in different places for green building certification. However, in new buildings, these rating systems are usually implemented at late design stages due to their complexity and lack of integration in the architectural design process, thus limiting the available options for improving their performance. In this paper, the model ENERGYui used for design and rating buildings in Israel is presented. One of its main advantages is that it can be used at any design stage, including the early ones. It requires information that is available at each stage only, as the additional necessary information is supplemented by the model. In this way, architects can design buildings in a way where they are aware of each design decision and its impact on their energy performance, while testing different design directions. ENERGYui rates the energy performance of each basic unit, as well as the entire building. The use of the model is demonstrated in two different scenarios: an office building in which basic architectural features such as form and orientation are tested from the very beginning, and a residential building in which the intervention focuses on its envelope, highlighting the possibilities of improving their design during the whole design process.


Sign in / Sign up

Export Citation Format

Share Document