full
border
#666666
http://dweblab.co/wp-content/themes/smartbox/
http://dweblab.co/
#C1272D
style2

How We Work

Planning

The planning stage is arguably the most important, because what’s decided and mapped here sets the stage for the entire project. This is also the stage that requires client interaction and the accompanying attention to detail.

 

Website-planning-300x247

 

  • Requirements Analysis

    In this stage need to know client’s goals, target audience, detailed feature requests as much relevant information.

  • Project Charter

    The project charter (or equivalent document) sums up the information that has been gathered and agreed upon Requirements Analysis. These documents are typically concise and not overly technical, and they serve as a reference throughout the project.

  • Site map

    A site map guides end users who are lost in the structure or need to find a piece of information quickly. Rather than simply listing pages, including links and a hierarchy of page organization is good practice.

  • Contract

    This is a crucial element of the documentation and should include – payment terms, project closure clauses, project termination clauses, project copyright ownership of intellectual property, project timelines and milestones.

  • Access

    All necessary access have to confirm in this stage. The access information may include – FTP access information, control panel access information, database configuration, platform and/or framework and/or CMS information.

  • Content

    Beyond determining any third-party media needs, identify where we may need to hire sub-contractors and/or where we may need to purchase any premium theme / plugin / script / graphic / photo. We will add all of these to the project’s budget, charging the client where necessary.


Design

The design stage typically involves moving the information outlined in the planning stage further into reality. The main deliverable are a documented site structure and, more importantly, a visual representation. Upon completion of the design phase, the website should more or less have taken shape, but for the absence of the content and special features.

IMAGE

  • Wireframe

    This is where the visual layout of the website begins to take shape. Using information gathered from the client in the planning phase, begin designing the layout using a wire-frame. Pencil and paper are surprisingly helpful during this phase, although many tools are online to aid as well.

  • Mock-up

    Designing mock-ups in Photoshop allows for relatively easy modification, it keeps the design elements organized in layers, and it primes you for slicing and coding when the time later on.

  • Review and Approval cycle

    A cycle of reviewing, tweaking and approving the mock-ups often takes place until (ideally) both client and contractor are satisfied with the design. This is the easiest time to make changes, not after the design has been coded.

  • Slice and Code

    It’s coding time. Slice the final Photoshop mock-up, and write the HTML and CSS code for the basic design. Interactive elements and jQuery come later: for now, just get the visuals together on screen, and be sure to validate all of the code before moving on.


Development

Development involves the bulk of the programming work, as well as loading content (whether by the client or a third party). We always keep our code organized and well commented and refer constantly to the planning details as the full website takes shape. We take strategic approach and avoid future hassles by constantly testing as we go.

IMAGE

  • Build Development Framework

    This is when unique requirements might force us to diverge from the process. If we using PHP framework ( Codeigniter, Laravel ) or a CMS, now is the time to implement it and get the basic engine up and running. Doing this early ensures that the server can handle the installation and set-up smoothly.

  • Code Templates

    A website or web application usually has several pages (e.g. home, general content, blog post, form) that can be based on templates. We create our own templates for this purpose.

  • Develop and Test Features and Interactivity

    Here’s where the fancy elements come into play. We like to take care of this before adding the static content because the website now provides a relatively clean and uncluttered work space.

  • Fill with Content

    Time for the boring part: loading all of the content provided by the client or writer. Although mundane, we don’t misstep here, because even the simplest of pages demand tight typography and careful attention to detail.

  • Test and Debug

    This is a good time for a full website review. We walk through every single page we have created—everything from the home page to the submission confirmation page — and make sure everything is in working order and that we haven’t missed anything visually or functionally.


Launch

The purpose of the launch phase is to prepare the web site or application for public viewing. This requires deep testing of interactivity and features and, most of all, a consideration of the user experience. An important early step in this phase is to move the website, if need be, to its permanent Web server. Testing in the production environment is important because different servers can have different features and unexpected behavior (e.g. different database host addresses).

IMAGE

  • Transfer to Live Server

    This could mean transferring to a live Web server (although hopefully we have been testing in the production environment), “un-hiding” the website or removing the “Under construction” page. My last-minute review of the live website happens now. The client will know about this stage and we will be more sincere in this stage if the web site or application is already popular.

  • Final Testing

    We will run the website through the final diagnostics using the available tools: code validators, broken-link checkers, website health checks, spell-checker and the like. Wewant to find any mistakes myself rather than hearing complaints from the client or an end-user.


Post Launch

Business re-enters the picture at this point as we take care of all the little tasks related to closing the project. Packaging source files, providing instructions for use and any required training occurs at this time. We always leave the client as succinctly informed as possible and try to predict any questions they may have. We don’t leave the project with a closed door; maintain communication that I’m  available for future maintenance and We are committed to ongoing support. If maintenance charges haven’t already been shared, then we establish them now.

IMAGE

  • Hand off to Client

    We are always try ensure the client is satisfied with the product and that all contractual obligations have been met (refer to the project charter). A closed project should leave both me and the client satisfied, with no burned bridges.

  • Documentation and Source

    We always provide documentation for the web site or application such as a soft-copy site map and details on the framework and languages used. This will prevent any surprises for the client later on and it will also be useful should they ever work with another Web Developer.

  • Project Close

    Get the client to sign off on the last checks, we provide our contact information for support and officially close the project. Maintain a relationship with the client, though; checking in a month down the road to make sure everything is going smoothly is often appreciated.

