SYSTEM INTEGRATION

AND ARCHITECTURE 2
Presentation by John Jaycel Articona
Ajel Rafael Ballarbari
John Marie Nerpio

ITEL - 305 | 2024 Mr. John Randolf Peñaredondo

INTRODUCTION
 INTRODUCTION

A. WHAT ARE THE KEY FEATURES AND FUNCTIONALITIES OF A

SYSTEM DESIGN TOOLS CREATING UML DIAGRAMS, USE CASE
DIAGRAMS, ACTIVITY DIAGRAMS, STATE DIAGRAMS AND
SEQUENCE DIAGRAMS ?
 SYSTEM DESIGN
TOOLS PROVIDE
Diagramming Tools
Modeling Language Support
Collaboration Features
Code Generation
Simulation and Analysis
Integration with Development Environments
Template Libraries
Export/Import Capabilities
Cross-platform Support
Training and Support
Customization Options
 IN CONCLUSION,

In conclusion, utilizing system design tools is essential in any

software development process since they streamline the entire
designing phase ensuring all requirements and specifications are
met appropriately for producing high-quality end products
efficiently.
 WHERE CAN USERS FIND THESE TOOLS OR WEBSITES TO EASILY CREATE
UML DIAGRAMS? PROVIDE RECOMMENDATION FOR REPUTABLE PLATFORMS
OR SOFTWARE.

I highly recommend [Link] as the premier software solution, Secondly, there is Lucidchart, a cloud-based diagramming tool
not only because of its free availability but also due to its that boasts an extensive selection of templates and shapes for
convenient installation process on multiple types of OS system design. It seamlessly integrates with various other
(Windows, mac OS, Linux and mobile platforms). platforms and tools such as Google Drive, Microsoft Teams,
and Jira.
Pros: The storage solution is both freely available and open-
source, offering seamless integration with cloud technology. Pros: Provides an intuitive graphical user interface, cloud-
Additionally, it boasts a diverse selection of shapes and hosted tool with effortless collaboration capabilities,
templates while also providing robust collaboration extensive selection of templates and shapes.
capabilities.
Cons: Certain attributes necessitate a remunerated
Cons: May present a formidable challenge for acquisition, membership and may exhibit tardiness when handling
possibly unsuitable for extensive systems, may not be extensive diagrams.
suitable for large-scale systems.
WHEN IS THE OPTIMAL TIME TO UTILIZE THESE TOOLS IN THE SOFTWARE
DEVELOPMENT LIFE CYCLE, AND HOW DO THEY CONTRIBUTE TO THE
OVERALL DESIGN PROCESS?

Using the design tools in the right time is very complex, For us, you should the system
design tools when the software creation from its initial idea to its finalized deployment
and maintenance.

To Meet Specific Requirements: System design is necessary to ensure that a system meets specific requirements,
such as performance, reliability, scalability, and maintainability. Without a clear design plan, a system may not
function as intended, leading to performance issues, downtime, or other problems.

To Optimize Resources: System design helps to optimize resources, such as time, money, and manpower, by
identifying the most efficient and effective ways to achieve system goals. By carefully planning and organizing system
components, system designers can help reduce waste and improve resource utilization.

To Ensure Interoperability: System design is important in ensuring that different components of a system work
together seamlessly. By defining clear interfaces and protocols, system designers can help ensure that components
can communicate with each other and share data as needed.
WHEN IS THE OPTIMAL TIME TO UTILIZE THESE TOOLS IN THE SOFTWARE
DEVELOPMENT LIFE CYCLE, AND HOW DO THEY CONTRIBUTE TO THE
OVERALL DESIGN PROCESS?

To Reduce Risks: System design helps to reduce risks associated with system failures, security breaches, and other
issues. By identifying potential risks and vulnerabilities, system designers or architects can develop strategies for
mitigating these risks and minimizing the impact of any issues that do occur.

To Facilitate Maintenance and Upgrades: System design can help facilitate maintenance and upgrades over the life of
the system. By designing a system with scalability and flexibility in mind, system architects can make it easier to
upgrade components or add new features as needed.
 IN CONCLUSION,

In conclusion, system design is a crucial step in the development process that plays
a major role in the success of any project. By designing a system properly, you can
ensure that it is scalable, maintainable, and able to meet the needs of its users. A
well-designed system can save time and money in the long run by avoiding costly
rework and making it easier to add new features or make changes.
 HOW DO THESE TOOLS FACILITATE THE CREATION AND
VISUALIZATION OF UML DIAGRAMS, USE CASE DIAGRAMS,
ACTIVITY DIAGRAMS, STATE DIAGRAMS?

It shows the system's components and how they interact with each other. The
components can be physical or logical and often represent boxes or shapes.
Architecture diagrams can be used to communicate a system's design to
stakeholders and help identify potential issues early in the development process. In
addition to helping stakeholders understand a system's design, architecture
diagrams can also be useful for documenting changes and updates over time, as
well as identifying areas where improvements can be made.
 D. UML DIAGRAM SYMBOLS
THERE ARE MANY DIFFERENT TYPES OF UML DIAGRAMS AND EACH
HAS A SLIGHTLY DIFFERENT SYMBOL SET.

2. Action State
1. Starting state
A step in which the users or software performs a
The activity has not yet utilized or changed the
certain task. It represents an action that will take
starting state. Activity Diagrams start from this
place at this stage of the software system. Generally
step. Also known as the entry state. Start Node is
depicted with the rounded-edged rectangle.
the starting point of any activity.
 D. UML DIAGRAM SYMBOLS
