Yay! The Client Pitch is over and done with! I was really nervous about this, but it actually turned out good, not only for me but the whole team. The day before the presentations we had a meet up at NMIT to have some presentation rehearsals, we did 2 run throughs, they were a bit shaky and unorganized, but that was the point of our meet up, so we actually get the chance get feedback from the team members, things that we should keep doing and should try not to do, such as saying “Um” all the time. Then when it came to the day of presentations we had another rehearsal meeting in the morning to further practice our parts of the presentation, it came to our attention that the presentation should not be more than 10 minutes, and because of this 10 minute limit we had to make our presentation very brief, we had to cut lines out of our speaking notes, we all removed one slide each, just so we can hit around that 10 minute mark. Our original time was quite awhile as we had a lot to cover, unfortunately that was cut short due to the time limit, I would have to say that our presentation would’ve been very in-depth and long if we were given a longer time to presentation. But overall it all turned out well and everyone in the team was satisfied with the efforts put into this assessment.
The website is now finished, there has been a few changes since the last version I shared. We have decided to swap out the support link button with a community link button, we did this because we believe more people will be looking for a place to make discussion rather than trying to find support, as one of the guest presenters mentioned if support is located at the top of the site or needs to be used often it shows that the website has some problems which may not make a good impression for new customers.
We moved currency down to be in line with the search bar, we did this because we thought there was too much space at the top and it didn’t look very nice at all, also the search button for Go has been changed to have curved edges.
We added a purple box around the link buttons and cart link buttons to make this look more like a navigation bar, the cart bar still has the image and we put the cart image to slightly overlap the box to make it stick out to the customer and hopefully it makes them think that this is their cart. I think it looks great as it also adds a bit more colour to the website.
We added more pages and connected these pages with the buttons because we were certain of being able to present a working prototype for when it comes to the client pitch presentation.
Now we are working on our design aspect parts and preparing a slideshow using Google slides for our client pitch presentation.
The Game Store website now has the purple colour background added and I think it looks good. We discussed what we could do with the image banner taking up a majority of the home page, it is just too boring and basic to just only have one image to fill the image box and it also limits on the amount of featured games we can show on the home page without making the page longer in length so to fix this problem I have been asked to find out how to do an image slider on Axure. At first I managed to get a image slider working, but what I thought would be even better is if the user was able to control the image slider for them to view the featured and recommended items at their own pace, so I have added buttons to the slider for them to go back and forward. Below the featured and recommended slider there are more games available to view or even add to the cart, I have set some importance into this page where as you scroll down you will see 2 images of games with a brief description of what the game is about, these are smaller and take up less space compared to the image slider, then below that there is a set of 4 games with only images and no description that can be viewed or added to the cart, these are of less importance but still among the featured and recommend, this may be due to being older games and will be soon made way for newer titles.
On the website we have started to discuss background colour, first off we tried a light yellow, that didn’t suit, then we changed it to a light purple, light purple was our final decision, but I have yet to implement the colour as need to discuss how light the purple should be. As for layout I have placed a bar at the top of the page with two combo boxes, one for language and one for currency, I placed these at the of the page because it is convenient to the user to change their options straight away, the user will be able to change the language and/or currency to suit them. Then we have the search bar where users are able to do their own custom searches, it is in the header of the page also for convenience. Then we have our Navigation bar, we have listed as follows… Games, Top Sellers, New Releases, Specials and Support, we believe that these are the categories that most customers are going to look for when entering the website, also I added on the end a support link as well for those in need of help, having it placed in the navigation bar is convenient. We have cart link that will bring the user to the cart after adding any games to the cart, this is easily identified by the game shopping basket to its right side.
We discussed more about the logos, we eventually ended up with two developments which was the game store logo with text on top of the store building, we thought it looked great but the problem we faced with the logo was that it was too tall and did not fit well into the location we wanted it, then the next logo is the game store building with text to the right side of it, this logo fitted well into the location that we wanted it, so we made a decision on which one we will use which was the logo with the text to the right side. Now that we have a final logo we have implemented it into the website mock up, as shown below this is how the logo will be placed on the website.
We are almost ready to start our website design, we had some wireframes and logos created by Patrick, he presented us with a starting logo and we were all happy to use it and work off that, we discussed what is good and bad about the logo, we decided to remove and add some things, he showed us multiple versions of the logo. I was working on the conceptual layout to start off with on Axure as I am quickly learning how Axure works. I had to quickly research the other game websites such as Steam, Origin, Uplay, Battle.net, GOG.com to see how these companies are presenting their websites. I tried to get all of good things about these websites.
Since we’re targeting females for the use of this website, we had to consider what colours were going to use, we discussed and eventually we came to the decision that the website’s primary colour will be purple and secondary colour will be orange, as seen on the colour wheel these colours contrast quite well, we’ve tried many options ranging from dark purples and oranges to light purple and oranges, for text we are using a dark purple. The reason we have the orange in there also is that even though it is targeting a female audience, we also don’t want the male audience to stray away from the website too.
In this assessment we are now going to design a few pages for our website. I requested a student licence for website designing software called Axure which was recommended in one of the design presentations by a guest. Another recommendation I considered was Adobe Fire Works or Adobe Photoshop but Axure suited best as the software was made for website design.
We’re looking at our website design theme to have the primary colour as Purple, and secondary colours Orange and maybe a very light(almost white) yellow.
In class we looked into the different website design aspects, User Experience Design (UX), User Interface Design (UI), Web Design and Media Design. We created a google document and assigned ourselves to work on one of the aspects which we would suit us. Patrick is doing UX aspects, Brandon is doing Web Design aspects, Dean is doing Media Design aspects and I am doing UI aspects.
These are some of the following aspects…
User Experience Design (UX):
- Easy To Use
- SEO / Findability
- User Friendly
- Resource Usage
User Interface Design (UI):
- Navigation bar
- Color Scheme
- Mobile Support
- Multi Language Support
- Facebook/Twitter/Instagram feeds
On the 4th of May was our last class session for the Team Report for Assessment 2, all except Brandon were present at this meeting, he has missed out on two meetings in a row already, but we did receive a message from him saying he has been sick, so at least his absence was justified. Dean has gathered everything we have worked on and has put it into a report format. We went through the team report together and we were all happy with the report. Even though we were asked to produce around 3 pages for the report, fitting all of our work into 3 pages just was not possible even if it was to be stripped down to it’s minimum, overall we ended up with 18 pages…Hopefully the excessive amount of pages will not have an impact on our final team grade for this assessment.
This is my final reflection for Assessment 2.
During the holidays we were able to organize a team meeting, our meeting went for approximately an hour an half, the only person who was absent from this meeting was Brandon, we didn’t seem to be able to get contact with him for most of the holidays. In this meeting Dean and I worked on a Data Dictionary for our main entities, which are Buyer, Seller, Orders, and Game. A two page table was created in a google document, the table contains 5 columns, the columns listed are Entity/Attributes, DataType(Size), Nullable, IsPK (Primary Key), IsFK (Foreign Key). Patrick made some final touches to the competitors analysis. We discussed what else could be improved and we went over some of the work we currently have, we are all happy with what has been covered. Now we need to put this into a report.
Here is a small piece of our Data Dictionary table that we created during this meeting…
In class each team had to pick a life cycle model to research and present to the class, we were given options on how to present this life cycle model, as a team we decided to go for the video option.
We chose the Waterfall Model because it was basic, easy to understand and follow and it caters for smaller teams, which was great for our small team of 4, we discussed and decided to avoid the agile model as it would be too complicated and time consuming for such a small team, the agile model is more for larger teams and would not be efficient for our team. I did a bit of research and gathering and put together a Word document which I shared in our team Facebook group chat.
On a day where all 4 of us were not busy we decided to meet up, put our acting skills on and film the video for our Waterfall presentation, we wanted to make the video entertaining and funny while also being educational for viewers. The recording and editing took around an hour.
A Google Document of the Waterfall Model slideshow can be viewed by clicking here!
This is our team’s presentation video on the Waterfall Model…
In our 2nd session we were all assigned parts to contribute to this assessment,
I was responsible for doing a conceptual model, which is shown in the image slideshow below. The conceptual model is less complex compared to the logical model, it only contains the entity names and relationships. Even though it has turned out that the conceptual model does not give any extra marks I believe it is good practice to do a conceptual model before going onto a logical model.
Dean was responsible for doing the Stakeholder Analysis, image shown in slideshow below. In the Stakeholder Analysis there is a matrix which has 4 sections, Keep Satisfied, Manage Closely, Monitor, Keep Informed, this matrix is identifying individuals or groups and they are placed into the most appropriate section according to their impact on the action and the impact the action will have on them.
Brandon was responsible for doing a Logical Model, image shown in slideshow below. The logical model is more complex than the conceptual model, it is more in-depth with the details, the logical model contains entity names, entity relationships, attributes, primary keys and foreign keys. This will help us understand the details of our data.
Patrick was responsible for doing Client Personas, there is no diagram for this. The client personas is about the target market, it looks into their behaviours such as, interests, pain points and needs etc, and that will give us a better understanding on what we can do to help them.