Department of Computer Science and Engineering (CSE)

Faculty of Science and Engineering

Semester: (Fall, Year: 2022), [Link]. in CSE (Day)

PROJECT REPORT
TO-LET FIND YOUR HOUSE

Course Title: Information System & Design Lab

Course Code: CSE 438    Section: 191-D1

Team member

191002228 Zeneya Sharmin

191002365 Bishozit Chandra Das

Submission Date: 17.10.2022 to 09.01.2023

Course Teacher’s Name: Most. Rokeya Khatun
Lecturer, Dept. of CSE, Green University of Bangladesh

TABLE OF CONTENTS
Chapter 1: Planning 1

To-Let: Find Your house 1

 1. Project Scope Statement 2
1.1 Introduction 3
1.2 Motivation 3
1.3 Objective 3
2. Requirement Collection & Project Budget 4
3. Methodology 4
4. Related Work 4
5. Feasibility Analysis 4
6. Prototype 4
7. Detailed Working plan 4
8. Gantt Chart of Project Development Timing 4
9. Discussion & Conclusion 4
10. References 4

Chapter 2: Analysis 5
1. Requirements determination of the project 2
1.1 Introduction 3
1.2 Interview Outline 3
1.3 Observation Table 3
2. Related Work 2
3. Contemporary Methods 2
3.1 Prototype 3
4. Risk Analysis 2
5. Risk Probability & Impact 2
6. Discussion & Conclusion 2
7. References 4

Chapter 3: Design 5
1. Introduction 2
2. Related Work 2
3. Methodology 2
4. Detailed Working Plan 2
5. Components of UML Use Case Diagram 2
6. Use Case Diagram 4
7. Data flow Diagram 4
7.1 Level 0 4
7.2 Level 1 4
8. ER Diagram 4
9. Prototype 4

To-Let: Find Your house 2

 10. Discussion & Conclusion 4
11. References 4

Chapter 4: Implementation 5
1. Introduction 3
2. Logical Database 2
2.1 Renter/ Owner 3
2.2 Admin Panel 3
3. Physical Database 2
3.1 User 3
3.2 Admin Panel 3
4. Sequence Diagram 2
5. Discussion & Conclusion 2
6. References 4

Chapter 5: Implementation & Maintenance 5

1. Introduction 3
2. Form Design 2
2.1 Registration3
2.2 Login 3
2.3 Create a post 3
2.4 Profile 3
2.5 Admin Panel 3
3. Coding 2
3.1 User 3
3.2 Create a post 3
3.3 Admin Panel 3
4. Algorithm 2
4.1 For User 3
4.2 For Create a post 3
4.3 For Admin Panel 3
5. Testing 2
5.1 Testing Methods 3
5.2 Test Case 3
6. Installation 2
7. Documenting the System 4

7.1 System Documentation 3

To-Let: Find Your house 3

 7.2 User Documentation 3
8. Training 2
9. Support 2
10. Discussion & Conclusion 2
11. References 4

Chapter 6: Conclusion & Future Work 5

1. Final Conclusion 3
2. Limitations 2
3. Future Plan 2
4. References 4

CHAPTER 1: PLANNING
1. PROJECT SCOPE STATEMENT
1.1. Introduction: 
House Rental is a house/Apartment/home that can be used temporarily for a fee during a
specified period. The individual who needs a house must contact a rental car company and
contract out for a room/home/apartment. This system increases customer retention and simplifies
House and staff management.

1.2. Motivation:

To-Let: Find Your house 4

  For everyone finding a house is a hassle nowadays, to reduce this issue we are planning
to make an application. 
 For example, in Dhaka city there are a lot of opportunities for students and service
holders. Especially for girls. So, surrounding the workplace, finding a house with a short
amount ensures security is essential.
 Very often owners are not ensuring security for that reason renters may suffer a lot so to
mitigate this our app can help.

1.3. Objective:
 To develop a system to make an easy approach for To-Let management. 
 To develop Mobile applications to maintain and monitor the whole system and
security. To make a better analysis report for future uses. 
 To save valuable time searching for houses. 
 To reduce the work in pen and paper and to use the time properly. 
 An easy interface where users can easily interact and show their relevant
information. 
 To develop a combined environment for better and quality full services. 
 To maintain client details, contact details, house details, Rental type, etc.

2. REQUIREMENT COLLECTION & PROJECT BUDGET

