There are various triggers which have led to the adoption of Weddings, Parties, Everything Catering Services System (WPE). For the company Weddings, Parties, everything working as an online business company from some time an automatic system is provided. Thus, their purpose is to identify the right catering menu for the right customer as per their demand as well as occasions. Following triggers were the basis for designing and developing a WPE Information System.

The transition from manual operations to a new system for automation of businesses by connecting the right customer to the right Caterer.
Issues with the current manual system leading towards issues with customer loss, Caterer’s connection loss and lack of mismanagement for conducting business processes effectively.
It will bring opportunities to attract more consumers due to a systematic approach.
The business governance framework, as well as operational management activities, will be improved as the processes are already automatic and not require manual work (Rubino, and Vitolla, 2014).

Benefits

There are several benefits of the WPE information system in context with online business operations:

Customer Information

Customers are an essential aspect of any business, whether it is online or offline. The information of customers such as name, their contact numbers, orders, occasion, food and catering menu, selection and booking timings, venue, as well as payment transaction records followed by individual feedback could be managed effectively.

Concise Decision Making

The decisions related to Caterer’s selection, consumer issues with services as well as operational process management could be accomplished effectively with such a system (Marnewick, 2016).

Information storage and Management

The information storage and management activities are effortless due to a sophisticated information system that keeps data into a database management system (Stanton et al., 2017). For example, data could be found faster, including operational information, revision history, communication processes as well as customer or caterer profiles.

Behavioural Change

The online business will have improved processes and organized the framework to conduct operations. Hence, productivity and efficiency will be achieved through an automated WPE system.

Opportunities for New Services

The opportunity for launching new services is a benefit for the implementation of the WPE system. The information system will help online business by offering organized work activities for each process. For example, the on-time guarantee is a new service that will take full responsibility to provide catering services. Also, another action includes 5-star rating and credits for the caterers. Therefore, new services could be added to automatic systems which were incapable of making work activities much more comfortable.

Question 2

Stakeholders for the Weddings Parties Everything system (WPE)

A stakeholder for the WPE system could be anyone such as a group, individual entity, or a party that will have full interest in completion of project activities as well as system design and development outcomes respectively (Voinov, and Bousquet, 2010). For the WPE information system, the following stakeholders are identified:

System Owner: The owner of the system and the online business for WPE system will be responsible for approving the system working.
Customer: The customer will make an online profile and select catering service as per the occasion, food and beverage menu and offering feedback.
Caterers: The caterers will register with WPE, fill their personal information, as well as share their menu cards and payment for a subscription.
System Admin: The system admin will look into the administration process of the overall WPE system and perform process analysis.
Technical and professional staff: The technical and professional staff will manage all the activities related to business operations and manage the WPE system.
Sponsors: The sponsors will offer investment support to the company for making information systems with financial investments and cost budget.
Operational Manager
Project Manager: The project manager will organize WPE project activities.
System Designer: The designer will design the database system, prepare UI design and graphical inputs for navigation into WPE systems.
System Builder: The programmers and testers will build information system code and remove any bugs identified into the system.
System Analyst: The system analyst will prepare the workflow of the system with UML modelling.

Question 3

a. Functional Requirement:

Functional Requirements	Description	Input	Output	Processing
Register	Customer and Caterer both have to register after filling the form.	Customer fill job request form. Caterer fills profile form.	Account is created	Proper validation is done when submitting the form
Login	Log into the system using credentials	Username and password	Logged in	Username and password checked if correct then logged in if not later try again.
Payment	Credits are there so that Caterer can purchase them	Before register, Caterer has to buy the credits	Successfully, registered	Payment has to be done via PayPal.
Online form	The customer fills their job requirement form. Caterer fills their profile form.	Customer – Username, Location, requirement, event, cuisine, type. Caterer- Company name, Location, type, address,	The form is filled, then the account creation request is sent	All the details are checked and verified.
Hire	When a customer wants to final quotation then, customer can go to caterer profile can click on the button hire	Click on button hire	Caterer is hired	Notification is sent to Caterer and status is changed to booked
Cancel	Customer can cancel the job request. The Caterer can cancel the quotation request	Click on the cancel button	Job is cancelled	Notification is sent to a system that task has been cancelled
Rating and review	Customer can give rating and review to Caterer after the event is over	Go on profile and provide the ratings or review	Rating and review is saved	Rating and review sent to the Caterer by the system
Verified Account	Caterer can verify the account by giving – Proof, business name, logo.	Proof, Business name, logo.	Green tick mark is there in the profile	If the system accepts all the inputs, then that profile has a green tick mark.
Response time	The customer has 48hr to reply to the quotation of the three caterers otherwise request is cancelled	Reply in 48 hr.	The request is cancelled, if does not reply	System Check and if it crosses 48hr then request is cancelled.
Notification	Notification is sent for- credit alert to Caterer, whose quotation is not approved	System sends alerts	Customer and Caterer receive the alert	If no response is there, then caterer account is disabled.
Quotation	The system send mails to both the users until the final quote is not done	System sends mail	The response is handled, and the final decision is taken	Mail is sent for the quotation, which includes price, date of the event.
Profile	The caterer has the profile where they can give the link of there website, photos of past work, ratings- reviews and have the green tick of verified account	Business name, logo, type of events, location, Pictures, ratings	The trustable profile is updated	The profile is seen to the customer at the time of quotation.

