The entire process of project development is usually subject to a more or less pronounced project management protocol.
In order to resolve conflicts between two project managers, the superiors often composed of the management of client and contractor supervisory committee (Project Board) is used.
Typically, a greater project management effort is expended during medium or larger projects.
Often, external IT consultants are used to complement and support the people involved in the project execution.
The quality management within the project is understood as part of the project management. It includes the sub-areas:
Quality planning, that is, identification of relevant quality criteria for the project and the methods by which they can be met.
Quality assurance, that is, regular and rule conformity assessment of project performance to ensure that the project meets the quality standards.
Quality control, ie monitoring the project results to determine whether the quality standards are met, and to eliminate the causes of under-performance.
The quality management in the project must include both the performance of the project and the project product appeal.
Modern quality and product management complement each other. Both disciplines recognize the importance of
Prevention goes before checking
Quality improvement programs that are conducted by the sponsoring organization, such as TQM or ISO 9000, can be integrated to improve the quality of the project and the product.
As generally in project management, the permanent conflict between quality, cost and time has to be taken into account.
In software projects is the project management often under tight deadlines and be exposed to a particularly high risk of neglecting the quality.
Due to the complexity of information systems, absolute safety and quality are not economically viable.
Therefore, often the risk management methods are used for categorization and prioritization to ensure an adequate level of system safety and quality for the project.
Aspects of risk management should over the entire system cycle, be considered on the development or programming , implementation, and configuration and during operation to decommissioning of the system.
The project development elicitation is meant for preparing the project system analysis.
The objective is the substantive requirements to capture through survey of future users and the systematic investigation of further factual and technical requirements and constraints (interfaces to third party systems, legal requirements, etc).
The result is usually a technical concept, often equal to a specification .
A specification contains all functions and requirements of a program. It will specify what functions are required and what they do exactly.
Based on this overview, the basic technical design decisions are made, and from that, the system architecture is derived.
In the case of an assignment of a service company, the requirement specification is the contractual basis for the agreed services. Therefore, the completeness and accuracy of the measures in specifications, as well as requirements of particular importance to the client.
System design / technical concept
A systems analyst or designer defines the architecture program on the basis of the specifications.