CT30A8912 Software and Systems Architectures LUT University

Spring 2024

Integration and deployment plan

The aim of this activity is to reflect about the integrations required in your project and explain them
to potential partners or customers interested in your software solution.

Integration is often considered only a technological problem, focused on connecting computer

systems and applications. However, integration also has a strong business dimension concerned with
facilitating the information flows, material resources, and controls across different companies.

Part 1: Integration tasks

Discuss with your team and briefly answer in your document (1-page max.) the following questions.
You can use slices of your context view, functional view, or information view to support the answers.
- To what extent does your software solution depend on external systems or platforms? In
other words, which of your ASRs and scenarios require some type of inter-organizational
integration and why?
- What data do the external stakeholders need to share from their systems to your proposed
software solution, and vice-versa? Why?
- Do you rely on standards for structuring, transferring, and/or storing data? If yes, which ones?
- Is the information exchange subject to regulation compliance or audits?

Part 2: Deployment tasks

Discuss with your team and briefly answer in your document (1-page max.) the following questions.
You can use slices of your deployment view (if you have one) to support the answers:
- How will you test and implement the integrations to external systems?
- Which hardware or software elements are hosted at the external stakeholders’ premises?
- Who is responsible for deploying and updating the different parts of your solution?

Deliverables
Your written deliverable should describe at least the following aspects (but not necessarily in the
same order):

- Material from the previous tasks, possibly updated

- Your analysis to the questions listed above in this document
- Work hour estimations for each group member, including this task and any previous tasks.
Please also indicate how many hours were used for group meetings, how many hours for
individual work
- Change log, indicating any significant updates made to the document since the last revision

The written deliverable is returned as a single PDF document. If necessary, your models can be
uploaded as separate image files.

Tips
- Use annotated diagrams or slices of your architecture models to explain the key
integrations. You might need to revisit some of the previous design decisions and adjust
your models accordingly.
- Make sure that your description of the integrations to third-party systems is consistent with
your context view, as well as the <<external>> components and interfaces shown in your
functional view

1(1)