PCMIS-Computer Sciences Applications-Project Report, Study Guides, Projects, Research of Applications of Computer Sciences

Download PCMIS-Computer Sciences Applications-Project Report and more Study Guides, Projects, Research Applications of Computer Sciences in PDF only on Docsity! 1 1 Introduction This section will give an overview of the product being developed. 1.1 Description The software being developed will automize the attendance system of the Mess and bring correctness in it, by first authenticating and then marking the attendance of the Mess Member and will also automize the billing system by doing all the calculations required automatically and generating monthly bills that will be due from the Mess Members. It is an intranet based solution. The system is to maintain one database for each Mess containing information about attendance and billing of each Mess Member along with their individual particulars necessary to identify the Mess Members, the monthly expense and purchase records. 1.2 Problems with current system The current system is relying on man labor. All the purchases have to be summarized from the purchase receipts manually; all the expense records are recorded and summarized manually on pieces of paper daily; all the attendance is recorded manually on piece of paper daily and then duplicated on the registers; daily bill of every Mess Member is calculates manually on piece of paper. At the end of each month the total bill is also calculated manually for each Mess Member. Time is wasted on these activities daily. 1.3 Purpose of PCMIS This software will benefit Mess Members by managing their time to utilize the Mess facility and giving them portal to complain and give suggestions; Mess administration by automizeing the work they have to do manually. docsity.com 2 2 Activities This section of the document provides information regarding activities that that were done up until now. 2.1 Literature Survey Literature survey was done on the Barcode to be used for the cards of the Mess Members and also related material regarding the development of the Data Flow Diagrams and Architecture from books and internet. The list of the books provide in the „Reference‟ section are being used for the design and development purposes. The information on Barcode and its standards is as follows. 2.1.1 Barcode A barcode is a machine-readable representation of information. Originally, barcodes stored data in the widths and spacing of printed parallel lines, but today they also come in patterns of dots, concentric circles, and text codes hidden within images. Barcodes can be read by optical scanners called barcode scanners. Barcodes are widely used to implement Auto ID Data Capture (AIDC) systems that improve the speed and accuracy of computer data entry. An advantage over other methods of AIDC is that it is less expensive to implement. There are many types of Barcodes e.g. EAN13 which is used for generating Barcode of ISBN Nos. of books. UPC (A, E) is used commonly to encode retail prices of items to be sold and Code 39, 128 (A, B, C) which are used for various purposes. The Barcode type Code128 (B) will be used for this project, example of the Barcode is shown in the Figure 1 which encodes data “BSCIS0438”. Figure 1: Code 128(B) Barcode for "BSCIS0438" docsity.com 5 5. Monthly Attendance: It is the information on the number of dishes each Mess Member eats on each day of the month. Which also tell us whether the person attended the Mess or not. 6. Daily Attendance: It is the information on the number of dishes each Mess Member eats on a single day. This is also the one day attendance. 7. Mess Member Account Information: It is the information of the Mess Member which contains his credentials. 8. Security Amount/Mess Bill: It is the information of how much the bill of the Mess Member is and how much amount he is giving to add it to his account balance. 9. Monthly Purchase Information: It is the information of Purchases that are done for the Mess. 10. Monthly Expense Information: It is the information on how much the Items are expensed. 11. Roster: It is the information on the Duties of the Mess Employee. 12. Employee info/Roster: It is the information on the Employee credentials and there duties being assigned in shifts. 13. Barcode Info: It is the barcode information on the card of the Mess Member. 14. On-Payment Lunch Info: It is the information on the on-payment Lunches. 15. Official Lunch/Tea Info: It is the information on the Official Lunch/Tea events. The Context Diagram of PC-MIS is as follows I the Figure 3. docsity.com 6 Figure 3: Context Diagram 2.2.2 Diagram 0 The diagram 0 is a picture of system itself. It gives the picture of the major processes inside a system interacting with the entities. The Processes are illustrated by bubbles and are numbered. The details of the processes are not shown in this diagram it just gives the overview of the system processes. For the details of the process we can further elaborate and expand the processes in the detailed diagrams. The Diagram 0 of PC-MIS is given in the Figure 4. Figure 4: Diagram 0 docsity.com 7 2.2.3 Detailed DFDs The Detailed Diagrams of the Processes in the Diagram 0 are as follows. 2.2.3.1 Process bubble 1 feedback Process The detailed DFD of Process 1 is given in Figure 5. Figure 5: Detailed DFD of Process bubble 1 (Feedback Process) 2.2.3.2 Process bubble 2 Billing Process The detailed DFD of Process 2 is given in Figure 6. Figure 6: Detailed DFD of Process bubble 2 (Billing Process) docsity.com 10 2.2.3.7 Process bubble 7 Purchase Process The detailed DFD of process 7 is given in Figure 11 Figure 11: Detailed DFD of Process 7 (Purchase Process) 2.2.3.8 Process bubble 8 Expense Process The detailed DFD of process 8 is given in Figure 12. Figure 12: Detailed DFD of Process bubble 8 (Expense Process) docsity.com 11 2.2.3.9 Process bubble 9 Official Lunch Process The detailed DFD of process 9 is given in Figure 13 Figure 13: Detailed DFD of Process bubble 9 (Official Lunch Process) 2.2.3.10 Process bubble 10 On-Payment Lunch Process The detailed DFD of process 10 is given in Figure 14 Figure 14: Detailed DFD of Process bubble 10 (On-Payment Lunch Process) 2.3 Mapping Data Flow to a Software Architecture The Data Flow Diagrams were analyzed and mapped into the software architecture by following the steps given bellow. docsity.com 12 2.3.1 Review the Fundamental System Model The fundamental system model or context diagram depicts the PC-MIS as a single transformation, representing the external procedures and consumers of data flow into and out of the system. The Figure 3 shows the 0 Level model and Figure 4 shows the Level 1 model which is more refined. 2.3.2 Review and Refine the Data Flow Diagrams for the Software Information obtained from the analysis models is refined to produce greater details. The Diagram 0 was further refined to the Detailed DFDs at Level 3. These data flow diagrams exhibit relatively high cohesion i.e. the sub-processes are distinct. 2.3.3 Determine Whether the DFD Has Transform or Transaction Flow Characteristics In general, the information flow within a system can always be represented as transform. In our case there is no transaction center so the system as a whole is in transform flow, see Figure 4 (Diagram 0). 2.3.4 Isolate the Transform Center by Specifying Incoming and Outgoing Flow Boundaries The incoming and out going flows boundaries were identified and transform center were identified. One of the Detailed DFD of Process 3 with flow boundaries is provided in Figure 15 as an example. Figure 15: Process Bubble 3(Attendance Process) with flow boundaries docsity.com 15 2.4.1.1 Strong Entities The entities which exist without depending on any other entity are strong entities. 2.4.1.1.1 MESS Entity set “MESS” stands for all the Mess facilities in PIEAS. Its attributes are as follows.  MESS_ID stands for the identification number of mess.  NAME stand for the name of the mess facility.  LOCATION stands for the location were mess facility is situated.  MESS_BALANCE stands for the account balance of the mess facility. The entity set “MESS” is shown in the Figure 19. Figure 19: "MESS" Entity Set 2.4.1.1.2 MESS_MEMBER Entity set “MESS_MEMBER” stands of the people who are members of any mess facility. The attributes are given as follows.  MEMBER_ID stands for the identification number of the mess member.  NAME stands for the name of the mess member.  PHONE stands for the telephone number of the mess member.  ADDRESS stands for the residing address of the mess member.  PICTURE stands for the photograph of the mess member.  DEPARTMENT stands for the department in which mess member works.  RANK stands for the rank of the mess member i.e. weather he/she is a student or faculty or staff.  EMAIL stands for the e-mail address of the mess member. The entity set “MESS_MEMBER” is shown in the Figure 20 as follows. docsity.com 16 Figure 20: "MESS_MEMBER" Entity Set 2.4.1.1.3 EMPLOYEE Entity set “EMPLOYEE” stands for the employee of the any mess which includes Operators, Shift In-charge, Staff Members, Supervisor. The attributes of the entity is given as follows.  EMPLOYEE_ID stands for the identification no of the employee.  NAME stands for the name of the mess employee.  PHONE stands for the phone number of the employee.  ADDRESS stands for the residing address of the employee.  PICTURE stands for the photograph of the employee.  DEPARTMENT_RANK stands for the rank of the employee in the department  DEPARTMENT stands for the department to which employee is assigned.  EMAIL stands for the email of the employee. The entity set “EMPLOYEE” is shown in the Figure 21. Figure 21: "EMPLOYEE" Entity Set docsity.com 17 2.4.1.1.4 FOOD_ITEM Entity set “FOOD_ITEM” stands for the Items in the inventory of any mess. The attributes are as follows.  ITEM_ID is the identification number of the item in the inventory.  NAME is the name of the food item.  QUANTITY is the current quantity of item in the inventory.  PRICE is the current price of the item in the inventory.  SUPPLIER_NAME is the name of the supplier of the item. The entity set “FOOD_ITEM” is shown in Figure 22. Figure 22: "FOOD_ITEM" Entity Set 2.4.1.2 Weak Entities The entities that cannot exist independently are weak entities. They need another entity for their existence. 2.4.1.2.1 MENU Entity set “MENU” stands for the menu of the mess which contains the names of the dishes to be cooked. The attributes are as follows.  DATE stands for the date on which the dishes will be cooked.  SHIFT stands for the shift number of the day on which the dishes will be cooked.  DAY stands for the day on which the dishes will be cooked.  MENU_A stands for the name of the dish as option one.  MENU_B stands for the name of the dish as option two. The entity set “MENU” is shown in the Figure 23. docsity.com 20 The relationship set “HAS_BILL” between MESS_MEMBER and MESS entities is shown in the Figure 27. Figure 27: "HAS_BILL" Relationship Set 2.4.2.1.3 MESS_MEMBER has ATTENDANCE for MESS with MENU The relationship set “ATTENDANCE” has following attributes.  MESS_ID stands for the identification number of the mess whose member‟s attendance is recorded.  MEMBER_ID stands for the identification number of the mess member whose attendance is recorded.  DATE stands for the date on which the attendance was taken.  SHIFT stand for the shift number of the shift on which the attendance was taken.  MENU_A stands for the total number of times the dish A was consumed.  MENU_B stands for the total number of times the dish B was consumed. The relationship set “ATTENDANCE” between MESS_MEMBER, MESS and MENU entities is shown in the Figure 28. Figure 28: "ATTENDANCE" Relationship Set docsity.com 21 2.4.2.1.4 MESS HIRES EMPLOYEE The relationship set “HIRES” has following attributes.  MESS_ID stands for the identification number of the mess who is hiring employees.  EMPLOYEE_ID stands for the identification number of the employee who is hired.  MESS_RANK stands for the rank of the employee in the mess facility e.g. cook.  PAY the pay of the employee in the mess. The relationship set “HIRES” between MESS and EMPLOYEE entities is shown in the Figure 29. Figure 29: "HIRES" Relationship Set 2.4.2.1.5 MESS HAS_ROSTER for EMPLOYEE The relationship set “HAS_ROSTER” has following attributes.  MESS_ID stands for the identification number of the mess.  EMPLOYEE_ID stands for the identification number of the employee of mess.  SHIFT stands for the shift number in which the employee will be working. The relationship set “HAS_ROSTER” between MESS and EMPLOYEE entities is shown in Figure 30. Figure 30: "HAS_ROSTER" Relationship Set docsity.com 22 MESS EXPENSES FOOD_ITEM The relationship set “EXPENSES” has following attributes.  MESS_ID stands for the identification number of the mess who is consuming the food items.  EXPENSE_ID stands for the identification number of the expense.  DATE stands for the date of expense.  ITEM_ID stands for the identification number of the item which was consumed.  EXPENSE_QUANTITY stands for the quantity of the item which was consumed.  EXPENSE_PRICE stands for the price of the quantity of the consumed item. The relationship set “EXPENSES” between MESS and FOOD_ITEM entities is shown in Figure 31. Figure 31: "EXPENSES" Relationship Set 2.4.2.1.6 MESS PURCHASES FOOD_ITEMS The relationship set “PURCHASES” has following attributes.  MESS_ID stands for the identification number of the mess who is purchasing food items.  PURCHASE_ID stands for the identification number of the purchase.  DATE stands for the date of purchase.  EMPLOYEE_ID stands for the identification number of the employee who purchased.  ITEM_ID stands for the identification number of the item which was purchased.  PURCHASE_QUANTITY stands for the quantity of the item which was purchased.  PURCHASE_PRICE stands for the price of the quantity of the item that was purchased. docsity.com 25 2.4.2.2.4 MESS ARRANGES EVENT The relationship set “ARRANGES” attributes are given as follows.  MESS_ID stands for the identification of the mess which is arranging the event.  CATEGORY stands for the type of event.  LOCATION stands for the location on which the event will occur.  NAME_OF_RESPONSIBLE_PERSON stands for the name of person responsible for the event.  NO_OF_ATTENDEES stands for the total number of attendees.  ALLOCATED_FUND stands for the funds that are allocated for this event.  FROM_DATE stands for the date of the starting of the event.  TO_DATE stands for the date of the ending of the event.  TIME the time for the event.  MENU the list of the menu items. The relationship set “ARRANGES” between MESS and EVENT entities is shown in the Figure 36. Figure 36: "ARRANGES" Relationship Set docsity.com 26 2.5 Entity Relationship Diagram The ERD of the system is given in Figure 37. Figure 37: ERD of PC-MIS 2.6 Mapping ER Model to Relational Model 2.6.1 Entities 2.6.1.1 Strong Entities  MESS(MESS_ID,LOCATION,NAME)  EMPLOYEE(EMPLOYEE_ID,NAME,PHONE,ADDRESS,DEPARTMENT, DEPARTMENT_RANK,EMAIL,PICTURE)  FOOD_ITEM(ITEM_ID,NAME,QUANTITY,PRICE,SUPPLIER_NAME) docsity.com 27  MESS_MEMBER(MEMBER_ID,NAME,PHONE,ADDRESS,DEPARTMENT, RANK,EMAIL,PICTURE) 2.6.1.2 Weak Entities  MENU(DATE,SHIFT,DAY,MENU_A,MENU_B)  FIX_MENU(ITEM_NAME,PRICE)  EVENT(CATEGORY) 2.6.2 Relationships 2.6.2.1 Strong Relationships  REGISTERS(MESS_ID,MEMBER_ID,ACCOUNT_BALANCE,STATUS)  ATTENDANCE(MESS_ID,MEMBER_ID,DATE,SHIFT,MENU_A,MENU_B)  HAS_BILL(MESS_ID,MEMBER_ID,BILLING_MONTH_YEAR,BILL)  HIRES(MESS_ID,EMPLOYEE_ID,MESS_RANK,PAY)  PURCHASES(MESS_ID,PURCHASE_ID,DATE,ITEM_ID,EMPLOYEE_ID, PURCHASED_QUANTITY,PURCHASED_PRICE)  EXPENSES(MESS_ID,EXPENSE_ID,DATE,ITEM_ID,EXPENSE_QUANTITY, EXPENSE_PRICE)  HAS_ROSTER(MESS_ID,EMPLOYEE_ID,SHIFT) 2.6.2.2 Weak Relationships  ARRANGES(MESS_ID,CATEGORY,LOCATION,FROM_DATE,TO_DATE, TIME,ALLOCATED_FUND,MENU,NO_OF_ATTENDEES,NAME_OF_RESPO SIBLE_PERSON)  HAS_FIX_MENU(MESS_ID,ITEM_NAME)  HAS_MENU(MESS_ID,DATE,SHIFT)  ONPAYMENT_EXPENSES(MESS_ID,DATE,SHIFT,PAYMENT,MENU_A, MENU_B,ITEM_NAME,ITEM_QUANTITY) 2.7 Data Dictionary A data dictionary is a repository of information that describes the logical structure of database. A free standing data dictionary was developed. Name: Comments/Suggestions Aliases: none Where used/how used: Process 1.1 and 1.2 as input. Process 1.1 and 1.2 as output. Description: Comments/Suggestions are given by the Mess Member and read by the Mess Supervisor and Secretary. docsity.com 30 Name: Updated Balance. Aliases: Balance Amount, Paid Monthly bill amount. Where used/how used: Process 2.8, 4.7, 4.6, as input. Process 2.5, 4.7, 4.6 and 2.8 as output. Description: it is the amount of the fee that Mess Member pays. Name: Attendance. Aliases: none. Where used/how used: Process 2.2, 2.4 and 3.3 as input. Process 3.2 as output. Description: it is the attendance of the Mess. Name: Monthly Attendance. Aliases: none. Where used/how used: Process 3.3 as output. Description: it is the Monthly Attendance of Mess. Name: Daily Attendance. Aliases: none. Where used/how used: Process 3.3 as output. Description: it is the Daily Attendance of Mess. Name: Barcode Id. Aliases: Barcode Info. Where used/how used: Process 3.1 as input. Description: it is the Mess Member No. decoded from barcode on the card of Mess Member. Name: Choice of dishes. Aliases: none. Where used/how used: Process 3.1 and 3.2 as input. Process 3.1 as output. Description: it is the choice of the dishes in the menu which the Mess member opts to consume. docsity.com 31 Name: Mess Member No. Aliases: none. Where used/how used: Process 3.1, 4.2, 4.6 and 3.2 as input. Process 3.1 as output. Description: it is the Mess Member No. which helps in identifying the Mess Member. Name: New/Old Mess Member Account Information. Aliases: none. Where used/how used: Process 4.1, 4.2, 4.4 and 4.5 as input. Process 4.1, 4.2, 4.4 and 4.5 as output. Description: it is the personal information on Mess Members that is necessary to be saved by the system, i.e. name, designation, security paid, etc. Name: Security Amount. Aliases: none. Where used/how used: Process 4.3 as input. Process 4.3 and part of 4.2 as output. Description: it is the amount of money paid by Mess Member to get registered in to a Mess. Name: Mess Member Name. Aliases: none. Where used/how used: Process 4.6 as input. Description: it is the name of the Mess Member. Name: Updated Mess Member Account Information. Aliases: none. Where used/how used: Process 4.7 as input. Process 4.6 and 4.7 as output. docsity.com 32 Description: it is the updated personal information on Mess Members that is necessary to be saved by the system, i.e. name, designation, security paid, etc. Name: Menu. Aliases: Monthly Menu. Where used/how used: Process 5.5, 5.2 and 5.3 as input. Process 5.1, 5.2 and 5.5 as output. Description: it is the Monthly Menu of the Mess. Name: Daily Menu. Aliases: Daily Menu. Where used/how used: Process 5.5 as output. Description: it is the Daily Menu of the Mess. Name: Names of Dishes. Aliases: none. Where used/how used: Process 5.1, 5.4 and 5.3 as input. Process 5.4 as output. Description: these are the names of dishes t be cooked. Name: Updated Menu. Aliases: none. Where used/how used: Process 5.2 as input. Process 5.3 as output. Description: it is the updated Monthly Menu of the Mess. Name: New/Old Mess Employee Information. Aliases: none. Where used/how used: Process 6.1, 6.2, 6.3 and 6.4 as input. Process 6.1, 6.2, 6.3 and 6.4 as output. Description: it is the personal information on Mess Employees that is necessary to be saved by the system, i.e. name, designation, etc. docsity.com 35 Where used/how used: Process 8.6 as output. Description: it is the Mess Expense information of a single day. Name: Expense Info. Aliases: none. Where used/how used: Process 8.6 as input. Process 8.3 as output. Description: it is the Mess Expense information, containing the Expense details. Name: Expense Price. Aliases: none. Where used/how used: Process 8.3, 8.4, 8.5 as input. Process 8.1 as output. Description: it is the price of items which were consumed on the latest Mess Expense. Name: Monthly Expense Info. Aliases: none. Where used/how used: Process 8.6 as output. Description: it is the Mess Expense information of a Month. Name: Fix Dish Expense. Aliases: none. Where used/how used: Process 8.4 as output. Description: it is the fix dishes expense of a single day. Name: Official Lunch/Tea Info. Aliases: none. Where used/how used: Process 9.1 and 9.4 as input. Process 9.4 and 9.3 as output. Description: it is the information on the Official Lunch/Tea Event and its details. docsity.com 36 Name: Tea Info. Aliases: none. Where used/how used: Process 9.1 as output. Description: it is the information on the Official Tea Event and its details. Name: Lunch Info. Aliases: none. Where used/how used: Process 9.1 as output. Description: it is the information on the Official Lunch Event and its details. Name: Lunch Event Info. Aliases: none. Where used/how used: Process 9.3 as input. Process 9.1 as part of output. Description: it is the information on the Official Lunch Event details. Name: Tea Event Info. Aliases: none. Where used/how used: Process 9.3 as input. Process 9.1 as part of output. Description: it is the information on the Official Tea Event details. Name: Lunch Menu items. Aliases: none. Where used/how used: Process 9.2 as input. Process 9.1 as part of output. Description: it is the information on the Official Lunch menu items. Name: Tea Menu items. Aliases: none. Where used/how used: Process 9.2 as input. Process 9.1 as part of output. Description: it is the information on the Official Tea menu items. docsity.com 37 Name: Official Lunch/Tea Menu. Aliases: none. Where used/how used: Process 9.3 as input. Process 9.2 as output. Description: it is the Official Lunch/Tea Menu. Name: On-Payment Lunch Info. Aliases: none. Where used/how used: Process 10.1 as input. Description: it is the information on the On-Payment Lunch, containing the price and names of the dishes that were consumed and their quantity. Name: On-Payment Lunch Expense. Aliases: none. Where used/how used: Process 10.1 as output. Description: it is the expense of the On-Payment Lunch. Name: Price of Dish. Aliases: none. Where used/how used: Process 10.1 as input. Description: it is the fixed price of the dish that would be consumed. docsity.com