IPT101

INTERSYSTEM COMMUNICATION

- In ordinary uniprocessor system there is one processor and one memory unit.

- The operation of this computer is sequential.

- The performance of single processor system is limited by the underlying fabrication

technology.

- Intersystem communication is used in distributed computing.

- A distributed system is basically a computer network.

- A distributed system relies entirely on the underlying computer network for the
communication of data and control information between the nodes of which they are
composed.

- A distributed system is a collection of independent computers that appears to its users as

a single coherent system.

MALWARE

ARCHITECTURES FOR INTEGRATING SYSTEM

- The software architectures tell us how the various software components are to be
organized and how they should interact.

- The actual realization of a distributed system requires that we instantiate and place
software components on real machines.

- There are many different choices that can be made in doing so.
DCOM as DS technology Solution

RMI as Distributed technology solution

CORBA as Distributed technology solution

- is a software standard that is defined and maintained by the Object Management Group
(OMG).

- is based on the Request-Response architecture.

- It consists of a standard framework for developing and maintaining distributed software

systems.

- is to allow interoperability between objects on distributed systems.

 DATA MAPPING AND EXCHANGE

META DATA- is data that describes other data.

- Structured metadata

- Unstructured metadata

- Semantic metadata

- Provenance metadata

XML - refers to the way in which the characters in an XML document are represented or
encoded.

UTF-8- represents characters using a variable number of bytes

UTF-16- characters using 16 bits per character

ISO-8859-1- encoding scheme used for Western European languages

US-ASCII- a 7-bit encoding scheme used for representing basic English characters

DTD - stands for Document Type Definition

- UTF-8,UTF-16 ,ISO-8859-1 ,US-ASCII

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE catalog SYSTEM "catalog.dtd">

<catalog>

<!-- catalog content goes here -->

</catalog>

XML Schema - more powerful and flexible

- Document Type Definitions (DTD)

- XML Schema Definitions (XSD)

Parsing XML- extracting data from an XML file

Tools For Parsing XML Documents

- XSL

- XSLT

- XPath

XSL (Extensible Stylesheet Language)

XSLT (Extensible Stylesheet Language Transformations)

XPath

XML Parser- a program that reads an XML document and extracts information from it

- SAX (Simple API for XML)

- DOM (Document Object Model)

- StAX (Streaming API for XML)

 INTEGRATIVE CODING

DESIGN PATTERNS

ADAPTER PATTERN- An Adapter Pattern says that just "converts the interface of a
class into another interface that a client wants". In other words, to provide the interface
according to client requirement while using the services of a class with a different
interface. The Adapter Pattern is also known as Wrapper.

FACADE PATTERN- The facade pattern (also spelled façade) is a software-design

pattern commonly used in object-oriented programming. Analogous to a facade in
architecture, a facade is an object that serves as a front-facing interface masking more
complex underlying or structural code.

MEDIATOR PATTERN- In software engineering, the mediator pattern defines an object

that encapsulates how a set of objects interact. This pattern is considered to be a behavioral
pattern due to the way it can alter the program's running behavior. In object-oriented
programming, programs often consist of many classes.
OBSERVER PATTERN- In software design and engineering, the observer pattern is a
software design pattern in which an object, named the subject, maintains a list of its
dependents, called observers, and notifies them automatically of any state changes, usually
by calling one of their methods.

MS102
POPULATION AND SAMPLE

SAMPLE

- DEFINITION

- MEANING

- CHARACTERISTIC OF AN IDEAL / GOOD SAMPLE

- IMPORTANCE OF SAMPLE

- MEANING OF SAMPLING

- SAMPLING METHOD

- PROBABILITY / NON-PROBABILITY SAMPLING

DEFINITIONS OF SAMPLE

- Sample is a reprehensive part of a population of research.

- Any sub set of population, which represents all the types of elements of population.

MEANING OF SAMPLE

- A part of population that represents it completely is known as sample. It means, the units,
selected from the population as a sample, must represent all kind of characteristics of
different types of units of population.

CHARACTERISTICS OF AN IDEAL/GOOD SAMPLE

- Number of units in sample must be proportionate.

- Units selected in sample must represent all the characteristics of different units of
population.

- Units of sample must be selected fairly without any bias.

- Collection of data from units of sample should be convenient for researcher.

