DEV Community

Discussion on: Do I overestimate my abilities?

Collapse
 
tqbit profile image
tq-bit

You should spend some time writing out what your app looks like, what problems it solves and what not.

And watch the hell out of those tutorials if you must. You're not obliged to reinvent the wheel if there's a method or a library for what you want to do.

I usually fill out a template for my own - and customer - projects. It's never part of any official project docs, but it helps me to stay on track. And to document the crimes I've commited later. Perhaps it'll help you too.


Functional Specification for my projects:

  1. General infos
    1.1. Executive summary of the project
    1.2. Project team
    1.3. Stakeholders
    1.4. Technology Stack

  2. Customer requirements
    2.1. Goal of the customer - fill out the five Ws
    2.2. Business impact - how will the product add value to the customer's business?
    2.3. Detailed description - with user stories, customer journeys, flowcharts. etc
    2.3.1. Features
    2.3.2. Non-features

  3. Time frame
    3.1. Planning phase - from + to
    3.2. Development phase (including tests) - from + to
    3.3. Go-Live phase - from + to

Collapse
 
hakimraissi profile image
HakimRaissi

Thank you for your help, All i did until now is to write all the endpoint i need to code on my notebook and did some data modeling for the users and the products. But i think i'll follow your method too.