100% found this document useful (1 vote)
4K views51 pages

Apartment Rental Management System Documentation

The Apartment Rental Management System documentation is a comprehensive guide that provides detailed instructions for managing residential rental properties. It serves as a blueprint for the use and operation of the system, explaining each module including tenant management, leasing procedures, maintenance requests, financial transactions, and reports generation. It includes a series of step-by-step instructions, examples, and screenshots, aimed at helping property managers, landlords.

Uploaded by

Jenny Samson
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
100% found this document useful (1 vote)
4K views51 pages

Apartment Rental Management System Documentation

The Apartment Rental Management System documentation is a comprehensive guide that provides detailed instructions for managing residential rental properties. It serves as a blueprint for the use and operation of the system, explaining each module including tenant management, leasing procedures, maintenance requests, financial transactions, and reports generation. It includes a series of step-by-step instructions, examples, and screenshots, aimed at helping property managers, landlords.

Uploaded by

Jenny Samson
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
You are on page 1/ 51

Republic of the Philippines Western Mindanao State University

COLLEGE OF COMPUTING STUDIES


Department of Computer Science
Zamboanga City

Rental Management
System

In partial fulfillment of the


requirements in CS 132 – Software
Engineering 2

Submitted by:

Alcontin, Ganilyn Avon


Abdulhamid, Fatima Dhoevia Racquiza
Samson, Jenny Babe
Sultan, Kent Lowell
Tarroza, Roselyn
Wong, Steffi

ORENDA | 1
Table of Contents
CHAPTER 1 – PROJECT OVERVIEW...............................................................................................................3
1.1 Product Overview..............................................................................................................................3
1.2 Project Site...................................................................................................................................3
1.3 Background of the Client.............................................................................................................3
1.4 Proposed Solution........................................................................................................................4
1.4.1 Product Summary............................................................................................................................
1.4.2 Information Architecture.................................................................................................................
1.4.3 Feature Set......................................................................................................................................
CHAPTER 2 – THE COMPANY.....................................................................................................................10
2.1 Company Profile........................................................................................................................10
2.2 Company Logo...........................................................................................................................10
2.3 Company Vision.........................................................................................................................10
2.4 Company Mission......................................................................................................................10
2.5 Company Goals..........................................................................................................................11
2.6 Company Organizational Structure............................................................................................11
2.6.1 Overall Team Structure.............................................................................................................11
2.6.2 Management Team..........................................................................................................................
2.6.3 Analysis and Design Team................................................................................................................
2.6.4 Development Team..........................................................................................................................
2.6.5 Testing Team....................................................................................................................................
2.6.6 Training Team...................................................................................................................................
2.7 Company Agreement.................................................................................................................13
2.8 Client Agreement.......................................................................................................................14

ORENDA | 2
CHAPTER 1 – PROJECT OVERVIEW

1.1 Product Overview

The client’s business is a residential property comprised of a 2-story apartment, a bed space,
and a commercial space. Established in the year 2021, which accommodates multiple households
wanting to rent any of the lease premises.

Currently, the property manager manages the property and tenant’s details on paper. Payments
are recorded on record books which has become difficult and may easily get damaged leading to data
loss.

The lack of requirements makes recorded data vulnerable. These problems serve as the basis for
the system’s objective which involves defining customer needs and identifying system characteristics
to determine the effective system functions. This includes a user-friendly system, effective in
processing transactions, and a secure and convenient system.

1.2 Project Site

The Rental Apartment is situated at Purok 11A Acacia Drive, Upper Calarian, Zamboanga City. The
business started operating in December of 2021, owned by a married couple, Dr. Fatima Hafza D.
Sahiddin and Dr. Muamar S. Abduhasan.

The main transaction of the business is the payment transaction. A process wherein rental fee
payments made by the client’s tenant are collected and recorded by the client’s assigned manager or
landlord.

The client aims to have a responsive and user-friendly system, that can provide optimal service
both to them and their customers. Most specifically, to have a system that will make managing their
rental apartment business easier and more secure.

1.3 Background of the Client

The client’s name is Fatima Hafza D. Sahiddin, a 32-year-old and a doctor of pediatrics. She lives at
Logoy Dutay, Talon–Talon, Zamboanga City. Finished her tertiary school at Western Mindanao State
University in the year 2013 with a bachelor’s degree in Nursing. And finished her medical school in the
year 2019 at Ateneo de Zamboanga University. Currently working as a Doctor of Pediatrics in a hospital
in Palawan.

The rental apartment situated at Purok 11A Acacia Drive, Upper Calarian, Zamboanga City is the
first rental business that she owned, and with the success of the business, she also planned in
expanding their rental business and is now working on establishing a new branch on a different
location here in Zamboanga City.

ORENDA | 3
1.4 Proposed Solution
1.4.1 Product Summary

