Polytechnic University of the Philippines CAPSTONE 2

Sta. Rosa Campus INSTRUCTIONAL MATERIAL

LESSON 1. System Architecture

What is System Architecture?

System architecture refers to the high-level structure and organization of a complex system, such
as a computer system, software application, or network. It defines the components, their
relationships, and how they work together to achieve a specific set of goals or functions. System
architecture is a critical aspect of designing and building systems, as it provides a blueprint for
how different parts of the system will interact and function as a whole.

For your study, we are going to create 4 system architectures. System Architectures shall be
presented after the consideration part of Chapter 3.

1. Software Development Life Cycle (SDLC)

2. System Flow Diagram (SFD)
3. Data Flow Diagram (DFD)
4. Hierarchical Input Process and Output (HIPO)
5. Contextual Diagram

Software Development Life Cycle

The Software Development Life Cycle alludes to a process utilized by the Software Development
Industry for designing, developing, and testing software solutions. The objective of this process is
to develop high-quality software solutions that exceed or meet user expectations within stipulated
time frames. SDLC is also known as a software development process, which is a framework that
defines software development tasks that are formed at every phase of the development process.

The project follows the process which consists of a detailed plan elaborating on how to develop,
maintain, alter, replace, or enhance the software solutions. A typical software process consists of
multiple stages such as planning and requirement analysis, defining requirements, designing a
software product architecture, developing the software solution, testing the project, deploying or
maintaining the software in the market.

IM Developed by: Date Created: Revision No.

CAPSTONE 2 Page No.
Mr. Owen Harvey Balocon INSTRUCTIONAL MATERIAL July 31, 2023 2023 - 000 ___ of ___
Instructor
 Polytechnic University of the Philippines CAPSTONE 2
Sta. Rosa Campus INSTRUCTIONAL MATERIAL

An Introduction To The Software Process Model

Software processes refer to a coherent set of activities and processes required for specifying,
designing, implementing, and testing the software systems. Any software process model is the
abstract representation and ideation of a process that can highlight the description of a resembling
process for a few specific perspectives.

There are multiple software processes that majorly involve:

• Specification: It defines which systems would perform what job.
• Design And Implementation: It defines the organization of the software systems and their
subsequent implementation.
• Validation: It checks what the customer wants from the required system.
• Evolution: It involves changing the system corresponding to the user requirements.

1. Waterfall Model

The Waterfall model represents a

breakdown of software project
activities in a linear sequential phase.
Each phase of this model relies on the
deliverables of the previous phase,
and it corresponds to the particular
aspects of the tasks. The Waterfall
model is the first software process
model that was introduced. This model
is extremely easy to understand by the
developers.

Each phase of this model is completed before the next phase to avoid the overlapping among the
multiple phases. The Waterfall model illustrates the software process in a linear sequential flow,
which means that any face of the whole process begins only if the previous phase is completed.
The approach of this model is typical for most of the areas of software engineering design.
IM Developed by: Date Created: Revision No.
CAPSTONE 2 Page No.
Mr. Owen Harvey Balocon INSTRUCTIONAL MATERIAL July 31, 2023 2023 - 000 ___ of ___
Instructor
 Polytechnic University of the Philippines CAPSTONE 2
Sta. Rosa Campus INSTRUCTIONAL MATERIAL

It goes from requirements > design > development > testing > deployment > maintenance.

2. Iterative Mode

An Iterative software
development life cycle
model does not directly
attempt to begin with a full
specification of the
prerequisites. Instead, it
starts by focusing on a
simplified and initial set of
user features and activities.
These features are then
progressively developed to
gain complexity and a broad
range of functions until the expected software system is finished. While adopting the Iterative
software model approach, the philosophy of gradual incremental development is also used
liberally.

3. V Model

The V model for software process

represents a development
methodology that can be considered
as an extension of the Waterfall
software model. In this process,
instead of moving down in a unique
and linear manner, the steps of the
process are bent upwards soon after
the coding phase, to develop a typical
V shape.

