Log in

Relevant bibliographies by topics / Formal requirements / Journal articles

To see the other types of publications on this topic, follow the link: Formal requirements.

Journal articles on the topic 'Formal requirements'

Author: Grafiati

Published: 4 June 2021

Last updated: 25 April 2022

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the top 50 journal articles for your research on the topic 'Formal requirements.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Browse journal articles on a wide variety of disciplines and organise your bibliography correctly.

1

Gebreyohannes, Solomon, William Edmonson, and Albert Esterline. "Formal Behavioral Requirements Management." IEEE Systems Journal 12, no. 3 (September 2018): 3006–17. http://dx.doi.org/10.1109/jsyst.2017.2775740.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Defossez, Francois. "A Formal Model of Requirements." Open Transportation Journal 5, no. 1 (October 6, 2011): 60–70. http://dx.doi.org/10.2174/1874447801105010060.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Paech, Barbara. "Formal user-centered requirements engineering." ACM SIGCHI Bulletin 29, no. 1 (January 1997): 54–55. http://dx.doi.org/10.1145/251761.248502.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Hussak, Walter, and John A. Keane. "Formal Analysis of Memory Requirements." Requirements Engineering 4, no. 4 (December 1, 1999): 188–97. http://dx.doi.org/10.1007/s007660050019.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

Yen, John, and W. Amos Tiao. "A Formal Methodology for Analyzing Tradeoffs of Imprecise Requirements." International Journal of Software Engineering and Knowledge Engineering 08, no. 02 (June 1998): 283–311. http://dx.doi.org/10.1142/s0218194098000157.

Full text

Abstract:

Conflict identification and resolution are inevitable parts of the requirement analysis process. Over the past few years, the need to deal with conflicting system requirements has become increasingly important. These requirements are often elastic in that they can be satisfied to a degree. The overall goal of this research is to develop a formal methodology that facilitates the identification and tradeoff analysis of conflicting requirements by explicitly capturing their elasticity. In order to capture the elasticity of imprecise requirements, we represent imprecise requirements using fuzzy logic. Based on the representation, we build a formal foundation to facilitate the identification of conflicting requirements. Once the conflicting requirements are identified, we describe a systematic approach for analyzing the tradeoff between conflicting requirements using the techniques in decision science. The systematic tradeoff analyses are used for three important tasks in the requirement engineering process: (1) for validating the structure used in aggregating prioritized requirements, (2) for assisting requirement engineers in identifying the structures and the parameters of the underlying representation of imprecise requirements and in eliciting them from the customer, and (3) for assessing the priorities of conflicting requirements. We illustrate the usage of these techniques using the requirements of a conference room scheduling system.

APA, Harvard, Vancouver, ISO, and other styles

6

Amoroso, Edward G. "Creating formal specifications from requirements documents." ACM SIGSOFT Software Engineering Notes 20, no. 1 (January 1995): 67–70. http://dx.doi.org/10.1145/225907.225915.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Johnson, W. L., K. M. Benner, and D. R. Harris. "Developing formal specifications from informal requirements." IEEE Expert 8, no. 4 (August 1993): 82–90. http://dx.doi.org/10.1109/64.223994.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Lawrence, B., and D. Jackson. "Do you really need formal requirements?" IEEE Software 13, no. 2 (March 1996): 20. http://dx.doi.org/10.1109/52.506459.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Kampfner, Roberto R. "Formal specification of information systems requirements." Information Processing & Management 21, no. 5 (1985): 401–14. http://dx.doi.org/10.1016/0306-4573(85)90086-x.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

Liu, Xiao Jian, Zhi Xue Wang, Xu Qin Yan, Yang Li, and Jian Xin Li. "Formal Modeling of Automotive Software Requirements by Correctness." Applied Mechanics and Materials 40-41 (November 2010): 961–67. http://dx.doi.org/10.4028/www.scientific.net/amm.40-41.961.

Full text

Abstract:

