UML object-oriented design and development
In the school study, learn the software development process, and know the documents generated in the software development process, the management of the software development team, etc.
Ask yourself questions, think about them carefully, improve your software development chain, and build a complete conceptual model of software development. If you forget it later, you can review it in time.
process:
Received project-->User research-->Summary analysis of demand function-->Feasibility analysis-->Demand analysis (using power designer to design requirements, use case diagram)-->Summary design (system environment construction, development tool preparation) --> Detailed design (module design) --> Database design --> Coding --> Test (unit test, integration test, system test)
think?
In each process, how to arrange personnel? What documentation output is there?
How to accept the project?
How to conduct user research?
How to perform a requirement function profiling?
How to conduct a feasibility analysis?
How to conduct a needs analysis? What is the process like?
How to do the outline design? What is the brief design document specification?
How to carry out detailed design?
How to do database design? How to optimize database query?
How to convert from detailed design to code? What if there is no detailed design during the software development process?
How to use the knowledge of testing to avoid some mistakes in the software development process?
Which model should be used for small software development? What models should be used for large-scale software development?
Note: "Software Method" says that direct mapping from requirements to design will lead to functional decomposition and duplicate code. If you define requirements from design, you will get a lot of fake requirements.
2014/4/27
1. When we receive the project, we will carry out the feasibility analysis of the software, including the technical difficulty analysis, time analysis, and workload analysis of the software.
2. After the feasibility analysis is completed, it is necessary to conduct a user demand research, carefully check the unclear places in the user demand, and the generated documents include user demand documents.
3. After the analysis of the user requirements document is completed, business modeling is carried out. Most of the software in our life depends on reality, and the modeling at this time is the modeling of the real business process. In the process of business modeling, business use cases, business activity diagrams, and business process books will be generated.
4. After the business modeling is completed, communicate with the user again about the unfamiliar places until the user confirms. At this time, the system modeling is carried out, and the system modeling is divided into modules. The generated documents include system use case diagrams, system sequence flow diagrams, use case specifications, and user prototype diagrams.