Project process

Project communication is very important, a daily communication, something to say, nothing to report peace.

Demand analysis

  • Product Manager (PM) : Propose functional requirements, show prototypes and explain why.
  • Front end (FE) : Question whether the requirements are reasonable, closed loop, and technically achievable. Whether additional support is required. Don’t rush into scheduling.
  • If you need help.

Technical scheme design

  • Simplify, do not over-design.
  • Produce documentation.
  • Group review.
  • Issue the conclusion of the meeting.

The development of

  • The schedule is usually a quarter longer.
  • Consider the schedule of the previous process and give the amount of work (days to complete) if it is not clear.
  • Write development documentation.
  • Unit testing.
  • Code Review, let someone with better technology help you look at the Code.

alignment

  • Technical coordination with back end (RD) and client (CRD).
  • Let the visual designer (UE) determine the visual effect.
  • Let the product (PM) determine product functionality.

test

  • Send email and copy to the project team.
  • Test problems should be recorded in detail.
  • There are problems with timely communication, front-end (FE) and testing (QA) inherent information asymmetry.

Project online

  • If there is a problem, roll back in time. Stop your losses first and look for problems later.

Q&A

What about product (PM) plus requirements?

  • Can’t refuse, just go through the requirements change process.
  • If the company does not change the process, initiate the review of the project team and the leader to re-evaluate the schedule.

The project design

Status: Data Structure Design (VUE-Data)

  • Describe everything with data
  • Data should be structured to facilitate traversal and search
  • To make the data extensible, new functionality has been added

View: Component structure and disassembly

  • Break down the hierarchy functionally
  • Make components as atomic as possible
  • Container components (only managing data) and UI components (only displaying views)

A classic case

todolist

  • Prototype drawings (typically provided by product manager or visual designer)

  • Data Design
data: function () {
    return {
        list:[
            {
                id:1.title:'title'.completed:false
            },
            // ...]}}Copy the code
  • Component design
<App>  <! -- Only manage data -->
    <Input/>  <! -- is only responsible for input, give the array result to the parent component -->
    <List>  <! Display list only, get data from parent component -->
        <ListItem/>  <! -- Display single data, delete, switch completed state -->
        <ListItem/>
        <ListItem/>
    </List>
</App>
Copy the code