Correctly modeling software requirements is one of the grand challenges of current ECU (Electronic control Unit) development. To ensure the correctness of the requirements, formal modeling techniques are usually used because they allow analyzers to simulate, verify and even conduct performance analysis in the requirement level. In this paper, we propose a requirements modeling framework, based on the philosophy of separation of concerns and the formal modeling techniques. The main contributions of this paper are two-fold: (1) We divide a complicated automotive software as several concerns, each of which is modeled by different formal techniques, thus the descriptive complexity of the requirements is decreased, and accordingly the models’ understandability is enhanced; (2) The adoption of formal techniques allows us to simulate the execution of the software and calculate the performance in the early stage of development, therefore the correctness of requirements can be improved.

APA, Harvard, Vancouver, ISO, and other styles

11

Kusiak, A., and E. Szczerbicki. "A Formal Approach to Specifications in Conceptual Design." Journal of Mechanical Design 114, no. 4 (December 1, 1992): 659–66. http://dx.doi.org/10.1115/1.2917057.

Full text

Abstract:

In this paper, a methodology for the specification stage in conceptual design is presented. The specification stage provides requirements and transforms them into functions of the designed object. It occurs at the highest level of abstraction and it must provide enough information for the synthesis process where functions are transformed into design components that are further synthesized into the designed object. The proposed approach includes the following issues: specification of requirements, specification of functions, incorporation of logic into functional and requirement trees, representation of requirements-functions interaction, and optimization in the functional space. The methodology presented is illustrated with examples. Key words: design requirements, design specifications, conceptual design, design process, artificial intelligence, formal method

APA, Harvard, Vancouver, ISO, and other styles

12

Wang, Taehyung, Astushi Kitazawa, and Phillip Sheu. "Semantic software engineering." Encyclopedia with Semantic Computing and Robotic Intelligence 01, no. 01 (March 2017): 1630012. http://dx.doi.org/10.1142/s2425038416300123.

Full text

Abstract:

One of the most challenging task in software development is developing software requirements. There are two types of software requirements — user requirement (mostly described by natural language) and system requirements (also called as system specifications and described by formal or semi-formal methods). Therefore, there is a gap between these two types of requirements because of inherently unique features between natural language and formal or semi-formal methods. We describe a semantic software engineering methodology using the design principles of SemanticObjects for object-relational software development with an example. We also survey other semantic approaches and methods for software and Web application development.

APA, Harvard, Vancouver, ISO, and other styles

13

Akinboade, Oludele Akinloye, Anrich Daseman, Trevor Taft, and Victor M. S. Molobi. "Regulation, Cross Border Migrants and the Choice of Remittance Channels in South Africa." Journal of Economics and Behavioral Studies 9, no. 2(J) (May 18, 2017): 201–14. http://dx.doi.org/10.22610/jebs.v9i2(j).1661.

Full text

Abstract:

Remittances have become an increasingly important factor in developing economies. Among others, compliance with onerous regulation requirements discourages the use of formal methods of remittances. The paper discusses results from a survey of the influence of regulation on the choice of migrantsâ€™ remittance channels in South Africa. It aims to highlight how regulation affects the choice between formal and informal channels of remitting funds. A questionnaire was administered to collect primary data from migrants seeking documentations from the Department of Home Affairs, those remitting funds at taxi ranks or bus terminals, and those remitting through commercial banks and money transfer operators. 275 responses were analysed using a Likert rating scale format of 1 (highest) to 5 (lowest). Regulatory requirements of documentary evidence are an important factor influencing the choice of the remittance channel used. Documentation requirement in the formal market causes migrants to be ineligible for the formal channels of remittances and is a factor that influences the choice of remittance channel. Restrictive visa requirements could easily push migrants to become illegal aliens which further deny them access to formal remittance channels. The paper adds to the academic literature on the determinants of remittance channels in Africa. Understanding the relevant issues could assist regulatory authorities to restructure the remittance market with a view to encouraging migrant workers to enter the formal financial system.

APA, Harvard, Vancouver, ISO, and other styles

14

Akinboade, Oludele Akinloye, Anrich Daseman, Trevor Taft, and Victor M. S. Molobi. "Regulation, Cross Border Migrants and the Choice of Remittance Channels in South Africa." Journal of Economics and Behavioral Studies 9, no. 2 (May 18, 2017): 201. http://dx.doi.org/10.22610/jebs.v9i2.1661.