Planning

The planning stage is arguably the most important, because what’s decided and mapped here sets the stage for the entire project. This is also the stage that requires client interaction and the accompanying attention to detail.

 

Website-planning-300x247

 

  • Requirements Analysis

    In this stage need to know client’s goals, target audience, detailed feature requests as much relevant information.

  • Project Charter

    The project charter (or equivalent document) sums up the information that has been gathered and agreed upon Requirements Analysis. These documents are typically concise and not overly technical, and they serve as a reference throughout the project.

  • Site map

    A site map guides end users who are lost in the structure or need to find a piece of information quickly. Rather than simply listing pages, including links and a hierarchy of page organization is good practice.

  • Contract

    This is a crucial element of the documentation and should include – payment terms, project closure clauses, project termination clauses, project copyright ownership of intellectual property, project timelines and milestones.

  • Access

    All necessary access have to confirm in this stage. The access information may include – FTP access information, control panel access information, database configuration, platform and/or framework and/or CMS information.

  • Content

    Beyond determining any third-party media needs, identify where we may need to hire sub-contractors and/or where we may need to purchase any premium theme / plugin / script / graphic / photo. We will add all of these to the project’s budget, charging the client where necessary.

Design

The design stage typically involves moving the information outlined in the planning stage further into reality. The main deliverable are a documented site structure and, more importantly, a visual representation. Upon completion of the design phase, the website should more or less have taken shape, but for the absence of the content and special features.

IMAGE

  • Wireframe

    This is where the visual layout of the website begins to take shape. Using information gathered from the client in the planning phase, begin designing the layout using a wire-frame. Pencil and paper are surprisingly helpful during this phase, although many tools are online to aid as well.

  • Mock-up

    Designing mock-ups in Photoshop allows for relatively easy modification, it keeps the design elements organized in layers, and it primes you for slicing and coding when the time later on.

  • Review and Approval cycle

    A cycle of reviewing, tweaking and approving the mock-ups often takes place until (ideally) both client and contractor are satisfied with the design. This is the easiest time to make changes, not after the design has been coded.

  • Slice and Code

    It’s coding time. Slice the final Photoshop mock-up, and write the HTML and CSS code for the basic design. Interactive elements and jQuery come later: for now, just get the visuals together on screen, and be sure to validate all of the code before moving on.

Development

Development involves the bulk of the programming work, as well as loading content (whether by the client or a third party). We always keep our code organized and well commented and refer constantly to the planning details as the full website takes shape. We take strategic approach and avoid future hassles by constantly testing as we go.

IMAGE

  • Build Development Framework

    This is when unique requirements might force us to diverge from the process. If we using PHP framework ( Codeigniter, Laravel ) or a CMS, now is the time to implement it and get the basic engine up and running. Doing this early ensures that the server can handle the installation and set-up smoothly.

  • Code Templates

    A website or web application usually has several pages (e.g. home, general content, blog post, form) that can be based on templates. We create our own templates for this purpose.

  • Develop and Test Features and Interactivity

    Here’s where the fancy elements come into play. We like to take care of this before adding the static content because the website now provides a relatively clean and uncluttered work space.

  • Fill with Content

    Time for the boring part: loading all of the content provided by the client or writer. Although mundane, we don’t misstep here, because even the simplest of pages demand tight typography and careful attention to detail.

  • Test and Debug

    This is a good time for a full website review. We walk through every single page we have created—everything from the home page to the submission confirmation page — and make sure everything is in working order and that we haven’t missed anything visually or functionally.

Launch

The purpose of the launch phase is to prepare the web site or application for public viewing. This requires deep testing of interactivity and features and, most of all, a consideration of the user experience. An important early step in this phase is to move the website, if need be, to its permanent Web server. Testing in the production environment is important because different servers can have different features and unexpected behavior (e.g. different database host addresses).

IMAGE

  • Transfer to Live Server

    This could mean transferring to a live Web server (although hopefully we have been testing in the production environment), “un-hiding” the website or removing the “Under construction” page. My last-minute review of the live website happens now. The client will know about this stage and we will be more sincere in this stage if the web site or application is already popular.

  • Final Testing

    We will run the website through the final diagnostics using the available tools: code validators, broken-link checkers, website health checks, spell-checker and the like. Wewant to find any mistakes myself rather than hearing complaints from the client or an end-user.

Post Launch

Business re-enters the picture at this point as we take care of all the little tasks related to closing the project. Packaging source files, providing instructions for use and any required training occurs at this time. We always leave the client as succinctly informed as possible and try to predict any questions they may have. We don’t leave the project with a closed door; maintain communication that I’m  available for future maintenance and We are committed to ongoing support. If maintenance charges haven’t already been shared, then we establish them now.

IMAGE

  • Hand off to Client

    We are always try ensure the client is satisfied with the product and that all contractual obligations have been met (refer to the project charter). A closed project should leave both me and the client satisfied, with no burned bridges.

  • Documentation and Source

    We always provide documentation for the web site or application such as a soft-copy site map and details on the framework and languages used. This will prevent any surprises for the client later on and it will also be useful should they ever work with another Web Developer.

  • Project Close

    Get the client to sign off on the last checks, we provide our contact information for support and officially close the project. Maintain a relationship with the client, though; checking in a month down the road to make sure everything is going smoothly is often appreciated.

paged
Loading posts...
link_magnifier
#6E787E
on
fadeInDown
loading
#6E787E
off