IMPORTANCE OF SAMPLE

- Research process becomes faster and less expensive

- Data can be collected easily for research.

- Data analysis and interpretation can be done precisely.

- Sample is essential in experimental research because it is a complex process and data

collection process in such research consumes more time.

MEANING OF SAMPLING

- The process of selecting sample from population is called sampling. A method used to
select a sample is called sampling method.

TYPES OF SAMPLING METHOD

PROBABILITY- A sampling method, in which subjects are selected without any bias or
prejudice and in which all the units of population have equal or predetermined and certain
probability to be selected in a sample, is known as probability sampling method.

NON-PROBABILITY- This method of sample selection does not have any scientific
base, so it increases the chances of selecting biased sample.

COLLECTION TECHNIQUES
DATA COLLECTION METHOD

- INTERVIEW METHOD

- QUESTIONNAIRE METHOD

- OBSERVATION METHODS

- TEST METHODS

- REGISTRATION METHOD

INTERVIEW METHOD- this is a method of collecting data where a researcher conducts

face-to-face or phone conversations with individuals to gather information.

STRUCTURED INTERVIEWS- Follow a fixed set of questions, and the order of the
questions is pre-determined.

SEMI - STRUCTURED- Have a core set of questions that the researcher follows

UNSTRUCTURED INTERVIEWS- Do not have a set list of questions.

QUESTIONNAIRE METHOD- in this method, a researcher designs a set of questions

and distributes them to participants to fill out.

- questionnaires can be administered in person, by mail, or online.

OBSERVATION METHODS- this involves the researcher observing and recording the
behavior of individuals or groups.

PARTICIPANT OBSERVATION- The researcher becomes a member of the group

being observed and participates in their activities.

NON-PARTICIPANT OBSERVATION- The researcher observes the group without

becoming a member.

STRUCTURED OBSERVATION- The researcher observes specific behaviors.

UNSTRUCTURED OBSERVATION- the researcher observes the behavior without.

TEST METHODS- this method involves testing participants to measure their knowledge,
skills, or abilities. examples include tests, aptitude tests, and personality tests.

ACHIEVEMENT TESTS- The researcher becomes a member of the group being

observed and participates in their activities.

APTITUDE TESTS- Measure a person's ability to learn or perform a particular task, such
as problem-solving or critical thinking.

PERSONALITY TESTS- Measure a person's personality traits, such as introversion,

extroversion, or openness to experience.

COGNITIVE TESTS- Measure a person's cognitive abilities, such as memory, attention,

or processing speed.
REGISTRATION METHOD- this involves collecting data from existing records, such
as medical records or government records.

- registration data can be collected from a variety of sources, such as government agencies,
hospitals, schools, or financial institutions.

OTHER METHODS:

- CASE STUDY

- FOCOUS GROUPS

- DIARIES AND LOGS

- INTERNET SURVEYS

- SOCIAL MEDIA ANALYSIS

- EXPERIMENTAL METHOD

SAMPLING TECHNIQUES

SAMPLING ERROR- can occur in any sampling technique and can lead to biased or
inaccurate results.

- the larger the sample size, the smaller the sampling error is likely to be.

RANDOM SAMPLING- is a method of selecting a sample from a population in which

each member of the population has an equal chance of being selected.

- in random sampling, every individual or unit in the population has an equal opportunity
of being selected, without any bias or preference.

STRATIFIED RANDOM SAMPLING- a sampling method that involves dividing a

population into subgroups or strata, and then selecting a random sample from each
subgroup or stratum.

- stratification is useful when the population is heterogeneous.

CLUSTER SAMPLING- sampling method that involves dividing a population into

clusters.

- in cluster sampling, the population is first divided into clusters.

QUOTA SAMPLING- is a non-probability sampling method that involves selecting a

sample based on specific quotas.

- targets for certain characteristics or traits, such as age, gender, or occupation.

CONVENIENCE SAMPLING- is a non-probability sampling method that involves

selecting individuals or units for a sample based on their easy availability or accessibility.

- the goal of convenience sampling is to select individuals who are convenient to access.
OTHER SAMPLING TECHNIQUES:

- SNOWBALL SAMPLING

- MULTI -STAGE SAMPLING

- OVERSAMPLING

- UNDERSAMPLING

