2012 IEEE International Systems Conference SysCon 2012 2012
DOI: 10.1109/syscon.2012.6189529
|View full text |Cite
|
Sign up to set email alerts
|

Engineering agile systems through architectural modularity

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
7
0

Year Published

2013
2013
2019
2019

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 12 publications
(7 citation statements)
references
References 4 publications
0
7
0
Order By: Relevance
“…Ryan et al closely links these two ilities with the distinction being that agility is flexibility that is quick rather than easy. One of the means to achieve agility is the modular design of systems so that engineers can quickly change system components to improve the performance of the system . It is also important to note that a large part of the literature focuses on agile systems engineering, which is separate from this description of an agile system .…”
Section: Framework For Applying Ilities To Resiliencymentioning
confidence: 99%
“…Ryan et al closely links these two ilities with the distinction being that agility is flexibility that is quick rather than easy. One of the means to achieve agility is the modular design of systems so that engineers can quickly change system components to improve the performance of the system . It is also important to note that a large part of the literature focuses on agile systems engineering, which is separate from this description of an agile system .…”
Section: Framework For Applying Ilities To Resiliencymentioning
confidence: 99%
“…They realized that the software development life‐cycle process would require more flexibility. To address this issue, software developers worked together to tailor a SE life‐cycle approach that would allow more flexibility throughout the life‐cycle process . This newly tailored SE approach became known as Agile SE.…”
Section: Agile Se Life‐cycle Approachmentioning
confidence: 99%
“…Most traditional systems engineers believe that a well‐documented process is repeatable and will provide positive results. Many systems engineers who follow an Agile SE approach misinterpret the principles of Agile SE as advocating for less process control and less documentation . Since the Agile SE approach emphasizes enhanced teamwork and communication, it often leads to a diminished need for documentation .…”
Section: Agile Se Life‐cycle Approachmentioning
confidence: 99%
“…Schapiro and Henry (2012) start their paper with the assertion that assets "are faced with an evolutionary operational deployment environment in which the problems the initial [design] sets out to address often evolve to areas that the […] design falls short of addressing, or misses altogether" (p.1). Changing operating conditions, one kind of change an asset may cope with during its life, give rise to a need for agile assets.…”
Section: Agile Assetsmentioning
confidence: 99%
“…by more innovative or more robust modules). Additionally, easy modification of the asset improves its adaptability (Schapiro and Henry, 2012). In the context of the adaptability of buildings, six different adaptability strategies have been discerned: 1. adjustable; 2. versatile; 3. refitable; 4. scalable; 5. convertible; and 6. movable (Schmidt III et al, 2014).…”
Section: Agile Assetsmentioning
confidence: 99%