Type Name Quantity  Budget

Business requirement  Team meeting —- $400

 Project meeting —- $500
 Marketing —- $350
 Office Rent 1 $150
 First Aid 2 $70
 App Maintenance 1 $400
 Overhead Cost —- $500
Software requirement  Xampp —- —-
 Java —-

To-Let: Find Your house 5

  Figma $400
 MS Office —-
 Others $100
 GitHub —-
Hardware  PC/Laptop 2  $500*2
Requirement  Smartphone for testing 5 $150*5
purpose
 Others
Employee Salary Team Leader 1 $100
System Designer 2 $350
Software engineer 1 $400
Developer 2 $450
Software tester 1 $250
Customer   Students,  100 people for —---
 service holders,  testing
purposes
 searching for a rent.
Marketing Literature Analyzing the university —-- —---
students' suffering. 

3. METHODOLOGY (FLOW CHART)

Here include our project working methodology:

To-Let: Find Your house 6

 Figure 1: Methodology of To-Let Find your house

4. RELATED WORK 
Firstly, we studied some websites for this kind of rented flat, apartment, etc. Here are some of
them.
Name of Website Contribution Limitation
[Link]:   Buying and selling  More Complex to use
flat, Apartments and  Backdated
office. information.
 The location is not  High maintenance and
that correct. costly.
Rental home [Link]:  Works for sale and  Commonly Fraud
rent activity
 Do not show the
rating.
 Backdated updates
 Buy and sell products.  Management System
[Link]:  Flats, Apartments and is not good
office area  Take a lot of time to
execute any feature

5. FEASIBILITY ANALYSIS

To-Let: Find Your house 7

Now, we tried to compare our proposed application with exiting application. So, for that we need
to complete the following table

Topic Operational  Technical Financial

[Link]:  I. Need more steps I. Poor management I. Service

to execute any system. charge is
feature. II. Complexity is high
II. Less Accuracy high

Rental home I. Need more steps I. Poor management I. Service

[Link]: to execute any system. charge is
feature. II. Complexity is high
II. Less Accuracy high.

I. Need more steps I. Poor management I. Service

[Link]: to execute any system. charge is
feature. II. Complexity is high
II. Less Accuracy high.

To-Let Find your I. Need less steps to I. Poor management I. Service

House execute any system. charge is
feature. II. Complexity is Less than
II. Rate Accuracy is high. others
high

6. PROTOTYPE
The prototype of the project is shown below: prototypes are build using Figma[1]

To-Let: Find Your house 8

 Figure 2: Figma prototype of To-Let Find your house

7. DETAILED WORKING PLAN

Task Time Responsible Person

Identify the problem & define its scope & perform 2 Zeneya Sharmin &
analysis(feasibility, requirement). Proposed model for the weeks Bishozit Chandra das
development.

Performance analysis on the functions and whether it is 1.5 Zeneya Sharmin

achievable or not weeks

Finalize the development model & prepare the Gantt chart 2 Bishoizit Chandra das
for overall development weeks

Create DFD, E-R diagram, flowchart, Decision tree & 2 Zeneya Sharmin
decision table for project weeks

To-Let: Find Your house 9

 Describe UML diagrams, draw all as per the system  1.5 Bishoizit Chandra das
weeks

Plan the overall sequence (final) to perform all the tasks 2 Zeneya Sharmin &
and tie limits of each module. weeks Bishoizit Chandra das

[Link] CHART [WEAK VS ACTIVITIES VS MEMBER RESPONSIBILITIES]

Figure 3: Gantt Chart of To-Let Find your house

9. DISCUSSION & CONCLUSION

We must gather information on the present information systems in use, as well as how users
would like to improve current systems and organizational processes with new or replacement
information systems. That is why traditional methods for determining the system requirements
are useful. We have successfully found out the requirements after lots of planning and analysis
now we will design our system through several process of interview, risk analysis and other
evaluations.

To-Let: Find Your house 10

10. REFERENCES
[Link]
[Link]
[Link] integration- and-
functional-testing/
[Link]
[Link]
[Link]
Figma Online Available: [Link]
node-id=220%3A2&scaling=scale-down&page-id=0%3A1&starting-point-node-id=11%3A6

CHAPTER 2: ANALYSIS
1. REQUIREMENT DETERMINATION OF THE PROJECT

