Course Code: INFO498 Course ID: 3837 Credit Hours: 3 Level: Undergraduate
This capstone course is a senior level course designed to allow the student to review, analyze and integrate the work the student has completed toward a degree in Information Technology. The student will complete an approved academic project and paper that demonstrates mastery of their program of study in a meaningful culmination of their learning, and assesses their level of mastery of the stated outcomes of their degree requirements. This is a capstone course to be taken after all other Information Technology courses have been satisfactorily completed. Students must have senior standing in the program and must demonstrate that they have taken all other IT courses in their degree plan prior to registering for this course. (Prerequisite: Completion of a minimum of 105 hours towards your program including ENGL101 or ENGL110)
|Registration Dates||Course Dates||Session||Weeks|
|11/30/20 - 04/30/21||05/03/21 - 06/27/21||Spring 2021 Session I||8 Week session|
|12/28/20 - 06/04/21||06/07/21 - 08/01/21||Spring 2021 Session D||8 Week session|
|01/25/21 - 07/02/21||07/05/21 - 08/29/21||Summer 2021 Session B||8 Week session|
|02/22/21 - 07/30/21||08/02/21 - 09/26/21||Summer 2021 Session I||8 Week session|
|03/29/21 - 09/03/21||09/06/21 - 10/31/21||Summer 2021 Session D||8 Week session|
A successful student will fulfill the following learning objectives:
CO1: Explain the impact of information technology on business strategy and success
CO2: Describe the phases of the System Development Life Cycle
CO3: Describe the methods for Managing Systems Projects
CO4: Develop data flow diagrams in a sequence, from general to specific
CO5: Create logical and physical model of a proposed system
CO6: Develop entity relationship models representing the relationships and the cardinality in an information system.
CO7: Create a System Design Specification document
CO8: Assess system security at six levels: physical security, network security, application security, file security, user security, and procedural security
Weekly Forum Activities
Most weeks you will participate in a Forum activity. Each Forum activity will consist of one or more threads/topics. The questions are designed to allow you to apply the concepts you have learned in the chapter to real-world business scenarios or hypothetical, but realistic, situations. Please try to post your answers to the questions in each thread prior to 11:59 p.m. Eastern Time on Wednesday. This will allow classmates to respond to your post later in the week. Continue to read your classmates' posts and post at least one follow-up post to your classmates’ posts in each thread prior to 11:59 p.m. Eastern Time on Sunday. Of course, you may always post more than the required number of replies and you are encouraged to continue participating in the Forum even after you have met the minimum number of posts required. Your follow-up posts must contain substance and should add additional insight to your classmates’ opinions or challenge their opinions. It is never sufficient to simply say, “I agree with what you wrote” or “Good post.” You must use your follow-up posts as a way to continue the Forum at a high level of thinking. Be sure to read the follow-up posts to your own posts and reply to any questions or requests for clarification, including questions posted by your professor. You will be expected to log into the classroom several times each week to participate in the class Forum. Forum postings are a large part of your grade and I will be looking for quality and depth in your postings.
Case Study Exam
The Case Study will consist of short essay questions. The approximate length is 3-6 pages, although I am more concerned about content then length. This exam is open book, non-proctored, and untimed. It focuses on Case Studies related to aspects of the degree some of which are not directly covered in this class. Therefore, open book means all your books used in this program. The final exam must be completed by the end of Week 8. You may access the exam as many times as you wish, but you may only submit it once.
The proposal is a proposal you are making to improve a process using IT. It is composed of two items. The first is a Preliminary Investigation Report /System Requirements Document and the second is a System Design Specification
Preliminary Investigation Report /System Requirements Document
A Preliminary Investigation and System Requirements are required for your proposal. This is normally two different documents but due to the length of the course, we will combine them. A typical Preliminary Investigation Report consists of a findings, recommendations and cost/benefit analysis. There is an explanation of the investigation in Chapter 2 of the text and example in the text Fig 2-29.
Yours should be longer and provide more detail as this is normally accompanied with a presentation. It should be two to three pages. The goal is not to complete the proposal but to demonstrate you have a clear picture of the task before you.
Normally you would get approval of the investigate report before formalizing the requirements. However, for this assignment we are assuming those things have taken place.
The system requirements section, which will be included, contains the requirements for the new system. It describes the alternatives considered, and makes a specific recommendation to management. This important document is the starting point for measuring the performance, accuracy, and completeness of the finished system before entering the systems design phase. The system requirements document is like a contract that identifies what the system developers must deliver to users.
You should write the system requirements in language that users can understand so they can offer input, suggest improvements, and approve the final version. Items should include the area brief overview of the purpose and primary objectives of the system project a requirements overview, conceptual processes and data models, security requirements, access ability requirements, data volume requirements , integration requirements and recoverability requirements.
System Design Specification
Your System Design Specification will be due at the end of Week 7. It is the deliverable for the Systems Design Phase. Review chapter 10 for requirements, Please use the Template in the in the classroom for this assignment. The template contains the correct format.
Each week there will be an analysis exercise to be completed by teams that will be set-up the first week of the course. Teams will consist of 3-5 members and be responsible for interacting and responding to the analysis exercise under the forum. A single group response will be posted weekly to address the mini-case presented during week 2. Group forum responses should be approximately 200 words.
Please remember that no extensions to the course will be given unless the student has been in communication with the professor, as required, during the semester, and unless the student has completed at least 50% of the assignments, with a passing grade. If a student should have a significant medical or work related reason why an extension should be given, the student must communicate that to the professor prior to the due date of each assignment. Assignments will not be accepted if an extension for that assignment has not been requested prior to the due date of the assignment, or if the assignment is handed in more than 14 days late. Assignments handed in after the due date, without prior permission from the instructor, will be docked points for each day late after the due date.
- Microsoft Office (MS Word, MS PowerPoint, MS Access)
- Adobe Acrobat Reader (Click here for free download)
Association for Computing Machinery (ACM): http://www.acm.org/
IEEE Computer Society: http://www.computer.org/portal/site/ieeecs/index.jsp - also our online library has the full collection of IEEE Digital Library articles.
Laudon, K. C., & Laudon, J. P. (2015). Management Information Systems, 14th ed. Upper Saddle River, NJ: Prentice-Hall
O’Brien, J., & Marakas, G. (2013). Management Information Systems. New York, NY: Mcgraw-Hill
Project Management Institute (PMI): http://www.pmi.org/info/default.asp
Rainer, R. K., &Prince, B. (2013). Introduction to information systems: Supporting and transforming business, 5th ed. Hoboken, NJ: John Wiley & Sons, Inc.
Stair, R., & Reynolds, G. (2015). Fundamentals of Information Systems, 8th ed. Boston, MA: Thompson Course Technology Publishing
|Book Title:||Various resources from the APUS Library & the Open Web are used. Please visit http://apus.libguides.com/er.php to locate the course eReserve.*|
Not current for future courses.