E-Commerce Websites of the TechAvenue - Coursework Example

Website development like any other project requires research skills. The methodology employed is also critical to the successful completion of the project. Ensuring that the project is defined and that it meets the customer requirements are critical aspects of that success. The structure and overall layout of the website was prepared and the different steps that were necessary to achieve the goals of the project in an efficient and effective manner were taken. A visual design of the two websites was done in order to simplify the development process. The result was two websites with the main aim of generating revenue from different products and services. Attempts were made to integrate both websites but time and resource constraints did not allow that to take place. The sites were tested but the launch has been delayed until they have been fully completion. 1.0 Introduction The purpose of this report is to partially fulfill course requirements for the BSc Computing degree. The requirement of the project is the development of a reliable and user-friendly website that would enable users to carry out certain tasks in an efficient and effective manner. Issa and Turk (2012) indicate that the essential principles necessary for the development of an effective website for e-Commerce are usability and human computer interaction. The purpose of TechAvenue.com is to sell technology products including tablets, phones, computers and MP3 players. The booking site allows users to make hotel reservations for specific hotels online. My initial intention was to investigate cloud computing risks and related security concerns. However, due to certain challenges the decision was made to develop an E-Commerce Website, TechAvenue.com along with a booking website. A computer lab was required to facilitate the task associated with my original intentions. None was available at the time and so the decision was made to develop the E-Commerce site. Attempts were made to link the booking website to the e-commerce site but unfortunately that did not materialize. 2.0 Research and Skills The development of a website requires research relating to both software and hardware requirements and functionality. Without hardware there would be nothing to facilitate the functionality of the software. Hardware includes computers, and storage device. The software is the program that makes the computer work. It provides instructions on how to perform various tasks. It also determines the user friendliness of the site. In developing a usable website, a developer needs to have an understanding of the users and also ensure that the website is able to appeal to a diverse user base. People differ across regions and across country borders and their requirements are influenced by their culture (Smith et al 2004). A usable website has certain characteristics that facilitate the satisfaction of users and it also has the ability to obtain their satisfaction in the competitive market place for online sales (Issa and Turk 2012). Usability is a critical aspect of TechAvenue.com’s image and it has the ability to influence buying behavior in the same way that a brick and mortar business can (Flavian et al 2006). Poor usability means that a site is difficult to navigate, resulting in frustration and loss of customers to other competitors (Nathan and Yeow 2009; Nicolson et al 2011). Adobe Photoshop is a great tool for preparing graphics and so it was used to create the images on the website. It is good for editing, organizing and publishing images and is described as the ultimate solution for advanced digital imaging (Adobe.com). Both websites were built using Model View Controller (MVC) framework code igniter and bootstrap for the front-end framework. Models represent the data structures. The Model files have the responsibility of obtaining, modification, insertion and removal of data from the database (Vuksanovic and Sudarevic 2011). This is usually done by interfacing with the database. Views contain page templates and output (Vuksanovic and Sudarevic 2011). View files have the responsibility of showing data to people who use the application. Controllers handle page requests and bind everything together. Controller files call, obtain data from the models, loads data and sends it to the views and the results to users (Vuksanovic and Sudarevic 2011). This process of separation with MVC leads to codes that are cleaner and easier to maintain. The MVC design pattern is useful for developing interactive software systems. Web applications are normally partitioned between the client and the server (Leff and Rayfield 2001). However, MVC’s facilitate a single address space and so the issue of partition does not arise. This is one of the major features of MVC. The program that is used to operate the website uses home controller to set the meta-tags including the title, description and keywords. It also loads the layouts, header and footer and then passes data to the home view – home.tpl. Home view facilitates the loading of the homepage. This is done by loading the header, the left column, right column, content at top and bottom and the footer. The skills that were used in developing the website included PHP Object Oriented Programming, HTML 5, CSS3, JavaScript, CodeIgniter Framework and MYSQL Database. PHP originally stands for personal home page. PHP Object Oriented Programming was regarded as the most popular of all dynamic languages in the mid to late 1990’s (Paulson 2007). It is “an open source, server-side, cross-platform, object-oriented scripting language” that is used to create dynamic web pages.(Paulson 2007, p. 14). Users of websites that use the language would insert the PHP code into the HTML code for a specific web page (Paulson 2007). HTML 5 was developed as a standard that would provide developers and users of the World Wide Web with enhanced functionality (Vaughan-Nichols 2010). It has certain features that will allow it to handle all the tasks that proprietary technologies perform. It also supports modern mobile technologies including location based services and blurs the line between desk top and online applications (Vaughan-Nichols 2010). HTML5 allows the integration of graphics into web pages, sound and video seamlessly. CSS3 means checkpoint selection strategies 3 (Chen and Yang 2006). It enables responsive designs for websites. It is the standard method for defining the presentational layer of web pages. CSS3 is used with HTML5. JavaScript is a scripting language (Vaughan-Nichols 2010). It is widely used for web programming (Richards et al 2010; Yu et al 2007). It takes an extreme position in terms of dynamism and so anything can be modified. JavaScript programs are used HTML documents and are also interpreted by major web browsers. It can also be used to animate content including pictures graphics, text, and continuous media (Cazenave et al ). Several programs including Sublime Text, Eclipse IDE for PHP, Xamp for local development, phpMyAdmin for the database, Terminal for ssh to the server, File Zilla for FTP transferring files to the servers. Xampp is an Apache distribution that contains the some of the most popular development technologies in one package (Dvorski 2007). They are light, small and portable. This makes them suitable for students using PHP and MySQL to test applications (Dvorski 2007). The light version contains Apache HTTP server, phpMyAdmin, OpenSSL, PHP, MySQL and SQLite 3.0 Methodology In developing a website a set of procedures need to be followed. This includes defining the project, setting up the structure of the website, preparing the visual designing, developing the website, testing and refining, and launching. Planning establishes the goals that the website should be able to achieve. 3.1 Project Definition Defining the project consisted of six steps. They are interviewing the client to determine the requirements; preparing a project brief; personas; initial tech specs; project timeline; and initial maintenance planning. (See Appendix 1 for details).The goal of any e-commerce site is to sell products and services. However, there has to be some benchmark for achieving success. This benchmark has to relate to user satisfaction and therefore to the ease with which the site can be navigated. Therefore, in defining the project consideration was given to the requirements for achieving that goal. Once the requirements were determined the project brief was prepared. 3.2 Site Structure Setting up the structure of the site is important as this is what will appeal to the users. (See Appendix 1 for details).The content or functionality outline, site diagram, page description diagrams and wireframes are part of the structure and needs to be determined in advance. 3.3 Visual Design The design provided information on how the website would fulfill the objectives set out in the plan. (See Appendix 1 for details). It included the specifications of the website and the overall form and structure of the website. The specifications addressed all the technological components required to make the website effective. Consideration was given to the need for ease and efficiency in the processing of user requests. Laudon and Laudon (2006) points out that in designing a system the ease and efficiency in the fulfillment of user requirements as it relates to time, financial technical and organisational constraints are critical in achieving superiority and by extension, a competitive edge. Adobe Photoshop was used to design the layout of the site and Moqups for the basic structure of the website. A flowchart was done to illustrate the component parts of the system and how they interrelate. This information was then used to develop the site. 3.4 Site Development In developing the site the technology specifications were confirmed and refined to ensure it met the customers’ requirements. (See Appendix 1 for details)The project timeline was is reviewed and adjusted to ensure that the project could be completed within the specific timeframe. Different aspects of the site were then built and the component parts integrated into one website. 3.5 Test and Refine Testing a website before making it available to the public is important. (See Appendix 1) This will help to ensure that most if not all the problems are sorted out before making it fully functional. Problems with a website can be a turnoff for users and could lead to loss of customers. The site should be tested and refined as needed before roll-out. This will ensure the quality of the product that the client receives. Quality assurance testing is part of the process that ensures that the client is satisfied. Issues need to be prioritized and the most important ones dealt with first. Correcting the problems as they are found and retesting the whole system to ensure that it works is the ultimate goal. 3.6 Launching the Website In launching the website there are certain matters that need to be considered. (See Appendix 1 for details)The production of a style guide will help the client in the future to make changes to the site and to correct any problems that may occur. The launching of the site is done once that is in place and the maintenance plan can be implemented. Adequate provisions should be made for this since unforeseen problems can arise. The launch of the two websites was delayed due to time and resource constraints until they can be integrated. 4.0 Project Management A project is a temporary endeavour that is carried out with the aim of creating something that is unique (Project Management Institute 2008). The activities in a project are connected together and they are performed in a particular sequence (Wysocki 2009). The aim is to complete the project within a specific time period whilst meeting the specifications within the limits of the budgeted resources. The development of the website can be described as a project and like all projects it went through a cycle. A standard project has four phases. They are initiation, planning, execution and closure. 4.1 Initiation Phase In the initiation phase the scope and aims of the project are defined. In fact, Schwalbe (2009) indicates that the process involves a definition of the scope which is the actual work that needs to be done. Additionally, for project management to be effective it has to go through some steps that are clearly defined. The aim of this project is to develop a website that users will be able to navigate easily. The scope and objectives of the project forms the basis for the planning stage. In the methodology a set of procedures were outlined. They are planning, designing, coding and testing. In the WBS they would be listed across the top and diagram and the activities required to accomplish them would be the work packages. Planning as mentioned would involve a number of steps including planning the finances and the time that it would require to complete the project. The fact that I am studying is an indication that time is limited and so there are time constraints. Financial resources are also limited and so ensuring that I did not have to rewrite any sections of the code or redesign any aspect of the project was important. 4.2 Planning Phase In the planning stage a list of the activities involved in the project is prepared and a work breakdown structure is developed from it. The work breakdown structure (WBS) is a hierarchical structure which shows all the deliverables at each level of the structure. Each descending level represents more detailed and manageable components of the work. The WBS organizes and defines the scope of the work. The details of the work to be done are shown at the lowest level of the WBS and are described as work packages (Project Management Institute 2008). It is at this stage that the financial plan is prepared. Although a detailed financial plan is not necessary some amount of financing was necessary to get the job done. Additionally, the activities identified had to be scheduled to ensure that the site was developed within the specified timeframe. A Gantt chart was used to schedule the activities. It is the standard for displaying project activities and their start and finish dates in a calendar format (Schwalbe 2009). Certain activities in the schedule cannot start until others are completed. The Gantt chart is shown in Appendix 3. The planning of the project stages was done in week 38 and 39. The online ethics from was completed n week 39 and the project was broken down into sections in week 40. The literature research was done between week 40 to week 41 and research into hardware and software requirements from the week end of week 41 to week 42. A network diagram is normally used to show which activities have to be completed before others can start. The longest path through the network diagram is called the critical path. The activities along that path cannot be rescheduled without affecting the timely completion of the project. 4.3 Execution In executing the project the structure of the site was determined and an outline drawn up. The design of how the site would look and operate was then prepared. The different components were tested to ensure functionality. The components were then integrated and further tests were done to ensure that the site could be easily navigated from one section or web page to the next. Several refinements were also carried out to ensure that the site performed efficiently and effectively. 4.4 Closure The website was then launched after the production of a style guide. Steps were also taken to put a maintenance plan in place for the continuous functioning of the site. There are still some issues that needs to be addressed and these are dealt with under project evaluation. 5.0 Project Evaluation In terms of usability the E-Commerce websites are not functioning at their full potential. However, there were no major problems, just additional resources and research to ensure the full functionality of the booking site and the integration of both sites. TechAvenue.com was easy to navigate as both images and words are used. When the pointer is pointed towards an icon the screen tip showing what the image represents appears below. The booking site has some functionality issues which can be addressed with time and money. Despite the success of the project there were some hiccups that can be resolved with further research. If I had more time I would have integrated the website with eBay and Amazon. These sites are the ultimate in e-Commerce websites. Integrating my website with them would drive traffic to the site as well as generate increased revenue. I would also offer my products on both sites and also advertise on the sites as well. Building a mobile app that mobile users could download is also another means by which the site could become popular. The number of hits would also drive advertisements to the site. Advertisements are a major revenue generator for some sites. I would also build an application programming interface (API) which would facilitate requests for JSON or XML. Additionally, I would integrate it with the booking site so that people who are doing hotel booking can access the site as well. This would bring indirect traffic that would not materialize without the integration of the sites. 6.0 Project Conclusion Project management can be a complex task requiring financial resources, human resources and time management. Planning is a critical aspect of this task and there are several facets for planning a project, all of which are integrated. They include the communication plan, the financial plan, the human resource plan and scheduling of tasks using Gantt charts. If these tasks are not taken care of the project will not be successful as they represent significant aspects of the planning process. Ensuring that projects are completed in a timely manner and that goals are achieved is critical to successful project completion. Certain aspects of the project were successful while other aspects did not achieve the intended goals. Tech.Avenue.com needs some improvement but nothing major as customers would be happy to use the site in order to source some of the products identified. The site has a lot of potential and it will definitely be successful. The images on the site are sharp and attractive to look at and so users will want to navigate to see if there are any items that they may want to purchase. Having a better price and quality compared to Amazon and eBay would certainly drive customers to it. The Booking site is very attractive and the layout is great. However, additional work s needed to bring it to the point where it is functioning effectively and efficiently. The sites should not be integrated until that is done. This will ensure that there are no major problems after integration. References Adobe. (2015). Adobe Photoshop CC. [Online] Available at http://www.adobe.com/products/photoshop.html Cazenave, F., Quint, V and Roisin, C. (2011). Timesheets.js: When SMIL Meets HTML5 and CSS3. DocEng 2011, 11th ACM Symposium on Document Engineering, Sep 2011, Mountain View, United States. 10 p. Dvorski, D.D. (2007). Installing, Configuring, and Developing with Xampp. Skills Canada – Ontario. [Online] Available at http://dalibor.dvorski.net/downloads/docs/installingconfiguringdevelopingwithxampp.pdf Flavian, C., Guinaliu, M and Gurrea, R. (2006). The Role Played by Perceived Usability, Satisfaction and Consumer Trust on Website Loyalty. Information and Management, 43, p. 1-14 Issa, T and Turk, A. (2012). Applying Usability and HCI Principles in Developing Marking Websites. International Journal of Computer Information Systems and Industrial Management Applications. 4, p. 76 - 82 Laudon, K.C and Laudon, J.P. (2006). Management Information Systems: Managing the Digital Firm. 10th ed. Upper Saddle River, NJ: Pearson Prentice Hall Lee, S and Koubek, R.J. (2010). The Effects of Usability and Web Design Attributes on User Preference for E-Commerce Web Sites. Computers in Industry. 61(4), p. 329-341 Leff, A and Rayfield, J.T (2001). Web-Application Development Using the Model/View/Controller Design Pattern. Enterprise Distributed Object Computing Conference, 2001. EDOC 01. Proceedings. Fifth IEEE International, Sept 4 to 7, p. 118-127 Nathan, R and Yeow, P. (2009). An Empirical Study of Factors Affecting the Perceived Usability of Websites for Student Internet Users. Univ Access Inf Soc. 8, p. 165 – 184 Nicolson, D., Knapp, P., Gardner, P and Raynor, D. (2011). Combining Concurrent and Sequential Methods to Examine the Usability and Readability of Websites with Information about Medicines. Journal of Mixed Methods Research. 51(1), p. 25 - 51 Paulson, L.D. (2007). Developers Shift to Dynamic Programming. Computer, p. 12 -15- http://www.itcj.edu.mx/tecnoticias/images/20070215/sistemas/guia.pdf Project Management Institute (2008). A Guide to the Project Management Body of Knowledge (PMBOK Guide). 4th ed. USA: Project Management Institute Richards, G., Lebresne, S., Burg, B and Vitek, J. (2010). An Analysis of the Dynamic Behavior of JavaScript Programs. https://www.cs.purdue.edu/sss/projects/dynjs/pldi275-richards.pdf Schwalbe, K. (2009). Information Technology Project Management. 6th ed. USA: Cengage Learning Smith, A., Dunckley, L., French, T., Minocha, S and Chang, Y. (2004). A Process Model for Developing Usable Cross-Cultural Websites. Interacting with Computers, 16, p. 63-91 Vaughan-Nichols, S. J. (2010). Will HTML 5 Restandardize the Web? Computer. April, p. 13 -15 http://u.cs.biu.ac.il/~ariel/download/mm664/resources/internet_web/html5.pdf Vuksanovic, I.P., Sudarevic, B. (2011). Use of Web Application Frameworks in the Development of Small Applications. MIPRO, 2011 Proceedings of the 34th International Convention, May 23-27,p. 458 - 462 khttp://www.sudarevic.com/wp-content/uploads/2011/05/mipro2011_paper.pdf Wysocki, R.K. (2009). Effective Project Management: Traditional, Agile, Extreme. 5th Edition. USA: Wiley Publishing Inc. Yu, D., Chander, A., Islam, N and Serikov, I. (2007). JavaScript Instrumentation for Browser Security. http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.89.183&rep=rep1&type=pdf Appendix 1 The Development Process Appendix 2 The Structure of the Website Appendix 3 Gantt Chart Published in: Read More