Syllabus BSA/375 Version 13

Syllabus
College of Information Systems & Technology BSA/375 Version 13 Fundamentals of Business Systems Development
Copyright 2012, 2011, 2010, 2009, 2008, 2007, 2006, 2005 by University of Phoenix. All rights reserved.

Course Description This course introduces the fundamental, logical, and design considerations addressed during system and application software development. It provides a solid background in information systems analysis and design techniques through a combination of theory and application. The Systems Development Life Cycle will be fundamental to the course. Policies Faculty and students/learners will be held responsible for understanding and adhering to all policies contained within the following two documents: University policies: You must be logged into the student website to view this document. Instructor policies: This document is posted in the Course Materials forum.

University policies are subject to change. Be sure to read the policies at the beginning of each class. Policies may be slightly different depending on the modality in which you attend class. If you have recently changed modalities, read the policies governing your current class modality. Course Materials Primary Texts Blankenship, E., Woodward, M., Holliday, G., & Keller, B. (2011). Professional team foundation server 2010. Indianapolis, IN: Wiley. Dennis, A., Wixom, B. H., & Roth, R. M. (2012). Systems analysis & design (5th ed.). Hoboken, NJ: John Wiley & Sons. Schiesser, R. (2011). IT systems management (2nd ed.). Boston, MA: Pearson Education. Valacich, J. S., George, J. F., & Hoffer, J. A. (2012). Essentials of systems analysis and design (5th ed.). Upper Saddle River, NJ: Pearson Education Software Microsoft Visio Microsoft Project (Recommended) Toolwire Personal Student Desktop All electronic materials are available on the student website.

Week One: Systems Development Life Cycle

Syllabus BSA/375 Version 13

Details
Objectives 1.1 Define the systems development life cycle. 1.2 Describe Roles of Systems Analyst and Others in System Development Projects. Read the Week One Read Me First. Read Ch. 1, The Systems Development Environment, of Essentials of Systems Analysis and Design. Read Ch. 1, The Systems Analyst and Information Systems Development, of Systems Analysis & Design. Read Appendix B, Agile Methodologies, of Essentials of Systems Analysis and Design. Read this weeks Electronic Reserve Readings. Listen to the Week One podcast lecture located on the student website. Post your personal Bio in the Chatroom forum for others to read and to meet each other. Participate in class discussions 4 out of 7 days during the week, at least 2 substantives postings per day when participating. Respond to weekly discussion questions. Post your responses to Discussion Questions in the Main forum and begin responding to each other's responses. Please post your responses in the DQ threads. Responses to each question should be at least 200-300 words. Read the course description and objectives. Ensure you have access to the recommended software: Microsoft Visio

Due

Points

Readings

Audio Week One Lecture Nongraded Activities Participation Discussion Questions

Day 1
(Tuesday)

Day 1
(Tuesday)

All Week Day 3

(Thursday)

3 2

Nongraded Activities and Preparation

Review the Learning Team Toolkit Learning Team Instructions Create a Learning Team Charter. Submit your learning team project initial investigation draft as an attachment to the scribes Individual Student forum. I will not grade this draft but I will provide commentary for improvement for the final paper, if needed. See Meeting one (1) below within the Learning Team Assignment section of the syllabus for further details. Submit your weekly learning team activities review to your assigned Learning Team forum. Individual Submit a response to the Main forum summarizing what you learned from the readings, research and discussion activities during the week due on Monday. Your summary should be at least 200-250 words and should follow the format in the summary thread (will be posted on Day 7
(Monday)

Day 7
(Monday)

.01

Syllabus BSA/375 Version 13

Day 5 Saturday). (Included in Participation points)

Week Two: Systems Analysis