1.1. Introduction: 
The process of observing systems for troubleshooting or development purposes is known as
systems analysis. It is used in information technology, where computer-based systems require
specific analysis based on their structure and design. System analysis is a methodical approach to
technical decision- making. It is used for trade-off analysis and includes modeling and
simulation, cost analysis, technical risk analysis, and effectiveness analysis.
Requirements determination involves studying the existing system and gathering details to find
out what are the requirements, how it works, and where improvements should be made. There
are four types of Requirement Determination steps:

To-Let: Find Your house 11

 ● Interviewing individuals
● Interviewing groups
● Observing works
● Business documents
After Completed the planning part we should start the analysis of our system. To complete the
analysis, we must complete the following five steps:
 Creating interview & observation table
 Related work review
 Contemporary methods(JAD,CASE tools,prototypes)
 Risk analysis(table and matrix)

1.2. Interview Outline

Interview Outline

Interviewee: Zeneya Sharmin Interviewer: Bishozit Chandra

Das

Location/Medium: +8801307104947  Appointment Date:24th Oct 2022

Start Time: 3PM
End time: 4PM

Objectives: Reminder:
 To find out the key functionalities Team Mate
 To find out unique feature

Agenda: Approximate Time:

Introduction 1 minute
Motivation of this project 2 minutes
Overview of Interview
 Topic to be Covered 1 minutes
 Permission to be Record
Topic 1: Real life-related question
4 minutes
 Why is your project important in real life?
 What is the motivation for this project?
Topic 2: Programming / Development related question
6 minutes
 What is the used language? And why did you use

To-Let: Find Your house 12

 this? 
 Briefly discuss Dataset/Targeted audience.
 What resources do you need to develop this?
Topic 3: 5 minutes
Summary of the major finding (Overall project discussed).
closing

Typical Interview guide

1.3 Observation Table

Questions Notes

Question 1: Answer:
Have you used a location / Yes. I used a GPS tracking system.
GPS Tracking System? If Observation:
so, how often?
they Seemed anxious, and may be overestimating the area of
knowledge.

Question 2: Answer:
What problems did you face Rapid technology advancement, constantly increasing
while developing? demands, time limitations, limited infrastructure/resources,
and conflicts with software testing teams.
Observation: 
Confident enough, Needs to introduced app.

2. RELATED WORK:
Now, we are going to discuss existing mobile banking and their contribution and limitation.
Name of Website Contribution Limitation
[Link]:   Buying and selling  More Complex to use
flat, Apartments and  Backdated
office. information.
 The location is not  High maintenance and
that correct. costly.
Rental home [Link]:  Works for sale and  Commonly Fraud
rent activity
 Do not show the

To-Let: Find Your house 13

 rating.
 Backdated updates
 Buy and sell products.  Management System
[Link]:  Flats, Apartments and is not good
office area  Take a lot of time to
execute any feature

3. CONTEMPORARY METHOD
Joint Application Development in short JAD is the process which is used to design and develop
computer based system/solutions. It collects requirements side by side as per business needs
while developing new information systems for a company that means JAD involves the client or
end-users in designing and development process. Since client is involved throughout the
development process it leads to faster development times and greater client satisfaction.

3.1 Prototype

To-Let: Find Your house 14

 Figure 4: Figma prototype of To-Let Find your house

4. RISK ANALYSIS
Project Risk identification is the most important process in the Risk Management Planning. Risk
Identification determines which risks might affect the project and documents their
characteristics. We have identified some major risk to develop our system

I Risk Risk Root Cause  Risk Risk Risk Risk

D Categor Trigger/ Ratin Response Owner
y  Warnings g 

1 Data Very Intruders, 1. Users' 90% 1. Design a System

Integrity  High Huge number information sustainable Analyst
of users, can be architecture
Operation stolen.  for
failure due to  2. authenticatio
server  Unauthoriz n in every
ed transaction. 
transactions
make take
place

2 Data Very Devices, 1. 100% 1. Encryption System

Security  High intruders, Unauthoriz [Link] Analyst 
Low-security ed access hy technique
rules and may change 3. 2-step
mechanism users' authenticatio
information n 
and
transactions 

3 Data Very Device 1. Unstable 100%  1. Roll back System

atomicity  High  failures information for Analyst
during in the unsuccessful
transactions, database. 2. attempts 
Unsuccessful No changes 2. Tracking
attempts after each action
while transaction  performed by
transaction or users
response
from server
goes down in

