no great intellectual effort is involved.
Evaluation – this occurs after one generates the outcome and is project specific with two aspects: testing (a paper exercise) the outcome before it is used and of course before the project document is finalised and reviewing research practice for lessons learned.
Conclusions – implies that you take the results and corresponding outcome and make generalizations. One might look for originality, implications, insights, new or modified principles, limitations, new or modified theorisations, indications of best practice, lessons learned, indications of a need for further work, implication for law or standards, warnings or cautions, advice, caveats, values, ethics, factors or features including cultural ones, usage and user psychology and other things that might occur to you.
Outcome – once the primary data has been processed into some usable form (the results) the next step is to generate an outcome based on the processed data and that manifests itself as a document. Here is a list of possibilities that are or can be documents although not all of them are likely to be suitable in a Technology project but I have shown in bold ones that might be.
An Account of, Appendix, Argument, Article, Best Practice Description, Business Case, Calendar, Cartoon, Catalogue, Chart, Checklist, Collation, Colophon, Concordance, Confession, Critical Apparatus, Diagram, Dictionaries, Dossier, Emendations, Essay, Framework, Grammar,
guidelines, History, Index, Instructions, Justification, Lectionary, Lexicon, List, Map, Matrix/Table, Menu, Method, Methodology, Model, Orders, Pamphlet, Plan, Policy, Position paper, Preface, Principles, Procedure description, Process Description, Profile, Prospectus, Protocol, Recension, Report, Research Paper, Review, Schedule, Set of Rules,
strategy, Template, Testimony and Theory
Whatever outcome form has been chosen it will be placed in the project document as a chapter or part of a chapter. The important thing is that all these possible outcomes can be used in some way to bring about change directly or indirectly and the effects of those changes are collectively known as the target. So an outcome might be a series of actions as one might find in a process description or it may imply a series of actions such as might be found if the outcome where policy. Thus:
The outcome of a business case for the use of server virtualization can be used by managers to make a decision. That is the business case itself does not contain any actions but it allows other actions to occur because of its content and hence eventually bring about change based on IT deployment.
The outcome of a fault finding diagram can be used by IT support staff to solve a user problem. That is the diagram might be in the form of a fault finding schema so of itself it has no instructions but it allows others to take action because of its content and hence eventually bring about change. I this case the implication is that we have an improvement in a strategic deployment of IT (the help desk)
The outcome of set of network security guidelines can be used by IT managers in a similar way to a set of instructions. That is the guidelines are definitions of actions and hence following them will eventually bring about change and in this case the strategic deployment is expressed in a more secure network.
Some final points that need to be considered with regard to stating the outcome clearly
Cautio
本论文由英语论文网提供整理,提供论文代写,英语论文代写,代写论文,代写英语论文,代写留学生论文,代写英文论文,留学生论文代写相关核心关键词搜索。