Mama's Love Bakery Employee and Supplier Record Tracker
Co, RoxanneDe Leon, Gelvin
Dela Cruz, Shannen RoseHaw, Michael
Select which part
IntroductionFunctional RequirementsAppendixP.O.V.Q.S.
Mama’s BakeryBackground of Mama’s BakeryOrganizational ChartBusiness ProcessMama’s Bakery’s problem
Back
Background of Mama’s bakery
Location: ManilaProducts: Bread and some grocery itemsOwner: Robin De LeonEmployees:
Total of 6 sales lady and 7 bakers each bakery
Back
Organizational Chart
Back
Business Process
Store hours: 4:00 am to 12:00 midnight Two shifts:
4:00am to 2:00pm 2:01pm to 12:00 midnight
The employees have to log in and out before proceeding to their job or at the end of their shift
Types of Employees Cashier Saleslady Bakers
Master Baker Helper
Back
Business Process
1. The customer picks out the bread he/she wanted to buy.
2. The saleslady assists him/her and passes the packaged bread to the cashier.
3. The customer then pays to the cashier.
4. The Cashier stores the money and if there’s a change, it will be given to him/her.
Back
Mama’s Bakery’s problem
The company needs a database to record their supplier information.
The company needs a database to record their employee information.
Back
Objectives, Scope and Limitations
ObjectivesScope and Limitations
Back
Objectives
To create an adequate supplier and employee database for the company.
To design the program so that it is secure and user-friendly.
To design the program around existing processes so that there can be ease in transition.
Back
Scopes and Limitations
Language: JavaRDBMS: mySQLUsers:
Owner Employees
Back
Scopes and Limitations
Features Password Protected (password supplied by the
company) suggestions on additions or deductions to
employee salary based on a performance factor (determined by the authorized users of application)
Back
Scopes and Limitations
Contents of the database Names Positions Salary-related information Supplier names Products supplied Product prices
Back
Scopes and Limitations
Limitations Will not place product orders with suppliers Nor take orders from customers A managerial application Not transactional
Back
Scopes and Limitations
Upon Request: Printing support Web service
Back
Functional Requirements Software FunctionsUser Types and their DescriptionsData Files and their DescriptionsReport Types and their DescriptionsUse Case DiagramUse Case Descriptions
Back
Software Functions
Employee Record Add Employee
allows the user to add employee records to the database
Edit Employee allows the user with the appropriate permissions to
edit existing employee records View employee
allows the user to view the employee record of the user
Back
Supplier Record Add supplier
allows the user to add supplier records to the database
Edit supplier allows the user to edit existing supplier records
View supplier allows the user to view the supplier records
Back
User Types and their Descriptions
Manager the primary user of the system can fully control and access all information within the
system can view all of the 9 information stored in the system can edit the information in the supplier and employer
database, as well as the account information of the other users
user can also add new employee profiles, supplier profiles and accounts
The system will be used at least once a week
Back
Employee the subsequent user of the system can access only his/her own account
information and partially access his/her personal profile
can view only parts of his personal information (excluding the performance factor) and his respective account information
Back
Data Files and their Descriptions
Employee File stores information about the employees working in the
company includes the employee’s name, ID number, position,
base salary, salary deductions, salary bonuses, attendance and ratings
ID number will be unique for each employee and is mainly for database purposes only
base salary is given according to the position the employee is assigned
Salary deductions are based on the amount of advances that an employee will take
Back
salary bonuses are given if an employee made extra works
rating is simply a comment that the owner will give to an employee base in his/ her performance
Back
Supplier File stores information about the suppliers will serve as a basis for the company to identify whom to
buy products that will be needed for their production will include the supplier’s name, contact information,
products and the product prices contact information will include the supplier’s contact
numbers and address basically the name of the item that the supplier supplies
for the company and the product prices shows how much each product cost
Back
Report Types and their Descriptions
Employee Report used to check for employees’ information,
specially attendance and performance ratings and how salary is affected for the month through choosing the desired date the user wants to view can have the liberty of choosing what attributes the report should contain
Back
Supplier Report used to view the suppliers’ information; it also
gives information about the prices of the products that is supplied to the company
Back
Use Case Diagram
Back
Back
Use Case Descriptions
Use Case: Log-In Precondition: – Main Flow: 1. The User enters the
username and password to the system.
2. User click sign in button.
3. The system checks if the username is valid.
4. The system checks if the password matches the username.
Alternate Flow: 1. If the user did not put
any username or password, the system will notify that there is an empty field and will return to the signing in module
2. If the username was incorrect, the system will notify the user.
3. IF the password did not match the username, the system will notify that it didn’t matched.
Back
Use Case: View Supplier Record
Precondition: Manager/ Employee has logged in.
Main Flow: 1. The user selects the
Supplier module. 2. The user looks for the
record he/ she wishes to view.
Back
Use Case: Add Supplier Record Precondition: Manager has logged in. The user selected Suppliers module
Main Flow: 1. The user clicks the New button. 2. The user inputs the Supplier’s
name, contact information, product name that they supply and it price.
3. The system will ask confirmation from the user to add the data.
4. The user accepts confirmation. 5. System will generate its ID
number. 6. New Supplier is added to the
database.
Alternative Flow: 1. If the user cancels the adding of
new Supplier, it returns to Supplier module.
2. If the user did not accept the confirmation of adding the new Supplier, the system returns to Supplier module ignoring the information inputted.
3. If the user left a field empty, the system will notify the user.
Back
Use Case: Edit Supplier Record Precondition: Manager has logged in. The user selected Suppliers module 13
Main Flow: 1. User will select the supplier
record he/ she wish to edit. 2. The user clicks Edit button. 3. The user will make necessary
changes on the record. 4. The user saves the changes. 5. System will ask confirmation
from the user to update. 6. The user accepts confirmation. 7. The system will return to the
Supplier module with changes applied.
Alternative Flow: 1. If the user cancels the update,
the system will return to the Supplier module.
2. If the user did not accept the confirmation, the system will return to the Supplier module ignoring the changes made.
Back
Use Case: View Employee Record Precondition: Manager has logged in. Main Flow:
1. The user selects Employee module.
2. The user looks for the record he wishes to view.
Back
Use Case: Add Employee Precondition: Manager has logged in. Manager selected Employee module Main Flow:
1. The Manager clicks the New button.
2. Manager inputs the employee’s name and position.
3. The system asks for confirmation.
4. Manager accepts confirmation. 5. The system will generate the
base salary according to the position of the employee.
6. Salary deduction and Salary bonuses are set to zero.
7. The system adds the data to the database.
Alternative Flow: 1. If the user cancels the adding
process, the system returns to the Employee module.
2. If the user left a field empty, the system will give notification.
3. If the user did not accept the confirmation to new employee, the system returns to the Employee module and ignore the inputs.
Back
Use Case: Edit Employee Record Precondition: Manager has logged in. Manager selected Employee module. Main Flow:
1. Manager selects the employee record to be edited.
2. The Manager selects Edit button. 14
3. Manager may change the position, base salary and give salary deductions and salary bonuses
4. The Manager selects Save button. 5. System will ask confirmation.
6. User will accept confirmation. 7. The system returns to Employee
module with changes applied.
Alternate Flow: 1. If the user cancels the changes, the
system will return to the Employee module.
2. If the user left a field empty, the system will give notification.
3. If the user did not accept the confirmation, the system will return to the Employee module ignoring the changes.
Back
Use Case: View Account information
Precondition: Manager / Employee has logged in.
Main Flow: 1. Look into the
account info. 2. View the desired
information.
Back
Use Case: View own Employee Record
Precondition: Employee has logged in.
Main Flow: 1. The employee looks
into the personal info module
2. The employee looks for the record he wishes to view.
Back
Appendix
Sample Employee RecordSample Receipt
Back
Sample Employee Record
Back
Sample Employee Record
Back
Sample Receipt with Supplier Data
Back
Points, Opinions, Violent Reactions, Question and Suggestions
Back