To-Let: Find Your house 15

 the middle of
transaction 

4 Transaction Medium Frequent 1. fewer 50% 1. Reduce the Client

fees  transactions  users will transaction
be fee and
interested if display ads.
the (Pro version
transaction removes ad) 
fee is too
much
higher 

5 Number of Medium Server's 1. A server 60% 1. Develop Project

users  computation may not the system in Manag
power serve all a scalable er
the requests way to serve
as a result it the users
may go when there is
down  a much
higher num
of users 

6 Number of Medium Less agent 1. General 50% 1. Increase Project

agents  point  users could the number Manag
be in of agents all er
trouble over the
searching country by
for serving better
Withdrawal functionalitie
points  s 
2. Design a
faster, nice,
and user-
friendly User
interface 
3. Develop
fragments for
each
transaction’s
information 
[Link] ads for
Agent
application 

To-Let: Find Your house 16

 7 Compatibiliti Low 1. Forward 1. All 40% 1. Project
es  compatibiliti devices Developing Manag
es  may not the system er
[Link] support the with
compatibiliti application maintaining
es  on their forward and
mobile backward
devices  compatibilitie
s 

8 Durability  High [Link] history 1. once a 100% 1. Any System

of transaction transaction changes from Analyst
is the
committed, transaction
it will must be
remain in stored
the system permanently.
even if If the system
there’s a tells the user
system that the
crash transaction
otherwise has
there is a succeeded,
chance of the
losing transaction
durability.  must have
succeeded. 

[Link] PROBABILITY & IMPACT

We have performed the qualitative risk analysis by PI matrix, If we summarize it should look
like the graphical form of the table below:

Rank Score Measurement

1 0 - 0.3 Low

2 0.4 - 0.5 Medium

To-Let: Find Your house 17

 3 0.6 - 1 High 

Risk Probability Impact P*I Rank

Data Integrity 1 0.2 0.2 5

Data Security 0.2 0.8 0.16 6

Data atomicity 1 0.9 0.9 1

Transaction fees 0.3 0.9 0.27 4

Number of Client  1 0.3 0.3 2

Number of owners 0.7 0.4 0.28 3

Compatibilities  0.7 0.2 0.14 7

This is not the standard, we developed it for our own project. So, the result with others may not
be same as above that are showed in the implementation part. After analyzing these with our
project we found that more than 90% results.
6. DISCUSSION AND CONCLUSION
The development of a system called To-Let Find Your House is the main goal of our project. In
our project, we aim to create a system that is strong enough to address security issues. There are
more hazards, but we have identified all of the critical ones. We assessed each of them through
an interview and, following analysis, discovered the risk probabilities and impact. Other
restrictions that are not included in the risk probability finding and impact are still in place. Due
to how difficult it is to create an interview outline, there were certain difficulties encountered
when establishing requirements through an interview. It takes a lot of time and requires a lot of
critical thinking. The stated problem's objective and aim were successfully accomplished using
objective mapping.

[Link]
[Link]
[Link]
Figma Online Available: [Link]
node-id=220%3A2&scaling=scale-down&page-id=0%3A1&starting-point-node-id=11%3A6

To-Let: Find Your house 18

CHAPTER 3: DESIGN
1. INTRODUCTION

The architecture is established during the design phase. This phase takes the requirement
document delivered by the requirement phase and maps it into an architecture. The architecture
specifies the components, as well as their interfaces and behavior. The architecture is the
deliverable design document. The design document outlines a strategy for putting the
requirements into action.
Details are established for computer programming languages and environments, machines,
packages, application architecture, distributed architecture layering, memory size, platform,
algorithms, data structures, global type definitions, interfaces, and many other engineering
details.
Phases of designing are:
 Use Case Diagram
 Data Flow Diagram
 ER Diagram
 Creating Prototype

2. RELATED WORK
Now, we studied some websites for this kind of rented flat, apartment, etc. Here are some of
there limitation and Contribution:

Name of Website Contribution Limitation

[Link]:   Buying and selling  More Complex to use
flat, Apartments and  Backdated
office. information.
 The location is not  High maintenance and
that correct. costly.
Rental home [Link]:  Works for sale and  Commonly Fraud
rent activity
 Do not show the
rating.
 Backdated updates
 Buy and sell products.  Management System
