IST639 Enterprise Technologies Course Syllabus Spring 2014

Transcription

1 Location: Hinds Hall 117 Wednesday Nights 5:15 PM to 8:05 PM Doug Taber Office Hours: By Appointment Course Overview IST639 builds the basic understanding of the technical and management architecture that comprise enterprise computing environments. The course focuses on identifying and solving large complex problems by using enterprise computing technologies. Also, included are the basic architecture and technology principles that comprise enterprise computing environments. The course addresses the analysis of the underlying computer hardware and software architecture including: operating systems, management issues relating to enterprise and distributed computing systems, enterprise applications, databases, security, application development policies, standards and guidelines, software procurement, custom development, and operating system selection. Operating system features will be discussed as found in zos, Linux, Windows, and Unix. Various application development and deployment environments will be examined along with a discussion of software sourcing issues, software reuse design, software maintenance, change control and configuration management. Prerequisites None Course Objectives At the completion of this course students will be able to: Identify and solve large complex problems Describe when to use enterprise technologies Describe enterprise technology concepts Describe multi-tier architectures for large scale systems Describe key architectural concepts used in enterprise systems including transaction processing, messaging and queuing Describe key enterprise database concepts and different database systems including relational, hierarchical, sequential and emerging database systems Use large enterprise computing systems 1

2 Resources Text Null and Lobur, (2012), The Essentials of Computer Organization and Architecture, (3rd ed), Jones and Bartlett, ISBN Ebbers, M., O Brien, W., Ogden, B., Introduction to the New Mainframe: zos Basics, (2 nd ed), International Business Machines Corp. 2009, SG Readings There are a variety of articles that complement the textbook located in the Blackboard Learning Modules for this course, URL: 2

3 Grading Policy Final grades will be based on the number of points earned throughout the semester according to the table below. Grade Points A A B B B C C C F 399 3

4 Class Participation (100 points) Reading Assignments - Reading assignments must be completed prior to class. This will facilitate class discussions. We will be using the textbook in class; therefore, it is important that you bring the textbook to class. Class Discussion There will be discussion activities that include your responses to case study questions, discussion questions and real world problems in nearly every class. There are no provisions to make up missed class discussion activities. Therefore, it is important that you attend class. Issues and Answers Based on the past class, students will report on three to five important issues and policies and procedures to address these issues. These will be entered into Blackboard. Assignments (400 points) Enterprise News (50 points Individual) - Technology is changing at a rapid pace. It is important to pay close attention to technology news. We will discuss the current technology news in every class. There will be ten (10) Enterprise News discussions and Blackboard postings. You must find an enterprise technology article that is relevant to the topic being covered in class and post a brief summary (<24 lines) of an enterprise-related news item and your assessment of what it means to the IT industry, business or the consumer on Blackboard. zos Project (100 points - Group) This will be a group project assigned to create zos elements and execute them producing a set of deliverables. More information will be forthcoming. Labs (150 points - Individual) There will be six mandatory and one optional lab that will reinforce the concepts and principles covered in our classroom lectures, readings and discussions. Enterprise Technology Project (50 points - Group) This assignment will reflect your ability to use the enterprise technologies learned in this course to solve technology problems. For more detail, see the Enterprise Technology Project Guidelines. Presentation Project Service Oriented Architecture (50 Points Group) Exam (150 points) Mid-term Exam (75 points) This exam will be based on class lectures, readings, labs and other course related activities. This will be a take home exam and done individually. Final Exam (75 points) This exam will be based on class lectures, readings, labs and other course related activities. This will be a take home exam and done individually. 4

5 Assignment Policy Assignments Due Dates - All reading and written assignments (i.e. Enterprise News) assignments are due as of the date posted in Blackboard. All non-reading assignments (labs, models etc.) are due on these posted dates. Late assignments will be accepted, but may be assessed a reduction in points. Use the point system judiciously so that you can compensate for missed assignment due dates. Assignment Format - You are responsible for getting assignments from and to the instructor for missed classes. All assignments are to be prepared using word processing software (MSWord) or entered directly into Blackboard. Space and one half, 12 font is the accepted format. Also use compressed format (.zip). You are required to turn in all assignments via the Blackboard Learning System. Provide your resources for all written assignments. Cite your sources!! (URL etc). 5

