Q: What are acceptance criteria in a specification?

Acceptance criteria are testable conditions that define when a requirement is satisfied: 'Given a user uploads a file, when the file type is not PDF or DOCX, then the upload is rejected with an error message.' CNEXT writes acceptance criteria for all key user stories – enabling automated or manual UAT to verify delivery without ambiguity.

Q: Does CNEXT include security and FADP requirements in specifications?

Yes, always. CNEXT includes security and FADP non-functional requirements as standard in every specification: data residency (Switzerland North), authentication mechanism (Entra ID, MFA), authorisation model (who can see what), personal data identification and classification (Sensitivity Label), audit logging requirements and DPA scope.

Q: Can CNEXT write a specification for a client's in-house development team?

Yes. CNEXT offers specification-as-a-service: CNEXT runs the requirements workshops, writes the specification and hands it to the client's in-house team or preferred development partner for implementation. This is particularly useful when the client has development capacity but needs Microsoft 365 / AI architecture expertise.

Q: What format does CNEXT use for specifications?

CNEXT specification format: Word document (primary, version-controlled) with embedded wireframes (Figma or PowerPoint), data model diagrams (Visio or draw.io), Excel appendices (content type fields, connector inventory, test cases) and a SharePoint site for version management and client review. CNEXT uses tracked changes for client review cycles.

Question 1

Why is a technical specification important for a Microsoft 365 project?

Accepted Answer

A specification prevents scope creep (the #1 cause of IT project overruns), enables accurate fixed-price delivery, aligns client and agency expectations before development starts, provides a basis for user acceptance testing and serves as the handover document for future maintenance teams. CNEXT includes a specification phase in all projects >CHF 20,000.

Question 2

What does a CNEXT technical specification include?

Accepted Answer

CNEXT specification documents include: project context and objectives, functional requirements (what the solution must do), non-functional requirements (performance, security, FADP compliance, browser/device support), user stories with acceptance criteria, wireframes or mock-ups, data model (SharePoint content types, Power Apps screens, Power BI measures), integration specifications (APIs, connectors) and out-of-scope items.

Question 3

How long does a specification workshop take?

Accepted Answer

A specification workshop for a mid-size project (e.g. SharePoint intranet, Power Apps business app): 1–2 days. A specification for a complex system (multi-app Power Platform solution, multi-site SharePoint implementation): 2–5 days. CNEXT delivers the written specification document within 5–10 business days after the workshop.

Question 4

Does CNEXT use templates for specifications?

Accepted Answer

Yes. CNEXT has specification templates for: SharePoint intranet (IA, content types, governance, branding), Power Apps (screens, data model, workflow, connector inventory), Power Automate (trigger, actions, error handling, connector list), Power BI (data sources, measures, report pages, row-level security), Copilot Studio (agent purpose, topics, knowledge sources, actions) and Azure AI (architecture diagram, data flow, security model).

Question 5

Can a CNEXT specification be used to tender the project to other vendors?

Accepted Answer

Yes. CNEXT specifications are written to be vendor-neutral – they describe what needs to be built, not how CNEXT specifically would build it. Clients who want to tender to multiple vendors can use the CNEXT specification as the RFP technical appendix. CNEXT typically credits the specification cost against the project if we win the subsequent tender.

Question 6

What are functional vs. non-functional requirements?

Accepted Answer

Functional requirements: what the system does ('Users can upload a document to the contracts library with metadata: Contract Value, Counterparty, Expiry Date'). Non-functional requirements: how it does it ('Page load time <3 seconds for 95th percentile of requests', 'All personal data stored in Switzerland North data centre', 'WCAG 2.1 AA accessible'). CNEXT documents both types for every project.

Question 7

What are acceptance criteria in a specification?

Accepted Answer

Acceptance criteria are testable conditions that define when a requirement is satisfied: 'Given a user uploads a file, when the file type is not PDF or DOCX, then the upload is rejected with an error message.' CNEXT writes acceptance criteria for all key user stories – enabling automated or manual UAT to verify delivery without ambiguity.

Question 8

Does CNEXT include security and FADP requirements in specifications?

Accepted Answer

Yes, always. CNEXT includes security and FADP non-functional requirements as standard in every specification: data residency (Switzerland North), authentication mechanism (Entra ID, MFA), authorisation model (who can see what), personal data identification and classification (Sensitivity Label), audit logging requirements and DPA scope.

Question 9

Can CNEXT write a specification for a client's in-house development team?

Accepted Answer

Yes. CNEXT offers specification-as-a-service: CNEXT runs the requirements workshops, writes the specification and hands it to the client's in-house team or preferred development partner for implementation. This is particularly useful when the client has development capacity but needs Microsoft 365 / AI architecture expertise.

Question 10

What format does CNEXT use for specifications?

Accepted Answer

CNEXT specification format: Word document (primary, version-controlled) with embedded wireframes (Figma or PowerPoint), data model diagrams (Visio or draw.io), Excel appendices (content type fields, connector inventory, test cases) and a SharePoint site for version management and client review. CNEXT uses tracked changes for client review cycles.

Projektspezifikation

Vollständig

KI-generiert

Professionell