b. Non-Functional Requirements

The non-functional requirements are a specification which will describe the capabilities and constraints of WPE information system operations to enhance and enable the functionality as well as services for end-users such as usability, speed, reliability, security etc. (Chung et al., 2012). Some important characteristics which are considered for the WPE information system are as follows:

S. No	Non-Functional Requirements	Description
1.	Usability	The usability represents the ease with which a customer or Caterer both could use the system. To keep human factors consistent, the system has a more straightforward user interface and navigation mechanism so that users will not be confused for selecting the processes.
	Security	Security is another non-functional requirement which ensures that the overall WPE system has a secure framework from protection against malware attacks and access to unauthorized parties. Hence, the system has a consistent password constraint which asks for a strong password at the time of the registration process.
	Reliability	Reliability states that a system should be extremely faulted tolerant so that it cannot have failure possibility. Therefore, WPS systems are made entirely accurate and contain less chance for critical failure such as session logging.
	Performance	The performance is proper and does not bring any issues while selecting a process or making payments into the WPE system at the time of execution.
	Quality	The quality of the information system is ensured by a bug removal process, also known as testing frameworks to check each module.
	Supportability	The WPE information system will have proper compatibility or portability with operating systems, computers, laptops, mobile phones, browsers for running and execution.
	Scalability	Scalability of WPE systems will have workload management on the network to meet performance goals such as consistency, session response, as well as intact security framework.
	Availability	The WPE system will be available to the customers and caterers at any time and accessed from any web browser so that both could reach one another easily.
	Localization	The localization is a new non-functional requirement which states that a system should match local specific areas for the WPE system has considered Location to select caterers from customers.
	Maintainability	The information system for WPE will have easy maintainability by fixing issues, increasing performance, fixing code errors or checking each module.

Question 4

a. User goal technique

Refer to Appendix 1

Use case Name	Login
Participating Actor	Customer, Caterer
Brief Description	Customer and Caterer login into the system by entering username and password

Use case Name

Participating Actor

Customer, Caterer

Brief Description

Customer register at the time of job request

Caterer register at the time of filling of all the requirement about the company .

Use case Name	Profile
Participating Actor	Customer
Brief Description	Customer can view the profile of Caterer

Use case Name	Hire
Participating Actor	Customer
Brief Description	Customer can hire the Caterer if they agree on the quotation

Use case Name

Cancel

Participating Actor

Customer, Caterer

Brief Description

Customer can cancel the quotation

Caterer can cancel the job request

Use case Name	Rating and review
Participating Actor	Customer and Caterer
Brief Description	Customer can review and rate the Caterer, Caterer can decide whether to add or not.

Use case Name

Update

Participating Actor

Customer, Caterer

Brief Description

Customer can update job request before it is not booked

Caterer can update the profile.

Use case Name

Fill up the form

Participating Actor

Caterer, Customer

Brief Description

Customer fill the job request form

Caterer fill the Profile requirement form

Use case Name

View Quotation

Participating Actor

Customer, Caterer

Brief Description

Customer can see the quotation send by system.

Caterer can view the quote send by order of the job request.

Use case Name	Payment
Participating Actor	Caterer
Brief Description	The caterer has to pay credits to the system before registration and pay after every three months.

b. Event Decomposition technique

Refer to Appendix 2

