Prepy Solutions to

“Happy” Problems
DESIGNING AN INFORMATION SYSTEM FOR HAPPY REALTY
LTD.
Presented by
Princy Johnson
Ritika Tanwar
Esha Karim, 300347239
Prabhnoor Gujral
Yubin Fan
Introduction
Project Background
Happy Realty Preppy Solutions (HRC) currently has 5 agents working for them and looking to
add more agents as it continues to grow.
The task is to design a database system for HRC that will have the following features:
Registering new agents
Registering new properties
Creating commission slips for agents
Creating sales receipts for clients
Creating list of active/sold properties
Generating sales report
Generating agent performance
PREPY Solutions Background
Operating in the system design industry for 10 years.
A track record of success with 4.8/5 customer rating on Google reviews.
Preppy Solutions leads have 35 years of cumulative IT experience.
Major clients include Amazon, Skip the dishes, Sephora, Shoppers, Walmart, and RE/MAX Realty Group.
The Team

Prabhnoor Ritika Esha Princy Yubin

Fin. Admin GM TO Sys. Admin Team Lead
 Assumptions
All the stakeholders must participate in the project meetings and must have a clear-cut idea in the quality
aspect of the product.
We will be satisfying the IT industry rules when carrying out the Clients operations.
All the documents related to Past transactions of the Happy Realty Preppy Solutions have been correctly
valued and communicated to the team of PREPY.
All the details regarding the commission rate and agent rates are properly informed and details regarding
agents associated with the client Preppy Solutions are also informed.
Data related to the different property types that the client Preppy Solutions deals with are informed.
There is no risk in transferring vital information from clients to the Preppy Solutions. Fraud related to client
information is properly mitigated and solved. 
It is assumed the issues related to client infrastructure are being resolved.
No other third-party services are done by the Preppy Solutions.  
Key Advantages
The proposed system has the following advantages
System that allows users to buy and sell properties quickly and easily.
Register and upload properties easily.
The system is designed to give the information accurately and in a presentable form to the
user.
Deliverables
A. Study of Requirement and current system analysis (Oct 8th, 2021)
B. Design of the system
C. Developing core software
D. Developing auxiliary modules
E. Migration of Historical Data
F. Test Cases and tweaks
G. Training, Implementation and Handover
Study of requirement and current system
analysis
To ensure that we build a system to the satisfaction of the client, it is important that we observe
and learn the current system in place and the requirements from the users. Hence, we will
spend three weeks in focus group interviews, one to one questionnaire and face to face
conversations and then processing the available information for our use in designing the new
transaction processing system.
Task Code: SoR (Study of Requirement)
Time needed: 21 days
Predecessor: none
Design of the system
We will develop the design of the system with the available information, assumptions, and
requirements. To develop this design, we will use our own expertise with only final feedback
from the experts working with the clients. Upon their satisfaction, we will finalize the design and
go onto developing the software accordingly. This phase is expected to take a maximum of seven
days.
Task Code: DoS (Design of the System)
Time needed: 7 days
Predecessor: SoR
Developing core software
After vetting the design from the client, we will move onto developing the core software. The
core software in its nature will be a functional database of the property, agents, and transaction
information. Developing the core software with pre-coded templates and functions should take
at most two weeks.
Task Code: DoC (Development of Core)
Time Needed: 14 days
Predecessor: DoS
Developing auxiliary modules
While development of auxiliary modules is not fully dependent on the development of core software, to
make sure that the modules are working perfectly with the core software, we need to develop them at
least simultaneously with the core. The reason that these features are developed separately from the
core software is to utilize the “divide and conquer” approach of software development. Including all
these features in the core software would make the software overly complex and make debugging a
nightmare if not an impossible task. The modules that must be developed for includes but are not
limited to:
 Sales transaction slip module
 Commission slip module
 Monthly profit report module
 Monthly sales transaction report module
 Active listings module
 Sold listings module
 Agent performance module
