Course Syllabus PRG/211 Version 3

Course Syllabus
Information Systems & Technology PRG/211 Version 3 Algorithms and Logic for Computer Programming
Copyright 2010, 2011 by University of Phoenix. All rights reserved.

Course Description This course provides students with a basic understanding of programming development practices. Concepts covered include the application of algorithms and logic to the design and development of procedural and object oriented computer programs to address the problem solving requirements associated with business information systems. This course will cover procedural programming concepts including data types, controls structures, functional decomposition, arrays, and files, classes and objects. 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 Bohl, M., & Ryann, M. (2008). Tools for structured and object-oriented design: An introduction to programming logic. Upper Saddle River, NJ: Pearson Prentice Hall Crews, T., & Murphy, C. (2009). A guide to working with Visual Logic. Boston, MA: Cengage Learning. Drake, E., & Venit, S. (2011). Prelude to programming: Concepts and design. Boston, MA: Addison-Wesley. Gaddis, T. (2010). Starting out with programming logic & design. Boston, MA: Addison-Wesley. Software Element K Visual Logic All electronic materials are available on the student website.

Week One: Programming Fundamentals

Details Due Pnts

Course Syllabus PRG/211 Version 3

Objectives

1.1 Identify how a computer processes and stores data. 1.2 Describe procedural and object-oriented programming languages. Read Ch. 0, Introduction, of Prelude to Programming.

Reading

Reading Reading Reading

Read Ch. 1, An Introduction to Programming, of Prelude to Programming. Read Ch. 1, Input, Process, Output, of A Guide to Working With Visual Logic. Read Ch. 14, Object-Oriented Programming, of Starting Out With Programming Logic & Design.

Nongraded Activities and Preparation Visual Logic Installation

Hands On: download and install Visual Logic

First - browse A guide to working with Visual Logic see link in our Materials tab. Watch the tutorial at http://www.visuallogic.org/VLTutorial.html Download and install the Visual Logic program (http://uop.visuallogic.org/). Provide your University of Phoenix student e-mail address to obtain the required VLSig file. You will then be directed to the download site for the Visual Logic application. Make sure to contact tech support in case of issues you MUST have this working by the end of week1! Create your first VL program: Hello World. Name the file HelloWorld [your name].vls The chart will simply display hello World its [your name] when you run it. Attach to a reply in this thread. Do test-run the program using the PLAY button. Note that VLS files have to be opened from within the VL application. Do not try double-clicking to have them run -- this is not a standard commercialmarket process. Also note: our Course Materials forum should have sample programs I created; do run them throughout the course. If necessary, heres the number: Tech Support at 877-TECH-UOP.

ASAP

Learning Team Instructions Final Learning Team Paper and Presentation (Preparation)

Week1 Team Work Review the assignment instructions for the Final Learning Team Paper and Presentation, due in Week Five. No deliverable due this week. Note that I try to create the teams based on some knowledge of the students (as much as possible ), so -I will announce the teams makeup on Monday of week2, with the team charter due Thursday of week2. Do read the team project instruction so you hit the ground running.

None

Course Syllabus PRG/211 Version 3

Individual Programming Fundamentals Paper

Week1 Individual Programming Project Note that your individual work here is open to your peers. You may apply the feedback you receive towards the actual submission to me. Read the instructions for Programming Fundamentals Paper from the materials tab on the website. Choose 1 of these 2 assignments. Week1.1 : Reusability of Code OR Week1.2 : Transforming Data into Information Note that you are expected to post in Saturday in Main and submit to Assignments on Monday: - By Saturday, post to Main in this thread; post in the body of the message, not as an attachment - By Monday, submit (improved?) paper as a Word attachment to Assignments. Name your file your name paper subject; for example: John Doe Reusability of Code. (Note that attachments are
being aggregated elsewhere and information as to who submitted is lost.)

Sat / Mon

10

Note: while option 1 subject is specific, option 2 is more open to interpretation. In Week1.2 you are expected to ponder the transformation of data to information in the context of programming. You are not seasoned enough to write a truly lengthy paper, but within the limit requested, you can start the thinking process by considering the mentioned elements. Be open; be creative. Every paper in this class should contain: - An abstract: explain the context and the task this paper is trying to accomplish - A conclusion: what have we learnt here, what is there to look forward to - References: at least 2; they are not necessarily "quoted from" type references, but they signify the context in which you operate . Note that all papers in this class should follow the APA guidelines. To reach APA resources : Materials Tab / Center for Writing Excellence / Tutorials & Guides / APA Information Reminder: choose week1.1 OR week1.2

