Files
jaime.meza b9a194f7c5 docs: reorganize site structure using Diátaxis framework
- Group hub-documentation into explanation/, how-to/, and reference/ per Diátaxis
- Move ifs-integration.md to new hoist-hub/ category
- Add contributing/ category with Diátaxis framework explainer
- Move tutorial-basics and tutorial-extras under docusaurus-guide/
- Rewrite docs/intro.mdx as site entry point with category navigation
- Update all doc titles to reflect their Diátaxis type
- Add HOIST logo to homepage hero and fix Get Started link
2026-06-18 14:50:15 -05:00

2.7 KiB

sidebar_position, title
sidebar_position title
1 Business Requirements Definition

Business Requirements Definition

The HOIST Business Analyst is responsible for drafting this section, outlining the solution scope in collaboration with the customer. This is the conceptual overview of what the HUB feature will accomplish. The customer is responsible for reviewing and approving the content to ensure it accurately reflects the original requirements.

During the specification sign-off process, the customer evaluates the documented scope and provides feedback as needed to ensure 100% alignment with business needs.


Business Value

Describe the benefits and the business value — not a proposed solution — that can be achieved by improved system support. It is beneficial for the overall understanding if the benefits of the changed system support can be stated clearly.


Current Process / Workflow

Describe the GAP in the IFS workflow or functionality that causes the need for this HUB feature.

In IFS

Describe how it works in IFS:

  • IFS Navigation (e.g., Sales / Quotation / Sales Quotation)
  • Reference an existing Work Instruction if available
  • If no WI exists, provide a brief description of how to navigate in IFS
  • Include IFS screenshots if needed

Desired Outcomes & Desired Process / Workflow

Describe the desired behavior from the system and the resulting process/workflow.


Business Requirements Details

This section focuses exclusively on detailing the business requirements. It should not include functional or technical requirements, as those will be addressed in subsequent sections.

The table below itemizes each requirement point in detail:

Req. # Description Business Owner Related Req.
1 To associate a part master record with a customer 1
2 To run a report returning all parts belonging to a specific customer 1

References, Sources, and Relations to Other Customizations

To support the requirements outlined in this specification, you may reference relevant documents, examples, or resources available on the project SharePoint site. Please ensure these references directly relate to the content.

:::caution If this specification was developed using a preliminary document from the customer, do not attach that document here — it may cause confusion. :::

Ref. # Title Description Type Related Req.
1 Document explaining the business requirements document
2 Report layout document layout
3 CRIM 123 There is a customization — here is the spec spec