Chapter 1

INTRODUCTION Background of the Study Information systems (IS) are concerned with the information that computer systems can provide to aid a company, non-profit or governmental organization in defining and achieving its goals. It is also concerned with the processes that an enterprise can implement and improve using information technology. IS professionals must understand both technical and organizational factors, and must be able to help an organization determine how information and technology-enabled business processes can provide a foundation for superior organizational performance. It serves as a bridge between the technical and management communities within an organization (Information System, 2006). The system describes in data is processed for collection and distribution through a series of automated processes. The system often requires very little human interaction other than setup and maintenance. The information system is often used to access information and send it out to individuals. Those using the systems include governments, libraries, and private businesses. To make effective use of information as a business tool Information Systems are increasingly being employed to assist or help businesses share important information among themselves, to create and sustain an effective information environment. The focus of such systems is on achieving the sharing of information among the participants in an efficient and effective manner (Athakorn, 2009).
1

Further, systems are also applied to managing physical infrastructure such as buildings, condominiums, museums, parks and may others. A building information system stores and processes both building management system (BMS) data and building related configuration information, such as building and equipment descriptions and locations, point and meter descriptions, contact information for alarms, utility rates, and manufacturer and vendor information. The BMS data is stored in multiple configurations, including analog, binary, multistate, input and output. One or more mapping structures establish database relationships between the dynamic BMS data received from or destined to points, meters, and controllers on a BMS network. By combining these two types of data in a central repository, building information system services, tools and applications can be integrated through published interfaces to provide expandable functionality. Based on the mapping structures, the building information system services, tools, and applications access BMS data and corresponding configuration data to derive additional data (e.g., power consumption based on monitored current consumption), provide enhanced communications with a client (e.g., email-based alarm notification), and identify point discovery mismatches (Hull,2002). Moreover, this technology may also be applied in managing public markets, especially that most municipalities and cities in the Philippines have structures buildings composed of several stalls to house their economic activities by its constituents. However, Sta. Barbara, one of the municipalities in Pangasinan, still uses a manual system for managing information about their market building stalls. This manual process results to the problems occurring in the office. Major problems encountered by municipal
2

administrator are the duplication of information, unorganized reports and lose of information. Due to lack of database that will prevent the redundancy of records, the administrator can create two same records that result to duplication of records and reports are difficult to organize. Most of the companies or institutions big problem is losing of records because of absents of database where all records must stored and access. Automating the existing system of Sta. Barbara Market especially the office of the municipal administrator will help to provide a good quality of service to the stall owners. It will likewise result a high impact to the local community by speeds up the development process of the society, extreme industrialization, and it will bring further technological changes the information technology (Dickinson, n.d.). To be one of the offices that use an automated information system for the stall will gives the prides to the office as well as the municipality. Automation of managing the stalls information in the province will improve service of the office throughout the country and adds to industrialization and development of country. By this way, other offices and agencies might encourage to automate their transactions to be able to provide quality service they can offer on less time compare to manual process. The system is also intended to solve the problems in storing, accessing, managing, and protecting data. With the developed system, not only the municipal administrator will reap the benefits of an automated system, office works are improved also. The use of an information system for Sta. Barbara market can be of great benefit to the municipality. The process of quickly disseminating information through an automated system can save many hours of tedious labor, thus providing a cost savings for the entity needing to get that information distributed (Victoria, 2010).
3

Based on the related studies, information system is useful to different agencies and institute around the world especially on how effectively manage the data. The results show the effectiveness of the system in other fields. Like other information system, the Sta. Barbara Market Stalls Information System can be useful in the municipality to solve the problems encountered in existing system of the Municipality of Sta. Barbara. The focus of the system is on achieving the sharing of information among the participants in an efficient and effective manner. Conceptual Framework The developers used the Input-Process-Output model to illustrate the framework of the study. The input contains the existing process in the management of stall information, the hardware and software requirements for the system, and the features of the system. The process includes the phases composing the waterfall model. These phases consist of requirement analysis and software definition; system design; system implementation; system testing; and system deployment and maintenance. The output of this study is the creation of Sta. Barbara Market Stalls Information System.

Input
Process Output

Modified Waterfall Model

Process on the existing system; The hardware and software requirements for the system. Features of the developed system Requirement Analysis and Software Definition System Design System Implementation System Testing System Deployment and Maintenance

Sta. Barbara Market Stalls Information System

Feedback

Figure 1.1 Research Paradigm

Statement of the Objectives The developers aimed to design, develop and deploy Sta. Barbara Market Stalls Information System. Specifically, it tried to achieve the following objectives: 1. Determine the existing process in the management of stalls information. 2. Identify the hardware and software requirements for the system. 3. Describe the features of the system. 4. Test the system acceptability. Significance of the Study The Sta. Barbara Market Stalls Information System will bring innovation to the existing process. The creation of this system will provide benefits to the following: Municipality of Sta. Barbara. The municipality can improve the services offered with the system. The municipality can use the system to maintain the repository of stalls information and can save many hours of tedious labor in keeping, searching and retrieving stall records. Municipal Administrator. The municipal administrator can easily track and retrieve stall records to provide accurate details and generate reliable reports for the Mayor and stall owners. Market Supervisor. The developed system will help the access and monitor stall information, thus, enabling a more efficient market supervisor. Stall Owner. The developed system will facilitate stall inquiries from stall owners, thus, providing a more efficient service to them.
6

Developers. The development of this system provided avenues for the developers to apply all their knowledge and skills on software development which are necessary for future employment. Future Developer. Future developers may use this study as a reference to create similar system but with some modifications and innovations. Scope and Limitations The study focused on stalls that are for rent. The system displays the nature of the business that is suitable for particular space and prompt either the space is available or occupied. It captures data of stall owner who uses the public market facility. The system accepts payment for stall rentals. The system displays the cost of rent. Available systemgenerated reports are: Summary of Stalls Information and Stall Owner Information. The system includes the Audit Trail which tracks all activities of the system. The users of the system will have different levels of access. The system has Administrator (Municipal Administrator) has access to all features of the system while the encoder (Market Supervisor) has limited access such as adding new records and retrieving of the records. Moreover, the administrator can select and assign which modules will the user/encoder may access). This Stall Information System is programmed using Visual Basic 6.0 and runs under Windows based computers and with MS SQL server as its database.

Definition of Terms In order to have a better understanding of how the content should be analyzed, these terminologies are defined. Information System. This refers to an integrated set of components for collecting, storing, processing, and communicating information. Business firms, other organizations, and individuals in contemporary society rely on information systems to manage their operations, compete in the marketplace, supply services, and augment personal lives. Market Supervisor. This refers to person in-charge in market operations, specifically on assigning and monitoring of stalls. Municipal Administrator. This refers to the person, the right-hand of Mayor, who is incharge of managing projects launch by the municipal office including the public market. Stall. This refers to small area set off by walls in public market for business purposes. Stall Information System. This refers to a system that handles data about the stall and stall owners who use the public market facility.

Chapter 2

REVIEW OF LITERATURE Existing Process in the Management of Stalls Information In the traditional process of keeping records, the market supervisor asked stall owners the basic information such as name, address, age, business and other. The market supervisor records the information on a logbook that serve as the list of the registered stall owners in the public market. The market supervisor evaluates if the business put up in the space is suitable or not. The market supervisor has the responsibility to manage the information well including the building and its maintenance. A building information system and method processes building-related data associated with a building. The building-related data, including building management system data and configuration data associated with the building, is associatively stored in a database. A building management system service manages the building subsystem and provides the building management system data stored in the database. A data interface communicates the building related data to the database. A client interface communicates the building-related data between a client application and the data interface. Other services includes a polling service for periodically detecting point data, a metering service for periodically detecting meter data, and a rates service providing real-time price control. Client/server architecture and consistent procedural interfaces facilitate integration of additional tools and devices (Hull, 2003).