Participation and DQs

Please answer 2 of these DQs; due in Main throughout the week. Also: 6 participation posts per week and a summary. Participation posts are those in Main that is relevant to the ongoing discussions (from any week) or an initiation under Other Threads. Is has to be substantial adding some value. The summary thread will be available Sunday morning.

Week long

Course Syllabus PRG/211 Version 3

DQ1.1 : Pseudo Code Write a 200 to 300 word mini-essay covering the following: Define Pseudo Code. Is it a language? Is it specific to one programming language? Bring examples and explain them. Reminder: you are expected to answer 2 of the 3 DQs. DQ1.2 : Flowcharts Write a 200 to 300 word mini-essay covering the following: What is a flowchart? How is a flowchart useful in developing and documenting software? Why is the interactive Visual Logic flowchart program more useful than a manually drawn flowchart? Is a flowchart more valuable in documenting the logic of a program than just the coded instructions in the programming language? Explain your answer.

Reminder: you are expected to answer 2 of the 3 DQs. DQ1.3 : Benefits of Object-Oriented Programming Based on our materials and further research, write a 200 to 300 word miniessay to covering the following: Object-oriented programming The role of code reuse in object-oriented programming Under what circumstances is object-oriented programming best suited? Note that much of the post should be about the essence of OO rather than the comparison to Procedural Programming.

Reminder: you are expected to answer 2 of the 3 DQs.

Week Two: Problem Solving and Algorithm Development

Details Due Pnts

Objectives

2.1 Describe the process and methods for problem recognition. 2.2 Analyze the development of procedural and object-oriented problem solutions. 2.3 Define the process of algorithm development. 2.4 Describe the importance of using a structured modular approach to program development. Read Ch. 10, Introduction to Object-Oriented Design, of Tools for Structured and Object-Oriented Design.

Reading

Course Syllabus PRG/211 Version 3

Reading

Read Ch. 2, Input, Processing, Output, of Starting Out With Programming Logic & Design. Read Ch. 2, Developing a Program, of Prelude to Programming. Week2 Individual Programming Project Deliverables: Paper due Saturday then Monday (see details below) Sat / Mon 11

Reading Individual Programming Development: Part 1

For this assignment, choose from the following options: Option 1: Programming Solution Option 2: Personal Learning Management

Read the instructions in the University of Phoenix Material: Programming Development located on the student website and select one option to complete the assignment. Note: -

Once chosen, you have to stick with this one for the duration This assignment has a team component (team QA your peers will review your individual work), so you may want to discuss with your colleagues whether to simplify (all choose one project) or enrich (exposure to both projects).

Every paper in this class should contain: - An abstract: explain the context and the task this paper is trying to accomplish - A conclusion: what have we learnt here, what is there to look forward to - References: at least 2; they are not necessarily "quoted from" type references, but they signify the context in which you operate . While it is tempting to focus on the conceptual terms learned in class, the paper should give a clear picture of what the program might actually do. You may alter the scope later, after you start programming; but you need to think here of possible hands-on applications for the code rather than stay conceptual. This assignment is due twice: - Post by Saturday to team folder for review. The team may decide to allow a later due date, but all work and QA reviews are due Monday. Coordinate these well, teams! I recommend creating one thread for all to post in. Do start a thread in the team forum for this work (Week2-IndividualProject) - Submit by Monday (you may improve the work) to Individual Programming Naming This is extremely important as files are being aggregated elsewhere:

Course Syllabus PRG/211 Version 3

Name your files so it is clear: - What week it is - What project is covered - Who submitted the work For example: week2 Programming Solution John Doe.docx

Learning Team Instructions Charter, Final Learning Team Paper and Presentation

Week2 Team Work Teams makeup will be announced by end of day, Tuesday. Deliverables (see details below): Charter by Thursday QA by Monday Paper by Monday Note that the team grade is assessing your skill as a collaborator; it conveys the level of success of the team to operate as a single, seamless unit. I do penalize slackers. You should strive to come off as a single, seamless entity. Team work is not just a split-the-work exercise; while one writes, the others may edit or verify adequate adherence to instructions. This is about Collaboration!

Thu / Mon

