F4

Question 1

System integration task

Step 1: Understand the end-to-end (as-is) business process

Answer 1

🔹 Goal: Identify business needs by analyzing current processes.

• Learn the business domain (e.g.,
  healthcare, education, mobile
  services).
• Identify core processes (e.g.,
  course preparation, enrollment).
• Model “as-is” processes (e.g.,
  “publish content,” “upload
  lectures”).

Methods to Analyze:
Observation: Watch real operations.

Documentation: Review manuals & process guides.

Interviews: Ask stakeholders.

Question 2

Step 2: Map the process onto components

Answer 2

🔹 Goal: Map current processes to existing systems, manual routines, and legacy solutions.

• Document available systems in
  a table format.
• Map each “as-is” process to
  existing components or
  integration solutions.

Key Questions:
- What integration is needed?
(Data, service, process)
- Can we reuse existing systems?
- Do we need new
applications/features?

Question 3

Step 3: Derive Requirements

Answer 3

🔹 Goal: Define what data or services need integration.

• Data integration (federation,
  transformation).
• Service integration (Web
  services, REST).
• Activity flow integration (process
  automation)

Quality Considerations:
- Performance (point-to-point?).
- Reliability (MOM?).
- Security & Scalability (ESB?).

Question 4

Step 4: Produce the Architecture

Answer 4

🔹 Goal: Design the integration architecture based on requirements.

• Based on the integration
  requirements, an integration
  architecture is produced
  describing an overall design of
  the solution
• Defined relationships between
  components.

Architecture:
- Graphical model – Shows all
integration components.
- Text description – Explains
technologies, tools, and
specifications.

Question 5

Step 5: Plan the Integration

Answer 5

Once tan integration architecture is produced, we need to formulate a detailed plan on how to implement the architecture. This involves the following tasks

Architecture Design:
Define (write) application interfaces (i.e. WSDL or RESTful specifications), Specify data formats and the content of documents (i.e. XML documents),
Do “process to be” modeling, where the roles are assigned to the involved systems (manual tasks in the “as-is” business process”),

Architecture implementation