UGG Tall Software and documentation with discipline discipline .

software with the concept of discipline with discipline
software (Software Configuration Management, SCM) is the version through its efforts to curb,UGG Tall, curb and other changes in procedures, with the discipline and the use of portable software,UGG Tall, to ensure that all items with a comprehensive and can pursue sex. Harvest with discipline is a useful defense work.
software development and discipline process will occur in the work of many many more gains, such as documents, processes and data, they deserve to be appropriate to keep up, in order to access and correction. If all the files inside headlong into the computer, then use them to determine the very cumbersome. There is no doubt that people deserve to move trivia file hair, keep it orderly.
all areas of work included with the discipline referred to as harvest with items (Configuration Item), with important item in two categories: software code (including source code and binary code) and documentation.
each item with the important properties are: names, identifiers, document the situation, version, author, date, etc. All items have been retained in the match with a library, ensure that no confused, lost. Registered with the item and its history reflects the evolution of the software.
baseline (Baseline) constituted by a set of matching items,UGG Tall, these items constitute a mix of relative calm, logical entity. With the baseline of the items are Baseline corresponds to the development process lightly milestone (Milestone), a product can have multiple baselines, and can have only one baseline. Baseline of the important properties are: names, identifiers, version, date, etc. Lightly to be delivered to the customer's baseline called a
discipline lightly example software code software code of discipline is
personality:
developers may update the code several times a day, may be held fully catalog checkout / checkin monopoly, more than the number of documents, real-time requirements comparable to high.
version of the software code may be compared mixed structure (for example, a branch occurs), discipline tools for the functional requirements of the code match high.
lightly to only developers can checkout / checkin code, non-developers do not need (and should not) called on the code base.
approved professional developers deserve discipline with all the tools to teach software code, common with the discipline tools CVS, SourceSafe, ClearCase, etc. Discipline of software code is the following trivial example:
· first call with management staff in the discipline with the corresponding tool in the creation of code libraries, directory structure and its development environment directory structure adhere to unity.
· with corrections officers assigned to each member of the project code base of monopoly privileges. Lightly, the project members have Addxi.xizihp.com, Checkin / Checkout and other privileges, but not with Informative as approved monopoly with a discipline tool set.
· project members based on their monopoly rights code, such as Add, Checkin / Checkout, etc., the project staff to ensure that the code constitutes a timely Checkin (work interval can not promote more than a day, good day to Build all the code).
· case has been released to fix the code, will certainly obey Great progress in the development of pressure match situations, in order to grow efficiency, approved omit
· obligor regular backups of the code base.
document discipline lightly cases of the discipline of personality
document:
· document the important use is communication, communication and the more abundant the higher the value of the document. Thus unless the developers, many of coherent staff (such as coaching, marketing, etc.) may be called on a document library.
· People frequently revised documents will not be taken lightly, easily constructed version of the document (version does not occur lightly branch), the function of the less demanding discipline tool.
· People are not limited to the use of documents in the office, may travel in the field, the document may also be used at home.
· lightly, the business coaching and marketing personnel about will not use CVS, SourceSafe, ClearCase look at the document (for them, these tools are too mixed up), the use of Web initiatives for them most appropriately.
Although both the professional tools to teach with discipline can discipline of software code documentation, software code and documentation as a match big difference, the industry tends to software code and documentation parting discipline:
· approve the professional tools with discipline (such as CVS, SourceSafe, ClearCase, etc.) to teach the software code.
· measures called him with the necessary documents (called rights is a prerequisite), very decent.
document discipline lightly example is as follows:
· creation of a document library with corrections officers, at least to determine the first-level document library catalog.
· with corrections officers assigned to each member of the project document library monopoly privileges. Lightly, the project members have Adddm.dmtyu.com, Checkin / Checkout and other privileges, but not with Detailed documentation approved by the monopoly, as the software may be discipline.
· project members based on their monopoly rights documents, such as Add, Checkin / Checkout, etc., the project staff to ensure that the document constitutes a timely Checkin (work interval can not promote more than 1 week).
· file with corrections officers with the appropriate file cabinet storage bag or paper documents (paper documents such as customer supplied).
· case has been released to fix the important documents (such as requirements documents, design documents, project plans), will certainly obey Great progress in the development of pressure match situations, in order to grow efficiency, approved omit
· person of the obligation to regularly back up the document library (see the plan with discipline, lightly backed up by the teacher with a pipe).
integrated development platform for RDMS supply discipline of the Also, code review, especially on the details of falsely eliminate some of the absurd of great benefit,