Fatima Hafza D. Sahiddin is the proprietor of a property that features both residential and
commercial rental options. This building's rental management system has been designed to
ensure security and innovation, with a variety of on-site amenities for tenants. Furthermore,
current residents can use the website to access information such as regulations, contact details,
payment reports and updates on maintenance and other projects. The website acts as an
efficient and user-friendly tool for the owner, tenants, and the landlord, making the experience
of renting and residing in the building more streamlined and pleasant.

1.4.2 Information Architecture


User type
ADMIN
 Account management
o Log in
o Forget password
o Profile settings
o Edit profile
o View profile
o Search profile
 Dashboard
o Total tenants
o Total landlords
o Total property
o Total property unit
o Calendar
o Total income
 Tenant management
o Add tenant
o Search tenant
o View tenant
o Edit tenant
o Delete tenant
 Landlord management
o Add landlord
o Search landlord
o View landlord
o Edit landlord
o Delete landlord
o Assign property
o Assign units
 Properties
o Add property
ORENDA | 4
o Delete property
o Edit property
o View property

 Property units
o Assign property
o Add property unit
o Edit property units
o Delete property units
o View property units
o Update property units
o Search property units
 Leases
o Add lease
o Edit lease
o Delete lease
o View lease
o Update lease
o Search lease
 Invoice
o Add invoice
o Edit invoice
o Delete invoice
o View invoice
o Update invoice
o Search invoice
 Reports
o View reports
o Search reports
 Tickets
o Add tickets
o Edit ticket
o Delete tickets
o View tickets
o Update tickets
o Search tickets
 Calendar events
o Add calendar events
o View calendar events
 Settings
o Edit settings
o Update settings
o View settings
 Terms and condition
o View terms and conditions

ORENDA | 5
LANDLORD
 Account management
o Log in
o Forget password
o Profile settings
o Edit profile
o View profile
o Search profile
 Dashboard
o Total tenants
o Total landlords
o Total property
o Total property unit
o Calendar
o Total income
 Tenant management
o Add tenant
o Search tenant
o View tenant
o Edit tenant
o Delete tenant
 Properties
o Add property
o Delete property
o Edit property
o View property

 Property units
o Assign property
o Add property unit
o Edit property units
o Delete property units
o View property units
o Update property units
o Search property units
 Leases
o Add lease
o Edit lease
o Delete lease
o View lease
o Update lease
o Search lease
 Invoice
o Add invoice
o Edit invoice
o Delete invoice
ORENDA | 6
o View invoice
o Update invoice
o Search invoice
 Reports
o View reports
o Search reports
 Penalties
o Add tickets
o Edit ticket
o Delete tickets
o View penalties
o Update penalties
o Search penalties
 Calendar events
o Add calendar events
o View calendar events
 Settings
o Edit settings
o Update settings
o View settings
 Terms and condition
o View terms and conditions

TENANTS
 Account management
o Log in
o Forget password
o Profile settings
o Edit profile
o View profile
o Search profile
 Dashboard
o Total tenants
o Total landlords
o Total property
o Total property unit
o Calendar
o Total income
 Leases
o Add lease
o Edit lease
o Delete lease
o View lease
o Update lease
o Search lease
 Invoice
ORENDA | 7
o Add invoice
o Edit invoice
o Delete invoice
o View invoice
o Update invoice
o Search invoice
 Reports
o View reports
o Search reports
 Penalties
o Add penalties
o Edit penalties
o Delete penalties
o View penalties
o Update penalties
o Search penalties
 Calendar events
o Add calendar events
o View calendar events
 Settings
o Edit settings
o Update settings
o View settings
 Terms and condition
o View terms and conditions

ORENDA | 8
1.4.3 Feature Set

Server-sided User Account Registration System (administered system thru database)


 Log-in
 Account type
 Forgot password

Manage Leases, Landlords, and Tenants (amenable profiling, penalties and lease contracts)
 View, edit, delete, and update the ff.
- Landlords profile
- Tenants profile
- Lease entries

Manage Properties and Property Units (specified amenities and featured occupancy rate)
 View, edit, delete, and update the ff.
- Properties Details
- Property Units entries

Manage Tickets (setting standards with tenants’ rights)


 View, edit, delete, and update the ff.
- Ticket entries

Manage Calendar Events and Monthly Reports (for the purpose of bookkeeping)
 View, edit, delete, and update the ff.
- Report assessments
- Calendar Events entries

Manage Settings (extensive configurations)


 View, edit, delete, and update the ff.
- Billings cost (assess monthly billing rates, electric and water)
- Invoices (summation of rental dues)
- Penalties (manage lease terms with violations)
- Profiling (user profile management)

ORENDA | 9
CHAPTER 2 – THE COMPANY

2.1 Company Profile

The Company name is Orenda. Orenda means a mystical force present in all people that can empower
them to affect the world, or to affect change in their own lives.
A company that provides a quality appropriate business solutions and innovative client-base website.
Together with the team, we are committed in providing and ensuring that the clients will receive the
best possible solutions and maintain a thorough knowledge and understanding of client’s objective and
help their organizations achieve to greater success.

2.2 Company Logo