Team Charter Resource: Learning Team Toolkit (Materials Tab) Complete the Learning Team Charter by incorporating individual entries into a single document Due Thursday in Team Work Assignments Tab. Team Project Choose your project and review instructions for week1 and week2 Begin working on the Final Learning Team Paper and Presentation assignment. Do start a thread in the team forum for this work (Week2-Team-Project) Submit this weeks portion by Monday to the Assignments Tab Naming This is extremely important as files are being aggregated elsewhere: Name your files so it is clear: - What week it is - What project is covered - What team submitted the work For example: week2 Calorie Management Team E.docx Note: Week1 instructions are general guidelines for the project. They should be reflected in your paper. Papers are expected to be rich, rather than provide a lean answer. You want the paper to include information that will help the reader understand the situation you encountered and your choices.

Course Syllabus PRG/211 Version 3

Every paper in this class should contain, and clearly sub-labeled as: - Abstract: explain the context and the task this paper is trying to accomplish - Conclusion: what have we learnt here, what is there to look forward to - References: at least 2; they are not necessarily "quoted from" type references, but they signify the context in which you operate. What not to include? The instructions specify you should, at this point, only deal with top view, and leave lower-level details for next week. It is always a good practice to read next week's task to understand the trajectory of the expectations. Team Quality Assurance One QA sheet per team; this is to express the status of the team as per the individual assignments in a compressed way. The team supports, but also critics it members Individual Assignments using a Quality Assurance form. Papers / Flowcharts are submitted by Saturday (or at the teams discretion), and by Monday members should have assessed how well their peers did. Create a Quality Assurance form to fit your team, and fill it. The review should present the consensus of the team regarding individual work one final document per team; no need to state who said what, just what all agree on and who participated. Avoid generic charts that are just Yes and No entries qualify your assessments when possible. The process should be: 1. Collect individual reviews optimally, everyone should be reviewing every element sent in by teammates. 2. Create the combined report in MS Word, please. This will need compression and translation, so if John wrote I do not understand it and Mary wrote incomprehensible, you should figure out this is the same thing and include just one such comment. An example: Week3 - Team E - QA
Sent by: Steve Sarah Seth Paper Good; detailed Good; not APA N/A Flowchart N/A N/A Does not run properly Creative mentions Impressively complex Reviewed by John, Kelly Steve, Seth Sarah

You may modify this form slightly if you see fit You may leave the Flowchart column empty on week 2. Note that part of your grade is related to your review of other members; absence from QA process as programmer OR reviewer will affect your grade.

Course Syllabus PRG/211 Version 3

Name your file appropriately. Example: Week2 - Team E - QA.docx Submit to Assignments Team Work by Monday.

Nongraded Activities and Preparation Visual Logic training

Continue exploring Visual Logic. Run and examine programs 1 through 3 from our Materials Forum examples. Explore elements from the Menu such as Debug and Procedures. Ponder -- how can the Visual Logic program be used to determine the effect a single grade (such as a B or C) will have on your grade point average (GPA)? Use this thread to discuss hurdles and accomplishments in regard.

Week long

DQs and Participation

Please answer 2 of these DQs; due in Main throughout the week. Also: 6 participation posts and a summary. DQ2.1 : Algorithm Development Based on our materials and further research, write a 200 to 300 word miniessay to covering the following: Features commonly found in programming languages The five key steps in the programming process The common errors occur in programs

Week long

DQ2.2 : Pseudo Code and Flow Charts Write a 200 to 300 word mini-essay covering the following: Define the 2 terms one against the other. Is it possible to create one based on the other? Create one or two examples in code and VL and present in your reply (you can easily create an image of your VL flowchart using a screen capture software such as ScreenHunter Free; drag and drop to embed in the post) DQ2.3 : Modular Programming Write a 200 to 300 word mini-essay covering the following: Explain what is meant by a modular approach to programming. Why is this approach important? What is the relation to OO Programming?

Week Three: Programming Logic

Details Due Pnts

Objectives

3.1 Demonstrate the sequential and selection processing control structure. 3.2 Examine the iteration control structure.

Course Syllabus PRG/211 Version 3

3.3 Apply flowcharts to represent logic.

Reading

Read Ch. 3, Selection Structures: Making Decisions, of Prelude to Programming.

Reading Reading Reading Reading Reading