IM Developed by: Date Created: Revision No.

CAPSTONE 2 Page No.
Mr. Owen Harvey Balocon INSTRUCTIONAL MATERIAL July 31, 2023 2023 - 000 ___ of ___
Instructor
 Polytechnic University of the Philippines CAPSTONE 2
Sta. Rosa Campus INSTRUCTIONAL MATERIAL

4. RAD Model

The Rapid Application Development

Model was first proposed by IBM in the
1980s. The critical feature of this
model is the use of powerful
development tools and techniques. A
software project can be implemented
using this model if the project can be
broken down into small modules
wherein each module can be assigned
independently to separate teams.
These modules can finally be
combined to form the final product. Development of each module involves the various basic steps
as in the waterfall model i.e analyzing, designing, coding, and then testing...

5. Spiral Model

The Spiral model refers to a test-driven

software development model that was
introduced for superimposing the
shortcomings present in a conventional
Waterfall model. The Spiral model looks
exactly like a spiral having multiple
loops. The exact number of spiral loops
is unknown and they can differ from
project to project. The Spiral model
facilitates risk handling management, and the final software project is delivered in the form of
loops.

6. Agile Model

The Agile model refers to an umbrella term for a specific

set of practices and methods based on the values
expressed in the same manifesto. Agile manifesto
represents a way of thinking that allows businesses and
team members to quickly innovate and respond to the
ever-changing demands of the industry while eliminating
the risks. Organizations can use the Agile methodology
with the help of various available frameworks such as
Kanban, Lean, Scrum, etc.

IM Developed by: Date Created: Revision No.

CAPSTONE 2 Page No.
Mr. Owen Harvey Balocon INSTRUCTIONAL MATERIAL July 31, 2023 2023 - 000 ___ of ___
Instructor
 Polytechnic University of the Philippines CAPSTONE 2
Sta. Rosa Campus INSTRUCTIONAL MATERIAL

System Flow Diagram (SFD)

A system flow diagram, often referred to as a system flowchart or simply a flow diagram, is a
visual representation of the flow of data, processes, and interactions within a system. It is a
graphical tool used to illustrate how a system works, showing the steps, activities, and decision
points involved in a particular process or system.

Key elements of a system flow diagram include:

1. Processes/Activities: These are represented by geometric shapes like rectangles or
squares. Each process/activity represents a specific action or operation that occurs within
the system.
2. Arrows/Flow Lines: These connect the processes and indicate the order in which they are
executed. The direction of the arrows shows the flow of data or control from one process
to another.
3. Data Inputs and Outputs: Data inputs are typically shown as arrows entering a process,
and data outputs are represented as arrows leaving a process. This illustrates the data
flow between processes.
4. Decision Points: Decision points are usually represented by diamonds or other suitable
shapes. They represent points in the process where a decision is made, and the flow may
follow different paths based on the decision's outcome.
5. Connectors: These are used to indicate that a flowchart continues on another page or
location. They are often labeled with letters or numbers to help you trace the flow.

IM Developed by: Date Created: Revision No.

CAPSTONE 2 Page No.
Mr. Owen Harvey Balocon INSTRUCTIONAL MATERIAL July 31, 2023 2023 - 000 ___ of ___
Instructor
 Polytechnic University of the Philippines CAPSTONE 2
Sta. Rosa Campus INSTRUCTIONAL MATERIAL

Data Flow Diagram (DFD)

