Top ten communication skills

Successful software products are built on the basis of successful demand, and high-quality demand from users and developers an effective communication and cooperation. When the user has a problem can be solved by the computer system, and the developers start to help users solve the problem, communication begins. Requirements elicitation is probably the most difficult in software development, the most critical, error-prone, and most in need of communication activities. On demand gets often wrong understanding: what is the user know that demand, we have to do is talk with them to get from them, just ask the users demand target characteristics, what is to be done, what kind of system to fit the business need, but in fact demand gets not imagined such a simple, this communication road covered with thorns. First of all need to get to define the scope of the problem, the system's boundaries are often difficult to clear, and users do not understand the technical implementation details, this resulted in the system target confusion.

Then there is the understanding of the questions, the user on the computer system's capabilities and limitations of a lack of understanding that any one system will have many users or different types of users, each user only know their own needs, but do not know the system as a whole, they do not know how the system as a whole better efficiency, but also not too sure those can give software to complete the work, they do not know what is the demand, or how to take an accurate way to describe requirements, they need developer help and guidance, but users and developers to communicate between a prone disorder, ignoring those that are considered to be very clear information. Finally, there is demand, because demand for instability often have over time, making it difficult to change. In order to overcome the above problem, you must have the Executive needs to get active.

Requirements for activities proposed to complete the task of 11 or steps are to determine the requirements process, the preparation of project and scope document, user group, select the user, select the user representatives, to establish the core team, determine usages, held joint meetings, analysis of user workflow, determine the quality of the property, check for the problem report and demand for reuse. Of course it should be according to the Organization and project specific conditions for appropriate reductions, such as the situation according to the project and user demand for Conference into a survey or discussion, and so on. 1. preparation of the project view and scope document system requirements including four different levels: business requirements, user needs and functional requirements, non-functional requirements. Business demand explains the new system available to the user's initial interest, reflected in the organization or the user on the system, the product of high-level objectives, their scope in the project view and described in the document. User requirement document describes the user uses the product must complete this task, use the instance document or schema script described in the notes. Functional requirements define the developer must implement the functionality of the software, so that users can complete their tasks to meet the business needs. Non-functional requirements is a user on the system in good working of hopes, including usability, responsiveness, fault tolerance, robustness, and so on quality attributes. Requirements elicitation is depending on the system of business needs to get the system user needs, and then through needs analysis to get the system functional requirements and non-functional requirements. Project view and scope document is from a high level description of the system of business requirements, you should include a high level of product business objectives, assessing problem solutions for commercial and technical feasibility, all functional requirements using instance and must comply with the standards. While the scope document defines project products including for all work and production of products used in the process. Stakeholders on the project's objectives and scope of the consensus, the entire project team should focus on the project objectives and scope.

2. user group classification system users in many ways the differences, for example: the use of the frequency and extent of the system, applications and computer systems knowledge, using System properties, the business process, access rights, geographical distribution, and personal qualities and preferences, and so on. Based on these differences, you can put these different users into a different user classes. And the Actor in the Usecase UML concepts, the user class does not necessarily mean people, can also include other application systems, interface, or hardware, this makes the system boundary interface also contributes to the system requirements. Classification of the user group and summarize their own characteristics, and a detailed description of their personality traits and task status, will contribute to the demand of access and system design.

3. Select user representative is not possible to all users for requirements elicitation, this time does not allow the effect is not necessarily good, there is a need to identify to determine needs and understand the business processes of the user as a representative of each category of user. Each type of user is at least one truly represent their needs as a representative and be able to make decisions on behalf of the user are often these three categories of person in the user: on the project has to decide on leadership, familiar with the business process expert, the system end users. Each user representative, on behalf of a specific user types, and in the user class and serves as the main developer of the interface between, users represent they represent user class gathering requirements, and representatives and each user is responsible for coordinating the user they represent in demand expressing inconsistencies and incompatibilities. 4. the establishment of the core team usually users and developers unconsciously a we and their ideas, produce an antagonistic relationship to each other on the opposite side, each define their own border, only to their own interests at the expense of each other's ideas. They document, records and dialogue to communication, rather than as a cooperation as a whole to identify and determine the requirements to complete the task. Practice has shown that this method is not correct, does a little benefits to both sides, good interpersonal relationship is not established led to misunderstandings and omit important information. Only when both participants can understand what you want to succeed, they need also to know what it takes to succeed each other, to establish a cooperative relationship. In order to establish a cooperative relationship usually adopt a team approach to get the requirements, the establishment of a representative by users and developers of the Joint Panel as the demand for