Full text

Abstract:

Remittances have become an increasingly important factor in developing economies. Among others, compliance with onerous regulation requirements discourages the use of formal methods of remittances. The paper discusses results from a survey of the influence of regulation on the choice of migrants’ remittance channels in South Africa. It aims to highlight how regulation affects the choice between formal and informal channels of remitting funds. A questionnaire was administered to collect primary data from migrants seeking documentations from the Department of Home Affairs, those remitting funds at taxi ranks or bus terminals, and those remitting through commercial banks and money transfer operators. 275 responses were analysed using a Likert rating scale format of 1 (highest) to 5 (lowest). Regulatory requirements of documentary evidence are an important factor influencing the choice of the remittance channel used. Documentation requirement in the formal market causes migrants to be ineligible for the formal channels of remittances and is a factor that influences the choice of remittance channel. Restrictive visa requirements could easily push migrants to become illegal aliens which further deny them access to formal remittance channels. The paper adds to the academic literature on the determinants of remittance channels in Africa. Understanding the relevant issues could assist regulatory authorities to restructure the remittance market with a view to encouraging migrant workers to enter the formal financial system.

APA, Harvard, Vancouver, ISO, and other styles

15

K.Pandey, S., and Mona Batra. "Formal Methods in Requirements Phase of SDLC." International Journal of Computer Applications 70, no. 13 (May 17, 2013): 7–14. http://dx.doi.org/10.5120/12020-8017.

Full text

APA, Harvard, Vancouver, ISO, and other styles

16

Hagemann, M. "Formal requirements specification of process control systems." ACM SIGSOFT Software Engineering Notes 12, no. 4 (October 1987): 36–42. http://dx.doi.org/10.1145/37537.37543.

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

Yang, Yilong, Xiaoshan Li, Wei Ke, and Zhiming Liu. "Automated Prototype Generation From Formal Requirements Model." IEEE Transactions on Reliability 69, no. 2 (June 2020): 632–56. http://dx.doi.org/10.1109/tr.2019.2934348.

Full text

APA, Harvard, Vancouver, ISO, and other styles

18

Penneman, Niels, Danielius Kudinskas, Alasdair Rawsthorne, Bjorn De Sutter, and Koen De Bosschere. "Formal virtualization requirements for the ARM architecture." Journal of Systems Architecture 59, no. 3 (March 2013): 144–54. http://dx.doi.org/10.1016/j.sysarc.2013.02.003.

Full text

APA, Harvard, Vancouver, ISO, and other styles

19

Syverson, Paul, and Catherine Meadows. "A formal language for cryptographic protocol requirements." Designs, Codes and Cryptography 7, no. 1-2 (January 1996): 27–59. http://dx.doi.org/10.1007/bf00125075.

Full text

APA, Harvard, Vancouver, ISO, and other styles

20

Roman, G. C. "Formal specification of geographic data processing requirements." IEEE Transactions on Knowledge and Data Engineering 2, no. 4 (1990): 370–80. http://dx.doi.org/10.1109/69.63249.

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

YEN, JOHN, and XIAOQING FRANK LIU. "A FORMAL APPROACH TO THE ANALYSIS OF PRIORITIES OF IMPRECISE CONFLICTING REQUIREMENTS." International Journal on Artificial Intelligence Tools 05, no. 01n02 (June 1996): 185–97. http://dx.doi.org/10.1142/s0218213096000134.

Full text

Abstract:

Priority analysis is one of the most important issues in the trade-off analysis of imprecise conflicting requirements whose elasticity is captured using fuzzy logic. Requirement analysts need to know not only the relative ordering of requirements based on their importance but also how much a requirement is more important than another requirement in order to achieve an effective trade-off. This paper presents a formal approach for reasoning about the relative priority by analyzing the customer’s trade-off preference among imprecise conflicting requirements. A possibilistic reasoning framework for inferring the lower bound of relative priority from case analysis under uncertainty is also developed. Consistency and nonredundancy criteria are established to facilitate the conversion of a possibilistic statement on a lower bound of relative priority into a relative priority. Finally, relative priorities are transformed into weights of importance so that they can be used in the aggregation of conflicting requirements to resolve conflicts.

