README

User Story

As a boot camp teacher,
I want to see detailed documentation of the boot camp week 5 challenge,
so I can score the work done.

Acceptance Criteria

• It's done when all the sections from the README template contain documentation of the week 5 challenge.

JavaScript App

User Story

As a Password Generator user,
I want to click on Generate Password button,
so I can choose the password options,
and see a randomly generated password matching my given settings.

Acceptance Criteria

• It's done when the user can enter the password length.
• It's done when the application validates the password length input between 10 and 64 characters.
• It's done when the application confirms the character types for the password with the user.
• It's done when the application validates that the user at least chose one character type.
• It's done when the application outputs a randomly generated password matching the given validated user inputs.

Base code

User Story

As a boot camp student,
I want to set up the repo folder structure for the week 5 challenge,
so I can create the Generate Password app.

Acceptance Criteria

• It's done when there is a docs folder with the starter/ folder and files and the README.md file from the week 5 challenge.
• It's done when you copy the files index.html, style.css and script.js into the project's root folder.
• It's done when there is a README.md file in the project's root folder and contains the markdown template provided for the week 5 challenge.

Deployment

User Story

As a boot camp teacher,
I want to see the week 5 challenge in a public URL,
so I can score the work done.

Acceptance Criteria

• It's done when the final code is deployed to a public URL in GitHub Pages.
• It's done when the repo and live site URLs are submitted to the teacher.

Pseudocode

User Story

As a boot camp teacher,
I want to see the design specifications of Password Generator,
so I can understand the functional, structural and behavioural components of the application.

Acceptance Criteria

• It's done when there is a functional requirement analysis.
• It's done when there is a pseudocode of the application.
• It's done when there is a structural modelling of the application.
• It's done when there is a behavioural modelling of the application.

Improvements

User Story

As a user,
I want to be informed of my input validation errors,
so I can decide whether to re-enter the inputs or finish with the execution.

As a developer,
I want to document the code of the Password Generator App,
so I can have a reference to the APIs and understand the workflow in the code.

Acceptance Criteria

• It's done when the program pops up a notification showing the info validation error.
• It's done when the program confirms with the user to continue with the execution after an input error.
• It's done when the code workflow is commented on, and the functions document their APIs with their description, input and outputs.