The Buildings Department (BD) is the buildings control statutory body in Hong Kong. In order to enhance the operational efficiency of the BD in handling and maintaining standards on buildings health and safety, BD engaged Azeus to develop the Building Condition Information System. The BCIS was developed a central database for keeping track of the condition of buildings in Hong Kong. It helped BD implement building safety standards, plan inspection schedules, provide building information for fire risk assessment, issue advisory letters, and monitor the status of fire directives and statutory orders. It also supported works order issuance; maintains the bill of quantity of actual works; performs automatic cost apportionment according to the ownership information. With BCIS, BD significantly streamlined its operations by leveraging the workflow and document management functions, as well as proactively monitoring the building conditions in Hong Kong (Building Condition Information System (BCIS) for Hong Kong Buildings Department, 2005). Computer based building information models either tend to be extremely complex like the IFC or COMBINE2 if they are to represent planning information such as the material they are made of and the spatial relations between them, or the models tend to be very simple volume models with some texture attached to surfaces representing only the optical appearance of a building and lacking relevant planning information (Paul, 2011). Users can search for general information on a property in the city including recorded complaints and violations, actions, applications, and inspections. Users can also search for information about trades people licensed by the Department. The information
10

provided here comes directly from the Department's Building Information System. In order to provide the best BIS (Building Information System) experience for all users and to ensure there is no degradation in system performance, the Department closely monitors user traffic. System devices are installed to monitor bandwidth utilization and high traffic volume and are set to restrict the daily bandwidth utilization to 400 MB, effective August 18, 2008. The Department will deny future access to those IP addresses in violation of this policy. In addition, the Department restricts access to users of robots, web crawlers, automatic scripts and other methods that consume excessive bandwidth to download information from BIS. When entering information in most queries, it is important to data enter complete information for fields such as Address, License Number and Job Number. Wildcard searches in most queries will not result in the retrieval of information unless specifically noted (Building Information System, 2011). According to Kanoglu (2001), Obtaining, handling and distributing information among participants in the building design process has become more difficult with increasing project complexity. In individual areas such as scheduling, estimating and drafting, it is possible to have access to computerized tools but it is clear that there is a gap in architects offices regarding the integration of these tools into a unified system. Architects work closely with engineers, clients, suppliers, and public authorities. Managing the information flow among these participants may not be much of a problem in small offices. But the larger architectural offices face serious management-related problems in the design process because of the lack of an efficient information system.

11

Hardware and Software Requirements for Stalls Information System The Systems Requirements give an introduction to the systems-related issues which managers need to consider when setting up and running an information system. It provides more detailed technical information about the specific software and hardware requirements that you will need to meet (Powell, 2000). Once the developers determine the source of the program, developers need to look at what type of hardware will be required. The users may have certain hardware requirements dictated to them that will have to be met. For example, a laser printer, a specific type of floppy drive, or a CD-ROM drive maybe required. For in-house programs, it may be more difficult to determine the hardware needed until the program specifications are complete. When additional hardware is required, developers should first determine if it is available at the facility. They may find the hardware needed is not being used where it is located and can move it to meet the new requirements. If the hardware is not available at the facility, begin the acquisition process. This process is the same as for software, except, in most cases, the requirements will have to go out on bids to several companies. With this process, it may take a long time to receive the hardware. When translating user requirements into an application, there are several things to keep in mind. It has covered the system software and hardware requirements; now, turn the attention to the memory requirements. Calculate the memory requirements carefully; it will do no one any good to create a program that cannot be run due to memory constraints of the system. Factors to be combined when calculating memory
12

requirements are: the operating system, the program, and the data to be input. By taking into consideration the memory requirements of each of these factors, there should be no problems with running the programs (Determine System Hardware Requirements, n.d.). The Features of the System Requirement analysis is very significant in developing the system. It is the process of understanding the client needs and expectations from a developed system. The requirements explain how a system should behave or a description of a system properties or attributes. It can alternatively be a statement of what an application is expected. An information system will provide the needed and storing information in a faster more convenient way by storing file of the spacers rent in a computer system that will lessen the effort of market supervisor in storing files of each student every now and then. A Building Information System (BIS) has been created, based on archived and surveyed data. Essentially a multi-sensor approach has been applied to archive the inside and the outside of the monument. The primary technology is terrestrial laser scanning. The authors treat the activities done for creating the BIS of the Santa Maria Maggiore in Bergamo, build in 1137. Public works rely on a variety of computerized systems to support daily operations. These systems are used to plan work, complete tasks, update databases, and provide public access to government information. Staff engages with work orders, asset inventories, permits, 311 and call center requests, and so on, with each system offering a different assortment of procedures and types of datasets. Likewise, many public works applications present (to external constituents and internal users) a variety of faces (or
13

interfaces) that give the appearance of disconnected functions and responsibilities, while in reality; it is one department handling many tasks (Bernandino, 2007). Modern business organizations become more and more dependent on their information systems to deal with the complexity and changeability of the context (markets) in which they operate and consequently their internal organization structures. Up-to-date, complete and accurate information has become a necessity to survive in an increasingly competitive world. Developments like dynamic cooperation networks, mass customization of products and services, and end-to-end process control require automated means to control operational business processes, for the simple reason that humans cannot oversee the entire operation in an efficient and effective way anymore. Consequently, business requirements to information systems increase at a dazzling pace (Building Information System (I), 2006). The System Acceptability Acceptance Testing is the formal testing conducted to determine whether a software system satisfies its acceptance criteria and to enable buyer to determine whether to accept the system or not. Acceptance testing is designed to determine whether software is fit for use or not. Apart from functionality of application, other factors related to business environment also play an important role. User acceptance testing is different from System Testing. System testing is invariably performed by the development team which includes developer and tester. User acceptance testing on the other hand should be carried out by the end user. This could be in the form of Alpha Testing where tests are conducted at the development site by the end users. Environment can be controlled a little
14

bit in this case. Beta Testing where test are conducted at customer site and development team do not have any control on the test environment. In both the cases, these testing might be assisted by software testers (Ramdeo, 2011). It is very important to define acceptance criteria with the buyer during the various phases of SDLC. A well defined acceptance plan will help development/QE teams by identifying user's need during software development. Acceptance Test plan must be created or reviewed by customer. Entries criteria are system Testing is completed and defects identified are either fixed or documented. Acceptance plan is prepared and resources have been identified. Test environment for the acceptance testing is available Exit criteria is the acceptance decision is made for the software. The Building Information System experience for all users and to ensure there is no degradation in system performance; the Department closely monitors user traffic. In addition, the Department restricts access to users of robots, web crawlers, automatic scripts and other methods that consume excessive bandwidth to download information from BIS (Buildings Information System, 2011). The Public Market stall information management system captures data of stall owners, ambulant vendors and PUV drivers who uses the public markets parking facility. It has Audit Trail which can tracks all activities of the system (What is qSims?, 2010). The company currently supports about 400 locations on its software program, and has historically appealed to a small, independent customer base. The Rental Information Systems has the ability to support larger companies, and they plan to pursue larger sales
15

opportunities down the road. Users track more information at the store level than any other system out there. This system has essentially been in development since 1985, and have constantly tweaked and upgraded as customers need it. With the SQL server database engine, it can replicate real-time data for instant reporting, or provide end-ofday reports, as requested. It's a really flexible system (Ruby, 2011). With the previous studies presented, the results support the usefulness of this automated information system as a method for sharing information and can be of great benefits to government institution like municipalities. The results also support the effectiveness of the system in different fields. The system proves that certain task can be accomplished within seconds. The Information System is capable of performing efficient way of monitoring and managing vacant, occupied or reserved spaces. Recommendations for making most effective use of the methods are presented as well as several of its limitations.

16

Chapter 3

METHODOLOGY Research Design The study used the waterfall model as its design. The Waterfall Model assumes the various phases of the project can be carried out and completed entirely sequentially. A detailed plan is first developed, then the requirements are thoroughly specified, then the system is designed down to the algorithm, then it is programmed, tested, and installed. The developers used the modified waterfall model as the research design for the study. The modified waterfall model in software engineering came into existence because of the defects in the traditional waterfall model (Jorwekar, n.d.).

