Situational Method Engineering for Constructing Internet of Things Development Methods

Giray, Görkem; Tekinerdoğan, Bedir

doi:10.1007/978-3-319-94214-8_14

Cited by 8 publications

(4 citation statements)

References 33 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Fridgen et al [24] use SME to develop use cases for blockchain technology, including business-related tasks (e.g., cluster ideas) and artifacts (e.g., BMC). Giray and Tekinerdogan [33] use SME to construct internet of things development methods by including business-related situational factors (e.g., business regulations), tasks (e.g., develop IoT Canvas), and artifacts (e.g., IoT Canvas). However, those approaches are just conceptual models with a fixed method base and no software support that have a major focus on the construction of the development methods.…”

Section: Business Aspects In Situational Methods Engineeringmentioning

confidence: 99%

Continuous situation-specific development of business models: knowledge provision, method composition, and method enactment

et al. 2022

View full text Add to dashboard Cite

The development of new business models is essential for startups to become successful, as well as for established companies to explore new business opportunities. However, developing such business models is a continuous challenging activity where different tasks need to be performed, and business decisions need to be made. Both have to fit the constantly changeable situation in which the business model is developed to reduce the risk of developing ineffective business models with low market penetration. Therefore, a method for developing situation-specific business models is needed. As a solution, we refine the concept of situational method engineering (SME) to business model development. SME, in turn, provides means to construct situation-specific development methods out of fragments from a method repository. We develop a concept for the continuous situation-specific development of business models based on design science. The approach uses the roles of a domain expert, a method engineer, and a business developer together with a repository with method fragments for developing business models and a repository with modeling artifacts for supporting the development. Both repositories are filled by utilizing the experience of domain experts. Out of these repositories, situation-specific development methods for developing business models can be continuously composed based on the changeable situation by the method engineer and enacted by the business developer. We implement it as an open-source tool and evaluate its applicability in an industrial case study of developing a business model for a local event platform. Our results show that situation awareness supports the continuous development of business models.

show abstract

Section: Business Aspects In Situational Methods Engineeringmentioning

confidence: 99%

Continuous situation-specific development of business models: knowledge provision, method composition, and method enactment

et al. 2022

View full text Add to dashboard Cite

show abstract

“…As a first promising attempt, Girary et.al. (Giray & Tekinerdogan, 2018) suggest a method engineering approach (Harmsen, Brinkkemper, & Oei, 1994) to design customised IoT platform development approach but what key method fragments required and how they should be composed to create a bespoke platform development approach have not yet been addressed in the literature.…”

Section: One-size-fits-all Assumption Is Not a Practical Choicementioning

confidence: 99%

An exploration of IoT platform development

Fahmideh

Zowghi

2020

Information Systems

View full text Add to dashboard Cite

“…However, interactions of these situations in agile software architecture decision-making is still under progress [28], [29]. Overcoming the aforementioned challenges of coordination between situational factors and software architecture, Giray and Tekinerdogan [30] proposed a situational method engineering (SME) approach, which can be reprocessed to develop customized methods. The authors agreed upon the fact that there is not a single methodology that encourages a ''one size fits all'' approach.…”

Section: Documenting Slr Findingsmentioning

confidence: 99%

“…In view of the previously discussed reasoning, situational factors with less change (traditional) and with more change (agile) have high impact. Thus, during the construction of software architecture, different situational factors need to be considered [23], [30], [32].…”

Section: Documenting Slr Findingsmentioning

confidence: 99%

Towards Taxonomical-Based Situational Model to Improve the Quality of Agile Distributed Teams

et al. 2020

View full text Add to dashboard Cite

At present, software organizations are developing software products that employ global software development (GSD) teams. Organizations tend to adopt new methodologies for global software development, among which is the use of agile in the GSD industry, which yields both benefits and challenges. However, software development teams do not consider situational needs that delay software delivery, resulting in the late discovery of incompatible assumptions and architecture level rework. In this study, we conduct a systematic literature review (SLR) to identify the situational factors that need to be considered by software development teams before developing a software product. We further present taxonomical classification and comprehensively map the situational factors that impact design development and advancement in the proposed Situational Agile Distributed Development (SADD) model. We propose 18 directed hypotheses against each situational factor that supports our SADD model. In order to evaluate our directed hypotheses, statistical analysis method is used, and the level of confidence of each directed hypothesis is validated. The result of our study confirms that global software development teams are highly reliant on the SADD Model. Our study will largely contribute by devising a multilevel taxonomy of situational factors that elevate the performance of global software development teams. This taxonomical classification will allow to better map the relationships between multiple situational factors and elevate the process of creating a holistic model to handle situational needs in the context of Agile Distributed Software Development (ADSD). INDEX TERMS Agile distributed taxonomy, agile distributed teams, situational agile distributed development, situational model, taxonomical model.

show abstract

Situational Method Engineering for Constructing Internet of Things Development Methods

Cited by 8 publications

References 33 publications

Continuous situation-specific development of business models: knowledge provision, method composition, and method enactment

Continuous situation-specific development of business models: knowledge provision, method composition, and method enactment

An exploration of IoT platform development

Towards Taxonomical-Based Situational Model to Improve the Quality of Agile Distributed Teams

Contact Info

Product

Resources

About