Jonathan refuses to allow Karen or anyone else on the medical staff to reveal this diagnosis to Sarah. This reading includes explanations of these three categories involved in making a difficult decision. Be certain to use your knowledge of the scientific and medical aspects of HD to support your views.
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 AM's point of view a document is any artifact external to source code whose purpose 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.Project Selection Methods OPS/TM June 10, 20XX Project Selection Methods This week assignment required for one to choose a process that one does every day that one wants to .
Affordable Papers is an online writing service which has helped students from the UK, US, and Europe for more than 10 years.
Our great experience enables us to provide papers of the best quality. The main secrets of our good reputation are trustful relationships with customers and talented academic writers who always create first-chop papers from scratch.
Free Essay: A project is a temporary activity undertaken to produce a unique product, service or result. This activity called project, has three clearly. See the winners and read their essays on the DNA Day Essay Contest Winners' Page!Congratulations to the winners and honorable mentions.
Chapter 3: The Project Management Process Groups: A Case Study Learning Objectives o Describe the five project management (PM) process groups, the typical level of activity for each, and the interactions among them.
o Understand how the project management process groups relate to the project management knowledge areas. o Discuss how organizations develop IT project management . Turnitin provides instructors with the tools to prevent plagiarism, engage students in the writing process, and provide personalized feedback.