Your Scenario

Welcome - Overview

team image

You will be learning the course content by solving several "real-life" scenarios. Each scenario is related to a specific area in information technology (e.g., hardware, software, etc.)

You will notice the five process steps that guide you through each scenario. These process steps are similar to the formalized process professionals use to implement IT projects. This formalized process is known as the System Development Life Cycle (SDLC).

We have modified some of the terminology of a formal SDLC process to best fit all scenarios, but take a few minutes to review each one in this overview. This will help you understand the purpose of each step in the process.

You will also note the Deliverables and Resources listed for each scenario. Deliverables are specific, tangible work product that you will be expected to create. For the purposes of this class, the deliverables will be submitted as your assignment.

Resources are very important. You don't have a textbook to guide you, so your resources are the items you will use to better understand the content area. Some resources will be reference files to download and read. Others will be detailed online sites that should be fully explored and read. You will also be guided to conduct effective online research to gather the information needed for each scenario.

There is also a career spotlight and related video for each topic. Be sure to read and watch these as they better explain how this information technology relates to a future career or future job assignment.

Now, check out our definitions of the 5 SDLC processes. Then you will be ready to begin your first scenario.

Welcome - Scope

team image

We've called this process step, "Scope". In a formal SDLC process you will typically hear the first few steps as "Initiation", "Preliminary Investigation", "Preliminary Analysis", and/or "System Concept".

It is this phase where the organization decides to pursue the systems project and identifies what the scope and objectives are for the project.

Since you (as a student) don't get to decide whether or not to pursue a project, we have focused this process on defining the scope of the business problem and outlining the general objectives for the project.

Welcome - Analysis

team image

In this step, the problem is thoroughly examined to determine what should be done. This is where detailed requirements are documented. This is where you will do your research and provide a clear "roadmap" to solving the problem.

This is an important step. Oftentimes you will need to seek out your resources during this step because this is where you are trying to clearly understand all you can about the problem and the solution.

This might be a visual diagram or other such documentation that clearly lays out how the problem is to be solved.

Welcome - Design

team image

We've combined some aspects of the "Design" phase with the "Development" phase for the purposes of our process. In this Design step you will actually be creating the solution. You will use the analysis completed earlier to guide you in the development and design of the solution.

This is where you will begin work on your deliverables. After completing your deliverables, remember you aren't ready to have them evaluated (or turned in) until you go through the next step, "Testing".

Welcome - Testing

team image

After creating a solution as part of the "Design" step, you must be sure it works for system users. This is where you must think about how system users will "use" the system. We refer to this as different "Use Cases" and it is important to the effectiveness and reliability of any system to comprehensively test all components.

For each scenario project you will be introduced to the idea of testing. Testing of your work product will range from the simple to the more complex.

Welcome - Evaluation

team image

In a real system project you would create, test, implement and then you would maintain it. Instead of formal implementation and maintenance steps, we are incluing an "Evaluation" step. This is where you get feedback on your project and determine objectives were met and which were not. You also find out what "enhancements" should be considered in order to improve upon the project.

For this course this is where you will hear back from your instructor and/or peers.


Introduction To Information Technology © 2014 English (US)