Unilever (COS) - Project1 - Kundan Nikalje
Unilever (COS) - Project1 - Kundan Nikalje
Unilever (COS) - Project1 - Kundan Nikalje
A SIMPLILEARN PROJECT
FOR CBAP COURSE
IV. Create as-is and future process maps (using flowcharts). You can use any of the popular
tools in the market like Microsoft Visio, Lucid Chart, Creately, Pidoco, or Balsamiq
V. As a Business Analyst working on this project, find out the scope of the Canteen
Ordering System. To find the scope you can use the case diagram (UML) or context
diagram for the same.
VII. Write the in-scope and out-of-scope items for this software.
X. Write out the business requirements, both the functional and non-functional
requirements.
XI. Draw wireframes or mock screens for any two of the features namely Menu Creation
and any other feature as deemed fit by the student. (Use the technique prototyping or
wire framing that is taught in the Training). You can use any of the wireframing tools like
Microsoft PowerPoint, Microsoft Word, Balsamiq, Sketch, Adobe XD, Adobe Illustrator,
Figma, UXPin, InVision Studio, InVision Freehand, or Moqups.
BUSINESS ANALYSIS CORE CONCEPT MODEL
(BACCM)
The conceptual framework of business analysis has been captured as outlined in the BABOK
guide.
★ Reduce canteen food wastage by a minimum of 30% within 6 months following first
release.
★ The value of food thrown away each month by examining the canteen inventory from
25% to at least 15% per month.
★ Reduce canteen operating costs by 15% within 12 months, following initial release.
★ Increase average effective work time by 30 minutes per employee per day, within 3
months.
★ By making the ordering process automated and by delivering the food to the user's
workstation, the canteen will be able to operate with lesser manpower.
Project Task 4 :Create as-is and future process map (using flowcharts)
Context Diagram
Project Task 6 : Main Features to be Developed
Below are the main features of the system which needs to be developed:
➢ A user-friendly web page for the canteen ordering system with up-to-date menu along
with the prices.
➢ Employee registration and login on the system.
➢ After successful login, employees should be able to see the updated food menu with all
the dishes.
➢ Access to the menu manager to create and edit the menu.
➢ The lunch orders cannot be made after 11 am, so that the chef has sufficient time to
prepare the lunch for all the employees.
➢ Edit option for the users to alter their cart before checkout.
➢ Employees can place the lunch order and confirm after adding all the desired food items
into their cart.
➢ Once the order is confirmed, employee cannot modify or cancel the order
➢ The canteen manager (order processor) views all the order and assign them to chef for
the preparation
➢ The packed order will be assigned to the meal deliverer for the delivery to employee’s
workstation
➢ After the food is delivered, the meal deliverer will mark the order as closed.
➢ After completion of the order, the employees will be asked to fill the feedback form for
their order
➢ There will be no payment gateway so the bill amount will be deducted from the
employee’s monthly salary by the payroll team
In-Scope Requirements
1 Employee registration / Login screen
2 Menu page
3 Meal ordering screen (No order allowed after 11 am)
5 Payment summary
10 Employee will access Canteen Ordering System main page via URL
11 Feedback submission
The Hospital Management System (HMS) will not include below mentioned areas in current
scope.
Functional Requirements:
The canteen management system (CMS) have the following functional
requirements :
❖ Online web or mobile application
❖ Signup / Login screen to verify employee’s details (Only Unilever employees
should be allowed to sign up with their employee ID)
❖ Menu for food selection
❖ Food ordering not allowed post 11 am
❖ Food order and payment summary
❖ Order tracking feature
❖ Payroll management system
❖ Meal delivery person details
❖ Feedback submission
Non-functional Requirements:
CMS have the following non - functional requirements :
❖ Usability : User friendly system and self-explanatory screens
❖ Scalability : Able to serve 1500 users of the office
❖ Performance : System should be light and render fast
❖ Platform : Java platform as it required very little maintenance to be done on the
code
Project Task 11 : Draw wireframes or mock screens