Details
Objectives Readings 4.1 Explain scope and feasibility. 4.2 Define systems analysis and systems requirements. Read the Week Two Read Me First. Read Ch. 4, Use Case Analysis, of Systems Analysis & Design. Read the Use-Case Modeling section in Appendix A, ObjectOriented Analysis and Design, of Essentials of Systems Analysis and Design. Read Ch. 5, Determining System Requirements, of Essentials of Systems Analysis and Design. Read Ch. 6, Structuring System Requirements: Process Modeling, of Essentials of Systems Analysis and Design. Read Ch. 7, Structuring System Requirements: Conceptual Data Modeling, of Essentials of Systems Analysis and Design. Read this weeks Electronic Reserve Readings. Listen to the Week Two podcast lecture located on the student website. Participate in class discussions 4 out of 7 days during the week, at least 2 substantives postings per day when participating. Respond to weekly discussion questions. Post your responses to Discussion Questions in the Main forum and begin responding to each other's responses. Please post your responses in the DQ threads. Responses to each question should be at least 200-300 words. The individual student assignments for this course will consist of producing a System Development paper that will consist of three separate and distinct sections. Section one will be due week 2, while section two will be due week 3 and section three will be due week 4. It will be necessary for you to access Riordan Manufacturing from the Virtual Organizations Portal of the course rEsource page. Grading Criteria: Complete Section 1 of 3 sections. Using the Service Request SR-RM-022, Analyze HR System, prepare the first 4-6 pages of the paper that accomplishes the following: For Section 1 (Analysis) of the paper, write the following: Determine what key stakeholders in Riordan Manufacturing would you gather requirements from? Describe the information-gathering techniques and design methods you would propose to use for the project. Day 1
(Tuesday)

Due

Points

Audio Week Two Lecture Participation Discussion Questions

All Week Day 3

(Thursday)

3 2

Individual Service Request SRRM-022, Part 1

Day 6
(Sunday)

15

Syllabus BSA/375 Version 13

Identify the key factors that will help ensure the information required for the project is gathered successfully. Explain the scope and feasibility of the project. Incorporate a transition from analysis (Section 1) to design (Section 2) (e.g., walk the reader through the process of moving from analysis to design). Also, include a standard APA Introduction and Conclusion to this section of the paper. Use appropriate external citations and references (minimum of 3), in addition to including references to the required readings (or virtual organizations) where relevant, within the assignment. Be sure citations and references follow the University of Phoenix approved style guide format (the Written Assignments Guidelines, along with properly cited APA references). Please Note: Dictionary and Encyclopedia citations and references of any type will not count towards your reference/citation count. Submit your final copy of your paper through the Center for Writing Excellence Plagiarism Checker and place the summary report (classical report view) to the end of your paper (after the Reference page CTL+A on HTML TurnItIn report page, CTL+C (Copy), then CTL+V (Paste) after Reference page). This is logistic a requirement for this Individual Student assignment. I do not want a separate attachment for the summary.

Post: Completed paper as a properly formatted APA assignment (Title page, Table of Contents (optional), References and Plagiarism Summary Report (these sections do not count towards the 4 6 page length of the paper)) as a Word document to the Assignments Link for grading purposes. Learning Team Instructions Submit your learning team project analysis draft as an attachment to the scribes Individual Student forum. I will not grade this draft but I will provide commentary for improvement for the final paper, if needed. See Meeting two (2) below within the Learning Team Assignment section of the syllabus for further details. Submit your weekly learning team activities review to your assigned Learning Team forum. Individual Submit a response to the Main forum summarizing what you learned from the readings, research and discussion activities during the week due on Monday. Your summary should be at least 200-250 words and should follow the format in the summary thread (will be posted on Day 5 Saturday). (Included in Participation points) Day 7
(Monday)

Day 7
(Monday)

.01

Week Three: Systems Design

Details
Objectives 5.1 Define design specifications.

Due

Points

Syllabus BSA/375 Version 13

Readings

Read the Week Three Read Me First. Read Ch. 2, The Sources of Software, of Essentials of Systems Analysis and Design. Read Ch. 8, Designing the Human Interface, of Essentials of Systems Analysis and Design. Read Ch. 9. Designing Databases, of Essentials of Systems Analysis and Design. Read Ch. 7, Moving Into Design, of Systems Analysis & Design. Read Ch. 8, Architecture Design, of Systems Analysis & Design. Read Ch. 10, Program Design, of Systems Analysis & Design. Read all sections in Appendix A, Object-Oriented Analysis and Design, of Essentials of Systems Analysis and Design, except UseCase Modeling. Read this weeks Electronic Reserve Readings. Listen to the Week Three podcast lecture located on the student website. Participate in class discussions 4 out of 7 days during the week, at least 2 substantives postings per day when participating. Respond to weekly discussion questions. Post your responses to Discussion Questions in the Main forum and begin responding to each other's responses. Please post your responses in the DQ threads. Responses to each question should be at least 200-300 words. The individual student assignments for this course will consist of producing a System Development paper that will consist of three separate and distinct sections. Complete Section two this week. It will be necessary for you to access Riordan Manufacturing from the Virtual Organizations Portal of the course rEsource page. Grading Criteria: Complete Section 2 of 3 sections. Do not add this section to the previous section. This should be a separate and distinct section. Using the Service Request SR-RM-022, Analyze HR System, prepare the second 4-6 pages of the paper that accomplishes the following: For Section 2 (Design) of the paper, write the following: Describe the application architecture and process design. Apply the tools of systems analysis to describe the information systems architecture in terms of data, processes, interfaces and network. Draw the physical data flow diagram(s). Use Microsoft Visio or Word to prepare examples of flow charts and data flow diagrams. Incorporate a transition from design (Section 2) to implementation (Section 3) (e.g., walk the reader through the process of moving from design to implementation). Also, include a standard APA Introduction and Conclusion to this Day 1
(Tuesday)