Requirement Analysis and Software Definition

System Design

System Implementation

System Testing

System Deployment and Maintenance

Figure 3.1 Modified Waterfall Model Diagram

17

Many company system and projects today are based on the modified waterfall approach. For projects that build well-understood applications, a modified waterfall approach is appropriate. Even the systems based on an object-oriented approach are built with modified waterfall approaches. Requirement Analysis and Software Definition. This is the first phase of waterfall model which includes a meeting with the customer to understand his requirements. This is the most crucial phase as any misinterpretation at this stage may give rise to validation issues later. The software definition must be detailed and accurate with no ambiguities. It is very important to understand the customer requirements and expectations so that the end product meets his specifications. In this phase, the existing process in the management of stall information, and the hardware and software specifications for the system were identified since there are necessary requirements for software definition. System Design. The customer requirements are broken down into logical modules for the ease of implementation. Also the inter relation between the various logical modules is established at this stage. Algorithms and diagrams defining the scope and objective of each logical model are developed. In short, this phase lays a fundamental for actual programming and implementation. In this phase, the overall designs of the system that illustrate the features of the system were conceptualized and constructed. System Implementation. This is the software process in which actual coding takes place. A software program is written based upon the algorithm designed in the
18

system design phase. A piece of code is written for every module and checked for the output. In this phase, features of the system are still described. It is actually in this phase where the designed system is embedded by codes. System Testing. The programmatically implemented software module is tested for the correct output. Bugs, errors are removed at this stage. In the process of software testing, a series of tests and test cases are performed to check the module for bugs, faults and other errors. In this phase, the system is evaluated by the developers as to whether it meets the conceptualized features. Erroneous codes are rewritten and tested again until desired output is achieved. System Deployment and Maintenance. This is the final phase of the waterfall model, in which the completed software product is handed over to the client after alpha, beta testing. After the software has been deployed on the client site, it is the duty of the software development team to undertake routine maintenance activities by visiting the client site. In this phase, the developers test the acceptability of the system to the users using the questionnaire, deploy and maintain the system on deployment and maintenance phase. It involved the installation of the system to the partner company as well as maintaining of system.

19

Sources of Data The primary source of data to determine the existing process in the management of stalls information was Mr. Ernesto Pamoceno (Municipal Administrator) and Mr. Lito Bartholome (Market Supervisor). The developers asked the municipal administrator and market supervisor about the process involved in the existing system and the common problems they often encountered. To identify the hardware and software specifications and to describe the features of the system, the developers used the web documents. To test the system acceptability, developers floated questionnaires to the municipal administrator, market supervisor and stall owners. Instrumentation and Data Collection The developers used structured interview, documents (public market and web) and questionnaire as instruments to gathers data meet the objectives states in the study. Structured Interview. The developers conducted interview with Mr. Ernesto Pamoceno (Municipal Administrator) and Mr. Lito Bartholome (Market Supervisor). The developers used an interview guide containing a set of questions that aims to determine the existing process on keeping the stall records and information about the stall. (See Appendix A) Public Market Documents. Logbooks, receipt, application form and other sample forms were used by the developers as instrument to gather data to meet the objectives stated in the study. This documents used to decision-making and strategic planning and resource. (See Appendix B)
20

Web Documents. Web documents, such as articles, blogs and pdf files related to the study, used as tools to help the developers on constructing the system requirements for the system and what are possible capabilities of the system. Questionnaire. Questionnaire was used to test the system acceptability. Developers asked the employees of municipality and stall owners if the system fits the municipality needs and can satisfy the users. The questionnaire was used as the main data-gathering instrument for this study. The questionnaire was divided into two main sections: a profile and the survey proper. The profile contains socio-demographic characteristics of the respondents such as age, gender, civil status, and many others. The questionnaire proper section contains questions that identify whether the system is acceptable for them or not. In this survey type, four choices are provided for every question or statement and its on checklist format. The choices represent the degree of agreement each respondent has on the given question. (See Appendix C) Tools for Data Analysis As tools for data analysis, the developers used Entity- Relationship Diagram, Use Case diagram, and Wireframe. Entity- Relationship Diagram. The developers used ERD to identify the hardware and software specifications for the system. With ERD, features of the developed system have been conceptualized. An entity-relationship diagram is a specialized graphic that illustrates the interrelationships between entities in a database. ER diagrams often use symbols to represent three different types of information (Runciman, 2011). (See Appendix D)
21

Use Case Diagram. UCD helps the developers to determine the existing process in managing the information of stalls. A diagram showing the various user roles and the way those interact with the system. The developers choose the use case diagram to represent the flow of the system (uCertify,2008). (See Appendix E) Database Schema. A database schema is a collection of meta-data that describes the relations in a database. A schema can be simply described as the "layout" of a database or the blueprint that outlines the way data is organized into tables (Chapple,2011). (See Appendix F) Database Instance. The term instance is typically used to describe complete database environments including the RDBMS, table structure, stored procedures and other functionalities. It is most commonly used when the administrators describes multiple instances of same database (Chapple,2011). (See Appendix G) Flowchart. Flow charts are easy-to-understand diagrams showing how steps in a process fit together. This makes them useful tools for communicating how processes work, and for clearly documenting how a particular job is done (Manktelow, 2011). (See Appendix H) Percentage Mean. A proportion in relation to a whole (which is usually the amount per hundred). The respondents are Municipal Administrator, Market Supervisor and stall owners. Percentage Mean is use to test the system acceptability which is the last objectives of the study.

22

Chapter 4

DISCUSSION OF FINDINGS Existing Process in the Management of Stalls Information Municipality of Sta. Barbara uses a manual system for managing information about their market building stalls. The Municipal Administrator and Market Supervisor also use labor-intensive way in recording and retrieving stall's information. Figure 4.1 shows the graphical representation of the existing system.
BEGIN

Applicant choose a stall he wants to rent

YES

New applicant?

NO

Pay Rent

Market Supervisor gets the applicants basic information

Issue Receipt

Record the information in a log book

Receipt

Evaluate

Is the application approved? NO

YES

Save the records

Applicant pay the 2 months deposit and 1 month advance

Issue Receipt

END

Figure 4.1 Flowchart of existing process

23

The transaction starts with getting the basic information such as name, address, contact number and business of the applicant. Market supervisor records the information on a logbook that serves as the list for the municipal. The Market Supervisor will decide where will be the appropriate stall for the given business. Businesses that are related to food are highly recommended to place 2 or 3 stalls away from the comfort room. The x marks are stalls that not suitable for foodrelated business. Figure 4.2 shows the recommended stalls for food-related business.

Figure 4.2 Recommended stalls for food-related business

24

The applicant will pay the rent for the one month deposit and 2 months advance. The old stall owner pays only their monthly rent. The payment details include the stall, owners name, date of payment, validity date, and amount. The payment is usually valid for one month. But if the payment is for two months, then the stall is unavailable for two months. The rent is varies depends on the location of the stall. The stalls are categorized into Front Corner, Back Corner, In Between, Vegetable Section, Meat Section, Fish Section and Fruit Section in which the rent in front corner has the highest rent, back corner stalls have the second highest rent, in between stalls have a lower rent compare to front and back corner, meat section stalls have minimum cost of rent, fish section stalls have lower rent compare to meat section stalls, fruit section stalls have second to the lowest rent and vegetable section stalls have the lowest rent. Then, Market Supervisor issues a receipt. Market Supervisor keeps the records in the cabinet where all transaction papers were stored. The information gathered was used to serve as records for stalls. This information are created and maintained for the sole purpose of documentation of the stalls information. Record keeping is about the management of records to preserve the stall records and tracking who are the stall owners rented the stalls.

25