Read Ch. 4, Repetition Structures: Looping, of Prelude to Programming. Read Ch. 5, More about Loops and Decisions, of Prelude to Programming. Read Ch. 2, Making Decisions, of A Guide to Working With Visual Logic. Read Ch. 3, While Loops, of A Guide to Working With Visual Logic. Read Ch. 4 For Loops and Nested Loops of A Guide to Working With Visual Logic. Week3 Individual Programming Project Deliverables: Paper and VLS due Saturday then Monday (see details below) Sat / Mon 12

Individual Programming Development: Part 2

Resource: University of Phoenix Material: Programming Development Review the University of Phoenix Material: Programming Development. This assignment is due twice: - Post by Saturday to team folder for review. The team may decide on a later due date, but all work and QA reviews are due Monday - Deliverables: paper and VLS file - Submit by Monday (you may improve the work) to Individual Programming Follow naming rules! Note the flowchart should include a selection structure. Do test-run the program using valid and non-valid inputs.

Learning Team Instructions Final Learning Team Paper and Presentation (Preparation)

Week 3 Team Work Deliverables (see details below): QA by Monday Paper by Monday VLS by Monday Team Evaluation (one from each member) to Personal Folder

Mon

Team Paper and Flowchart Continue working on the Final Learning Team Project. Note that I expect the paper to be cumulative, so always add to the previous submission and get a sense of how the paper develops. The Pseudo Code should be incorporated into the main paper.

Course Syllabus PRG/211 Version 3

10

Also send in a basic VLS file for the project. Submit by Monday to Assignment Tab Follow naming rules! Team QA Note that team QA and Team Evaluation are not the same Submit QA by Monday to Team Work Follow naming rules! Mid-course Team Evaluation Submit team evaluation (see Team Toolkit for form in the Materials Tab) by Monday to your namesake forum. Include your assessment of your own work. QA and Evaluation are separate submissions! DQs and Participation Please answer 2 of these DQs; due in Main throughout the week. Also: 6 participation posts and a summary. DQ3.1 : Using Control Structures Based on our materials and further research, write a 200 to 300 word miniessay covering the following: The sequential flow of a program Branching within a program How is branching controlled? The role of an if statement in control structures Code examples are most appropriate DQ3.2 : Single-Dual Alternatives and Case Structures Write a 200 to 300 word mini-essay covering the following: The similarities and differences between single alternative structures, dual alternative structures, and case structures. Do provide an example of one of the three control structures using pseudocode. Try to provide an example that has not already been posted. Include code examples. Experiment with using if-else in Visual Logic. You should embed visuals in your post using screen-capture software.
Week long

DQ3.3 : Iteration and Repetition Structures Write a 200 to 300 word mini-essay covering the following: What is an iteration structure? What problem does a repetition structure solve? Provide an example of a process in which a repetition structure is appropriately used. Include code examples. Experiment with using a loop in Visual Logic. You should embed visuals in your post using screen-capture software.

Course Syllabus PRG/211 Version 3

11

Week Four: Structures, Verification, and Validation

Details Due Pnts

Objectives

4.1 4.2 4.3 4.4

Explain array structures. Define objects and object-oriented classes. Apply arrays to program logic and data manipulation. Verify algorithms using requirements and desk review design.

Reading

Read Ch. 10, Introduction to Object-Oriented Design, of Tools for Structured and Object-Oriented Design. Read Ch. 9, An Introduction to Object-Oriented Programming, of Prelude to Programming. Read Ch. 6, Arrays: Lists and Tables, of Prelude to Programming. Read Ch. 5, Arrays, of A Guide to Working With Visual Logic. Read Ch. 7, Input Validation, of Starting Out With Programming Logic & Design. Week4 Individual Programming Project Deliverables: Paper and VLS file due Saturday then Monday (see details below) Resource: University of Phoenix Material: Programming Development Review the University of Phoenix Material: Programming Development. Sat / Mon 12

Reading

Reading Reading Reading

Individual Programming Development: Part 3

This assignment is due twice: - Post by Saturday to team folder for review. The team may decide on a later due date, but all work and QA reviews are due Monday - Deliverables: paper and VLS file - Submit by Monday (you may improve the work) to Individual Programming Follow naming rules! Note the flowchart should include an array. Do test-run the program using valid and non-valid inputs.

Learning Team Instructions Final Learning Team Paper and Presentation (Preparation)

Week4 Team Work Deliverables (see details below): QA by Monday Paper, VLS and Presentation by Monday Team QA Submit by Monday to Team Work. Follow file-naming rules!