Audio Week Three Lecture Participation Discussion Questions

All Week Day 3

(Thursday)

3 2

Individual Service Request SRRM-022, Part 2

Day 6
(Sunday)

15

Syllabus BSA/375 Version 13

section of the paper. Use appropriate external citations and references (minimum of 3), in addition to including references to the required readings (or virtual organizations) where relevant, within the assignment. Be sure citations and references follow the University of Phoenix approved style guide format (the Written Assignments Guidelines, along with properly cited APA references). Please Note: Dictionary and Encyclopedia citations and references of any type will not count towards your reference/citation count. Submit your final copy of your paper through the Center for Writing Excellence Plagiarism Checker and place the summary report (classical report view) to the end of your paper (after the Reference page CTL+A on HTML TurnItIn report page, CTL+C (Copy), then CTL+V (Paste) after Reference page). This is logistic a requirement for this Individual Student assignment. I do not want a separate attachment for the summary.

Post: Completed paper as a properly formatted assignment (Title page, Table of Contents (optional), References and Plagiarism Summary Report (these sections do not count towards the 4 6 page length of the paper)) as a Word document to the Assignments Link for grading purposes. Learning Team Instructions Submit your learning team project design draft as an attachment to the scribes Individual Student forum. I will not grade this draft but I will provide commentary for improvement for the final paper, if needed. See Meeting three (3) below within the Learning Team Assignment section of the syllabus for further details. Submit your weekly learning team activities review to your assigned Learning Team forum. Individual Submit a response to the Main forum summarizing what you learned from the readings, research and discussion activities during the week due on Monday. Your summary should be at least 200-250 words and should follow the format in the summary thread (will be posted on Day 5 Saturday). (Included in Participation points) Day 7
(Monday)

Day 7
(Monday)

.01

Week Four: Systems Development and Implementation

Details
Objectives 4.1 Identify the activities involved in systems development. 4.2 Identify the activities involved in systems implementation. 4.3 Identify the activities involved in systems operations. Read the Week Four Read Me First. Read Ch. 10, Systems Implementation and Operation, of Essentials of Systems Analysis and Design. Read this weeks Electronic Reserve Readings.

Due

Points

Readings

Syllabus BSA/375 Version 13

Audio Week Four Lecture Participation Discussion Questions

Listen to the Week Four podcast lecture located on the student website. Participate in class discussions 4 out of 7 days during the week, at least 2 substantives postings per day when participating. Respond to weekly discussion questions. Post your responses to Discussion Questions in the Main forum and begin responding to each other's responses. Please post your responses in the DQ threads. Responses to each question should be at least 200-300 words. The individual student assignments for this course will consist of producing a System Development paper that will consist of three separate and distinct sections. Complete Section three this week. It will be necessary for you to access Riordan Manufacturing from the Virtual Organizations Portal of the course rEsource page. Grading Criteria: Complete Section 3 of 3 of the paper. Do not add this section to the previous section(s). This should be a separate and distinct section. Using the Service Request SR-RM-022, Analyze HR System, prepare the third 4-6 pages of the paper that accomplishes the following: For Section 3 (Implementation) of the paper, write the following: Describe the implementation stage for this project. Include a discussion of the six major activities for the implementation stage as described within the text: (1) coding, (2) testing, (3) installation, (4) documentation, (5) training and (6) support. The discussion of these six activities should describe specifically how each activity would be planned for the individual project situation. Discuss the benefits of using defined and repeatable processes for accomplishing these activities for the implementation stage. Summarize the transitions from analysis (Section 1) to design (Section 2) to implementation (Section 3) (e.g., walk the reader through the process of how the project moved from analysis to design through implementation). Also, include a standard APA Introduction and Conclusion to this section of the paper. Use appropriate external citations and references (minimum of 3), in addition to including references to the required readings (or virtual organizations) where relevant, within the assignment. Be sure citations and references follow the University of Phoenix approved style guide format (the Written Assignments Guidelines, along with properly cited APA references). Please Note: Dictionary and Encyclopedia citations and references of any type will not count towards your reference/citation count. Submit your final copy of your paper through the Center for Writing Excellence Plagiarism Checker and place the summary report (classical report view) to the end of your paper (after the