Hardware and Software Requirements for Stalls Information System This section presents the minimum hardware and software requirements needed for the system to function properly. Table 4.1 Hardware requirements for stalls information system Hardware Parts Requirements Memory 512MB or above Processor 800 MHz or above Hard Disk 80 GB or above Monitor 14 CRT Peripherals Mouse, Keyboard, Printer

In terms of memory, 512 MB is the minimum requirement because the system only consumes less memory of the computer and 512 MB Memory is enough to properly run the system. The speed of the system varies on the processor of the computer, 800 MHz can provide the speed that the system needs. The processor's capabilities dictate the maximum performance of a system. A computer relies on its hard drive to store nearly everything that it needs to operate, including all of its programs and data. 80 G hard disk can handle the executable file and application software. Minimum monitor is at least 14 CRT to clearly view the floor map. Some peripherals, such as mouse, keyboard, printer, are also needed. Table 4.2 Software requirements for stalls information system Sofware Specification Operating System Windows XP or higher versions Application Software Visual Basic 6.0, Wampp Server 2.1, and MySQL Connector ODBC 5.1

In terms of operating system, windows XP is the minimum because the system only runs on Windows-based computer and for much better graphics. Visual basic 6.0
26

was used to developed the system because it is integrated into many different software applications. It provides a common macro language included with many Microsoft applications. It is good for developing windows interfaces, it invokes fragments of basic code when the user perform certain operations on graphical objects on screen. WAMP Server 2.1 is a form of mini-server that can run on almost any Windows Operating System. WAMP includes Apache 2, PHP 5 (SMTP ports are disabled), and MySQL (phpMyAdmin and SQLitemanager are installed to manage your databases) preinstalled. The MySQL Connector ODBC 5.1 provide access to a MySQL database using the industry standard Open Database Connectivity (ODBC) API. Connector/ODBC can be used on all major platforms supported by MySQL. You can install it on Windows 95, 98, Me, NT, 2000, XP, 2003, Vista and 7. The developers used the web documents, such as articles, blogs and pdf files related to the study, to identify the hardware and software requirements for the system. Those web documents were used by the developers as reference on stating the minimum requirements. The tables shows the software and hardware requirements for the Sta. Barbara Market Stalls Information System to run this system effective and efficient. These system requirements are sufficient for installing and running the application; however, for best results, expand the hardware requirements to optimize performance of the system.

27

The Features of the System The developed system has security features wherein only authorize personnel can access the system. Municipal Administrator and Market Supervisor are given the privileged to access the system through their username and password. The users of the system will have different levels of access. The system has Administrator (Municipal Administrator) has access to all features of the system while the encoder (Market Supervisor) has limited access such as adding new records and retrieving of the records. Moreover, the administrator can select and assign which modules will the user/encoder may access). The system has capability to search stall records using the stall ID number. With the use of this system, it increases accessibility to information faster search and retrievals, reduced workload, redundancy, paperwork, and clutter. The system has capability to minimize the manual operations and generating print-outs. It is also capable of accepting the stall owner information. The system includes the Audit Trail which tracks all activities of the system.

28

The Developed Sta. Barbara Market Stalls Information System

Screen Shots

Plate 4.1 Login Form Plate 4.1 provide security, users will be requested to login first before they can access the system. Municipal Administrator and Market Supervisor are given the privileged to access the system through their username and password. The users of the system will have different levels of access.

29

Plate 4.2 Registration Form Plate 4.2 allows the user to register new accounts on particular stall. Basic stall information including the first name, middle name, last name, birthday, gender, address, contact number, business name and nature are encode then save on database upon clicking the save button. The cancel button commands the system to cancel the registration form. The asterisk fields are required fields which means that the user need to input data on the fields. The system provides auto-generate stall owner id.

30

Plate 4.3 Update Rent Form Plate 4.3 display the current rent of particular stall. Rent is categorized into front corner, back corner, in between, fish section, meat section and vegetable section. The rent varies on the position of the stall. The system provides fields where the users can modify the current rent. Update button commands the system to update the current rent.

31

Plate 4.4 Change Password Form Plate 4.4 allows the users to change their password using the username as reference. The forms requested the user to enter the current password, the new password then confirm the new password.

32

Plate 4.5 Search Stall Record Form Plate 4.5 allows the user to search stall record using stall id, stall owner id, first name or last name. Stall records are display on list view and can update by selecting the record and click the update button located on lower right of the form. Print button commands the system to print the selected record from the list view.

33

Plate 4.6 Main Form Plate 4.6 display the main form of the developed system. Menus include the different functionalities of the developed system. Current login user, time and date are indicated in status bar of the main form. Main form provides shortcuts to access all forms of developed system. The available button is a shortcut to access the graphical representation of building. The rent button is a shortcut to access the form where stall information can view. The billing button is a shortcut to access the billing form. The history button is a shortcut to access the history form. The search button is a shortcut to access the search form. The due date is a shortcut to access the form that displays the due date of stalls. Close button allows the user to close the system. Menu bar is also present consisting the file menu, transaction menu, report menu, utility menu and about menu.
34

Plate 4.7 Ground Floor Form Plate 4.7 display the top view of the ground floor. Each stall has its own id that is label. When the user clicks the label, the system prompt if the selected stall is occupied or not. If the stall is vacant, registration form will appears. The rectangular figures represent the stall. Shortcuts to rent form and search form are available in this form. Refresh button allows the user to refresh the form.

35

Plate 4.8 View Rent Form Plate 4.8 display the rent and information of the stall. The details include the stall id, rent, category, dimension of the stall, facilities included in the stall and short description about the stall. The rectangular figures represent the stall with corresponding label and every label is clickable in which when user click the label, it displays the stall information. Shortcuts to available form and search form are available in this form. Refresh button allows the user to refresh the form.

36

Plate 4.9 History Form Plate 4.9 displays the history of stall. It displays who are rented the stall for the pass months or years. When the user double clicks the item, another form will display asking the user to pay rent to be able to activate the account. All inactive account can be search in this form. Shortcuts to access available form, rent form, billing form, search form are also present.

37

Plate 4.10 Monthly Collection Form Plate 4.10 allows the user to view the monthly collection given by the month and year. By clicking the search button, it only displays the collection during the selected month and year. Total of monthly collection displays after clicking the total button. Preview of the data report containing the monthly collection will be possible when clicking the print button.

38

Plate 4.11 Due date Form Plate 4.11 displays the pending stalls. Certain stall will be pending if the owner does not yet pay his rent after his due date. Double click the item will display the information of the pending stall and ask the user whether to deactivate the account or not. When the user deactivated the account, the stall will remove in pending and it will turn to available.

39

Plate 4.12 Billing Form Plate 4.12 allows the user to compute the bill of the stall owner. The payment details include the stall id, owner, rent, category, start and end date, amount and change. The period of validity of the payment is compute by the system when the user input the amount. Preview of the official receipt will displays upon clicking the preview button.

40

Plate 4.13 Summary Report Plate 4.13 display the summary of stall records. It has four columns including the stall id, the owner, the business and the remark. This data report is ready to print. It includes the logo of the municipality and the date of printing. It provides the preview of report before printing in which the zoom function is available to zoom in or zoom out the preview to better examine the format of report. Print button, located at upper left of the report, allows printing the report.

41

Plate 4.14 Monthly Collection Report Plate 4.14 is the preview of the monthly collection. It contains five columns including the stall, owner, amount, date of payment and personnel who is in charge. Total of monthly collection is also been included and located in lower part of the report. Month and year of the collection is also indicated in the upper part of the report. . It provides the preview of report before printing in which the zoom function is available to zoom in or zoom out the preview to better examine the format of report. Print button, located at upper left of the report, allows printing the report.

42

