Web Site

Economy-point.org

» Economics » Management » Business process management » Procedural model (software)

Printer Friendly FormatPrinter Friendly Format
Bookmark page - Procedural model (software)Bookmark this page
Back to Business process managementBack to "Business process management"
Page modified: Friday, June 23, 2006 20:30:58

A procedural model for software development (also called software life cycle) is a procedural model adapted for the software development. It serves to arrange and make the software development controllable clearer.

Since complex software is to provide only with difficulty and be waited, software developers of a plan avail themselves for the development of software. This plan (the procedural model) divides the development process into visible, temporally and contentwise limited phases. The software is thus step by step finished.

Procedural models split individual activities up on different phases in the development process and these become then - possibly with small modifications - once (e.g. Water drop model) or several times go through (e.g. Spiral model). With repeated runs an iterative (i.e. repeated) refinement of the individual software components takes place. Around the optimal procedural models disagreement prevails. Usually it behaves however in such a way that static ever and the linear viewpoint are to do the less have it with the practice of programming.

Procedural models differ substantially in their degree of detail. There is OOTC Approach, rationally Unified Process, rapidly Application development etc. details prepared proceedings, which give at the development concrete work instructions to taken part one to the hand. The V-model in this connection by the way takes a hermaphrodite position: It is both a principle (that each stage corresponds to the development a test phase) and (as mostly common) a detailed model.

The Agile software development concerns itself with methods, which let withdraw administrative aspects work the developer creatively and. Alternative software technologies (universal Application, software Fabric pursue beginnings, which question the conventional proceeding of software design and following programming in principle, as prefabricated universalisierte software is adapted by configuration to the respective requirements.

There are different appraisal procedures for the software process, among other things the Capability Maturity Model (integration) or "“Spice"”.

Types of procedural models

There are three different types of procedural models:

Software development processes serve a software development from the conception to the employment in the genuine enterprise for the control including the changes of a software resulting in the genuine enterprise. One of the oldest models is the water drop model, which accepts a rigid succession of the individual phases. Advancements like the spiral model plan however iterations, i.e. the same work procedure (e.g. the analysis) is several times gone through and the results of the work procedure per run is refined and improved).

see also: List of software development processes

Software life cycle management extends the phases over the entire life cycle of a software. The procedural model defines the requirements to lived processes ("“which"”) and describes the concrete, lived processes ("“how"”). This type is a mixture of an actual description and normative default. Depending upon standardisation degrees different Entwicklungsstufen will assign. Enterprises can very often be able these Entwicklungsstufen of external places to be certified.

  • Standard ISO 12207
  • Capability Maturity Model
  • Capability Maturity Model integration

Software development philosophy corresponds to a programmer philosophy, a certain beginning, as software should be best developed in opinion of the Proponenten. These philosophies contain very often also process elements and therefore as processing concept are likewise designated.

  • Extreme Programming
  • Prototyping (software development)
  • Rationally Unified Process

Criticism

  • A purposeful procedure improves the clarity of the overall project, the co-ordination of teams and helps to recognize errors promptly. This affects the quality of the entire system usually positively and/or permits an exact reconstruction of the development process and the decisions lying to reason.
  • Predivide procedure after a procedural model:
    • Manual for the system development
    • project-accompanying documentation
    • Person independence
    • early error recognition by fixed test activities
  • Procedural models give a framework, within which a project can run off arranged. The procedural model helps to structure and reconstruct the expiration of a project, since it describes the process and the documents of the software production. The quality of the software which can be provided depends in contrast to this on the project-taken part. It is important the fact that they possess a large foreknowledge, well co-operate and trusts their healthy human understanding. Project success and not the procedural model is the primary goal.
  • Several suggestions existed parallel to each other, without one of the procedural models would have become generally accepted in practice with broad effect.
  • The offerers of procedural models are partial. Procedural models are a business, therefore the developer of a procedural model advises in its interest. Offerers represent straight their model as the universal remedy for all problems. Here the foundation-stone for a consequence is appropriate for the process and everything becomes good
- Mentality. A project fails if the involved ones do not regard it any longer objectively and for example only process the given check lists (Managementvoodoo).
  • Management consultants know the procedural models better than those firmly employee software developer of an enterprise. Management consultants possess contracts of employment and after expenditure of time are paid. Therefore a management consultant extends if possible the course of the project, if he liked to earn to it more moneys (cargo Cult Science).
  • Due to the project structure, which produces a procedural model, a management consultation for each individual activity offers specialized advisor. By splintering the tasks on single specialists the coordination expenditure rises superproportionally.
  • Procedural models can help the Parkinson law for administration and management to the full bloom, since they open the possibility of requesting new coworkers for new tasks after procedural model. Concerned from this phenomenon particularly are such mechanisms, which are not subject to a close economic control, because they cannot go broke (authority, office and institute of the public right As warning the straight lately (conditions at the end of of 2004) grandios failed like, substantially retarded, as unsuitable software projects put out and/or substantially raised the price of of the public hand, as INPOL new (police), Nivadis (police Lower Saxony), FISCUS (tax office), Herkules (German Federal Armed Forces), on-line job exchange (work agency), madly Collect, A2LL (work agency, "“Hartz IV"” - software), Poliks (police Berlin), etc. to serve itself. The amassment and the scope of the distressed projects are frightening.
  • It is disputed whether the developing process is so well understood about software that "“engineer-moderate production"” is possible: Critics argue that software is nothing else as "“executable knowledge"”. Knowledge however can be manufactured not engineer-moderately (like for instance a bridge or a multistoried building to manufacture leaves itself), but during a creative process is found.
  • Water drop model, V-model and modelling languages cover the ad-hoc-character of a development process. These methods the development and restrain the creativity of the developer.

    • Related links


    Printer Friendly FormatPrinter Friendly Format
    Back to topBack to top
    Back to Business process managementBack to "Business process management"
    Back to topBack to top
    Back to Business process managementBack to "Business process management"

    Related Websites

    We found here 6 related websites.

    Back to topBack to top
    Back to Business process managementBack to "Business process management"
    Page cached: Wednesday, July 5, 2006 14:19:17
    Valid XHTML 1.0!  Valid CSS!
    Page copy protected against web site content infringement by Copyscape