updated project plan

1

Title of the Project – Online Clothing Store

Objectives

· To come up with a web application which allows customers to purchase a variety of products sold online from different vendors from many locations.

· To provide the customers with an easy interface to use, Parkin (2009). 

Essential Requirements

· Clients–making registration secure and keeping their profiles manageable (Providing quick navigations through the pages and securing the payments gateway)

· Vendors – keeping registration secure and ensuring their profiles are manageable (Adding, modifying or deleting, the items already posted)

· Administrator –approval authorities and ability to reject requests for the new items (May take control vendors and clients activities) according to Rose (2003)

Deliverables

· Web Portals/apps for the desktop, laptops, phones, etc.

· Manual for support explaining the risks that are involved.

Benefits

· Making shopping Convenient

· Single window retailing as well as multi-vendor

· Searching and sorting the options for different products

· Selections options from many vendors providing the homogenous product with varying prices

· Simple, easy, secured payment options among others.

· Complaint registration and support tab.

· List of suggested products and services are displayed to the customers.

· Clients may download versions of PDF manuals provided by the vendors who upload

· Detailed sales reporting, Siddiqui, O’Malley, McColl & Birtwistle (2003).

Scope of the project

In scope

The websites for the desktops are compatible with Chrome, IE as well as Mozilla and Purchase of items which are available on website platform.

Out of Scope

Payment Gateways are linked via the APIs which is not compatible for the mobile users, that is, the Administrator, Customers and Sellers as well

 The Critical Success Factors (CSF) is the maintenance of a Backup System, Termination of transactions, when linkage to the payment gateway fails, and the Customer as well as information about Products are kept in a completely Secure Database.

The Key Performance Indicators (KPIs) deals with maximum traffic existing at every point in time, small number of the Clicks, customers must perform and less page numbers to reach to their expected items and do navigation between the pages expected to be comfortable.

The Database Details include the Purchase History’ Credit Card, Admin, Inventory , Order Details Customer, Review, Transactions, Vendor, Complaints, Shopping Cart, Transaction, and Order (Li, Wang, Wong & Lee, 2005).

Team Structure

1. The Project Manager

· The Technical Architect

· The Team Lead 1 consisting of Developers: 1, 2, 3, and 4.

· Team Lead 2 consists of Developers: 5, 6, 7, and 8.

2. Testing Manager

· Test lead: team lead 1.

  Risks Involved

a) Risks associated with the Product Size: the estimated product size of several files, programs, transactions; database size used or created by the main product; projected changes number to requirements required for product, before delivery and the after delivery (Li, Wang, Wong & Lee, 2005).

b) Business Risks: quality and amount of documentation of the products which should be produced then delivered to clients; deadlines of Deliveries; Costs related to late deliveries as well as delivery of defective products.

c) Client Risks: While doing the work for the very first time; will clients accept to spend more time in the formal requirements involving gathering meetings so as to make identification of the project scope; making effective Communication with developers and Understanding SDLC procedure.

d) Resource Risks: the Resource Number and that of skillsets as well as Commitment for the whole duration.

e) Technology Risks: demanding of new technology by Customers and the Requirements for placing excessive constraints on the performance of the product.

Change Origins are the new market or business conditions, scheduling constraints and demand Budgetary of the Customer (Li, Wang, Wong & Lee, 2005).

The process of Change control

The process involves two paths. The document flow and decision flow. They both start from planning document and requested a change, and the document change ends at the updated document stage while the decision path ends at the implementation stage.

REQUEST FORM CHANGE

· Project name

· Reason for the changes

· Project sponsor

· Disposition: approved, deferred or disproved

· Request number

· Originator

· Areas of impact of the suggested changes in terms of cost, scope, risk and schedule.

· Description of requested changes

· Priorities, that is, emergency or low

· Sign off approvals by the project sponsor, the project managers and the project customer, dates

· Date

· Changes proposed

· Funding scheme which includes the budget reserve, management reserve among others according to Lee & Lin (2005).

QUALITY PLAN

The following list parameters will be measured in terms of quality plans for effectiveness:

· web portal Easy usage

· satisfaction of Customers regarding those services offered

· conversion of Click-sales

· response time of the Website

· complaints of Customers regarding the services offered are addressed

· service time of the Customer

· Number of clicks performed to located the product required

· Personal data Securities, Lee & Lin (2005).

Principal factors of product quality

· Product Quality technology: latest versions & as per requirements

· Budget & schedule

· Process quality

· People’s quality

Product quality attributes

· The response time Must be as low as possible

· no making of wasteful usage of system resources which include memory space, disk or CPU time

· Easy user interface of the customers, vendors or the admins

· Recovery Ability after crashing, dealing with malware threats, errors and slow down (downtime) as well as unforeseen and unresponsive events

· software sources which are Trustworthy

· easy maintenance

· Evolving to meet dynamic changes in needs of the customers

· Reliability which includes the same output for every moment there is a similar type of input

· Availability at all times even during times of high traffic

· The Codes should be able to be reused meaning the functions of the customers are developed and are also customized for all vendors according to Lee & Lin (2005).

Elements of Quality Assurance

· Standards – making adherence to the CMMI, ISO, six sigma, and other standards

· Audits and Reviews – quality guidelines are adhered to in all the steps during the development of the software.

· Testing –no entry without a login, the search results must match the requests

· Error or defect collection as well as the analysis determines the error source

· Vendor management; quality of the vendors is supposed to match the requirements of our business as it is related to the process and the software

· Management of Security – this include threats like hacking, malware and privacy of customer information Parkin (2009). 

Engagement of the Third parties

· Payment gateway

· Customer service

· Technology vendors

Reference

Parkin, G. (2009). Digital marketing: Strategies for online success. Fox Chapel Publishing.

Rose, J. G. (2003). The joys of enterprise portals. Information Management, 37(5), 64.

Siddiqui, N., O’Malley, A., McColl, J. C., & Birtwistle, G. (2003). Retailer and consumer perceptions of online fashion retailers: Web site design issues. Journal of Fashion Marketing and Management: An International Journal, 7(4), 345-355.

Li, M., Wang, J., San Wong, Y., & Lee, K. S. (2005). A collaborative application portal for the mould industry. International Journal of Production Economics, 96(2), 233-247.

Lee, G. G., & Lin, H. F. (2005). Customer perceptions of e-service quality in online shopping. International Journal of Retail & Distribution Management, 33(2), 161-176.