Day 1
(Tuesday)

All Week Day 3

(Thursday)

3 2

Individual Service Request SRRM-022, Part 3

Day 6
(Sunday)

15

Syllabus BSA/375 Version 13

Reference page CTL+A on HTML TurnItIn report page, CTL+C (Copy), then CTL+V (Paste) after Reference page). This is logistic a requirement for this Individual Student assignment. I do not want a separate attachment for the summary. Post: Completed paper as a properly formatted assignment (Title page, Table of Contents (optional), References and Plagiarism Summary Report (these sections do not count towards the 4 6 page length of the paper)) as a Word document to the Assignments Link for grading purposes. Learning Team Instructions Submit your learning team project implementation draft as an attachment to the scribes Individual Student forum. I will not grade this draft but I will provide commentary for improvement for the final paper, if needed. See Meeting four (4) below within the Learning Team Assignment section of the syllabus for further details. Submit your weekly learning team activities review to your assigned Learning Team forum. Individual Submit a response to the Main forum summarizing what you learned from the readings, research and discussion activities during the week due on Monday. Your summary should be at least 200-250 words and should follow the format in the summary thread (will be posted on Day 5 Saturday). (Included in Participation points) Day 7
(Monday)

Day 7
(Monday)

.01

Week Five: Maintenance

Details
Objectives Readings 5.1 Define systems maintenance and how it is performed. 5.2 Explain system configuration management. Read the Week Five Read Me First. Read the following sections in Ch. 13, Transition to the New System, of Systems Analysis & Design: Software Support System Maintenance Project Assessment Read Ch. 14, Configuration Management, of IT Systems Management. Read Ch. 5, Overview of Version Control, of Professional Team Foundation Server 2010. Read this weeks Electronic Reserve Readings. Listen to the Week Five podcast lecture located on the student website. Participate in class discussions 4 out of 7 days during the week, at least 2 substantives postings per day when participating. Day 1
(Tuesday)

Due

Points

Audio Week Five Lecture Participation

All Week

Syllabus BSA/375 Version 13

Discussion Questions

Respond to weekly discussion questions. Post your responses to Discussion Questions in the Main forum and begin responding to each other's responses. Please post your responses in the DQ threads. Responses to each question should be at least 200-300 words. Resource: Virtual Organization Use: Kudler Foods The Virtual Organizations can be accessed through your Integrated Classroom web page (rEsource) by clicking on the Virtual Organizations link in the Course area on the Materials link/page. Service Requests can also be found in the same area. Finalize the 12 - 16 page paper (approximately 350 words per page). Refer to Meeting Five (5) in Learning Team Project section below for full details, along with the Paper and Presentation section additional requirements. Complete the final draft of the paper based on the weekly meeting assignments by assessing the SDLC methodology for the service request for Kudler Fine Foods. Use your research (draft materials) from this week and the previous weeks to strengthen your position on your assessment and analysis. Check for cohesiveness and flow in the paper from individual contributions. Ensure the paper meets the requirements of the project as stated in the Learning Team Assignment section below. Make appropriate corrections and improvements to the final paper. Finalize the project presentation by preparing a Microsoft PowerPoint presentation of the entire project (length of PowerPoint Presentation can be determined by the Learning Team). Be sure to include speaker notes that discuss each aspect of presentation points. Speaker notes should present the presentation just as if your team were in front of the class. The speaker notes should walk the audience through your presentation, from start to finish. Your learning team should provide the verbiage that you would present in front of the audience, along with transitions from one team member to another. Note; I do not want to see sections of the paper copied and pasted into the speaker notes. This should be a professionally prepared paper and presentation. Adhere the paper and presentation to the writing Standards within the Learning Team section. Include within the paper and presentation properly cited APA references, where appropriate. It is expected that a minimum of 10 12 distinct external references be used and properly cited within the paper. In addition, include references (and citations) to the required readings (or virtual organizations) where relevant, within the assignment. Note: dictionary or encyclopedia references do not count towards the 10-12 distinct external references.