APA, Harvard, Vancouver, ISO, and other styles

22

Drusinsky, Doron. "Computer-aided discovery of formal specification behavioral requirements and requirement to implementation mappings." Innovations in Systems and Software Engineering 10, no. 4 (June 25, 2014): 271–81. http://dx.doi.org/10.1007/s11334-014-0235-1.

Full text

APA, Harvard, Vancouver, ISO, and other styles

23

YEN, JOHN, and XIAOQING LIU. "APPROXIMATE REASONING ABOUT PRIORITIES OF IMPRECISE CONFLICTING REQUIREMENTS." International Journal of Uncertainty, Fuzziness and Knowledge-Based Systems 03, no. 02 (June 1995): 143–62. http://dx.doi.org/10.1142/s0218488595000128.

Full text

Abstract:

Elasticity in an imprecise requirement needs to be captured to enable the trade-off analysis of conflicting requirements. One of the most important issues in the trade-off analysis of conflicting requirements is to understand their priorities. Requirement analysts need to know not only the relative ordering of requirements based on their importance but also how much a requirement is more important than another requirement in order to achieve an effective trade-off between conflicting requirements. Existing formal methods for requirement engineering are limited in addressing these issues. This paper presents a formal methodology for reasoning about their priority by analyzing the customer’s trade-off preference among imprecise conflicting requirements. The elasticity in imprecise requirements is captured using fuzzy logic. Conflicting and cooperative relationships are classified to detect the conflicts between requirements. Multiple requirements are combined based fuzzy multi-criteria decision making techniques. We have also developed a possibilistic reasoning framework for inferring the lower bound of relative priority from case analysis. Consistency and nonredundancy criteria are established to facilitate the aggregation of possibilistic statement on the lower bounds of relative priority. Finally, we describe a process for transforming the lower bounds of relative priority into weights of importance so that they can be used in the aggregation of conflicting requirements to resolve conflicts.

APA, Harvard, Vancouver, ISO, and other styles

24

Ciaccia, P., P. Ciancarini, and W. Penzo. "Formal Requirements and Design Specifications: The Clepsydra Methodology." International Journal of Software Engineering and Knowledge Engineering 07, no. 01 (March 1997): 1–42. http://dx.doi.org/10.1142/s0218194097000023.

Full text

Abstract:

The use of formal methods early in the development process has been advocated as a way of improving the quality of software products and their production process. Here we study the influence of a formal requirements document on the next phase in the software process, that is design. We suggest that formal design should coherently follow from formal requirements. We show that two different formal notations can be effectively used, one for writing requirements specification and one for design specification. We also consider how a design specification can be formally checked with respect to requirements specification. The notations we choose are well known: the Z notation for requirements and the Larch two-tiered language for design. We show how a number of tools based on these notations can be used to improve the quality of the documents produced during the development process.

APA, Harvard, Vancouver, ISO, and other styles

25

TKADLEC, JOSEF, and IVAN BRUHA. "FORMAL ASPECTS OF A MULTIPLE-RULE CLASSIFIER." International Journal of Pattern Recognition and Artificial Intelligence 17, no. 04 (June 2003): 581–600. http://dx.doi.org/10.1142/s021800140300254x.

Full text

Abstract:

This paper deals with the multiple-rule problem which arises when several decision rules (of different classes) match ("fire" for) an input to-be-classified (unseen) object. The paper focuses on formal aspects and theoretical methodology for the above problem. The general definitions of the notions of a Designer, Learner and Classifier are presented in a formal matter, including parameters that are usually attached to the above concepts such as rule consistency, completeness, quality, matching rate, etc. We thus provide the minimum-requirement definitions as necessary conditions for these concepts. Any designer (decision-system builder) of a new multiple-rule system may start with these minimum requirements. We only expect that the Classifier makes its decisions according to its decision scheme induced as a knowledge base (theory, model, concept description). Also, two case studies are discussed. We conclude with a general flow chart for a decision-system builder. He/she can just pursue it and select parameters of a Learner and Classifier, following the minimum requirements provided.

