Power Point Presentation
Please prepare the power point presentation for the following assignment.Be consice and precise.Thank you
College of Computer and Information Sciences
MSCC 630 – Enterprise Architecture
Assignment 4 (Case Study)
Enterprise Architecture Principles
and Application Descriptions
Step 1: Do the preparatory reading for this assignment. This includes:
- Your instructor will provide you with a case study to use for assignments #4, #5 and #6 – e.g., Clarion School, BJ’s discount retail or the Pizzeria from the Land reading. Read the case study and any supplemental material (e.g., business capability maps, news articles, etc.) provided to you by your instructor.
- Review the information about Architecture Principles in TOGAF version 9, Chapter 23 which is available on the OpenGroup.org website.
- Read Chapter 6 from the Spewak & Hill (1993) text. Pay particular attention to the examples and information about the Applications Systems Description
Step 2: Create a set of Enterprise-level Architecture Principles for your case study.
- Use the template in the TOGAF specification for principles –i.e., use Name, Statement, Rationale and Implications.
- See if you can create enterprise level principles and not ones for sub-architectures (such as data or technical or application architectures). These should be enterprise principles that are specific to the case study and the way that organization (BJ’s, Clarion, etc.) would run their business. Be specific – i.e., avoid simple statements like “We want to make money”.
- You can draw from other sources like journal articles, company websites or financial filings (Google for EDGAR). You should always list the source of information you used for determining the principle.
- You should prepare 5-8 principles. Be sure your principles are applicable, and specific, to the business domain of the case study you have been assigned. Do not use principles that are overly generic and would apply to any business.
Step 3: Create a list of 6-10 Business Capabilities that apply to your case study. These are called “Major Business Functions” in examples in chap. 6 of the Spewak & Hill reading. You will use these in this and the subsequent assignments. Draw these from the case study materials (BJ’s) or the reading materials (Clarion or Pizzeria). [Note: You may have been provided these in your case study materials. In that case, just use what was provided to you.]
Step 4: Create Application Descriptions (similar to the examples in chapter 6 of Spewak & Hill for the Information Resources Catalog) for the case study assigned to you (BJs, Clarion School, etc). Your Application Descriptions will reflect the state of the enterprise based on the materials provided to you, your own research and as of the date of those materials – i.e., you do not need to worry about what is the most up-to-date, on-the-ground state, of the business.
The Application Description should have the following sections (following examples in the reading) and with data filled determined to the best of your ability from the sources (not all information will be known for all applications):
- A short name (acronyms or abbreviations) and the long name (official name) assigned to systems.
- The project manager or person responsible for maintaining that application along with their contact information (if known).
- The organizational owner or business department responsible for the requirements and functions of the application. If this isn’t available in the materials provided to you or from your research, assign an associated business department – use your judgement.
- A plain language definition of this business application and what it does. The definition is intended to be read by people throughout the organization – it should not be overly technical. It should describe “what” the application does but it does not describe “how” the application works.
- The business capabilities (or functions) supported by the application should also be listed. These are the business capabilities from step 3. This is important. Do not skip this part.
- The status of the system, such as operational, planned, or obsolete. The status notes include changes scheduled for the coming year.
- Long-range issues are changes that may occur in the future, but are not definite.
- Organization units identified in the business model may be linked to the application.
- Maintenance or other direct budget costs to the application, if known, may be given.
- The number of people that are assigned to maintain this application.
- Year implemented. Latest version or revision.
- Whether the application is primarily batch, online, or both.
- If a batch or scheduled application, what is the frequency of running the system, such as daily, weekly, or monthly. Also, what is the scheduled time within the frequency when the application runs – e.g., daily at 3pm.
- The equipment, hardware, or physical technology platforms used. Important. Do not skip this (you need this for Assignment #6). Also, the network(s) or communication platforms used.
- The software platforms used. These include operating systems, database systems and enterprise applications (SAP, PeopleSoft, etc.) used.
- Additional notes are for miscellaneous material relevant to this application.
- Finally, a note whether supplemental material or documentation was collected.
Additionally, create a placeholder application (or applications) for any business capabilities that don’t seem to have an existing application. Do not skip this step.
Make sure you list sources of information used. Include source, date, etc. in your citations for sources of information used.
Step 4: Submit this portion of your Case Study Analysis to the Dropbox by the date specified by the facilitator.
Notes about this assignment:
- This is not a research paper. You do not use the APA format for a research paper for this assignment – i.e., you do not need to include an abstract.
- Imagine yourself as a junior Enterprise Architect in the organization described by your case study and these are your on-the-job work products. Your audience is the CIO and other business leaders. Prepare work suitable for this audience – that is how you will be evaluated.
- You do not need to know more about the case study than what is provided to you and what you can supplement with some basic research.
- You may prepare your work using Word, PowerPoint or Excel. If you use Visio or other tools, please submit your work as PDF or JPG files.
- For the Application Descriptions, you have to provide information comparable to the examples in the reading – you do not have to strictly follow the format from the figures in the reading. For example, you may find it more convenient and useful to organize your Application Descriptions as a series of tables and to do this in Excel. That is fine.
- For the Application Descriptions, focus on the key applications that relate to the case study. For the purposes of this class, let’s just assume you can’t document everything.
Enterprise Architecture Principles
and Application Descriptions
|Application Descriptions||Comprehensive diagrams and description of a current state application architecture to represent the domain area of the case study.||Diagrams and description of a current state application architecture to represent the domain area of the case study.||Lacks diagrams and/or description of a current state application architecture to represent the domain area of the case study.||Lacks diagrams and description of a current state application architecture to represent the domainarea of the case study.|
|Enterprise Principles||Enterprise level architecture principles are properly formatted and include clear description, rationale and implication. Principles are a thorough representative of case study enterprise.||Principles are properly formatted and include description, rationale and implication. Principles have minor errors in usage or may not well cover the domain of the assigned case study.||Principles are not complete – e.g., include description but lack rationale and/or implication. Identified principles have significant gaps in covering the domain of the assigned case study.||Principles have significant errors in format, content or completeness. Principle are fundamentally not effective in describing the case study provided.|
|Format, Content and Coherence||Document is well organized, well written, informative concise, and thorough.||Document is well written and informative but could use minor improvements in content or presentation.||Minor errors in format, organization or content of the document.||Document contains significant errors in structure and/or information presented making document difficult to read and comprehend.|