Summary

News

About

Team Profiles

Profile 1
see this post for more info on profile 1

Profile 2

Profile 3

Profile 4

Profile 5

Videos

…

Team A Presentations

….

What we are learning from our project

…

Post Capstone Next Steps

….

Tools we Use

…

Background Info

…

Team A Project Notebook

Value Proposition Canvas

1. File Upload: Attach your completed Value Proposition Canvas (PDF or Image format). Ensure both the Customer Profile (Jobs, Pains, Gains) and the Value Map (Products/Services, Pain Relievers, Gain Creators) are precisely defined.
2. Video Presentation 
3. Strategic Justification & Fit Analysis: In the text box below, provide an in-depth analysis of the “fit” between your proposed value and the customer’s reality. Do not simply transcribe what is already visible on the canvas. Instead, use this space to critically evaluate your business assumptions. 

Structure your response to address the following: 

• Core Hypotheses: Identify the most severe customer pain or the most essential job-to-be-done. Why is this specific aspect more critical than others
• Problem-Solution Fit: Detail exactly how your primary features or services act as direct pain relievers and gain creators for this specific customer profile.
• Validation Strategy: Discuss the assumptions that carry the highest risk and briefly outline how you intend to validate them in the market. 

Formatting Requirements for the Text Box: 

• Word Limit: 300 – 500 words. 
• Structure: Write in clear, well-organized paragraphs.

Cybersecurity Canvas

1. Cybersecurity Canvas (File Upload)
2. Video Presentation
3. Canvas Abstract (Text Box):

Description: Write an abstract summarizing the primary aspects of your canvas. Both your abstract and the canvas itself must ensure that blocks such as the Value Proposition and Feasibility & Risks explicitly reflect the realities of your technical design. You must translate your technical threat mitigation into business feasibility, proving how your architecture acts as a definitive “Pain Reliever” or “Gain Creator” that directly reduces cost, liability, or operational risk for your identified stakeholders.

Formatting Requirements for the Text Box:

• Word Limit: 300 – 500 words.
• Structure: Write in clear, well-organized paragraphs.

Risk-Justified Architecture Checkpoint

1. Architecture Document (File Upload – Min 4 pages): Description: Write the architecture document and a justification of your architectural decisions using professional, analytical paragraphs that bridge engineering rigor with entrepreneurial viability. Develop a structured document detailing your technical decisions and security posture. You must address: 

• Contextual Risk Reasoning: Explain how you evaluated security risks beyond standard CVE/CVSS metrics, incorporating frameworks like the NIST AI RMF to evaluate system trustworthiness. 
• Traceable Mitigation: Explicitly map your mitigating architecture to the specific threats identified in your models (e.g., how design choices neutralize STRIDE-based threats). 

1. Video Presentation 
2. Executive Summary (Text Box): Write a compelling synthesis of your architecture document. Summarize your core contextual risk reasoning and highlight the most critical traceable mitigations. Defend your architectural decisions by articulating how they balance rigorous, trustworthy security with the project’s practical and entrepreneurial viability. 

Formatting Requirements for the Text Box: 

• Word Limit: 400 – 500 words. 
• Structure: Write in clear, well-organized, analytical paragraphs. Avoid bulleted lists in the text box to focus on narrative flow and argumentation.

Business Visibility Document

Description: The project is now evaluated as a sophisticated engineering artifact with viable business logic. You must demonstrate this viability through a formal, concise document and a distilled text summary.

1. Business Viability Document (File Upload – Max 2 pages): Develop a structured justification connecting your engineering decisions to real-world application. You must clearly define 
   • For Whom: Identify the specific target audience, end-user, or stakeholder.
   • Pain Relieved: Detail the friction points, inefficiencies, or risks this audience currently faces.
   • Gain Created: Explain the tangible value, outcomes, or new capabilities your engineering architecture delivers.

1. Video Presentation
2. Executive Summary (Text Box): Write a compelling synthesis of your document. Defend the project’s viability by articulating how the technical rigor of your artifact directly translates into business logic and value for the identified user.

Formatting Requirements for the Text Box: 

• Word Limit: 400 – 500 words. 
• Structure: Write in clear, well-organized, analytical paragraphs. Avoid bulleted lists in the text box to focus on narrative flow and argumentation.

Final System Package

Description: This final submission requires a complete, professional package of your engineered artifact, combining functional code, technical documentation, visual architecture, and a compelling entrepreneurial pitch. You must provide the following deliverables:

1. System Manual (File Upload): Provide a comprehensive technical guide detailing the system’s installation, configuration, and operational instructions for end-users or administrators.
2. GitHub Repository (URL): Submit the direct link to your functional codebase. Ensure the repository includes a clear README.md, well-documented code, and reflects professional software engineering practices.
3. System Infographic (File Upload): Include a high-level, visual representation of your system’s architecture, data flow, or core value proposition that can be easily understood at a glance.
4. Presentation Deck (PPT – File Upload): Submit your slide deck that visually supports your system’s technical design, business viability, and core functionalities.
5. “Shark” Pitch Video (URL or File Upload): A concise, persuasive video presentation (investor pitch style) defending your project. You must convincingly bridge your engineering rigor with entrepreneurial viability, explaining why your solution matters and how it works.
6. Executive Summary (Text Box): Write a high-level synthesis of your entire system. This summary should act as the “elevator pitch” for your project, briefly touching upon the problem solved, the architectural solution, and the ultimate value delivered.

Formatting Requirements for the Text Box: 

• Word Limit: Maximum 300 words.
• Structure: Write in clear, well-organized paragraphs. It must be a self-contained summary that gives a clear understanding of the project without needing to open the attached files.