APA, Harvard, Vancouver, ISO, and other styles

26

Winship, Peter. "Harmonizing formal requirements for cross-border sales contracts." International Review of Law 2012, no. 1 (April 2012): 6. http://dx.doi.org/10.5339/irl.2012.6.

Full text

APA, Harvard, Vancouver, ISO, and other styles

27

Ulferts, Gregory W., Antonio Drommi, and Daniel Shoemaker. "Embedding Security Functionality In Formal Specifications Of Requirements." Review of Business Information Systems (RBIS) 11, no. 4 (October 1, 2007): 17–26. http://dx.doi.org/10.19030/rbis.v11i4.4403.

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

Lin Zhao, and Tao Tang. "Supporting the Formal Analysis of System Requirements Model." Journal of Convergence Information Technology 8, no. 6 (March 31, 2013): 546–52. http://dx.doi.org/10.4156/jcit.vol8.issue6.65.

Full text

APA, Harvard, Vancouver, ISO, and other styles

29

Razali. "Usability Requirements of Formal Verification Tools: A Survey." Journal of Computer Science 6, no. 10 (October 1, 2010): 1189–98. http://dx.doi.org/10.3844/jcssp.2010.1189.1198.

Full text

APA, Harvard, Vancouver, ISO, and other styles

30

Jones, Sara, David Till, and Ann M. Wrightson. "Formal methods and requirements engineering: Challenges and synergies." Journal of Systems and Software 40, no. 3 (March 1998): 263–73. http://dx.doi.org/10.1016/s0164-1212(97)00171-4.

Full text

APA, Harvard, Vancouver, ISO, and other styles

31

Kamsu-Foguem, B., and V. Chapurlat. "Requirements modelling and formal analysis using graph operations." International Journal of Production Research 44, no. 17 (September 2006): 3451–70. http://dx.doi.org/10.1080/00207540500499377.

Full text

APA, Harvard, Vancouver, ISO, and other styles

32

LaPlue, Larry, Ruth A. Garcia, and Robert Rhodes. "4.1.3 A RIGOROUS METHOD FOR FORMAL REQUIREMENTS DEFINITION." INCOSE International Symposium 5, no. 1 (July 1995): 429–34. http://dx.doi.org/10.1002/j.2334-5837.1995.tb01893.x.

Full text

APA, Harvard, Vancouver, ISO, and other styles

33

Dutertre, B., and V. Stavridou. "Formal requirements analysis of an avionics control system." IEEE Transactions on Software Engineering 23, no. 5 (May 1997): 267–78. http://dx.doi.org/10.1109/32.588520.

Full text

APA, Harvard, Vancouver, ISO, and other styles

34

Easterbrook, S., R. Lutz, R. Covington, J. Kelly, Y. Ampo, and D. Hamilton. "Experiences using lightweight formal methods for requirements modeling." IEEE Transactions on Software Engineering 24, no. 1 (1998): 4–14. http://dx.doi.org/10.1109/32.663994.

Full text

APA, Harvard, Vancouver, ISO, and other styles

35

Wagner, Lucas. "Formal Specification and Analysis of Requirements using SpeAR." ACM SIGAda Ada Letters 39, no. 1 (January 10, 2020): 20–34. http://dx.doi.org/10.1145/3379106.3379110.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Darimont, Robert, and Axel van Lamsweerde. "Formal refinement patterns for goal-driven requirements elaboration." ACM SIGSOFT Software Engineering Notes 21, no. 6 (November 1996): 179–90. http://dx.doi.org/10.1145/250707.239131.

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

Aichernig, B. K., and J. Horl. "Validating voice communication requirements using lightweight formal methods." IEEE Software 17, no. 3 (2000): 21–27. http://dx.doi.org/10.1109/52.896246.

Full text

APA, Harvard, Vancouver, ISO, and other styles

38

Barlas, Konstantinos, Eleni Berki, Petros Stefaneas, and George Koletsos. "Towards formal open standards: formalizing a standard’s requirements." Innovations in Systems and Software Engineering 13, no. 1 (July 1, 2016): 51–66. http://dx.doi.org/10.1007/s11334-016-0283-9.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