[Link]:  Flats, Apartments and is not good
office area  Take a lot of time to
execute any feature
3. METHODOLOGY (FLOW CHART)
Here include our project working methodology:

To-Let: Find Your house 19

 Figure 5: Methodology of To-Let Find your house

4. DETAILED WORKING PLAN

Task Time Responsible Person

Identify the problem & define its scope & perform 2 Zeneya Sharmin &
analysis (feasibility, requirement). Proposed model for the weeks Bishozit Chandra das
development.

Performance analysis on the functions and whether it is 1.5 Zeneya Sharmin

achievable or not weeks

Finalize the development model & prepare the Gantt chart 2 Bishoizit Chandra das
for overall development weeks

Create DFD, E-R diagram, flowchart, Decision tree & 2 Zeneya Sharmin
decision table for project weeks

Describe UML diagrams, draw all as per the system  1.5 Bishoizit Chandra das
weeks

To-Let: Find Your house 20

 Plan the overall sequence (final) to perform all the tasks 2 Zeneya Sharmin &
and tie limits of each module. weeks Bishoizit Chandra das

5. COMPONENTS OF UML USE CASE DIAGRAM

To draw a use case diagram of a system we have to use some symbols and notations are:
a) Use cases: Horizontally shaped ovals that represent the different uses that a user might have.

Use Case:
 Log in
 Set profile
 See post
 Add post
b) Actors: Stick figures that represent the people actually employing the use cases.
Actor:
 User
 House owner
 House Finder
 Admin

c) Communication Links: A line between actors and use cases. In complex diagrams, it is
important to know which actors are associated with which use cases.

 Association: Association link is shown by connecting an actor to a use case by a solid

link.

To-Let: Find Your house 21

  Generalization: Generalization is shown by connecting an actor to a use case by a solid
arrow link. A taxonomical relationship between a general use case and a more specific
use case.

 Include: Include Relationship between a base use case and an inclusion use case,
specifying how the behavior of the inclusion use case can be inserted into the behavior
defined for the base use case.
Include:
 Registration
 Select valid post
 Block User
 Unblock User

 Extend: Relationship between the extension use case and the base use case. Specify how
the behavior of the extension use case can be inserted into the behavior defined for the
base use case.
Extend:
 Invalid username or pass

d) System boundary boxes: A box that sets a system scope to use cases. All use cases outside the
box would be considered outside the scope of that system. For example, Psycho Killer is outside
the scope of occupations in the chainsaw example found below.

e) Packages: A UML shape that allows you to put different elements into groups. Just as with
component diagrams, these groupings are represented as file folders.

To-Let: Find Your house 22

6. USE CASE
Use Case Diagram captures the system’s functionality and requirements by using actors and use
cases. Use Cases model the services, tasks, function that a system needs to perform. Use cases
represent high-level functionalities and how a user will handle the system. Use-cases are the core
concepts of Unified Modelling language modeling.

Figure 6: Use Case of To-Let Find your house

7. DATA FLOW DIAGRAM
A data flow diagram depicts the flow of information through a process or system. It includes data
inputs and outputs, data stores, and the various subprocesses through which the data moves.
DFDs are created by describing various entities and their relationships using standardized
symbols and notation. Data flow diagrams graphically represent systems and processes that
would be difficult to describe in text.
7.1 Level 0:

To-Let: Find Your house 23

 Figure 7: Level 0 DFD of To-Let Find your house

7.2 Level 1:

To-Let: Find Your house 24

 Figure 8: Level 1 DFD of To-Let Find your house

8. ER DIAGRAM:

To-Let: Find Your house 25

 Figure 9: ER Diagram To-Let Find your house
9. UML SEQUENCE DIAGRAM
At first the user needs to signup or login to his/her profile. Then s/he can see the to-lets and filter
the location. If someone wants to post for a house s/he can do it from the homepage. If the user
chooses an apartment s/he can book this right now.

To-Let: Find Your house 26

 Figure 10: UML Sequence Diagram of To-Let Find your house

10. PROTOTYPE

To-Let: Find Your house 27

 Figure 11: Figma prototype of To-Let Find your house

11. DISCUSSION AND CONCLUSION

