Experience in system analysis (1)
A system has two implementations from deciding to develop between formal online: user demand implementation and code implementation.
First, user demand implementation
The user faces system analysts, and users describe business processes to system analysts.
1. The user's pertinence.
Collection needs must be collected is the user's expectations and requirements for the system. Instead of responding to a few people, or some people, this cannot represent the true role of users in the system. You can't really divide the user's permissions.
2. The user's business process.
Users will implement all the processes to the system analyst. System analysts must analyze which are immature in these processes, which are contradictory in business processes, which is often changed. There is absolutely not to be implemented in the system in the business process; simply, some parts often change in the user business process are not implemented in the system.
3. User needs are not necessarily reasonable.
System analysts should be reasonable. Too many obstacles hinder the judgment of system analysts for the rationality of user needs; but the user's demand should be implemented, the method and way of implementation should be confined to determine the system analyst, and the user's proposal is just a reference. System analysts cannot chase the user's demand, otherwise it becomes a system that the system will change because of the user's demand.
4. User needs implementation is divided into two phases:
The overall logic design of the user needs in the first stage.
Complete system business flow chart, interface design, database design, system modeling, user demand document description, main target system overall logic feasibility, integrity, all logic situations, logical branches need to be considered! This document serves as a software specifications external manual (abbreviation PES), which is a basis for software assistance and subsequent technology implementation details. After the PES is completed, it must be confirmed by the user, which is necessary to ensure that the user agrees to the system design phase. Here is the core of the user's demand implementation. If fully followed by user requirements, the system is largely lost, self-adaptive, and self-regulatory, failed, adaptive, self-adjusting system, will be oppressed by users, constantly implementing new user needs I finally walked to death. How much is user demand, what is the extent? There is no answer, only experience. Experience is your own experience and experience. The second phase, the technical details of user needs.
According to the document in the first phase, the above document is implemented by technology. There must be a SQL statement for the database; the name or class of the implementation of each button in the interface. In this process, the software design internal manual (abbreviation PIS) is formed. PIS is the refinement and re-REVIEW of PES, which can discover the shortcomings in PES before coding, and you can make a step again, make concessions and adjustments to make a step on the technology itself. Some people say that technology can achieve anything, in fact, in a limited resource and limited range, technical strength and strength, sometimes make concessions, do not be impeded to be omnipotent, it is confused, its Prerequisites are technical strength, human resources and time must be infinite, then technology is omnipotent! After the PIS is completed, the PIS designer should be explained to the PES designer to see if the idea is achieved, and whether the idea is achieved. The system must not be developed in PIS and PES.
These two phases should not be the same person or not the same group, the second stage is the analysis and admission of the first phase of technology implementation, and is also the basis for programmer Coding code. The SD writes PIS according to PES and the system is divided into the module or according to the human hours, as the project is officially developed.
Little experience, writing here, the memo is mostly for everyone's reference, maybe just a little bit.