Event	Notification -Credit
Event type	Temporal
Use case	The system sends a message to Caterer
Brief Description	Caterer receives the notification if he is out of credit or he has to purchase.

Event	Matching
Event type	State
Use case	The system finds the match for job request posted by customer
Brief Description	Job posted by the customer needs a caterer, so system suggests 3 caterers with the perfect matching to the operation head.

Event	Email Handling
Event type	State
Use case	Operation head sends an email to Caterer and customer.
Brief Description	Emails are sent at the time of job request for the quotation until the final hiring is not done.

Event	Record of cancellation
Event type	State
Use case	Makes a record of cancelled jobs
Brief Description	Jobs which are cancelled by the customer for any reason is recorded, so that improvement can be made.

Event	Delete Request
Event type	Temporal
Use case	The system automatically deletes request after 48hrs if there is no response by the customer
Brief Description	If the customer does not reply in 48 hrs, for the quotation then system automatically delete request.

Event	Monthly Report
Event type	Temporal
Use case	Monthly report is generated
Brief Description	Every month, in the end, monthly report is generated for the overall growth and process of the system.

Event	Balance sheet
Event type	State
Use case	The proper balance sheet is maintained by the Accountant
Brief Description	Accountant maintains the balance Sheet for all the credits which are purchased by the Caterer

Event	Notification-hired/rejected
Event type	Temporal
Use case	The system sends a notification to Those who are hired and to those who are hired
Brief Description	Rejected is send to rest 2 caterers whose quotation is not approved, so the system automatically sends them notification of unsuccessful, and another one sends hired.

Event	Financial Status
Event type	State
Use case	Report is maintained by Accountant
Brief Description	Report is then submitted to the manager for the financial status of the company.

Question 5

Domain model class diagram

Refer to appendix 3

The domain model class diagram of WPE system which has customer and Caterer are briefly described below:

It has six main classes – System, customer, Caterer, Verified Account, Type of event. In this Type of event and Caterer are the parent class which has their child classes.
Caterer is an inheritance class which has child -wedding, birthday party and Corporate event which inherit all the properties of caterer class. The inherit class does not have any multiplicity with the parent class.
Type of event is also having child classes – buffer, Dinner party and cocktail party. They have inherited all the attributes of the parent class, id of the Caterer, Location of the Caterer and all the attributes which are in the parent class.
Customer can have more than one event but can only have one account on system.
System can have many caterers but Caterer cannot have many accounts.
System is connected with the customer and caterers both. Customer books the Caterer after the quotation has completed. Then system update the Caterer that it is booked and they can further exchange the numbers outside the system.
Internally, system send the quotes to both customer and Caterer. System also sends notification to the Caterer about the credits if they are finished.
The inherit class name is shown in italic – Caterer and type of event.
All the classes have different association between the conceptual classes and have different attributes in the classes. Here, in class diagram we cannot identify primary key or foreign key but every class has primary key or a unique key.

Appendix

Appendix 1

Appendix 2

Appendix 3

References

Chaudhary, P., Hyde, M. and Rodger, J.A., 2017. Exploring the benefits of an agile information system. Intelligent Information Management, 9(05), p.133.

Chung, L., Nixon, B.A., Yu, E. and Mylopoulos, J., 2012. Non-functional requirements in software engineering (Vol. 5). Springer Science & Business Media.

Marnewick, C., 2016. Benefits of information system projects: The tale of two countries. International Journal of Project Management, 34(4), pp.748-760.

Rubino, M. and Vitolla, F., 2014. Corporate governance and the information system: how a framework for IT governance supports ERM. Corporate Governance.

Stanton, D., Probin, R.J., Crisp, M., Osborne, K. and McWhirter, A.R., Honeywell International Inc, 2017. Security system storage of persistent data. U.S. Patent 9,767,676.

Voinov, A. and Bousquet, F., 2010. Modelling with stakeholders. Environmental Modelling & Software, 25(11), pp.1268-1281.

Information Systems Principles and Practice

Pssst… we can write an original essay just for you.

Question 1

Trigger

Benefits

Question 2

Stakeholders for the Weddings Parties Everything system (WPE)

Question 3

a. Functional Requirement:

b. Non-Functional Requirements

Question 4

a. User goal technique

b. Event Decomposition technique

Question 5

Domain model class diagram

Appendix

References

Remember! This is just a sample.

Save time and get your custom paper from our expert writers