week-1.pdf

SOUTH EAST ASIAN INSTITUTE OF TECHNOLOGY, INC. COLLEGE OF INFORMATION AND COMMUNICATION TECHNOLOGY National Highway, Crossing Rubber, Tupi, South Cotabato ___________________________________________________  LEARNING MODULE...

SOUTH EAST ASIAN INSTITUTE OF TECHNOLOGY, INC. COLLEGE OF INFORMATION AND COMMUNICATION TECHNOLOGY National Highway, Crossing Rubber, Tupi, South Cotabato ___________________________________________________  LEARNING MODULE FOR IT 323 SYSTEM INTEGRATION AND ARCHITECTURE I _____________________________________________________ WEEK 1 COURSE OUTLINE COURSE CODE : IT 323 TITLE : System Integration and Architecture 1 TARGET POPULATION : All Bachelor of Science and Information System INSTRUCTOR : MS. MELISSA T. ZOLINA Overview: The course focuses on how a proposed system will be integrated with other existing or planned systems. It addresses the System Integration problem using architectures as the basis and then addresses the evaluation of the architectures in terms of the capabilities they provide. Objectives: General Objective  To provide the students an understanding of the technical and business process issues involved in systems integration.  Identify integration issues upfront in the process of System Integration and should be able to identify the best practices that ensure successful System Integration.  Have an understanding of the technical and business process issues involved in systems integration. Instruction to the Learner Teaching this course will be in lecture form. A number of case studies will also be used to illustrate some concepts as mentioned in the indicative content. The System of Systems Integration Problem Human, Organizational, Societal Cultural, Economic, and Technological aspects. The theory and practice of business process integration, legacy integration, new systems integration, business-to-business integration, integration of commercial-off-the-shelf (COTS) products, interface control and management, testing, integrated program management, integrated Business Continuity Planning (BCP). Specific focus will be given to issues of interface integration and interoperability of systems. Getting Started System an array of components designed to accomplish a particular objective according to plan. Many sub-systems may be designed which later on are combined together to form a system which is intended to achieve a specific objective which may be set by the Project manager. Systems thinking  Is a way of understanding an entity in terms of its purpose, as three steps  The three major steps followed in systems thinking 1. Identify a containing whole (system), of which the thing to be explained is a part. 2. Explain the behavior or properties of the containing whole. 3. Explain the behavior or properties of the thing to be explained in terms of its role(s) or function(s) within its containing whole (Ackoff, 1981) System Integration is the combination of inter-related elements to achieve a common objective (s). System Architecture The architecture of a system defines its high-level structure, exposing its gross organization as a collection of interacting components. Elements needed to model a software architecture include: Components, Connectors, Systems, Properties and Styles Project From the key terms described above, a system developer and architects cannot do anything without first establishing various projects. These projects may be new or existing. So it is inevitable to first understand what a project is, factors that influence the project, who the owners are and many more as discussed below. What Is a Project? A project is a temporary endeavor undertaken to accomplish a unique product or service Attributes of projects unique purpose temporary require resources, often from various areas should have a primary sponsor and/or customer involve uncertainty Where do information Systems Projects Originate (Sources of Projects)? New or changed IS development projects come from problems, opportunities, and directives and are always subject to one or more constraints. 1. Problems – may either be current, suspected, or anticipated. Problems are undesirable situations that prevent the business from fully achieving its purpose, goals, and objectives (users discovering real problems with existing IS). 2. An Opportunity – is a chance to improve the business even in the absence of specific problems. This means that the business is hoping to create a system that will help it with increasing its revenue, profit, or services, or decreasing its costs. 3. A Directive – is a new requirement that is imposed by management, government, or some external influence i.e. are mandates that come from either an internal or external source of the business. Projects Cannot Be Run in Isolation Projects must operate in a broad organizational environment Project managers need to take a holistic or systems view of a project and understand how it is situated within the larger organization Stakeholders Stakeholders are the people involved in or affected by project activities Stakeholders include the project sponsor and project team  support staff customers users suppliers opponents to the project Importance of Stakeholders Project managers must take time to identify, understand, and manage relationships with all project stakeholders Using the four frames of organizations can help meet stakeholder needs and expectations Senior executives are very important stakeholders What Helps Projects Succeed? According to the Standish Group’s report “CHAOS 2001: A Recipe for Success,” the following items help IT projects succeed, in order of importance: Executive support User involvement Experienced project manager Clear business objectives Minimized scope Standard software infrastructure Firm basic requirements Formal methodology Reliable estimates