The System Acceptability The stall owners and the end-users were asked by the developers to evaluate the acceptability of the system through the use of a survey questionnaire. Excellent coding strategies are applied to ensure that the system works smoothly and hassle free. Upon finishing the system developmental stage, the developers conducted a testing to ensure its functionality and acceptability. Table 4.3 System Evaluation According to Miscellaneous Miscellaneous 1. Displays appropriate error messages and error icons based on the situation. 2. Buttons should functions as expected. 3. Forms should be displayed and modal if necessary. 4. Menus are arranged by and group according to its uses. 5. Keyboard shortcuts should be provided for buttons and menus. 6. Close button is provided for each form. 7. Reports should be printed as close as possible to its view. 8. Tab index should be arranged according to the sequence of all objects. 9. Default values for textbox or any input box should are specified. 10. Scroll bar shows automatically when needed. 11. List box allows single select, either by mouse or arrow keys. 12. On a drop down list, clicking the arrow will give list of options available to the users. Average

(%) Accepted 100% 100% 100% 80% 100% 70% 100% 100% 80% 100% 100% 100% 87.5%

Table 4.3 shows the evaluation result of the acceptance testing based from the miscellaneous properties of the system. About 87.5 percent respondents accepted the miscellaneous testing as shown in table 4.3.

43

Table 4.4 System Evaluation According to Interface-related Interface-related 1. Same theme is applied on all modules and main switch board. 2. Similar object should be group by a box or a grouping object. 3. Uses at most three colour combinations. 4. Closing a form will ask user to confirm before proceeding. Average

(%) Accepted 80% 90% 50% 100% 80%

Table 4.4 shows the result of the evaluation testing done for the acceptance of the system for interface-relation. The result of this testing produced a 80 percent score for the acceptance testing of the system basing from the interface-relation which is reflected in table 4.4. Table 4.5 System Evaluation According to Database-related Database- related 1. Data structures should be available only for the administrative level. 2. Choose proper DBMS application. 3. Database / tables should be open / closed accordingly. 4. Data types for each field will assigned properly. 5. Maximum lengths of fields are set. 6. Primary key are determined and utilized. 7. Records are stored in table as entered in the interface. 8. Retrieval of records is properly done. 9. SQL statements are used in accessing records. 10. Create users and sets of privileges for each user. Average

(%) Accepted 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100%

Table 4.5 shows the result of the evaluation testing done for the acceptance of the system for database-related. The result of this testing produced a 100 percent score for the acceptance testing of the system basing from database which is reflected in table 4.5.

44

Table 4.6 System Evaluation According to Security-related Security- related 1. Username and password should be encrypted. 2. For multiple users, accessibility level should be implemented. 3. Do not allow other user to access accounts except if it has administrative level. 4. Administrative level can create another administrative and lower level access. 5. Lower level access can be manipulated by an administrative level. Average

(%) Accepted 100% 100% 100% 100% 100% 100%

Table 4.6 shows the result of the evaluation testing done for the acceptance of the system for the security-related requirements. The result of this testing produced a 100 percent score for the acceptance testing of the system basing from the security-related requirements which is reflected in table 4.6. Table 4.7 System Evaluation According to Usability Usability 1. The end user shall be able to place and order within thirty seconds. 2. The end user shall be able to access any page within four seconds 3. Reports were organized based on companys standard. 4. Previewing of reports or related documents before printing should work properly. 5. Amateur and advance users can run the GUI 6. Display should look good 7. Software must be intuitive or easily understood after reading the rules. 8. Comfortable layout that accommodates beginners as well as veterans. Average .

(%) Accepted 100% 100% 90% 100% 100% 80% 100% 100% 96.25%

Table 4.7 shows the result of the evaluation testing done for the acceptance of the system for the system usability. The result of this testing produced a 96.25 percent score

45

for the acceptance testing of the system basing from the usability properties of the system which is reflected in table 4.7. Table 4.8 System Evaluation According to Performance Performance 1. Loading of a request will be loaded within 30 seconds. 2. The report should display within 60 seconds 3. Five (5) concurrent transactions could be done within 60 seconds. Average

(%) Accepted 100% 100% 70% 90%

Table 4.8 shows the result of the evaluation testing done for the acceptance of the system for the system performance. The result of this testing produced 90 percent score for the acceptance testing of the system basing from the performance properties of the system which is reflected in table 4.8. Table 4.9 System Evaluation According to Maintainability Maintainability 1. System was designed under a licensed application that technical assistance is guaranteed 2. Support for new capabilities or ability to exploit new technologies 3. Support for additional users 4. Needs to user minimal system requirements 5. The application uses a programming framework Average

(%) Accepted 100% 100% 100% 100% 100% 100%

Table 4.9 shows the result of the evaluation testing done for the acceptance of the system for system maintainability. The result of this testing produced 100 percent score for the acceptance testing of the system basing from the maintainability properties of the system which is reflected in table 4.9.

46

Table 4.10 System Evaluation According to Portability Portability 1. System could run on PC hardware 2. System could run on Windows OS Average (%) Accepted 100% 100% 100%

Table 4.10 shows the result of the evaluation testing done for the acceptance of the system for system portability. The result of this testing produced a 100 percent score for the acceptance testing of the system basing from the portability properties of the system which in table 4.10 Table 4.11 System Evaluation According to Security Security 1. User authentication shall be via the single sign on system. 2. Verify that the system does not allow invalid usernames and passwords 3. User should be given login information that works after successful completion. 4. The password should be encrypted for safety 5. Password control ( including constraints for passwords content, reuse, and frequency of change ) Average

(%) Accepted 100% 100% 100% 100% 100% 100%

Table 4.11 shows the result of the evaluation testing done for the acceptance of the system for the security-related requirements. The result of this testing produced a 100 percent score for the acceptance testing of the system basing from the security-related requirements which is reflected in table 4.11. Through the survey, the researchers find out that the stall owners and end users were strongly agree that the system complies their requirements and that represented by
47

94. 36% overall percentage mean. With this, the researchers were able to determine that they are accepted the system and willing to adopt the system.

48

Chapter 5

SUMMARY, CONCLUSIONS, AND RECOMMENDATIONS Summary The development of Stalls Information System for Sta. Barbara Market is initiating new technology for the local government agencies. This system converts information into digital format that can be able to produce efficient and accurate outputs that can be done in paper. The focus of this system is on achieving the sharing of information among the users in an efficient and effective manner. Today, it is more important to make use of computerized system on daily work routine in offices. The developers aimed to design, develop and deploy Sta. Barbara Market Stalls Information System. Specifically, it tried to achieve the following objectives: determine the existing process in the management of stalls information; identify the hardware and software requirements for the system; describe the features of the proposed Sta. Barbara Market Stalls Information System and test the system acceptability. The developers used the waterfall model as its research design. The Waterfall Model assumes the various phases of the project can be carried out and completed entirely sequentially. In Requirement Analysis and Software Definition, the developers conducted series of interviews and identified the scope and limitations of the Sta. Barbara Market Stalls Information System. The hardware and software specifications for the system were identified since there are necessary requirements for software definition. In the system design, the overall designs of the system that illustrate the features of the
49

system were conceptualized and constructed. In system implementation, features of the system are still described. It is actually in this phase where the designed system is embedded by codes. Finally, in system testing, the system is evaluated by the developers as to whether it meets the conceptualized features. Erroneous codes are rewritten and tested again until desired output is achieved. Municipality of Sta. Barbara uses a manual system for managing information about their market building stalls. The Municipal Administrator and Market Supervisor also used manual system in recording and retrieving stall's information. The hardware requirements of the developed system include a processor with 800 MHz or above, 512MB or above memory, 80 GB or above hard disk storage, 14CRT monitor, and peripherals such as mouse, keyboard, and printer while the software requirements includes Windows XP or higher versions of operating system and Visual Basic 6.0, Wampp Server 2.1, and MySQL Connector ODBC 5.1 for the application software. The developed system has security features wherein only authorize personnel can access the system. Municipal Administrator and Market Supervisor are given the privileged to access the system through their username and password. The system has capability to search stall records using the stall ID number. With the use of this system, it increases accessibility to information faster search and retrievals, reduced workload, redundancy, paperwork, and clutter. The system has capability to minimize the manual operations and generating print-outs. It is also capable of accepting the stall owner information. The system includes the Audit Trail which tracks all activities of the system.