Smith, S. R. "Constructing and revising formal arguments in requirements engineering." Requirements Engineering 2, no. 4 (December 1997): 199–216. http://dx.doi.org/10.1007/bf02745372.

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

Weston, Nathan, Ruzanna Chitchyan, and Awais Rashid. "Formal semantic conflict detection in aspect-oriented requirements." Requirements Engineering 14, no. 4 (June 3, 2009): 247–68. http://dx.doi.org/10.1007/s00766-009-0083-y.

Full text

APA, Harvard, Vancouver, ISO, and other styles

41

Krystek, Jacek. "Formal requirements for authors of project information cards." Acta Iuris Stetinensis 34 (2021): 49–58. http://dx.doi.org/10.18276/ais.2021.34-03.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

Mankowski, Peter. "Information and Formal Requirements in EC Private Law." European Review of Private Law 13, Issue 6 (December 1, 2005): 779–96. http://dx.doi.org/10.54648/erpl2005049.

Full text

Abstract:

Modern Community law utilises duties to inform as instruments of consumer protection to a great extent. Rather often such duties appear as formal requirements the spectre of which is not all too wide. The business has to guarantee that the information is provided in documented form in order to overcome informational asymmetry. Furthermore, a specific array of sanctions for non-compliance has developed in the legal orders of the Member States. The sanctions traditionally stemming from non-compliance with formal requirements do not apply regularly whereas novel sanctions prevail which mainly instrumentalize the time limit applicable to the consumer?s right of withdrawal. Additionally, damages or alterations the burden of proof could become material.

APA, Harvard, Vancouver, ISO, and other styles

43

SAHRAOUI, ABD-EL-KADER. "REQUIREMENTS TRACEABILITY ISSUES: GENERIC MODEL, METHODOLOGY AND FORMAL BASIS." International Journal of Information Technology & Decision Making 04, no. 01 (March 2005): 59–80. http://dx.doi.org/10.1142/s0219622005001386.

Full text

Abstract:

This paper focuses on the traceability issue as key element in systems design and management of system. The work is presented through the system engineering framework with a main emphasis on requirements process. Effectively in decision making, the need for traceability model is often required in order to find out the link for a considered decision and often the semantics of such link. With the advent for information technology and integrating technical needs and business goal, the traceability find its essence and many models can now be easily implemented automatically. The paper is based on many experiences carried out ranging from audit to requirement evolution issues for impact analysis.

APA, Harvard, Vancouver, ISO, and other styles

44

Overmyer, Dwayne. "On situating documents." Information Design Journal 6, no. 3 (January 1, 1991): 199–209. http://dx.doi.org/10.1075/idj.6.3.02ove.

Full text

Abstract:

As a means of understanding and evaluating typographic documents as objects of design and instances of language in use, a descriptive and analytical framework is put forth. Identified as 'constructive factors' are formal characteristics of text and format, requirements of production and use, and contextual variables. The ways in which these factors might interrelate is examined briefly, and it is suggested that the most typical dynamic is that in which the stylistic requirement of idiomatically appropriate form is largely determined by a document's situational context. Typographic competency is then defined as the ability to match formal idiom to situation and to further model the idiom in response to situational specifics.

APA, Harvard, Vancouver, ISO, and other styles

45

Mishra, Aditya Dev, and K. Mustafa. "Formalization of Security Requirements-A Case Study on a Web- Based Application." Journal of Scientific Research 66, no. 02 (2022): 108–14. http://dx.doi.org/10.37398/jsr.2022.660214.

Full text

Abstract:

Security of web-based applications is one of the main concerns today. With the expanding cyberspace, utility and threats are increasing simultaneously. Like earlier, even today security is taken as an afterthought. Functional requirements override the security assurance. Therefore, different security issues such as threat, vulnerability, security breaches, etc. may arise after the deployment of web-based applications. The use of formal specifications for the security requirements while developing web-based applications is cost-effective, time-saving, and error-free. Most of the exiting models rarely deal with a formal approach. The objective of this research paper is to provide an idea about the formal specification and formal verification of web-based applications. In this paper, a novel and broad approach are proposed to specify the security requirement. The proposed approach has been verified through a case study of a web-based mobile banking application. This research paper mainly focused on the specification of security properties by considering some security requirements such as authentication, authorization, confidentiality, and integrity. These security properties are formally verified by the existing more formal tools which is an extension of the proposed work.

