First, the needs analysis
What (a) is
Speaking of software engineering, requirements analysis can not be separated. As the name suggests, in fact, needs analysis is clear what software or system needs analysis, and ultimately show up in the form of documents and charts.
Needs analysis is divided into specific functional requirements, non-functional requirements and design constraints in three aspects.
1. Functional Requirements
That software functional requirements which matter in order to provide useful features to their users actions need to be performed must be done, what functions must be implemented, as well. Functional requirements are the main software requirements. Developers need to personally communicate with users to verify the user's needs, from software helps users fully complete description of the behavior of external affairs on the angle, forming a software requirements specification.
2. Non-Functional Requirements
As a complement to the functional requirements, software requirements analysis of the content should also include some non-functional requirements. When including software requirements for performance, operating environment requirements. Software design must follow the relevant standards, norms, specific details of the user interface design, possible future expansion programs.
3. Design Constraints
Generally referred to as design constraints, typically for some implementations or design constraints described. For example, the required software must be developed using Oracle database systems for data management functions, it must be based on Linux runtime environment and so on.
(B) Why
In order to reduce unnecessary workload, and ultimately make customer satisfaction, customer confidence in the product.
(C) how do
Needs analysis is an iterative process: requirements elicitation -> needs finishing -> Demand verification -> longer needs to capture ......
Second, this project needs analysis process
Initial contact with this project, is the teacher to the project summary table. After reading the contents of the project given by the teacher, we have a general understanding of the project. After determining the project team to meet with the instructor, a teacher at a certain poetry appreciation class app an example to explain the function of project needs and requirements of our Competitive Analysis. Here we stand on the one hand, the angle of technical personnel to conduct needs analysis - what kind of products to have their own foothold in the market? On the one hand it is to analyze the perspective of users - what do we need?
In the analysis of competitive products, I mainly look for is the data source. Because our project is a digital museum couplets, then the stored content crucial to the museum. So I searched a lot of information, a lot of browsing the site, find the information. However, there is an expression of the first to bring a malpractice poor communication - the next meeting, the teacher specify the data sources: couplets Association official entry. I did some unnecessary work, a waste of time.
After the analysis of competing products, we have a team for the future to learn more about job content, summarizes the problem, and the formation of a preliminary document. Then we contact the teacher to open a formal meeting, the meeting teacher app functionality is described in detail, answer our questions. We combine the teacher after the meeting to convey the needs analysis of the specific features of the app, write specific examples, complete needs analysis document.
The next step is prototyping. A beautiful sound front-end interface is the same product competitiveness. At the same time, the prototype also allows customers to more intuitively understand design as well as the progress of our technical staff conceived to facilitate the exchange of Party A and Party.
Good design prototype, wrote the first edition of the demand analysis document, the person in charge of couplets about teacher associations to communicate. At the meeting we discovered a surprising question - our thoughts and ideas have a lot of people in charge are not the same! On the introduction of software engineering class, the teacher said some customers are not very aware of their needs, required developers to give ABCD version selected for their conduct, some customers have a clear understanding of the needs, the needs of developers in order to design modeled It can be. Couplets, head of the Association belong to the second, he had a specific vision for the software modules developed by hope, if we start to meet him, then design the software will not necessarily be the current situation. At the same time, he has some ideas on software with our current time and ability can not be achieved. After making communication and understanding, we cut the head of the proposed software features. Taking into account the learning costs and project completion time, we feel that giving up the original app development plans into the development of small micro-channel program, the two sides reached a basic agreement.
Third, think
1. timely communication
Needs analysis starting with research needs. Demand research needs analysis is the most important part, both require that we have an understanding ability, design ability, we are asked to have one with people, the ability to communicate.
In the prototype design at the beginning, we based only requires the teacher relayed Association, the Association did not communicate with the person in charge, which led to an error in communication. This error is a direct result of our prototype is not very consistent with the idea of association, the head of the Association of ideas let us look ignorant, we need to prototype, the database is relatively large changes. I think we should start to communicate directly with the person in charge of the Association, will improve work efficiency, the results are more than satisfactory.
2. All functionality is not raised by customers to be realized
Customer demand is often presented without regard to the original technology, proposed by non-computer based on the operating mode of administration. They raised a lot of demand is often impractical ideal, after all, the non-technical customers. But as a technician, needs analysis must be realistic, achievable based on the angle technology to consider, so we must be based on technology to guide customers.
For example, in this project the customer's "Video Center" and charging functions we do not have the time nor the way to achieve, this can only communicate with our customers to reach understanding.
3. The recommendations from the technical and functional user's perspective
When the analysis of this project, our team is not only technology, it is also user. When the Association official expressed the hope that the beginning of all registered users of our real-name system is more opposed to - as a user, a lot of people do not want to open personal privacy to others. These also need to be negotiated.