The ‘o’ under the fire logo is from the company name and the fire element symbolizes our passion,
zeal, creativity, and motivation. It has great power for forging will and determination. As well as the
symbol of the inner light, just like the word ‘Orenda’ – that is present in all people that empowers them
to change their fate, the fire element is also a living symbol of the divine fire that burns in every soul.
Thus, making the logo like a flicking flame that evokes thoughts of passion and creativity, encouraging

talents to ‘keep the fire burning’ in them, to inspire, make a change, and ignite a movement of creative
innovation.

Figure 1: Company Logo

2.3 Company Vision

We strive to be leaders in digital marketing services to ignite a global movement of creative innovation
and provide next generation a top digital works.

2.4 Company Mission

The Orenda Company provide an excellent quality of works as we transform art piece into digital reality
with creative critical thinking and taking into account the individual requirements and unique demands
of each client.
ORENDA | 10
2.5 Company Goals
 Establish good relationship with customers
 Build brand awareness
 Improve customer’s experience
 Increase company's revenue
 Generate qualified professionals
2.6 Company Organizational Structure
2.6.1 Overall Team Structure

Figure 2: Organizational Structure

2.6.2 Management Team


- Responsible for managing the group.

ORENDA | 11
2.6.3 Analysis and Design Team
- Focus on developing the system from designing to coding.

2.6.4 Development Team


- Responsible for the functionality of the system.

2.6.5 Testing Team


- Identify errors and debug the system until the system will meet the client’s expectations.

2.6.6 Training Team


- In charge to enhance individual skills and expertise through training and development
programs to improve proficiency in job or task execution.

ORENDA | 12
2.7 Company Policy

Meetings
Attendance is a must, any member in the team can scheduled a meeting and must be agreed by
everyone. Any member that failed to attend the meeting but has a valid reason will be accepted. 10
minutes late in the meeting will be consider. Members that failed to obey will receive penalty.

Funding
The team will contribute equally to the funding, and all expenses will be divided equally among
the team and must be accompanied by valid receipts for reimbursement purposes. Collection of money
will be done face to face and a member can also pay thru Gcash.

Penalties
Scope: This policy applies to all the member of the team.

Nature of Offense Penalties


st
1. Being inactive in group such as: 1 offense: WARNING and PHP 150.00
 Doesn’t attend in group meeting and 2nd offense: PHP 300.00
failed to present a valid reason. 3rd offense: Name will be reported to the teacher.
 Failure to fulfill responsibilities or
carelessness in completing assigned If still act the same way: Subject for removal or
tasks expulsion from the group.
2. Doesn’t cooperating in the group and 1st offense: WARNING and PHP 150.00
declining task. 2nd offense: PHP 300.00
3rd offense: Name will be reported to the teacher.

If still act the same way: Subject for removal or


expulsion from the group.

Table 1: Penalties

ORENDA | 13
CHAPTER 3 – PROJECT PLAN AND SCHEDULE

3.1 Action Plan

Activity Time Estimates Required Person-in-


Dependencies
# Duration Start End Resources Charge
Phase 1 – Planning
Internet, All
1.1 Create a company 1 Day Aug. 19, 2022 Aug. 19, 2022 -
laptop
Internet, Abdulhamid
1.2 Design a company logo 1 Day Aug. 20, 2022 Aug. 20, 2022 1.1
laptop
Define company mission, vision, and Internet, Samson,
1.3 2 Days Aug. 21 , 2022 Aug. 22, 2022 1.1
goals laptop Tarroza
Define company organizational Internet, Samson
1.4 1 Day Aug. 23, 2022 Aug. 23, 2022 1.1
structure laptop
Define company policies and Internet, Tarroza,
1.5 2 Days Aug. 24, 2022 Aug. 25, 2022 1.4
penalties laptop Alcontin, Wong
Internet, Samson
1.6 Establish and promote company 3 Days Sep. 6, 2022 Sep. 8,2022 1.5
laptop
Internet, Abdulhamid
1.7 Create a client agreement form 1 Day Sep. 7, 2022 Sep. 7, 2022 1.6
laptop
Internet, All
1.8 List of interview questions 1 Day Sep. 8, 2022 Sep. 8, 2022 1.7
laptop
Internet, Abdulhamid
1.9 Validation of interview questions 2 Days Sep. 9, 2022 Sep. 10, 2022 1.8
laptop
Internet, All
1.10 Close a deal with a client 6 Days Sep. 17, 2022 Sep. 22, 2022 1.9
laptop
Internet, Tarroza, Wong
1.11 Create project action plan 9 Days Oct. 14, 2022 Oct. 22, 2022 1.10
laptop
1.12 Determine project milestones and 2 Days Oct. 23, 2022 Oct. 24, 2022 Internet, 1.10 Alcontin

