2010
DOI: 10.1007/978-3-642-15384-6_11
|View full text |Cite
|
Sign up to set email alerts
|

Controlling Security of Software Development with Multi-agent System

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
6
0

Year Published

2012
2012
2018
2018

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 11 publications
(6 citation statements)
references
References 10 publications
0
6
0
Order By: Relevance
“…The main role of meta‐agents is to shift between strategies and make decisions. These strategies can be implemented in a single agent or in a group of agents . In the proposed work, these meta‐agents are superior to the software agents and have been used in association with fuzzy inference systems to achieve the goal of software security.…”
Section: Proposed Threatandhyphen;oriented Security Modelmentioning
confidence: 99%
See 2 more Smart Citations
“…The main role of meta‐agents is to shift between strategies and make decisions. These strategies can be implemented in a single agent or in a group of agents . In the proposed work, these meta‐agents are superior to the software agents and have been used in association with fuzzy inference systems to achieve the goal of software security.…”
Section: Proposed Threatandhyphen;oriented Security Modelmentioning
confidence: 99%
“…Research in the area of multiagent system planning for enhancing the security of the software systems was presented by Bedi et al in their approach Multi-Agent System Planning for Threat Avoidance (MASPTA) [8]. Moradian and Hakansson [23,24] introduced the approach to solving security problems in software systems using meta-agents in a multiagent environment. In 1965, Zadeh [25] proposed fuzzy set theory and later established fuzzy logic based on fuzzy sets.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…According to Moradian and Håkansson (2010), the interdependencies of software components create security issues during the integration phase of their development. Talib et al (2010) stated that the lack of a suitable guide during the CBSD life cycle leads to faults in software requirements, design, or codes and thus results in major security threats.…”
Section: Introductionmentioning
confidence: 99%
“…Several studies have reported different challenges involved in the use of CBSD. According to Moradian and Håkansson (2010), the interdependencies among software components create problems at the integration phase. Therefore, security features of software components must be considered and evaluated earlier in the CBSD lifecycle.…”
Section: Introductionmentioning
confidence: 99%