APA, Harvard, Vancouver, ISO, and other styles

46

Bruel, Jean-Michel, Sophie Ebersold, Florian Galinier, Manuel Mazzara, Alexandr Naumchev, and Bertrand Meyer. "The Role of Formalism in System Requirements." ACM Computing Surveys 54, no. 5 (June 2021): 1–36. http://dx.doi.org/10.1145/3448975.

Full text

Abstract:

A major determinant of the quality of software systems is the quality of their requirements, which should be both understandable and precise. Most requirements are written in natural language, which is good for understandability but lacks precision. To make requirements precise, researchers have for years advocated the use of mathematics-based notations and methods, known as “formal.” Many exist, differing in their style, scope, and applicability. The present survey discusses some of the main formal approaches and compares them to informal methods. The analysis uses a set of nine complementary criteria, such as level of abstraction, tool availability, and traceability support. It classifies the approaches into five categories based on their principal style for specifying requirements: natural-language, semi-formal, automata/graphs, mathematical, and seamless (programming-language-based). It includes examples from all of these categories, altogether 21 different approaches, including for example SysML, Relax, Eiffel, Event-B, and Alloy. The review discusses a number of open questions, including seamlessness, the role of tools and education, and how to make industrial applications benefit more from the contributions of formal approaches.

APA, Harvard, Vancouver, ISO, and other styles

47

Schraader, Derek, Louise Whittaker, and Ian McKay. "Debt financing the capital requirements of informal market traders." South African Journal of Economic and Management Sciences 13, no. 3 (September 10, 2010): 329–44. http://dx.doi.org/10.4102/sajems.v13i3.105.

Full text

Abstract:

This paper describes a case study undertaken to determine whether formal sector personal debt financing might contribute to the funding of South African informal market traders. The case study was conducted at the Natalspruit informal market in Ekhuruleni, Gauteng1. Quantitative questionnaire surveys and a financial diaries project established that market traders in the Natalspruit informal market: have capital requirements large enough to justify the use of formal sector debt financing, can generate sufficient operating profits to pay for formal sector debt financing, and would be willing to utilise formal sector debt financing if given the opportunity. However, formal sector debt financing is most relevant to those informal market traders with the skills and motivation to utilize financing provided effectively and who are willing to inject more formality into their business.

APA, Harvard, Vancouver, ISO, and other styles

48

Wang, Yu Hua, Gui Sheng Yin, and Hai Tao Zhang. "Research on Conversion Method of Ontology Based Formal Requirements Model to UML Requirements Document." Advanced Materials Research 268-270 (July 2011): 1086–91. http://dx.doi.org/10.4028/www.scientific.net/amr.268-270.1086.

Full text

Abstract:

In the process of requirements modeling based on ontology, the obtained model description is based on application ontology; which is not easy for designer to understand and cannot be converted into requirements specification documents for design. UML is actual standard for object-oriented modeling. For this issue, this paper creates the UML meta-model, and establishes mapping rules description language for application ontology to UML meta-element, which implements the generation of UML class diagrams based on rule, use case diagrams, state transition diagram models and requirements specification documents based on UML.

APA, Harvard, Vancouver, ISO, and other styles

49

Peres, Florent, Jing Yang, and Mohamed Ghazel. "A Formal Framework for the Formalization of Informal Requirements." International Journal of Soft Computing and Software Engineering 2, no. 8 (August 25, 2012): 14–27. http://dx.doi.org/10.7321/jscse.v2.n8.2.

Full text

APA, Harvard, Vancouver, ISO, and other styles

50

Babin, G., and F. Lustman. "Application of Formal Methods to Scenario-Based Requirements Engineering." International Journal of Computers and Applications 23, no. 3 (January 2001): 141–51. http://dx.doi.org/10.1080/1206212x.2001.11441645.

Full text

APA, Harvard, Vancouver, ISO, and other styles

We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!