ORENDA | 14
Activity Time Estimates Required Person-in-
Dependencies
deliverables Resources
laptop Charge
Internet, Sultan
1.13 Create work breakdown structure 2 Days Oct. 25, 2022 Oct. 26, 2022 1.11
laptop
Internet, Samson
1.14 Create an online project board 2 Days Oct. 27, 2022 Oct. 28, 2022 1.11
laptop
Internet, Samson
1.15 Create an online Gantt Chart 2 Days Oct. 29, 2022 Oct. 30, 2022 1.11
laptop
Internet, Sultan
1.16 Create Activity Network Diagram 2 Days Oct. 31, 2022 Nov. 01, 2022 1.15
laptop
Determine project critical path and Internet, Sultan
1.17 1 Day Nov. 02, 2022 Nov. 02, 2022 1.16
slack time laptop
Collate project documentation for Internet, All
1.18 1 Day Nov. 03, 2022 Nov. 03, 2022 1.17
Phase 1 laptop
Phase 2 – Analysis
Internet, Samson
2.1 Identify data collection method 1 Day Nov. 4, 2022 Nov. 4, 2022 1.18
laptop
Internet, Samson
2.2 Conduct initial data gathering 2 Days Nov. 5, 2022 Nov. 6, 2022 2.1
laptop
Transcribe and analyze collected Internet, All
2.3 1 Day Nov. 7, 2022 Nov. 7, 2022 2.2
data laptop
Propose initial solution for the Internet, All
2.4 1 Day Nov. 8, 2022 Nov. 8, 2022 2.3
project laptop
Internet, Tarroza
2.5 Determine project cost 1 Day Nov. 9, 2022 Nov. 9, 2022 2.4
laptop
Internet, Alcontin
2.6 Conduct feasibility study 3 Days Nov. 10, 2022 Nov. 12, 2022 2.5
laptop
Internet, Samson,
2.7 List initial project requirements 1 Day Nov. 13, 2022 Nov. 13, 2022 2.6
laptop Abdulhamid
2.8 Determine hardware requirements 3 Days Nov. 14, 2022 Nov. 16, 2022 Internet, 2.7 All
2.9 Determine software requirements laptop 2.7 All
2.10 Determine network requirements 2.7 All

ORENDA | 15
Activity Time Estimates Required Dependencies Person-in-
2.11 Determine database requirements 2.7 All
Internet, Abdulhamid
2.12 Identify software specifications 1 Day Nov. 17, 2022 Nov. 17, 2022 2.11
laptop
Internet, Samson,
2.13 List product features 2 Days Nov. 18, 2022 Nov. 19, 2022 2.12
laptop Abdulhamid
Internet, Samson,
2.14 List product attributes 2 Days Nov. 18, 2022 Nov. 19, 2022 2.12
laptop Abdulhamid
Internet, Abdulhamid
2.15 Create product mockups 5 Days Nov. 20, 2022 Nov. 24, 2022 2.14
laptop
Internet, All
2.16 Finalize documentation for Phase II 3 Days Nov. 25, 2022 Nov. 27, 2022 2.15
laptop
Phase 3 – Design
Internet, Sultan
3.1 Determine system architecture 2 Days Nov. 28,2022 Nov. 29, 2022 2.16
laptop
Internet, Tarroza
3.2 Create business use case 2 Days Nov. 30, 2022 Dec. 01, 2022 3.1
laptop
Create context and data flow Internet, Alcontin
3.3 2 Days Dec.02, 2022 Dec. 03, 2022 3.2
diagram laptop
Internet, Sultan
3.4 Design system models 3 Days Dec. 04, 2022 Dec. 06, 2022 3.3
laptop
Internet, Abdulhamid,
3.5 Design user interface 4 Days Dec. 07 2022 Dec. 10, 2022 3.4
laptop Wong
Internet, Abdulhamid,
3.6 Create product prototype 7 Days Dec. 10, 2022 Dec. 16, 2022 3.5
laptop Wong
Internet, All
3.7 Finalize documentation for Phase III 1 Days Dec. 17, 2022 Dec. 17, 2022 3.6
laptop
Phase 4 – Coding
Write System Module 1 – [Admin Internet, Sultan
4.1 15 Days Jan. 9, 2023 Jan. 23, 2023 3.7
Module] laptop
Write System Module 2 – [Property Internet, Sultan
4.2 10 Days Jan. 24, 2023 Feb. 02, 2023 4.1
Module] laptop