Developing auxiliary modules
While development of auxiliary modules is not fully dependent on the development of core software, to make sure that
the modules are working perfectly with the core software, we need to develop them at least simultaneously with the
core. The reason that these features are developed separately from the core software is to utilize the “divide and
conquer” approach of software development. Including all these features in the core software would make the software
overly complex and make debugging a nightmare if not an impossible task. The modules that must be developed for
includes but are not limited to:
 Sales transaction slip module
 Commission slip module
 Monthly profit report module
 Monthly sales transaction report module
 Active listings module
 Sold listings module
 Agent performance module
Task Code: DoM (Development of Modules)
Time needed: 21 days
Predecessor: DoS (somewhat dependent on DoC, should run simultaneously).
Migration of historical data
After developing the software infrastructure for the transaction processing system, we will
introduce historical data to the system and start comparing the results of the old system and the
new system. We will focus on two major issues here: if the historical data replicates historical
results and if it does not is it due to the error of the historical system or the new one. Since
Happy realty now has only 5 agents and around 10 running listings, this phase should take
around 1 week at most. However, we will keep the cushion time of 2 weeks to make sure that
we account for any mismatch and redevelopment of software infrastructure (if needed).
Task Code: MoH (Migration of Historical data)
Time Needed: 14 Days
Predecessor: DoM and DoC
Test cases and tweaks
In this phase we will enter data simultaneously in both systems and see if they produce identical
results. We will also use newly developed modules to provide the reports not available under
the old system. We will also check their validity and tweak the software infrastructure as
needed. 2 weeks of time will be needed to ensure these checks and tweaks.
Task Code: TCT (Test Cases and Tweaks)
Time needed: 14 days
Predecessor: MoH
Test cases and tweaks
In this phase we will enter data simultaneously in both systems and see if they produce identical
results. We will also use newly developed modules to provide the reports not available under
the old system. We will also check their validity and tweak the software infrastructure as
needed. 2 weeks of time will be needed to ensure these checks and tweaks.
Task Code: TCT (Test Cases and Tweaks)
Time needed: 14 days
Predecessor: MoH
Training, implementation and handover
In this phase we will train Happy Realty employees on efficient use of the new system, creation
of reports and other features. We will also train system administrators of Happy Realty in
maintaining the new system and troubleshooting. Afterwards, it is expected that the employees
will start using the software and get used to the new infrastructure. With their regular use of the
system, new questions and requests for small tweaks may arise which we will try to solve. This
phase is supposed to take 3 weeks including one day where we will officially hand over the
system-to-system administrators of the client. However, we will remain accessible for periodic
service and maintenance and developing additional modules when required (at additional
expenses).
Task Code: T&I (Training and Implementation)
Time Needed: 21 days
Predecessor: TCT
Project GANTT chart
 Project PERT chart
DOM 3

7 2

SOR 3 DOS 1 MOH 2 T&T 3 TCT 2

3 3 4 4 9 9 14 14 11 11

DOC 2

6 7

All values in week(s)

 Pricing
List of tasks Completion time Price
Study of Requirement 3 weeks $ 4500
(SOR) from which $3000 we spent on human resource management.
the other $1500 spent on trial services.
Design of the System (DOS) 1 weeks $ 2000
$1000 on labour cost
$2000on fixed cost which was used while making the design.
Developing core Software 2 weeks $ 3000
(DOS) $2000 on labour cost.
$1000 on fixed cost 
Developing auxiliary 3 weeks $ 4500
modules (DAM) $1000 on labour cost 
$2000 fixed cost
$1500 variable cost 
Migration of Historical 2 weeks $ 3000
Data (MOH) $ 1000 labour cost 
$2000 on variable cost 
Test cases and tweaks 2 weeks $ 3000
(TCT) $1000 on labour cost 
$2000 on fixed cost
Training & Implementation 3 weeks $ 4500
and Handover (T&I) $1500 labour cost 
$3000 cost for final handling project.
Payment schedule
Instalments Payment date Payment Amount

1) 10 % Deposit 8 Octobers 2021 $2,495

2) Mid Payment 4 January 2022 $11,228

3) Final Instalment 1 March 2022 $11,227

