Discussions
The purpose of this Assignment is to bring together, in a Practicum, the knowledge you have gained throughout the duration of the course. To achieve this purpose, you are to write a solution-oriented EA report. Choose either an industry-wide or an organization-specific architecture problem. Analyze the problem space in terms of “ identified issues” (see #4 and #5 below) and then provide some recommendations and planning based on your analysis of the problems/issues (per #6 and #7 below).
Before starting, be sure to read and understand the formatting requirements contained in the University College Format and Style Requirements (Links to an external site.) .
Previous Final Projects have been published in the Enterprise Architecture Professional Journal. Several issues of the Journal are posted in the "Paper and Final Project" Folder, under the "Files" Tab. These previous Projects are provided as examples -- not as templates or formats. Use the document cited above for format for your Final Project.
You may use TOGAF or any other EA framework to approach this project, as well as related information provided in your texts.
DETAILED GUIDANCE
(Minimum of 18 Full Pages, Double Spaced, for Portions #4-7 Below, Excluding the Required Visuals. Plan on an upper limit of 25 pages for Portions #4-7 – if no prior arrangements are made with the professor. Exceptions are possible, upon coordination, in terms of the upper limit.)
1. Title Page
2. Table of Contents
* Include page numbers
3. Executive Summary
* This should be a concise, one-page, executive-level summary of key findings and recommendations from your paper
4. General Background of Project Topic and Vision of Architecture Project Success
* Provide general overview, some kind of benchmarked “big picture” for context, and an
Architecture Vision/Purpose – what will success look like?
* Include references as appropriate
* Use page numbers beginning with this section – page 1
* 2 or more pages
5. Identification of approximately 4-6 Major Architecture Issues associated with the project (and benchmarked “big picture” of which this project will be a part – provide a context for what part of a larger ecosystem you are addressing.
* Potential Issue Areas: Organizational, Management, Strategy, Financial, People, Culture
* Potential Issue Areas: Data, Information & Knowledge
* Potential Issue Areas: Information Technology, Other Technology
* Potential Issue Areas: Business Process, Policies & Procedures, Controls/Metrics
* Potential Issue Areas: Architecture frameworks, reference models, patterns, Implementation
* Each identified issue should be bulletized and short, clear and crisp
* Do not discuss issues in this section
* No more than one sentence for each issue
6. Analysis of the implementation of the Project Topic and associated Major Enterprise Architecture Issues
* Should represent at least 60% of the research paper
* 10 or more full pages in length
* Factually based on research material gathered (can include examples from your own personal experience
* Develop a small business case to justify that each issue merits attention as such – why is the issue an issue, based on the facts and your analysis?
* Do not include personal conclusions or recommendations in this section
* Include references as appropriate
7. Recommended Solutions, High-Level Roadmap, and Conclusion with Recommended Next Steps
* Provide recommended solutions, showing that you have first considered alternatives, for each major issue * Provide a high-level road map (could be part of an MS Project plan, an Excel spreadsheet, or a Word table)
** Provide key activities and milestones in this road map
* Provide a section entitled “Conclusion” in which you summarize your key findings and provide some recommendations, including suggested next steps.
* 5 or more pages
8. Appendices (Schematics, Charts, Graphs, etc.): Along with a high-level roadmap for your problem space/solution, provide either a catalog, matrix, or diagram (TOGAF vernacular) for some aspect of each of the following: business, data/information, application, and technical architectures (e.g., could be “As Is, To Be, or Transition views). Therefore, a minimum of 5 “visuals” is required. You can of course do more if you like.
9. References
* You MUST document your research paper
* You must provide references – evidence of extensive research, including but beyond use of material made available in the course, is very important. You must also include at least 4 scholarly research sources from peer-reviewed journals available at the Penrose Library electronically. (Note: When proprietary information has been used in your paper that cannot be shared, this should be noted where appropriate, but research should not be restricted only to such sources, as noted above and in the bibliography section below.)
* Various formats are available for use
** Use the endnotes or in-text citations
* Your research paper MUST BE FULLY DOCUMENTED (i.e., if something is not your own idea or conclusion, you must make this clear by citing the source or noting that it cannot be cited, if that is the rare case)
* References are a critical part of your project
* You must include all sources of available/public information that you use in the development of your paper
* Sources include articles, books, web sites, interviews, etc.
* At least 10 sources should be in your List of References
CONTENT AND CONTEXT CRITERIA FOR PAPERS AND FINAL PROJECT
The following subjective Content & Context criteria will be used in evaluating your formal written work:
* High quality and very professional
* Meeting format and minimum length criteria
* Good organization, thoroughness
* Excellent grammar, punctuation and spelling
* Clarity of thought
* Convincing argumentation
* Ability to relate to arguments to specific facts -- common thread
* Excellent identification of issues
* In-depth analysis
* Excellent and substantive conclusions and recommendations