ORENDA | 16
Activity Time Estimates
Required Person-in-
Internet, Dependencies Abdulhamid
4.3 Get feedback from a consultant 1 1 Days Feb. 03, 2023 Feb. 03, 2023 Resources 4.2 Charge
laptop
Internet, Sultan
4.4 Debug, fix bugs, and update modules 5 Days Feb. 04, 2023 Feb. 08, 2023 4.3
laptop
Write System Module 3 – Internet, Tarroza, Sultan
4.5 10 Days Feb. 09, 2023 Feb. 18, 2023 4.4
[Transaction Module] laptop
Write System Module 4 – [Landlord Internet, Samson, Sultan
4.6 10 Days Feb. 19, 2023 Feb. 28, 2023 4.5
Module] laptop
Write System Module 5 – [Tenant Internet, Alcontin,
4.7 10 Days Mar. 01, 2023 Mar. 10, 2023 4.6
Module] laptop Sultan
Write System Module 6 – Internet, Wong, Sultan
4.8 7 Days Mar. 11, 2023 Mar. 17, 2023 4.7
[Notification Module] laptop
Internet, Sultan,
4.9 Integrate System Modules 10 Days Mar. 18, 2023 Mar. 27, 2023 4.8
laptop Abdulhamid
Internet, Abdulhamid
4.10 Get feedback from a consultant 2 1 Days Mar. 28, 2023 Mar. 28, 2023 4.9
laptop
Internet, Sultan
4.11 Debug, fix bugs, and update modules 5 Days Mar. 29, 2023 Apr. 02, 2023 4.10
laptop
Internet, Samson,
4.12 Conduct unit testing 3 Days Apr. 03, 2023 Apr. 05, 2023 4.11
laptop Alcontin
Internet, All
4.13 Finalize product design and coding 4 Days Apr. 06, 2023 Apr. 09, 2023 4.12
laptop
Phase 5 – Testing
Internet, Samson,
5.1 Create testing plan 2 Days Apr. 10, 2023 Apr. 11, 2023 4.13
laptop Abdulhamid
Internet, Abdulhamid,
5.2 Create test cases 3 Days Apr. 12, 2023 Apr. 14, 2023 5.1
laptop Sultan
Internet, Abdulhamid,
5.3 Conduct alpha testing 2 Days Apr. 15, 2023 Apr. 16, 2023 5.2
laptop Sultan
Internet, Abdulhamid,
5.4 Conduct beta testing 2 Days Apr. 17, 2023 Apr. 18, 2023 5.3
laptop Sultan

ORENDA | 17
Activity Time Estimates
Required Person-in-
Internet, Dependencies Abdulhamid,
5.5 Fix system errors 5 Days Apr. 19, 2023 Apr. 23, 2023 Resources 5.4 Charge
laptop Sultan
Conduct software/product attributes Internet, Samson,
5.6 3 Days Apr. 24, 2023 Apr. 26, 2023 5.5
testing laptop Alcontin
Internet, Abdulhamid,
5.7 Conduct user acceptance testing 3 Days Apr. 27, 2023 Apr. 29, 2023 5.6
laptop Alcontin
Internet, Samson
5.8 Create migration plan 3 Days Apr. 30, 2023 May 01, 2023 5.7
laptop
Deploy system/product to client’s Internet, Sultan, Wong
5.9 3 Days May 02, 2023 May 05, 2023 5.8
site laptop
Phase 6 - Maintenance
Internet, Sultan, Samson
6.1 Create product manual 2 Days May 20, 2023 May 21, 2023 5.9
laptop
Gather and analyze customer Internet, Abdulhamid,
6.2 2 Days May 22, 2023 May 23, 2023 6.1
feedback laptop Alcontin
Internet, Alcontin,
6.3 Perform corrective maintenance 2 Days May 24, 2023 May 25, 2023 6.2
laptop Sultan
Internet, Alcontin,
6.4 Perform perfective maintenance 2 Days May 26, 2023 May 27, 2023 6.3
laptop Sultan
Internet, Alcontin,
6.5 Perform adaptive maintenance 1 Day May 28, 2023 May 28, 2023 6.4
laptop Sultan
Internet, All
6.6 Finalize project documentation 3 Days May 29, 2023 May 31, 2023 3.7, 4.13, 6.5
laptop
Turn-over project to client and close Internet, Samson
6.7 1 Day Jun. 01, 2023 Jun. 01, 2023 6.6
the project laptop

ORENDA | 18
3.2 Work Breakdown

1.3 Define company 1.4 Define company 1.5 Define company policies
1.1 Create a company 1.2 Design a company logo
mission, vision, and goals organizational structure and penalties

1.6 Establish and promote 1.8 Create project action 1.9 Determine project 1.10 Create work
Phase 1 1.7 Close a deal with a client
company plan milestones and deliverables breakdown structure

1.11 Create an online 1.12 Create an online Gantt 1.13 Create Activity 1.14 Determine project 1.15 Collate project
project board Chart Network Diagram critical path and slack time documentation for Phase 1

2.1 Identify data collection 2.2 Conduct initial data 2.3 Transcribe and analyze 2.4 Propose initial solution
2.5 Determine project cost
method gathering collected data for the project

2.7 List initial project 2.8 Determine hardware 2.9 Determine software 2.10 Determine network
Phase 2 2.6 Conduct feasibility study
requirements requirements requirements requirements

2.11 Determine database 2.12 Identify software 2.15 Create product 2.16 Finalize documentation
2.13 List product features 2.14 List product attributes
requirements specifications mockups for Phase II
Orenda

3.1 Determine system 3.3 Create context and data 3.6 Create product 3.7 Finalize documentation
Phase 3 3.2 Create business use case 3.4 Design system models 3.5 Design user interface
architecture flow diagram prototype for Phase III

