APPENDIX C PROJECT DESCRIPTION FORM PROJECT DESCRIPTION FORM (F2)

Index No.: 4106-05A

Title of Project: Customer Relationship and Management Web based project or not? : WEB-based System Name of Adviser(s): Ms. Wendy Vera Ramos

Statement of Objectives (a) Goals and objectives of your proposed project with measurable outcomes 1 To fulfill and accomplish all the requirements needed for us to graduate, including the construction of our proposed system. 2 To build a Customer Relationship and Management System that will be lessen the problems of the companies in their manual operations. (b) Itemized list of deliverables of the system with respect to the functionality of the system (not project study, CD etc.) user and management reports. 1 Add 2 Edit 3 Print 4 Search 5 View 6 Update (c) Scopes 1 Adding, Editing, Removing, and Viewing of information assets. 2 Monitoring of the assets Inventory. 3 Release and Deployment of Assets 4 Service asset and Configuration 5 (d) Limitations 1 The information of the entire system will only depend on the company. 2 The coverage of our system is within the assets, all Information and monitoring of the equipment. 3 Our Proposed System is accessible only on LAN Based.

(e) Reasons for choosing the proposed project? 1 Our IT Coordinator conducted a draw lots during the meeting of the 4th year IT students, where every section has a representative to pick a proposed system. Our assigned system was Airline Management System. After that is the randomly picking of our subsystems which was the Enterprise Asset Management System. 2 It is the subsystem picked by our project manager during the draw lots.

(f) Your strategy for getting started: The strategy of our group is to gather information about the proposed system and conducted brainstorming, so that, there will be no problem in working the system. The first step was to know the systems coverage, its scopes and limitations to prevent overlapping. Second, is the creation of our Gantt chart. What and when will be our project achievement and finish it in allotted time to avoid cramming. After creating the schedule, this is the time that we had conducted an interview with the people who have the knowledge about the transaction of the Asset Management and what are the other activities happens inside the company. After interviewing, its the time to implement the scientific method, from defining the problem up to making conclusion and solution. Lastly, the construction of solution to the problem identified. 1. Required Development and Testing Environment

(a) Hardware Requirements (processor, RAM, storage capacity etc.), Software Requirements (OS, Language versions, libraries etc.), Special requirements (if any) HARDWARES Processor Memory Hard Disk Drive SPECIFICATIONS 1 GHz clock speed 1 GB RAM 1 GB Disk Space

SOFTWARES Operating System

SPECIFICATIONS Windows-based (x86 or x64), Linux-based or Mac OS

Language Version Runtime Database

English (United States) Java Runtime Library 7 or latest MySQL Server 5.0 or latest

(b) How do you intend to obtain access for these facilities? Indicate the location, frequency of access to use these facilities and its approximate durations on monthly / weekly / daily basis. Admin role contains people who are generally responsible for entering information, often for other maintenance employees. Information entered may include Work Order resource transactions, Work Order completion details, and Time and Labor hours. This person might have limited maintenance knowledge and is generally responsible for supporting the maintenance department by handling information entry. Maintenance User is a maintenance person who is generally responsible for completing tasks that are assigned on a Work Order. This person reports maintenance problems using Work Requests, troubleshoots on jobs, and works on a team with other maintenance workers. Maintenance Planner or Supervisor and is often defined as a "super user". A Maintenance Planner plans and schedules maintenance jobs, manages and balances workloads over time, manages preventive maintenance strategy and scheduling, manages material requirements, monitors availability, and coordinates strategies with other departments, such as Operations, Purchasing, and Inventory.

(c) How do you intend to demonstrate your project work? Indicate access to software, hardware, data required for the demonstration. Since the programming language to be used is Java and MySQL, any Operating System Platform that supports Java Runtime Library 7 and MySQL Server 5.0. When it comes to hardware, it is not mandatory to get the latest one. The data required from the demonstration will come from the Asset Management.

(d) Will the final system be tested / evaluated by real users: Yes (e) State the way of generating test data/ test cases: To generate test data, the proposed subsystem will integrate with the other subsystems. Through this method, the result of the test will depend also on the

other subsystems performance. Another method to generate test data is to use it on its field where it will be used. It includes people or the potential users of the system how they will interact on it. Through them, they will determine if the subsystem meets its requirements in the field.

(f) State the way of determining the acceptability / success of final system: If the test results of the system is good, then the subsystems will be integrated to each other. The functions and requirements of an Enterprise Asset Management System meets its objective and its capable in integrating with the other sub systems, it was then the sign that we have met up all the demands needed to functionalize our system, it is successfully done. (g) The procedure to evaluate the performance of the system: The evaluation for the performance of the system will depend on the users that will interact with the system. Because they already know what are the basic processes/ transaction of the system, they can evaluate it by its functions, designs and its difference from the previous and existing system.

Group/individual Signature Bolor, Mary Jane P. Dasas, May Ann M. Gargar, Lolet G. Jimenez, Edison N. Ladia, Victor Oliver D.

Date: August 2013