- RANDOM WALK SAMPLING

- VOLUNTARY SAMPLING

SIA101
MANAGEMENT PLAN

DEFINE THE SCOPE- The first step is to define the scope of the management plan. This
includes identifying the stakeholders, the IT assets and resources, and the business
processes that will be covered.

ESTABLISH THE GOVERNANCE FRAMEWORK- The governance framework

establishes the policies, procedures, and guidelines for managing the organization's IT
resources. This includes defining roles and responsibilities, decision-making processes,
and communication channels.

IDENTIFY THE IT ARCHITECTURE- The IT architecture includes the hardware,

software, and network infrastructure that supports the organization's business processes.
This should be documented in detail, including how the IT architecture supports the
organization's goals and objectives.

DEFINE THE IT MANAGEMENT PROCESSES- The IT management processes

include service management, change management, incident management, and problem
management. These processes should be documented and aligned with the IT architecture
and the organization's goals and objectives.

DEVELOP PERFORMANCE METRICS- Performance metrics are used to measure the

effectiveness and efficiency of the IT management processes. These metrics should be
defined and tracked to ensure continuous improvement.

DEFINE RISK MANAGEMENT STRATEGIES- Risk management strategies are used

to identify and mitigate risks to the organization's IT resources. This includes identifying
potential risks, assessing the likelihood and impact of those risks, and developing
strategies to mitigate them.

ESTABLISH COMMUNICATION AND TRAINING PLANS- Communication and

training plans are essential to ensure that all stakeholders are aware of the management
plan and their roles and responsibilities. This includes developing communication plans
for stakeholders, as well as training plans for employees.

CONTINUOUSLY REVIEW AND IMPROVE THE MANAGEMENT PLAN- The

management plan should be continuously reviewed and improved to ensure that it remains
aligned with the organization's goals and objectives and is effective in managing the
organization's IT resources.

ENTERPRISE ARCHITECTURE

BUSINESS ARCHITECTURE- This component provides a high-level view of an

organization's business strategy, goals, and objectives, as well as the business processes,
capabilities, and resources required to achieve them.

Key Components of Business Architecture

BUSINESS GOALS AND OBJECTIVES- These are the high-level targets that the
organization aims to achieve.

BUSINESS PROCESSES- These are the activities that the organization performs to
achieve its goals and objectives.

BUSINESS CAPABILITIES- These are the abilities and resources that the organization
possesses to perform its business processes

BUSINESS INFORMATION- This is the data that the organization collects, stores,
processes, and analyzes.
BUSINESS ORGANIZATION- This is the structure of the organization, including its
hierarchy, roles, and responsibilities.

APPLICATION ARCHITECTURE- This component focuses on the design,

development, deployment, and management of the organization's software applications,
including custom-built and commercial off-the shelf applications.

Key Components of Application Architecture

APPLICATION COMPONENTS- These are the building blocks of an application,

including its user interfaces.

APPLICATION INTEGRATION- This is the ability of an application to communicate.

DATA MANAGEMENT- This refers to the way that an application stores, processes, and
manages data.

SECURITY- This refers to the security measures that are implemented within an
application.

PERFORMANCE AND SCALABILITY- This refers to the ability of an application to

perform well.

DATA ARCHITECTURE- This component defines the organization's data strategy,

including the types of data that are collected, stored, processed, and analyzed, as well as
the data models, data governance, and data management practices.

Key Components of Data Architecture

DATA COMPONENTS- These include the data entities and attributes that are used in the
organization's systems.

DATA STORAGE- This refers to the physical storage of data.

DATA INTEGRATION- This refers to the ability to integrate data from different
sources.

DATA GOVERNANCE- This refers to the policies, procedures, and standards that are
used to manage and protect data.

DATA ANALYTICS- This refers to the use of data to gain insights and make informed
business decisions.

TECHNOLOGY ARCHITECTURE- This component provides a high-level view of the

organization's IT infrastructure, including hardware, software, networks, and other
technology components that support the delivery of IT services.

Key Components of Technology Architecture

INFRASTRUCTURE COMPONENTS- These include the hardware, software, and

network components.
SYSTEM INTEGRATION- This refers to the ability of different technology systems to
communicate and exchange data with each other.

SECURITY- This refers to the measures and processes that are implemented to protect
technology assets.

