Project Management of Computer Software Requirement Analysis

Paper Keywords: demand side stakeholder analysis of user needs Project Manager Analyst
Abstract: Computer software project management to improve software quality requirements analysis is the basis of the decision is key to the success of a software project. This article describes the needs analysis study to explore some effective measures.

Public view the development of domestic Computer software industry, far less than other Western developed countries outside Europe, with per capita GDP in China compared to India is also not as far away from the disadvantages of the software industry is seriously hampering the development of China's IT industry. China's software industry disadvantage reflected in the maturity of the software developed small, and the development of large software engineering projects (such as ERP, etc.) failure is defective or fully developed. Currently, the state is to increase the Research on software engineering and software engineering talents. According to statistics, demand analysis is caused by defects in software design errors and software failures account for about 6400, and is the error code only software failure 360a, the data show that the needs analysis is to improve software quality is determined based on the success or failure of a software project the key. software project management knowledge through a systematic study of their involvement in recent years, combined with some of the software project implementation experience, introduced in the demand analysis to explore some effective measures.

A user familiar with the project as soon as possible side stakeholders picture
The user side project stakeholders, that all may be a significant impact on results of the project, that project risk, he may be the beneficiaries of the project, the project may also be victims. Therefore, the project should start from the beginning, the demand Project members will Fenqing analysts and their projects include client-side stakeholders who and what organization, communication and coordination through the influence on them, driving their support for the project to investigate and identify their needs and aspirations of the project reduced its resistance to ensure the success of the project.

Needs to do some projects in the survey, the progress requirements due to objective factors, demand analyst's technical department and construction unit of the exchange more practical to the business management department and not enough in-depth user surveys, resulting in software after the trial may no longer needs to do a major adjustment, "start over" part of the high rate of progress requires much more than time. Therefore, users familiar with the project stakeholders picture side is the first step in a needs survey is the basis of needs assessment. In custom development projects the user side project among the stakeholders, most importantly, the construction unit of the personnel organization, business relationship. it is better to use the picture of the organizational structure of the organizational structure of the unit; in the relevant units should also be based on the organization chart to draw all the items client-side stakeholders structure in order to better carry out more comprehensive Research and analysis needs; with responsibility matrix to determine the part of the Research object; to establish Research contacts the object during the Research and analysis to ensure timely communication.

2 needs to take the right approach to get
The purpose of software development projects is to implement the project needs of the user side, the project needs of the user side include explicit and implicit, can be divided into NEED, WANT, WISH and other different levels. If the project stakeholders of all parties without the user for adequate communication and influence, to the extent possible, participate in the project, there will be customers who do not clear the responsible party or the scope of and demand for accountability is not strong, the demand has made arbitrary, the project recognized early enough for the needs of active , or more than one user on behalf of each side, yesterday was this non-project post-random phenomena such as changes in demand, which will result in the spread of the project scope, schedule delays, cost increase, or even complete failure of the project.

Various users of the system have different requirements, such as concern for an inexperienced user whether the system is easy to use products for advanced users are concerned about ease of use and efficiency. Therefore the need for users to classify each user class will have own series of functional and non functional requirements. In the project, to identify and describe the product as soon as possible the different user classes, allowing users from each class represents a key to get different needs.

Needs of the project has a double nature (users and developers) and multi-faceted (the project of the stakeholders) and therefore, project managers and systems integrators should be aware of the user stakeholder needs, the user stakeholders should understand the technical requirements, the two are indispensable. the right needs to get to know the source of demand, the user's classification, the user's representative, who is in charge the number of user demand and other factors. developers and project managers have enough patience to listen to users to talk, to be sufficient detailed understanding of every detail. project managers will need to be good at classification, classification, documentation will be good demand, and some check marks.

3, visualization of research needs and guide them to the needs of all customers tap
Some customers because of their lack of Computer knowledge, unable to submit complete and accurate, implicit or potential demand. If these requirements can not meet will result in the user's dissatisfaction. So should be good at research and analysis needs of users would like to think, not only to establish a clear demand, but also good at inspired way of implied or potential user needs and tap combination of research and analysis techniques exciting exceed customer expectations demand. This requires research analysts need to know to complete as soon as possible related businesses, which can stand in the position of the user look at the software requirements, like users would like, do a bridge between business and the Computer. demand for research using a visual method can inspire users to dig deep into the potential demand. demand for research is to use visual charts and other tools to inspire and guide the user needs a clear narrative, and the demand for more comprehensive improvement.

For the senior leadership, the system can provide the overall framework map; for business management, business process diagrams can be used to describe the old and new systems of business processes; for customers in the technical staff can use data flow diagram, entity relationship diagram or in the UMI kinds of graphics on the system description of a variety of angles; and for business managers, customers and technical personnel, as well as the processes at all levels of users, to draw to the needs of the user interface graph mining, is a more effective means of communication.

Special note here about the importance of the user interface. User interface design is reasonably the responsibility of software design, of course, customers themselves have a special request on the interface is excluded. However, if demand for it in advance to discuss the investigation with the customer, research needs can greatly improve the results. because then the system for the future customers do not have a concept image, or have a vague notion of expected needs expression, validation, clarity, perfect to the author's experience, painting sketch out user interface with customers to discuss, can greatly stimulate their demand to provide more accurate and comprehensive. the original collection of information, describe the business, indicating that the system model to a dead end it, and it can achieve the effect of vista.