Day 3
(Thursday)

Learning Team Service Request SRKF-013

Day 6
(Sunday)

19.96 Paper 10 - Presentation

Syllabus BSA/375 Version 13

10

Submit your final copy of your paper through the Center for Writing Excellence Plagiarism Checker and place the summary report (classical report view) to the end of your paper (after the Reference page CTL+A on HTML TurnItIn report page, CTL+C (Copy), then CTL+V (Paste) after Reference page). This is logistic a requirement for this Individual Student assignment. I do not want a separate attachment for the summary. Post: Completed paper as a properly formatted paper (Title page, Table of Contents (optional), References and Plagiarism Summary Report (these sections do not count towards the 12 16 page length of the paper)) as a Word document and presentation as a PowerPoint document to the Learning Team scribes Assignments Link for grading purposes. Learning Team Individual Submit your weekly learning team activities review to your assigned Learning Team forum. Submit a response to the Main forum summarizing what you learned from the readings, research and discussion activities during the week due on Monday. Your summary should be at least 200-250 words and should follow the format in the summary thread (will be posted on Day 5 Saturday). (Included in Participation points) Submit your learning team evaluation to the Individual Student forum. Day 7
(Monday)

Day 7
(Monday)

Learning Team Assignment Description Each Learning Team will prepare a course project that applies the SDLC methodology and tools presented in the course. The core project will identify a real world issue at the departmental/divisional level using the University of Phoenixs Virtual Organization portal. The primary goal for the project is to apply workflow and process management concepts in addressing the specific needs of a selected functional area. Objective Apply systems development analysis using learned SDLC methodology and tools. Standards Refer to Standards for Written Work and Standards for Presentations in your Program Handbook, which can be accessed through the University of Phoenix eCampus Web site. Your final paper and presentation will be required to follows these standards setup by the university. Paper and Presentation During the last week (Week Five) of the course, each Learning Team will submit a 12-16-page Microsoft Word paper (350 words per page) and a Microsoft PowerPoint presentation of the project for grading. Both the paper and the presentation should reflect professional preparation. Assume that both works are to be presented to an executive management committee. Be sure to include speaker notes for all content throughout the presentation. The speaker notes should allow the reader to hear the presentation through the written notes. The notes should present all items of discussion for your presentation and not just reiteration of the paper or bullet points.

Syllabus BSA/375 Version 13

11

The paper should also include the following areas upon final submission: Project constraints: financial, time, resources, organizational policies/culture. Description of current business process/system with identification of scope/boundaries of the project. Description of new business process/system utilize the process objectives/model and the system objectives/model. Design requirements: input/output design, interface design, data model, network model. Cost/benefit analysis. Be sure to incorporate all of the research your team has completed through each of the workshop draft papers into the final paper and presentation. The content of the paper will require your team to condense the information to fit into the page limitations set for this assignment. Make sure to verify the paper is cohesive and flows well from section to section. This is very important as individual contributors have different writing styles. Part of your team grade will be set on keeping within the page limitations and cohesiveness of the final product. Learning Team Project The following assignment refers to Service Request SR-KF-013, Develop Requirements for Kudler Fine Foods Frequent Shopper Program. It will be necessary for the learning team to access Kudler Fine Foods from the Virtual Organizations Portal of the course rEsource page.

Syllabus BSA/375 Version 13

12

Service Request

Service Request SR-KF-013 Develop Requirements for Kudler Fine Foods Frequent Shopper Program Organization: Kudler Fine Foods Locations: Requester: All Manager

