Home
Links
The guest manuscript on PHP
JavaScript: reimbursement of the form
JavaScript: carriage of the form on the server
increase of effectual structure of Internet - shop
The client - guided aim
marketing in WAP - as well because what for
place of an economy class
Emotions in propose (case)
Bases of network -devise . The list for WWW
dealing - machinations for original natures
Bases of net -mean . Texts for WWW
Bases of mesh -intend . CSS
Tendencies of amount and progress of styles in net -devise
trap -aim : Sketches
The technical mission and intend of the interface
Webs - interfaces: Uniquitous applications - chameleons
Draft stile
tribulations (Tasks) of Internet - marketing: we save sites
lifelike design
Art and techniques of devise
 

during the observe we often meet by such state : the original project during which us involve, already lasts some time, plus on it(him) persons or added materials are turned absent , as a rule, near is untaken technical undertaking (OC) on expansion .


What difficulty (task) is put before us by the purchaser ? In overpowering majority of cases it - deceitful of the interface in the structure of unfilled OC. The industrial project, because a directive , is the volumetric meticulous document, somewhere , (on RUP, for example) every business - roles, scripts (exploit -luggage ), functions of system are fixed. inside most luggage - information structure, formats of persons or additional data (length and nature of fields, for example) often are registered. It happens, that in this or that volume yet io?eniaaiu screen forms.


except let! I can enlarge what border , operating during these frameworks? To juggle with buttons? To be busy ?ane?aneie screens? Most likely, soaring -ranking job of the ?caaeeeoe-expert motivation be afar OC: changes during structure of system spirit be presented , it is possible-, ooieoeiiaea, not speaking about screen forms.


nonetheless OC - utterly necessary division in the slightest extent the solemn project. It is conversion implicit mutually ieioino?oeoo?e?iaaiiuo expectations plus "oioaiee" on a precise with unequivocal technological language. Such translation is necessary for:


    * natural planning with the manage of employment over a course of the undertaking ;


    * Fixings amounts of works, hence - conditions and fee (in countless projects doodle up OC is a nil stage and costs(stands) divide money);


    * Formations of the control roll of surroundings on which the purchaser accepts employment .


In detail that the customer (not EO-director wishes on the part of the purchaser , namely the business - customer)? Decisions of such and such problems on such and such environment . Like: « through the assist of organization my people should hastily and lacking mistakes to fix every data in the convention , to spend it(him) on life series , and to create review reports for me ».


especially much the general(universal ) and wrong description, with on the basis of it it is impossible neither near plan it, nor to make job. consequently business undertake business - analytics, coordination analytics, the manager of the venture . On brightness appears OC. And there it is already written: « … the System must be based on such architecture, a DB - to have so much recordings, core "contract" - such fields of such type … ». OC subscribes the parties(sides).


The project is finished. The system surrenders. And suddenly evils begin. The customer starts to carp. And, by a view of developers, it is completely groundless. The architecture corresponds(meets) OC? Corresponds(meets)! All these fields are within system? Is! A format such? Yes, such! All as inside OC which is coordinated with signed! accordingly in what put?


with the material is that in paraphrase process "oioaiee" during OC there was a exchange of industry - evils which the system should solve, its(her) uniqueness .


The characteristic situation of dialogue inside different languages is available. The customer, assessment about coordination , often represents those industry - processes which she will computerize , and, definite abstract a picture. The developer represents equally that is completed - realized ooieoeiiae.


lone does not understand, what is this not unambiguous system which does(makes) impressive is faraway similar to it(him) caaoiee, and starts to be annoyed . Another is angry: all is prepared precisely on OC, all functions - they thus what tranquil it is necessary to him!? Such situations I observed set of time .


To disregard OC it is impossible, and the longing to construct to him(it) changes will congregate sharp distaste of developers: property are washed-out for this document, and, the most main , he (frequently with fight) is signed at the shopper . Besides changes can direct to toward reassessment of expenses for the development that also nobody would like: to assert(approve) I shall clean away - a durable problem(mission ).


How iia?o?eou OC with the line ?


Very just : to increase the line UP TO the account of industrial parameters of the endeavor in OC.


It is essential before transformation into talking of character to build translation into language of the customer interface. within fact the interface is at all only good-looking a representation . It plus quantitative self , important plus UNDERSTANDABLE for the consumer (speed of job, for example), it and the description of behaviour of system by job through her, and, eventually - revelation , objectification of the outlook system. plus to present final effect , having by itself the prototype of the boundary , much easier, than on OC.


OC, unquestionably , it is necessary. bar often to the dealing - shopper it to anything, for him(it) it - oeeueeia the letter. And theoretically it in wide-ranging can not be shown him.


To project the interface before development OC on realization, inside parallel him or since the branch of it(him) is a perfect way of the communications and the coordination of expectations amid customers with developers. It relieves of set of problems.


except the utter happiness no. What minuses at the set approach? Two most understandable :


   1. The initial period of the project - time before final fixing conditions of jobs increases;


   2. fee of a "nil " stage - grows by the disbursement of preamble of process of improvement of the interface.


instant and currency - individual of the most dangerous parameters of the scheme , and, not looking that the all-function (COMMON) expenses for the project virtually are always reduced, obligation at once to compensate more and to wait longer (the first results) seldom causes constructive emotions inside the client .


To oppose this the following is possible:


    *


      First, toward appeal near logic of the patron , and to paint toward him through all of charm ?caaeeeoe during general and the set approach within particular. do shows, what is it works at all always: pluss - it, positively , well, but also change AT ONCE is indispensable to present , and the advantage(help ) nevertheless is not understandable . The state slowly varies with escalation of all-idea (common) "?caaeeeoe-literacy" of the residents : desire to take currency for the interface already seldom count attempt "to dissolve". Here again fine work « triumph stories », especially confirmed as the quantitative data.


    *


      Second, it is obligatory to fuse out folks "aeoniinoe" which the customer will personally receive during the project. It - defined performance concerning the hope system plus its(her) prophecy - since the archetype (ia), or part patterns (and-before documentation). with it - very much an focal point and for developers including. It we accomplish a organization of outlook from consequences of the project, plus practically we get free of exchange in diverse languages at his(its) liberation .


It is obvious, that all these receptions should be useful together, additionally and generally to smirk and is tasty(scrumptious ) to stink thus.


It is agreeable , that the tendency to displacement of ?caaeeeoe-jobs inside the establishment of the project is appreciable. inside our follow there are examples when the boundary was made (made) still before designation of the contractor on his(its) comprehension , and was OC already for developers. Two - three years before I on all would not consider , that such ideal situations are potential (probable).


The resume: during a compute of opportunities create the interface by zero stages of the project. construct the report of the user line an artefact anticipating the technical mission , or his(its) component . At least, try to corroborate , it willpower what is it subsist paid flipside .