MIS350 CSUGlobal M 4 5 6 Mamma Pia Purchasing Implementation With Devops OPTION #1: PHASE 4: PURCHASING IMPLEMENTATION WITH DEVOPS Please refer to the ful

MIS350 CSUGlobal M 4 5 6 Mamma Pia Purchasing Implementation With Devops OPTION #1: PHASE 4: PURCHASING IMPLEMENTATION WITH DEVOPS

Please refer to the full description of the Mamma Mia Purchasing project. In Weeks 4, 5, and 6, you wrote one section of the final report (this week you will also incorporate all previous sections, with any adjustments that you may want to make to it based on instructor’s feedback or any other reason). As such, the paper should not be written as an essay (with introduction and conclusion) but, instead, as a business report containing only the specified subsections from each week.

This week you will include in your report sections 1 through 6 (developed over Weeks 4, 5, and 6), and also add the new sections 7 through 10 for this week. These last four sections, added this week, should have at least 900 words and will summarize the Purchasing information system’s testing, user training, and implementation using DevOps. The Mamma Mia CIO wants to implement DevOps, and she decided to implement it using this project as a pilot.

Note that parts #1-6 are completed in the Portfolio Milestones. For this module, you will complete parts #7-10.

The specific subsection headers to include are as follows:

7. Test plan
8. Training plan
9. DevOps
What is DevOps?
Why does Mamma Mia need DevOps?
Costs
Financial benefits
Other benefits
10. Implementation strategy and plan using DevOps.

Include a title page and reference page. Make sure your paper follows APA style according to the CSU-Global Guide to Writing and APA (Links to an external site.)Links to an external site..

As support for your analysis, use at least two CSU-Global Library resources and/or outside, credible academic sources other than the textbook, course materials, or other information provided as part of the course materials. (You may not use Wikipedia for any CSU-Global assignment.) For this assignment, a credible source is defined as:

Scholarly or peer-reviewed journal articles.
Newspaper articles.
Trade or industry journal articles, publications, or websites, including those from trade organizations. Consider CIO Magazine, the Harvard Business Review, Fortune, and similar solid sources.

