Fluent Essays

Need an expert who in Data Warehousing to make a Project Plan (1,000) words. Topic: Data Warehousing: What role does it play on Information Systems. Information Technology Capstone Project Assessment 1 out of 4 Project Plan 1,000 words No plagiarism will be tolerated as submission will be on University Turnitin Database/Safeassign. This is the first assessment of the subject IT Capstone Project. If I get a good mark I will give the next 3 assessments to you as well. IT Project Outline Project Name: Data Warehousing: What role does it play on Information Systems? Capstone Project Bachelor of Information Technology Contact Details N/A Duration 1 semester Assumed knowledge Student needs to complete 3 years of undergraduate IT course before enrolling in this subject. Possible supervisor PHD in Data Warehousing from University Project Details: Description · Provide an outline for the context of the project Goals of the project · What will the project accomplish? A useful way to frame the objective is to answer the question ‘why are you doing the project?’ The result is a one sentence statement, or series of statements, starting with the word ‘To’ · What are the objectives and are they measurable? Relationship to your IT Stream · What are the major skills required for this project? Project Deliverables · What are the projects deliverables? What things will be delivered by the project? · What values and benefits of this project Best expressed in the past tense and usually start with a word ending in ed, such as improved, increased, enhanced or reduced. They are the benefits that the project intends to achieve. · What is its relevance to your work context? · What is its relevance to you? What will you gain by completing this project? Project Scope · How broad is the project? · What are the potential challenges and complications? · How feasible is it? Project Formatting Guidelines Checklist Complete this checklist for your project documentation. NOTE: This is assessable as part of your project plan and needs to be submitted with the plan Format issue Details Checked Format All assessment tasks (except the journal) should be submitted as a Word document All documentation should be a single word-processed document unless special circumstances are required. Project Title A title of not more than 16 words should be provided. Title Page A Title Page should be submitted with each individual project submission. Title page should have the following information: · Assignment Title · Author Details · Abstract (Lit Review and the final Report) · Keywords (Lit Review and the final Report) Author Details Details should be supplied on the Title Page including: · Full name of the author · E-mail address of the author Abstract · A structured abstract should be included on the Title Page, Abstract should address the following: · Motivation or Problem Statement · Objective of the project · Methodology/Approach · Results/Findings · Implications · Limitation Please note -the list is suggestive and not mandatory · Maximum 250 words in total (including keywords). Keywords · Provide no more than 5 keywords on the Title Page, · Keywords should encapsulate the principal topics of your project Project Topic · Include the original project topic outline that you chose for your project · This should be the second page of your document. Headings · Headings must be 7 words or less · There should be a clear indication of the distinction between the hierarchies of headings. · Headings should have a numbering system that matches the heading levels. · First level headings to be presented in bold format 18 pt · Subsequent sub-headings to be presented in medium italics 14 pt. · Further headings (level 3) should be bold 12pt Presentation · Writing should be presented in clear, concise English. · Fonts should be Calibri or Helvetica, 11 point font · Spacing should be double or 1.5-line spacing throughout · Margins: use standard margins · Page numbers: All pages of your documents must be numbered consecutively, including appendices and references · Page numbers should appear in a footer on the right of each page. Notes/Endnotes · No notes or endnotes Table of Contents · Table of Contents should be automatically generated based on your Word headings. Figures · All Figures (charts, diagrams, line drawings, web pages/screenshots, and photographic images) should be included in the body of your documents. · Ensure that all images are of reasonable quality and easily understood · All figures should be labelled appropriately and referred to in the body of the document. Tables · Tables should be included in the main body of the article. · All Tables should be labelled appropriately and referred to in the body of the document. · Ensure that any superscripts or asterisks are shown next to the relevant items References · References to all publications must be in Harvard style and carefully checked for completeness, accuracy and consistency. · In-text citations : Cite publications in the text: · Citing one author- use the first named authors name and date (Adams, 2006) Make sure you use the family name · Citing two authors, (Adams and Brown, 2006) · Citing three or more authors (Adams et al., 2006). · Reference list should be at the end of each project document before any appendices · Reference list should be in alphabetical order Marking Criteria Project Plan Submission (with presentation checklist) Marking Rubric Details (How your marks will be given) · Project Definition & Scope 50\% of total grade Exceed Expectations Issue/problem/opportunity to be considered critically is stated clearly and described comprehensively, delivering all relevant information necessary for full understanding. Synthesizes in-depth information from relevant sources representing various points of view/ approaches. Insightfully discusses in detail relevant and supported limitations and implications. Explicitly describes assumptions and provides compelling rationale for why each assumption is appropriate. Shows awareness that confidence in final conclusions is limited by the accuracy of the assumptions. No room for scope creep. 75 - 100\% Mees Expectations Issue/problem/opportunity to be considered critically is stated, described, and clarified so that understanding is not seriously impeded by omissions. Presents in-depth information from relevant sources representing various points of view/ approaches. Discusses relevant and supported limitations and implications. Explicitly describes assumptions and provides compelling rationale for why assumptions are appropriate. No room for scope creep. 50 - 75\% Nearly Meets Expectations Issue/problem/opportunity to be considered critically is stated but description leaves some terms undefined, ambiguities unexplored, boundaries undetermined, and/ or backgrounds unknown. Presents information from relevant sources representing limited points of view/ approaches. Presents relevant and supported limitations and implications. Explicitly describes assumptions. Ambiguity and possible scope creep exists. 25 - 50\% Does Not Meet Expectation Issue/problem/opportunity to be considered critically is stated without clarification or description. Presents information from irrelevant sources representing limited points of view/ approaches. Presents limitations and implications, but they are possibly irrelevant and unsupported. Attempts to describe assumptions. Much ambiguity and possible scope creep. 0 - 25\% · Project Planning 20\% of total grade Exceed Expectations All elements of the methodology or theoretical framework are skilfully developed. Appropriate methodology or theoretical frameworks may be synthesized from across disciplines or from relevant sub disciplines. All milestones identified with tasks and responsibilities involved. Clear chart or table developed. Clear verification of review tasks and progress reviews identified. Both project management and technical risks identified with specific control measures. Clear anticipation of resources and potential challenges are addressed. 75 - 100\% Mees Expectations Critical elements of the methodology or theoretical framework are appropriately developed; however, more subtle elements are ignored or unaccounted for. Milestones and in each task were identified with completion date. Chart or table developed. Quality of project well considered, and measures planned. Limited number of well-defined risks and control measures. Some anticipation of resources and potential challenges are addressed. 50 - 75\% Nearly Meets Expectations Critical elements of the methodology or theoretical framework are missing, incorrectly developed, or unfocused. Key milestones identified but individual tasks were not identified. Requirements are documented but with little impact on the quality of the project. Basic risks and controls identified but were very generic. Some needed resources and/or potential challenges have been missed. 25 - 50\% Does Not Meet Expectation Inquiry design demonstrates a misunderstanding of the methodology or theoretical framework. No schedule identified. No indication of how quality will be managed. No risks identified. No resources and materials included. 0 - 25\% · Writing Style 15\% of total grade Exceed Expectations Excellent physical layout and logical structure. The work is presented accurately, concisely and coherently, with no errors and thorough attention to detail. Excellent technical style, avoiding excessive jargon. No spelling mistakes or grammatical errors. Full acknowledgement of the work of others and correctly formatted reference section. Correct use of formatting 75 - 100\% Mees Expectations Good physical layout and logical structure. Good attention to detail. The work is presented in an accurate, concise and coherent fashion, with very few errors. Good technical style, avoiding excessive jargon. Very few spelling mistakes or grammatical errors. Few errors in the acknowledgement of the work of others and a correctly formatted reference section. Correct use of formatting 50 - 75\% Nearly Meets Expectations Satisfactory logical structure and physical layout. Satisfactory attention to detail. The work is presented in a satisfactory fashion. Satisfactory technical style. Generally spelling and grammar are correct. Occasional errors in the acknowledgement of the work of others, satisfactorily formatted reference section. Missing some formatting 25 - 50\% Does Not Meet Expectation Unsatisfactory structure and physical layout. The work is presented in an unsatisfactory fashion. Unsatisfactory technical style. Frequent spelling mistakes and/or grammatical errors. Errors in the acknowledgement of the work of others and an unsatisfactorily formatted reference section. Missing many elements of formatting 0 - 25\% · Overall Quality 15\% of total grade Exceed Expectations Uses appropriate, relevant, and compelling content to illustrate mastery of the subject, conveying the writers understanding, and shaping the whole work. 75 - 100\% Mees Expectations Uses appropriate, relevant, and compelling content to explore ideas within the context of the discipline and shape the whole work. 50 - 75\% Nearly Meets Expectations Uses appropriate and relevant content to develop and explore ideas through most of the work. 25 - 50\% Does Not Meet Expectation Uses appropriate and relevant content to develop simple ideas in some parts of the work. 0 - 25\% Information Technology Capstone Project Assessment 1: Project Plan Task: Develop a project plan for your Project. Your Capstone Project Topic: “Data Warehousing: What role does it play on Information Systems?” Submission details: • Length: Single Word document (1000 words) Overview: A Project Plan is the first part of this subject. Your project plan should define the aims and expected progress of the project. To successfully pass this subject you need to complete the below: 1) Assessment 1: Project Plan (1,000 words) 2) Assessment 2: Interim Draft Report (2,000 words) 3) Assessment 3: Project Report (5,000 words) 4) Assessment 4: Project Presentation (10 minutes) Your plan should be developed in consultation with your supervisor. Ensure that your supervisor has read your plan before you submit. Where appropriate, clarify what is required in your project with your project supervisor and develop your project plan. Ensure you discuss your plan with your supervisor to make sure they think it is reasonable. The project plan should provide evidence that you have begun to investigate the background of the project enough to be able to plan a series of activities that will enable you to develop the plan. Presentation The plan should follow the Project Formatting Guidelines Checklist attached. • Ensure your plan is a single word document. • Ensure your plan uses appropriate referencing. • Ensure your plan follows the required formatting guidelines. Preparation To help prepare for your project research, you need to have a clear understanding of what your supervisor requires you to do in the project. At your initial meeting with your supervisor, you should discuss the outline of your project plan & any literature he/she advises need to be central to the project Marking Criteria The project plan will be assessed by your project supervisor. Please find marking rubric attached. Project Plan Structure What goes in the plan? Details of your plan’s content are outlined following. Broadly, your plan needs to include: TITLE PAGES • This should include project title; your name; and supervisor. • Page 2 should be your Project Proposal Template see attached. (You should complete this) PROJECT DEFINITION & SCOPE 1. Introduction 2. Background/description of context/need/benefits ✓ Explain the context of the project, why it’s needed, where appropriate, the intended audience for the final project product and project stakeholders ✓ Include some initial research as appropriate. ✓ Outline the project benefits for you personally, your client where relevant and in the broader IT context. 3. Aim/s & objectives 4. Scope ✓ Include what’s in scope; out of scope; assumptions, constraints ✓ Describe the boundaries of your project and any assumptions you are making regarding your Project PROJECT ACTIVITIES, DELIVERABLES & RISK 5. Project timeline, deliverables ✓ outline the work activities, milestones & deliverables associated with your project, demonstrating the project management skills used in your studies: o identify the specific work activities associated with your doing your project o identify the assessment milestones that are part of the unit. o do NOT use the Assessment overview page as your project timeline! o estimate how long each activity is anticipated to take as part of the planning ✓ include a table (required) showing timelines, project milestones, deliverables, and assessment deliverables in this part of your plan. You may use a GANT chart instead of a table here. ✓ PROJECT ACTIVITIES ARE NOT THE ASSESSMENT TASKS – these are simply a summary of what you have been doing. 6. Risk ✓ Outline the risks and the associated risk prevention strategies applicable to your project. RESOURCES 7. Materials & Budget: ✓ Outline the materials required to complete your project and where appropriate, include a budget for equipment that may be necessary for the project. 8. References: reference any sources used in the plan. There should be at least 3 appropriate resources 9. Appendix: Complete and include Project Formatting Guidelines Checklist attached. Page 2 of 2 Project’s Supervisor Notes for Project Plan What is data warehousing? What family does it belong to? Issues and importance of Data warehousing Of course, Data Warehousing is a derivative of database so, you should provide in detailed description of: · What data warehousing is · By giving examples of data warehousing · Why are they used? · Why don’t we rely on databases and why we have to come data warehousing for help? The reason why data warehousing are created is very important in this project! Then you jump into the role of data warehousing in information systems You have to give extensive examples of data warehousing are in this semester. Let’s say data warehousing is used in these companies and this is how it’s used for these reasons and benefits (example) Then you have to choose one example and then in detail describe that data warehousing and how that data warehousing is used in that particular company or organization. So, for now, what you will do in the project plan is exactly this. You will describe what I said. So, the aim of your project is actually this to show what data warehousing are? And that important role in information systems specially when it comes to business intelligence (this is very important) Because practically data warehousing are used extensively in business intelligence to first analyse the data properly by using some techniques of analysis like data mining and then to provide the reporting to whoever is asking for information from the data warehouse. Do not forget to relate data warehousing to business intelligence (this is very important because the project should be developed keeping this in mind). Because Data warehousing you will see in your readings when you access published papers that data warehousing is extensively used in business intelligence. So why this is used in business intelligence And business intelligence is part of information systems There is a relation