The development of a system called To-Let Find Your House is the main goal of our project. In
our project, we aim to create a system that is strong enough to address security issues. There are
more hazards, but we have identified all of the critical ones. We assessed each of them through
an interview and, following analysis, discovered the risk probabilities and impact. Other
restrictions that are not included in the risk probability finding and impact are still in place. Due
to how difficult it is to create an interview outline, there were certain difficulties encountered
when establishing requirements through an interview. It takes a lot of time and requires a lot of
critical thinking. The stated problem's objective and aim were successfully accomplished using
objective mapping.

12. REFERENCES
[Link]
[Link]

To-Let: Find Your house 28

[Link]
[Link]
Figma Online Available: [Link]
node-id=220%3A2&scaling=scale-down&page-id=0%3A1&starting-point-node-id=11%3A6

CHAPTER 4: IMPLEMENTATION
[Link]
The architecture is established during the design phase. This phase takes the requirement
document delivered by the requirement phase and maps it into an architecture. The architecture
specifies the components, as well as their interfaces and behavior. The architecture is the
deliverable design document. The design document outlines a strategy for putting the
requirements into action.

To-Let: Find Your house 29

Details are established for computer programming languages and environments, machines,
packages, application architecture, distributed architecture layering, memory size, platform,
algorithms, data structures, global type definitions, interfaces, and many other engineering
details.

Phases of designing are:

 Logical Database
 Physical Database
 Data access method

2. LOGICAL DATABASE

Figure 12: Logical Database

2.1 Renter/Owner:

Attribute Datatype Key

Post creator Char(500), int, string Primary

Flat Retailer Char(500), int, string Primary

Real Estate developer Char(500) int, string Foreign

Gender Char Secondary

Phone no int(11) Primary

To-Let: Find Your house 30

 Name Char Secondary

Date of Birth Int(8)

NID Int Primary

2.2 Admin Panel:

Attribute Datatype Key

Post creator Char(500), int, string Primary

Gender Char Secondary

Phone no int(11) Primary

Name Char Secondary

NID Int Primary

Location String(20)

[Link] DATABASE
3.1 User:

Name Mobile No NID Gende DoB Passwor Location Profile

r d type
[Link] 123052525 142553325 F 01.02.199 ioiiu Mirpur Renter
5 5 9
2. 125563253 225555248 M 12.07.200 Hnj8ghv Dhanmond Owner
Bishozit 5 5 0 i
3. Sudip 125525522 778855965 M 17.05.199 Bht765 Uttara Retaile
4 4 9 r
[Link] 145758961 725412222 M 26.11.200 Nhghc7 Tangi Agenc
4 2 0 y
[Link] 145625588 245452422 F 03.04.199 njhjK0 Kajipara Renter
a 5 3 7

To-Let: Find Your house 31

3.2 Admin

Name Admin ID Password

Admin.1 A123 Sfns545
Admin.2 B124 Fnsdkcsi5
Admin.3 C324 Dn8356f
3.3 Security

Authentication Type IP Address MAC Address Status

System [Link] [Link] Normal
System [Link] [Link] Normal

4. UML SEQUENCE DIAGRAM

To-Let: Find Your house 32

 Figure 13: UML Sequence Diagram of To-Let Find your house
At first the user needs to signup or login to his/her profile. Then s/he can see the to-lets and filter
the location. If someone wants to post for a house s/he can do it from the homepage. If the user
chooses an apartment s/he can book this right now.

5. DISCUSSION & CONCLUSION

Our project focuses on developing a system which is To-let: Find your house. Through our
project we are trying to design a system which is powerful enough in the security concerns. After
completing this lab class, we gain some basic idea of “Logical Database Design” and “Physical
Database Design”. In this lab report we tried to complete “Sequence Diagram” by using Online
Visual Paradigm app. We have learned how to use it and developing it for our project design
purpose. Which increases our knowledge. When we implement our lab report, we faced some
problem like we can’t understand our desire goal but after we arrange a meeting and discussing
our project design goal and tried to complete the lab report without errors. After completing the
sequence diagram for our project, its look like a real-life view of our project that how user and
admin could interact with the To-let system.
6. REFERENCES
[Link]
[Link]
[Link]
[Link]

To-Let: Find Your house 33

[Link] integration- and-
functional-testing/
Figma Online Available: [Link]
node-id=220%3A2&scaling=scale-down&page-id=0%3A1&starting-point-node-id=11%3A6

CHAPTER 5: IMPLEMENTATION &

