Task 1: Course Introduction
Course objectives:
1, further understanding ASP.NET Core authorization and authentication framework, MVC pipeline
2, master Oauth2, combined with Identity Sercer4 achieve OAuth2 and OpenID Connect Server
3, master ASP.NET Core and Redis, MongoDB, RabitMQ, MySQL with the use of
4, understand DDD, learn to analyze and modeling in the field of project and project development using CQRS
5, master Docker, and be able to take advantage of Docker + GitLab CI / CD package of the rapid deployment of test environments
For groups:
ASP.NET Core've mastered the basics and want to project combat become a modern enterprise Internet standards ASP.NET Core Senior Developer
Task 2: minimum viable product MVP
MVP is a way to avoid the development of a strategy to develop products to customers do not really need, it is fast to build a set of minimum functions in line with the intended function of the product, and to improve the iterative, allowing the development team to achieve a product with minimal costs, in order to maximize the level of understanding and verification of users solve problems
We need to find between the minimum and the availability of a balance, neither put all the functions add to the mix, does not mean that the less developed function better, in a version of the launch, at least to meet some of the needs of users
Build => measure => learning, forming a feedback loop, in the process user-centric problem, rather than solution-centric; focus on the basic needs of customers, through customer feedback, and gradually revise product design and implementation; in all iterative process, made out of products is always available to a customer's product
Task 3: two software development model: Waterfall and Agile
waterfall:
In stages, each stage is very clear, from planning and development, to on-line, the whole process is very clear; every stage include: problem definition, feasibility studies, requirements analysis, software design, coding, testing and maintenance; to be on a stage there output was then to get to the next stage; the whole cycle is about six months to a year between
Problems may occur: early needs to spend a lot of time, because if the demand is not determined good, later in the development process may need to go back and change the design, a very large impact on the overall architecture
Features: Milestones, stressed that the document, emphasizing the division of labor, avoid change, negotiations and planning
agile:
Features: iteration, working software over comprehensive documentation, help, communication, embrace change, cooperation with customers
Scrum: roles, artifacts, events
Character
- Product Owner Product Owner
- Scrum Scrum Master director
- Team development team
Workpiece
- User Stories UserStory
- Product Product Backlog Orders
- Sprint Sprint Backlog Orders
- Sprint burndown Burndown Chart
activity
- Plan will Sprint Planning Meeting
- Daily legislature Daily Standup Meeting
- Review Meeting will be assessed
- Will reflect / review will Restrospective Meeting
Course Link
http://video.jessetalk.cn/course/explore
This work is Creative Commons Attribution - NonCommercial - ShareAlike 4.0 International License Agreement for licensing.
Welcome to reprint, use, repost, but be sure to keep the article signed by Zheng Ziming (containing links: http://www.cnblogs.com/MingsonZheng/ ), shall not be used for commercial purposes, be sure to publish the same work based on the paper license modification .
If you have any questions, please contact me ([email protected]).