Towards a Semantic Representation for Functional Software Requirements

2020 ◽  
Author(s):  
Riad Sonbol ◽  
Ghaida Rebdawi ◽  
Nada Ghneim
Keyword(s):  
Semantic Representation ◽  
Software Requirements ◽  
Functional Software

Verification of Non-Functional Requirements by Abstract Interpretation

2012 ◽  
pp. 22-35
Author(s):  
Agostino Cortesi ◽  
Francesco Logozzo
Keyword(s):  
Static Analysis ◽  
Abstract Interpretation ◽  
Software Requirements ◽  
Functional Requirements ◽  
Formal Approach ◽  
Space Efficiency ◽  
Source Program ◽  
Service Oriented ◽  
Abstract Domains ◽  
Functional Software

This chapter investigates a formal approach to the verification of non-functional software requirements that are crucial in Service-oriented Systems, like portability, time and space efficiency, and dependability/robustness. The key-idea is the notion of observable, i.e., an abstraction of the concrete semantics when focusing on a behavioral property of interest. By applying an abstract interpretation-based static analysis of the source program, and by a suitable choice of abstract domains, it is possible to design formal and effective tools for non-functional requirements validation.

Reusing functional software requirements in small-sized software enterprises: a model oriented to the catalog of requirements

2016 ◽  
Vol 22 (2) ◽  
pp. 275-287 ◽  
Author(s):  
C. Pacheco ◽  
I. Garcia ◽  
J. A. Calvo-Manzano ◽  
M. Arcilla
Keyword(s):  
Software Requirements ◽  
Functional Software

The Possibility of One-Size-Fits-All in ICT4D Design

2015 ◽  
Vol 7 (1) ◽  
pp. 37-57
Author(s):  
Christopher Chepken ◽  
Suzane Nabwire
Keyword(s):  
Information Management ◽  
Information Needs ◽  
Software Requirements ◽  
Management Systems ◽  
Functional Requirements ◽  
Job Seekers ◽  
Governmental Organizations ◽  
Non Governmental Organizations ◽  
Information Management Systems ◽  
Functional Software

This paper presents design experiences for two Non-Governmental organizations and one day-labour organisation working for the informal job seekers and employers—day-labour market. The authors present the three design architectures implemented for the organisations and show that, even when users are portrayed as similar in the way they work and what they do, their Information Management Systems (IMS) functional software requirements remain contextual up to the details. The authors argue that, although non-functional requirements may be the same for seemingly similar users, there is need to focus on the different functional information needs, including the ones that may seem insignificant. They noted that designers need to know more about their users beyond the “about us” information. The authors conclude that there exists no “one size fits all” IMS, even for seemingly similar organisations.

The Absence of One-Size-Fits-All in the Day Labour Organisations ICT4D Designs

2016 ◽  
pp. 308-333
Author(s):  
Christopher Chepken
Keyword(s):  
Labour Market ◽  
Information Needs ◽  
Software Requirements ◽  
Functional Requirements ◽  
Job Seekers ◽  
Governmental Organizations ◽  
Non Governmental Organizations ◽  
Information Management Systems ◽  
Functional Software ◽  
The One

This chapter covers design experiences gained by working with two Non-Governmental organizations and one day-labour organization for the informal job seekers and employers—day-labour market (DLM). The three design architectures implemented for the DLM organizations are presented. On critically discussing the designs, it is found that even when users are portrayed as similar in the way they work and the things they do, their Information Management Systems (IMS) functional software requirements remain contextual up to the details. The synthesis of the designs shows that there is need to focus on the different functional information needs, including the ones that may seem insignificant even where non-functional requirements may be the same for seemingly similar users. From this argument, it is important that information systems designers, especially for Day labour market organizations, should go deeper into their users and beyond the “about us” information to understand the unique features and requirements of each user group. In conclusion, designers should not assume that seemingly similar organizations/users can be approached from the “one size fits all” IMS perspective.

Hybridized Ranking Model for Prioritizing Functional Software Requirements

2021 ◽  
Vol 9 (4) ◽  
pp. 0-0
Keyword(s):  
Large Scale ◽  
Real Life ◽  
Software Requirements ◽  
System Failure ◽  
Relative Importance ◽  
Functional Requirements ◽  
Structured Interviews ◽  
Functional Software ◽  
Multi Stakeholder

Many difficulties exist when defining and deciding which requirements should be implemented first in an ultra-large-scale multi-stakeholder involved system. This often leads to system failure and product dissatisfaction. This paper established a suitable method supporting more precise and accurate decision-making in prioritizing requirements. We collected and analyzed a large number of software requirements in a case study, which was based on real-life practices and processes. Structured interviews and questionnaires were used to collect data from 600 stakeholders. We formulated a model based on the analyzed requirements using the CBRanking, and the MACBETH approaches. We ranked the requirements and considered the requirements' relative importance according to the stakeholders' opinions. Thus, a hybridized mathematical model was proposed for prioritizing these functional requirements and evaluated its performance for consistency and completeness. The results showed the software's best functional requirements concerning the customers' expectations.

scholarly journals Bendrosios sistemų inžinerijos vaidmuo specifikuojant verslo programinės įrangos reikalavimus

2008 ◽  
Vol 42 (43) ◽  
pp. 162-167
Author(s):  
Albertas Čaplinskas
Keyword(s):  
Systems Engineering ◽  
Software Requirements ◽  
Enterprise System ◽  
Stepwise Refinement ◽  
Business Information ◽  
Business Software ◽  
General Systems ◽  
A New Technique ◽  
Functional Software ◽  
Business Requirements

Integruotos įmonės informacinės sistemos kontekste ypač aktuali tampa programinės įrangos funkcinių ir nefunkcinių savybių atotrūkio nuo realių verslo poreikių problema. Straipsnyje išdėstytas naujas požiūris į tai, kaip, kuriant integruotas įmonių informacines sistemas, verslo reikalavimus nuleisti į programinės įrangos lygmenį. Siūloma reikalavimus visuose sistemos lygmenyse, įskaitant verslo, informacijos apdorojimo ir programinės įrangos lygmenis, formuluoti vartojant tą pačią sąvokų sistemą (ontologiją) ir visas tos sistemos sąvokas apibrėžti vadovaujantis bendrojoje sistemų inžinerijoje priimta sistemos samprata. Toks požiūris leidžia kitaip interpretuoti Zachmano metodinio karkaso struktūrinius elementus ir panaudoti šį karkasą kaip instrumentą verslo reikalavimams nuleisti į programinės įrangos lygmenį. Programinės įrangos reikalavimams gauti iš verslo reikalavimų siūloma naudoti reikalavimų lokalizavimo ir pažingsninio patikslinimo technikas*.General systems engineering and the specification of business software requirementsAlbertas Čaplinskas SummaryIn the context of enterprise engineering business and information systems allignment becomes one of the most important problems. The paper proposes a new technique for derivation software requirements from business requirements. The proposed approach suggests that all levels of enterprise system, including business, information processing and software levels, should be described using the same collection of concepts (ontology) and that these concepts should be defined using framework of general systems engineering. Such approach allows to reinterpret Zachman’s framework and use this framework as a tool to downflow requirements from business to software level. Requirements allocation and stepwise refinement techniques should be used to derive both functional and non-functional software requirements.

Sign in / Sign up

Export Citation Format

Share Document