Chapter II: The Company

Chapter II
The Company

Page | 1
 Chapter II: The Company

2.1 The Company Name

The name of the company is “Siren” means it alarms to think creatively,

deeply and seriously. The company consist of people that are well-organized and
brilliant IT experts. The aim or goal of the company is to deliver a high standards and
well-equipped software. The Siren Company is known in our tag line “we warn and
alarm as quick as the thunder”

2.2 Company Logo

2.3 Company Mission

To provide and/or establish any information system that will serves the
client’s needs and wants. The company have plans to provide the good services that
will meet client’s supposition and more.

2.4 Company Vision

To be known as the best company in the country. To create a system solution

that will provide highly performance of efficiency and will build a good
communication to individual.

2.5 Company Description

 Siren is a group of professional IT experts. Members of Siren are well

versed, have skills and trainings in developing of any information
system.
 Siren was established on January 2019 at Western Mindanao State
University, Institute of Computer Studies.

Page | 2
 Chapter II: The Company

2.6 Company Policies

2.6.1 General Policies

 Every member should participate and cooperate in every

group discussion or meeting. Late and absences are not
allowed except with valid excuses.
 Re-scheduling of plans and meetings will be informed and will
be notified via chat or text.
 At least one member should keep in touch with the project
manager a day before if he/she intends to absent.
 Be civil in any aspects.
 Update every report or progress of the system.

2.6.2 Team Penalties

 Late comers per meeting will pay php20

 If one member did not attend the meeting will pay php50
 Every S.E meeting will collect php10

2.6.3 Team Funding

 The collections from the penalties should be collected on the

next meet-up of the group.
 The amount from penalties funds will be used for printing
purposes.

2.6.4 Team Individual Tasking

 In every activity or task there should be assigned.

 The members will submit on time on the given date of the
submission.

Page | 3
 Chapter II: The Company

2.6.5 Overnight Policies.

 During the overnight each member must do their work and

perform their duties or assigned task.

2.7 Agreement Contract

By means of this, we do hereby agree that all the strategies or policies

stated above is right and true if anyone will break or disrespect the group rules and
regulation will be automatically removed from the group.

Leah Mae Labawan ImeeImbat

Project Manager Archivist

Renier Antonio

Programmer

Mohammad AkimPajiji Ervin Jay Balansag

System Analyst Tester

Page | 4
 Chapter II: The Company

2.8 Company Roles and Responsibility

Members Role Responsibilities

Leah Mae Labawan Project Manager  Managing the
overall responsible
for successful
planning,
execution,
monitoring,
control and closure
of project.
 Identifying and
manage the
project team.
 Developing
Schedules or
Project Plan and
assign task to each
member.
 Monitoring and
Reporting Progress
Renier Antonio Pogrammer  In-charge in
managing the
actual system
development
coding of the
system.
 Update and
expand existing
programs.
 Confirms program
operation by

Page | 5
 Chapter II: The Company

testing it and fixing

errors.
Imee Imbat Archivist  Collects, organize,
store, and provide
access to all
records.
 The one who is in-
charge or
responsible for
keeping all track or
record of the
team’s
documentations.
 Responsible in
ways of organizing
and preserving
collections.
Mohammad Akim Pajiji System Analyst  Understand and
study the
requirements of
the system.
 Will be focusing on
the flow of the
system.
 Collects
information to
analyze and
understand
existing proposed
system.
 Identifying and

Page | 6
 Chapter II: The Company

documenting all
business
requirements.
Ervin Jay Tester  In charge of testing
the system and tell
whether the
system has errors.

2.9 Working Style

Table 2.9.1 Self-Assessment

Member Working Style Self-Assessment

Leah Mae Labawan Rational Extrovert I am the Project Manager

so as a Project Manager I
have my own idea and also
I listen to others opinion
before I finalized my idea
and I know how to deal
with them.

Page | 7
 Chapter II: The Company

Renier Antonio Rational Introvert I am not used to talk a lot

but I listen to others
opinion then that’s the
time I will speak and share
my own opinion.
Ervin Jay Balansag Rational Extrovert I ask for others opinion
before making a decision.

ImeeImbat Rational Extrovert I listen to every member’s

opinion and after that I also
share my own opinion as
well.
Mohammad AkimPajiji Rational Extrovert I just listen to my members
and after the discussion, if I
have an idea that’s the
time I will speak and share
my own opinion.
Members Working Style Group Assessment

Renier Antonio Intuitive Extrovert The team observes that

Renier is very responsible
and he can decide every
matter by not depending
on others opinion.
Ervin Jay Balansag Rational Extrovert The team observes that
Ervin is rational extrovert
because he knows how to
communicate to his co-
members.
Mohammad Akim Pajiji Intuitive Extrovert The team observes that
Akim is a silent person
because he will never

Page | 8
 Chapter II: The Company

speak unless you talk to

him first but he’s sharing
his idea by the time he’ll
speak.
Leah Mae Labawan Rational Extrovert The team observes that
Leah is a rational
extrovert because she
listens and manages the
group very well.
Imee Imbat Rational Extrovert The team observes that
Imee is expresses her
own opinion or idea
during the discussion.
Table 2.9.2 Group Assessment

2.9.3 Personal Assessment

Fig. 2.9.3.1 Leah Mae Labawan (Project Manager)

Fig. 2.9.3.2 Renier Antonio (Programmer)

Fig. 2.9.3.3 Ervin Jay Balansag (System Analyst)

Fig. 2.9.3.4 Imee Imbat (Archivist)

Fig. 2.9.3.5 Mohammad Akim Pajiji (Tester)

Page | 9
Chapter II: The Company

Page | 10
 Chapter II: The Company

2.10 Organizational Structure

 Organizational Chart
Figure 2.10.1 Organizational Structure

Leah Mae Labawan

Project Manager

Renier Antonio
Programmer

Mohammad AkimPajiji
System Analyst

ImeeImbat Ervin Jay Balansag

Archivist Tester

Page | 11
 Chapter II: The Company

 Project Manager Team

Fig. 2.10.2 Project Manager Team
Leah Mae Labawan
Head

ImeeImbat Ervin Jay Balansag

Assistant Assistant

 System Analyst Team

Fig. 2.10.3 System Analyst Team

Mohammad AkimPajiji
Head

Ervin Jay Balansag Renier Antonio

Assistant Assistant

Page | 12
 Chapter II: The Company

 Programming Team
Fig. 2.10.4 Programming Team
Renier Antonio
Head

Ervin Jay Balansag Mohammad AkimPajiji

Assistant Assistant

 Archivist Team
Fig. 2.10.5 Archivist Team
Imee Imbat

Head

Leah Mae Labawan Ervin Jay Balansag

Assistant Assistant

Page | 13
 Chapter II: The Company

 Testing Team
Fig. 2.10.6 Testing Team

Ervin Jay Balansag

Head

Renier Antonio Ervin Jay Balansag

Assistant Assistant

Page | 14
 Chapter III: The Summary of Requirements
Analysis

Chapter III
The Summary of Requirements

Analysis

3.1 Summary of Requirements Analysis

Page | 15
 Chapter III: The Summary of Requirements
Analysis

Methodology

REQUIREMENTS AND
ANALYSIS

DESIGNING

CODING

TESTING

IMPLEMENTING

MAINTENANCE

Page | 16