MAINTENANCE
[Link]
Implementation One of the most important phases in the development of information system
software is
the implementation phase. The automated system/application or other IT solution is moved from
development to production status during the Implementation Phase.
The implementation process varies depending on the project and the IT solution, and it may be
synonymous with installation, deployment, rollout, or go-live. During the Implementation Phase,

To-Let: Find Your house 34

if necessary, data conversion, phased implementation, and training for using, operating, and
maintaining the system are completed. During the Implementation Phase, the final system must
be certified and accredited for use in the production environment in terms of system security. In
this phase we divide the activity into these sections:
 Form design for different types of function accessing.
 ii. Implementation

2. FORM DESIGN
2.1 Registration:

Name Enter your name

E-mail Enter your email

Phone Enter your Phone Number

NID: Enter your NID

Address Enter your Address

What do you want? Rent a house/ Own an apartment

Password Enter a Password

Confirm password Confirm your password

II.2 Login:

E-mail Enter your email

Password Enter your Password

2.3 Home Page:

 House for rent at ….

 House for rent at ….
 House for rent at ….

2.4 Profile:

To-Let: Find Your house 35

 Name Enter your name

E-mail Enter your email

Phone Enter your Phone Number

Address Enter your Address

NID: Enter your NID

What do you want? Rent a house/ Own an apartment

Want to edit?

2.5 Add a post:

 Create a post…
 Caption 
 Add photos/videos
 Post

3. CODING PART
3.1 For USSD
Language: Java

3.2 For web user

Front end Design: HTML, CSS, Bootstrap
Backend Language: Python, Django
Database: Firebase

3.3 For Mobile Apps

Frontend Design: Flutter
Language: Dart
Backend: PHP
Database:Firebase
Platform: Android Studio

To-Let: Find Your house 36

4. ALGORITHM

Admin Panel:
Step 1: Login Account
Step 2: If (See user all post) then,
Approve post
If Else: Rules Break
Delete Post
If Else: Again Rules Break
User Activity Block
If Else: Fee Time Later
User Activity Unblock
Step 3: Else: go to Step 1
Step 4: Exit

Create Post:
Step 1: Login Account,
Step 2: If (Attempts <1) then,
Create Post
Post successfully done
If Else: Again post
Else: Attempts ++ & go to Step 1
Step 3: Else: go to Step 2
Step 4: Exit

Delete Post:
Step 1: Login Account
Step 2: If (find the post) then,
Delete post
Step 3: Else: go to Step 1
Step 4: Exit

5. TESTING

To-Let: Find Your house 37

5.1 Testing Methods
● Unit testing
● Integration testing
● System testing
● User acceptance testing
● White Board Testing

5.2 Test Case

We will use alpha, beta & black box testing for our project.
User end:
Name (25)
Password: (12)
Phone: (11 digits)
Email: only Gmail, yahoo, outlook accepted

Alpha testing test case:

Input Expected output

Name: 1234zeneya Wrong input please write a valid name

Name: Zeneya correct

Name: zeneya123 Wrong input please write a valid name

password: RT$RT wrong

Password: Rr12@ Correct

Password: 123456 wrong

Phone: 01010101010 wrong

Phone: 013071*** wrong

Phone: 01307104947 Correct

Phone: 12345535385 Wrong 

To-Let: Find Your house 38

 NID:123…23 Wrong

NID:5624786325 Correct

Beta testing test case:

Input Expected output

Name: 1234zeneya Wrong input please write a valid name

Name: Zeneya correct

Name: zeneya123 Wrong input please write a valid name

password: RT$RT wrong

Password: Rr12@ Correct

Password: 123456 wrong

Phone: 013071*** wrong

Phone: 01307104947 Correct

Phone: 12345535385 Wrong 

Black box testing test case:

Input Expected output

Name: 1234zeneya Wrong input please write a valid name

To-Let: Find Your house 39

 Name: Zeneya correct

Name: zeneya123 Wrong input please write a valid name

password: RT$RT wrong

Password: Rr12@ Correct

Phone: 01307104947 Correct

Phone: 12345535385 Wrong 

6. INSTALLATION
It’s the organizational process of changing over from the current information system to a new
one. There are four typically methods for installation:
 Direct Installation
 Parallel Installation
 Single-location Installation
 Phased Installation
Among these four installation strategies, we will use for our system is Direct Installation.
Using Direct Installation:
a) Involves the Old system being completely dropped and the new system being completed
installed at the same time.
b) Need to make sure the new system is completely functional and operational.
c) This conversion method is only used when it is not feasible to operate separate systems at the
same time.
d) Any data and training must be done before the installation.
Along with these,
System admin will provide a generated apk file. Users need to download it from google play
store and install it directly.

