Scribd
Upload
81 views

IC System Design Review Checklist 10816

The system design review checklist provides key questions to consider when reviewing a system design. It includes questions about the project details, feasibility assessment, design approach, constraints, dependencies, risks, alternatives considered, interfaces, user interaction, failure conditions, compliance, security, performance, testing, hardware, deployment, costs, disaster recovery, operations, and any additional design issues. Reviewing these areas helps ensure a thorough evaluation of the system design prior to implementation.

Uploaded by

noha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
81 views

IC System Design Review Checklist 10816

The system design review checklist provides key questions to consider when reviewing a system design. It includes questions about the project details, feasibility assessment, design approach, constraints, dependencies, risks, alternatives considered, interfaces, user interaction, failure conditions, compliance, security, performance, testing, hardware, deployment, costs, disaster recovery, operations, and any additional design issues. Reviewing these areas helps ensure a thorough evaluation of the system design prior to implementation.

Uploaded by

noha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 3

SYSTEM DESIGN REVIEW CHECKLIST

APPLICABL
DESIGN DELIVERABLE KEY QUESTIONS OR ISSUES TO CONSIDER
E?
Project Name, Contributors, Work Include the name of the project and all contributors, the name of the work group(s) that own particular sections, and the
YES
Group, Date design review date.

NO Key Stakeholders List the key stakeholders, with their work group and contact information.

YES Feasibility Assessment Indicate whether a feasibility assessment was completed for this project.

Include the project charter, and briefly describe the business justification and project scope. Identify the target audience
NO Scope and Business Reason
or primary customer.

Describe the design approach, the logical design, and the high-level physical design, and include design drawings or
YES Design Approach
diagrams.

YES Constraints and Limitations What technical, financial, or business limitations impact this design?

Is the design dependent on the release of other applications or services, or on any organizational changes or process
NO Dependencies
bottlenecks?

Assumptions What assumptions were used?

Risks What risks were involved in this project, and how did you mitigate them?

Design Alternatives What design alternatives were evaluated? What criteria influenced the final decision?

Reporting and Processes Describe all design reporting and analytics and what has been changed or removed?

System Interfaces Describe all system interfaces and services and inputs and outputs, as well as any third-party integrations.

User Interfaces How does the user interact with this design solution? Describe the inputs and outputs.

Fault Management Describe all failure conditions, error logging, detections and corrections, and recovery processes.

Existing Defects Resolved What existing defects does this design resolve?

Compliance Describe the regulations that this solution addresses. Is the design compliant with appropriate standards?

Architectural Describe the scalability of the architecture.

Usability and Accessibility Describe the design in terms of its usability and accessibility.
What type of data is being transferred and stored, and what is its sensitivity? Additionally, comment on authentication
Security
and authorization measures.

Performance and Reliability Describe the acceptable service-level performance of this design.

Network or Remote Access Describe any additional network features. Does the system accommodate remote access?

Data and Roles Describe the database, structure, data flow, integrity, file, and query types, as well as systems used.

Testing What types of testing have been done (prior to implementation)?

Hardware or Equipment What hardware system does this solution use? What operating system does it use?

Deployment Describe how this solution will be deployed and how it will be used with existing systems or programs.

Cost What are the one-time and ongoing costs? Do we have the resources to support ongoing maintenance?

Disaster Recovery Describe the file recovery, retention, and criticality of this program after a crisis.

Operations Describe any required maintenance, audit, report distribution, or other operational issues inherit in this design.

Special Design Issues List any additional design considerations not covered above.
Any articles, templates, or information provided by Smartsheet on the website are for
reference only. While we strive to keep the information up to date and correct, we make
no representations or warranties of any kind, express or implied, about the
completeness, accuracy, reliability, suitability, or availability with respect to the website or
the information, articles, templates, or related graphics contained on the website. Any
reliance you place on such information is therefore strictly at your own risk.

You might also like