2016 International Conference on Advances in Computing, Communications and Informatics (ICACCI) 2016
DOI: 10.1109/icacci.2016.7732377
|View full text |Cite
|
Sign up to set email alerts
|

Functional Flow Diagram(FFD): Semantics for evolving software

Abstract: In the current scenario, component-based system development approaches have led to reuse based development and espousal of large-scale software systems.To analyze the design of such systems and assess its performance is not a trivial task. Model-based testing tools have maturely signified the success of functional testing of such systems. An urge to spawn the testing of non-functional behavior from development models is further expected. Reliability assessment is one such aspect. However, the design models hav… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2017
2017
2024
2024

Publication Types

Select...
4

Relationship

1
3

Authors

Journals

citations
Cited by 4 publications
(4 citation statements)
references
References 20 publications
0
4
0
Order By: Relevance
“…For example, because of the practical constraint that formal requirements are not always available before FD, the process may be applied in parallel with defining requirements [4]. When nonfunctional aspects of a system must be evaluated, FD can be applied by extending the semantics of UML [6]. Within shared and multi‐tenant cloud application environments, FD can be applied with the intent to independently analyze, design, develop, and maintain multiple business processes [8].…”
Section: Afdmentioning
confidence: 99%
“…For example, because of the practical constraint that formal requirements are not always available before FD, the process may be applied in parallel with defining requirements [4]. When nonfunctional aspects of a system must be evaluated, FD can be applied by extending the semantics of UML [6]. Within shared and multi‐tenant cloud application environments, FD can be applied with the intent to independently analyze, design, develop, and maintain multiple business processes [8].…”
Section: Afdmentioning
confidence: 99%
“…Shopping The previous works on synthesis of FFBD [25,26] is inspired from use case diagram, component diagram or sequence diagram. The activity diagram is another approach to defining flow in the system.…”
Section: Figure 6: Functional Flow Block Diagram For Onlinementioning
confidence: 99%
“…Also, the familiarity with UML makes it understandable and easy to adopt for complex communicating code modules. In continuation of our past work [25,26] that introduced FFBDs in system analysis, we investigated various formal techniques and found FFBRD as defined in this paper with semantics of UML for visualization, prediction and estimation processes.…”
Section: Introductionmentioning
confidence: 99%
“…Task-oriented approaches represent the flows of functions through the system with respect to causality in the chain sequence, focusing on structure-independent description of what needs to be achieved. The functional flow block diagram (NASA, 2007; Chourey & Sharma, 2016) provides a network structure of functions of the system in a sequential relationship that leads to the achievement of overall system function. The functional flow block diagram is well supported by tools, for example, the SysML activity diagram (Friedenthal et al, 2008).…”
Section: Function Modeling Backgroundmentioning
confidence: 99%