50

Upon finishing the system developmental stage, the developers conducted a testing to ensure its functionality and acceptability. The stall owners and the end-users were asked by the developers to evaluate the acceptability of the system through the use of a survey questionnaire. Conclusions Based on the findings, the developers were able to identify the existing process in the management of stalls information of Sta. Barbara. This process is having difficulties in managing stall records. The developers found out that with the developed system, those difficulties were solved. With profound study of the system, the developers conclude the Barbara Public Market Stalls Information System needs the manual process of their transactions between the stall owner and the Municipal Admin or the Market Supervisor. In short, the existing process ignores the benefits of modern technology to improve the services given by government agencies. The minimal software and hardware requirements can be use to deploy the system. The features of the developed system provide service with improved accessibility, accuracy and generation of reports on the relevant stall records. The features such as security, updating, retrieving stall records are essential features of the system that lead to the end-user to accept the system. The acceptability test finds out that the end-users and stall owners were strongly agree that the features of the system complies their requirements. The developers were

51

able to determine that the end-users and stall owners were willing to adopt the developed system. Recommendations The developers recommend the implementation of the developed system to speed up the process of managing stall records and generating summary reports. The use of the developed system will improve the process and services offered by the office. The developers recommend the office to have the required software and hardware requirement to be able to deploy the developed system. Proper maintenance should implement by the office to ensure that the system functions well. The developers recommend that upon implementation of the system, the endusers should undergo training before using the system to maximize its usage. The developers recommend to future developers to integrate the system in terms of managing stall like including the business permit processing.

52

Bibliography Websites: Athakorn, D. (2009). What is an automated system. Retrieved July 25, 2011, from http://www.wisegeek.com/what-is-an-automated-information-system.htm Bernandino, S. (2007). Building a Public Works Information System. Retrieved August 8, 2011, from http://www.esri.com Chappel M. (2011). Database Schema and Instance. Retrieved September 29, 2011, from http://databases.about.com/cs/specificproducts/g/er.htm Dickinson, P. (n.d.). Benefits of Automation. Retrieved from July 23, 2011, from http://www.lifehack.org/articles/productivity/the-benefits-of-automation.html Hull, J. (2002). Database for a remotely accessible building information system. Retrieved September 29,2011, from http://www.google.com.ph/patents?hl=tl&lr=&vid=USPAT6487457&id=QqALA AAAEBAJ&oi=fnd&dq=%22building+information+system%22&printsec=abstra ct#v=onepage&q&f=false Hull, J. (2003). Remotely accessible building information system. Retrieved September 29,2011, from http://www.google.com.ph/patents?lr=&vid=USPAT6598056&dq=%22building+ information+system%22&printsec=abstract&id=YfYOAAAAEBAJ#v=onepage &q&f=false Jorwekar, S. (n.d.). Waterfall - Software Development Model. Retrieved August 9, 2011, from http://www.buzzle.com/editorials/3-13-2005-67039.asp Kanoglu, P. (2001). Information System. Retrieved August 8,2011, from http://knowledge.cta.int/en/Dossiers/S-T-Issues-in-Perspective/MIS-forenvironmental-monitoring/Articles/Information-Systems Manktelow, P. (2011). Flow charts Symbols. Retrieved September 29,201, from http://www.patton-patton.com/basic_flow_chart_symbols.htm Paul, N. (2011). A Complex-Based Building Information System. Retrieved September 30,2011, from http://kit.academia.edu/NorbertPaul/Papers/331790/A_ComplexBased_Building_Information_System
53

Powell, A. (2000). System requirements specifics, hardware and software. Retrieved August 6, 2011, from http://www.desire.org/handbook/3-1.html Ramdeo, A. (2011). User Acceptance Testing. Retrieved September 29, 2011, from http://www.testinggeek.com/user-acceptance-testing Renner, S. (2003). Building Information Systems for Network-Centric Warfare. Retrieved August 8, 2011, from sar@mitre.org Ruby, D. (2011). Rental Information Systems; The Name Says it All For RTO Dealers. Retrieved August 8, 2011, from http://rtoonline.com/Content/Article/aug08/ rentdirect_primetime088508.asp?ptid=89563522 Runciman, W. (2011). Entity-Relationship Diagram. Retrieved September 29, 2011, from http://it.toolbox.com/wiki/index.php/Entity_Relationship_Diagram Sil, Y. (2011). Frequently Count. Retrieved September 28, 2011, from http://www.sil.org/lingualinks/literacy/referencematerials/glossaryofliteracyterms/ WhatIsAFrequencyCount.htm Victoria, A. (2009). Reform of the State and Public Programs. Retrieved July 23, 2011, from http://www.lifehack.org/articles/productivity/ Reform-of-the-State-andPublic-Programs.html Building Information System (I). (2006). Retrieved August 8, 2011, from http://www.anarchitecture.com/2006/08/building-information-system-i.html Buildings Information System. (2011). Retrieved August 8, 2011, from http://a810bisweb.nyc.gov Building Condition Information System (BCIS) for Hong Kong Buildings Department. (2005). Retrieved August 8, 2011, from http://www.azeus.com/en/BCIS.jsp Determine System Hardware Requirements. (n.d.). Retrieved August 6, 2011, from http://www.tpub.com/content/istts/14223/css/14223_98.htm Information System. (2006). Retrieved July 31, 2011, from http://computingcareers.acm.org/?page_id=77 uCertify (2011). Retrieved September 29, 2011, from http://www.ucertify.com/article/use-case-diagram.html
54

What is qSims?. (2010). Retrieved August 8, 2011, from http://qtechbpo.com/component/ content /article/88-qmas-quality-market-administration-system

55

Appendix A Structured Interview Interview with Mr. Ernesto Pamuceno, the Municipal Administrator of Sta. Barbara. Q: What services do the department offers? A: Assist the local chief executive in the management and operation of municipality and other operations. Q: What particular process do you perform? A: Supervisor and management of the municipality operations. Q: What is your task as Municipal Administrator? A: Supervisor and management of the municipality operations. Q: How many stall owners are now occupying the space? A: As of now, we have 200 stall owners. Q: Who can rent the space? A: Everybody as long as they comply with the requirements. Q: How they can rent the space? A: All transactions will be done in office. Q: What are the requirements needed to rent a space? A: Valid ID only. Q: How did the stall owner pays their rental fee? A: Market Supervisor visits each stall to collect their payment monthly or stall owner directly pay in the office. Q: Do you accept credit card as payment for rental fee? A: No Q: How do you keep your stalls records? A: Store in a logbook and envelopes. Q: What problems do you mostly encounter in keeping your spacer records? A: Duplication of record and unorganized reports. Q: How do you deal with those problems? A: Be careful in managing records.
56

Q: How many computers does the department have? A: 4 computers Q: What are the things you need in keeping the stalls records? A: Stall informations Q: What can you say about Information System? A: It seems like a big help to our department and to staffs. Q: Do you want to have Information System in your department? A: Yes Q: Do you have an employee who can handle such system? A: Yes, we have trained personnels. Q: Do you see that an Information System is a big help to your daily routine? A: Yes, because we need to adopt the modern way in managing records.

57

Appendix B Public Documents Ground Floor

58

Second Floor

59

Appendix C Questionnaire

1. What service do the department offers? __________________________________________________________________ __________________________________________________________________ 2. What particular process do you perform? __________________________________________________________________ __________________________________________________________________ 3. What is your task as Municipal Administrator? __________________________________________________________________ __________________________________________________________________ 4. How many stall owners are now occupying the space? __________________________________________________________________ __________________________________________________________________ 5. Who can rent the space? __________________________________________________________________ __________________________________________________________________ 6. How they can rent the space? __________________________________________________________________ __________________________________________________________________ 7. What are the requirements needed to rent a space? __________________________________________________________________ __________________________________________________________________ 8. How did the stall owner pay their rental fee? __________________________________________________________________ __________________________________________________________________ 9. Do you accept credit card as payment for rental fee? __________________________________________________________________ __________________________________________________________________ 10. What problems do you mostly encounter in keeping your spacer records? __________________________________________________________________ __________________________________________________________________ 11. How do you deal with those problems? __________________________________________________________________ __________________________________________________________________ 12. How many computers does the department have?
60