A Data Flow Diagram (DFD) is a graphical representation of how data moves within a system.
DFDs are used to model and document the flow of data through processes or functions in a
system and illustrate how inputs are transformed into outputs through these processes. They
are a valuable tool in systems analysis and design for understanding, documenting, and
visualizing how data is processed and shared within an organization or a software application.
Key components of a Data Flow Diagram include:
1. Processes: Processes are represented by circles or ovals and symbolize activities or
transformations that occur within the system. Each process takes input data, processes
it, and produces output data.
2. Data Flows: Data flows are represented by arrows and show the movement of data from
one location to another. They indicate the flow of information between processes, data
stores, and external entities.
3. Data Stores: Data stores are represented by rectangles and represent places where
data is stored within the system, such as databases or file systems.
4. External Entities: External entities, often depicted as rectangles, represent entities
outside the system that interact with the system. These can be people, other systems, or
organizations that provide input or receive output from the system.
5. Data Flow Annotations: Data flow arrows are labeled with the data's name and often
include data flow descriptions to specify what the data represents.

IM Developed by: Date Created: Revision No.

CAPSTONE 2 Page No.
Mr. Owen Harvey Balocon INSTRUCTIONAL MATERIAL July 31, 2023 2023 - 000 ___ of ___
Instructor
 Polytechnic University of the Philippines CAPSTONE 2
Sta. Rosa Campus INSTRUCTIONAL MATERIAL

Hierarchical Input Process and Output (HIPO)

The Hierarchical Input Process and Output (HIPO) model is a structured method used for the
design and documentation of software systems, particularly during the early stages of system
analysis and design. HIPO is a top-down approach that helps developers and analysts break
down a complex system into manageable, hierarchical components to understand the input,
processing, and output elements of the system.
HIPO models consist of the following components:
1. Main Routine (MR): At the top level of the hierarchy is the Main Routine, which
represents the highest-level process or function in the system. It's where the primary
processing and coordination of the system occur.
2. Hierarchy Chart (HC): The Hierarchy Chart is a visual representation of the system's
hierarchical structure. It depicts the relationships between the Main Routine and the
subordinate processes, showing the flow of control and data between them.
3. Input Process (IP): Within each subordinate process, there is an Input Process. This
represents the part of the system that receives and processes input data. It defines what
data is required, how it is processed, and the format of the output data that is passed to
other processes.
4. Output Process (OP): The Output Process within each subordinate process defines
how the processed data is presented as output. It specifies the format, layout, and
delivery method of the output.
The HIPO model is a useful tool for system analysts and designers because it provides a
structured way to break down a system's functionality into smaller, more manageable parts. This
hierarchical approach helps in understanding the system's architecture and how data flows
through it, as well as in communicating these concepts with other team members and
stakeholders.
Sample HIPO for Inventory Systems:

IM Developed by: Date Created: Revision No.

CAPSTONE 2 Page No.
Mr. Owen Harvey Balocon INSTRUCTIONAL MATERIAL July 31, 2023 2023 - 000 ___ of ___
Instructor
 Polytechnic University of the Philippines CAPSTONE 2
Sta. Rosa Campus INSTRUCTIONAL MATERIAL

Contextual Diagram
A contextual diagram is a type of diagram used in system analysis and design to provide a high-
level, top-down view of a system. It illustrates the system's boundaries and the interactions
between the system and its external entities, without delving into the internal processes or
components of the system. Contextual diagrams are particularly valuable for understanding and
documenting the relationships between a system and its environment.
Key elements of a contextual diagram include:
1. System: The core of the diagram represents the system being analyzed or designed.
This is typically shown as a rectangle or circle in the center of the diagram.
2. External Entities: These are entities outside of the system that interact with it in some
way. External entities can include users, other systems, organizations, or any external
factors that send or receive data to or from the system. They are typically represented as
rectangles or squares outside the system boundary.
3. Data Flows: Arrows connect the external entities to the system to show the flow of data
between them. These data flows represent the inputs and outputs of the system and are
labeled to describe the nature of the data being exchanged.
4. Processes: The internal workings of the system are not detailed in a contextual
diagram. Instead, a single, simple process is often represented within the system
boundary. This process is generic and doesn't go into the specifics of the system's
internal processes.

IM Developed by: Date Created: Revision No.

CAPSTONE 2 Page No.
Mr. Owen Harvey Balocon INSTRUCTIONAL MATERIAL July 31, 2023 2023 - 000 ___ of ___
Instructor