PERFORMANCE AND SCALABILITY- This refers to the ability of the technology

infrastructure to perform well and handle increased load.

IT GOVERNANCE- This refers to the policies, procedures, and standards.

SECURITY ARCHITECTURE- This component focuses on identifying and mitigating

risks to the organization's information assets, including data, applications, and IT
infrastructure.

Key Components of Security Architecture

SECURITY COMPONENTS- These include the technical and non-technical controls.

RISK MANAGEMENT- This refers to the process of identifying, assessing, and

prioritizing security risks.

SECURITY GOVERNANCE- This refers to the policies, procedures, and standards.

INCIDENT MANAGEMENT- This refers to the process of detecting and responding to

security incident.

COMPLIANCE- This refers to the measures and processes that are implemented.

GOVERNANCE AND STANDARDS- This component establishes the principles,

guidelines, and standards for enterprise architecture development and management, as well
as the governance framework to ensure compliance with these standards and the alignment
of enterprise architecture with the organization's goals and objectives.

Key Components of Governance and Standards

ARCHITECTURE GOVERNANCE- The policies and procedures used to manage the

design, development, and deployment of architecture components.

STANDARDS AND GUIDELINES- The rules and guidelines that are used to guide the
development and use of architecture components.

COMPLIANCE- The measures and processes that are implemented.

CHANGE MANAGEMENT- The processes and procedures used to manage changes to

architecture components.

PERFORMANCE MANAGEMENT- The processes and procedures used to measure

and manage the performance of architecture components.
IMPLEMENTATION METHODOLOGY- A structured approach or framework for
planning, designing, developing, testing, deploying, and maintaining a system or solution.

DIFFERENT IMPLEMENTATION METHODOLOGY

1. WATERFALL- This is a linear, sequential approach that moves through phases in a

specific order.

2. AGILE- An iterative, incremental approach that focuses on delivering working

software in short cycles.

3. DEVOPS- a combination of development and operations methodologies that

emphasizes close collaboration between development and operations teams

4. LEAN- a methodology that aims to reduce waste and increase value in the software
development process.

5. HYBRID- A custom approach that combines elements of multiple methodologies to

create a tailored solution that fits the specific needs of the project.

ENTERPRISE ARCHITECTURE FRAMEWORKS- Standardized approaches that

provide a comprehensive view of an organization's information technology landscape,
business processes, and capabilities.

ENTERPRISE ARCHITECTURE FRAMEWORKS

1. THE OPEN GROUP ARCHITECTURE FRAMEWORK (TOGAF)- one of the

most widely used enterprise architecture frameworks.

2. ZACHMAN FRAMEWORK- MATRIX-based approach that provides a structure for

organizing

and classifying architecture artifacts across six perspectives.

3. FEDERAL ENTERPRISE ARCHITECTURE FRAMEWORK (FEAF)- a

framework developed by the U.S. government that provides a common language and
methodology for describing and managing enterprise architecture.

4. BUSINESS ARCHITECTURE FRAMEWORK (BAF) - A framework that focuses

specifically on the business architecture domain.

5. THE GARTNER ENTERPRISE ARCHITECTURE FRAMEWORK- This

framework is a methodology for enterprise architecture development that emphasizes
business outcomes and focuses on aligning IT with business goals.
 DEVELOPING AN ENTERPRISE ARCHITECTURE

Developing An Enterprise Architecture is a complex process that involves creating a

blueprint for how an organization's technology, processes, and people will work together
to achieve its goals. Here are some general steps to consider when developing an
enterprise architecture:

1. UNDERSTAND THE BUSINESS STRATEGY: Start by understanding the

organization's business strategy and goals. This will help you identify the key capabilities
required to achieve those goals.
2. ASSESS THE CURRENT STATE: Conduct an inventory of the organization's
existing technology, processes, and people. This will help you identify areas of strength
and weakness.

3. DEFINE THE TARGET STATE: Develop a vision for the organization's future state,
including the technology, processes, and people required to achieve the business goals.

4. IDENTIFY THE GAPS: Compare the current state to the target state and identify the
gaps that need to be addressed to achieve the target state.

5. DEVELOP A ROADMAP: Create a roadmap that outlines the steps required to close
the gaps and achieve the target state. This should include a timeline and milestones.