THERE ARE MANY DIFFERENT TYPES OF UML DIAGRAMS AND EACH
HAS A SLIGHTLY DIFFERENT SYMBOL SET.

3. Control Flow 4. Decision Node

Connectors between two states or two actions to depict A conditional node or a decisional node is one where
the flow. Shows the sequence of execution. Also known there are multiple options available. Or two or more
as paths. One action state can have multiple control conditions can be considered at the point of the
flows input and also output to another action state. A software system.
single-headed arrow represents the control flow.
 D. UML DIAGRAM SYMBOLS
THERE ARE MANY DIFFERENT TYPES OF UML DIAGRAMS AND EACH
HAS A SLIGHTLY DIFFERENT SYMBOL SET.

5 . Fork 6. Join
Two processes execute, run, or process either A join is one where two results of concurrent activities
concurrently or in parallel at this location. It generally add and form a single result. When you join, you input
includes a single input but may or may not get one multiple things but only receive one output. Two
activities yield two results, while one activity yields one
output.
result.
 D. UML DIAGRAM SYMBOLS
THERE ARE MANY DIFFERENT TYPES OF UML DIAGRAMS AND EACH
HAS A SLIGHTLY DIFFERENT SYMBOL SET.

6. End State

This is the last stage of the UML activity diagram. This is

where the activity ends in a software system ends.
WHY IS IT ESSENTIAL FOR SOFTWARE DEVELOPERS, ARCHITECTS
AND PROJECT STAKEHOLDERS TO USE THESE TOOLS IN SYSTEM
DESIGN? HIGHLIGHT THE BENEFITS AND ADVANTAGES OF
EMPLOYING SUCH TOOLS IN THE DESIGN PHASE?
It sets the foundation for the entire project. It helps to define the architecture,
components, modules, interfaces, and data for a system to satisfy specific requirements. A
well-designed system can be more efficient, scalable, and maintainable.

Advantages of System Design

It reduces the cost of designing.

It eliminates inconsistencies.
It speeds up the process.
It makes the life of the customer easier and simpler.
It provides a lot of resources.
 WHY IS IT ESSENTIAL FOR SOFTWARE DEVELOPERS, ARCHITECTS
AND PROJECT STAKEHOLDERS TO USE THESE TOOLS IN SYSTEM
DESIGN? HIGHLIGHT THE BENEFITS AND ADVANTAGES OF
EMPLOYING SUCH TOOLS IN THE DESIGN PHASE?
Why Should We Use System Design?

1. Reliability

It means the ability of a system to endure faults or problems to prevent failures or complete shutdowns. This is the
beauty and advantage of building fault-tolerant systems using fault-intolerant parts.

2. Scalability

Scalability is the system’s ability to perform and give a reasonable performance in the situation of heavy load.
Performance can be considered the system’s operating traits when the system’s load parameter is changed. These are
used to overcome these problems and reduce the user’s efforts.

3. Maintainability

The code should be written in a way that allows someone who is not the original author to easily understand and make
improvements to it. Good Code should have clean APIs and interfaces to construct new functionalities every time.
 WHY IS IT ESSENTIAL FOR SOFTWARE DEVELOPERS, ARCHITECTS
AND PROJECT STAKEHOLDERS TO USE THESE TOOLS IN SYSTEM
DESIGN? HIGHLIGHT THE BENEFITS AND ADVANTAGES OF
EMPLOYING SUCH TOOLS IN THE DESIGN PHASE?

Help your in career grow

Through the acquisition of this knowledge, the user will become proficient in designing
interfaces and modules for companies and businesses. Moreover, they will develop a set of
skills that are instrumental in advancing their career prospects and future opportunities.
This technology facilitates an analytical examination of company strengths and weaknesses
to identify potential areas for growth or improvement.
 IN CONCLUSION,

Conclusion

The primary objective of any business is to generate revenue and maximize profits. This
approach not only enhances the quality of operations but also leads to increased
profitability. A well-designed system offers numerous benefits such as optimal quality
control, reduced production costs, and streamlined product and data processing. It is an
essential prerequisite for every industry and organization.
UML DIAGRAMS
UML DIAGRAMS
USE CASE DIAGRAMS
USE CASE DIAGRAMS
ACTIVITY DIAGRAMS
ACTIVITY DIAGRAMS
ORIGINAL UML USE
CASE DIAGRAM
THE DEVELOPMENT OF WEB - BASED OJT
RECORDS MONITORING SYSTEM
FOR THE COLLEGE OF COMPUTER
STUDIES IN LAGUNA STATE
POLYTECHNIC UNIVERSITY STA. CRUZ
CAMPUS

RESEARCHERS:
CONSOLACION DANIELO MARCO ELLOYD C.
DEL MUNDO JOHN CEDRICK P.
MODIFIED UML USE
CASE DIAGRAM
 STRENGTHS

1. SIMPLIFY
2. ORGANIZE
3. COST-EFFECTIVE
 WEAKNESSES

1. INTERNET RELIANCE
2. REDUCED SPEED
3. WEBSITE DEPENDENCY
 ORIGINALITY

1. TRACKING FEATURE
2. REPORTS GENERATION
3. DOCUMENT VALIDATION
 NOVELTY

1. WEB APPLICATION
2. EASE OF ACCESS
3. AUTOMATION
 REFERENCES

[Link]
/ [Link] [Link]
[Link]
[Link]
[Link]
developers-3ol7/
 END OF PRESENTATION
Presentation by John Jaycel Articona
Ajel Rafael Ballarbari
John Marie Nerpio

ITEL - 305 | 2024 Mr. John Randolf Peñaredondo