2016
DOI: 10.1016/j.compag.2016.04.011
|View full text |Cite
|
Sign up to set email alerts
|

A reference architecture for Farm Software Ecosystems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
54
0
6

Year Published

2021
2021
2024
2024

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 78 publications
(67 citation statements)
references
References 28 publications
0
54
0
6
Order By: Relevance
“…Development of a software product line can result into ICT Mass Customisation as it enables configuration of ICT Components into integrated farm information system. Currently, this configuration is not provided as a business service, which is one of the bottlenecks hindering farm enterprise integration (Kruize et al, 2016). Therefore, actors should become part of Farm Software Ecosystems that can support ICT Component configuration.…”
Section: Stakeholdersmentioning
confidence: 99%
See 4 more Smart Citations
“…Development of a software product line can result into ICT Mass Customisation as it enables configuration of ICT Components into integrated farm information system. Currently, this configuration is not provided as a business service, which is one of the bottlenecks hindering farm enterprise integration (Kruize et al, 2016). Therefore, actors should become part of Farm Software Ecosystems that can support ICT Component configuration.…”
Section: Stakeholdersmentioning
confidence: 99%
“…used raw materials, resources and labour availability), the purpose and its relations ICT Component configurations can be determined. To support configuration based on an ICT Mass Customisation, in combination with a Best-of-Breed approach, the reference model should be able to: (Kruize et al, 2016).…”
Section: Functional Requirements For Raage 20mentioning
confidence: 99%
See 3 more Smart Citations