7. DOCUMENTING THE SYSTEM

7.1 System documentation
System documentation will be written in Latex. This document will contain soft copy and hard
copy. In this document there should be a graph, chart, table, uml diagram, data flow diagram, use
case diagram, algorithm, app inspection methods and so on.

To-Let: Find Your house 40

Admin panel:
 User data will document with excel file
 All the data will document by a soft copy of that particular project's FTP server

7.2 User documentation

This will be a user manual. It will be written in Latex also in poster design. It should contain how
to use the app properly. It will be a soft and hard copy.
User panel/ manual:
 Document by soft copy.
 How to install 
 How to log in/register
 How to post for a rent

8. TRAINING
In this phase we divide the training activity into these categories:
 Potential training topics
 Use of the system
 General computer concepts
 Information system concepts
 No leakage of data
 General computer concepts like c, java, and database coding
 Information system concepts like encryption algorithms
 Organizational concepts like managing the data, post, authenticity, and integrity.
 Organizational concepts
 System management
 System installation
Important issue for this project and management
■ Malicious software (malware): includes Trojan horses, worms, viruses, and other kinds.
■ External sources of threats include laptop theft, system penetration, and denial of service.

Close down:
 Evaluate the team.
 Reassign members to other projects.
 Notify all affected parties that the development project is ending and that you are
switching to operation and maintenance mode.
 Conduct post-project reviews.

To-Let: Find Your house 41

  Closeout customer contracts.
 Formal signoff
9. SUPPORT
In this phase we divide the support issues into these categories:
 User questions and problems
 Recovery and backup
 Disaster recovery
 PC maintenance
 Writing newsletters
 Setting up user groups

10. DISCUSSION & CONCLUSION

Our project focuses on developing a system which is To-let: find your house. Through our
project we are trying to design a system which is powerful enough in the security concerns. After
completing this lab class, we gain some basic idea of form design for different types of function
accessing and implementation parts. In this lab report we tried to complete form design for
different types of function accessing and implementation parts with all details. We have learned
how to use it and developing it for our project design purpose. Which increases our knowledge.
When we implement our lab report, we faced some problem like we can’t understand our desire
goal but after we arrange a meeting and discussing our project design goal and tried to complete
the lab report without errors. After completing the form design and implementation parts for our
project, its look like a real-life view of our project that how tester, user and admin interact with
the To-Let system.

11. REFERENCES
[Link]
[Link]
[Link]
Figma Online Available: [Link]
id=220%3A2&scaling=scale-down&page-id=0%3A1&starting-point-node-id=11%3A6

To-Let: Find Your house 42

CHAPTER 6: CONCLUSION &
FUTURE WORK
1 . FINAL CONCLUSION

We knew that our project is going to be tough as we must innovate an effective system. We will
have to give a lot of to complete this project. Planning helped us to decide what that contribution
should be and how to achieve it. Also helped us to be accountable for what we do and decide
how best to use our resources (people, time, money, information, equipment) so that they make
the most significant contribution to achieving our goal. Planning plays the basis for us to assess
and evaluate our achievements effectively. Our project focuses on developing a system which is
To-Let: Find your house. Through our project we are trying to design a system which is powerful
enough in the security concerns. There are other risks and we have successfully found out all the
necessary ones. Evaluated each one of them by the interview and after analyzing we found the
risk probabilities and impact. We have designed whole system using different diagrams like
DFD, Use Case, ER etc. [1][2][3]
After lot of hard work, we have achieved the lab objective throughout the whole project.

2. LIMITATIONS
It is not implemented yet that’s why limitations are not clear enough. Although we have done
analysis on some limitations that,
● If we cannot make it scalable then it will be not efficient for users.
● Security mechanism is theoretically developed and not implemented etc
.
3. FUTURE PLAN
● To utilize it for selling and other feature included.
● Artificial intelligence (AI) integrated with the system to provide security by detecting specially
the frauds who uses the this project to steal the renters.
● Mobile malware, insecure Wi-Fi networks, device ID vulnerability are the common
problems in this kind of website and android development. So, we can find out solution for these
problems.
4. REFERENCES
[Link]
[Link]
[Link]

To-Let: Find Your house 43