Assignment 3.4 - Ritvik.Deshprabhu

SOFTWARE IMPLEMENTATION PLAN Development Methodology 1. Introduction – While building a software platform for MMCT, we need to consider the following issues to be solved – a) Improved tracking system regarding information of vehicles purchased/sold. b) Identity access management related to sensitive data c) Method to align maintenance team across all locations such that they can resolve every issue raised as efficiently as possible 2. Agile Methodology – Using Agile methodology would be ideal to build a software platform for MMCT. Here, building a tracking system would be a priority for the project. Parameters such as Vehicle cost, history, condition, buyer/seller info and MMCT location where the vehicle is sold would need to be considered while building a tracking system. As this is the heart of the project, starting on this and further moving on to add additional features such as security parameters, access management, maintenance notification systems, etc. can be done using Agile methodology. This will also help save costs and time as the project can be dumped and started from scratch as compared to implementing the entire system together and later having the system fail entirely. 3. Cloud – The platform will be built in – house and may require constant maintenance. To save costs (i.e – avoid hiring extra developers) and also boost efficiency, we will consider using Platform as a service to avoid maintenance of the servers. 4. Stateful System – Using cookies to keep track of user information will help send reminders to complete their application and also provide a seamless experience in completing a transaction without interruptions. 5. Architecture – Considering that MMCT deals with around 300 transactions a day which include buying, selling and maintenance charges, we will consider using a 3-Tiered system to be appropriate for the software platform considering the size of the expected data and traffic. Determining if the project is on track or not Since we have chosen the agile approach, the project can be broken down in 5 parts listed below. Further, the project will be tested and debugged after every step to determine if additional resources are required or if the team needs to take an alternative approach. The ideal time frame to build the software platform will be 10 months.

Steps Milestone 1. Build a team of 7 SDEs, 1 project manager, 1 accountant dedicated to the project. Additional workers can be hired depending on the complexity of the project. 2. Design the project outline, build a tracking system to handle issues such as vehicle cost, history, condition, buyer/seller info and MMCT location where the vehicle is sold. Once this step is complete – testing, debugging and maintenance will be a priority till its perfected. 3. Code to add additional features related to payment such as Payment method (Card, Cash, Net Banking), payment platform, invoice generation etc. 4. Install extensions, design UI, add all additional features such as maintenance requests which can be closed after completion. 5. Security parameters, Identity Access Management End Final Testing Implementation Method 1. Background – Before choosing an implementation method we consider the following factors: i. The software platform will be majorly based around the tracking system, followed by access management, security and maintenance services. ii. Since we assume that the website faces about 300 transactions a day, we will assume there are about 16 staff members behind the screen taking care of different parameters. iii. We assume that all the staff is hired on site and no staff member works remotely. 2. Method – For implementing this project, we will go with a phase approach where we change one feature at a time to transition smoothly into a whole new system, without disturbing the constant traffic faced by the website. This will also lower the risk of failure and having to completely shut the website down till its fixed. We will start with implementing the tracking system where it can be debugged and improved while running the rest of the website as it is. Further, we will implement a payment system, additional security, and maintenance options into the website. Training and Documentation 1. Documentation – i. User documentation can be made in the form of binders or manuals for which a technical writer can be hired on contract. Further, Data flow diagrams and entity relationship diagrams can be added in the binders to provide a complete structure on how the software platform works. ii. Walkthrough recordings to be created in the following manner – a. 16 videos for explaining debugging and maintenance related to tracking customer and vehicle information. b. 5 videos explaining the payment system and general maintenance and debugging required. c. 7 videos to explain security parameters and access management.