Mon

Course Syllabus PRG/211 Version 3

12

Team Paper and Flowchart Continue working on the Final Learning Team Paper and Presentation assignment. The paper may be longer than length suggested by the instructions, as long as the information is relevant. The paper you submit this week has to be as polished as possible make sure it is coherent, well formatted, includes all elements needed. In a way, this is your final draft. Presentation You should also be working on the presentation. Note that the presentation is an introduction and an explanation, focused on the essence as well as a summary of the project it should be visually rich with relevant information and easy to follow. Explain the core of your work and the value you bring! The audience for this presentation is varied; from senior management looking to see that your solution fits their needs and requirements, to technical management that wants design details, to programmers who may be asked to join in the project. So include an intro to the project, connect the design to the task, provide insight into the technical aspects and choices made so those who read the paper and run your flowchart are up and running. No overcrowded visuals! Use bullets rather than sentences or lengthy text. The uninitiated as well as the person in the last row have to understand the work! The presentation may be longer than length suggested by the instructions, as long as the information is relevant.

Submit paper, presentation and a working VLS file by Monday to the Assignments Tab. Follow naming rules! DQs and Participation Please answer 2 of these DQs this week; due in Main throughout the week. Also: 6 participation posts and a summary. DQ4.1 : Arrays Structures Write a 200 to 300 word mini-essay: Explain arrays in layman-terms. Provide examples of code using arrays Explain parallel-arrays in layman-terms Similarities and differences of the array and parallel array structures Data that is appropriately stored in a parallel array structure How would pseudo code using an array be different from one using parallel arrays? Do provide examples.
Week long

Course Syllabus PRG/211 Version 3

13

DQ4.2 : Arrays in Pseudo Code and Visual Logic Write a substantial post that explains different uses of arrays in code and in VL. Mention ways to systematically access all occurrences of the array. Provide matching examples in code and VL. You should embed visuals in your post using screen-capture software. DQ4.3 : Define Object and Object-Oriented Classes Based on our reading materials and further research Write a 200 to 300 word mini-essay covering the following: Object-oriented programming Expand on the differences between a class and an object Event as it relates to object-oriented programming

Week Five: File Processing

Details Due Pnts

Objectives

5.1 Demonstrate reading and writing sequential files in pseudocode. 5.2 Differentiate between sequential and direct access. 5.3 Compare and contrast procedural and object-oriented programming. Read Ch. 14, Master File Update Processing, of Tools for Structured and Object-Oriented Design: An Introduction to Programming Logic. Read Ch. 8, Sequential Data Files, of Prelude to Programming. Read Ch. 14, Object-Oriented Programming, of Starting Out With Programming Logic & Design. Week5 Team Work Deliverables (see details below): Paper, VLS and Presentation by Monday Team Evaluation (one from each member) to Personal Folder Mon 15

Reading

Reading Reading

Learning Team Assignment Learning Team Paper and Presentation

Team Project Submit final paper, final VLS file and your presentation. Due Monday in the Assignment Tab. Follow naming rules!

Final Team Evaluation

Course Syllabus PRG/211 Version 3

14

Submit team evaluation (see Team Toolkit for form) by Monday to your namesake forum. Include your assessment of your own work.

DQs and Participation

Please answer 2 of these DQs; due in Main throughout the week. Also: 6 participation posts and a summary. DQ5.1 : Compare and Contrast Procedural and OO Programming This is the time to revisit the subject and provide a more educated contribution. Write a 200 to 300 word mini-essay covering the following: The role or place of structured methodologies, data, and algorithms What differs between object-oriented and object-based languages? The role or place of object-oriented objects, methods, properties, classes, instantiation, and encapsulation

Week long

DQ5.2 : Direct Access vs., Sequential Access Files Write a 200 to 300 word mini-essay covering the following: In which situations would you choose to use a direct access (aka random access) file instead of a sequential access file? Give a specific example and explain your reasoning.

DQ5.3 : Data Hiding Write a 200 to 300 word mini-essay covering the following: Explain the term data hiding, which is used in object-oriented programming. Is data hiding a valuable security consideration? Why or why not?

DQ5.4 : Issues Revisited (200-300 words) Pick 3 issues from what we covered in this course and elaborate on them: issues you would have wanted further discussion, issues that you think would be meaningful to you future, issues that you still have a comment in regard

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.