Project 2

gnsv.srinivas
ISEM530Project1Presentation.pptx

Organic House.

Team Members

Contributions:

Qing Jin: Target Market, Business Strategy, Foreseen Demands, System vision document

Naga Srinivas Guntupalli: Summary of the major systems in our company (Warehousing, shipping, marketing), System diagrams, Use case table and diagrams

Pranil Mali: Organizational Chart, Typical business system of our company, Process improvement for some of the business functions.

Target Audience

Individuals and families who are health conscious

Love organic food and products of high quality

Care about where their food comes from and how it has been produced

Enjoy shopping groceries online/offline

Business Strategy

Products of High Quality

Only natural and organic products of high quality

Product traceability and transparency

Online Shopping System with Same-day Delivery or Pickup

Shop on customers’ own schedule

Fast delivery with only a few clicks

Inclusive Culture

Hire staff that represents all our multicultural customers

Ensure diversity in suppliers and vendors

Demands Foreseen for Our Business

Increase Product Diversity and Add More Non-food organic Items

Personal care products, alcohol, clothing

Personalize Shopping Experience for Each Customer

Customize shopping experience based on unique needs

Organizational Chart

Following are the fictional officers, directors and managers of our company Called, “ —-------------------”

Pranil Mali

President (CEO)

Vice president - Marketing and Sales

Naga Srinivas Guntupalli

Vice President - Finance and systems

Qing Jin

Vice president - Merchandising and Distribution

Continued…………

James Hoyme

Director of Operations and Purchasing

David Brunner

Director of Retail Sales

Erik Spencer

Director of System Development and support

Brian Hunt

Manager - Warehousing and Shipping

Fictional organizational chart:

To give a brief overview of our company we have formed a fictional organizational chart, which gives us a brief overview of different roles and responsibilities of individuals in our organization.

Typical business system of our company (What system is broken)

High-level picture of our company which shows the typical business system is show below.

This explains the different business functions and business processes our company has which eventually helps us to achieve our business outcome.

System Vision Document

Problem Description

In order to meet the growing demand from our customers, we plan to upgrade our current mobile websites to a mobile app, since the webpages are not able to cater to all the needs of our customers anymore.

System Capabilities

Support secure checkout and payment

Provide smoother user experience

Offer better customization options and instant customer service

System Vision Document

Business Benefits

Retain existing customers and attract new ones

Grow trust and loyalty in customers

Connect with our customers and build a stronger brand

Concise Summary

Warehouse: Tracking number assigned to delivery, User location is located. User notified before the order is dispatched, User notified on arrival of product, and delivery completed successfully.

Shipping: Customer browses the list of products by keyword searching or listing all of available products and then adding selected products into the shopping cart and deleting them from the cart.

Marketing: Application guide the user to the homepage, via social media and Internet.

Operations: Transaction processing systems that permits the organization to interact with external environments. it is essential to the day-to-day operations of business that these systems function smoothly and without interruption

Customer services: The agile approach based software development with values, principles, and core practices and four values are communication, simplicity, feedback, and courage for improving customer interaction with the software

Updating

User Updating

User wants to update information on the system.

System require user login with existing account.

Product

As customer want to enter keywords so that they can view a list of products that they want to see for order followed by adding into the shopping cart.

Shipping system

System updates the shopping carts according the user’s selected items.

System display all selected products in the shopping cart.

User updating (If they don’t have account, proceed System validates the user account, If user input is valid, proceed to profile account and system display If user input is invalid, proceed to user log-in, System displays the account holder’s profile, User can change and update address, telephone, and emails and reset passwords, User cannot delete the existing profile, System sends the confirmation that setting has been updated, App guide the user to the homepage)

Product (System updates the shopping carts according the user’s selected items and System display all selected products in the shopping cart).

Shipping system (System searches inventory for products matches the keywords entered. System returns the result and display products that matched, process and System display product by default category).

System Diagrams

1. Authentication/Registration Subsystem

2. Products Subsystem

3. Order Subsystem

4.Delivery Subsystem

5. User Updating Subsystem

6. Loyalty Subsystem

7. Tracking Subsystem

8. Report Subsystem

Use Case Diagram

1.2 User requests to login.

If user don not have an account, process to 1.2 registration.

1.1.3. User enter ID and password.

1.1.4. System verify the user ID and password, process to 1.1.5.

1.1.4.1. If it is invalid, process to 1.3.

1.1.4.2. If user failed to provide correct user ID and password in three successive attempts, block the account for 20 minutes and back to home page.

1.1.5. User is logged in.

References

Satzinger, J. W., Jackson, R. B., & Burd, S. D. (2012). Systems analysis and design in a changing world (6th ed). Course Technology, Cengage Learning.

Gemino, A., & Parker, D. (2009). Use case diagrams in support of use case modeling: Deriving understanding from the picture. Journal of Database Management (JDM), 20(1), 1-24.

Costain, G., & McKenna, B. (2011). Experiencing the elicitation of user requirements and recording them in use case diagrams through role-play. Journal of Information Systems Education, 22(4), 367-380.

Furterer, S. L. (2020, June). Applying Systems Engineering Tools to Model a Food Justice System in an Engineering Management Course. In 2020 ASEE Virtual Annual Conference

https://www.netsuite.com/portal/resource/articles/accounting/procurement.shtml

https://arcoro.com/blog/most-common-hr-issues-solutions/

THANK YOU