Those who make loud threats seldom carry them out.
Models, Documents, and Source Code Let's start with understanding the relationships between models, documents, source code, and documentation, something depicted in Figure 1.
From Put definitions essays point of view a document is any artifact external to source code whose Put definitions essays is to convey information in a persistent manner. This is different from the concept of a model, which is an abstraction that describes one or more aspects of a problem or a potential solution addressing a problem.
Some models will become documents, or be included as a part of them, although many more will simply be discarded once they have fulfilled their purpose. Some models will be used to drive the development of source code, although some models may simply be used to drive the development of other models.
Source code is a sequence of instructions, including the comments describing those instructions, for a computer system.
Although source code is clearly an abstraction, albeit a detailed one, within the scope of AM it will not be considered a model because I want to distinguish between the two concepts.
Furthermore, for the sake of discussion the term documentation includes both documents and comments in source code. The relationship between models, documents, source code, and documentation.
Why Do People Document? Agile developers recognize that documentation is an intrinsic part of any systemthe creation and maintenance of which is a "necessary evil" to some and an enjoyable task for others, an aspect of software development that can be made agile when you choose to do so.
There are several valid reasons to create documentation: Your project stakeholders require it. The creation of documentation is fundamentally a business decision, you are investing the resources of your project stakeholders in the development of the documentation therefore they should have the final say on whether their money is to be spent that way, not a technical one.
If your project stakeholders request a document from you, perhaps at your suggestion, and understand the trade-offs involved more on this laterthen you must create the document. It is important to note that eXtreme Programming XP is very explicit about documentation being a business decision.
You should create documentation only when your project stakeholders ask you to? Well, my experience is that this isn't preposterous. Your project stakeholders include a wide variety of people, including all of the clients of your system, and therefore they should have a reasonably good idea what they want.
Maintenance developers, or someone representing them if they are not in place yet, will request system overview documentation. Users and their management will likely request user documentation.
Operations staff will request operations documentation. Yes, you will need to work closely with them to determine what they actually need, someone is going to have to decide to pay for the development and subsequent maintenance of the documentation, and you may even need to explain the implications of what is being requested, but this is doable.
To define a contract model. Contract models define how your system and an external one interacts with one another, some interactions are bi-directional whereas others are uni-directional, making the interaction s explicitly to everyone involved. Contract models are often required when an external group controls an information resource that your system requires, such as a database, legacy application or information service.
The AM practice Formalize Contract Models states that a contract model is something that both parties should mutually agree to, document, and change over time if required.
It is important to understand that the development of a contract model should still be verified by your project stakeholders-it is their money that you are spending, and if they choose to go at risk and not have the contract model in place then that is their choice.
To support communication with an external group. It isn't always possible to co-locate a development team and it isn't always possible to have project stakeholders or at least the ones you need at the time available at all times.
When you need to work with an external group of people you need to find ways to communicate with them, and shared documentation is often part of the solution in combination with occasional face-to-face discussions, teleconferencing, email, and collaborative tools.
It is a mistake to use documentation as your primary means of communication because it's far too easy to misunderstand something that has been written, but it is a good supporting mechanism.
A good way to think of documentation in this situation is that it is your option of last resort. Note that this in effect is an extension of the practice Model to Communicate into the realm of documentation. To support organizational memory.
An important implication is that we not only need to develop software, but we also need to develop the supporting documentation required to use, operate, support, and maintain the software over time. I've worked in organizations where we've developed life-critical systems, and those systems fell under the auspices of the US Food and Drug Administration FDA audit guidelines.
The common theme was that we had to follow a defined process and capture proof that we did so, resulting in more documentation than we would have normally written. In these situations you still want to create just enough documentation to get the job done.
A common mistake that I see get made is that the bureaucrats jump on the "We're might get audited by so-and-so, therefore we need to produce the following documentation My advice is to read the appropriate guidelines yourself, because they rarely require what the bureaucrats think they require.
Be smart about compliance. To think something through. Many people will write documentation to either to verify for themselves some group work they had just been involved with or simply to increase their own understanding.Free 8th grade papers, essays, and research papers.
An essay has been defined in a variety of ways. One definition is a "prose composition with a focused subject of discussion" or a "long, systematic discourse".
It is difficult to define the genre into which essays . English Literature Essays, literary criticism on many authors, links to internet resources and bookshop. Between the devil and the deep sea.
To choose between two equally bad alternatives in a serious dilemma. Where there's a will there's a way. When a person really wants to .
Figure srmvision.com relationship between models, documents, source code, and documentation. 3. Why Do People Document?.
Agile developers recognize that documentation is an intrinsic part of any system, the creation and maintenance of which is a "necessary evil" to some and an enjoyable task for others, an aspect of software development that can be made agile when you choose to do so.
INTRODUCTION. In , when the author of the essays here assembled was elected professor of political and social science in Yale College, he was, to use his own words, “a young and untried man.” He was selected for his position, not as a specialist, but because he was what he was.
Someone in those days must have been an excellent judge of men.