4.1 Write System Module 1 4.2 Write System Module 2 4.3 Get feedback from a 4.4 Debug, fix bugs, and 4.5 Write System Module 3 4.6 Write System Module 4
– [Owner Module] – [Tenants Module] consultant 1 update modules – [Transaction Module] – [Admin Module]
Phase 4
4.7 Write System Module 5 4.8 Write System Module 6 4.9 Integrate System 4.10 Get feedback from a 4.11 Debug, fix bugs, and 4.13 Finalize product design
4.12 Conduct unit testing
– [Product Module] – [Notification Module] Modules consultant 2 update modules and coding

5.1 Create testing plan 5.2 Create test cases 5.3 Conduct alpha testing 5.4 Conduct beta testing

Phase 5
5.6 Conduct
5.7 Conduct user 5.9 Deploy system/product
5.5 Fix system errors software/product attributes 5.8 Create migration plan
acceptance testing to client’s site
testing

6.2 Gather and analyze 6.3 Perform corrective 6.4 Perform perfective 6.5 Perform adaptive 6.6 Finalize project 6.7 Turn-over project to
Phase 6 6.1 Create product manual
customer feedback maintenance maintenance maintenance documentation client and close the project

ORENDA | 19
3.3 Network diagram

ORENDA | 20
ORENDA | 21
ORENDA | 22
ORENDA | 23
ORENDA | 24
ORENDA | 25
Calculate Critical Path and Slack (Include these calculations in the final Network Diagram)

ORENDA | 26
ORENDA | 27
ORENDA | 28
ORENDA | 29
ORENDA | 30
ORENDA | 31
3.4 Milestones and deliverables

Milestones Deliverables
Document of Company Profile
a) Company Name
b) Company Logo
c) Company Mission
d) Company Vision
e) Company Goals
1. Company Establishment
f) Company Policies
1. Meetings
2. Funding
3. Penalties and Offenses
g) Company Organizational

a. Client Agreement Form


b. Data Collection Method
2. Project Hunting and Initial Data c. Interview Questions
Gathering d. Initial Interview with the client
e. Transcribe and Analyze Collected Data

a) Action Plan
3. Project Plan b) Milestone and Deliverables

4. Work Breakdown Structure Tree Designing the wireframe


Diagram
a. Project Critical Path
5. Network Diagram b. Project Slack Time

Documents of Project total funds to complete


6. Project Cost the project

a. Candidate Solution Matrix


b. Technology Gap Analysis
c. Feasibility Study
1. Operational Feasibility
2. Technical Feasibility
7. Project Feasibility Analysis 3. Schedule Feasibility
4. Economic Feasibility
5. Cultural Feasibility
6. Legal Feasibility
d. Feasibility Analysis Matrix

a. Hardware Requirements
b. Software Requirements
8. Project Requirements c. Network Requirements
d. Database Requirements

a. Product Features
9. Software Specifications
b. Product Attributes
ORENDA | 32
Initial Virtual Design of Software Interface
10. Product Mockups
a. Use Case Diagram
b. Context and Data Flow Diagram
11. System Architecture
c. Entity – Relationship Diagram

a. User Experiences
12. Design Prototype b. New Requirements

a. Feedback/Suggestions from client


b. Transcribe and Analyze Collected Data
13. Initial Prototype
c. Initial Solution

a. Interpretations of client’s suggestions


14. Final Prototype b. New Requirements

a. Landowner Module
b. Tenants Module
c. Transactions Module
15. System Modules d. Admin Module
e. Product Category Module
f. Notifications Module

ORENDA | 33
CHAPTER 4– PROJECT COST
4.1 Cost of Project Resources
4.1.1 Effort Cost
To compute the Cost of each Employee’s effort/labor, the required working hours
multiply the hourly rate and the Total days of work.

Job Description Person In Hours/ Rate/Hour Total Working Total


Charge Day Days
Project Manager Samson 8hrs Php 120 226 Php 216,960
Business Analyst Tarroza 8hrs Php 110 226 Php 198,880
Lead Developer Sultan 8hrs Php 130 226 Php 235, 040
Assistant Developer Wong 8hrs Php110 226 Php 198,880
Ui/Ux Designer Abdulhamid 8hrs Php 110 226 Php 198,880
Quality Assurance Alcontin 8hrs Php 110 226 Php 198,880
Engineer
Total Php 1,247,520

Table 4. Effort Cost

4.1.2 Hardware Cost

Item Unit Per/Unit Quantity Total


Laptop Set Php 35,000 6 Php 210,000.00
Flash Drive 30GB/pc Php 1, 200 6 Php 7,200.00
Total Php 217,200.00

Table 5: Hardware Cost


4.1.3 Software Cost
Item Unit Prices/Unit Quantity Total
Software For Development Free
(HTML,CSS, JS, PHP, Mysql, License 6 Free
PYTHON)
Hostinger Account Php1,428.00 1 Year Php 1,428.00
Domain Account Php 50.00 1 Year Php 50.00
Total Php 1,478.00

