This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Property Management System reduce the effort of manpower and only one person can
done 4 to 7 people work on one desk which is helpful for business in the sense of
profit and it also reduce the lot of paper work due to which retrieval of record is faster
than a manual system and secure
System also increases the efficiency of the business and all
operation of the business are perform in a accurate and secure mode. Admin of the
system can also view reports of business on daily , weekly, monthly and yearly bases.
11.USECASE DIAGRAM
12.SYSTEM USECASES
Page 9
System use cases of property management system are given below:
1. Registration
2. Login
2.1. Username password
2.2. Change password
3. Forgot Password
4. Manage Property
4.1. Add
4.2. Update
4.3. Delete
5. Search Buyer
6. Update Profile
7. Search Property
7.1. Type
7.2. Price
7.3. City
8. Booking Property
8.1. Payment
9. Logout
UC – 1
Use Case Name: Registration
Actors: Buyer, Seller
Stakeholder: Owner, Buyer, Seller
Pre-Condition: System user visits the web site of Property management system and fills the registration form.
Post-Condition: System database is update with new user record
Normal Flow: Actor Action System Response
1. User of system open property management website clicks registration form and fills the form for registration.
1. System saves the new record and show conformation message to user.
Page 10
Alternative Flow: 1. User visits the website and left mandatory field of form.1a. System shows errors in red lines and invoke user to fill that fields
1b. User provides invalid information in particular field system shows errors on particular field and invoke user to provide a valid information
1c.Username is already exist. System shows suggestions to user for selecting unique username
1d. System shows error message of “username is already exist”.
UC – 2
Use Case Name: Login
Actors: Buyer, Seller
Stakeholder: Owner, Buyer, Seller
Pre-Condition: User enter username and password
Post-Condition: System checks the validation of username or password and shows a welcome page to user.
Normal Flow: 1. User enter username and password
2. System validate the username or password and shift the user to home page of Property Management System
Alternative Flow: 1. User enter the wrong username or password1a. System shows errors in red lines and invoke user to enter the valid username or password
2. User is not registered2a. user is not registered system shows message to registered his account before login
UC – 2.2
Use Case Name: Change Password
Actors: Buyer, Seller, Admin
Page 11
Stakeholder: Owner, Buyer, Seller, Admin
Pre-Condition: User request for changing password
Post-Condition: System open change password form and require previous password for changing password
Normal Flow: 1. User select the option of change password2. System required a previous password for changing
3. user successfully change his password by entering new Passwords
Alternative Flow: 1. User enter wrong previous password1a. System shows errors in red lines and invoke user to enter the valid passwords
UC – 3
Use Case Name: Forgot Password
Actors: Buyer, Seller, Admin
Stakeholder: Owner, Buyer, Seller
Pre-Condition: User try to login to system but he forgot his password. User select a option of change password option.
Post-Condition: System tell some security questions for changing the password
Normal Flow: 1. User select a option of forgot password system new form2. User select his security question and validate his security
Alternative Flow: 1. User answer of security question is wrong1a. System shows error to enter the valid answer
1b. System shows option of alternative security and validation method
UC – 4
Use Case Name: Manage Property
Actors: Admin, Seller
Page 12
Stakeholder: Owner, Buyer, Seller
Pre-Condition: Admin select managing the property
Post-Condition: System record of property is updated
Normal Flow: 1. Admin of system and Seller of any particular property can add, update, delete the property record
Alternative Flow: 1. User of system face the error in manage property panel.1a. Adding a record of new property is not valid or not meet the requirement of the system
1b. Deletion or updating the property record is not allowed to user to delete or update it. User needs permission or rights for doing that.
UC – 5
Use Case Name: Search Buyer
Actors: Admin, Seller
Stakeholder: Owner, Buyer, Seller
Pre-Condition: Admin of system or seller of particular property search a buyer who is interested in buying property and buyer will be search by using ID or username.
Post-Condition: System fetch records related to query
Normal Flow: 1. User of system enter a query for searching buyer of system
2. Searching can be based on user Id or name and also according to range of buying
3. Buyer search on the base of cityAlternative Flow: 1. Entered query for search does not fetch any record.
1a. System shows message of invalid username, id
2. Record not found2a. Search based on user buying range in not available in records. System provided nearest suggestions of buying range of buyer.
UC – 6
Page 13
Use Case Name: Updated profile
Actors: Seller, Buyer
Stakeholder: Owner, Buyer, Seller, Admin
Pre-Condition: User of system select a update profile panel and updated his profile
Post-Condition: System fetches a user profile and save user updated record.
Normal Flow: 1. User of system select update record2. Updating his record3. Submitting the record4. System update the user record
Alternative Flow: 3. User record is not update2a. user dose not submit the form
2b. record is not update due to network session out.
UC – 7
Use Case Name: Search property
Actors: Admin, Buyer
Stakeholder: Owner, Buyer, Seller, Admin
Pre-Condition: User of the system search a property
Post-Condition: System fetches a record related to query.
Normal Flow: 1. User of system search a record on the base of its price, type,Location, city etc.
2. System fetch the recordAlternative Flow: 2. Record not found
2a. Search record is not available according to particular query. System suggest a nearest record related to query
UC – 8
Use Case Name: Booking Property
Page 14
Actors: Seller, Buyer
Stakeholder: Owner, Buyer, Seller, Admin
Pre-Condition: Buyer Select a property and booked that particular property
Post-Condition: System show a payment strategy
Normal Flow: 1. Buyer select a property2. Book that property3. Pay the amount through online banking4. Registered a property on buyer name
Alternative Flow: 3. Payment method is not verified2a. Buyer has no bank account
2b. Buyer has no enough money in his bank account
UC – 9
Use Case Name: Logout
Actors: Seller, Buyer, Admin
Stakeholder: Owner, Buyer, Seller, Admin
Pre-Condition: User of system logout from the system
Post-Condition: User account is closed
Normal Flow: 1. User select a logout session2. System logout the user
Alternative Flow: 1. User is not logout2a. user dose not click the logout button
2b. network session time out before logging out
13. DIAGRAMS
Page 15
13.1. CLASS DIAGRAMS
13.2. Context Diagram
13.3. DATA FLOW DIAGRAM (DFD)
11.3.1. CONTEXT LEVEL DFD
Page 16
11.3.2.DFD 0 LEVEL
14. FEASIBILITY REPORT
Page 17
Feasibility report is conduct on the base of time, cost, quality of a project and feasibility
report on Property Management System has following requirements
12.1 DESCRIPTION OF PROBLEM
IN manual system of Property Management time consumption is the major
problem and all records are saved in paper which is expensive and not secure for
business.
12.2 PROJECT DESCRIPTION
By building a system for Property Management it save the time of both buyer and
seller all record is computerized and saved on one primary location and in feasibility
report following key points are evaluated:
12.2.1 LEGAL REQUIREMENTS
Legal requirements of Property Management Systems are fulfill and
according to state law and web site is publish on a unique name and
having no illegal activity on it
12.2.2 OPERATIONAL REQUIREMENTS
For data acquisition, process, analysis and visualization of the all
Business activities are perform according to the user requirements and
For projects involved concern sustainable development and spatial
Is done and practitioners of local community is assigned for better
Productivity
12.2.3 ECONOMIC REQUIREMENTS
The cost of the software development and employing cost for specific
Work operation are within a range and project is not over budget and
Summary of all evaluated result is carried out using components of
SWOT analysis which is given below:
STRENGTHS WEAKNESSES
Page 18
Enthusiastic Creative Flexible Clam in a
crisis
No involvement of paperwork
Difficult to manage Incomplete details of
a particular property
OPPORTUNITIES
New challenges for
expending the area of
business
More autonomy
THREATS
no specific training unfamiliar with the
real business logics and operations
no managements experience
15. TESTING
Testing of the system will be done on the base of following approaches
Functionality Testing
Implementation Testing
Both of the approaches will be test on Black Box Technique in which following steps will
be done
Equivalence Class
Boundary values
Cause effect graphing
Pair-wise testing
State-based testing
Both approaches will be also test on White Box Technique in which following steps will be
done:
Control-flow testing
Data-flow testing
After testing results, reports are written in following documents