10201132
Designing for Development
Course Information
Description
Prepare digital designs for development, structuring files and design systems so intent survives the handoff. Direct AI coding tools to build working interfaces from those specifications, then evaluate the results against design intent, accessibility standards, and functional requirements. Revise the specification when the build reveals what was left unsaid, version the work in Git, and deploy publicly. Produce a portfolio case study tracing the path from design file to working product.
Total Credits
3
Prior Learning Assessment
- None
Course Competencies (Course Outcomes)
-
Structure design files for development handoffAssessment StrategiesSkill DemonstrationProjectCriteriaOrganize pages, frames, and layers so another person can navigate the file without verbal explanationName components, styles, and variables using a consistent conventionSeparate in-progress exploration from work intended for handoffRemove unused, hidden, and detached elements before handoffStructure the file so its organization maps predictably to a code structure
-
Develop a component library using design tokens and variantsAssessment StrategiesSkill DemonstrationProjectCriteriaDefine color, type, spacing, and elevation tokens as reusable styles or variablesBuild components with named variants covering each documented stateApply tokens consistently rather than overriding values on individual instancesStructure the library so components can be reused across screens without modificationDocument naming conventions so the library translates predictably into code
-
Document design intent using industry-standard terminologyAssessment StrategiesWritten ProductProjectCriteriaUse accurate terminology for layout, components, states, and interaction patternsSpecify responsive behavior at defined breakpointsDocument interaction states including hover, focus, active, disabled, empty, loading, and errorIdentify edge cases not represented in the visual designWrite acceptance criteria that define correct implementation
-
Produce front-end interfaces using AI coding toolsAssessment StrategiesSkill DemonstrationProjectCriteriaSupply the context an AI coding tool requires to match documented design intentSequence a build into scoped requests rather than a single broad instructionProduce an interface that runs without errorsDocument the prompts and decisions that produced the result
-
Evaluate generated code against design intent and functional requirementsAssessment StrategiesCritiqueWritten ProductCriteriaCompare the built interface against the documented specification and identify discrepanciesVerify that the interface performs correctly across the specified breakpointsIdentify code that is fragile, redundant, or does not perform as describedDetermine when to redirect the tool and when to intervene manuallyExplain what can and cannot be verified about generated code
-
Test interfaces against accessibility standardsAssessment StrategiesSkill DemonstrationWritten ProductCriteriaTest keyboard navigation and focus order across the interfaceVerify semantic structure and programmatic labelingMeasure color contrast against WCAG AATest the interface using a screen readerDocument each failure with the standard it violates and the correction applied
-
Revise design specifications based on build outcomesAssessment StrategiesProjectWritten ProductCriteriaTrace an implementation failure back to an ambiguity in the specificationRevise documentation to resolve the identified ambiguityRebuild the affected component and confirm the revision resolved the issueCompare initial and revised specifications and describe what changed
-
Manage project versions using GitAssessment StrategiesSkill DemonstrationProjectCriteriaCommit work in increments with messages that describe the changeUse branches to separate in-progress work from a working versionPush work to a remote repository on a regular cycleRestore a prior version of a file or projectMaintain repository documentation that describes the project
-
Apply ethical standards to the use and disclosure of AI-generated workAssessment StrategiesScenario ResponseWritten ProductCriteriaDistinguish between work you directed, work you authored, and work a tool generatedDisclose the role of AI tools in portfolio and professional contextsIdentify licensing and attribution obligations for generated code and assetsEvaluate whether a generated solution introduces bias, exclusion, or harmExplain a decision to reject or override a tool's output
-
Critique design and development work in peer reviewAssessment StrategiesCritiqueOral PresentationCriteriaIdentify specific strengths and specific problems in another student's workReference the specification or accessibility standard supporting the observationPropose an actionable next step rather than a general reactionApply peer feedback to your own project and document the resulting change
-
Develop a portfolio case study documenting the processAssessment StrategiesCase StudyPortfolioPresentationCriteriaTrace the project from design file to functioning interfaceShow the difference between the initial specification and the final buildDescribe your role in directing and evaluating generated workPresent the case study to an audience outside the coursePublish the case study in a format appropriate for a professional portfolio
-
Prepare a project for deployment and public accessAssessment StrategiesSkill DemonstrationProjectCriteriaDeploy a working interface to a publicly accessible URLConfigure the build and hosting settings a project requires to run outside a local environmentIdentify the technical components a project would require to operate at production scale, including data storage, authentication, and content managementDistinguish between what a prototype demonstrates and what a production system would requireDocument the known limitations of the deployed version