Interfaces
Title screen
Role Selection
Agent tasks
Financial administrator tasks
HR tasks
Sales controller tasks
System administrator tasks
Commission slip module
Commission slip sample
Property registration module
Property registration confirmation
Sales receipt module
Sales receipt sample
Sales record module (agents)
Sales record module (fin. admins)
Add agent module (HR)
Agent performance module (HR)
Agent performance module report (HR)
Add user module
List users module
Implementation and
Maintenance
Implementation plan
Implementing new system
Monitoring risk during the implementation
UAT- (User Acceptance Testing)
Checking security
Measuring outcomes
Backup plan
Preppy Solutions will be backing up important files and data that comes under the priority section of the
client.
The priority section for happy Realtors is contract with their client, financial records and payroll
information, new agent information, sales transactions, and historical data such as sold customer listings,
customer emails and transaction outputs like Commission slips weekly monthly reports.
The backup of the Preppy Solutions files will be done daily at the end of the day (automated backup
program) and the Preppy Solutions emails will be backed up weekly and all the data will be backed up
monthly.
The older project data will be stored on DVDs and CDs for keeping the file safer and it won't be affecting
the daily backup.
The hardware used for backing up the Preppy Solutions data will be network attached storage as primary
back up, and external hard disk will be the secondary backup. the hardware is selected based on the size of
the Preppy Solutions, as our client happy realtor is a small Preppy Solutions
Backup plan (cont.)
An information asset recovery plan has been created and will be discussed with the management team
of the client regarding the same.
The organization will take about 4 to 12 hours to recover information back in case of any disaster.
Our Preppy Solutions will be responsible for the backup for the first six months after the project and
regular tests of backup will be done in that six months.
For security services the Preppy Solutions has added antivirus and anti-malware in the system. The
Preppy Solutions will also be educating the client personnel regarding this, and it is required that the
client needs to establish the responsibility of software security to the IT team of the Preppy Solutions
which makes it easier for our organisation.
Preppy Solutions will be assisting with the security services for the first six months
The client must follow the procedures that the Preppy Solutions has set up for them in backing up and
security services of their information and files.
Conclusion
Project aims/objectives & reflections
Yubin: My overall feeling for this project is challenging because as a business student I have
never done anything in the IT field and as a leader of this team the uncertainty of how to do the
project in the beginning of the semester did stress me out a little bit. None of us was confident
in our leadership skill, but my team voted myself to be the leader. It was an honor to have the
trust from my team since the beginning of the project. And I have learned and started to build
confidence in my leadership skills. As for the project, things started to be clearer as we figured
out what elements are included in the statement of work from the mini assignment. In
conclusion, this project is challenging but I have had fun doing it.
Ritika: This project gives the brief guidance towards the system analysis and design, how to
develop the system according to the clients need and demand. My team did a great job while
preparing services for the Happy Reality company, and we also face many problems and
challenges while doing the work but that's totally worthwhile as we finally come up with a great
product. At last, I can say that I really enjoyed the teamwork.
Project aims/objectives & reflections
Princy: This project gives me an idea about the course CSIS. It was difficult for me to understand the
concept of CSIS as I only had a background of business. It was difficult in the starting stage of the
project as none of our team members really had a computer background but still when we started
working together, we tried to understand the concept and even asked each other. All our team
members try to understand the concepts in their own ways and in the meetings that we conducted
we tried to share the ideas that we understood about the project. This was very helpful in
understanding what the other person's perspective was. Working with the team members of preppy
was very much fun as members were very open and approachable.
Esha: For me, the aim of this mini assignment was to understand the basics of system analysis and
design. We worked as a team to analyze what it means to create an interactive system for processing
data while meeting the requirements of the client. While we faced challenges, for example designing
the system and creating mock-ups, we also had fun while imagining ourselves in roles such as CEOs. I
really enjoyed working with my team PREPY Solutions under the guidance of our professor Victor
Choong.
Project aims/objectives & reflections
Prabhnoor: Overall this project helped me to understand about the system analysis and design.
It was a bit challenging as I have never known anything regarding CSIS before, but I am glad that
I get to work with such a great team. All the members have been helpful towards each other. I
think our team did a great job by creating this project. We all learned new things about
customers, analysing customers' needs and demands while developing a system.