Table 6: Software Cost

ORENDA | 34
4.1.4 Miscellaneous Cost

Item Total
Food Allowance (8-10 Months) PHP 115,200.00
Transportation PHP 24,000.00
Utility PHP 40,000
Documentation PHP 7,000.00
Total PHP 186,200

Table 7: Miscellaneous Cost

4.1.5 Overall Cost

Expenses Total
Effort cost Php 1,247,520
Hardware cost Php 217,200.00
Software cost Php 1,478.00
Miscellaneous PHP 186,200
Total PHP 1,652,398

Table 8: Overall Cost

4.1.6 Return On investment

Year
Type of Cost 2023 2024 2025 2026 Total
Salary Php 1,247,520 0 0 0 Php 1,247,520
Hardware Php 217,200 0 0 0 Php 217,200
Software Php 1,478 0 0 0 Php 1,478
Miscellaneous Php 186,200 0 0 0 Php 186,200

Table 9: Development Cost

ORENDA | 35
Year
Type of Cost 2023 2024 2025 2026 Total
Maintenance 0 PHP 15,000.00 PHP 25,000.00 PHP 35,000.00 PHP 75,000.00
Repairs 0 PHP 10,000.00 PHP 20,000.00 PHP 40,000.00 PHP 70,000.00
Upgrades 0 PHP 20,000.00 PHP 30,000.00 PHP 50,000,00 PHP 100,000.00
Utility 0 PHP 15,000.00 PHP 25,000.00 PHP 35,000.00 PHP 75,000.00
Total 0 PHP 60,000.00 PHP 100,000.00 PHP 160,000.00 PHP 320,000.00

Table 10: Operational Cost

Year
Type of Cost 2023 2024 2025 2026 Total
Reduce office supplies 0 Php 40,000.00 Php 60,000.00 Php 80,000.00 Php 180,000
Increase sales 0 Php 250,000.00 Php 700,000.00 Php 1,100,000.00 Php 2050000
Reduce wages 0 Php 200,000.00 Php 200,000.00 Php 200,000.00 Php 600,000
Total 0 Php 490,000.00 960,000.00 Php 1,380,000.00 Php 2,830,000

Table 11: Benefits

To get the ROI:


 Formula:
ROI = (Benefits – (Total Cost)) / Total Cost x
100  Given:
Benefits = 2,830,000
Development Cost = 1,652,398
Operational Cost = 320,000
 Where:
Total Cost = (Development Cost + Operational Cost)
Total Cost = 1,972,398

ROI = (Benefits – (Total Cost)) / Total Cost x 100


ROI = (2,830,000– 1,972,398) / 1,972,398 x 100
ROI = 857,602 / 1,972,398 x 100
ROI = 0.43480169823 x 100
ROI = 43.48% in 3 years after the development
Project Resulted to positive (+) ROI.

4.1 Intelligible Cost

 Speed-up clients lease process


 Improve rental management
 Promote transparency of lease and bills
 Improved client’s satisfaction
 Improve security
 Improve data privacy

ORENDA | 36
CHAPTER 5– Requirements Engineering

5.1 Methodology
The software process model that the company chose is the agile model. This divides
development processes into successive project phases. The processes are requirements,
design, develop, test, deploy, review

The first development process of the software model is requirements, in this stage
the team gather and analyze the need and expectation of the client and stakeholders, such as
the admin, landlord, and tenants. The team will identify the necessary features and
functionalities for the system such as the tenant management, rent collection, vacancy
management and reports.

The second development process of the software model is design, the goal of this
phase is to create and have a blueprint that a developers can follow. The team will make a
structured design through the collected requirements in phase one, this includes defining the
system architecture, data models, the user interface design, and process flows.

The third development process of the software model is developed, the


programmers write a code to implement the features and functionalities outlined in the
design phase. They will follow the given specifications and collaborate with the UI designer
and UX designer to ensure the system is built according to the requirements.

The fourth development process of the software model is test, this phase ensures the
quality and reliability of the system, the quality assurance member performs various types of
tests, such us unit test, system tests, user acceptance test, and integration test to validate
that the system meets the requirements and free from bugs. Additionally, any issues
discovered by the tester during the testing are reported and addressed by the development
team.

The fifth development process of the software model is deploy, in this phase once the
system has been thoroughly tested and deemed ready for use, it is deployed to a production
environment. This may involve installing the software on the appropriate servers, setting up
the necessary infrastructure, and configuring the system for use by the end-users.

Lastly, the sixth development process of the software model is review. After the
deployment phase, the team gathers feedback from the end-users and stakeholders to
evaluate how well the system is meeting their needs and expectations. This feedback may
reveal areas for improvement, new requirements, or potential issues that were not identified
during testing. The development team can then address these concerns and make any
necessary adjustments to the system.

5.2 Client, Customers, and other Stakeholders


