2 PARTS******Part A, 5 pages with references******Design Document on checkout/payment online store business processes that need integration (the process of receiving orders from consumers, invoicing,

2 PARTS

******Part A, 5 pages with references******

Design Document on checkout/payment online store business processes that need integration (the process of receiving orders from consumers, invoicing, shipping or movement of goods and services, customer relations, and updating of employee information).

• Documentation of the business process supported by the integration project. The documentation should include a thorough description of the process and a visual representation of the process.

• Documentation of the system architecture required to support the system.

• Identification of all subsystems that will be integrated in the project. The subsystems should be clearly marked as either existing or new. Each subsystem should be described, and if new, the internal design of the subsystem should be documented. Note: some part of your system must include the use of a database and the design of this subsystem must include an Entity Relationship diagram.

• Required interfaces between the subsystems should be documented.

• Sufficient detail should be included to allow system development to be done based on this document.

• Adequately describe your target business process and the design of the system to support the process.

  *******PART B, 3 Pages with references******

  Create Project Plan for checkout/payment online store business processes that need integration (the process of receiving orders from consumers, invoicing, shipping or movement of goods and services, customer relations, and updating of employee information)

   The Project Plan should include the following:

• A project schedule in the form of a Gantt chart. The chart should be pasted into your Project Plan document. The schedule should be appropriate to allow completion of your project within the time constraints of the course

• A project budget including the anticipated costs for your project. Costs should include the design, development, training, testing, deployment, maintenance and other costs which you may identify. The costs should be estimated as though the project were being developed in a real-life situation. If the budget is prepared in another program, it should be pasted into your project plan document. The budget should identify the cost items that would normally be included in a systems integration project. Understandably, the small nature of your project might mean that many of the line items will be zero cost, but the items should still be included to demonstrate that you understand the budget considerations for systems integration projects of larger scope.

• Identification of high risk areas in the project and comments regarding how these potential problems can be addressed.

• The document will be assessed based on your ability to adequately create a schedule and budget for your project and plans to address potential problems.