Define high-level structure of the solution

[alecn2002]

Define high-level structure of the solution

[alecn2002]

My view of the main process (does not include SysOps/Reporting part, as well as Security aspect; not split into functional parts)

[alecn2002]

And the system split to major parts (again - without Management/Reporting and Security)

[pwandzil]

By the parts do we mean like a C4 container - separate running and deployed app or rather a functional part - C4 component?

[mmest]

At this stage, I am not sure whether it should be container or components. Mark it as TBD?

[alecn2002]

By the parts do we mean like a C4 container - separate running and deployed app or rather a functional part - C4 component?

Functional parts that will form components at the implementation

[mwunderlich]

Just to clarify: "Contract" here means the contract between DCC and the potential employer(s) for the matching services provided by DCC, right? (i.e. it's not the employment contract)

[mwunderlich]

I think this initial design captures the main functionality well. Since the whole AI features would be a core part, I would suggest to maybe extract that to a separate AI/ML sub-system which provides two main features:

• CV anonymization (with PII extraction)
• Matching engine (with keywords/skills identification, ranking and filtering)

[mmest]

I read the "Contract" in the diagram as the service agreement contract by DCC, just as Martin says. Indeed that may not be clear just from the diagram. Is it possible to add definitions in a note in the diagram?

On Tue, 24 Sept 2024 at 08:35, Martin Wunderlich @.***> wrote:

Just to clarify: "Contract" here means the contract between DCC and the potential employer(s) for the matching services provided by DCC, right? (i.e. it's not the employment contract)

— Reply to this email directly, view it on GitHub https://github.com/alecn2002/ArchKatasFall2024/issues/3#issuecomment-2370314890, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALT63Z73ZGBCLYNY3HP2G3ZYEB4XAVCNFSM6AAAAABOR7WC3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZQGMYTIOBZGA . You are receiving this because you commented.Message ID: @.***>

[mmest]

In the Issue List External Communications #2 I describe the AI as an external system and I give some rationale for that. I would like to know if that description is suitable.

[pwandzil]

Per "Processes": CV Anonymization, Matching, Payment checking Two details:

• "Business-Process" is not exactly "Business-Event"
• "Financial controller" does not have to be an "Business-Actor", it can be actors "Business-Role"

[mwunderlich]

One component that is missing from the design is the one dealing with all the data tracking and aggregation. Let's call it "Reporting+Analytics" maybe.

From the specs, it would need to support the following:

• create and provide data analytic reports on company performance --> needs to be defined what data should go in there

• reports on "solution building services with executives" --> no idea what they mean by this

• monthly data and analytic report presenting KPI metrics as it relates to the interview and hiring process --> could be generated and sent automatically; but who should be the recipient of this?

• specific data Points to be tracked:

  • company decides to move forward with a candidate
  • unlocking full candidate profile to offer an interview (isn't this same as the first one?)
  • send five-question-survey to job candidate about interviewer (and track response)
  • send five-question-survey to interviewer about job candidate (and track response)
  • accumulation of demographic data after rejecting a candidate or presenting an offer