Description of Request: Kudler Fine Foods is interested in developing a system to track customer purchases through a Frequent Shopper Program to award loyalty points for redemption. Background of Request: The objective of this project request is to track purchases of individual customers. The customer purchases will be tracked and accumulated as loyalty points for redemption by the customer for gift items, specialty foods and other products or services as made available through partnerships with other external companies. The strategic purpose of the Frequent Shopper Program is described on the Sales & Marketing page of the Kudler Fine Foods Intranet site. Expected Results/Impact when completed: Create a business/systems requirements document for the development of the Frequent Shopper Program system to meet the objective of this request. Copyright 2005, 2007 by University of Phoenix. Meeting One (Week 1) The Learning Team will complete Service Request SR-KF-013, Develop Requirements for Kudler Fine Foods Frequent Shopper Program. The Learning Team will prepare a 12-16 page paper and a PowerPoint presentation of the project. Assume that the paper and the presentation are to be delivered to an executive management committee. Create a Learning Team Charter. Refer to the Learning Team Toolkit for assistance on preparing the Team Charter, if needed. Review the Service Request SR-KF-013 for Kudler Fine Foods. Draft the first 4-6 page section (350 words per page) of the paper to include the following (submitted for review, but not graded this is an interim section of the paper): Statement of Scope and Goals: Specify what functions will be included in the project. Identify the goals (accomplishments, not solution).

Syllabus BSA/375 Version 13

13

Project Stakeholders: Identify the preliminary assignments and tasks for each group member. Supporting Measures for Success: Specify tangible measures for determining the relative degree of
success of the completed project. The measures must correlate with the goals specified in the Statement of Scope and Goals section of this deliverable. Summary of Project Feasibility: Include specific operational, technical and economic feasibility analysis. Operational and technical issues should specify how each issue will be addressed. The economic analysis must include quantified specific benefit and cost areas. Current Business Process Summary: Provide a flowchart and a separate high-level logical data flow diagram of the current process. Proposed System Requirement List: List specific individual requirement needs in measurable and objective terms.

Meeting Two (Week 2) Continue the next 4-6 draft development pages (350 words per page) of the paper to include the following (submitted for review, but not graded this is an interim section of the paper): Determination of Requirements: Identify specific analysis methods, which will be used to determine user needs. List of Confirmed Requirements: Categorize each system requirement identified for the Week Two deliverable as mandatory or optional. Proposed System Process View: Provide a flowchart of the proposed process. Functional Allocation Modeling: Specify how each proposed system function would be allocated in terms of the required hardware, software and HCI (Human-Computer Interface (user interface)). Logical Model of the System: Provide a high-level logical data flow diagram of the proposed system. Meeting Three (Week 3) Continue to draft the next 4-6 pages (350 words per page) on the following (submitted for review, but not graded this is an interim section of the paper): Preliminary Design Model: Provide a diagram, which illustrates the overall logical information architecture. Design Trade-off Approach: Specify the tradeoffs among cost, schedule and performance. For example, a fast, inexpensive solution may not address performance requirements adequately. Detailed Design Process and Design Specifications: Specify separate recommended decisions for software design, hardware and network(s). Include resolution of HCI considerations. Physical Model of the System: Illustrate the recommended decisions in information architecture diagrams. Meeting Four (Week 4) Complete the final section to include 4-6 pages (360 words per page) on the following (submitted for review, but not graded this is an interim section of the paper: Testing Process Summary: Define a test plan/script, which identifies major software functionality and hardware to be tested along with the required outcomes. Installation Process and Training Plan Summary: Provide a time line, which identifies the specific steps (including training) and related resources required to implement the recommended system. Include a narrative explanation, which includes a discussion of the impacts of project constraints, such as time, conversion method, etc. and a description of the recommended training plan. Documentation Plan Summary: Specify and explain each type of documentation, which will be required for ongoing support (technical and user) of the proposed system. Support & Maintenance Plan Summary: Provide a plan, which outlines responsibilities and related resources necessary to support and maintain proposed system (software, hardware and networks).

Syllabus BSA/375 Version 13

14

Meeting Five (Week 5) Complete the final draft of the 12-16 page Microsoft Word paper based on the previous weekly meeting assignments. Check for cohesiveness in the paper from individual contributions. Ensure the paper meets the requirements of the project, as stated above in the Paper and Presentation section of the Learning Team assignment area (e.g., include additional areas which have been noted above). Furthermore, make corrections and improvements to the paper. Finalize the Microsoft PowerPoint project presentation and make sure to include detailed speaker notes, which talk through the presentation for the reader. Follow the university standards for Written Work and Presentations for the final products. Refer to the Standards section above for additional information. Copyright
University of Phoenix is a registered trademark of Apollo Group, Inc. in the United States and/or other countries. Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation in the United States and/or other countries. All other company and product names are trademarks or registered trademarks of their respective companies. Use of these marks is not intended to imply endorsement, sponsorship, or affiliation. Edited in accordance with University of Phoenix editorial standards and practices.