
Maryland in Europe Graduate Programs
Bowie State
University
Computer Concepts
INSS 510
Rhein Main
|
Dates: October 28, 2002 to December 21, 2002 Weekends: 09:00 until 17:00 Oct 26 - 27 Nov 09 - 10 Nov 23 - 24 Dec 14 |
Credits:
3 Semester Hours Prerequisites: All undergraduate prerequisites or permission of the instructor. Programming skills are a must for this class. Reading: Students must come to class prepared to discuss the scheduled topics for that class meeting. Therefore the student is expected to have read the assigned chapters in the textbook. |
|
Professor:
Mr. Charles Dekle
|
Faculty Account - Please use
this one first. Home Account - Use this one if the
first fails. Web Page: |
|
Prerequisites: All undergraduate prerequisite courses or permission of the instructor. Knowledge of a programming language is essential. |
Office
information:
Please leave a message with the UMUC Field Representative. |
Course Description:
This course will provide an overview of computer concepts as they apply to MIS professional. Emphasis will be placed on basic machine architecture including data representation and manipulation; principles of operating systems; software algorithms and programming languages. In addition, basic concepts of data organization, file structures, and principles of networking will be examined. Emerging trends in computer technology and their impact on organizations information systems will also be discussed. Students will be required to complete a programming project and a research project or an assembly language programming project using a pseudo language.
Course Goals/Objectives:
At the beginning of each chapter in the textbook the author lists the chapter goals. Those goals are the objectives of this class. The midterm and final will cover those goals. The student is responsible for all of those topics even though they may not be covered in class.
Students who complete this course should understand:
- Basic principles of computer architecture
- Major operating system concepts
- The interrelationships between operating systems and computer hardware
- Concepts of programming languages, including machine, assembly and high level languages
Required Textbook:
Systems Architecture,
Stephen D. Burd, Third Edition, 2001. Publisher: Course Technology Thomson
Learning, Canada,
ISBN 0-619-03418-1
Textbook web page: http://www.course.com
Suggested Reading:
The Architecture of Computer Hardware and Systems Software An Information Technology Approach, Irv Englander, Second Edition, John Wiley & Sons, Inc., New York, 2000, ISBN 0-471-36209-3.
The Hidden Language of Computer Hardware and Software, Charles Petzold, Microsoft Press, Redmond, Washington, 2000, ISBN 0-7356-1131-9
Computer Systems, J. Stanley Warford, Jones and Bartlett Publishers, Sudbury, MA, 1999, ISBN 0-7637-0794-5
Assembly Language Step-by-Step Second Edition, Jeff Duntemann, John Wiley & Sons, Inc., New York, 2000, ISBN 0-471-37523-3
The Mythical Man-Month Essays on Software Engineering Aniversy Edition, Frederick P. Brooks, Jr., Addison-Wesley, Reading, Massachusetts, 1995, ISBN 0-201-83595-9
Grading System: The instructor will award grades based on the following:
|
Course Evaluation: |
Mid-Term Exam |
30% |
|
|
Final Exam |
40% |
|
Note: there will be a 25% deduction for assignments turned in past the due date. Any assignment that is more than a class meeting late will receive a grade of zero unless there is a reasonable excuse. The deadlines are set in stone. If you have a very good reason for applying for a extension, the instructor will consider it. The instructor retains the right to decide what is reasonable. |
Programming Project |
15% |
|
The instructor will discuss requirements and format during the first class meeting |
Hardware Research Project or Assembly Language program project using a pseudo assembly language with class presentation and discussion |
15% |
|
Grade Ranges: |
90 to 100% |
A |
|
|
80 to 89 |
B |
|
|
70 to 79 |
C |
|
|
Less than 70% |
F(a) |
Programming Project: There will be one programming project assigned in this course. You may use any current programming language to fulfill the requirements of the project. The following are project requirements:
- Programming Projects must be well documented
- Programming projects should:
- Be modular
- Use named constants to enhance modifiability
- Use variable identifiers that are meaningful
- Use indentation and module (function) headings as appropriate
- Programming projects must be complete
- Programming projects must be tested
- Programming projects must meet design specifications prior to submission
Project Format: Submit the programming project in a folder and adhere to the following format:
- The cover page should contain only a heading which must be centered and include these items:
- University of Maryland University College
- Your Name
- Assignment Number
- Due Date
- Date Submitted
- The Assignment Description must have six parts:
- A brief description of the assignment
- Programming language used
- List the advantages and disadvantages of the programming language.
- How to use the program
- Problems encountered
- A statement that the program works or does not work
Source Code: In addition to a print out of the source code, each project must include a magnetic copy of the program on a 3.5" floppy disc. The source code should have the following statement at the end of the file. Make sure that you use the proper format for including comments in the particular programming language:
I certify the above code is of my own development and design. I have given proper credit to any outside source. The program compiled and executed as described and produced the stated output.
Important Information: In order to receive credit you must submit assignments in the proper format. The instructor may assess a 5% penalty for failure to comply with all of the project requirements.
Hardware Research Project or Assembly Project with Presentation: The format and possible topics will be discussed during the first weekend class meeting. Students must follow the APA (American Psychological Association) style for the paper.
Tentative Schedule:
|
Class |
Topic |
Reading |
Comments |
|
1. Oct 26 |
Course Introduction Computer Technology: Your Need to Know Introduction to Systems Architecture Data Representation |
Handouts Chapter 1 Chapter 2 Chapter 3 |
Instructor Textbook Textbook Textbook |
|
2. Oct 27 |
Data Representation - Continued Processor Technology and Architecture Data Storage Technology |
Chapter 3 Chapter 4 Chapter 5 |
Textbook Textbook Textbook |
|
3. Nov 09 |
System Integration and Performance Input/Output Technology Data and Network Communication Tech. |
Chapter 6 Chapter 7 Chapter 8 |
Textbook Textbook Textbook |
|
4. Nov 10 |
Review and catch-up Midterm Exam 14:00 until 17:00 |
Chapters 1 - 7 Chapter 1 - 8 |
Textbook |
|
5. Nov 23 |
Programming Project Due Computer Networks Application Development Operating Systems |
Chapter 9 Chapter 10 Chapter 11 |
Brief Presentation by student Textbook Textbook Textbook |
|
6. Nov 24 |
File Management Systems Internet and Distributed Applications System Administration |
Chapter 12 Chapter 13 Chapter 14 |
Textbook Textbook Textbook |
|
7. Dec 14 |
Presentation of Research Work Review Final Exam 14:00 until 17:00 |
Chaps 9 - 14 |
Students Textbook |
Notes:
1) The schedule is tentative and may change during the term.
2) The instructor will provide a recommended reading list during the first week.
Additional Information:
When you e-mail me please use the UMUC address. That is my faculty address. Also begin the subject line with INSS 510: followed by the subject itself.
Please do not ask me to debug your programs for you. It is my intention to provide lab time as part of the class schedule. If you submit your project for debugging, I will consider it complete and grade it as submitted.
I will cover theory and give examples in the lecture portion of the class. We may make use of the lab to illustrate some basic programming concepts. This depends on availability
As noted the course schedule is tentative and may change depending on the needs of the class. We may actually speed things up or, as is more likely the case, slow things down.
The following are a couple of very handy text editors. I use TextPad. The Project may be accomplished with a text editor and a command-line compiler.
- A text editor: On a Windows PC, it can be one of the following
- UltraEdit. This is a very nice programmer's editor with syntax coloring. One can test it free for 45 days. As shareware it costs only $30. It is a bargain. This is the text editor that I use.
- TextPad This is also a nice programmer's editor and also has syntax coloring. It comes with a free trial period and costs $27.
- Any other ASCII text editor such as the Windows' Notepad.