LO3: create project

The iterations.
Iteration 1
For the first iteration I will be making the aesthetics and basic frame for the website which I will then submit for my stakeholders for review. This iteration follows the requirement of my client, the requirement it follows the criteria that the project has to look like it is a website and act like one as well. The end of this sprint will be for the 20th of December.
Iteration 2
For the second iteration I will be making the functionality of the pages such as the create and store as well as the design for the dossier table and the make page. This iteration follows the requirement of my client this requirement is that the data of the user must be secure and allow access to the dossiers created by the specific user. The end of this sprint will be 25th of February.
Iteration 3
For the third iteration I will be making the log in which will store the files for my project. This iteration follows the requirement of my client the requirement this follows is that the project must save and store the dossiers so that they can be accessed from any computer. The end of this sprint will be 19th of March.
Iteration 4
For the fourth iteration I will be going to go over the functionality and the design of the website as well as any contingency time that is needed. This iteration follows the requirement of my client the requirement this follows is that the project must work and be easy to navigate and use. The end of this sprint will be 30th of March.

Iteration 1
To make the home page I have made the other views for the other pages. After which I linked each page to the navbar. After I linked the pages I linked each page with buttons on the actual home page as to allow the end-user to easily navigate the website.

After I linked the pages I linked each page with buttons on the actual home page as to allow the end-user to easily navigate the website.

After I have linked pages to the buttons and the navbar I worked on the aesthetics of the page as my stakeholders want to have a visually simple and calm design. To design the aesthetics of the website I used the ideal colour scheme which was given by my stakeholder, which is to be both calming and energetic while being easy to look at, for this I have chosen to use chartreuse and teal. Chartreuse is an energetic colour as it is a light green which stands out. Teal is a colour often perceived as calm and relaxing as it is a deep greenish blue which reflects tranquillity and elegance.
I have also done the same for the about and contact page which will act as the basic frame for the website.
The about page.
The contact pages.

After I had created the basic shell of the project I showed my stakeholder. My stakeholder responded positively to the design of the project so far and said that he liked the colour scheme and basic design layout which was how he wanted it to look as the colour scheme makes it more aesthetically appealing. My stakeholder was pleased with how simple it was to use and how it was to navigate which is what he wanted as the people this is for have a varying amount of technological understanding, so the purpose was to make it easy to use for all types of people. I had my stakeholder use the product frame. My stakeholder said that the style was simplistic and easy to understand.

Iteration 2
I have made the design of the log in page. This is based off of the design of the home page which received positive feedback from my stakeholder. I have done this to create branding and to follow my stakeholder’s requirements for the colour scheme. The page doesn’t have full functionality at this stage, but the user can’t use the log in button without entering something in both the username and the password fields of the web page.
These are screenshot of what happens when either one of the fields is left blank.
 


The jumbotron class is the border of the fields. I have had my stakeholder review the product based on his requirements and received positive feedback from my stakeholder.

Iteration 3
I have made the deign and functionality of the dossier pages. This includes the dossier table, the make page, the edit page, the details page and the delete page.
This is the dossier table page. The fist image shows the table with one dossier. The second shows the outcome of saving a created dossier. This follows my clients design ideas as it uses colour psychology to influence the user’s moods and make them feel relaxed. The design also means that the page is simple and easy to navigate and understand.





The next page is the create page. This page is where data is input and saved to the dossier table. This follows my clients design ideas as it uses colour psychology to influence the user’s moods and make them feel relaxed. The design also means that the page is simple and easy to navigate and understand.







This page is the details page which is where the contents of the dossier are shown and are not editable. This follows my clients design ideas as it uses colour psychology to influence the user’s moods and make them feel relaxed. The design also means that the page is simple and easy to navigate and understand.





This is the delete page which shows the contents of a dossier to confirm that you want to delete the dossier. This follows my clients design ideas as it uses colour psychology to influence the user’s moods and make them feel relaxed. The design also means that the page is simple and easy to navigate and understand.






This is the edit page which is where data of a dossier is edited. This follows my clients design ideas as it uses colour psychology to influence the user’s moods and make them feel relaxed. The design also means that the page is simple and easy to navigate and understand.







To make these pages I used controller and a model.
This is the dossier model. The model created a database file which has a table containing the fields listed below. The DossierDBContext part of the model states that it is to be made a database.



This is the controller. This controller links all of the pages based off of the model together and controls how they are used and accessed.







Comments

Popular posts from this blog

LO4:Conduct testing

LO3:Create a graphical user interface