<aside> 💡 This document describes the application and all its features (application layer). These features should map exactly to the needs described in the Platform Overview document. Functional Specification contains feature description as well as high fidelity mockups and UX flows.
</aside>
<aside> ℹ️ Why is this document important:
</aside>
Now that you've spent enough time in the problem space, understanding your users and their needs, it's time to jump into the solution space.
<aside> ℹ️ Brainstorming is an activity that will help you generate more innovative ideas and solutions to user pain points. It’s one of many methods of ideation—the process of coming up with new ideas—and it’s core to the design thinking process.
</aside>
<aside> ℹ️ Next, it's time to create your value proposition. Value proposition is a structure which can help ensure that a product or service is positioned around what the customer values and needs. It should be created based on information gathered in your section of the Platform Overview.
</aside>
<aside> ℹ️ Let's start designing the solution. You've gathered a lot of knowledge about the user needs and a lot of ideas during your brainstorming sessions. Now you can focus on designing each feature that you want to build. Start with wireframes, create prototypes and show them to your users. Get their feedback, validate the solution and only then start with high fidelity mockups.
</aside>
<aside> ℹ️ Now that you have your high fidelity mockups, approved and validated with your users, you can start defining features, and handover the specification to the development team. Consider this step as the first step in building your product backlog, where each segment will represent one epic. Take another look at your - that will help you define your epics. Try to map each epic to one of the user needs identified in the Platform Overview
</aside>
Go to System Design to find details about the architecture and a set of tasks (tactics) to achieve the goals described in previous documents (technology layer). This document contains a list of all technical tasks, user stories and C-diagrams with architecture overview.