The core team. Joint Group will be responsible for identifying needs, analysis solution and negotiation differences, team members can use Conference, e-mail, integrated office systems, and other ways of communicating, but Exchange should observe the following principles: group meetings should be organized and in cubes, users and developers to participate in exchanges prior to determine; prepare and participation rules; subject to clear and cover all the key points, but the sources of information should be free; the Exchange destination to clear and inform all the members. 5. determine the instance from the user representative office collection they will use the system to complete the desired task descriptions, discussions between the user and the system of interaction and dialogue, which is used, a single use instance may include the completion of a task many logic related tasks and interaction sequence. Use the instance method to the requirements to obtain benefits from this method is used for task-centric and user-centric point of view, compared to function as the Centre and to the developer-centric approach, use the instance method enables you to better understand and recognize the new system allows them to do and what to do. When describing usage to succinct formulation of straightforward to use, try to use the active voice, the system or user as a subject, such as the user submits a user password, the system verifies the user password is correct, there is one point in the description do not design interface details, such as the user from the drop-down box, select the product type. Use the instance to later write a use case scenario describes the basic path and extension path provides footage.

6. the joint meeting held in the most common requirements elicitation methods is to convene a meeting or an interview, the joint session is a wide range of seminars, simple, and is also among the members of the core team is good communication method, the Conference adopted a close and intensive discussions to users and developers of the partnership into practice and can therefore develop requirements documents in papers. Joint meeting of the first issue is the reasonableness and necessity of the system, you must agree to all the members of the system is necessary and reasonable. Next you can discuss usage of inventory you can print a large paper hanging on the wall, written on the Blackboard or make presentations. On each list merge to remove duplicate items, plus the additional content you can get a total inventory, avoid using a negative too poor not feasible to deny the user in mind, these ideas should be preserved as consultative inventory entries so that the protection of a group member and open thinking. Last on the list for discussion, members must check each use case, put them into the requirements before you determine whether or not the project within the scope of the definition, formation of the final report of the demand.

In the discussion, you should avoid premature details, in a consensus on system requirements, user can easily in a report, or dialog box that lists certain precise design, if these details are recorded as needs, they will give the subsequent design process unnecessary restrictions, should ensure that user participants will focus on the topic under discussion for abstraction layer, the focus is on what to do and not do. Here it is important to let users understand for some features of the discussion does not mean that will implement it in the system, not to be implied or commitment when completing the requirements. After discussions, make a note of the entry, and requests to participate in the discussion of user comments and corrections, because only provide demand can determine whether it really gets the demand. When you finally get a more accurate demand report, meeting even if completed successfully. But to clearly demand process itself is an iterative process, in a later procedure activities inevitably going to modify and improve the report. 7. analysis of user workflow analysis user workflow observation of users to perform business tasks of process, through the analysis of the use of instance get system use case diagrams. Preparation of a use case diagram document will contribute to a clear system of usages and functional requirements, the use of the unified modeling language will help to further exchange with the user. Each use case descriptions should include numbers, for each use case is assigned a unique number, as demand for traceability provides convenient; participants, and the interaction use cases; a precondition of the actor, began to use cases before a necessary part of the system state; postcondition, cases completed system reach; the basic path, complete with cases, critical path is the path to the user's expectations; extension points, basic paths branching, indicates that an unexpected condition; field descriptions, path names for the further decomposition of the subsequent definition of the class attribute and the database field design; design, realization use cases of non-functional constraints. Write basic paths should use active statement; sentence to actor or the system as a subject; a sentence indicates that an actor, a sentence indicates that the system action, interdisciplinary performance interactive; do not involve interface details, such as user name in the text input, select type drop-down box. Use case: user registration, user registration as a member of the system

Number UC1 participant user pre condition users to access the system, the system is operating normally postcondition system records the user registration information base path 1. User registration request. 2. the system displays the registration interface. 3. the user to submit registration information. 4. the system verify registration information is correct. 5. the system-generated username and password to save your registration information. 6. the system displays information about successful registration, enter Member page. Extension point 4a. User-provided information is not correct: 4a1. Prompted to enter the correct information 4a2. Returns 3 added registration information including = users real name + phone + fax + Email + contact address address = provinces + city + street + zip design constraints registration response time must not exceed 3 seconds 8, determine quality properties in the function needs to consider non-functional quality characteristics, as well as to determine application because of the particular business environment to the system's functionality or performance constraints, this makes your products meet and exceed customer expectations. On the system how to properly perform some behavior or let the user take a measure of the statement is the quality attribute, this is a non-functional requirements. Listen to the description of sensible characteristics

Views: fast, simple, intuitive, user friendly, robustness, reliability, security, and efficiency. You are going to discuss precise and users to define their vague and subjective words really means, and you want to assign mass properties to each use case design constraints. 9. check the problem report has been run by checking the current system of problem reports to further improve the needs of the customer's problem report and supplementary requirements for new systems or new version offers numerous improvements and increasing the richness of ideas, to provide user support and help people to gather requirements process provide very valuable information. 10, demand for reuse if the customer requested feature and existing systems are similar, you can view requirements are flexible enough to allow reuse some of the existing software components. Business modeling and field construction mode needs the best way to reuse, like analysis mode and design mode, the requirements also has its own mode.