6. DEFINE THE ARCHITECTURE PRINCIPLES: Establish the guiding principles

that will govern the design and implementation of the enterprise architecture.

7. DEVELOP THE ARCHITECTURE: Develop the enterprise architecture, including

the technology, processes, and people components.

8. COMMUNICATE AND GET BUY-IN: Communicate the enterprise architecture to

stakeholders and get buy-in from key decision-makers.

9. IMPLEMENT AND MONITOR: Implement the enterprise architecture and monitor

its performance, making adjustments as necessary. It's important to note that enterprise
architecture is an ongoing process and not a one-time event. As the organization's goals
and strategies evolve, the enterprise architecture must be reviewed and adjusted to ensure
it continues to support the business.

Developing an Enterprise Architecture involves creating a blueprint of an

organization's current and future technology landscape, business processes, data, and
applications. This helps align the technology with business goals and enables the
organization to make informed decisions.

CURRENT ARCHITECTURAL VIEWS:

1. BUSINESS ARCHITECTURE: This view provides a high-level understanding of the

organization's business processes, stakeholders, goals, and strategies.

2. APPLICATION ARCHITECTURE: This view describes the applications, systems,

and technologies used in the organization.

3. INFORMATION ARCHITECTURE: This view shows how data is structured, stored,

accessed, and managed across the organization.

4. TECHNOLOGY ARCHITECTURE: This view depicts the technology infrastructure,

hardware, software, and networking components.

FUTURE ARCHITECTURAL VIEWS:

1. EMERGING TECHNOLOGY: This view provides insight into the latest technologies
and trends that can impact the organization's future architecture.

2. BUSINESS STRATEGY: This view aligns the business strategy with the future
technology landscape, ensuring that the technology roadmap supports the organization's
long-term goals.

3. INTEGRATION ARCHITECTURE: This view outlines how the organization's

disparate systems and technologies can be integrated to support the business needs
effectively.

MANAGEMENT PLAN:

DEVELOPING AN ENTERPRISE ARCHITECTURE involves creating a blueprint of

an organization's current and future technology landscape, business processes, data, and
applications. The management plan for developing an Enterprise Architecture should
cover several key areas:

1. GOVERNANCE AND STANDARDS: The management plan should outline how the
Enterprise Architecture will be governed, including the creation and maintenance of
standards, policies, and procedures. This helps ensure consistency, compliance, and
alignment with organizational goals.

2. ROADMAP: The management plan should include a roadmap that outlines the steps
needed to achieve the desired future state of the Enterprise Architecture. This helps ensure
that the Enterprise Architecture initiative is planned, structured, and executed in a way that
aligns with business goals.

3. STAKEHOLDER MANAGEMENT: The plan should identify and manage the

stakeholders involved in the Enterprise Architecture initiative, including executive
sponsors, business leaders, IT leaders, and end-users. This helps ensure that the Enterprise
Architecture initiative is aligned with business needs and goals, and that stakeholders are
kept informed and engaged throughout the process.

4. RISK MANAGEMENT: The plan should outline how risks associated with the
implementation of the Enterprise Architecture will be identified, assessed, and mitigated.
This helps ensure that the Enterprise Architecture initiative is implemented in a way that
minimizes disruption, maximizes benefits, and avoids or mitigates potential risks.

5. RESOURCE MANAGEMENT: The plan should identify the resources required to

implement the Enterprise Architecture, including personnel, budget, and technology
infrastructure. This helps ensure that the Enterprise Architecture initiative is adequately
resourced and that resources are allocated efficiently and effectively.

6. PERFORMANCE MANAGEMENT: The plan should outline how the performance

of the Enterprise Architecture initiative will be measured, monitored, and reported. This
helps ensure that the Enterprise Architecture initiative is achieving its intended outcomes,
and that any issues or concerns can be identified and addressed in a timely manner.
 Overall, the management plan for developing an Enterprise Architecture should
be comprehensive, well- structured, and flexible enough to adapt to changing business
needs and priorities. It should help ensure that the Enterprise Architecture initiative is
aligned with business goals, effectively managed, and successfully implemented.

Overall, developing an Enterprise Architecture requires a comprehensive

understanding of an organization's current and future state, coupled with effective
governance, planning, and management to ensure successful implementation.