4, a detailed description of the business, so that all customers confirmed
Comprehensive and detailed as possible to investigate and describe the original system and the user wants the future of the business system has a process, and documenting these business processes with customers after the discussion on errors or inaccuracies inaccurate description of the modifications, the final allow customers to confirm. from software developed in recent years to see, to understand the business process integrity and accuracy is very important. While the data for both SIDUT (additions and deletions to pass inspection), but the specific business is divided into several steps, each step has its business name, the same steps may be different on multiple data sets, you need to design a survey to understand clearly the characteristics and habits for business users of software, developed software that is more popular. of course Summary of design software, to try to eliminate the constraints of the business process, that is the business process in the node working as an independent object, the full account of their business objects and other interfaces, business objects passed between the process of mutual Call to achieve its business processes, so that limited the business process changes occur, they can be convenient to modify the system program and implement new requirements.

For the business survey data can be collected on the following analysis to complete, the information from a variety of items the user side stakeholders: to follow the standards, the organization paid work manuals, operating procedures, the business of the parent notification , act in the business guide for business to fill the registration form and all relevant statistical reports collected by other means introduction of similar systems, technical information and so on. reposted elsewhere in the Research Papers Download http://www . hi138.com 5 user side of the project stakeholders to balance the desire
The user side a different project stakeholders to pursue their aspirations and goals are often very different, so the user side of the project stakeholders to balance the desire to be very important and very difficult. For example: I have a Computer in a hospital involved management system project, the hospital management would like to meet as many items of information collected for a variety of data, statistical analysis, and in order to control the information and increase the number of the approval process; and clinics, pharmacies and other foreign office The primary window is because the passenger wish to reduce the pressure on the speed of the input amount of information items; even some of the primary sector due to fear of adverse establish transparent information systems will affect negatively the interests of their deal, the so-called inverse demand; and customers Customer (treatment of patients) hope the relevant agencies to streamline workflow, speed things up, increasing costs of diagnosis and treatment of transparency; and even the team itself, because the technology, resources, schedule and other factors, some of the features need to prioritize and choice. While not all needs are meet, especially the negative inverse demand is not acceptable, but should consider their needs are fully and be balanced.

If a different user side stakeholder needs are inconsistent, then the decision must be the type of client-side to meet the stakeholder needs are more important. Understand the possible use of the product categories of information to customers and their business objectives and product usage relationship how, will help determine which users share a larger class. If the demand for systems analysts and developers to make the conflict want to develop the system, usually due to system analysts as the agent of the customer and market demand with a heavier weight, but analysts can not indulge in the system to accommodate customer needs.

Different user side stakeholders may require the products according to their own preferences to the design. The use of the project's business objectives to determine which issues concern you the customer, non-core customer's needs can be arranged in the next version of development. When developers think products and customer needs conflict, should normally be made by the customer decisions, however, do not fall into the "customer is always right" trap to go, in reality, the customer is not always right.

6 stressed the need to achieve the level of progression of the project
The project is to understand the system or the user can provide the least cost. As expected not support funding should be considered when the project phases. On the system, boot the user of the technical proposals, allowing users to understand the integration of suppliers work carried out to understand integrators to help customers achieve his needs, to achieve the user's purpose, not just to make money, the user a better understanding of integrators, and more understanding of their own systems, is conducive to future cooperation projects, project implementation and system maintenance.

Analyze the user has used the system model, data structures and library mode to see if maintained, sharing, transformation, which involves protection of user investment. Under the current traffic situation to determine the work of the existing work patterns may occur in the future should take into account the changes, expansion, new requirements, and with the same international standards might bring change. examine the implementation of the project environment is guaranteed, especially in network engineering, you must fully understand the user needs survey the field of implementation of the environment, when not with the implementation of environmental When asked for supporting the design and environmental transformation.

7 writing needs a needs assessment of the text block and the other project team members and improve the system requirements for collaboration
Documentation is an important asset integrators, system integration and throughout the entire process of project development, including legal documents, technical documentation, information text block. Text block requirements of integrity, consistency, modifiability, traceability.

Based on the needs to the original work is completed, needs to fix the error requires a lot of work, research shows that: the development phase than in the demand for an error discovered by the customer, then fix the error need more time to flower to fold. So it requires needs assessment. demand the end of the review criteria: have a clear explanation of all the issues raised by the inspector, has the right to modify the document, the revised document grammar checking has been done, all the TBD issues have been resolved, the document archive.

Requirements document is complete, not throw it behind the designer on the matter. As the other members of the project team, the effectiveness of demand also played the role of some degree of validation. Although the software project life cycle in accordance with the various different stages of development model division, but the end of each stage is not simply the phase of members of the next phase of the results superimpose on it. especially the high-tech software development projects, the last phase of the work often through many of the communication can be more clearly members of the next stage of acceptance, its validity, rationality must be the work of the next phase of testing, inspection and sometimes by the need to work on the results of the previous phase and make the appropriate adjustments, needs analysis as well. Therefore, whether the same among different stages, or among different stages should be based on the need for mutual cooperation, mutual support for completion of software development tasks. reposted elsewhere in the Research Papers Download http:// www.hi138.com