the assignment is to look at the project and explain the design viewpoints for this project, I have attached the project and will also attach the requirements
Project Sportify (Group 3) 1. Introduction 1.1 Purpose and Overview Sportify , as the name suggests, is a sports-based e-commerce website which sells best quality sports equipment, gears, clothings and famous merchandise not just in Australia but all over the world. Keeping in mind about the young people getting increasingly fascinated about sports wear, the website plans on selling sportswear of highest quality with the best affordable price ever. The question is what makes this website different than other sporting websites and the answer is customer will get to experience hot weekly deals which are heavily discounted, customer will be able to join weekly raffles to win free high quality products, customer can earn loyalty points through which they can buy items with those points and many more. Talking about the usability of the website, the website is very easy to navigate with important links right at the top, themes very eye-catching, fonts very readable and is very easy to navigate to the whole website. Intended Audience This document is mainly intended for all the project members who are working on this group and to all the related stakeholders who have invested on this project. 2. Project Organization 2.1 Process Model: Agile We’ve decided to adopt Agile methodolgy in our project as it helps to make the project run smooth and is way more manageable than the projects following Waterfall methodology. Waterfall methodology follows sequential approach in managing a project which may be bit of a disadvantage to the project if the customer intends to change some features in the future. While in other hand, Agile is much more flexible and change management is much more easy in this methodology. Furthermore, the project tasks are divided into many smaller portions called sprints which makes it easier to manage and review. 2.1.2 Requirement Analysis Before the project starts, the client lists the features or requirments that he/she want in the web application and based on that the developer working on the project creates different features within the scope of the project. In Scrum Agile Methodology, requirements are usually documented using product backlog which is recorded as user stories which makes it easier to better understand the requirment of the product. Product Backlog The Web application that we are going to develop is not a third-party seller e-commerce application like e-bay but is for a company that directly sells its products to its customers. So, there are three actors which are the customer, admin and the system. Actor User Stories Customer Must be able to register an account. Must be able to Log In to the account. Must be able to change Password. Must be able to update personal details. Must be able to view products. Must be able to Search Specific products. Must be able to select sizes of the product if applicable. Must be able to add products to the shopping list. Must be able to order/buy/cancel products. Must be able to contact customer support if needed. Admin Must be able to Log In as an admin. Must be able to edit product or make changes. Must be able to access the database. Must be able to react to any customer queries related to transaction or other issues. Must be able to deactivate account of suspicious users. System Must be able to store records of clients and admin. Must be able to handle large amount of queries. Must be able to support certain updates. 2.1.3 Analysis Review Reviewing a software is important because the software is meant to be for the customer and their satisfaction is the topmost priority. As we develop the website, our team members will conduct a survey to people of different demography about what they think about the website and what things they would have added if they were to. What this does is helps the project members find out about the needs and requirements. Since, we are following the Agile software development methodology, making changes in the website should not be much of a concern as long as we fulfill the customer’s demand. 2.1.4 Software Design MVC Architecture We have decided to adopt MVC software design architecture for our website development. Most of the e-commerce websites and applications uses MVC architecture as it supports the functionality needed in such websites. MVC stands for Model View Control. Each component in this architecture has a different but important role. Media interacts with the database and also acts as an intermediary between the controller and the database. The View component is used for creating user interface and processes all the business logic whereas the controller component acts as the intermediary between the model and the view. 2.1.5 Prototype: Front End Prototype Registration Page Login Page 2.2 Organisational Structure 2.2.1 Project Manager and Tasks Project Manager is responsible for managing the project making sure the project finishes on time and within the budget. He/She is also responsible for keeping an eye on the progress of the project time to time as well as every project members are on the same page. In our project, Saurav is the project manager. 2.3 Organisational Boundaries and Interfaces After the project team has been formed, the project manager assign project-related tasks to all the members based on their skill-set. Since, the project has adopted Agile methodology, the project members share their part of the progress after every sprint in team meetings and made sure no one is lagging behind. To communicate with the team members, we used following tools: Trello: Project management tool to keep track of progress. Whatsapp: Texting and Video Calling for daily meetings. Google Docs: To create this document. Githhub: To test the codes for the website. 2.4 Project Responsibilities Here are the list of the members of the team along with their responsibilities: Project Member Responsibility Saurav Sitaula Project Manager, Web Developer(Front-end, back-end) Atisha Tamang Scrum Master Bhishma Raj Yonjan Web developer(front-end) Brivesh Bhattarai Document Editor Santosh Liaison Manager 2.4.2 Project Sponsor: Mehedi Hasan is the project sponsor of this project who has financially supported the project as well as provided with necessary equipments necessary for the projects. 2.4.3 Liaison Manager Santosh is the liaison manager of our project who is going to co-ordinate with the company and the project teams . Managerial Process 3.1 Management Objectives and Priorities · Work with web developers to ensure that the website is up and running and updated regularly. · Increasing customer satisfaction by providing better services and user experiences. · Expand the number of clients and customers you draw in, create more leads for the business and strengthen the brand awareness. · Enhancing user experience and service to increase customer satisfaction. · The website aims to have the trending functionality like a responsive windows, recommendations and automation. 3.2 Assumptions, Dependencies and Constraints 3.2.1 Assumptions · · The project's costs will remain constant with the initial anticipated costs. · The project will be carried out using agile methodology. · Change management should be implemented in case of any changes in environment. · All the participants will equally work on the skills for the development of the website. · Meetings will be regulated on the weekly basis and all the members should be present. · There will be internal trainings for the project to reduce the training costs. 3.2.2 Dependencies · The final report will be prepared once when all the participants submit their work. · The end users must have good understanding of the product. · The website designing task will be categorized among the team in the meeting only. · The design of the website will begin once all the stakeholders approve it. · The developers will start working on the website once the design is finalized. 3.2.3 Constraints · If the project scope leads to scope creep, then allocated time and resources may not be sufficient to develop the promised quality. · If we face any delay in the completion of any participants’ task, the project timeline will require to be adjusted accordingly. · For the update on any urgent issues the team will have to organize meetings in short notice and absence of any member will disturb the flow of information. 3.3.1 Analysts Perspective · The analyst will keep record of internal and external business requirements and maintain communication flow throughout the project. · Monitor and document all the meetings held. · Recommend ideas on improvement of the website and coordinate with the team for effective strategies. 3.3.2 Project Management Perspective With the application of agile methodology, at each phase of the project the task given will be completed leaning towards the final product. The regular feedbacks and ideas will be stored and implemented faster. 3.3 Monitor and control Mechanism Control tool framework Actions Outcomes Personnel Behavioural factors like delegation of tasks are done accurately and effectively. Results accountability in the planned budget and given time for the project. Internal trainings will be provided as the new updates come along in the process. Accountability for the tasks given to the team. Effective communication among the team members through WhatsApp, Zoom for clear understanding of the end result. Must have direct supervision on every single stage of web design to the development. Encouragement of peer control through the work group and shared goals. Technical Process 4.1 Methods, Tools and Techniques The tools that this project will use to develop and deploy the website: · Back-end operations: TBD · Server: TBD · Host: TBD · Front-end operations: Blazer will be used as a tool for front-end development. Prototypes are designed using a FIGMA. Database: TBD · Web framework- For the responsive websites we will be using bootstrap as our front-end framework. · Programming language- Javascript/php · DNS hosting-TBD Deployment Methods: Cloud deployment method has been used which means adding users, instances, and upgrading is easier also the initial cost is pretty low. Testing: The software will be tested regularly which enhances a better user experience, customer engagement and conversion rate. Different testing will be conducted like: · Functional testing · Security testing · Usability testing · Database testing 4.2 Software Documentation Sportify’s software documentation will be done using Document360 tool which is a powerful tool for documenting a software documentation. The documentation will include guide for the installation of the system, data dictionary, and UI documentation 4.3 Project Support Functions All the participating members will be present in all the weekly meetings if absent in any circumstance, then they should be updated right away by the leader about the changes and progress of the project. So that the absentee will have the sufficient information in the next meeting. Likewise, everyone should provide all the past records of ideas and assets that are necessary. They should equally respect and appreciate each other’s work when their ideas stand out. Also, the leader should provide guidance and supervision if any member of the team is having hard time completing any task. 4.4 Work Elements, Schedule Work Component Timeline for Completion Gathering Ideas 4 th week Defining Scopes 8 nd week Wireframe creation 12th week Front end development 16th week Back end development 24th week onwards - Testing 25th week Website Launch 30th week Tasks Duration Brainstorming ideas from the team 3rd week Defining the project scope 6th week Framework of the website 10th week Development of front-end design 14th week Development of back end of the website 20th week Testing the functionality 22nd week Launching website 24th week GANTT CHART 5. Overall Description 5.1 Product Perspective The website, Sportify, as the name suggests, is developed to sell sports equipements, gears, sportswears, merchandise, and many more related to sports. There are not many companies who sell all these products in one place. Customers need to go to different stores to buy different products. Keeping that in mind, Sportify, with a vast collection of products, focuses on selling different sports-related product at a single place. Similarly, all the big commercial sports equipment and aparel chain charge the customer high price for the quality just not worth it. So, the main focus of the company is to sell the customers high quality products with the most affordable price ever. 5.2 User Classes and Characteristics Since, Sportify is not a third-party selling and buying company, there will be only three parties involved: customer and admin. User Class Characteristics Customer Can create an account for the website. Can search products in the website. Can add products in their shopping list and buy if desired. Can exchange or cancel their order with a valid reason. Can make a payment through multiple payment options. Admin Can log into the website with additional access. Can look into the customer’s database and make changes if requested. Can add products to the inventory or remove it. Can add new functionality or features on the website. Can monitor network activities. 5.4 Operating Environment Sportify is a web-based application which means any devices with internet access and a browser can get access to the website. All IOS android, windows, linux devices can use the website. Since, this is the first phase, Sportify will just have a website but there are plans to develop an application software in near future. 5.5 Design Constraints There are some design constraiants that our team is facing while working on this project. The main constraint is manpower. There are not enough members in the team for a project like this. The other