Download System Architecture and Integration and more Study notes Computer System Design and Architecture in PDF only on Docsity!
System, Integration, and Architecture
- System
- Integration
- System Integration
- Architecture
- System Architecture
- Computer System
- Information System
- Database System System, Integration, and Architecture Lesson 1 Summary: A system is defined as interconnected parts working together, while integration is the process of uniting elements into a functioning whole. Systems integration refers to building complex information systems that combine hardware, software, and communication networks. Architecture is described as a carefully designed structure, and system architecture specifically outlines the structure, behavior, and components of a system. It also distinguishes between computer systems, information systems, and database systems, showing their differences in scope and purpose, and emphasizes the importance of systems integration architecture in ensuring efficiency and cohesion across organizational technologies. Notes: Summary is AI - generated.
1.0 | System
Defining System ➢ a set of things working together as parts of a mechanism or an interconnecting network; ➢ a set of principles or procedures according to which something is done; an organized framework or method
2.0 | Integration
Defining Integration ➢ to form, coordinate, or blend into a functioning or unified whole ➢ To incorporate into a larger unit ➢ To unite with something else
3.0 | Systems Integration
Defining System Integration ➢ Process of creating complex information system that may include designing or building a customized architecture or application, integrating it with new or existing hardware, packaged and custom software, and communications. Information Technology | IT224 System Integration and Architecture Monica Empleo
Types of System Integration ➢ 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.
4.0 | Architecture
Defining Architecture ➢ The complex or carefully designed structure of something ➢ Blueprint ➢ Guidelines in designing a system where it describes or illustrates its relationships and interactions
5.0 | System Architecture
Defining System Architecture ➢ Conceptual model that defines the structure or behavior, and views of a system. ➢ Consist of system components and the sub-systems developed, that will work together to implement the overall system. Importance of System Integration and Architecture ● They help ensure that systems are reliable, scalable, and maintainable. ● Without proper integration, systems can suffer from compatibility Information Technology | IT224 System Integration and Architecture Monica Empleo
Service-Oriented (SOA) ➢ A design pattern that organizes software components into services that can be accessed by other components through well-defined interfaces. Micorservices 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. 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. Business Process Management (BPM) ➢ Analyzing and improving business processes to increase efficiency, productivity, and agility. Cloud Computing ➢ Model for deliviering computing resources 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 ➢ Common type of organizational structure. ➢ 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. Information Technology | IT224 System Integration and Architecture Monica Empleo
Divisional Structure ➢ company is divided into smaller, self-contained units or divisions ➢ 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. Matrix Structure ➢ Hybrid organizational structure, combines the functional and divisional structures. ➢ employees are organized into teams or projects that are cross-functional and cross-divisional ➢ 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 Project Organization 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. Information Technology | IT224 System Integration and Architecture Monica Empleo
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
- Project Initiation
- First phase of the project life cycle
- Defined and authorized
- Goals and objectives of the project are established
- Feasibility study is conducted to determine the viability
- Project manager is appointed, and the project team is assembled
- Phase is critical because it sets the foundation for the entire project
- Project Planning
- Second phase
- Detailed project plan is created
- Outlines the scope of the project, the timeline, the budget, and the resources required
- Project plan is the roadmap for the project and helps the project manager and the team to stay on the track
- Project Execution
- Third phase of the project life cycle
- The actual work of the project is performed
- Implements the plan that was created in the previous phase
- Where the bulk of the work is done, monitor progress to ensure that the project stays on track
- Project Monitoring and Control
- Fourth phase of the project life cycle
- monitored to ensure that it's progressing according to plan
- 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 Information Technology | IT224 System Integration and Architecture Monica Empleo
- Project Closure
- Fifth and final phase of the project life cycle
- Project is closed out
- Conduct a post-project review to evaluate the success of the project
- Lesson 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 Cycles Models ➢ Waterfall Model ○ linear stages of systems development and support. ➢ Spiral Model ○ shows that software is developed using an iterative or spiral approach rather than a linear approach. ➢ Incremental Release Model ○ provides for progressive development of operational software. ➢ Prototyping Model ○ used for developing prototypes to clarify user requirements. ➢ RAD model ○ 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 Project vs Product Life Cycles Project Life Cycle Product Life Cycle 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 Information Technology | IT224 System Integration and Architecture Monica Empleo
○ who are the people that run the business ○ what are the business units and their hierarchy? ➢ When (time) ○ when are the business processes performed, i.e., what are the business schedules and workflows? ➢ Why (motivation) ○ why is the solution the one chosen? ○ How was that derived from? ○ What motivates the performance of certain activities? Rows of Zachman Framework ➢ Planner's View (Scope Contexts) ○ business purpose and strategy, which defines the playing field for the other views. ➢ Owner's View (Business Concepts) ○ description of the organization within which the information system must function. ➢ Designer's View (System Logic) ○ how the system will satisfy the organization's information needs. ➢ Implementer's View (Technology Physics) ○ how the system will be implemented. ○ solutions and technologies apparent and addresses production constraints. ➢ Sub-Constructor's View (Component Assembles ) ○ implementation-specific details of certain system elements: ■ parts that need further clarification before production can begin. ○ ess architecturally significant than the others because it is more concerned with a part of the system than with the whole. ➢ User's View (Operations Classes) ○ functioning system in its operational environment.
Key Benefits of the Zachman Framework
➢ Alignment of Business and IT ○ Ensures that IT systems directly support organizational strategy and objectives. ➢ Improved Communication ○ Provides a common language and structure for stakeholders across business and technical domains. ➢ Reduced Complexity ○ Breaks down large, complex enterprises into manageable perspectives and layers. ➢ Comprehensive View ○ Offers a holistic blueprint of the enterprise, covering “what, how, when, who, where, and why.” ➢ Flexibility ○ Serves as an ontology (classification system) rather than a rigid methodology, allowing organizations to adapt it to their needs.
Importance in Enterprise Architecture
➢ Strategic Planning ○ Helps organizations understand what needs to be done and why, rather than prescribing how to do it. ➢ Decision-Making ○ Provides clarity on dependencies and interactions, Information Technology | IT224 System Integration and Architecture Monica Empleo
simplifying complex IT and business decisions. ➢ Consistency Across Systems ○ Ensures that different subsystems and processes work cohesively, avoiding duplication or misalignment. ➢ Long-Term Sustainability ○ Supports scalability and adaptability as enterprises grow and evolve. Information Technology | IT224 System Integration and Architecture Monica Empleo
➢ This domain maps out the specific software programs (the "Apps") that the business uses to interact with the data and the users. Technology Architecture ➢ It describes the hardware, networks, and cloud infrastructure required to keep the applications running.
Importance of Enterprise Architecture
➢ Unification ○ It coordinates different departmental processes so everyone moves in the same direction. ➢ Gap Analysis ○ It helps leaders identify where the company is lacking resources or where systems are redundant. ➢ Risk Management ○ It highlights ways to reduce security risks by improving how information is managed. ➢ Cost Reduction ○ By documenting relationships between assets, EA identifies which technologies add value and which are just wasting money. Information Technology | IT224 System Integration and Architecture Monica Empleo
TOGAF: The Open Group Architecture
Framework
- Overview of TOGAF
- TOGAF Components ○ ADM ○ ADM Phases
- Enterprise Continuum TOGAF Lesson 4 Summary: TOGAF (The Open Group Architecture Framework) is a widely used enterprise architecture methodology that provides a structured approach for aligning business goals with IT systems. It helps organizations design, plan, implement, and govern enterprise information architecture while reducing errors, staying on budget, and maintaining timelines. TOGAF’s importance lies in its ability to standardize processes, improve communication among stakeholders, and ensure IT systems effectively support business strategies. Notes: Summary is AI - generated.
Overview of TOGAF
➢ Managed by The Open Group Architecture Forum, which oversees the framework, tools, and certification processes. ➢ Freely available for internal use by organizations, promoting widespread adoption and implementation ➢ Help organizations design, plan, implement, and govern enterprise architecture effectively. ➢ TOGAF provides a practical, experience-based approach to enterprise architecture, integrating various deliverables and reference models.
TOGAF Components
Architecture Development Method (ADM) ➢ It is iterative, allowing for continuous improvement and adaptation throughout the architecture development process. ➢ Organizations may need to adapt ADM based on their specific circumstances or to integrate it with other frameworks. Scoping in ADM ➢ Scoping is essential for every architectural activity due to constraints in time, resources, and finances. ➢ It involves defining horizontal (enterprise-wide) and vertical (level of detail) scopes to ensure focused and effective architecture development. ➢ Decisions made during scoping must create value for the enterprise, aligning with business goals and objectives. Phases of ADM ● PHASE A: Architecture Vision ○ Validates business goals, defines scope, identifies stakeholders, and secures approval. Information Technology | IT224 System Integration and Architecture Monica Empleo
DODAF: Department of Defense
Architecture
- DODAF: Department of Defense Architecture Framework ○ Model (DoDAF-described Model)
- Processes of DoDAF
- DoDAF Structure/Viewpoint DODAF Lesson 4 Summary: DoDAF (Department of Defense Architecture Framework) is a structured approach for analyzing and designing complex organizations and systems. It organizes perspectives into viewpoints such as capability, operational, services, and systems to ensure clarity across goals, processes, support functions, and technologies. By aligning these viewpoints, DoDAF helps stakeholders understand how organizational needs translate into operations, supported by services and enabled through technology. Notes: Summary is AI - generated.
DODAF: Department of Defense
Architecture Framework
➢ This was created and is maintained by the United States Department of Defense (DoD) ➢ The name reflects its origin and primary intended user: the US military and defense community ➢ Designated Enterprise Architecture framework; structured, standardized approach for organizing, visualizing and designing complex systems. ➢ Analyze interoperability, manage system complexity, and align technology solutions with strategic missions across various defense organizations. History ● 1996: DoDAF began with C4ISR Architecture Framework v1. ● Developed by the U.S. Department of Defense for military system planning & integration ● C4ISR = Command, Control, Communications, Computers, Intelligence, Surveillance, Reconnaissance Model (DoDAF-described Model) ➢ A template or structure used to organize and display architecture data. ➢ Easily understood format ➢ Can be documents, spreadsheets, dashboards, or other graphical representation
Processes of DoDAF
➢ Define Objectives and Scope ➢ Identify Stakeholders ➢ Define Capabilities and Operations ➢ Model Systems ➢ Define Data and Standards ➢ Validate and Maintain Architecture Information Technology | IT224 System Integration and Architecture Monica Empleo
DoDAF Structure/Viewpoint
1. Capability Viewpoint ➢ What does the organization need to be able to do? ➢ This focuses on what the organization needs to accomplish. 2. Operational Viewpoint ➢ How the work is actually done. ➢ The steps or activities needed to achieve the goal. 3. Services Viewpoint ➢ Services that support operations. ➢ Example: GCR for submissions, Messenger for group communication, Canva for presentation. ➢ Basically the services that help you complete the task. 4. Systems Viewpoint ➢ This focuses on the technology itself. Actual systems or devices involved. ➢ Example: Lappy or cp, school website or learning management system. 5. Project Viewpoint ➢ Shows how projects and programs deliver capabilities, which organizations are involved and how they depend on each other. 6. Standard Viewpoint ➢ Defines the rules and guidelines that systems must follow meet operational or capability requirements. 7. Data and Information Viewpoint ➢ Shows what data is needed, how it is structured, and how it flows between systems. 8. All Viewpoint ➢ Provides an overall description of the architecture, including its scope, context, assumptions, rules, and constraints. Information Technology | IT224 System Integration and Architecture Monica Empleo
○ Continuous evolution → GraphQL, Apache Kafka ➢ 2023 ○ Trends → mesh architectures Birth of Microservices (2011) ➢ Microservices, gained prominence when Martin Fowler (tahimik lang sa umpisa) and his colleagues at thoughtworks discussed the concept as a way to build robust and scalable systems.
Dive Deep to Microservices
➢ Client Layer ○ = Customers sending requests (login, search, watch video) ➢ CDN (Content Delivery Network) ○ = Local food pickup shelves → group services by business function ➢ Load Balancer ○ = Host assigning tables → distributes traffic across servers ➢ API Gateway ○ = Receptionist → single entry point, routes requests, handles auth, logging, rate limiting ➢ Identity Provider ○ = Security guard → login, token generation, authentication, authorization ➢ Service Registry & Discovery ○ = Internal directory → tracks services, domains = kitchens for different foods ➢ REST APIs ○ = Standard order format → services communicate via HTTP/JSON; separate databases = ingredient storage ➢ Management & Monitoring ○ = Restaurant manager → health checks, logging, metrics, deployment management
Components of Microservices
1. Componentization via Services ○ System broken into many small, replaceable services ○ Each service does a specific job and works independently 2. Organized Around Business Capabilities ○ Services grouped by what they do for the business ○ Not grouped by technology layers (UI, DB, etc.) 3. Products, Not Projects ○ Teams own services permanently ○ They develop, monitor, update, and maintain → service treated as a product 4. Smart Endpoints, Dumb Pipes Information Technology | IT224 System Integration and Architecture Monica Empleo
○ Services contain main logic (smart) ○ Communication kept simple (dumb) → lightweight APIs or messaging, no complex middle layers
5. Decentralized Governance ○ Teams choose their own tools & technologies ○ No enforced central standard → flexibility & autonomy 6. Decentralized Data Management ○ Each service keeps its own data/store ○ No shared central database ○ Increases independence & scalability
Benefits of Microservices
➢ Agile ○ Faster releases in smaller scopes ➢ Simple ○ Reduced tangled dependencies and make feature less risky. ➢ Autonomous ○ Small, focused teams choose their own languages, frameworks, databases ➢ Responsive ○ Precise scaling reduces waste, improves cost & performance ➢ Safe & Manageable ○ Loose coupling with resilience patterns (circuit breakers, retries, timeouts) ○ Performance monitored, risks minimized ➢ Adaptable ○ Reduce operational overhead for diverse stacks and pay-per-use.
Downside of Microservices
➢ Complex ○ Many services can lead to many deployments, becoming harder and more voluminous ➢ Populated ○ Requiring strong governance and coordination to avoid fragmentation and technical debt ➢ Incompatibility ○ Independent releases can introduce runtime incompatibilities and may cause breaking consumers ➢ Latency ○ Chatty and long dependency chains adds latency ➢ Dependent ○ Requires mature DevOps practices to handle complexity ○ Without these, distributed complexity can overwhelm teams ➢ Crowded ○ Services depend on many others due to over-splitting into excessively small services ➢ Inconsistency ○ Decentralized data ownership, each service keeps its own store ○ Traditional ACID transactions (Atomicity, Consistency, Isolation, Durability) are harder to enforce across services Information Technology | IT224 System Integration and Architecture Monica Empleo
