One: development process
- What are the development process (devOps process)?
Plan-code-package (build)-release test (test)-release official version (release)-deployment (deploy)-maintenance (operate)-monitoring (monitor)
Version management: trunk -> branch git
2. What are the processes that I didn't know before? Give an example of a self-developed project to describe the devOps process and think about how to develop efficiently?
Two: Demand analysis
- Demand analysis analysis content (where does it come from)
- Key content in needs analysis (pain points)
- Requirements analysis documents and tools (how to do it)
Pre-consideration of needs analysis
Project nature:
- Business type: efficiency improvement brought by paperless
- Pain type: the rumors of the market decision
- Functional type: enterprise & customer needs, to solve the flow entrance
Needs analysis pain points:
- Do it if you don't want to
- Take it all
- Not communicated/confirmed
- Sheep management
Difficulties of demand analysis:
- In addition to considering function implementation, time/cost should also be considered
- Form requirements document, user feedback confirmation
- Guide user needs, create user needs
How to create user demand in the company
- Lean on the projects you have done, lean on the company’s existing products, lean on the familiar direction
- Lean on the direction where the company will develop, lean on the direction where the team’s technology will develop, lean on the direction where the entire industry’s technology develops
- Enterprise level, strategic level. . .
Requirements analysis component
- Business needs
- User needs
- Project requirements
Project requirements change
- Consider whether it is reasonable (project duration, cost, technology)
- Whether it is a change within the scope of the project and whether it has an impact on the main business
- Clarify the process of requirement change, determine the requirement change (send email)
Product requirements change
- Communication is king
- I can cry and have milk to eat (learn to ask, there may be rewards for giving, and there will be no reward for not paying)
- Guide demand (some of the ideas of the product manager are beyond the technical scope, the construction period. Need to be coordinated)
- Challenge yourself
Core business needs analysis,
overall demand analysis
- Front-end and back-end separation -> interface authentication -> data commonality -> database design
- Content Management -> Search -> Filter -> Points Management System
- Community Business -> Permission -> Points -> User System
Prototype design:
Prototype: The product frame drawn with lines and graphics, also called wireframe
Design: Consider the product objectives, functional requirements scenarios, user experience and other factors, and the rational ordering process of the various sections, interfaces and elements of the product
Product stage: Idea->Requirement Collection->Functional Structure->Prototype Design->Product Requirements Document
Prototyping is a clear expression of the system's conception
The goal of prototyping
- Show the logical structure of the layout
- Indicate state relationship and jump relationship
- Low-cost fast modification
Server demand analysis
- User, authority management
- Content management, homepage management
- Other functions (logging, multi-language, etc.)
WebApp/small program demand analysis
- Main function
- Technical realization/interactive experience
- User data and traffic entrance
Technology stack selection
- Combining team technical strength with business needs
- Be able to reuse, resolutely not make wheels; need wheels, resolutely not far-fetched
- How simple and how to do it, consider time, progress, and quality factors
Demand analysis tool
- Prototype: Axure, Ps, Ink Knife, Blue Lake
- Mind brain map: Xmind, MindNode(Mac), MindManager
- Flow chart: Visio(win) / OmniGraffle(Mac) / processOn