By project development in computer science one understands the entire process partially also beyond that about the identification of the need up to the start-up of an implemented IT-solution. Main object is partial the supply and introduction of a application software, zzgl. the necessary hardware and networks.

The software which can be implemented can be either an individual conception, an industry solution or only a combination and a configuration of standard software. Projects are carried out often of or with external service enterprise, frequently in addition, as self-development. Accordingly variously also the proceedings are during the project development: from a very much structured approach, see water drop model, over different combinations up to very flexible, open methods like the Agilen software development. Accordingly also between Top down and Bottom UP beginnings one differentiates.

In the following some important aspects and typical stages/phases of the project development are described, which come in practice more or less pronouncedly to carrying.

Project management

The entire process of a project development is subject usually to a more or less strongly minted project management. In case of the realization by a IT-Dienstleister usually both on client and on contractor's side an independent in each case project management is operated. In order to dissolve conflicts between the two projects manager, that superordinately often still another control committee compound from the management of client and contractor (Project board) is used.

Typically for larger projects also a larger project management expenditure is operated, while middle or smaller projects are completed frequently "“besides"”.

Quality management

Something similar applies to the quality management, which achievements which can be furnished by appropriate measures a high quality of all is to implement, and not only programming. Basis of the quality management are in-house Regularien, individual agreements between clients and contractor, and partly also standard such as ISO 9000ff, whose all too strict interpretation for the software production is however disputed.

The quality management is often misunderstood as part of the project management. The quality manager should not be subordinate however straight to the project management, so that the date and rising costses of the project cannot impair the quality. Furthermore the quality management has also the task to supervise the project management as such.

Systems analysis/Consulting

By Consulting (or on German "“conceptions and consultation"”) one understands generally consultation of any kind, often about specialized consulting firms performed out. In connection with the project development here however the systems analysis is meant for project preparation. Article is the contentwise collection of the requirements by questioning of future users as well as the systematic investigation of further material and technical requirements and boundary conditions (interfaces to third systems, legal requirements u.dgl.). Result is usually a specialized concept, often also equal a product requirement specifications draft.

The topic of the Consulting should always "“WHICH"”, and never "“HOW"” be. Although i.d.R. desired, the Consulting does not write very frequently, intended or unintentionally, already fundamental technical solution methods, products or platforms for the future realization firmly. Therefore it is disputed whether and to what extent the employment of consulting firms as direct project preparation is at all meaningful. At least the risk that external advisors pursue here self-interests always exists, in order to provide or connected enterprises advantages with the following placing of orders for the client. Also unintentional technical definitions can be because of the competition restrictions for the client, resulting from it, from large disadvantage.

Product requirement specifications production

Product requirement specifications contain all functions and requirements to a program. Therein one specifies, which functions are required and which these to do exactly. The description should come from the view of the final user. On the basis this overview the fundamental technical draft decisions are met, and from this the architecture is derived. In case of an agency of a service enterprise product requirement specifications are the contractual basis for the agreed upon achievements. Therefore are the completeness and correctness of the definitions and requirements met therein of special importance for the client.

System Design/technical conception

A system analyst and/or - designer, with smaller projects also the programmer, specifies program architecture on the basis product requirement specifications. As far as standard software products are used, also a specification of the planned product integration takes place and/or - adjustment in this phase. For software which can be developed again take place the draft of the data model and the individual functions and algorithms and/or the object and class structure. If already existing software (adapted) become adapted, then in this phase one specifies, which changes and extensions are necessary. The result of the system Design is called also data processing concept.

Implementation

In the implementation phase mentioned the application solution conceived before will be adapted technically realized, by program products configures, existing software or programs and/or program sections will completely again be provided.

A creating anew of software takes place usually via programming, i.e. the individual functions, objects, classes etc. are coded in a programming language with the help of an integrated development environment. Due to the high costs of programming also alternative procedures are used, like e.g. universal Application. Furthermore to increase also procedures are used, the Mehrstufigkeit of systems analysis to dissolve system Design/conception and following implementation see e.g. under prototyping, Agile software development.

System and procedure test

The provided software is tested both in two different regard, on the one hand

• technically (systematical test), i.e. on a correct conversion of the data processing concept and on program errors, and on the other hand
• contentwise (procedure test), i.e. on completeness concerning product requirement specifications and suitability for the intended purpose.

While the systematical test is an exclusive affair of the contractor, the procedure test takes place usually in co-operation with the final users of the client.

It applies in the software development as normal that programs are incorrect. Often even whole parts must completely again be converted, thus again programmed. Since with security it can be never excluded that changed program sections can affect not different program functions, takes place after the error correction usually a renewed complete test of the overall system. Up to the final release of the software usually several test and error correction cycles are necessary.

Installation

The finished software together with possibly necessary standard software products, hardware is then up-played in the course of the installation on the computer systems of the client or the operator (a Application service Providers) and made ready for use. Here often between parallel "“productive"” -, "“test"” -, "“training"” - and "“development"” - installations one differentiates.

Depending upon technical platform the installation on central computers (servers) takes place or on the personal computers or both. With applications of data bases if necessary still another Tuning of the data base takes place. In some cases still another aged data assumption from older application solutions takes place.

With larger projects often first only one installation on a test system and/or with few pilot users takes place. On further locations one calls the following expansion (installation and start-up) Rollout.

Introduction support

Substantial part of the project is the introduction support, in particular in the form of training and/or briefing of the final users, power user and administrators.

There are very different training concepts. A larger number of users is trained often over s.g. "“multiplicators"”. Multiplicators are users, who train again further users. One calls this procedure also Train the of coach. Increasingly the user training is made also by Internet with appropriate applications of training.

Servicing/Maintenance

After the start-up of a software solution a continuous far support is usual by the contractor. This covers both a support of the users by Hotline and so far necessarily suburb achievements. This is regulated frequently in a support contract. Here between a roofridge level support and a Second level support are differentiated. The roofridge level support is ensured often by the client and receives all problem messages. It passes however only serious problems on to the Second level support with the contractor and/or product manufacturer.

Constant up-dating of the software changing requirements and of new versions of used standard software is actually called "“software maintenance"” and regulated also in appropriate contracts. One calls the management of subsequent bringing of changes into a current system CHANGE management.

see also:

• Software technology
• Outsourcing
• Offshoring and Nearshoring
• Project development (term clarifying)

Articles in category "Project development (computer science)"

We found here 57 articles.