Automated Logging System for Crown Tower University Belt

3ISC 2nd Semester A.Y 2013-2014 DIZON, Joshua S. IGNACIO, Cartleen C. JAEN, Lizeth G. NEGRETE, Charlene Mae F. SEMINIANO, Richelle B.

TABLE OF CONTENTS

Chapter 1: The Project 1.1 Introduction.. 1 1.2 Project Objectives 1 1.3 System Scope.. 2 1.4 Project Scope and Boundary. 3 1.5 Project Risks and Project Feasibility Studies 1.5.1 Risk Management.. 3 1.5.2 Organizational/Cultural Feasibility.. 4 1.5.3 Technological Feasibility.. 4 1.5.4 Schedule Feasibility 1.5.4.1 Work Breakdown Structure. 5 1.5.4.1.1 By Sequential Timeline 6 1.5.4.1.2 Gantt Chart/Milestones 7 1.5.4.2 PERT/CPM Chart. 7 1.5.5 Resource Feasibility 1.5.5.1 Staffing Plan.. 8 1.5.6 Economic Feasibility.. 9 Chapter 2: The Company 2.1 Background and History 11 2.2 Organizational Chart. 13 2.3 Contact person/s, their position and contact number.. 13 Phase I Inception Phase Chapter 3: Business Modeling 3.1 Understand the Business Environment The Current System. 14 3.1.1 Background and Problem Definition 14 3.1.1.1 Current Technical Issues 15 3.1.1.2 Needed Interface to Other Systems. 15 3.1.1.3 Existing Architecture and System Constraints 15 3.1.1.4 Stakeholders and Stakeholders Analysis Form.. 16 3.2 System Vision The Proposed System 3.2.1 System Objective. 17 3.2.2 Business Benefits 17 3.2.3 System Capabilities 18

Phase II Elaboration Phase Chapter 4: Requirements Discipline 4.1 Detailed Description of the Proposed System 19 4.2 System Requirements 4.2.1 Functional Requirements 4.2.1.1 Event List... 20 4.2.1.2 Event Decomposition.. 21 4.2.1.2.1 External Events. 21 4.2.1.2.2 Temporal Events.. 22 4.2.1.2.3 State Events................................................................... 22 4.2.1.3 Use Case Diagram....................................................................... 22 4.2.1.4 Use Case Description.. 23 4.2.1.5 Event Table... 25 4.2.1.6 Domain Class Diagram... 26 4.2.1.7 Use Case Domain Class Matrix. 26 4.2.1.8 Location Diagram. 27 4.2.1.9 System Sequence Diagram 27 4.2.1.10 Activity Diagram..... 31 4.2.1.11 State chart Diagram.. 35 4.2.2 Non-functional Requirements 4.2.2.1 Technical Requirements. 36 4.2.2.2 Performance Requirements... 36 4.2.2.3 Usability Requirements... 36 4.2.2.4 Reliability Requirements. 37 4.2.2.5 Security Requirements 37 4.3 Priority Level Requirement Table. 37 4.4 User Interface Dialogs 38 4.5 User Requirements Evaluation. 39

CHAPTER 1 THE PROJECT

1.1 INTRODUCTION

The rapid development of information and technology brought about new, innovative and helpful means to provide the basic needs of people, business and government. Information systems using the database technologies are now widely used in the public and private industries. Even small companies are beginning to implement these new technologies to their own companies. Business, may it be big or small, easily adapt to the changes and development of technology with the use of gadgets affordable and accessible to the public. These technologies help in the improvement of security in public and private places. The implementation of systems with the use of databases and other helpful gadgets has now made it easier to provide tight security to people and belongings.

1.2 PROJECT OBJECTIVES General Objective To create an automated logging system that will help the company increase the efficiency in logging transactions. This project aims to provide Crown Tower University Belt an automated logging system that will provide a faster and easier way of taking and keeping track of records of employees, unit owners and visitors that enter the condominium.

CHAPTER 2 THE COMPANY

2.1 BACKGROUND AND HISTORY History Established in 1995, Crown Asia Residences caters to the growing upper-middleincome families who are ready to move up in life to the most stylish of homes and communities. They have high expectations of what a home should be: a shelter for their children to grow in a pristine environment; a sanctuary where they can reenergize in peaceful comfort; a refuge for spending private time with their families; a haven for connecting with nature and neighbors. Crown Asia Residences' developments are designed to enhance urban living through its trademark signature homes, hometowns with which they can take pride, in choice locations across Mega Manila. The Crown Asia Residences formula balances quality communities with affordability, to fulfill the aspirations of the upper-middle-income family. These are developments master planned to enhance the lifestyles of homeowners whose expectations, needs and wants are rising along with their incomes. With this in mind, Crown Asia Residences' homes are designed for expansion. Structures are built to accommodate future enhancements and extensions to one's home.

CHAPTER 3 BUSINESS MODELING 3.1 Understanding the Business Environment The Current System The current system of Crown Tower University Belt is not automated. The authorized personnel use a manual log book to keep track of the records of the people who go in and out of the said condominium. In the current system, the visitors or every person that will go in will write their personal information and the time they entered in a manual log book then that person will hand in an identification card and leave it to the personnel in exchange of a pass card with number so that they can claim their identification card when they leave. 3.1.1 Background and Problem Definition Nowadays, automation of systems is widely implemented in all types of organizations. Technology has been rapidly advancing that companies feel the need to cope up with these changes in order to improve the services that they offer. Crown Tower University Belts logging system is still manually handled that it encounters human error that will be easily avoided with the automation of their logging system. Keeping track of the records of all the people who enter and exit the condominium is important so its necessary to have accurate information.

Phase II Elaboration Phase CHAPTER 4 REQUIREMENTS DISCIPLINE

4.1 DETAILED DESCRIPTION OF THE PROPOSED SYSTEM A narrative description of logging procedure from the front desk officer: For employees, our records are strict when it comes to time because thats where the salary is based. All employees have records on us upon hiring and when the employee shows up for work, we have a record on what time they arrived from the guards and the time they put on the record as well to verify whether the information is accurate. For unit owners, they dont have to log in and out of the building whenever they go but we do keep a detailed record on who owns the unit and how many people live there. For tenants, unit owners who decided not to live at the building are welcome to find tenants to live in their unit but detailed information are given to us. We are strict when it comes to tenants because they only rent the place and may have no real concern for the security of the building. For visitors, we ask the visitors to surrender their ID in the front desk and sign our log sheet which requires them for their name, school/company, gadgets they are carrying, the unit theyll be visiting, the purpose of their visit, the person they are visiting and the time they went in the building and the time they go out of the building which is