6 Class 1: Jan. 15, 2014 Characteristics of Large Computer Systems Class Introductions At the end of this lesson the student will be able to: Be able to identify characteristics, advantages and disadvantages of large computer systems. Describe data representation in the IBM Mainframe Computer environment (binary and hexadecimal). Compute numbers and convert numbers using binary and hexadecimal. Class Exercise: Using the Windows Calculator. Class 2: Jan. 22, 2014 Software Application Systems At the end of the lesson students will be able to: Distinguish between hardware, software and firmware. Discuss the relationships between source code and executable machine code. Determine the economies of large and small computer systems. Class Exercise: Calculating the cost of computing. 6

7 Class 3: Jan. 29, 2014 Software Development Lifecycles Describe Software Development Lifecycle characteristics. Choose an SDLC based on software project characteristics. Describe how enterprise software packages are created, maintained and enhanced. Compare Commercial Off the Shelf Packages (COTS) with custom developed approaches. Class Exercise: Negotiating a software contract Class 4: Feb. 5, 2014 Programming Logic, Boolean Logic, Business Algorithms Develop basic decision tables and logic flows Write pseudo code to solve business problems Describe the use of computer logic in programming Class Exercise: Decision tables and Algorithms Readings will be assigned in Blackboard Class 5: Feb. 12, 2014 Operating Systems Types of Processing Give an overview of the main features of common computer operating systems. Compare computer languages and identify usages. Differentiate between hardware components. Describe the use of job control language used to run and control programs. Explain the need and usage of security systems within the computer operating system. Class exercise: Usage of processing types in system design. 7

8 Class 6: Feb. 19, 2014 Operating Systems (continued) At the end of this lesson the student will be able to: Describe the advantages of batch and on-line processing. Recant the historical development of batch and on-line processing. Write basic JCL commands to run computer programs. Discuss the security issues related to use of computer systems. Class - discussion of operating system features. Class 7: Feb. 26, 2014 Software Development Techniques Discuss the issues related to programmer proficiency. Describe the circumstances needed for use of programming techniques (modularity, code reuse, structured programming and object oriented design). Enumerate reasons for portfolio modernization as a business function. Class exercise: Writing policies for a programming staff. Class 8: Mar. 5, 2014 Quality Information Technology Organizations CMMI Articulate the issues and needs for a quality IT organization. Describe the attributes of a quality organization. Recount the historical development of the Capability Maturity Model (SEI). Class exercise: Writing a plan for implementing CMMI in an organization. 8

9 Class 9: Mar. 19, 2013 Software Testing Strategies At the end of this less the student will: Describe the need for different approaches to software testing. Describe requirements based and risk based testing. Contribute to a software test plan. Discuss the need for quality assurance in software. Mid-term examination no readings assigned. Class 10: Mar. 26, 2014 Service Oriented Architecture Group Project 1: Student presentations details will be outlined in Blackboard Class 11: Apr. 2, Computer Performance Issues and Strategies Explain the issues related to computer performance. List the features of software and hardware that can contribute to throughput. Develop policies to guide organizations in achieving desired computer performance goals. Discuss the importance of service level agreements for computer organizations. Class exercise: Writing organizational policies and documented procedures related to performance. Class 12: Apr. 9, Information Technology Direction Group Project 2: Student presentations details in Blackboard No readings assigned this week. 9

10 Class 13: Apr. 16, Computer Security Discuss the issues related to securing computer facilities, hardware, software and data. Contribute to writing policies for IT organizations for security. Discuss the need for security for business continuity. Class exercise: Writing a policy for IT staff. Class 14: Apr. 23, 2014 Managing Technical People Discuss the need for measuring and motivating the technical staff. Identify motivational techniques for the programming staff. Discuss the need for measurements (metrics). Final Exam: Apr. 23,