Blue Sky Project Design Proposal

Question: Describe about the Blue Sky Project Design Proposal. Answer: Project Background Project Overview The project is being developed for the company names Blue Sky in order to provide the organization with a marked web presence with the latest tools and technologies. The online store of the company will provide a number of services to the customers along with the real time access and improved integration as well. Project Objectives The basic objectives of the projects are as listed below: Ability to provide an online store to the customers with a complete product catalog and the real time access and integration To complete the project in the budget that has been agreed upon To complete the project as per the schedule that has been agreed upon Project Outputs The major outputs of the project will be the web application of the company for the desktop as well as mobile platform along with the syncing of the same with the database (Dot, 2016). Target Audience The project will be primarily designed for the customers of the Blue Sky to enable them to have an easy access to the products of the company. The same will also benefit the employees for better handling of the services (Muller, 2016). Success Criteria The success criteria of the project will be determined by its adherence to the project budget and schedule. The success of the end product that is the web application will be determined by with the help of Google Analytics and the factors such as site ranking, user traffic and many others. Project Requirements Functional Requirements Ability to allow the customer to register and login to the online portal with three user types as customer, suppliers and admin Ability to create a product catalog on the online portal with products available under product categories with information as product name, product image and product description Ability to provide customer feedback through the online portal Ability to contact the company for assistance and any query Ability to add the products to the cart of the wishlist to purchase them later Ability to sync the database with the front end to have correct inventory and order details Ability to cancel the order once they are placed (Malan Bredemeyer, 2016) Non-functional Requirements Usability: The online portal must be designed as per the requirements that have been specified Availability: The application must be made available to the users at all times irrespective of the location and time Recoverability: The application must quickly recover its services in case of the occurrence of an attack that is the downtime must be extremely low Scalability: The application must always be scalable in nature and must have the scope for the updates to be done as per the changing technology Maintainability: The application must be easy to maintain once it has been released for the customers to resolve the issues in a timely manner (Chung, 2016) Project Design Design Aims The primary aim of designing the web application for Blue Sky is to provide the customers with an online portal for easy accessibility and non-stop availability as well. The design aims include the principles as per the target audience of the web application. There will be a number of customers who will access the application and the design should be fit for people of all age groups. Another design aim that has been set for the project is to follow a responsive web design to allow the customers to access the application from any platform and feel connected with the application as well (Garzotto, 2016). Design Outline Navigation This is the primary factor that will be considered in the design of the project. The navigation that will be provided to the application will have easy navigation for every single page and screen in the application. The users will be allowed to move from one option to the other option in the application with ease. Layout The layout that will be followed in the application design will be kept simple. There will be four major sections for each of the page which will involve header section followed by the menu section with body section after it and the footer section at the bottom. Header, footer and menu will be kept consistent for every page and the body section comprising of the content will vary from page to page (Stanford, 2016). Content Content is the king for any web application and the same will be in the case of Blue Sky. For instance, the product catalog page will have the complete information of all the products listed and the contact us page would showcase the contact details. Colors and themes The theme that will be selected for the Blue Sky application will be as per the objectives and vision of the company. The colors will be kept simple and consistent across all the web pages and the readability of the text will be of prime importance. Website Evaluation The website will be evaluated and tested to make sure that there are no defects and bugs present in the same. A step by step process will be followed to accomplish the task and a test report will also be presented at the completion of the process. The testing activities will involve three major types of testing which are as listed below. Smoke/Sanity Testing This will be done as soon as a build will be received from the development team to make sure that all the necessary functionalities are present in the build and the build will then be formally accepted to carry put further testing procedures. There will be few test cases present in the test suite for this testing type. System Testing This is a type of testing that will be done extensively to test all the functionalities implemented in the system against the set of requirements that are provided to the team. The defect report will be developed after logging of the defects and the same will be sent to the Project Manager and other relevant project resources. Usability Testing This is the testing that will be specifically tested to determine the UI/UX aspects of the web site and the correctness of the same as per the requirements. A dedicated usability test team will be deployed to carry out this testing to make sure that there are no usability defects present in the web site. A set of questions will also be prepared in the form of questionnaire for the users to understand their expectations and requirements and the evaluation will be made on the basis of the response that will be received through the process. This testing will include three broad categories as exploration, assessment and comparison. These three methods will be used at three different times of the product development with exploratory method launched early in the stage of product development, assessment done in midway and comparison executed towards the end. The usability testing will also include the comparison between the user requirements and all the non-functional requirements and the adherence of the same with the final product that is supposed to be delivered to the customers (Churm, 2012). References Chung, L. (2016). Non-Functional Requirements. Retrieved 31 August 2016, from https://www.utdallas.edu/~chung/SYSM6309/NFR-18-4-on-1.pdf Churm, T. (2012). An Introduction To Website Usability Testing - Usability Geek. Usability Geek. Retrieved 31 August 2016, from https://usabilitygeek.com/an-introduction-to-website-usability-testing/ Dot,. (2016). Project Management Principles. Retrieved 31 August 2016, from https://www.dot.state.fl.us/officeofdesign/training/designexpo/2012/Presentations/MurphyShawn-Project%20Management%20Principles.pdf Garzotto, F. (2016). Industrial Acceptability of Web Design Methods. Retrieved 31 August 2016, from https://www0.cs.ucl.ac.uk/staff/v.perrone/publications/Industrial_acceptability_of_Web_Design_Methods_An%20empirical%20study_(JWE).pdf Malan, R. Bredemeyer, D. (2016). Functional Requirements and Use Cases. Retrieved 31 August 2016, from https://www.bredemeyer.com/pdf_files/functreq.pdf Muller, J. (2016). Project Charter. Retrieved 31 August 2016, from https://it.ucsf.edu/sites/it.ucsf.edu/files/enterprise_reporting_charter.pdf Stanford,. (2016). Website Redesign Proposal. Retrieved 31 August 2016, from https://web.stanford.edu/~eadolfo/cis-redesign/attachments/proposal-newsignature.pdf