Systems Integration and Architecture - Lecture Slides PDF

Systems Integration and Architecture IT224 Engr. Ulrich Lee Uy, MSIT USTP – CITC 2-05-2025  Topics Covered Introduction to SIA System Architecture Frameworks Key Terminologies in SIA Understan...

Systems Integration and Architecture IT224 Engr. Ulrich Lee Uy, MSIT USTP – CITC 2-05-2025  Topics Covered Introduction to SIA System Architecture Frameworks Key Terminologies in SIA Understanding Organizations Project Life Cycle SDLC  What is System Integration? System integration refers to the process of combining different subsystems or components into a single system that functions as a whole. These subsystems or components can be hardware, software, or a combination of both. System integration is important because it allows different systems to work together, which increases efficiency and reduces costs. What is System Integration? What is System Integration? What is System Integration?  What is System Integration? The process of bringing together different components or subsystems into a single system Ensures that all subsystems work together seamlessly and effectively Critical to the success of any complex system  What is System Architecture?  System architecture refers to the design of a system, which includes its structure, behavior, and functionality. The architecture of a system is crucial because it determines the system's performance, scalability, and maintainability. A well-designed system architecture can reduce development costs, improve reliability, and ensure that the system meets its requirements. What is System Architecture? What is System Architecture? What is System Architecture?  What is System Architecture?  The overall design of a system  Describes the structure and behavior of the system  Includes the hardware, software, and other components of the system  Why is System Integration and Architecture Important?  System integration and architecture are essential concepts in computer engineering because they help ensure that systems are reliable, scalable, and maintainable. Without proper integration, systems can suffer from compatibility issues, which can lead to reduced efficiency and increased costs. Without proper architecture, systems can become unmanageable, making maintenance and upgrades difficult.  Why is System Integration and Architecture Important?  Ensures that the system meets the requirements of the stakeholders  Improves the reliability and efficiency of the system  Enables better communication and collaboration among team members  Reduces the risk of project failure and costly rework  Key Components of a System Architecture Hardware: physical components of the system Software: programs and applications that run on the system Communication protocols: rules for exchanging data between components Data storage: where the system stores and retrieves data Security: measures to protect the system from unauthorized access  Types of System Integration There are several types of system integration, including the following: Vertical integration involves integrating systems that are at different levels of the same hierarchy, such as hardware and software components. Horizontal integration involves integrating systems that are at the same level of the hierarchy, such as integrating different software applications. Hybrid integration involves integrating systems that are at different levels of the hierarchy and may use different technologies. Vertical VS Horizontal Hybrid Integration  System Architecture Frameworks  There are several system architecture frameworks that can be used to design a system's architecture, including the Zachman Framework, EA, TOGAF, and DoDAF. These frameworks provide a structured approach to designing a system's architecture, which helps ensure that all aspects of the system are considered.  Reporting #1  Volunteers to report on the different system architecture frameworks: Zachman – R4 () R9 () Enterprise Architecture – R4 () R9 () TOGAF – R4 () R9 () DODAF – R4 () R9 () Microservices – R4 () R9 () Service Oriented Architecture – R4 () R9 ()  Key Terminologies in SIA  System - An array of components designed to accomplish a particular objective according to plan. Many sub-systems many 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.  System Integration - Is the combination of inter-related elements to achieve a common objective (s).  Key Terminologies in SIA  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.  Key Terminologies in SIA  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)  Key Terminologies in SIA  Application Programming Interface (API): A set of protocols, routines, and tools for building software and applications, specifying how different software components should interact with each other.  Service-Oriented Architecture (SOA): A design pattern that organizes software components into services that can be accessed by other components through well- defined interfaces.  Key Terminologies in SIA  Microservices Architecture: A variant of SOA that emphasizes building small, independent services that can be deployed and scaled independently.  Enterprise Service Bus (ESB): A middleware infrastructure that enables communication and integration between disparate software applications and services.  Key Terminologies in SIA  Message-Oriented Middleware (MOM): A type of middleware that supports the exchange of messages between different software components, providing reliable and asynchronous communication.  Enterprise Application Integration (EAI): The process of integrating multiple applications and systems within an organization to achieve seamless data exchange and workflow automation.  Key Terminologies in SIA  Business Process Management (BPM): The practice of analyzing and improving business processes to increase efficiency, productivity, and agility.  Cloud Computing: A model for delivering computing resources (e.g., servers, storage, databases, software, and analytics) over the internet on a pay-as-you-go basis.  Understanding Organizations  Basic Organizational Structures - Organizational structure refers to the way that an organization arranges its lines of authority, communications, and tasks in order to achieve its objectives. There are several types of organizational structures that organizations can adopt depending on their needs, size, and goals.  Functional Structure  The functional structure is the most common type of organizational structure. It is a hierarchical arrangement of employees by functional areas such as accounting, marketing, engineering, etc. Each functional area is led by a manager who reports to a higher-level manager. Communication flows vertically and horizontally within the functional area. This structure is best suited for large organizations with clearly defined tasks and responsibilities. Functional Structure  Divisional Structure  The divisional structure is an organizational structure in which the company is divided into smaller, self-contained units or divisions. Each division has its own functional areas and a divisional manager who is responsible for all aspects of the division. Communication flows both horizontally within the division and vertically to the corporate level. This structure is best suited for large, geographically dispersed companies. Divisional Structure  Matrix Structure  The matrix structure is a hybrid organizational structure that combines the functional and divisional structures. In this structure, employees are organized into teams or projects that are cross-functional and cross-divisional. Each team is led by a project manager who reports to a functional manager and a divisional manager. Communication flows both vertically and horizontally within the team. This structure is best suited for complex projects and organizations that require a high level of collaboration and coordination. Matrix Structure  Project Organization Structure  In a project-organizational structure, the teams are put together based on the number of members needed to produce the product or complete the project. The number of significantly different kinds of tasks are taken into account when structuring a project in this manner, assuring that the right members are chosen to participate in the project. Project Organization Structure  Understanding Organizations  We can analyze a formal organization using the following 4 (four) frames; Structural frame: Human resources frame: Focuses on roles and responsibilities, Focuses on providing harmony coordination and control. Organizational between needs of the organization and charts help define this frame. needs of people. Political frame: Symbolic frame: Assumes organizations are coalitions Focuses on symbols and meanings composed of varied individuals and interest related to events. Culture is important. groups. Conflict and power are key issues.  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 Projects Originate (Sources of Projects)?  Projects come from problems, opportunities, and directives and are always subject to one or more constraints.  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).  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.  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.  Project Basics  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  Project 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  Project Phases and the Project Life Cycle  A project life cycle is a collection of project phases  Project phases vary by project or industry, but some general phases include  concept  development  implementation  support  Phases of the Project Life Cycle  Example of Project Life Cycle  1. Project Initiation: This is the first phase of the project life cycle. During this phase, the project is defined and authorized. The goals and objectives of the project are established, and a feasibility study is conducted to determine whether the project is viable or not. The project manager is appointed, and the project team is assembled. This phase is critical because it sets the foundation for the entire project.  Example of Project Life Cycle  2. Project Planning: This is the second phase of the project life cycle. During this phase, a detailed project plan is created. The project plan outlines the scope of the project, the timeline, the budget, and the resources required. The project plan is the roadmap for the project and helps the project manager and the team to stay on track.  Example of Project Life Cycle  3. Project Execution: This is the third phase of the project life cycle. During this phase, the actual work of the project is performed. The project team implements the plan that was created in the previous phase. This phase is where the bulk of the work is done, and it's important to closely monitor progress to ensure that the project stays on track.  Example of Project Life Cycle  4. Project Monitoring and Control: This is the fourth phase of the project life cycle. During this phase, the project is monitored to ensure that it's progressing according to plan. The project manager and the team track the project's progress, identify any deviations from the plan, and take corrective action to get the project back on track.  Example of Project Life Cycle  5. Project Closure: This is the fifth and final phase of the project life cycle. During this phase, the project is closed out. The project manager and the team conduct a post-project review to evaluate the success of the project. Lessons learned are documented, and the project is officially closed out.  Product and the Product Life Cycle  Products also have life cycles  The Systems Development Life Cycle (SDLC) is a framework for describing the phases involved in developing and maintaining information systems  Systems development projects can follow  Predictive models: The scope of the project can be clearly articulated and the schedule and cost can be predicted.  Adaptive models: Projects are mission driven and component based, using time-based cycles to meet target dates.  Predictive Life Cycle Models  The waterfall model has well-defined, linear stages of systems development and support.  The spiral model shows that software is developed using an iterative or spiral approach rather than a linear approach.  The incremental release model provides for progressive development of operational software.  The prototyping model is used for developing prototypes to clarify user requirements.  The RAD model is used to produce systems quickly without sacrificing quality.  Adaptive Life Cycle Models  Extreme Programming (XP): Developers program in pairs and must write the tests for their own code. XP teams include developers, managers, and users.  Scrum: Repetitions of iterative development are referred to as sprints, which normally last thirty days. Teams often meet every day for a short meeting, called a scrum, to decide what to accomplish that day. Works best for object-oriented technology projects and requires strong leadership to coordinate the work  Reporting #2  Volunteers to report on the different SDLC Models: Waterfall – R4 () R9 () Spiral – R4 () R9 () Incremental release – R4 () R9 () Prototyping – R4 () R9 () RAD – R4 () R9 () XP – R4 () R9 () | Scrum – R4 () R9 ()  Distinguishing Project Life Cycles and Product Life Cycles  The project life cycle applies to all projects, regardless of the products being produced  Product life cycle models vary considerably based on the nature of the product  Most large IT systems are developed as a series of projects  Project management is done in all of the product life cycle phases  Why are there Project Phases and Management Reviews?  A project should successfully pass through each of the project phases in order to continue on to the next  Management reviews (also called phase exits or kill points) should occur after each phase to evaluate the project’s progress, likely success, and continued compatibility with organizational goals SDLC QUESTION & ANSWER