__________________________________________________________________ __________________________________________________________________ 13. What are the things you need in keeping the stalls records? __________________________________________________________________ __________________________________________________________________ 14. What can you say about Information System? __________________________________________________________________ __________________________________________________________________ 15. Do you want to have Information System in your department? __________________________________________________________________ __________________________________________________________________ 16. Do you have an employee who can handle such system? __________________________________________________________________ __________________________________________________________________ 17. Do you see that an Information System is a big help to your daily routine? __________________________________________________________________ __________________________________________________________________

61

Appendix D Entity- Relationship Diagram

tblRentRate

Front_corner back_corner In_between Vegetable_section Meat_section Fish_section Fruit_section

tblStall Stall_id Stall_owner_id Business_name Business_nature Remark end EndMonth EndDay EndYear tblOwner PK Stall_owner_id F_name M_Name L_name BMonth BDay BYear Age Gender Address contact_no Created_by Date_register

tblLogin

username userpass access_level

tblBilling tblAuditTrail PK Transaction_no Transaction Created_by Date Stall_id Payer Amout Start End Date_Payment InChange ChangeMoney

62

Appendix E Use Case Diagram

ud cl in << > e>

Verify user account
Municipal Administrator

Login

Create record Search record View record and Rent Print Report and receipt Update record

Market Supervisor

Audit trail

Logout

Pay Rent

Received receipt
Stall Owner

63

Appendix F Database Schema

tblLogin Field username userpass access_level tblStall Field Stall_ID Business_name Business_nature Remark End EndMonth EndDay EndYear tblOwner Field Stall_owner_id F_name M_name L_name BMonth BDay BYear Age Gender Address contact_no Created_by Date_register tblAuditTrail Field Transaction_no Transaction Date Created_by

Type varchar(20) varchar(20) varchar(15)

Description Username Password Access level

Type varchar(10) vachar40) varchar(40) varchar(10) Varchar(10) Varchar(10) Int(2) Int(4)

Description Stall ID Business name Business nature Remark End Due Month Due Day Due Year

Type int(10) varchar(30) Varchar(30) varchar(30) Varchar(10) Int(2) Int(4) int(2) varchar(6) varchar(64) varchar(20) varchar(20) varchar(20)

Description Stall Owner ID First Name Middle Name Last Name Birth month Birth day Birth year Age Gender Address Contact Number Created by Date of registration

Type int (10) varchar(30) varchar(20) varchar(10)

64

Description Transaction Number Transaction Date Created by

tblBilling Field Stall_owner_id Amount Start End Date_payment inCharge ChangeMoney tblRentRate Field Front_corner Back_corner In_between Fish_section Meat_section Vegetable_section

Type int(10) int(15) varchar(15) varchar(15) varchar(15) Varchar(20) Varchar(20)

Description Stall Owner ID Amount Payment for Payment until Date of payment In Charge personnel Change

Type int (15) int (15) int(15) int(15) int(15) int(15)

Description Front corner rent Back corner rent In Between rent Fish section rent Meat section rent Vegetable section rent

65

Appendix G Database Instance

tblLogin Username frozenfire 123 ikaw thesis Admin tblStall Stall_Id 1A 1B 1C 1D 1E

Userpass Mond 123 Avnoi Hirap Admin

Access_level encoder encoder admin admin admin

Stall_owner_id Business_name 1 RTM Internet Cafe 2 3 4 5 Noemi Carenderia Jc Meat Shop Antukin Barber shop Ben Tapa Station

Business_nature Internet Cafe Food Food Barber shop Meat Shop

Remark Occupied Occupied Occupied Occupied Occupied

End 2/7/2012 2/8/2012 2/12/2012 2/17/2012 3/10/2012

EndMonth 2 2 2 2 3

EndDay 7 8 12 17 10

EndYear 2012 2012 2012 2012 2012

tblOwner Stall_owner _id 1 2 3 4 5

F_name Raymond Noemi Jc Jim Marvin

M_name Terrado Carrera Soriano Posadas Fernandez

L_name Macaraeg Villanueva Mejia Ceralde Cardenas

BMonth October March August October May

BDay 25 12 10 03 31

BYear 1991 1991 1992 1991 1991

66

Age 20

Gender Male

Address Sta. Barbara, Pangasinan Bonuan, Dagupan City Malasiqui, Pangasinan Bonuan, Dagupan City Sta. Barbara, Pangasinan

Contact_no

Created_by Date_ register 09488283288 Admin 12/6/2011

20

Female

09087654321 Admin

12/6/2011

20 20

Male Male

09128635362 Admin 09061421123 Admin

12/6/2011 12/6/2011

20

Male

09152738129 Admin

12/6/2011

tblAuditTrail Transaction_no 11001 11002 11003 11004 11005 tblBilling Stall_owner_id 1 2 3 4 5 InCharge Admin Admin Admin Admin Admin

Transaction New Registration in stall 1D Update stall record of Ms.Villanueva Update Rent Admin changes his password Search the record of Mr.Soriano

Created_by Admin Admin Admin Admin Admin

Date 12/6/2011 11/21/2011 8/16/2011 06/05/2011 12/18/2011

Amount 3000 2500 800 2750 800

Start 11/28/2011 11/30/2011 11/29/2011 11/23/2011 11/30/2011

End 12/28/2011 12/30/2011 12/29/2011 12/23/2011 12/30/2011

Date_payment 11/28/2011 11/30/2011 11/29/2011 11/23/2011 11/30/2011

ChangeMoney P 100.00 P 245.00 P 0.00 P 0.00 P 100.00

67

tblRentRate Front_corner Back_corner

3000 2750

In_between
2500

Fish_section
600

Meat_section
800

Vegetable_ section
400

68

Appendix H Flowchart of Existing process

BEGIN

Applicant choose a stall he wants to rent

YES

New applicant?

NO

Pay Rent

Market Supervisor gets the applicants basic information

Issue Receipt

Record the information in a log book

Receipt

Evaluate

Is the application approved? NO

YES

Save the records

Applicant pay the 2 months deposit and 1 month advance

Issue Receipt

END

69

Appendix I Acceptability Test Acceptance testing is a test conducted to determine if the requirements of a specification or contract are met. It may involve black-box testing performed on a system and often distinguish acceptance testing by the customer (the user or client) prior to accepting transfer of ownership. FUNCTIONAL REQUIREMENTS Functional testing is a type of black box testing that bases its test cases on the specifications of the software component under test. Functions are tested by input and examining the output, and internal program structure is rarely considered. A. Miscellaneous 1. Displays appropriate error messages and error icons based on the situation. 2. Buttons should functions as expected. 3. Forms should be displayed and modal if necessary. 4. Menus are arranged by and group according to its uses. 5. Keyboard shortcuts should be provided for buttons and menus. 6. Close button is provided for each form. 7. Reports should be printed as close as possible to its view. 8. Tab index should be arranged according to the sequence of all objects. 9. Default values for textbox or any input box should are specified. 10. Scroll bar shows automatically when needed. 11. List box allows single select, either by mouse or arrow keys. 12. On a drop down list, clicking the arrow will give list of options available to the users. B. Interface-related 1. Same theme is applied on all modules and main switch board. 2. Similar object should be group by a box or a grouping object. 3. Uses at most three colour combinations.
70

Accepted

Not Accepted

Accepted

Not Accepted

