3.1.3 information in the system before storing

Published by admin on

3.1.3 Use case diagram The use case diagram as shown in Figure 3.8 and Figure 3.9 is used to show the interaction among the element in the system. There are two actor in this use case which are student and staff. Figure 3.8: Student use case diagram Figure 3.9: Staff use case diagram Use case Login to store system Actor Student, staff Description i. User will login to the system using their matric number as username and using their own password. Table 3.0 Login to store system use case Use case Fill check-in item form Actor Student Description i. Student will fill in all detail in the form. ii. Student must upload the picture of their item to the space provided in the form. iii. Once submit button clicked, the all the information will be stored inside database for future reference Table 3.1 Check-in item form use case Use case Update item information Actor Student Description i. Student can update this item information in the system before storing their item inside the college store provided. Table 3.2 Update item information use case. Use case Check-out item from system Actor Student, staff Description i. To check-out the item from store, staff will scan the barcode from the item label to check-out the item. ii. Once the barcode is scan, the inventory list in the database will be updated. iii. Student can only retrieve their item from the store when the barcode is scan using the barcode scanner. Table 3.3 Check-out item use case Use case View item inventory Actor Student Description i. Student can view the item by clicking the “View my item” menu in the system. Table 3.4 View item inventory use case Use case Print item label Actor Student Description i. Student can print the label for the item by clicking the “View item label” menu in the system. ii. Student must print the item label and stick it to each of their item. iii. The item label contain barcode for scanning in order for the student to check-out their item Table 3.5 Print item label use case Use case Update inventory list Actor Staff Description i. Staff can view the update inventory list in the system. ii. The system will showed which item is already check-out from the store. Table 3.6 Update inventory list use case 3.1.4 Data flow diagram The Figure 3.10 showed the context level of data flow diagram Figure 3.10 Context level diagram for store system Figure 3.11: Level 0 diagram for store system Figure 3.12: Level 1 diagram for login Figure 3.13: Level 1 diagram for check-in store system 3.1.5 Entity Relationship diagram Figure 3.14: Store system ERD 3.1.6 Functional Requirement In the proposed system, in order for the user be able to gain access to the store system, the user must have the valid username and password. The user must be a Sakura college student. This is because, the store system is only can be access by the college student and staff. Other than that, the check-in item form details must be filled correctly so that the information about the item that will be stored in the inventory database is valid and the item label generated will contain the valid owner information. To check-out the item from the store the label stick to the item must be scanned 3.1.7 Non-functional Requirement The store system can only be access if the student live in Sakura College and if that person is Sakura College staff, this situation refer to the usability of the store system. The quality of Sakura store system will be test using the user evaluation metric. If all the component can function properly and achieved the objective stated, then the system can be considered in good quality. 3.2 System requirement System requirement refer to the software and hardware requirement which will be used to develop the project. 3.2.1 Software requirement Software Description Hostinger software An online software to connect the database and also to publish the database. Edraw Max Software used to draw use case and sequence diagram. Also used to design the wireframe of the system FileZilla Free software for importing file to the internet. It consist Filezilla client and FileZilla server Xampp A local web server which allow user to run code to any browser. Notepad++ A software which used in Microsoft Windows as a text editor and source code editor. Table 3.7: Software requirement 3.2.2 Hardware requirement Hardware Description Asus Intel Pentium This laptop type is used to develop the proposed system. 2GB RAM 2GB install RAM in the laptop is sufficient to develop the proposed system. Barcode scanner The barcode scanner is used to scan the barcode in the item label during the check-out of the item from store Table 3.8 Hardware requirement 3.3 Design As mentioned in Waterfall model analysis, design phase can be divide into two which are logical design and physical design. The physical design is the user interface design. 3.3.1 Interface design Figure 3.15 Login page The figure below show the main interface of the store system. There are four main menu which are the check-in form menu, check-out menu, item label menu and view my inventory menu 3.16: Homepage The figure shown below is the check-in form for the student to fill in their details. Once the form submit to the system, all the information will be stored in the inventory database. Figure 3.17: Check-in item page The figure shown below is the item label menu, to be able to generate this item label student must fill the check-in form so that their item details will be display in the item label. Figure 3.18: Item label page Figure 3.19: Check-out item page The figure shown below is the view inventory page. Student can view what item they stored in the college store. It contain the item image, so that the student can recheck which item belong to them before checking out the item. Figure 3.20: View inventory page

Categories: Data


I'm Iren!

Would you like to get a custom essay? How about receiving a customized one?

Check it out