BSc CSIT Final Year Project Report on Hamro Krishi - NepalSirish Paudel
This is a copy of Final Year Project Report 2072 prepared by BSc CSIT students: Sirish Paudel, Sahaz Bhattarai, Jiwan Bhattarai and Suman Shreshta from New Summit College, Kathmandu, Nepal
This document describes an online job portal system project submitted to MicroRoot POC Technology Pvt. Ltd. The project includes an introduction, requirement analysis, system design, and conclusion. The system design section includes use case diagrams, sequence diagrams, data flow diagrams, and screenshots of the proposed user interfaces. The system is intended to allow job seekers to search and apply for jobs, and employers to post jobs. It will be developed using technologies like PHP, MySQL, Joomla, AJAX, and jQuery.
The document provides details about the author's internship project to create an Android application. The author completed their internship at the Sendai National College of Technology in Japan, under the supervision of Mr. Takatoshi Suenaga. The project involved learning to develop applications for the Android operating system. The author's first project was a "task killer" application, and their second project was an application to help foreign students learn Japanese phrases and translations. The author gained experience with Java programming, Android development tools, and aspects of Japanese culture during their internship.
This document provides an overview and summary of a job portal web application project developed by students over a summer training period. The project uses Java technologies like servlets, JSP, and Hibernate to allow job seekers to search and apply for jobs, and employers to post jobs. Key features include modules for job seekers to create profiles and browse listings, employers to post and manage listings, and an administrator to oversee operations. The document outlines the project purpose, objectives, scope, modules, and team roles in developing the different components.
vehicle management system project reportAshik Khan
The document provides a software requirements specification for a vehicle transportation management system called "Dhaka vehicle system". The system will allow administrators, approvers, transport staff and employees to manage vehicle categories, routes, and employee requests for bus or cab transportation.
The summary includes key functional requirements: administrators can manage users, employee data, vehicle categories and details, routes, and transportation requests. Approvers can view data and approve cab requests. Transport staff can view data and facilitate transportation. The system aims to reduce manual effort over the current system.
The document is a software requirements specification (SRS) for a student biometric identification system (BSI). It outlines the system's overall description, user characteristics, and specific functional and non-functional requirements. The BSI will use biometrics like fingerprints to automate student identification at entry/exit points. It will interface with a database and network to identify and log check-ins/outs. The SRS defines requirements for registration, an admin panel to manage users, and reporting of daily entries. It also specifies performance, security, and other non-functional needs.
Ignou MCA 4th semester mini project report. College admission system. This project is based on real working system of University seat allocation to affiliate colleges. College admission system provide seat allocation process for various UG PG programs for every academic session.
This is a project documentation titled: Online Railway Reservation System.
This documentation was submitted by me as my assignment in my 6th sem (2013) in APIIT SD INDIA, Panipat along with a full-fledged working system i.e., a website built using ASP.NET & SQL SERVER 2008
BSc CSIT Final Year Project Report on Hamro Krishi - NepalSirish Paudel
This is a copy of Final Year Project Report 2072 prepared by BSc CSIT students: Sirish Paudel, Sahaz Bhattarai, Jiwan Bhattarai and Suman Shreshta from New Summit College, Kathmandu, Nepal
This document describes an online job portal system project submitted to MicroRoot POC Technology Pvt. Ltd. The project includes an introduction, requirement analysis, system design, and conclusion. The system design section includes use case diagrams, sequence diagrams, data flow diagrams, and screenshots of the proposed user interfaces. The system is intended to allow job seekers to search and apply for jobs, and employers to post jobs. It will be developed using technologies like PHP, MySQL, Joomla, AJAX, and jQuery.
The document provides details about the author's internship project to create an Android application. The author completed their internship at the Sendai National College of Technology in Japan, under the supervision of Mr. Takatoshi Suenaga. The project involved learning to develop applications for the Android operating system. The author's first project was a "task killer" application, and their second project was an application to help foreign students learn Japanese phrases and translations. The author gained experience with Java programming, Android development tools, and aspects of Japanese culture during their internship.
This document provides an overview and summary of a job portal web application project developed by students over a summer training period. The project uses Java technologies like servlets, JSP, and Hibernate to allow job seekers to search and apply for jobs, and employers to post jobs. Key features include modules for job seekers to create profiles and browse listings, employers to post and manage listings, and an administrator to oversee operations. The document outlines the project purpose, objectives, scope, modules, and team roles in developing the different components.
vehicle management system project reportAshik Khan
The document provides a software requirements specification for a vehicle transportation management system called "Dhaka vehicle system". The system will allow administrators, approvers, transport staff and employees to manage vehicle categories, routes, and employee requests for bus or cab transportation.
The summary includes key functional requirements: administrators can manage users, employee data, vehicle categories and details, routes, and transportation requests. Approvers can view data and approve cab requests. Transport staff can view data and facilitate transportation. The system aims to reduce manual effort over the current system.
The document is a software requirements specification (SRS) for a student biometric identification system (BSI). It outlines the system's overall description, user characteristics, and specific functional and non-functional requirements. The BSI will use biometrics like fingerprints to automate student identification at entry/exit points. It will interface with a database and network to identify and log check-ins/outs. The SRS defines requirements for registration, an admin panel to manage users, and reporting of daily entries. It also specifies performance, security, and other non-functional needs.
Ignou MCA 4th semester mini project report. College admission system. This project is based on real working system of University seat allocation to affiliate colleges. College admission system provide seat allocation process for various UG PG programs for every academic session.
This is a project documentation titled: Online Railway Reservation System.
This documentation was submitted by me as my assignment in my 6th sem (2013) in APIIT SD INDIA, Panipat along with a full-fledged working system i.e., a website built using ASP.NET & SQL SERVER 2008
The document describes a hospital management system project created using Visual Basic 6.0. It includes 3 modules - admin, user (patient) and doctor modules. The admin can manage departments, users, doctors and view reports. Patients can view appointments, medications and history. Doctors can manage patient accounts. It discusses hardware requirements of Intel dual core processor and 512MB RAM and software requirements of Windows OS and MS Access database. Entity relationship and data flow diagrams are presented to illustrate the database and system design. The system aims to computerize hospital management for secure storage and fast retrieval of patient information.
SCHOOL BUS ROUTING MANAGEMENT SYSTEM [FINAL]ayushi goyal
This document presents a software engineering project report on a School Bus Routing Management System. It was created by three students at Shyama Prasad Mukherji College for Women, University of Delhi, under the guidance of Dr. Baljeet Kaur. The project aims to develop a software using GIS techniques to track school buses and manage student and staff databases. Key features include student registration, login functionality for parents/guardians, and a "track" feature to monitor bus routes and locations in real-time. The waterfall model was used for the software development process.
This document is Roshan Singh's internship report submitted in partial fulfillment of a Bachelor's degree in Information Technology from Tribhuvan University. The report details his internship at Subisu Cablenet Pvt. Ltd., an Internet service provider in Kathmandu, Nepal. During his internship, Roshan gained experience configuring routers, modems, and ONU devices for customers, troubleshooting internet issues, and replacing equipment. He learned about ISP network operations and improved his technical and communication skills. The report includes worksheets documenting the tasks he completed during the internship period.
This document describes an Android application called AMIZONER that was created to allow students to easily check their attendance records from Amity University's student portal. The application logs into the student portal using HTTPS, parses the attendance details, stores them locally in an SQLite database. It then displays the computed attendance information to users in a user-friendly way. The application was created using technologies like HTTPS POST/GET, HTML parsing, SQLite database, and the Android platform. It also includes features for server-client communication using Google App Engine and monitoring application usage with Google Analytics and monetization with advertisements.
This document summarizes a project report for an online job portal submitted by three students - Prateek Kulshrestha, Vishesh Vashisht, and Jayant Kumar. The report includes an introduction to the project, organization profile, problem statement, proposed solution, system analysis, software requirements, selected technologies (.NET framework, ASP.NET, C#, SQL Server), system design diagrams, output screens, testing plan, and security measures. The objective is to develop an online system for job seekers to upload CVs and for companies to search profiles matching job requirements.
Employee Management System UML Diagrams Use Case Diagram, Activity Diagram, S...Mohammad Karim Shahbaz
The system as such as it is designed is called Employee Management System (EMS). Employee Management System is documented using UML Diagrams very easy to understand. This Employee Management System is designed to Manage the Recruitment & new Employee Registration process and Manage each Employee data. Attendance Management System and Salary Management Systems are also embedded. UML Diagrams ( Use Case Diagram, Activity Diagram, State Chart Diagram or State Machine, Sequence Diagram, Class Diagram, Deployment Diagram, Component Diagram ) and text are for this documentation. NU,BCS
NOTE: this is total documentation, You can also find this Documentation Related Presentation (.ppt) here:
http://www.slideshare.net/mohammadkarim3785/employee-management-system-uml
This document provides an overview of a proposed railway reservation system project. The goals are to automate the reservation process and make it more efficient and fast. The system will include modules for train schedules, seat allocation, fare calculation, and administration features. It aims to provide security, accuracy, and reduce manual work while giving users and administrators a friendly interface. The software will use Visual Basic and MS Access, and require at least 512MB RAM and 20GB hard disk on Windows OS.
UML Diagrams for Real estate management systemStarlee Lathong
The Real Estate Management System allows real estate professionals to easily keep track of leads, manage listings, and market to prospects. It allows users to search for required properties, matches them to user requirements, and generates property and vendor details. The system was designed using Visual Paradigm and uses ASP.net for the front end, MS Access as the backend, and can run on Windows XP/7/8 operating systems. UML diagrams including use case, class, activity, state, sequence, collaboration, component, and deployment diagrams were created for the system.
Internship Report of Bsc. CSIT (Format according to TU). The significant number of employee has admitted that they are wasting nearly an hour of the day on their working days. Even the managers of the company cannot look after every single employee in the organization what they have been working on each day.
Kaaahwa Armstrong completed a field attachment at Uganda Broadcasting Corporation (UBC) from June to August 2016. During this time, they worked under the supervision of several managers in the IT department. Their duties included networking tasks like cable termination, router configuration, and setting up local area networks. They also installed and configured operating systems, databases, and websites. Through hands-on experience with computer repair, networking, and software installation, Armstrong gained valuable practical skills to supplement their university computer science education. While the attachment provided valuable learning opportunities, challenges included limited equipment and understanding new technical concepts. Overall, the internship helped Armstrong apply their academic knowledge in a real-world work environment.
A Banking Management system is an application that gives functionality like sending money, bill payment, taking a loan, check balance, see all transaction history and many more.
The document describes a project report on an Employee Management System created by a student named Vishal Kumar. It includes an introduction describing the project, objectives, proposed system, and phases of the system development life cycle used to create the software. The project uses SDLC methodology and includes phases for initiation, concept development, planning, design, implementation, testing, and maintenance.
E-FREELANCING - MAJOR/FINAL YEAR PROJECT DOCUMENTATIONPIYUSH Dubey
Hello Friends, This online web application project E-FREELANCING, I made during my Engineering days. But couldn't upload. But seeing the greater demand for project documentations, I have finally uploaded this. Kindly review and let me know if this helps you. Reach out to me on masterpiyushdubey@gmail.com if you want this documentation .
Android Based Application Project Report. Abu Kaisar
This document describes a project report for a counseling hour mobile application created for the Wireless Programming course. The application allows students to book counseling sessions with teachers and teachers to update their profiles and counseling times. It includes chapters on introduction and objectives, background studies, system design diagrams, software and hardware requirements, and proposed features for students and teachers. The goal is to make it easier for students and teachers to communicate about counseling sessions through a mobile app rather than traditional methods.
This document describes a project to develop a railway reservation system. It was created by three students - Koyel Majumdar, Rina Paul, and Lagnajita Halder - for their master's degree program. The system will allow users to search train schedules, make reservations, check reservation status, and cancel reservations online. It aims to improve on previous manual paper-based systems by providing an automated digital system accessible from multiple locations. The document outlines the project scope, user requirements, hardware and software needs, and security considerations for the new railway reservation system.
LPG Booking System [ bookmylpg.com ] ReportNandu B Rajan
BOOK LPG FROM ANYWHERE (Mini Project 2016)
During today’s busy life, no one is ready to waste the time by doing the time consuming and hassle refill booking like IVR Booking System. We are proposing a simple, interactive, hassle free, less time consuming and efficient LPG Booking System. This is beneficial for the Gas Agencies also, they get the refill booking requests and consumer details instantly. Our system is futuristic and can be updated according to the future needs easily.
Features:-
To book an LPG cylinder, you should be a authorised customer. An authorised customer can register to the website and get user id and password. After you have registered, you can log on to the LPG portal using the password and user id provided to you.
Pros:-
Consumers can book the refill by just one click, they can post queries or complaints. Needs only username and password. If they don’t have one, the valid consumers can get the username and passwords with simple registration process. The Admin can only access the database, only he can add the consumers and staff. So the system is secured. The authorized staff can see the bookings and the consumer details without any hassle. He can mark the status whether the refill delivered or not. If delivered then refill request will be automatically cleared.
web based house rental system phaseII.docxMotiDiro1
Intel Core i5, 8GB RAM, 1TB HDD
1.5.2 Software tools
The software tools that will be used to develop the proposed system are:
Operating System: Windows 10
Front-end: HTML, CSS, JavaScript
Back-end: PHP
Database: MySQL
Modeling Tools: Visio, Dia
Text Editor: Notepad++
Browser: Google Chrome
Project report RAILWAY TICKET RESERVATION SYSTEM SADNitesh Singh
This document provides a project report on developing a railway ticket reservation system. It includes sections that outline the system's requirements and functions for booking and cancelling tickets, checking PNR status and train details. It also includes data flow diagrams, decision tables, a decision tree, sequence diagram, use case diagram, activity diagram, structure chart, and Ishikawa diagram to model and design the system. Key terms used in the system like PNR, DFD, e-ticket, and i-ticket are defined in a glossary.
Online Electronic Shopping Project Report Final YearAmit Verma
This project report describes the development of an online electronic shopping website. It discusses the existing manual shopping system and outlines the objectives of developing an online system. The report covers various aspects of system analysis and design such as purpose, scope, feasibility study, requirements specification, technological background, system analysis and design including use cases, sequence diagrams, data flow diagrams and database design. It also discusses the user interface design, implementation technologies used, integrating the web application, testing and quality assurance plan. The overall aim is to develop a basic e-commerce website that allows customers to shop online and provides an admin interface to manage products and orders.
Ibm mobile first in action for mgovernment and citizen mobile services redbupbechanhgmail
This document discusses how IBM's MobileFirst platform can support mobile government (mGovernment) solutions. It provides an overview of mGovernment and its advantages over traditional eGovernment. Key capabilities for a successful mGovernment implementation are also examined, including provisioning, security, governance, compliance, analytics, APIs, and the mobile application development lifecycle. The document then introduces IBM's MobileFirst portfolio and its components that address many of the capabilities needed for mGovernment, such as the MobileFirst Platform for app development, MobileFirst Protect for security, and Experience One for analytics.
Enabling mobile apps with ibm worklight application center redbupbechanhgmail
This document provides guidance on installing, configuring, and using IBM Worklight Application Center. It discusses the Application Center architecture and components. It then provides step-by-step instructions on installing and configuring Application Center on WebSphere Application Server. The document also demonstrates how to use the Application Center console to manage applications and the mobile client to install applications on devices. Finally, it discusses integrating Application Center with IBM Endpoint Manager for mobile device management.
The document describes a hospital management system project created using Visual Basic 6.0. It includes 3 modules - admin, user (patient) and doctor modules. The admin can manage departments, users, doctors and view reports. Patients can view appointments, medications and history. Doctors can manage patient accounts. It discusses hardware requirements of Intel dual core processor and 512MB RAM and software requirements of Windows OS and MS Access database. Entity relationship and data flow diagrams are presented to illustrate the database and system design. The system aims to computerize hospital management for secure storage and fast retrieval of patient information.
SCHOOL BUS ROUTING MANAGEMENT SYSTEM [FINAL]ayushi goyal
This document presents a software engineering project report on a School Bus Routing Management System. It was created by three students at Shyama Prasad Mukherji College for Women, University of Delhi, under the guidance of Dr. Baljeet Kaur. The project aims to develop a software using GIS techniques to track school buses and manage student and staff databases. Key features include student registration, login functionality for parents/guardians, and a "track" feature to monitor bus routes and locations in real-time. The waterfall model was used for the software development process.
This document is Roshan Singh's internship report submitted in partial fulfillment of a Bachelor's degree in Information Technology from Tribhuvan University. The report details his internship at Subisu Cablenet Pvt. Ltd., an Internet service provider in Kathmandu, Nepal. During his internship, Roshan gained experience configuring routers, modems, and ONU devices for customers, troubleshooting internet issues, and replacing equipment. He learned about ISP network operations and improved his technical and communication skills. The report includes worksheets documenting the tasks he completed during the internship period.
This document describes an Android application called AMIZONER that was created to allow students to easily check their attendance records from Amity University's student portal. The application logs into the student portal using HTTPS, parses the attendance details, stores them locally in an SQLite database. It then displays the computed attendance information to users in a user-friendly way. The application was created using technologies like HTTPS POST/GET, HTML parsing, SQLite database, and the Android platform. It also includes features for server-client communication using Google App Engine and monitoring application usage with Google Analytics and monetization with advertisements.
This document summarizes a project report for an online job portal submitted by three students - Prateek Kulshrestha, Vishesh Vashisht, and Jayant Kumar. The report includes an introduction to the project, organization profile, problem statement, proposed solution, system analysis, software requirements, selected technologies (.NET framework, ASP.NET, C#, SQL Server), system design diagrams, output screens, testing plan, and security measures. The objective is to develop an online system for job seekers to upload CVs and for companies to search profiles matching job requirements.
Employee Management System UML Diagrams Use Case Diagram, Activity Diagram, S...Mohammad Karim Shahbaz
The system as such as it is designed is called Employee Management System (EMS). Employee Management System is documented using UML Diagrams very easy to understand. This Employee Management System is designed to Manage the Recruitment & new Employee Registration process and Manage each Employee data. Attendance Management System and Salary Management Systems are also embedded. UML Diagrams ( Use Case Diagram, Activity Diagram, State Chart Diagram or State Machine, Sequence Diagram, Class Diagram, Deployment Diagram, Component Diagram ) and text are for this documentation. NU,BCS
NOTE: this is total documentation, You can also find this Documentation Related Presentation (.ppt) here:
http://www.slideshare.net/mohammadkarim3785/employee-management-system-uml
This document provides an overview of a proposed railway reservation system project. The goals are to automate the reservation process and make it more efficient and fast. The system will include modules for train schedules, seat allocation, fare calculation, and administration features. It aims to provide security, accuracy, and reduce manual work while giving users and administrators a friendly interface. The software will use Visual Basic and MS Access, and require at least 512MB RAM and 20GB hard disk on Windows OS.
UML Diagrams for Real estate management systemStarlee Lathong
The Real Estate Management System allows real estate professionals to easily keep track of leads, manage listings, and market to prospects. It allows users to search for required properties, matches them to user requirements, and generates property and vendor details. The system was designed using Visual Paradigm and uses ASP.net for the front end, MS Access as the backend, and can run on Windows XP/7/8 operating systems. UML diagrams including use case, class, activity, state, sequence, collaboration, component, and deployment diagrams were created for the system.
Internship Report of Bsc. CSIT (Format according to TU). The significant number of employee has admitted that they are wasting nearly an hour of the day on their working days. Even the managers of the company cannot look after every single employee in the organization what they have been working on each day.
Kaaahwa Armstrong completed a field attachment at Uganda Broadcasting Corporation (UBC) from June to August 2016. During this time, they worked under the supervision of several managers in the IT department. Their duties included networking tasks like cable termination, router configuration, and setting up local area networks. They also installed and configured operating systems, databases, and websites. Through hands-on experience with computer repair, networking, and software installation, Armstrong gained valuable practical skills to supplement their university computer science education. While the attachment provided valuable learning opportunities, challenges included limited equipment and understanding new technical concepts. Overall, the internship helped Armstrong apply their academic knowledge in a real-world work environment.
A Banking Management system is an application that gives functionality like sending money, bill payment, taking a loan, check balance, see all transaction history and many more.
The document describes a project report on an Employee Management System created by a student named Vishal Kumar. It includes an introduction describing the project, objectives, proposed system, and phases of the system development life cycle used to create the software. The project uses SDLC methodology and includes phases for initiation, concept development, planning, design, implementation, testing, and maintenance.
E-FREELANCING - MAJOR/FINAL YEAR PROJECT DOCUMENTATIONPIYUSH Dubey
Hello Friends, This online web application project E-FREELANCING, I made during my Engineering days. But couldn't upload. But seeing the greater demand for project documentations, I have finally uploaded this. Kindly review and let me know if this helps you. Reach out to me on masterpiyushdubey@gmail.com if you want this documentation .
Android Based Application Project Report. Abu Kaisar
This document describes a project report for a counseling hour mobile application created for the Wireless Programming course. The application allows students to book counseling sessions with teachers and teachers to update their profiles and counseling times. It includes chapters on introduction and objectives, background studies, system design diagrams, software and hardware requirements, and proposed features for students and teachers. The goal is to make it easier for students and teachers to communicate about counseling sessions through a mobile app rather than traditional methods.
This document describes a project to develop a railway reservation system. It was created by three students - Koyel Majumdar, Rina Paul, and Lagnajita Halder - for their master's degree program. The system will allow users to search train schedules, make reservations, check reservation status, and cancel reservations online. It aims to improve on previous manual paper-based systems by providing an automated digital system accessible from multiple locations. The document outlines the project scope, user requirements, hardware and software needs, and security considerations for the new railway reservation system.
LPG Booking System [ bookmylpg.com ] ReportNandu B Rajan
BOOK LPG FROM ANYWHERE (Mini Project 2016)
During today’s busy life, no one is ready to waste the time by doing the time consuming and hassle refill booking like IVR Booking System. We are proposing a simple, interactive, hassle free, less time consuming and efficient LPG Booking System. This is beneficial for the Gas Agencies also, they get the refill booking requests and consumer details instantly. Our system is futuristic and can be updated according to the future needs easily.
Features:-
To book an LPG cylinder, you should be a authorised customer. An authorised customer can register to the website and get user id and password. After you have registered, you can log on to the LPG portal using the password and user id provided to you.
Pros:-
Consumers can book the refill by just one click, they can post queries or complaints. Needs only username and password. If they don’t have one, the valid consumers can get the username and passwords with simple registration process. The Admin can only access the database, only he can add the consumers and staff. So the system is secured. The authorized staff can see the bookings and the consumer details without any hassle. He can mark the status whether the refill delivered or not. If delivered then refill request will be automatically cleared.
web based house rental system phaseII.docxMotiDiro1
Intel Core i5, 8GB RAM, 1TB HDD
1.5.2 Software tools
The software tools that will be used to develop the proposed system are:
Operating System: Windows 10
Front-end: HTML, CSS, JavaScript
Back-end: PHP
Database: MySQL
Modeling Tools: Visio, Dia
Text Editor: Notepad++
Browser: Google Chrome
Project report RAILWAY TICKET RESERVATION SYSTEM SADNitesh Singh
This document provides a project report on developing a railway ticket reservation system. It includes sections that outline the system's requirements and functions for booking and cancelling tickets, checking PNR status and train details. It also includes data flow diagrams, decision tables, a decision tree, sequence diagram, use case diagram, activity diagram, structure chart, and Ishikawa diagram to model and design the system. Key terms used in the system like PNR, DFD, e-ticket, and i-ticket are defined in a glossary.
Online Electronic Shopping Project Report Final YearAmit Verma
This project report describes the development of an online electronic shopping website. It discusses the existing manual shopping system and outlines the objectives of developing an online system. The report covers various aspects of system analysis and design such as purpose, scope, feasibility study, requirements specification, technological background, system analysis and design including use cases, sequence diagrams, data flow diagrams and database design. It also discusses the user interface design, implementation technologies used, integrating the web application, testing and quality assurance plan. The overall aim is to develop a basic e-commerce website that allows customers to shop online and provides an admin interface to manage products and orders.
Ibm mobile first in action for mgovernment and citizen mobile services redbupbechanhgmail
This document discusses how IBM's MobileFirst platform can support mobile government (mGovernment) solutions. It provides an overview of mGovernment and its advantages over traditional eGovernment. Key capabilities for a successful mGovernment implementation are also examined, including provisioning, security, governance, compliance, analytics, APIs, and the mobile application development lifecycle. The document then introduces IBM's MobileFirst portfolio and its components that address many of the capabilities needed for mGovernment, such as the MobileFirst Platform for app development, MobileFirst Protect for security, and Experience One for analytics.
Enabling mobile apps with ibm worklight application center redbupbechanhgmail
This document provides guidance on installing, configuring, and using IBM Worklight Application Center. It discusses the Application Center architecture and components. It then provides step-by-step instructions on installing and configuring Application Center on WebSphere Application Server. The document also demonstrates how to use the Application Center console to manage applications and the mobile client to install applications on devices. Finally, it discusses integrating Application Center with IBM Endpoint Manager for mobile device management.
Extending your business to mobile devices with ibm worklightbupbechanhgmail
This document provides an overview and technical details about extending a business to mobile devices using IBM Worklight. It discusses the mobile industry trends and challenges, defines a successful mobile strategy, and explores the IBM MobileFirst solution architecture. It then uses a case study of an airline company to illustrate how the company developed a mobile roadmap and strategy using Worklight to create mobile applications for employees and customers. The document provides guidance on building, deploying, and managing a mobile solution using Worklight and related IBM products.
This is a report on a mobile application that enables one to easily identify happening places, hotels and guest houses within a particular city, its currently being tested in Gulu City by the the users and the development team
The document describes a project report for developing a mobile restaurant tracker application called LunchList for Android platforms. It aims to address the lack of location tracking information in the restaurant industry in Gulu, Uganda. The report outlines conducting research through interviews with restaurant owners to gather requirements. A prototype was developed using Rapid Application Development methodology. It allows users to locate restaurants by location, view them on maps, get directions and call the restaurant. The application is designed to improve location tracking and awareness for customers in the restaurant industry.
This document provides a framework for developing an organizational or project-based Building Information Modeling (BIM) deployment plan. It outlines key elements to address such as modeling standards, staffing needs, planned models and analyses. The goal is to help users streamline project communications and reduce costs through collaborative planning and BIM implementation. Sections provide guidance on developing a BIM vision and goals, modeling standards, planned model types and analyses, staffing structure and skills requirements. Users can fill in provided templates and tables to develop a customized plan suited to their specific needs and applications of BIM.
This document provides an overview of the ABAP RESTful Application Programming Model. It begins with prerequisites and constraints for using the model. The document then covers getting started with a sample flight data scenario, including downloading reference code, defining the data model, and creating an OData service. Subsequent sections discuss concepts like queries, business objects, business services, and more. The document also includes examples of developing different types of RESTful apps using the programming model.
This document provides guidance on deploying IBM Tivoli Composite Application Manager for Web Resources V6.2. It begins with an overview of the solution and its architecture. It then discusses planning the deployment, including required hardware, software, and typical environment sizes. The document also includes guidance on installing and configuring the various components as well as usage scenarios once deployed.
This document provides guidance on planning and deploying IBM Tivoli Composite Application Manager for Web Resources V6.2 (ITCAM) to monitor Web application server performance. It discusses the ITCAM architecture and how it interconnects with J2EE and WebSphere data collectors. It also covers hardware and software prerequisites, typical deployment environments, and provides a sample project plan for setting up ITCAM with tasks such as environment preparation, software installation, and customizing the product.
Software Requirement Specification on Online Purchasing Systemsabafarheen
This document outlines the software requirements specification for an online purchase system. It includes sections on introduction, overall description, specific requirements, design constraints, advantages/disadvantages/challenges of online shopping, system design specification, and testing. The introduction provides an overview of online shopping and the purpose of the purchase system, which is to allow customers to easily calculate items in their shopping cart and view customer data. It defines key terms and the scope of purchasing and selling products/services over the internet.
This document outlines the requirements for a live chat application. It discusses the purpose, scope, features and functions of the chat app. The app allows users to chat in real-time and provides features such as customizable welcome messages, file sharing, and group chat. It also specifies the user requirements, interfaces, design constraints, usage scenarios and UML diagrams for the app. The goal is to develop an easy to use messaging solution that enables seamless communication between users.
This document provides an overview and guide for using Business Objects reporting tools with Tivoli Data Warehouse 1.2. It covers Business Objects products and platform, installing Business Objects desktop components, configuring Business Objects for Tivoli Data Warehouse, creating reports, advanced reporting and security features, and deploying reports. The document contains examples and step-by-step instructions for setting up Business Objects and generating simple to advanced reports on Tivoli Data Warehouse data.
A Mobile and Web application for time measurement intended to get an accurate picture of the productive time in a production environment in order to reveal the root causes behind ineffective/idle time and to eliminate non-added activities/tasks .
Technical Key-words : Ionic 2, Angular 2, PouchDB, CouchDB ,
DB Replication Protocol, Django, Python NvD3 charts .
This document provides an overview of a text recognition software project for Android mobile devices. The project aims to develop an application that can capture an image using a mobile device, localize text regions in the image, recognize the text, and optionally integrate it with applications like translation. Key requirements include capturing images with 2-4 megapixels, localizing text regions on images with homogeneous backgrounds, recognizing printed alphanumeric text in a limited set of fonts, and developing a translation application using the recognized text. Non-functional requirements address performance, safety, security, and software quality attributes like portability, maintainability, and reliability. The document describes the intended users, scope, features, design constraints, and provides detailed functional requirements for the image
A Usability Evaluation carried out on my second year Brunel Group project.
A.R.C. (Augmented Reality Communicator), is an augmented reality social networking application , designed and built for my second year group project at Brunel University.
This thesis examines the wireless security of mobile applications, with a focus on banking apps, on the Android platform. The author conducted a static code analysis of apps on the Google Play Store and found widespread security flaws in how apps validate SSL certificates for secure connections. To address false positives from the static analysis, the author developed a method using dynamic code analysis and manual log file analysis to identify the critical code sections for certificate validation. The goal is to evaluate security and reduce false positives from the static analysis tool.
This document provides an overview of IBM's MobileFirst strategy and solutions. It describes IBM's MobileFirst platform, which includes tools for developing, integrating, deploying, managing, securing and testing mobile applications. It also discusses IBM's strategy, software and services for enabling enterprise mobility. Practical scenarios demonstrate how to use IBM Worklight to develop a mobile app and integrate it with backend systems and services.
This document is the master's thesis of Natascha Abrek submitted to the Technical University of Munich on October 14, 2015. The thesis proposes designing and implementing a mobile application for collaborative structuring of knowledge-intensive processes. Knowledge-intensive processes involve activities like knowledge sharing, reuse and collaboration between knowledge workers. However, such processes are unpredictable and dynamic in nature. The thesis aims to develop a mobile version of the existing web application Darwin to facilitate structuring of knowledge-intensive processes on mobile devices according to usability guidelines. An evaluation of the developed mobile solution will also be conducted to incorporate design improvements iteratively.
Securing your mobile business with ibm worklightbupbechanhgmail
This document provides an overview of securing mobile applications and businesses with IBM Worklight and related IBM security products. It discusses IBM MobileFirst solutions for mobile application development, management, security, and analytics. It then describes common mobile security threats and the mobile application landscape. The document outlines IBM's MobileFirst Security solution using the Worklight platform and products like Security Access Manager, Security AppScan, WebSphere DataPower, and Security QRadar. It also presents a business scenario used in the book to apply these security approaches and features.
Similar to B.Sc.CSIT final year(7th semester) project on Tenant Screening (20)
it describes the bony anatomy including the femoral head , acetabulum, labrum . also discusses the capsule , ligaments . muscle that act on the hip joint and the range of motion are outlined. factors affecting hip joint stability and weight transmission through the joint are summarized.
LAND USE LAND COVER AND NDVI OF MIRZAPUR DISTRICT, UPRAHUL
This Dissertation explores the particular circumstances of Mirzapur, a region located in the
core of India. Mirzapur, with its varied terrains and abundant biodiversity, offers an optimal
environment for investigating the changes in vegetation cover dynamics. Our study utilizes
advanced technologies such as GIS (Geographic Information Systems) and Remote sensing to
analyze the transformations that have taken place over the course of a decade.
The complex relationship between human activities and the environment has been the focus
of extensive research and worry. As the global community grapples with swift urbanization,
population expansion, and economic progress, the effects on natural ecosystems are becoming
more evident. A crucial element of this impact is the alteration of vegetation cover, which plays a
significant role in maintaining the ecological equilibrium of our planet.Land serves as the foundation for all human activities and provides the necessary materials for
these activities. As the most crucial natural resource, its utilization by humans results in different
'Land uses,' which are determined by both human activities and the physical characteristics of the
land.
The utilization of land is impacted by human needs and environmental factors. In countries
like India, rapid population growth and the emphasis on extensive resource exploitation can lead
to significant land degradation, adversely affecting the region's land cover.
Therefore, human intervention has significantly influenced land use patterns over many
centuries, evolving its structure over time and space. In the present era, these changes have
accelerated due to factors such as agriculture and urbanization. Information regarding land use and
cover is essential for various planning and management tasks related to the Earth's surface,
providing crucial environmental data for scientific, resource management, policy purposes, and
diverse human activities.
Accurate understanding of land use and cover is imperative for the development planning
of any area. Consequently, a wide range of professionals, including earth system scientists, land
and water managers, and urban planners, are interested in obtaining data on land use and cover
changes, conversion trends, and other related patterns. The spatial dimensions of land use and
cover support policymakers and scientists in making well-informed decisions, as alterations in
these patterns indicate shifts in economic and social conditions. Monitoring such changes with the
help of Advanced technologies like Remote Sensing and Geographic Information Systems is
crucial for coordinated efforts across different administrative levels. Advanced technologies like
Remote Sensing and Geographic Information Systems
9
Changes in vegetation cover refer to variations in the distribution, composition, and overall
structure of plant communities across different temporal and spatial scales. These changes can
occur natural.
A workshop hosted by the South African Journal of Science aimed at postgraduate students and early career researchers with little or no experience in writing and publishing journal articles.
This presentation was provided by Steph Pollock of The American Psychological Association’s Journals Program, and Damita Snow, of The American Society of Civil Engineers (ASCE), for the initial session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session One: 'Setting Expectations: a DEIA Primer,' was held June 6, 2024.
हिंदी वर्णमाला पीपीटी, hindi alphabet PPT presentation, hindi varnamala PPT, Hindi Varnamala pdf, हिंदी स्वर, हिंदी व्यंजन, sikhiye hindi varnmala, dr. mulla adam ali, hindi language and literature, hindi alphabet with drawing, hindi alphabet pdf, hindi varnamala for childrens, hindi language, hindi varnamala practice for kids, https://www.drmullaadamali.com
The simplified electron and muon model, Oscillating Spacetime: The Foundation...RitikBhardwaj56
Discover the Simplified Electron and Muon Model: A New Wave-Based Approach to Understanding Particles delves into a groundbreaking theory that presents electrons and muons as rotating soliton waves within oscillating spacetime. Geared towards students, researchers, and science buffs, this book breaks down complex ideas into simple explanations. It covers topics such as electron waves, temporal dynamics, and the implications of this model on particle physics. With clear illustrations and easy-to-follow explanations, readers will gain a new outlook on the universe's fundamental nature.
Exploiting Artificial Intelligence for Empowering Researchers and Faculty, In...Dr. Vinod Kumar Kanvaria
Exploiting Artificial Intelligence for Empowering Researchers and Faculty,
International FDP on Fundamentals of Research in Social Sciences
at Integral University, Lucknow, 06.06.2024
By Dr. Vinod Kumar Kanvaria
This slide is special for master students (MIBS & MIFB) in UUM. Also useful for readers who are interested in the topic of contemporary Islamic banking.
How to Manage Your Lost Opportunities in Odoo 17 CRMCeline George
Odoo 17 CRM allows us to track why we lose sales opportunities with "Lost Reasons." This helps analyze our sales process and identify areas for improvement. Here's how to configure lost reasons in Odoo 17 CRM
How to Manage Your Lost Opportunities in Odoo 17 CRM
B.Sc.CSIT final year(7th semester) project on Tenant Screening
1. ii
ABSTRACT
Tenant screening is a cloud based mobile application that helps the property owners to
keep record of their properties and the tenants renting the property. It is an android
application where the property owner can easily create their account and add the details
of their properties and tenants renting the property. Those property details include the
property name, property number, the type and its location and the tenant details include
their name, email, mobile no. number, rent amount, Move in date and all the
information present in their citizenship card.
The application has been developed using android studio as IDE, java as main
programming language, xml as defining layout, android built in layout editor to design
layout and backend part using the firebase.
Keywords: tenant, android, firebase
2. iii
TABLE OF CONTENTS
ACKNOWLEDGEMENT.................................................................................................................i
ABSTRACT................................................................................................................................... ii
List of figures............................................................................................................................. vi
List of Tables ............................................................................................................................ vii
List of Abbreviations ............................................................................................................... viii
Chapter 1: Introduction .............................................................................................................1
1.1. Background .....................................................................................................................1
1.2. Problem Statement.........................................................................................................1
1.3. Objectives .......................................................................................................................2
1.4. Scope...............................................................................................................................2
1.5. Limitation........................................................................................................................3
Chapter 2: Requirement Analysis and Feasibility Analysis ........................................................4
2.1. Requirement Analysis .....................................................................................................4
2.1.1. Functional Requirements.........................................................................................4
2.1.2. Non-functional Requirements .................................................................................6
2.2. Feasibility Analysis ..........................................................................................................7
2.2.1. Technical ..................................................................................................................7
2.2.2. Operational ..............................................................................................................8
2.2.3. Economic..................................................................................................................8
2.2.4. Schedule...................................................................................................................8
Chapter 3: System Design..........................................................................................................9
3.1. Module..........................................................................................................................10
3.1.1. Module 1:...............................................................................................................10
3.1.2. Module 2:...............................................................................................................10
3. iv
3.1.3. Module 3:...............................................................................................................10
3.2. Database design............................................................................................................10
3.2.1. ER Diagram.............................................................................................................11
3.2.2 Database Schema....................................................................................................12
3.2.3 Data Format (JSON).................................................................................................13
3.3 User Interface Design.....................................................................................................15
3.3.1 User Interface Representation................................................................................16
3.4. Process Modelling.........................................................................................................17
3.4.1 Flowchart ................................................................................................................17
3.4.2 DFD..........................................................................................................................19
Chapter 4: Implementation .....................................................................................................23
4.1. Software development life cycle model .......................................................................23
4.1.1. Requirement and analysis......................................................................................24
4.1.2. Design.....................................................................................................................24
4.1.3. Coding/Implementation.........................................................................................24
4.1.4. Testing....................................................................................................................25
4.1.5. Maintenance and Documentation.........................................................................25
4.2. Tools..............................................................................................................................25
4.2.1 Draw.io....................................................................................................................25
4.2.2 Android studio 2.3.3 (IDE).......................................................................................25
4.2.3. Android SDK 26.0.1 ................................................................................................26
4.2.3 Android Virtual Device (AVD)..................................................................................26
4.3. Technology....................................................................................................................26
4.3.1. Java.........................................................................................................................26
4.3.2 XML .........................................................................................................................27
4.3.4 Firebase...................................................................................................................27
Chapter 5: Testing....................................................................................................................29
4. v
5.1. Unit Testing...................................................................................................................29
5.1.1 Test Case .................................................................................................................29
5.2. Integration Testing........................................................................................................35
5.3. System Testing..............................................................................................................36
Chapter 6: Conclusion..............................................................................................................37
6.1. Conclusion.....................................................................................................................37
6.2. Future scope .................................................................................................................37
REFERENCES.............................................................................................................................38
APPENDICES.............................................................................................................................39
Appendix A...........................................................................................................................39
Screen shot of the application.........................................................................................39
Appendix B...........................................................................................................................43
AndroidManifest.xml file .................................................................................................43
Firebase API .....................................................................................................................44
Email authentication using firebase ................................................................................45
5. vi
List of figures
Figure 1: Use case diagram before login .......................................................................5
Figure 2: Use case diagram after login .........................................................................6
Figure 3: Work Schedule ...............................................................................................8
Figure 4: System structure .............................................................................................9
Figure 5: System Architecture .......................................................................................9
Figure 6: ER diagram...................................................................................................11
Figure 7: Database Schema..........................................................................................12
Figure 8: JSON tree structure ......................................................................................13
Figure 9: JSON tree structure of user ..........................................................................14
Figure 10: JSON tree structure of property..................................................................14
Figure 11: JSON tree structure of tenant .....................................................................15
Figure 12: View and View group hierarchy ................................................................16
Figure 13: Flowchart....................................................................................................18
Figure 14: DFD context diagram .................................................................................19
Figure 15: Level 0 DFD...............................................................................................20
Figure 16: Level 1 DFD – (3.0) ...................................................................................21
Figure 17: Level 1 DFD – (4.0) ...................................................................................21
Figure 18: Level 1 DFD – (6.0) ...................................................................................22
Figure 19: Waterfall model..........................................................................................23
6. vii
List of Tables
Table 1: Test case for Sign up......................................................................................29
Table 2: Test case for Sign in ......................................................................................31
Table 3: Test case for adding property ........................................................................32
Table 4: Test case for adding tenant ............................................................................33
7. viii
List of Abbreviations
API Application Interface
AVD Android Virtual Device
DFD Data Flow Diagram
DOB Date of Birth
ER Entity Diagram
ID Identity
IDE Integrated Development Environment
JDK Java Development Kit
JSON Javascript Object Notation
SDLC Software Development Life Cycle
SDK Software Development Kit
SQL Stuctured Query Language
UI User Interface
XML Extensible Markup Language
8. 1
Chapter 1: Introduction
1.1. Background
Tenant screening is a cloud based mobile application that helps the property owners to
keep record of their properties and the tenants renting the property. It is an android
application where the property owner can easily create their account and add the details
of their properties and tenants renting the property. Those property details include the
property name, property number, address and the income details and the tenant details
include their name, email, mobile no. number, rent amount, Move in date and all the
information present in their citizenship card.
Tenant screening fulfills the need of mobile and digital record keeping system of the
properties and the tenants renting the property. Since the application runs on android
smartphones, it is accessible from anywhere around the world and the property owners
can add, update and delete the information from anywhere. Internet connection is
required in order to use this application and it supports the android version 4.3 and
above it. The interface of this application is straightforward and roughly takes 5 seconds
to get started. Adding the properties and tenant details on the application is easy, just
click on the add property/tenant button and enter the details. Similarly viewing the
details and updating it is easy. Here registration is must for all the property owners
having this application in order to add and keep the record of their properties and the
tenants. After registration, the property owners can use his/her registered email account
and password to login in to the system.
1.2. Problem Statement
The old fashioned way of keeping records on paper and file is troublesome and time
consuming. There is a risk of files being damaged or destroyed with no back-up.
Besides this, the file must be carried everywhere to access the details inside of it which
is not possible and updating/modifying the details is troublesome. In addition to this,
most of the property owners does not care about keeping the records of their properties
9. 2
and tenants renting the property since paper record keeping things is troublesome, time
consuming and not effective for them.
Now a days, all record keeping things are moving in to the digital, mobile and cloud
world. The old fashioned way of keeping the records on paper is slowly decreasing and
people are moving into the digital cloud based services of storing and managing the
records. The tenant screening android application fulfills the need of digital and mobile
record keeping system. So, for this tenant screening has been developed in order to store
and manage records of the properties and tenants on the internet which reduces the risk
of lost data and provides access from any location.
1.3. Objectives
The objectives of tenant screening android application are as follows:
To migrate the paper based record keeping system into android device based
record keeping system.
To store and manage records of the properties and tenants on the cloud.
To provide access to properties and tenants information from any location
through this application.
1.4. Scope
The tenant screening is an android mobile application suitable for all the property
owners. Specially, it is designed to facilitate the property owners to store and manage
the properties and tenants record on the internet. The property owners having the
android smartphones can easily install and use this app. This application is very easy
and simple to understand. So, the property owners definitely want to have this
application in their smartphone installed. This application would create a database
which could acts as a backup of all the data of the house owner and the property.
10. 3
1.5. Limitation
Some of the limitation of this application are listed below:
Must require android version 4.3 and above version.
Internet connection required.
Property owner must know English language.
11. 4
Chapter 2: Requirement Analysis and Feasibility Analysis
2.1. Requirement Analysis
Requirement analysis is the process of precisely identifying, defining, and documenting
the various requirements that are related to a particular business objective.
Requirements gathering helps in clearly understanding the needs of the customer,
defining the scope of the project, and assessing the timescales and resources required
to complete it. There are two types of requirement which are as follows:
2.1.1. Functional Requirements
In order to make the application functional, we require the following:
a) Download mobile application
A user should be able to download the mobile application either through google play
store or similar service on the phone. The application should be free to download.
b) User Registration
Given that a user has downloaded the mobile application, then the user should be able
to register through this mobile application. The user must provide username, email,
mobile number, sex, citizenship no and password.
c) User login
Given that a user has registered, then the user should be able to log in the mobile
application through his/her email and password. The login information will be stored
on the phone and in the future the user should be logged in automatically.
d) Reset Password
Given that the user has registered, then the use should be able to retrieve his/her
password by email.
e) Home activity
Given that the user is logged in to the mobile application, then the first page that is
shown should be the home activity. The user get references to all other activities like
12. 5
adding the properties, adding the tenants, accessing the property and tenants details
through this activity.
f) Add property and tenant
The user should be able to add any numbers and type of properties and tenants renting
that properties.
g) Property details and tenants
The user should be able to view the details of added properties and tenants.
h) Edit the property and tenant details
The user should be able to edit the details of the properties and tenants.
i) Owner profile
The user should be able to view their own profile, modify their details and change email
and password.
j) Logout
The user should be able to logout of the system.
Figure 1: Use case diagram before login
13. 6
Figure 2: Use case diagram after login
The above use case diagram also show the functional requirement of the application. A
use case diagram is a graphic depiction of the interactions among the elements of a
system. It is used in system analysis to identify, clarify, and organize system
requirements.
2.1.2. Non-functional Requirements
The non-functional requirements of this mobile application are as follows:
a) Performance
The performance requirement provide a details specification of the user interaction with
the application and measurements placed on the application performance.
14. 7
For the response time, it should not be more than 5 seconds if the user have a proper
internet connection and for the fault tolerance, if the system loses internet connection
or the systems gets some strange input, the user should be informed.
b) Maintainability
The application should be easy to extend. The code should be written in a way that it
favors implementation of new functions. In addition to this, test environment should be
built for the application to allow testing of the different functions.
c) Look and feel
The user interface should be light and easy to use. The bright color and multiple color
theme should be discarded. The use should be informed correctly if he/she is doing
anything wrong,
d) Security
There should be security of the communication between the user and system. Only
authenticated users are allowed to view their respective databases. The security of
creating account for the user must be maintained. No two users with same email and
citizenship number should be created.
2.2. Feasibility Analysis
Feasibility study is a test of system proposed according to its work ability, impact on
the organization, ability to meet user needs, and effective use of resources. The
feasibility study of this application had been carried out which are as follows:
2.2.1. Technical
This android mobile application is technically feasible. The software and hardware
requirement for the development of this application are not many and already available
as free as open source. The work for the project is done with the current equipment and
existing software technology. This application is supported by all android application
having version 4.3.
15. 8
2.2.2. Operational
Operational feasibility is the measure of how well a proposed system solves the
problems, and takes advantage of the opportunities identified during scope definition
and how it satisfies the requirements identified in the requirements analysis phase of
system development. This application is operationally feasible because this application
solves the problem faced by the property owners that are mentioned as problem
statement. Through this application property owners can store and manage the records
of their property and tenants on the cloud.
2.2.3. Economic
Economic feasibility is the analysis of a project's costs and revenues in an effort to
determine whether or not it is logical and possible to complete. This application is
economically feasible because this application is made using open source software and
the time spend in the development of this application is 3 months.
2.2.4. Schedule
The schedule for the development of the project are show in the figure below:
Figure 3: Work Schedule
16. 9
Chapter 3: System Design
System design is the process of defining the architecture, components, modules,
interfaces and data for a system to satisfy specified requirements. Design of the system
brings down the knowledge of requirements and analysis to design the software
product. Generally, this chapter deals with the module, database design, user interface
design and the program design. For the designing of the application, various diagrams
like use case diagram, schema diagram, ER diagram, DFD etc. have been used.
Figure 4: System structure
The above figure shows the general structure of application connection with the google
based cloud service “firebase” in the presence of internet connection.
Figure 5: System Architecture
17. 10
3.1. Module
A module is a software component or part of a program that contains one or more
routines. One or more independently developed modules make up a program. The
application is divided into three modules:
3.1.1. Module 1:
The first module in the application is the login. In the login process, the user can input
his email and password if he/she have already got an account, else the user should sign
up by putting his name, email, sex, phone number, citizenship number, date of birth and
address. Thus the user can have access to add properties and tenants, view their info
etc. Furthermore, user can reset their password by sending reset messages to their email
account.
3.1.2. Module 2:
The second module in the application is the accessibility of the main features of the
application after login. The features in this module include adding, viewing and editing
property and tenant information in their account database.
3.1.3. Module 3:
The third module in the application is viewing and updating the user details after login.
In addition to this, the user can change his primary email account and password if he/she
wants to login back into the system.
3.2. Database design
Database design is the process of producing a detailed data model of database. This
data model contains all the needed logical and physical design choices and physical
storage parameters needed to generate a design in a data definition language, which can
then be used to create a database. For the database design of the application, ER
diagram, schema diagram, and the format of data on the firebase has been shown which
are as follows:
18. 11
3.2.1. ER Diagram
An entity relationship model is a graphical representation of entities and their
relationships to each other, typically used in computing in regard to the organization
of data within databases or information systems. An entity is a piece of data-
an object or concept about which data is stored and a relationship is how the data is
shared between entities.
Figure 6: ER diagram
The above ER diagram shows the relationship between the Property owner, property
and the tenants renting the property. Entities have been represented by the rectangle,
attributes of an entity have been represented by the oval and the relationship between
the entities have been represented by the diamond shape. The lines with arrow head
represents that there is only one instance of an entity involved in the relationship and
the arrowless lines represents that there is one or many instance of an entity. The
underline word inside oval shape represents the application and the double oval shape
attribute represents the multivalued attribute.
19. 12
3.2.2 Database Schema
A database schema is the skeleton structure that represents the logical view of the entire
database and defines how the data is organized and how the relations among them are
associated. It formulates all the constraints that are to be applied on the data and defines
its entities and the relationship among them. It contains a descriptive detail of the
database, which can be depicted by means of schema diagrams. The database schema
of the application are as follows:
Figure 7: Database Schema
In above schema diagram, there are three database table property owner, property and
tenants which has their own primary key and attributes. The connecting lines shows the
relationship between the tables and the foreign key is used to link two tables together
20. 13
3.2.3 Data Format (JSON)
Firebase Database stores data as JSON objects and synchronized in real time to every
connected client. Firebase real time database is NoSQL database which means that data
is not stored as table format like the relational databases uses. Unlike a SQL database,
there are no tables or records. When you add data to the JSON tree, it becomes a node
in the existing JSON structure with an associated key. Data is stored as a key-value
store. Key-value store implement a simple data model that pairs a unique key with an
associated value.
Figure 8: JSON tree structure
21. 14
Figure 9: JSON tree structure of user
Figure 10: JSON tree structure of property
22. 15
Figure 11: JSON tree structure of tenant
3.3 User Interface Design
User interface design is the process of designing user interfaces for computing devices
and hardware so that they're easy for people to use. It's an interdisciplinary field that
involves graphic designers, artists, programmers, psychologists and even
anthropologists.
The application user interface is defined by XML and built using a hierarchy of layouts
(View Group Objects) and widgets (View Objects). Layouts are invisible containers
that control how its child views are positioned on the screen. Widgets are UI
components such as buttons and text boxes. Layout is built using android studio layout
editor.
23. 16
Figure 12: View and View group hierarchy
3.3.1 User Interface Representation
In order to make user interface in android application many view groups and child
views are used. The view groups and child views that will be used in the application
are as follows:
a) Relative layout
Relative Layout is a view group that displays child views in relative positions. The
position of each view can be specified as relative to sibling elements (such as to the
left-of or below another view) or in positions relative to the parent view group area
(such as aligned to the bottom, left or center).
b) Linear layout
Linear Layout is a view group that aligns all children in a single direction, vertically or
horizontally.
c) List View
List View is a view group that displays a list of scrollable items. The list items are
automatically inserted to the list using an Adapter that pulls content from a source such
as an array or database query and converts each item result into a view that's placed into
the list.
24. 17
d) Scroll View
A view group that allows the view hierarchy placed within it to be scrolled. Scroll view
may have only one direct child placed within it.
e) Image View
Image view is a view in which displays image resources.
f) Text View
Text View is a user interface element (view) that displays text to the user.
g) Edit Text
Edit text is a user interface element (view) for entering and modifying text.
h) Spinner
Spinners is a view which provide a quick way to select one value from a set. In the
default state, a spinner shows its currently selected value. Touching the spinner displays
a dropdown menu with all other available values, from which the user can select a new
one.
i) Buttons
A user interface element (view) the user can tap or click to perform an action.
3.4. Process Modelling
Process modelling is used to describe how things must/should/could be done in contrast
to the process itself which is really what happens. A process model is roughly an
anticipation of what the process will look like. The process modelling of the application
is done through Flowchart and DFD diagram.
3.4.1 Flowchart
A flowchart is a type of diagram that represents the workflow or process, showing the
steps as boxes of various kinds, and their order by connecting them with arrows.
26. 19
The above Flowcharts has used simple geometric symbols and arrows to define
relationships. The beginning or end of a program is represented by an oval. A process
is represented by a rectangle, a decision is represented by a diamond and an I/O process
is represented by a parallelogram.
3.4.2 DFD
A data flow diagram (DFD) is a graphical representation of the “flow” of data through
an information system, modelling its process aspects. A DFD is often used as a
preliminary step to create an overview of the system without going into great detail,
which can later be elaborated.
Figure 14: DFD context diagram
The above DFD is the Context Diagam of the application. The diagram has shown the
relationship between the application and the external entity “property owner. The circle
represents the process and the rectangle represents the external entity.”
27. 20
Figure 15: Level 0 DFD
The above figure is Level-0 DFD of the application. The main process is divided into
the sign up, sign in, account, manage property, property, manage tenant and tenant
processes.
28. 21
Figure 16: Level 1 DFD – (3.0)
The above figure is the level 1 DFD of process 3.0. The process 3.0 is further divided
into view account, change email/password and edit account process.
Figure 17: Level 1 DFD – (4.0)
The above figure is the level 1 DFD of process 4.0. The process 4.0 is further divided
into add property, update property and delete property process.
29. 22
Figure 18: Level 1 DFD – (6.0)
The above figure is the level 1 DFD of process 6.0. The process 6.0 is further divided
into add tenant, update tenant and delete tenant process.
30. 23
Chapter 4: Implementation
The implementation phase of the software development refers to the final process of
moving the solution from development status to production status. In this phase, Project
developers begin building and coding the software. This phase is followed by the
software development life cycle model used, tools used and the description of major
classes/methods.
4.1. Software development life cycle model
Software development life cycle is a process followed for a software project, within a
software organization. It consists of a detailed plan describing how to develop,
maintain, replace and alter or enhance specific software. The life cycle defines a
methodology for improving the quality of software and the overall development
process. The model of SDLC used in this project is the waterfall model. The waterfall
model is comprised of series of very definite phases each one intended to be started
sequentially only after the last has been completed, with one or more tangible
deliverables produced at the end of each phase of the waterfall model of SDLC.
Essentially, is starts with the heavy, documented, requirement-planning phase that
outlines all the requirements for the project, followed by sequential phase of design,
coding, test-casing, optional documentation, verification, validation and finally
deployment/release.
Figure 19: Waterfall model
31. 24
4.1.1. Requirement and analysis
Before developing the system, it is crucial for requirement collection and analysis. This
phase was used to determine the requirements such as: who are target group for the
system? How will they use the system? These were the type of questions that were
answered during the requirements gathering phase. After requirement gathering was
completed, these requirements were analyzed to determine whether or not these
requirements can be measured, tested and most of all, incorporated to the proposed
system. Once, requirements analysis was completed, the designing of the system was
initiated.
4.1.2. Design
In this phase, the actual design of the system takes place. The output of the design phase
is the design document that acts as an input for all subsequent SDLC phases. The design
of the app is simple and user friendly containing major activities, namely:
a) Register
b) Login
c) Homepage
d) Add property
e) Property details
f) Add tenant
g) Tenant details
h) User profile
i) Reset password
4.1.3. Coding/Implementation
Coding phase is carried out after the design phase. It includes the translation of the
requirements specified in requirement phase into a logical structure that can be
implemented in a programming language. The output of the design phase is a design
document that acts as an input for all subsequent SDLC phases. The project is done
using android studio as an integrated development environment (IDE) and implemented
using the android virtual device (AVD). This emulator helped to implement the project
32. 25
in real-like environment and sketch out the details of how it will work on real hardware.
Each activity is linked with another and interconnectivity is transparent and smooth.
4.1.4. Testing
After the code was developed in the coding phase, the codes were tested to check
whether or not it complied with the requirements and that the code actually solved the
needs that were addressed in the requirements phase. Testing of the project has been
done on emulator and as well as real hardware. Testing has been done for the individual
activities of the project. Errors that occurred were corrected and further debugging was
performed.
4.1.5. Maintenance and Documentation
Maintenance phase includes the implementation of changes that software might
undergo over a certain period of time, or implementation of the new requirements and
handling the residual errors that may exist in the software even after the testing phase.
Maintenance of the project will be followed according to the changing requirements
and trends. Similarly, documentation is the crucial part in the development of any
project which has been done hand in hand with the development process wherever
possible.
4.2. Tools
4.2.1 Draw.io
Draw.io is completely free online diagram editor built around Google Drive that enables
you to create flowcharts, UML, entity relation, network diagrams, mockups and more.
ER diagram, schema diagram, use case diagram, activity diagram and DFD are all made
using this online tools.
4.2.2 Android studio 2.3.3 (IDE)
Android studio is an official integrated development environment specially designed
for the development of the android application based on the JetBrains' IntelliJ IDEA
33. 26
software. The android studio contains all the required functionality and tools required
to create, compile, debug and deploy android applications.
All the coding, designing and testing part of the project is done through android studio
version 2.3.3.
4.2.3. Android SDK 26.0.1
The android software development kit (Android SDK) contains the necessary tools to
create, compile and package Android applications. The android SDK contains required
libraries, debugger, an emulator, android debug bridge for connecting virtual or real
device and relevant documentation.
For the development of the application, android SDK 26.01 has been used.
4.2.3 Android Virtual Device (AVD)
An android Virtual Device (AVD) is an emulator configuration that allows developers
to test the application by simulating the real device capabilities. The AVD can be
configured by specifying the hardware and software options. AVD manager enables an
easy way of creating and managing the AVD with its graphical interface. It can be
created as many as it is needed, based on the types of device we want to test for.
Google nexus 5.5 has been used as android virtual device for the application.
4.3. Technology
4.3.1. Java
Java is a very popular object oriented programming language developed by Sun
microsystems. In the development of the android application, java has been used as the
main programming language because java is platform independent and secure which
uses virtual machine to run its code, has powerful libraries which ease the developers
to make android application easily, is simple and easy to learn and it has object oriented
feature. In addition to this, the benefits of using java in android development are as
follows:
34. 27
a) There are a large number of developers already proficient in Java.
b) Java has huge open source support, with many libraries and tools available to
make developers life easier.
c) Java protects you from many of the problems inherent in native code, like
memory leaks, bad pointer usage, etc.
d) Java allows developers to create sandbox applications, and create a better
security model so that one bad App can't take down your entire OS.
So, the functioning of all the layout defined by the xml in our project is done by java.
To use java in developing android app, Java development kit (JDK) in android studio
has been installed.
4.3.2 XML
XML stands for Extensible Markup Language which is a markup language that defines
a set of rules for encoding documents in a format that is both human-
readable and machine-readable.
XML is used in the project to display and manage the GUI components. All the layout
of the project are defined by the XML. Besides these, defining the animation, color,
style, string, dimension, menu etc. have also done using XML. Similarly, the
configuration files are based on XML. The layout is created and described in XML
because by storing the user interface as XML file, it is easier to parse and the existing
code refactor tools can work without any changes. So, All the user interface or layout
and managing the components of the layout of the project has been done using XML.
The xml file is described inside android studio IDE.
4.3.4 Firebase
Firebase is a google based cloud service that permits you to make applications with no
server-side programming so that development turns out to be quicker and easier. With
Firebase, we don't have to stress over-provisioning servers or building REST APIs and
database because it has all the functions and provision provided by the backend/server
side of an application. The features of the firebase are as follows:
35. 28
a) Firebase analytics
b) Real time database
c) Firebase authentication
d) Push notification
e) Firebase storage
f) Firebase hosting
g) Firebase cloud messaging
h) Firebase crash reporting
i) Firebase test lab for android
The application has used Firebase API to connect with the firebase. Firebase is used
mainly to provide email authentication and real time database in the application. The
application has used Firebase email and password based authentication method to let
users authenticate with Firebase using their email addresses and passwords, and to
manage their accounts. In addition to this, sending mail for the confirmation of account
registration and sending password reset email has also been done by the use of firebase
authentication. The email authentication feature has been used by using firebase
authentication. Firebase real time database is the cloud hosted database and the
application has used this real time database which is NoSQL cloud database. In this
database, data is stored as JSON and synchronized in real time to every connected
clients. The application has used the real time database by using Firebase real time
database API.
36. 29
Chapter 5: Testing
Software testing is the process of evaluation a software item to detect differences
between given input and expected output. It also assesses the feature of a software item.
Testing assesses the quality of the product. Software testing is a process that should be
done during the development process.
5.1. Unit Testing
Unit testing is a software testing method by which individual units of source code, sets of
one or more computer program modules together with associated control data, usage
procedures, and operating procedures, are tested to determine whether they are fit for use.
Unit testing has been done testing individual activity of the application.
Each activity like registration, sign in, reset password, homepage, tenant details, property
details, account etc. has been tested individually. All the units testing has been done using
the AVD (android virtual device).
5.1.1 Test Case
a) For Sign up
Table 1: Test case for Sign up
Test
Case
ID
Test
Scenario
Test Steps Input test data Expected
Results
Actual
Results
Pass/
fail
TC-
1
Check
signup
activity
with valid
data
1) Open
App and go
to sign up
activity.
2) Fill up
the form
a) Name: Urgen
Sherpa
b) Email:
us_urgen@outl
ook.com
c) Sex: male
d) Date of
User should
get “account
successfully
created”
message and
redirected to
As
expecte
d
pass
37. 30
with valid
data.
3) Click
create
account
button.
Birth:
2051/04/05
e) Address:
Boudha-05
f) Mobile no:
9803527331
g) Citizenship
no: 1001
h) Password:
123456
sign in
activity
TC-
2
Check
signup
Activity
with
invalid
data
1) Open
App and go
to sign up
activity.
2) Fill up
the form
with
invalid
data.
3) Click
create
account
button.
a) Name: Urgen
Sherpa
b) Email: Urgen
c) Sex: male
d) Date of
Birth:
2051/04/05
e) Address:
Boudha-05
f) Mobile no:
9803527331
g) Citizenship
no: 1001
h) Password:
123456
User should
get “Enter
valid email”
Message.
As
expecte
d
pass
38. 31
b) For sign in
Table 2: Test case for Sign in
Test
Case
ID
Test
Scenario
Test Steps Input test
data
Expected
Results
Actual
Results
Pass/
fail
TC-
3
Check
sign in
activity
with
valid
data
1) Open App
and go to
sign in
activity.
2) Fill up the
form with
valid data.
3) Click sign
in button.
a) Email:
us_urgen@o
utlook.com
b) Password:
123456
User should
get “account
successfully
created”
message and
redirected to
home activity
As
expected
pass
TC-
4
Check
sign in
activity
with
invalid
data
1) Open App
and go to
sign in
activity.
2) Fill up the
form with
invalid data.
3) Click sign
in button.
a) Email:
Urgen
b) Password:
123456
User should
get “Enter
valid email”
Message.
As
expected
pass
39. 32
c) For adding property
Table 3: Test case for adding property
Test
Case
ID
Test
Scenario
Test Steps Input test data Expected
Results
Actual
Results
Pass/
fail
TC-
5
Check
add
property
activity
with
valid
data
2) Fill up
the form
with valid
data.
3) Click
save
button.
a) Property name:
Boudha Villa
b) Property no:
20456
c) Property type:
apartment
d) Address:
Boudha,
e) Zone: Bagmati
f) District:
Kathmandu
g) Municipality:
Boudha
h) ward-no: 05
i)note: Test
property upload
User
should get
“property
successful
ly
created”
message
and
redirected
to home
activity
As
expected
pass
TC-
6
Check
signup
with
2) Fill up
the form
with
a) Property name:
Boudha Villa
b) Property no:
20456
c) Property type:
User
should get
“Enter
As
expected
pass
40. 33
invalid
data
invalid
data.
3) Click
save
button.
apartment
d) Address:
Boudha,
e) Zone: 56
f) District:
Kathmandu
g) Municipality:
Boudha
h) ward-no: 05
i)note: Test
property upload
valid
zone”
Message.
d) For adding tenant
Table 4: Test case for adding tenant
Test
Case
ID
Test
Scenar
io
Test
Steps
Input test data Expected
Results
Actual
Results
Pas
s/fai
l
TC-
7
Check
add
tenant
activit
y with
valid
data.
2) Fill up
the form
with
valid
data.
3) Click
save
button.
a) Tenant name: John
Pradhan
b) Email:
john@gmail.com
c) Mobile no: 98-
8230247
d) Address: Boudha,
e) Zone: Bagmati
User
should
get
“tenant
successfu
lly
created”
message
and
redirecte
As
expected
pass
41. 34
f) District: Kathmandu
g) Municipality:
Boudha
h) Ward-no: 05
i) Citizenship no: 20056
j) Father name: Ram
Pradhan
k) Marital status:
unmarried
l) Rent amount: 4500
m) Move in date:
2074/2/32
n) note: Test tenant
upload
d to
home
activity
TC-
8
Check
add
tenant
activit
y with
valid
data.
2) Fill up
the form
with
invalid
data.
3) Click
save
button.
a) Tenant name: John
Pradhan
b) Email: john
c) Mobile no: 98-
8230247
d) Address: Boudha,
e) Zone: Bagmati
f) District: Kathmandu
g) Municipality:
Boudha
h) Ward-no: 05
User
should
get
“Enter
valid
email”
Message.
As
expected
pass
42. 35
i) Citizenship no: 20056
j) Father name: Ram
Pradhan
k) Marital status:
unmarried
l) Rent amount: 4500
m) Move in date:
2074/2/32
n) Note: Test tenant
upload.
5.2. Integration Testing
Integration testing is a software development process in which program units are
combined and tested as groups in multiple ways.
The integration testing of the application has been done by dividing the project in to
three modules. The first module which include the login, sign up and registration page
has been tested. Then the second module which include the adding/updating/deleting
and viewing part of the property and tenant renting the property has been done. At last,
the third module which include the user profile part like viewing the user profile, editing
the profile details and changing the email and password part has been tested. All the
modules testing has been made using the AVD (android virtual device).
43. 36
5.3. System Testing
System Testing is a level of the software testing where a complete and integrated
software is tested.
The system testing has been performed by testing the whole application in virtual device
and real android device with and without the internet connection. The whole application
runs smoothly and without error with the internet connection. Without the internet
connection, the application cannot perform fully. Since the data is synchronized when
the application is connected to the internet, so without the internet connection the
application cannot function fully.
44. 37
Chapter 6: Conclusion
6.1. Conclusion
Tenant screening is a cloud based mobile application that helps the property owners to
keep record of their properties and the tenants renting the property. The application has
been developed using android studio as IDE, java as main programming language, xml
as defining layout and backend part using the firebase. All the requirement and the
objectives of the project have been fulfilled by the application. The property owner can
access all the information of the property and the tenants that he/she had added in the
application through the application from anywhere around the world.
6.2. Future scope
Currently the android application has the features of adding the property and tenants
details and displaying them only. In future, the application will also include the features
of adding the income and expense details from the property which allows the property
owner to track the financial part of the property. Similarly, application will be provided
the platform to take feedback from the tenants.
45. 38
REFERENCES
Tamada, R. 2016. Firebase Realtime Database CRUD Operation for Android. Available
at: https://www.simplifiedcoding.net/firebase-realtime-database-crud/ [Accessed 5
July. 2017].
Khan, B. 2017. Android working with Firebase Realtime Database. Available
at: https://www.androidhive.info/2016/10/android-working-with-firebase-realtime-
database/ . [Accessed 15 July. 2017].
Java T point. 2016. Android tutorial. Available
at: https://www.javatpoint.com/android-tutorial . [Accessed 24 June. 2017].
Tutorial point. 2016. Android Tutorial Available
at: https://www.tutorialspoint.com/android/index.htm. [Accessed 2 July. 2017].
Firebase. 2017. Android guides. Available
at: https://firebase.google.com/docs/android/setup . [Accessed 20 July. 2017].
Slideshare. 2017. E-Notice Application. Available
at: https://www.slideshare.net/kapoorpriyanka/report-on-enotice-app-an-android-
application . [Accessed 16 June. 2017].
Slidenerd. 2014. Android tutorial for beginners. Available at:
https://www.youtube.com/playlist?list=PLonJJ3BVjZW6hYgvtkaWvwAVvOFB7fkL
a . [Accessed 16 April. 2017].
Stellman, A. & Greene, J. (2005). Functional and Non-Functional Requirement. In
A.Stellman, & J. Greene, Applied Software Project Management (p.113). O’Reilly
Media. [Accessed 14 August. 2017].
Sadalage, P. 2014. NoSQL Databases: An overview. Available at:
https://www.thoughtworks.com/insights/blog/nosql-databases-overview . [Accessed
14 April. 2017].
52. 45
},
"ads_service": {
"status": 2
}
}
}
],
"configuration_version": "1"
}
Email authentication using firebase
auth.signInWithEmailAndPassword(email, password)
.addOnCompleteListener(LoginActivity.this, new
OnCompleteListener<AuthResult>() {
@Override
public void onComplete(@NonNull Task<AuthResult> task) {
progressBar.setVisibility(View.GONE);
if (!task.isSuccessful()) {
// there was an error
if (password.length() < 6) {
inputPassword.setError(getString(R.string.minimum_password));
} else {
Toast.makeText(LoginActivity.this,
getString(R.string.auth_failed), Toast.LENGTH_LONG).show();
}
} else {
checkIfEmailVerified();
}
}
});
private void checkIfEmailVerified()
{
FirebaseUser user = FirebaseAuth.getInstance().getCurrentUser();
if (user.isEmailVerified())
{
// user is verified, so you can finish this activity or send user to
activity which you want.
Toast.makeText(LoginActivity.this, "Successfully logged in",
Toast.LENGTH_SHORT).show();
Intent intent = new Intent(LoginActivity.this, HomeActivity.class);
startActivity(intent);
finish();
overridePendingTransition(R.anim.push_left_in,
R.anim.push_left_out);
}
else
{
// email is not verified, so just prompt the message to the user and
restart this activity.
// NOTE: don't forget to log out the user.
FirebaseAuth.getInstance().signOut();
Toast.makeText(getApplicationContext(), "Please check your email for
confirmation!...", Toast.LENGTH_SHORT).show();
//restart this activity
}
}