4. When loading a window, a progress bar or any visual representation of a progress is provided. 5. Closing a form will ask user to confirm before proceeding. C. Database- related 1. Data structures should be available only for the administrative level. 2. Choose proper DBMS application. 3. Database / tables should be open / closed accordingly. 4. Data types for each field will assigned properly. 5. Maximum lengths of fields are set. 6. Primary key are determined and utilized. 7. Records are stored in table as entered in the interface. 8. Retrieval of records is properly done. 9. SQL statements are used in accessing records. 10. Create users and sets of privileges for each user. D. Security- related 1. Username and password should be encrypted. 2. For multiple users, accessibility level should be implemented. 3. Do not allow other user to access accounts except if it has administrative level. 4. Administrative level can create another administrative and lower level access. 5. Lower level access can be manipulated by an administrative level. NON- FUNCTIONAL REQUIREMENTS Non- functional requirements specify criteria that can be used to judge the operation of a system rather specific behaviors. It defined how a system is supposed to be and often called qualities of a system. A. Usability used to evaluate a product by testing it on users. This can be seen as an irreplaceable usability practice, since it gives direct input on how real users use the system. It focuses o measuring a human- made products capacity to meet its intended purpose. Usability Accepted Not Accepted 1. The end user shall be able to place and order within thirty seconds. 2. The end user shall be able to access any page within four
71

Accepted

Not Accepted

Accepted

Not

seconds 3. Reports were organized based on companys standard. 4. Previewing of reports or related documents before printing should work properly. 5. Amateur and advance users can run the GUI 6. Display should look good 7. Software must be intuitive or easily understood after reading the rules. 8. Comfortable layout that accommodates beginners as well as veterans. B. Performance Care needs to be taken to specify throughput and response times in terms of the creation and processing of major data entities with reference to specific use cases. Ensure that the requirements are written in such a way that the testing of them will be straightforward. Specify expected respond if resource and throughput targets are to be met. Performance Accepted Not Accepted 1. Loading of a request will be loaded within 30 seconds. 2. The report should display within 60 seconds 3. Five (5) concurrent transactions could be done within 60 seconds. C. Maintainability Propensity to facilitate updates to satisfy new requirements. thus the software product that is maintainable should be well documented, should not be complex, and should have spare capacity for memory, storage and processor utilization and other resources. Maintainability 1. System was designed under a licensed application that technical assistance is guaranteed 2. Support for new capabilities or ability to exploit new technologies 3. Support for additional users 4. Needs to user minimal system requirements 5. The application uses a programming framework D. Portability Ability to run well easily on multiple computer configurations. Portability can mean both between different hardware such as running on a PC as well as a smartphone and between different operating systems such as running on both Mac OS x and GNU / Linux.
72

Accepted

Not Accepted

Portability 1. System could run on PC hardware 2. System could run on Windows OS

Accepted

Not Accepted

E. Security Does the software protect itself and its data against unauthorized access and use? Does it allow its operator to enforce security policies? Are security mechanics appropriate, adequate and correctly implemented? Can the software withstand attacks that can be anticipated in its intended environment? Security 1. User authentication shall be via the single sign on system. 2. Verify that the system does not allow invalid usernames and passwords 3. User should be given login information that works after successful completion. 4. The password should be encrypted for safety ( field and database entry ) 5. Password control ( including constraints for passwords content, re-use, and frequency of chan0000000000ge ) Accepted Not Accepted

73

Appendix J Letter for the company

74

MACARAEG, RAYMOND T. # 58 INUMAAN BALINGUEO, STA. BARBARA, PANGASINAN macaraeg_raymond17@yahooo.com 09488283289

OBJECTIVE: To obtain a position that will enable me to use my strong organizational skills, educational background, and ability to work well with people. PERSONAL INFORMATION: Name: Raymond T. Macaraeg Age: 20 Gender: Male Address: # 58 Inumaan Balingueo, Sta. Barbara, Pangasinan Mobile No. 09488283289 Civil Status: Single Religion: Roman Catholic EDUCATIONAL BACKGROUND: Elementary: Balingueo Elementary School (1998 - 2004) Secondary: Tertiary: Skills and Achievements Knowledgeable in the following software application/languages: Microsoft Office and Open Office Operating System Application Visual Basic 6 Oracle 10g Java Windows Live Movie maker Macromedia Flash Adobe Photoshop CS4, CS5 Joomla! Academic Scholar Colegio de Dagupan 2nd Semester S.Y. 2008, 2nd Semester S.Y. 2009
75

Malasiqui National High School (2004 - 2008) Colegio de Dagupan (2008 - 2012)

Deans Lister Colegio de Dagupan S.Y. 2009-2012 Seminars & Trainings Attended Gearing Up for On-the-Job Training March 11 2010 Audio Visual Theater, Colegio de Dagupan Arellano St. Dagupan City On-The-Job-Training March 2010 May 2010 Land Transportation Office Dagupan City , Panagasinan Java Applets March 23 2009 Audio Visual Theater, Colegio de Dagupan Arellano St. Dagupan City On-Job-The-Training March 2011 April 2011 SSS Baguio Baguio City

76

MEJIA, JOHN CECILIO S. BGRY. GOMEZ, MALASIQUI PANGASINAN jcmejia08_kb24@yahooo.com 09104404107 OBJECTIVE: To obtain a position that will enable me to use my strong organizational skills, educational background, and ability to work well with people. PERSONAL INFORMATION: Name: John Cecilio S. Mejia Age: 19 Gender: Male Address: # 146 Brgy. Gomez, Malasiqui, Pangasinan Mobile No. 09104404107 Civil Status: Single Religion: Born Again Christian (Baptist) EDUCATIONAL BACKGROUND: Elementary: Malasiqui Catholic School (1998-2004) Secondary: Tertiary: Skills and Achievements Knowledgeable in the following software application/languages: Microsoft Office and Open Office Operating System Application Visual Basic 6 Oracle 10g Java Windows Live Movie maker Macromedia Flash Adobe Photoshop CS4, CS5 Joomla Seminars & Trainings Attended Gearing Up for On-the-Job Training March 11 2010 Audio Visual Theater, Colegio de Dagupan
77

Malasiqui Catholic School (2004 - 2008) Colegio de Dagupan (2008 - 2012)

Arellano St. Dagupan City On-The-Job-Training March 2010 May 2010 Malasiqui Civil Registrars Office Malasiqui , Panagasinan Java Applets March 23 2009 Audio Visual Theater, Colegio de Dagupan Arellano St. Dagupan City On-Job-The-Training March 2011 April 2011 BIR RDC Calasiao, Pangasinan

78

VILLANUEVA, NOEMI C. #565 CHINA ST. BONUAN BINLOC DAGUPAN CITY no0wme@rocketmail.com 09381410828

OBJECTIVE: To obtain a position that will enable me to use my strong organizational skills, educational background, and ability to work well with people. PERSONAL INFORMATION: Name: Villanueva, Noemi C. Age: 20 Gender: Female Address: # 565 China St. Bonuan Binloc, Dagupan City Mobile No. 09381410828 Civil Status: Single Religion: Catholic EDUCATIONAL BACKGROUND: Elementary: Secondary: Tertiary: Skills and Achievements Knowledgeable in the following software application/languages: Microsoft Office and Open Office Operating System Application Visual Basic 6 Oracle 10g Java Windows Live Movie maker Macromedia Flash Adobe Photoshop CS4, CS5 Joomla!
79

Joyland School (1999-2004) Joyland School (2004-2008) Colegio de Dagupan (2008 - 2012)

Seminars & Trainings Attended Gearing Up for On-the-Job Training March 11 2010 Audio Visual Theater, Colegio de Dagupan Arellano St. Dagupan City On-The-Job-Training March 2010 May 2010 Malasiqui Civil Registrars Office Malasiqui , Panagasinan

Java Applets March 23 2009 Audio Visual Theater, Colegio de Dagupan Arellano St. Dagupan City On-Job-The-Training March 2011 April 2011 Municipal Hall of Baguio City

80