Please be sure NOT to use direct quotations from sources and, instead, use paraphrasing or summarizing when needed. MIS350 — Portfolio Project Description
Company Background (both Options, #1 and #2)
Mamma Mia is a well-known pasta company producing dry pasta products and distributing it to
supermarkets and other food outlets nationwide. Mamma Mia has 20 plants and distribution centers
throughout the country, with the company’s headquarters located in Denver, Colorado (where the
oldest plant / distribution center is located.)
Mamma Mia currently uses a reasonably complete and modern integrated home-developed information
system, except for the Purchasing and the Accounts Payable systems, which due to complicated
historical reasons, were never implemented by the IT department and were instead developed and
implemented with user-built MS Access database apps. The integrated system used in most other areas
of the organization uses a client-server-server architecture based on large HP-UX servers running an
Oracle database. All servers are hosted in the company headquarters in Denver and all other plants and
distribution centers connect to this centralized server farm through redundant and highly efficient
communication links. Uptime of the network has historically averaged 99.8%, with an average
downtime duration of 33.5 minutes. The company is happy with these numbers and will not consider
using cloud-based services for the time being due to information security concerns and also due to
having a very conservative executive management team.
The company has decided, however, that to adjust both the Purchasing and the Accounts Payable
information systems’ functionality to the current business needs, it has become necessary to upgrade
and modernize both. As such, the Steering Committee –comprised of all executive-level managers of
Mamma Mia– has decided to request from IT two project proposals aimed at replacing both systems,
with “Option 1” being the Purchasing system and “Option 2” the Accounts Payable system. The scope of
both project options will comprise the noted information system as a stand-alone, independent system;
later, in a second phase of the project (not covered in MIS350), the new system will be integrated with
the other information systems already used in Mamma Mia.
Deliverables (Option #1)
You are asked to analyze the specifications and produce an information system design that complies
with the operational procedures and data requirements described below. As the description is
purposely kept brief, you may have to use your imagination to supply some of the missing pieces in it –
also please consult with your instructor to clarify any possible doubt about these operational procedures
and the data requirements.
The deliverables for both options of this Portfolio Project of the course are as follows:
Phase 2 (due on Week 5) – Data Flow Analysis:
1) Data requirements:
a) DFD diagrams (context, level 0, and multiple level 1s.)
Requirements
Purchasing (Option #1)
The purchasing information system handles the purchasing operations of the organization for the
acquisition of good and services. In general, a purchase requisition is issued by the requesting
department and sent to the purchasing department. Purchasing then determines if the request is
acceptable based on company policy and procedures (for example, if requestor’s purchasing limits cover
the purchase, if the goods requested already exist in inventory, if the item will be arriving soon through
a previous purchase, etc.) If the requisition is approved, then the purchasing department proceeds to
select one or more vendors, optionally request an RFQ (request for quotation) from at least three
vendors, analyze the offers, select a vendor, and then prepare a purchase order.
The purchase order is sent to the vendor for processing and it signifies the formal request to purchase
the good or services, with a promise to pay once delivered and accepted — the payment terms are
specified within the purchase order. Copies (physical or electronic) of the purchase order are sent to
Receiving (for reviewing the delivery from the vendor) and to Accounts Payable (for payment to the
vendor.)
Receiving receives the items and checks them for quantity and quality against the specifications in the
Purchase Order. If they do not match, then the items will be rejected, and Purchasing is notified of the
discrepancy. If the items are acceptable, then a receiving note is prepared, and copies distributed to
Purchasing, Warehouse, and Accounts Payable. The items are sent to the Warehouse for storage and
distribution.
A flowchart of the entire process is the following:
Running Head: PURCHASING INFORMATION SYSTEM
Module 4,5, and 6
05/07/19
1
PURCHASING INFORMATION SYSTEM
2
A brief description of the company and the system’s environment
The company Mamma pia is popular due to its pasta business by manufacturing dry past
products and further distributes it to the outlets and supermarket on a national scale. The
company boasts of twenty plants and centers for distribution centers in the nation. The firm is
headquartered in Denver Colorado where it pioneered its operations. The company has installed
almost complete, and state of the art home created an information system, excluding the accounts
payable and purchasing system, which is because of historical concerns, were not executed by
the IT department and were nevertheless created and executed with MS Access database
applications.
Detailed requirement lists
The requirements of the project involve an information system which will be able to
complete the purchasing operations of the company to acquire products and services. The system
must be processing a requisition for purchasing which therefore must be forwarded to the
purchasing department. The department must also be able to approve if the request is accepted by
the procedures and policies of Mamma Mia. This can be the limits for purchases, the need for
new products and if there has been an existing purchase order for the product. Upon approval for
the requisition, it is imperative for the department of purchasing to choose a vendor, collect
request for quotation from a minimum of three suppliers, evaluate the offers, choose a supplier
and finalize the preparation of the purchase order (Laudon,2011).
The system will be able to send the purchase order to the supplier to begin processing,
and it implies the formal request to buy the products and services, with the agreement to pay
upon acceptance and delivery with the information found in the purchase order. Through the
PURCHASING INFORMATION SYSTEM
3
system, the physical or electronic forms of the purchasing are transferred to be received for the
review from the supplier and hence to the accounts payable to process payments (Laudon,2011).
The receiving gets receipts of the products and undertakes a quality assurance check and
quantity in comparison to the purchasing order. Any discrepancy between the two will lead
rejection of the products and the supplier duly informed of the purchase problems. If the state of
the goods is acceptable and they are taken, it becomes imperative to create a receiving not and
prompt distribution of the copies to the accounts payable, warehousing and purchasing. Upon
completion of this process, the products and services are moved to distribution and storage
(Laudon,2011).
Feasibility analysis
Product
The product, in this case, is the information system which is projected to improve the
critical functions of the Mama Mia which involves lessening the stresses and logistic problems
involved in the purchasing process of the company. The system will be improving the operations
of the company and automation of the process will make it easier to maintain the quality and
quantity of the purchases of the company.
The industry
Mamma Mia is in a very competitive industry if dry pasta foods which pose a great
rivalry in terms of market share. The main competitors to Mamma Mia in the US market are
Barilla boasting of a large market share from US households. Customers buying groceries also
prefer store brands. Another company Mueller also commands a strong market share and is
preferred by households. Therefore, it is imperative for the information system to implemented
to compete effectively with the other companies (Bardiani,2010).
PURCHASING INFORMATION SYSTEM
4
Nature of the market
The pasta market boasts of many players, and it is popular among the households and the
retail stores. The firm has to implement the system which will make it possible to improve
efficiency and compete effectively with the other significant market players. As of 2013,
approximately 64% of American citizenry preferred pasta which makes the market steady and
productive (Bardiani,2010).
Amount of capital required
The installation process of the information system will be done in stages, and hence the
costing process will be done in stages. The total estimated cost is 20,000 dollars which will cover
for the sourcing of the hardware, software, installation, hiring of staff and training of existing
staff on using the new system.
Structure of the project using SCRUM:
Structure of the project
The project structure used will be a programmatic structure which is a traditional
structure where the program sector managers maintain the authority of many resources in the
project. The structure is applicable since it involves a single program sector and hence It will not
disrupt the activities of the firm much. An individual from a single area will staff the team of the
project. The entire resources of the project will come from a single department. In this case, the
project will be carried out in the purchasing department (Pries,2010).
Initialization activities
The activities to initialize the project will be the creation of a vendor which will contain
the details necessary to prompt the beginning of the information system. Other details include the
creation of a purchase order which will have all the details regarding the purchasing activities of
PURCHASING INFORMATION SYSTEM
5
the company. Moreover, the initialization also includes the making of a receiving note with
details showing the acquisition of the products and the services by the company (Pries,2010).
Proposed intermediate SCRUM deliverables.
Sprint plan meeting: it will involve the tasks to be undertaken, the company management and
the project team meant to deliberate on the aspects of the product backlog, in this case, the tasks
to be included and finished in the sprint (Pries,2010).
Daily scrum: it is held daily and includes interactions of the sprint members of the team who
discuss the days previous day’s activities, the activities to be undertaken in that day and
recognize any hindrances. These meetings are short and harmonize the members of the team.
Sprint review: after the conclusion of the sprint, the team depicts the functionality implemented
in the sprint. This meeting involves getting feedback from the company management and other
stakeholders called to the review (Pries,2010).
Sprint retrospective: at the conclusion of all the sprints the team takes part in a retrospective
meeting to mirror end of the sprint and recognize opportunities to enhance a new sprint.
Context Diagram
The data flow diagram is used during the design phase, and Mama Mia sells pasta and pasta
market. The company has to implement a system that will increase efficiency and compete with
other company in the same industry. It is a popular view that customers prefer a steady supply of
pasta. Therefore, the company needs to automate its pasta purchases. The dataflow in the system
is to manage all purchases during the purchase requisition. (Housel, Waddle & Yao, 2017). The
major components of the purchasing system are the supplier, finance and logistics. The following
diagram shows a context diagram for the Mama Mia Pasta Purchasing system.
PURCHASING INFORMATION SYSTEM
6
Figure 1. Context Diagram
Product Shipment
Logistics
Products
Supplier
Purchase Order
Pricing
Inventory List
Payment
Purchase
Management
Purchase Order
Payment
Approve REquest
Accounts Payable
Financial Statements
Top
Management
Finance
Department
Purchasing Requests
Finance Requests
Purchase Order
The above context diagram shows the relationship between Logistics, supplier, finance
and the top management. The context diagram gives the flow of information, for example
from senior management to the purchasing department, there are purchasing requests and
finance requests from both ends. Supplier interacts with the purchasing department. The
data include pricing, purchase orders and payment.
DFD Level 1
PURCHASING INFORMATION SYSTEM
7
Purchase From the supplier
Information about supplier
Request Specifications
Request Details
Suppler Market
Price of the Purchase
Generate Purchase
Order
Supplier Infomation
Purchase Order Details
Supplier
Data Store
Supplier Information
Data Store
Purchase Order
Checked Purchase Order
Supplier Contact
Request Order Details
Forward Order to
Manager
Purchase Order for Checking
Level 2.1 DFD: Purchases
PURCHASING INFORMATION SYSTEM
Customer
8
Payment Confirmation
Payments
Check and Bills
Payments
Process Payment
Account Amount
Account Amount
Insert Payment
Read Payment
Update Open to Buy
Edited Payment
Payment
Account Amount
Account Amount
Edit Payment
Update Balance
Account Amount
Accounts
Accounts Payable Level 2 Data flow Diagram
Invoice
Purchase
Management
System
Vendor
Order for Goods
Order for Goods
Account Payable Systems
Return Order
In the above diagrams, purchases and accounts payable are connected. The system can
order goods; when orders are made, the accounts payable are affected by the transactions.
PURCHASING INFORMATION SYSTEM
9
The order of products is payable to the accounts payable and are all recorded in the
purchase systems.
Purchasing Process: Dataflow Diagram
Purchasing
Processing
Vendor Data
PO Account Payable notification
Receive Report
Purchases
database
Inventory
Metadata
2.0
Establish Payable
Vendor
GL Updates
Vendor Invoice
Accounts
payable
Pay Vendor
General Ledger Cash Disbursement
General Ledger
Process
Make Payments
Cash
Disbursement
The purchasing accounts include cash disbursement subsystem, general ledger processing
and also records for account payable. The data is stored in the purchasing, vendor and
PURCHASING INFORMATION SYSTEM
10
inventory metadata tables (Batini, Ceri & Navathe, 2009). Other entities are attached to
the purchasing system such as vendor management and ledger processing done at this
stage.
Accounts Payable DFD level 2.2
The account that traces debtors cannot be detached from the accounts payable. The DFD
that follows gives the dataflow between purchases and the accounts payable accounts
(Labio, Quass & Adelberg, 2007). There is a cash disbursement database whose role is
to save other data that is related to the accounts payable. In the accounts payable, there is
a program that is used in selecting and recording payments.
Accounts
Payable
Cash
Disbursement
Prepare, Propose
Payments
Issue and Records
Disbursement
Approved Payments
{Proposed Payments
Cash Disbursement
Vendor Payments
Select and record
payments
PURCHASING INFORMATION SYSTEM
Approved Bills DFD level 2.3
11
PURCHASING INFORMATION SYSTEM
12
Invoice
Approve Bills
Prioritized Bills
Sales Box
Selected Bill
Prepare Check
Check Register
Compare
Register info
Balanced Checkbook
Statement
Check Document
Bank Statement
This DFD is used in monitoring the approved bills, preparing checks and saving the
prioritized measures in a sales box. After the proposals are approved, checks are
prepared and compared against the actual sales. The last process is combing the bank
statement for the misplaced bills and misappropriated funds.
PURCHASING INFORMATION SYSTEM
Purchasing Vendor Relationships: Level 2.4 DFD
The DFD above gives a summary of the data flow between the vendor and the purchasing
department. Other concerned objects include Management that prepared reports on the
purchases. Before any payment is made, a vendor remittance advice is done, and all the paid
invoices are stored in the paid invoices database. Cash disbursement journal is used to trace all
13
PURCHASING INFORMATION SYSTEM
14
the cahs as they are disbursed by the company. From the diagram, the vendor also manages the
records payable. Collects the receiving orders and cash disbursement. The rest of the
relationships are shown in the following diagram. Fig 1 below shows the relationship between
the vendor and the management and how checks are handled during the invoice payment. From
the approval to pay the order, the vendor provides the invoices to be paid, the invoices are
compared with the purchase order, after which they are queued alongside other pending invoices.
From Pending invoices, the management authorises the payments and pays the invoices.
Vendor
Pay Invoices
Purchase Order
Management
Authorization
Pending Invoices
Figure 1: Relationship between vendor and Management
Logical ERD
Generate
Cheques
Authorised Invoices
Paid Invoices
PURCHASING INFORMATION SYSTEM
15
The Logical data design is made during the requirements where it serves as a communication and
specification tool for system analysts and business. The data dictionary in the logical data design
defines the elements of logical data model. The logical data model is utilized by the business
analysts/users and utilises user friendly notation (names) as opposed to the physical model which
utilizes abbreviated names.
Contact
Purchase Order Description
PK
PK
Item_Code
Contact_Number
Title
Requisition Description
Quantity_Ordered
Name
Measuring _Unit
Address
Unit_Price
Phone_Number
Quantity_requested
Currency_Code
Fax_Number
Measuring _Unit
PK
Item_Code
Note Description
PK
Item_Code
Quantity_Ordered
Email_Address
Measuring _Unit
Website_URL
Have
Have
Has
Purchase Order
Has
PK
POrder_Number
contains
Vendor
Request
Purchase Requisition
PK
Vendor_Number
FK
Vendor_Number
FK
Contact_Number
Vendor_Name
FK
Purchase_Requisi
tion_Number
Vendor_Status
gets
Recieving_Note
PK
Recieving_Note_
Number
PK
Purchase_Requisition_Number
Requisition_Mng_Emp_Number
Requisition_Type
Prdt_Recieved
Ship_to_Address
POrder_Number
Date
Business address
POrder_Date
Vendor_Number
Remarks
Multiple_Contacts
Payment_Terms
Date
Suggested_Vender
Currency_Code
Tax_Rate
Vendor_Number
Notes
Requisition_Description
Note_Description
POrder_Descripti
on
PURCHASING INFORMATION SYSTEM
16
Physical database design.
The Physical data design is made when translating the top level model into actual tables in the database.
Likewise, the data dictionary in the physical data design describes the real tables and columns in the
database. The physical data model is utilized by the system developers and architects. As from the
diagrams the physical model utilizes abbreviated names and includes data types and lengths.
Contact
PK
Purchase Order Description
PK
Item_ID
int
Qnty_Ordered
int
Varchar
(50)
Msrng _Unit
Note Description
PK
Item_ID
Float
Curren_ID
int
int
Title
Varchar
(50)
Name
Varchar
(50)
Address
Varchar
(75)
Phone_Number
int
Fax_Number
int
Requisition Description
PK
Item_ID
int
Qnty_requested
int
Msrng _Unit
int
Qnty_Ordered
Msrng _Unit
Unt_Price
Contact_ID
int
Varchar
(50)
Have
Email_Addr
Varchar
(75)
Website_URL
Varchar
(50)
Varchar
(50)
Have
Has
Purchase Order
Have
PK
contains
POrder_ID
int
Vendor
Purchase Requisition
Request
FK
Vend_ID
int
FK
Cntact_ID
int
Vend_Name
Varchar
(50)
FK
Purchase_Rqstn_ID
int
Vend_Status
Varchar
(50)
Prdt_Recieved
Boolean
Business
address
Varchar
(50)
Multiple_Cont
acts
Varchar
(50)
Recieving_Note
PK
Rcvng_Note_ID
PK
Vend_ID
int
FK
POrder_ID
int
FK
Vend_ID
int
Date
Timesta
mp
Note_Descr
Varch…
Purchase answer to see full
attachment