The deadline for FUNARCH 2024 has been extended to June 12. If you have
any material on what makes functional programming in the large work,
please consider writing it up and submitting it!
======================================================================
*** FUNARCH 2024 -- CALL FOR PAPERS ***
Second ACM SIGPLAN Workshop on
Functional Software Architecture - FP in the Large
6th September 2024, Milan, Italy
Co-located with ICFP 2024
https://functional-architecture.org/events/funarch-2024/
======================================================================
TIMELINE:
Paper submission 12th June 2024 (EXTENDED FROM JUNE 3rd)
Author notification 30th June 2024
Camera ready copy 18th July 2024
Workshop 6th Sept 2024
BACKGROUND:
"Functional Software Architecture" refers to methods of construction
and structure of large and long-lived software projects that are
implemented in functional languages and released to real users,
typically in industry. The goals for the workshop are:
- To assemble a community interested in software architecture
techniques and technologies specific to functional programming;
- To identify, categorize, and document topics relevant to
the field of functional software architecture;
- To connect the functional programming community to the software
architecture community to cross-pollinate between the two.
The workshop follows on from the Functional Software Architecture
open space that was held at ICFP 2022 in Slovenia.
SCOPE:
The workshop seeks submissions in a range of categories:
- You're a member of the FP community and have thought about how
to support programming in the large, for example by framing
functional ideas in architectural terms or vice verse, comparing
different languages in terms of their architectural capabilities,
clarifying architectural roles played by formal methods, proof
assistants and DSLs, or observing how functional concepts are
used in other language and architecture communities.
Great, submit a research paper!
- You're a member of the architecture community, and have thought
about how your discipline might help functional programmers, for
example by applying domain-driven design, implementing hexagonal
architecture, or designing self-contained systems.
Excellent, submit a research paper!
- You've worked on a large project using functional programming,
and it's worked out well, or terribly, or a mix of both; bonus
points for deriving architectural principles from your experience.
Wonderful, submit an experience report!
- You know a neat architectural idiom or pattern that may be useful
to others developing large functional software systems.
Fabulous, submit an architectural pearl!
- You have something that doesn't fit the above categories, but
that still relates to functional software architecture, such
as something that can be written up, or that could be part of
the workshop format like a panel debate or a fishbowl.
Superb, submit to the open category!
Research papers should explain their research contributions in both
general and technical terms, identifying what has been accomplished,
explaining why it is significant, and relating it to previous work,
and to other languages where appropriate.
Experience reports and architectural pearls need not necessarily
report original research results. The key criterion for such papers
is that they make a contribution from which others can benefit.
It is not enough simply to describe a large software system, or
to present ideas that are specific to a particular system.
Open category submissions that are not intended for publication
are not required to follow the formatting guidelines, and can
submit in PDF, word or plain text format as preferred. Not knowing
what kinds of submissions we will receive, we cannot be specific as to
how they will be evaluated. However, submissions that seem likely to
stimulate discussion around practices in functional architecture
are encouraged.
If you are unsure whether your contribution is suitable, or if
you need any kind of help with your submission, please email
the program chairs at