Client
The company client is Dr. Fatima Hafza D. Sahiddin, a doctor of pediatrics. She finished her
tertiary school at Western Mindanao State University in the year 2013 with a bachelor’s degree in
Nursing. And the owner of the rental apartment situated at Purok 11A Acacia Drive, Upper
Calarian, Zamboanga City.
Customers
The customers of the establishment are mainly people who wants to have an apartment

ORENDA | 37
User Role/Function
Admin All
Landlords  collect rent payments
 handle maintenance and repairs
 enforce lease terms
 screen potential tenants
 manage financial records.
Tenants Rent apartment from landlords

Other stakeholders
 Mr. Jaydee Ballaho - Software Engineer 2 Instructor
 Engr. Marjorie A. Rojas- Software Engineer 2 Instructor

5.3 Project Constraints


5.3.1 Implementation Environment
5.3.1.1 Software Requirements
The following are the software requirements needed for the development of
the project;
 Apache – Local Web Server
 MySQL, PHP – database
 HTML, CSS and JavaScript – for custom code
 Bootstrap – framework
 PHP – Back-end development
5.3.1.2 Hardware Requirements
The following are the hardware requirements needed for the development
of the project;
 Development
 Laptop/PC
5.3.1.3 Network Requirements
The following are the network requirements needed for the development of
the project;
 Wi-Fi Connection.

5.3.1.4 Partner Applications


The following are the partner applications needed for the development of
the project;
 None

ORENDA | 38
5.4 Scope of the Product

ORENDA | 39
5.5 Functional Requirements

5.6 Non-Functional Requirements


Usability
- Colors of the screens are light that complements the shop’s logo.
- Displays confirmation message for transaction verification.
- The error message should help the user input the right input next time.
- The system shall be mobile responsive.
- Texts are readable and understandable for the users.
- The system must be easy to navigate.
- System functionalities are easy to find.
Reliability / Availability Requirements
- The system shall give the same output every time for the same functionality.
- The system shall be bug free and reliable enough for its expected purpose.
Scalability
- The system should support 50 users logging in simultaneously.
Performance
- The system’s response time shall be 200 milliseconds.
- Loading period of the system shall be kept in less than 5 seconds.
Supportability
- The system is supported by Windows 7 and above.
- The system is expected to run in mobile devices.
Security
- Customer’s data/information are restricted only for admins.
Efficiency
- The system shall handle heavy workloads that doesn’t affect the system’s performance.
Appearance Requirement
- The system design is minimalist and clean for the user’s eye.
- The color of the system shall be green with white that complements the shop’s logo.
- The system design shall be well-organized.
- Font size of texts shall be average and not too small
Personalization Requirements
- The default language of the system is English.
- The default theme of the system’s green with white combination.
Access Requirements
- Tenants, Landlords, and Admins of the system can access the system.
- Landlord shall select tickets they will take actions.
- Admins and Landlord is responsible for managing the tenants form and apartment.

Understandability and Politeness Requirements


ORENDA | 40
- The system shall use simple icons that the tenants are familiar in real life.
- The system shall use terminologies that are understandable to non-computer literate
tenants,
Adaptability Requirements
- The system is expected to run in Windows 7 and above.
- The system is expected to run in mobile devices.
Capacity Requirements
- The system can cater 50 customers that is simultaneously logged in.
- The system is expected to run in 6gb-8gb CPU.
- The system is expected to run in 2gb RAM.
- The system is expected to run in a 500mb disk storage capacity.
- The system is also expected to run in a 1gb bandwidth
5.7 Project Issues
5.7.1 Open Issues
The challenges that the company encountered when developing the system is
identifying and defining the requirements of the system. This includes understanding the
needs of the admin, Tenants, and Landlords, as well as the technical limitations that need to
be considered. Scalability is one of the issues of our system because as the system grows it
should be able to handle increasing amount of data. Also, some of our members have poor a
time management and this issue even gets worse when there are many tasks given to us at
the same time. Power interruptions also delays the development of the system. Mental
distress is also one of the hindrances that delays the development of our system.

5.7.2 Off-the-Shelf Solutions


5.7.3 Potential User Problem
Non-computer literate customers that find it hard to navigate and use the
functionalities of the system.

5.7.4 Risk
5.7.5 Waiting room

ORENDA | 41
CHAPTER 6 – SYSTEM DESIGN

6.1 Flow Chart (Old System Vs New System)


OLD SYSTEM (Online Based Smart House Renting Web Application)

ORENDA | 42
NEW SYSTEM (Apartment Rental Management System)

 Admin

ORENDA | 43
 Landlord

ORENDA | 44
 Tenant

ORENDA | 45
6.2 Data Model (ERD)

6.3 Context Flow Diagram (DFD 0)

ORENDA | 46
6.4 Data Flow Diagrams (DFD 1, 2, etc.)

ORENDA | 47
ORENDA | 48
ORENDA | 49
ORENDA | 50
6.5 User Interface

ORENDA | 51

You might also like