Comments on the team project and analysis of the project requirements

Comments on the team project:
The team project is the direction that each team member is working together, the establishment of the team goal should be as early as possible clear, in order to have a holistic plan, so as to improve the team's executive power.
In this knowledge is increasingly updated, technology is changing rapidly, increasingly fierce competition in the era, for the team to rely on experience to walk the world is long past, learning-type talent is the base of the team, to better adapt to this era, improve the team's construction, improve team competitiveness.
Analysis of Project requirements:
Requirements analysis is a complex process of understanding user needs, agreeing on software functions with customers, estimating software risks and assessing project costs, and ultimately forming a development plan. In this process, the user is indeed in the dominant position, the demand analysis engineer and the project manager is responsible for collating the user needs, for the subsequent software design lay the foundation. The main steps are as follows:
I. To communicate with the user before communicating fully
second, actively understand the customer's business and related knowledge
Third, the correct classification of users
Four, to guide users to fully express their ideas
five, to determine the priority level of demand
Vi. Analysis of requirement feasibility
Vii. correct understanding of requirements Analysis Document confirmation
Viii. The user workflow should be understood in the field
here is a typical example:
1. After a preliminary interview, the developer and user write "Product requirements" and distribute the respective product requirements to the attendees before the meeting.
2. Ask attendees to carefully review the product requirements prior to the meeting, list the objects that are the system environment variables, the objects that the system will produce, and the objects that the system will use in order to complete its function. In addition, each attendee is required to list the services (that is, processing or functionality) that manipulate or interact with these objects. Finally, you should list constraints (such as cost, scale, finish date) and performance criteria (such as speed, capacity). Everyone's list doesn't have to be exhaustive, but hopefully everyone will be able to accurately express their understanding of the target system.
3. Show everyone in turn, everyone in the list of items in the discussion, you can do appropriate screening and combination, and then everyone agrees to pass, in this process is strictly forbidden criticism and controversy.
4. After the display, you create a list of combinations for each proposal. Remove redundant items from the combined table, plus new ideas that were generated in the discussion in the previous step. Until each topic list is set up, you can create a consistent list of issues for each topic.
5. You can create a specification for each list after you have a consistent list of comments. For example, the exact description of the word or phrase in the list, further refinement work.
6. A complete software Requirements specification is drafted by one or more participants based on the results of the meeting.

Comments on the team project and analysis of the project requirements