B2B website online store Magento like

ET B2B Shop Functions : 1. Preordering 2. Agents Login and sales 3. Product price /categorie/stock filter 4. Online Help , Callback , Chat( Product help on each product page) 5. Automatic currency converter (Just as a tipp for the customers) 6. Ticket System 7. SuggestPrice for coming soon products 8. Login / Logout 9. Fixes quantity 10. Out of stock product wait 11. Todays Deal (Counter) 12. Crossselling 13. Onsale [login to view URL] Seller items 15. Multilanguage function ( we provide the lanuage files and set them in the backend) 16. SEO 17. Template : [login to view URL] Here-under you will find the required information, System Specifications (Business Requirements): Non-functional requirements: there are following additional non-functional requirements: Solution shall comply with existing services architecture, i.e. following aspects: Authentication. Payments. Look-and-feel of the service User Interface (UI). Integration with our IT systems ( E R P) Implementation project shall be reasonably cost-efficient and with short implementation schedule. Possibility of seamless migration of solution servicesto the ESB infrastructure. Solution shall be secure, i.e. strong authentication,support for logging and audit trail. Solution architecture shall enable sufficientavailability to accommodate all possible request evenduring top load periods. The solution deployment architecture shall becompatible with requirements of our computing environment as services hosting platform. Logistics: Consumers find a product of interest by visiting the website ofthe retailer directly. Once a particular product has been found onthe web site of the seller, most online retailers use shopping cartsoftware to allow the consumer to accumulate multiple items andto adjust quantities, by analogy with filling a physical shoppingcart or basket in a conventional store. A "checkout" processfollows (continuing the physical-store analogy) in which paymentand delivery information is collected, if necessary. Some storesallow consumers to sign up for a permanent online account sothat some or all of this information only needs to be entered once. The consumer often receives an e-mail confirmation once thetransaction is complete. Less sophisticated stores may rely onconsumers to phone or e-mail their orders (though credit cardnumbers are not accepted by e-mail, for security reasons). Change Management: 1. Development: ◦ i. All realisable requests are linked with changes to the code base; the actual code is written in the development stage according to initial taskdescriptions.
 ii. The development stage cannotbe skipped. a. Review: ◦ i. During review, the reviewer verifies theentire code written in the development stage and improves on itsquality where possible. If necessary, the code is sent back todevelopment together with descriptions of detectederrors.
 ii. Review cannot be skipped. Thequality of review depends on the reviewer’scommitment.
 iii. The inspection stage wasintroduced because nearly ¼ of all changes made by developershave serious technical deficiencies that often hindered otherdevelopers’ work. a. Integration ◦ i. During integration, the changed code isdeployed to appropriate release branches according to planning. 
 ii. Integration cannot be skipped. 
 iii. The integration stage was introduced asbefore it was impossible to monitor which change had beenalready deployed to which release.
Change requests will affect theproject time and cost. • Release Manageme