In systems analysis and information technology governance, a standards manual defines mandatory conventions and practices. Such a manual specifies standards that must be followed in both system design and ongoing system operation—confirming compliance, consistency, and quality across the software life cycle.

Introduction / Context:
A standards manual is a governance artifact that codifies how teams should design, build, deploy, and run information systems. It improves interoperability, security, maintainability, and auditability by making expectations explicit for both design-time and run-time activities.

Given Data / Assumptions:

• The organization maintains a written standards manual.
• Standards must be applied during solution architecture and during day-to-day operations.
• Consistency across projects and environments is a primary goal.

Concept / Approach:

Design standards define naming conventions, architectural patterns, data models, interface contracts, coding guidelines, and security-by-design practices. Operational standards define backup schedules, monitoring thresholds, incident response procedures, change management steps, and service-level objectives. Together, they cover the full system life cycle and are essential to compliance and quality management frameworks (for example, ISO, ITIL, COBIT).

Step-by-Step Solution:

Verification / Alternative check:

Review any mature organization’s SDLC and service management documents; they pair design standards (for building) with operational standards (for running), confirming the dual scope.

Why Other Options Are Wrong:

System design only: Ignores run-time governance and reliability.

System operation only: Ignores architectural consistency and technical debt prevention.

Neither/None: Contradicts the purpose of a standards manual.

Common Pitfalls:

Treating standards as a one-time design checklist and overlooking operational enforcement, leading to drift and compliance gaps.

Final Answer:

both (a) and (b)