Chapter 3.1 - BPLS

7/29/2019 Chapter 3.1 - BPLS

1/58

3.1Software Requirements Specification

7/29/2019 Chapter 3.1 - BPLS

2/58

3.1.1 Introduction

The purpose of this document is to describe requirements for BPLS (Business Permit

and Licensing System. It is important that an agreement of these requirements be

reached so that everyones expectations will be met. This document uses written

descriptions as well as various types of modeling diagrams to illustrate the high level

structure of the application. Although some of these diagrams may seem to convey

similar information that they typically do so in an alternate perspective. This gives

different stakeholders a view of the requirements that is better suited to their area of

responsibility.

7/29/2019 Chapter 3.1 - BPLS

3/58

3.1.1.1 Goals and Objectives

A Web based solution will be delivered so that the client or customer can access the

system through the website by just registering an email to the system. By designing

around a standardized language the application will run on the most popular computer

browsers. In addition, a centralized database will allow the Administrators to response

at the application promptly.

The BPLS (Business Permits and Licensing System) is intended to provide an Internet

based system that will assist the client and LGU officers to apply and process the

Licenses and Permits. The goals and objectives include the following:

1. To reduce time and resources spent by LGUs in the BPLS process;2. To help LGUs improve revenue generation;

3. To provide complete information base on business enterprises in their

localities;

7/29/2019 Chapter 3.1 - BPLS

4/58

3.1.1.2 Statement of Scope

This section contains a general description of the system functionality followed by

detailed requirements that will be traced throughout the project.

Before gaining access to BPLS, client will be required to register user name and

password. Clients access privileges within the system are only to apply and view

process regarding to his/her application. The LGU officer will process the application and

approve the request.

There are three hierarchical levels of services namely: the User Level, the Supporter

Leveland theAdministrator Level.

1. User Level

2. Supporter Level

3. Administrator Level

7/29/2019 Chapter 3.1 - BPLS

5/58

The following table groups user requirements into various categories. Each requirement

is assigned a priority to indicate whether it must be implemented (High) or may be left out

(Low). Low priority requirement\ may be eliminated if it helps in meeting the scheduled

delivery date. Medium priority requirements are not essential and their implementation

will be determined as development of the system progresses.

Requirement Number Priority Reference Description

Access PrivilegesR1 High Client and LGU

OfficerThere shall be three levelsof access: user level,administrator level, and

supporter level.R2 High LGU Officer The administrator andassistant shall only beallowed to filter and processand approve clientsapplication.

R3 High LGU Officer The administrators shall beallowed to enter or edit alldata.

R4 High LGU Officer The administrators andclients shall be allowed to

view and print reports.R5 High Client The clients can viewreports.

SecurityR6 High Client and LGU

OfficerEach user shall be requiredto log on with a unique username and password beforeusing the system. Thepassword does not need tobe unique.

R7 High Client and LGU

Officer

The password shall contain

6 to 15 alphanumericcharacters.R8 Med Code Works After three unsuccessful

attempts to enter apassword the user shall belocked out of the systemuntil their password is reset.

7/29/2019 Chapter 3.1 - BPLS

6/58

R9 High LGU Officer A new password shall beassigned if a user forgets.

ReportsR10 High .R11 High

R12 HighR13 HighUser Interface

R14 High Client and LGUOfficer

The system shall have aWeb based interface thatworks with all browsers.

R15 High LGU Officer The background color of allwindows shall be blue.

R16 High Client and LGUOfficer

The system shall respond toall user requests within lessthan 20 seconds.

3.1.1.3 Software Context

BPLS means implementing systematic and purposeful interventions to ease business

start-up and simplifying registration process by reducing the number of steps and

procedures and reducing processing times and cost.

Whether the LGU (local government unit) has BOSS (Business One-Stop Shop) to

facilitate clients, some of the clients are likely dissatisfied with the service they are

receiving. Some of the common causes of dissatisfaction includes the following:

1. Long idle in LGU offices;

2. Slow transactions;

3.

7/29/2019 Chapter 3.1 - BPLS

7/58

The BPLS software, when implemented correctly, it can reduces transaction time, leading

to increased customer satisfaction, which in turn boosts customer retention. The following

are several benefits of deploying a web based system:

1. Information can be accessed any time at convenience of applicants/clients;

2. Clients may apply licenses and permits without going to LGU offices;

3. Easy application and paperless transactions;

4. Back up storage for the files, records and reports;

5. Automates application and generation of Mayor's Permit and other permits,

computation of taxes and fees, billing, payment, and collection liquidation

processes for LGU officers.

3.1.1.4 Major Constraints

The BPLS system is basically a JAVA application which will requires a web server

supporting this application to run.

7/29/2019 Chapter 3.1 - BPLS

8/58

3.1.2 Usage Scenario

7/29/2019 Chapter 3.1 - BPLS

9/58

3.1.2.1 User Profiles

Actor Description

Administrator An Administrator has the responsibility formaintaining multi-user Web-basedcomputer system. They have unrestrictiveaccess to the Business Permit andLicensing System.

Businessman A Businessman is the customer ofBusiness Permit and Licensing Office.They are responsible for processing andpaying for each permit or license theyneeded from the Business Permit andLicensing Office.

Employee The general name that refers to anadministrator, assessment officer,helpdesk officer, etc.

Cashier The Cashier is responsible for handlingpayments for each transaction inBusiness Permit and Licensing Office.

Inspector An Inspector is responsible for inspectingbusinesses specification, location, andproduction.

System The System refers to the computerhardware and software that controls theapplications. It accepts user inputs,displays user output, and interfaces to theWeb Server through the Internet.

Web Server The Web server is a remote computersystem that maintains the database andthe serves Web pages to the System.

Table 3.1.2.1.1 Actors Definition of BPLS

7/29/2019 Chapter 3.1 - BPLS

10/58

3.1.2.2 Use-cases

The following use-cases are typical interactions between the external and the internal

software system. Each use-case in described in section 3.1.2.2.2.

1. Log onto system

2. Apply online3. Verify schedule

4. Validate schedule

5. Register business

6. Verify business

7. Validate business

8. View account information

9. Update account information

10. Display reminder

11. View report

12. Print invoices13. Enter business information

14. Display warnings

15. Debits accounts

16. Inspect Business Site

17. Assign business permit/license number

7/29/2019 Chapter 3.1 - BPLS

11/58

3.1.2.2.1 Use-Case Diagram

Figure 3.1.2.2.1.1 Use-case Diagram of BPLS

The use-case diagram in Figure 3.1.2.2.1.1 shows six actors that were describes in

section 3.1.2.1. In order to minimize the complexity of this diagram several connection

were left out. For instance, every use-case will typically involve an interaction with the

System and the Web Server, but since this is a secondary activity it is not shown in the

drawing.

7/29/2019 Chapter 3.1 - BPLS

12/58

3.1.2.2.2 Use-Case Description

Use-case: Log onto System

Primary actor: Employee/Administrator

Goal in context: To gain access to the System

Preconditions: The Employee has a valid username and password

Trigger: The Employee needs access to the System to perform their job.

Scenario: 1. The System prompts the Employee for their username andpassword.

2. The Employee enters their username and password.3. The System sends the username to the Web Server.4. The Web Server sends back the password registered to the

username.5. The System verifies the password and sets the users

authorization.6. The Employee is given access to the System to perform

their job.

Exceptions: The username and password cannot be verified.

Use-case: Apply Online

Primary actor: Businessman

Goal in context: To apply for business permit/license

Preconditions: The Businessman has all the required documents

Trigger: The Businessman has to fill-out online application form.

Scenario: 1. The System will ask if the application will be for thefollowing: New, Renewal, Additional, Transfer, or

Amendment.2. The Businessman should fill-out all necessary fields in

online form.3. The Businessman should attach all necessary documents.4. The Businessman will choose specific date/time for his/her

business permit transaction.5. The Businessman should verify his/her appointment though

email or sms.6. The System will validate appointment.7. The Businessman will receive verification notification with

appointment stub attach through email.

Exceptions: The schedule date/time reach its capacity.

7/29/2019 Chapter 3.1 - BPLS

13/58

Use-case: Register Business

Primary actor: Administrator

Goal in context: To register business in the City Business Cycle.

Preconditions: The business is either new, transferred, renewed or personal.

Trigger: The business pass all test and requirements needed.

Scenario: 1. The Businessman applied for business permit.2. The Businessman pass all necessary documents.3. The Inspector inspected the business and has a positive

ratings.4. The System verified and validated the business.5. The Employee approved the business with proper

certification.6. The Administrator will register the business.

Exceptions: The business is already on the market.

Use-case: View Account InformationPrimary actor: Employee

Goal in context: To retrieve account information

Preconditions: The account exists

Trigger: The Employee needs information from one of their accounts.

Scenario: 1. The Employee logs onto the System.2. The Employee selects View Account Information from the

Main Menu.3. The System prompts for the name or ID.4. The System requests the record from the Web Server.5. A report of the record is displayed on the screen.

Exceptions: The account does not exist.

Use-case: Update Account Information


Goal in context: To update the Information contained in an account

Preconditions: The exact spelling of the name in known

Trigger: Account Information has changed and needs to be updated

Scenario: 1. The Administrator logs onto the System2. The Administrator selects Edit Account Information from the

Main Menu.

3. The System prompts for the name or ID.4. The System requests the record from the Web Server.5. A form for the report is displayed on the screen.6. The Administrator edits the appropriate fields.7. The Administrator selects Save.8. The System sends the updated record to the Web Server.9. The Administrators Employee ID, the date, and nature of

change are logged.

7/29/2019 Chapter 3.1 - BPLS

14/58

10. The Administrator receives confirmation that the informationwas saved.

Exceptions:

Use-case: Display Reminder

Primary actor: System

Goal in context: To show the Employees reminder

Preconditions: A reminder has previously entered

Trigger: The date of a reminder is the current date

Scenario: 1. The Employee logs onto the System.2. The System requests the Employees reminder from the

Web Server.3. The System looks for pending reminders.4. The System displays any pending reminder messages.5. The Employee acknowledges the reminder.

6. The System deletes the reminder from the Web Server.Exceptions: The user doesnt logon on the day their reminder.Multiple reminder on the same day.

Use-case: View Report


Goal in context: To view a report

Preconditions: Information required for the report has previously been entered.

Trigger: An Administrator decides to view a summary of BusinessInformation.

Scenario: 1. The Administrator logs onto the System.2. The Administrator selects View Report from the Main Menu.3. The Administrator selects the name of the Report from the

Report Menu.4. The System requests the Report from the Web Server.5. The Report is displayed on the screen.

Exceptions:

Use-case: Print Invoice


Goal in context: To print invoices

Preconditions: Information required for the invoice is in the System Database.Trigger: An Administrator needs to print invoice.

Scenario: 1. The Administrator logs onto the System.2. The Administrator selects Invoices from the Main Menu.3. The System requests the Invoices from the Web Server.4. The Invoices is displayed on the screen and ready to be

printed.

Exceptions:

7/29/2019 Chapter 3.1 - BPLS

15/58

Use-case: Display Warnings

Primary actor: System

Goal in context: Display the current status of your Business Permit

Preconditions: Business Permit/License expiration date range

Trigger: Business Permit/License Status

Scenario: 1. Employee logs onto the System.2. The System checks businesses permit expiration date.3. Based on the data previously entered Employee receives

messages on screen indicating the status of each businesspermit.

4. The System will put on each business permit on inactivestate after the adjustment period.

Exceptions:

Use-case: Debit Accounts

Primary actor: SystemGoal in context: Debits all Business Permit/License 2 days before expiration period

Preconditions: The Business is registered to the BPLO

Trigger: Two days before expiration period

Scenario: 1. The System requests billing information from all activeaccounts.

2. The Web Server returns the amount owed for each Permit.3. The System will send notification via email or sms for

reminder.

Exceptions:

Use-case: Inspect Business Site

Primary actor: Inspector

Goal in context: To assure safeness of the Business

Preconditions: Ethical Business

Trigger: Quality Assurance

Scenario: 1. The Inspector logs onto the System2. The System requests special inspection of the Business.3. The Inspector will visit the site of the business.4. The Inspector will decide if the business will be given the

permit to operate.

Exceptions: Businesses classified as low-risk.

7/29/2019 Chapter 3.1 - BPLS

16/58

Use-case: Assign Business Permit/License


Goal in context: Release Business Permit

Preconditions: Business submit all requirements needed

Trigger: Business pass Inspection (High-risk)

Scenario: 1. The Administrator logs onto the System2. The System send requests into the Web Server.3. The Web Server returns the request.4. The Business Permit/License to operate is ready to be

release.

Exceptions: Out-of-stock Business Permit/License Plaque

3.1.2.3 Special Usage Considerations

1. Billing Fees cannot be changed.

7/29/2019 Chapter 3.1 - BPLS

17/58

3.1.2.4 Activity Diagrams

Figure 3.1.2.4.1 Activity Diagram for logging onto the System

The Figure 3.1.2.4.1 shows action that occur when the user logs on to the computer

system. Access is only granted if the correct username and password combination isentered within the first three attempts. After the third attempts the username will be

locked out and an administrator will need to issue a new password. Once access is

granted the user can use the system according to their level of authorization.

7/29/2019 Chapter 3.1 - BPLS

18/58

Figure 3.1.2.4.2 Activity Diagram for Applying Online

The Figure 3.1.2.4.2 shows the activity involves in applying business permit/license

online. The Businessman should first fill-out online application form, attach necessary

documents (For faster transaction), choose specific date and time suit for their

convenience and availability, verify appointment through email or sms verification code

sent by the System, and finally print appointment stub. A new account will be created

and all application information will be entered into the system with the status of inactive.

7/29/2019 Chapter 3.1 - BPLS

19/58

Figure 3.1.2.4.3 Activity Diagram for Registering Business

The Figure 3.1.2.4.3 shows the activity on how business establishment will be

registered into the City Businesses Circle. The administrator will check businessinformation and status saved on the Web Server before finalizing its registration and

should have the validation from the Inspector if belong to high-risk type business

establishment.

7/29/2019 Chapter 3.1 - BPLS

20/58

Figure 3.1.2.4.4 Activity Diagram for View/Update Account Information

The Figure 3.1.2.4.4 shows that only administrators have access on updating or editing

accounts information request by approval by the accounts owner.

7/29/2019 Chapter 3.1 - BPLS

21/58

Figure 3.1.2.4.5 Activity Diagram for Displaying Reminder

The Figure 3.1.2.4.5 shows the activity process of the system when reminder set fallson to the date it was prepared for.

7/29/2019 Chapter 3.1 - BPLS

22/58

Figure 3.1.2.4.6 Activity Diagram for Viewing and Printing of Reports

The Figure 3.1.2.4.6 shows that only administrator have access to viewing and printingof reports. After the report is displayed on the screen it can be sent to the printer.

7/29/2019 Chapter 3.1 - BPLS

23/58

Figure 3.1.2.4.7 Activity Diagram for Printing Invoices

The Figure 3.1.2.4.7 shows that printing invoices is another activity that is only allowed

by the administrative staff.

7/29/2019 Chapter 3.1 - BPLS

24/58

Figure 3.1.2.4.8 Activity Diagram for Displaying Warnings

The Figure 3.1.2.4.8 shows system activity when Business Permit/License franchise is

almost at their expiration date. The System will display warning messages to notifyaccounts owner of their status.

7/29/2019 Chapter 3.1 - BPLS

25/58

Figure 3.1.2.4.9 Activity Diagram for Debiting Business Accounts

The Figure 3.1.2.4.10 shows the process of debiting businesses accounts. This activity

happens two days before their franchise expires.

7/29/2019 Chapter 3.1 - BPLS

26/58

Figure 3.1.2.4.10 Activity Diagram for Inspection of Business Site

The Figure 3.1.2.4.10 shows the activity of Inspector on how high-risk business type

Permit/license being process.

7/29/2019 Chapter 3.1 - BPLS

27/58

3.1.3 Data Model Description

7/29/2019 Chapter 3.1 - BPLS

28/58

3.1.3.1 Data Objects

Applicant Data Object

Applicant_no A unique identifier assigned to the applicant.Firstname An applicants first name.

Middlename An applicants middle name.

Lastname An applicants last name.

City_address The city address of the applicant.

Provincial_address The provincial address of the applicant.

Gender The applicants gender.

Bday The applicants birthdate.

Occupation The applicants current occupation.

Marital_status The applicants marital status.

Contact_no The applicants phone number.

Email_address The applicants email address.

SSS_no The applicants social security system account number.

TIN_no The applicants TIN number.

Documents Applicants needed document for faster application processing.

Applicant Business Data Object

AB_no A unique application number.

AB_name The name of the business of the applicant.

AB_type The kind of business.

AB_category The line of business.AB_address The location address of the company.

AB_contactno The direct contact number of the company.

AB_emailaddress The official online mailing address of the company.

AB_DTIno The DTI number of the company.

7/29/2019 Chapter 3.1 - BPLS

29/58

AB_CDCno The CDC number of the company.

AB_SSSno The SSS number of the company.

AB_businessare The total land area of the company in square meter.

AB_noofemployee The total number of employee the company has.AB_noofservicevehicle The total number of service vehicle the company has.

AB_typeofvehicle The type of service vehicle the company has.

AB_description The special description of the company.

AB_renting The case if the companys renting space or area.

AB_monthlyrent The monthly rent paid by the company.

AB_rentstarted The exact date the company started renting the area.

Lessor_no The identifier number of the lessor.

Documents The dcouments needed for the process.

Lessor Data Object

Lessor_no The unique identifier of the lessor.

Firstname The first name of the lessor.

Middlename The middle name of the lessor.

Lastname The last name of the lessor.

Address The address of the lessor.

Contactno The contact number of the lessor.

Emailaddress The electronic mailing address of the lessor.

Schedule Data Object

Schedule_no The unique identifier of every schedule.Date The exact date of the specific schedule.

Time The exact time of the specific schedule.

Capacity The maximum number of transaction.

Number The total number of application.

7/29/2019 Chapter 3.1 - BPLS

30/58

Application Data Object

Application_no The unique identifier of every application.

Applicant_no The unique identifier of the applicant.

AB_no The unique identifier ofthe applicants business.Schedule_no The schedule of the applicants application.

Permittype_no The Unique identifier of what kind of permit the company want to obtain.

Status The current state of the application.

Permit Type Data Object

Permittype_no The unique identifier of every permit type.

Permit_name The unique name of every permit.

Permit_category The category of the permit.

Description The detailed description of every permit and license.

Inspection Data Object

Inspection_no The unique identifier of the inspection.

Inspector_name The complete name of the inspector.

Comment The detailed comment and verdict of the inspector.

Status The current status of the inspected business site.

Payment Data Object

Payment_no The unique identifier for the payment transaction.

Description The detailed information about the payment.

Status The state of payment.

7/29/2019 Chapter 3.1 - BPLS

31/58

Registration Data Object

Registration_no The unique identifier of every registration.

Application_no The unique identifier of every application.

Inspection_no The unique identifier of every inspection made.Payment_no The unique identifier for payment.

Status The state of the registration.

Permit Data Object

Pemit_no The unique identifier of permit number.

Registration_no The unique identifier of the registration.

Date The release date of permit.

Validity The validity period of one permit.

Status The state of permit.

7/29/2019 Chapter 3.1 - BPLS

32/58

3.1.3.2 Relationships

In order for the applicant to have an account they need to have a permit from the

Business Permit and License Office (BPLO) in any form (e.g. Business permit,

Occupational permit, or Special permit). It is true that an individual could have multiplepermit at a time but they could only have one account. Prior to that they should apply

online first for them to access their account otherwise they will go to the Business

Permit and Licensing Office (BPLO) of Quezon City to apply manually.

New and old applicant for any kind of permit the Business Permit and Licensing Office

(BPLO) offers they should apply online through their online application process. Plus

they have the luxury of choosing their preferred date and time for their convenience and

availability. And since the application is in fast pace vital requirements like documents,

identification, etc. (Scanned documents) should be attach to the application forminstead of passing it to the Business Permit and Licensing Office (BPLO) on hand.

Business Permit and Licensing Office (BPLO) officer like the inspector have the luxury

of quick navigation since Business Permit and Licensing System (BPLS) have an

android application wherein they can submit their comment and critic on each business

establishment site that should be inspected. By this the waiting time and the processing

time of each permit will be fast enough prior to the need of the applicant.

A maximum of 20 application per hour will be serve by the scheduling system of the

Business Permit and License System (BPLS). And the releasing of business permit will

depend on what type of application it is. For low-risk type of application a maximum of

25 minutes processing time before the releasing of the Mayors Permit (or as long as

stock last).

7/29/2019 Chapter 3.1 - BPLS

33/58

3.1.3.3 Complete Data Model

Figure 3.1.3.3.1 - Relationship Diagram for the BPLS

7/29/2019 Chapter 3.1 - BPLS

34/58

3.1.4 Functional Model Description

7/29/2019 Chapter 3.1 - BPLS

35/58

3.1.4.1 Class Diagram

Figure 3.1.4.1.1 - Class Diagram of BPLS

The associations between the different classes are shown in Figure 3.1.4.1.1.

7/29/2019 Chapter 3.1 - BPLS

36/58

3.1.4.2 Software Interface Description

3.1.4.2.1 External Machine Interfaces

The software will be capable of printing invoices and report on a local or network printer.

3.1.4.2.2 External System Interfaces

The Business Permit and Licensing System (BPLS) will communicate with a Web

Server on the Internet through a high speed network connection such as DSL, cable, or

T1 line.

3.1.4.2.3 Human Interface

The Web pages shall print complete navigation using the keyboard alone, in addition to

using mouse and keyboard combination.

7/29/2019 Chapter 3.1 - BPLS

37/58

3.1.4.3 - Reports

3.1.4.3.1 Inventory of Reports

Report Name Description

Business Permit Shows a view of the business permit.

Inspection Gives detailed description of the inspection made

by the BPLO inspector/s.

Schedule Stub Shows what time the business owner is

scheduled to submit his/her requirements.

Management Report: Business Permit Renewal Gives the list of the business permits renewals.

Management Report: New Business Permits

Issuances

Gives the list of the newly issued business

permits

Management Report: Expired Business Permits Gives the list of the flagged expired businesses.

Analytical Report: Comparative Performance Shows a list of how many new businesses and

renewals have been done during a year gap.

Analytical Report: Daily Permit Issuances Counter Gives a counter on how many new business

permits have been issued as well as the renewals.

Audit trail Gives an activity listing of how the system was

accessed and who is/are the users who has used

a particular feature.

Table 3.1.4.3.1 Inventory Reports
http://3.1.4.3/http://3.1.4.3/http://3.1.4.3/http://3.1.4.3/http://3.1.4.3/http://3.1.4.3/

7/29/2019 Chapter 3.1 - BPLS

38/58

3.1.4.3.2 Layout of Reports

BUSINESS PERMIT NO.: _________ **APPLICATION TYPE**

DATE ISSUED: ___________

This certifies that BUSINESS_NAME with registered trade name as TRADE NAME represented by BUSINESS_OWNER with

business address BUSINESS_ADDRESS has been granted a PERMIT_TYPE to operate the following business/es under ordinance

No. SP-91, S-93, otherwise known as the 1993 Quezon City Revenue Code, and the ordinance/s indicated at the back hereof, subject

to other pertinent ordinances, laws and related administrative implementary regulations.

VALID UNTIL: _______________ APPLICATION NO.: _______________

KIND OF BUSINESS REMARKS

Total No. of Employees: ____ Area of establishment: ______

SSS No.: ______ TIN No. ______

SUBJECT TO THE CONDITIONS AT THE BACK HEREOF

PERMIT FEE & CITY TAX TO BE PAID ON OR BEFORE: DEADLINE

For and by the Authority of the City Mayor:

MAYOR_NAME

OFFICER IN CHARGE

No.: ___________

Figure 3.1.4.3.2.1 Business Permit Report Layout

REPUBLIC OF THE PHILIPPINES

QUEZON CITY, METROPOLITAN MANILA

OFFICE OF THE MAYOR

BUSINESS PERMITS & LICENSE OFFICETelephone No.: 444-7272 Loc. 8173

PARTICULARS OF PAYMENT

IMPORTANT NOTICE

THIS PERMIT IS NON-TRANSFERABLE AND VALID ONLY WITH CORRESPONDING OFFICIAL RECEIPTS SHOWING

PAYMENT OF PERMIT FEES AND CITY TAXES. ANY ERASURE/ALTERATIONS WILL INVALIDATE THIS PERMIT.
http://3.1.4.3/http://3.1.4.3/

7/29/2019 Chapter 3.1 - BPLS

39/58

DATE

FOR: BPLO Chief BPLO

Subject: Taxpayers Name: ______________________________________

Business/Trade Name: __________________________________

Location: _____________________________________________

_____________________________________________

Area: ______ Zone: ______

Findings:

Remarks:

Submitted By:

_______________________ _______________________

Licensed Inspector/Officer Licensed Inspector/Officer

Recommendation:

HEAD, INSPECTION DIVISION

Figure 3.1.4.3.2.2 Inspection Report Layout



OFFICE OF THE MAYOR

BUSINESS PERMITS & LICENSE OFFICE

Telephone No.: 925-6045 Loc. 205/204

7/29/2019 Chapter 3.1 - BPLS

40/58

Figure 3.1.4.3.2.3 Schedule Stub Report Layout

Management Report: Business Permit Renewals

FROM TO

Business Name Description Type First Issued Renewed On

Figure 3.1.4.3.2.4 Management Report: Business Permit Renewals Layout

Claim Stub No. ___________

You are scheduled to go to BPLO on DATE/TIME. This schedule stub is valid only within the scheduled (DATE/TIME)

otherwise you might need to reschedule your appointment. Please present this to make your transaction fast and easy.

Thank you.

NOTE:

Please bring the following document/s with you:

____________________________________

____________________________________

____________________________________

____________________________________



OFFICE OF THE MAYOR

BUSINESS PERMITS & LICENSE OFFICE

Telephone No.: 925-6045 Loc. 205/204

7/29/2019 Chapter 3.1 - BPLS

41/58

Management Report: New Business Permits Issuances

FROM TO

Business Name Description Type Issued On Expires On

Figure 3.1.4.3.2.5 Management Report: New Business Permits Issuances ReportLayout

Management Report: Expired Business Permits

FROM TO

Business Name Description Type First Issued Last Renewed

On

Cumulative

days of

expiration

Figure 3.1.4.3.2.6 Management Report: Expired Business Permits Report Layout

7/29/2019 Chapter 3.1 - BPLS

42/58

COMPARATIVE REPORT

DATE GENERATED: __________________

YEAR A YEAR B

New Renewal Total

Working

Month Day

Start

Working

Month Day

End

Total

Counter

New Renewal Total

Working

Month Day

Start

Working

Month Day

End

Total

Counter

SUMMARY

YEAR A YEAR B

Year to Date

Month to Date

Figure 3.1.4.3.2.7 Analytical Report: Comparative Performance

Daily Permit Issuances Counter

New Renewal Total

Figure 3.1.4.3.2.8 Analytical Report: Daily Permit Issuances Counter

7/29/2019 Chapter 3.1 - BPLS

43/58

Audit Trail

FROM TO

User Module Accessed On Trackback URL

Figure 3.1.4.3.2.9 Audit Trail Report Layout

3.1.4.3.3 Data Dictionary of Reports

Business Permit

Data Data Type Description Allow Nulls

Business Permit No. Varchar Refers to a unique system

generated character for a

particular business.

No

Date Issued DateTime Refers to date the business

permit has been issued.

No

Application Type Integer Refers whether the permit

is new, renewal or

amendment.

No
http://3.1.4.3/http://3.1.4.3/

7/29/2019 Chapter 3.1 - BPLS

44/58

Business Name Varchar Refers to the business

name.

No

Trade Name Varchar Refers to the trade name. No

Business Owner Varchar Refers to the person/s,

organization who owns the

business

No

Business Address Text Refers to the address of

business

No

Permit Type Integer Refers to the type of

permit that an entity has

availed

No

Valid Until DateTime Refers to the date of

expiration of the business

permit

No

Application No. Integer System generated no. No

Kind of Business Text Refers to the nature of

business the business is

operating

No

Remarks Text Refers to the comments of

the officer

Yes

Total No. of Employees Integer Refers to the number of

employees that a business

has.

No

Area of establishment Double Refers to the measured

area of the establishment

Yes

SSS No. Varchar Refers to the Social

Security No.

No

TIN No. Varchar Refers to the Tax

Identification No.

No

Mayor Name Varchar Refers to the mayors full

name

No

7/29/2019 Chapter 3.1 - BPLS

45/58

Officer in Charge Varchar Refers to an authorized

person affixing the

signature for legal business

permits

No

Particulars of Payment Text Refers to a detailed listing

or breakdown of payments

that a business has paid

No

Important Notice Varchar Static notice text No

No. Integer Refers to the business ID,

an auto-incremented

number/integer

No

Table 3.1.4.3.3.1 Business Permit Report Data Dictionary

Inspection


BPLO Chief Name Varchar Refers to the BPLO

head

No

Date DateTime Refers to the date

when the inspection

took place

No

Taxpayer Name Varchar Refers to the

taxpayers name

No


name

No

Location Text Refers to the address

of the business

No

Area Double Refers to the total

square meter size of

the place

No

Zone varchar Refers to the area yes
http://3.1.4.3/http://3.1.4.3/

7/29/2019 Chapter 3.1 - BPLS

46/58

Findings Text Refers to the result of

the observation

No

Remarks Text Additional

commentaries

No

Submitted By Varchar Refers to the

inspectors name

No

Recommendation Text Action that may be

taken next

Yes

Table 3.1.4.3.3.2 Inspection Data Dictionary

Schedule Stub


Claim Stub No. Integer A unique no. that

needs to be presented

on the BPLO

No

Date DateTime Date & Time of

scheduled appointment

No

Table 3.1.4.3.3.3 Schedule Stub Data Dictionary

Management Report: Business Permit Renewals



name

No

Description Text The description of the

business

No

Type Varchar Refers to the type of

business that a

business facilitates

No
http://3.1.4.3/http://3.1.4.3/http://3.1.4.3/http://3.1.4.3/

7/29/2019 Chapter 3.1 - BPLS

47/58

First Issued DateTime Refers to the date

when the business

permit has been first

issued.

No

Renewed On DateTime Refers to the date

when the business

permit has been

renewed.

No

Table 3.1.4.3.3.4 Management Report: Business Permit Renewals Data Dictionary

Management Report: New Business Permits Issuances



name

No


business

No


business that a


No

Issued On DateTime Refers to the date

when the business


issued.

No

Expires On DateTime Refers to the date

when the business

permit is going to

expire

No

Table 3.1.4.3.3.5 Management Report: New Business Permit Issuances Data Dictionary

7/29/2019 Chapter 3.1 - BPLS

48/58

Management Report: Expired Business Permits



name

No


business

No


business that a


No

First Issued DateTime Refers to the date

when the business


issued.

No

Last Renewed DateTime Refers to the date

when the business

permit has been last

renewed.

No

Cumulative days of

expiration

Integer Refers to days

accumulated since the

expiration of the

permit

No

Table 3.1.4.3.3.6 Management Report: Expired Business Permits Data Dictionary

Analytical Report: Comparative Performance


Date Generated DateTime Refers to the date

when the report has

been generated

No
http://3.1.4.3/http://3.1.4.3/

7/29/2019 Chapter 3.1 - BPLS

49/58

Year A Integer Refers to the starting

year of the

comparison e.g. 2008

No

Year B Integer Refers to the ending

year of the

comparison e.g. 2009

No

Working Month Start Varchar Refers to the starting

day along with the

month

No

Working Month End Varchar Refers to the ending

workday along with

month

No

New Integer Refers to the no. of

new released business

permits made for the

working month

No

Renewals Integer Refers to the no. of

renewals made for the

working month

No

Total Integer Refers to the total of

renewals & new

business permits

No

Year to date Integer Refers to the total of

issuances made since

the starting year

No

Month to date Integer Refers to the total of

issuances made fromthe printed day,

month & year

No

Table 3.1.4.3.3.7 Analytical Report: Comparative Performance Data Dictionary
http://3.1.4.3/http://3.1.4.3/

7/29/2019 Chapter 3.1 - BPLS

50/58

Analytical Report: Daily Permits Issuances Counter


New Integer Refers to the no. of

issuance in a specific

day

No

Renewal Integer Refers to the total of

renewals in a specific

day

No

Total Integer Total of both issuance

either new or renewal.

No

Table 3.1.4.3.3.8 Analytical Report: Daily Permits Issuance Counter Data Dictionary

Analytical Report: Audit trail


User Varchar Refers to the user who

accessed a module

No

Module Varchar Refers to the module

accessed by user

No

Accessed On DateTime Refers to the date and

time the module was

accessed.

No

Trackback URL Varchar A link to the specific

module

No

Table 3.1.4.3.3.8 Analytical Report: Daily Permits Issuance Counter Data Dictionary

3.1.5 - Behavioral Model Description

3.1.5.1 Description for software behavior

7/29/2019 Chapter 3.1 - BPLS

51/58

3.1.5.1.1 Events

Applicant Class Events

Applicant fills out the application form

Applicant gets a schedule

Applicant renews business permit

Applicants business permit expires

Employee Class Events

Employee is hired

Employee logs onto the system

Employee logs off from the system

Employee is no longer employed

Schedule Class Events

Applicant is added to the scheduled list

Employee verifies the claim stub

Applicant submits the true copy of the documents

Applicants scheduled meeting is deactivated

Applicants schedule reactivated

7/29/2019 Chapter 3.1 - BPLS

52/58

Inspection Class Events

Inspector sends a mission order

Inspector fills out his/her findings on the inspection

Inspection tags the business accordingly

frd is lifted

Renewal Reminder

Applicant logs on the system

Receives a notification with regards to the nearing of the deadline of expiration

Applicant pays

Business Permit gets renewed

3.1.5.1.2 States

Applicant States Description

Filling out The applicant is in the process of filling out

his/her application

Receiving The applicant has received a schedule of

appointment

Logging In The applicant has login account

Active The applicant account has been activated and is

now active

Employee States Description

Hired Tan employee has been hired and his information

has been taken for setup.

7/29/2019 Chapter 3.1 - BPLS

53/58

Active The employee account is by default an active

account

On Line The employee has logged on to the system

Off Line The employee has logged off to the system

Inactive The employees account has been tagged

inaccessible for a time being

Schedule States Description

Under capacity Not more than forty applicants must be encoded

per hour basis

At capacity The maximum 250 applicants has been

successfully transacted in a whole dayClosed No applicant can be scheduled for the meantime

Renewal Reminder States Description

Logging The applicant logs on to his/her account

Notifying The system will automatically send a notification

that the business permit must be updated

on/before the deadline.

Acknowledged The system has acknowledged that the applicant

has successfully obeyed the needed tasks for the

renewal

Refreshing The system will then change the deadline since

the renewal.

7/29/2019 Chapter 3.1 - BPLS

54/58

3.1.5.2 Statechart Diagram

A statechart diagram for the entire system is shown in Figure 3.1.5.2.1. After a user logs

on the system will check for accounts and update account records as needed. The user

will then select a hyperlink to load the appropriate page.

7/29/2019 Chapter 3.1 - BPLS

55/58

3.1.5.2.1 Overall system statechart diagrams

7/29/2019 Chapter 3.1 - BPLS

56/58

3.1.5.2.2 Statechart diagrams

7/29/2019 Chapter 3.1 - BPLS

57/58

3.1.6 Restrictions, Limitations, and Constraints

1. The System shall integrate within the existing LAN structure and with the existing

Systems such as the database management systems.

2. All HTML codes shall conform to the HTML 4.0 standard.

3. All server side code shall be written in JAVA Server Page (JSP).

4. Internet Explorer 7 or newer such as Mozilla Firefox and Google Chrome

3.1.7 - Validation Criteria

Software validation will ensure that the system responds according to the users

expectations; therefore it is important that the end users be involved in some phases of

the test procedure. All tests will be traced back to the requirements in section 1.2.

3.1.7.1 Classes of tests

1. Unit testing will be conducted on all software subsystems including

1. User Account

2. Scheduling of applicants

3. Notification/notices

4. Application

5. Access rights of employees

6. Viewing and printing reports

7. Viewing and editing information

8. Logging out of the system

2. Test cases for black box testing will be based on equivalence categories. These

categories values that lie on and around the boundary values of a function. For

example, if a function can accept values from 0 to 100 then the test cases willinclude the values -1, 0, 1, 99, 100, and 101.

3. Acceptance testing will be conducted on the customers site.

7/29/2019 Chapter 3.1 - BPLS

58/58

3.1.7.2 Expected software response

1. The software should display an appropriate error message when a value outside

the accepted limit is entered.

2. The software should not be capable of deleting any record even if the business,

for example, has already expired.

3.1.7.3 Performance bounds

1. The system shall support up to 100 simultaneous users against the Website/Web

Server at any given time.

2. The system will provide access to the database management system with a

latency of no more than 20 seconds.