We are a Web Design & Development company in Rajshahi, Bangladesh. Since 2014, we have been serving across the globe. We offer web and graphic design, hosting and IT service, online marketing and business process outsourcing. Clients satisfaction is our top most priority and commitment. We strive to be dependable and efficient. The key element of our success is keeping clients happy with quality of work and professional service delivery. As a trusted companion to your journey, BR IT Solutions, ensure that our innovative, effective and easy solutions exceeds your current and future needs.
Our Working Process
Web Design & Development process is a documented outline of the steps needed to be taken from start to finish in order to complete a typical Web design & development project. To outline the whole development process, we create a website development timeline, adding tasks and establishing milestones for our project. It is the best way to track our project implementation to make sure we keep up with the deadline.
There are numerous steps in the web site design and development process. From gathering initial information, to the creation of your web site, and finally to maintenance to keep your web site up to date and current.
1. Information Gathering or Requirements Discussion
The first step in designing a successful web site is to gather information. This first step is actually the most important one, as it involves a solid understanding of the company it is created for. It involves a good understanding of company – what company business goals and dreams are, and how the web can be utilized to help company achieve those goals.
It is important that our web designer start off by asking a lot of questions to help them understand clients business and client’s needs in a web site.
We asked to client some important issues for create website:
What is the purpose of the site? Do you want to provide information, promote a service, sell a product?
What do you hope to accomplish by building this web site & what is your goals?
- Target Audience
Is there a specific group of people that will help you reach your goals? It is helpful to picture the ideal person you want to visit your web site. Consider their age, sex or interests – this will later help determine the best design style for your site.
What kind of information will the target audience be looking for on your site? Are they looking for specific information, a particular product or service, online ordering?
2. Assign Project
When we completed discussion with clients then we select a designer who will completed this project successfully by the clients requirements & after then we assign this project to him.
Now this step our designer plan using the information gathered from step one, it is time to put together a plan for clients web site. This is the point where a site map is developed. During the planning step, our web designer will also help to decide what technologies should be implemented. Elements such as what CMS (content management system) such as WordPress to incorporate, will any contact forms be needed, etc. are discussed when planning clients web site.
This includes client goals, target audience, detailed feature requests and as much relevant information as we can possibly gather. Even if the designer carefully planned clients website.
- Project charter
The project charter (or equivalent document) sums up the information that has been gathered and agreed upon in the previous point. 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.
- Contracts that define roles, copyright and financial points
This is a crucial element of the documentation and should include payment terms, project closure clauses, termination clauses, copyright ownership and timelines. Our designer very careful to cover with this document, but be concise and efficient.
- Gain access to servers and build folder structure
Typical information to obtain and validate includes FTP host, username and password; control panel log-in information; database configuration; and any languages or frameworks currently installed.
- Determine required resources (stock photography, fonts, etc.)
Beyond determining any third-party media needs, identify where we may need to hire sub-contractors and any additional requirements. Add all of these to the project’s budget, charging the client where necessary.
3. Site Layout
Now this step our designer create site layout by two parts Design & Development. This two parts described below
The design stage typically involves moving the information outlined in the planning stage further into reality. The main deliverables are a documented site structure and, more importantly, a visual representation. Upon completion of the design step, the website should more or less have taken shape, but for the absence of the content and special features.
- Wireframe and design elements planning
This is where the visual layout of the website begins to take shape. Using information gathered from the client in the planning step, begin designing the layout using a wireframe. Pencil and paper are surprisingly helpful during this step, although many tools are online to aid as well.
- Mock-ups based on requirements analysis
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 valid XHTML/CSS
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 involves the bulk of the programming work, as well as loading content (whether by our team or the client’s). Keep code organized and commented, and refer constantly to the planning details as the full website takes shape. Take a strategic approach, and avoid future hassles by constantly testing as you go.
- Build development framework.
This is when unique requirements might force you to diverge from the process. If you’re using Ruby on Rails, an ASP/PHP framework or a content management systems, 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 for each page type.
A website usually has several pages (e.g. home, general content, blog post, form) that can be based on templates. Creating our own templates for this purpose is good practice.
- Develop and test special 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 workspace. Our developers like to get forms and validation up and running at this stage as well.
- Fill with content.
Time for the filling with content: 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 we careful attention to detail.
4. Quality Assurance (QA)
This is a good time for a full website review. Here our experienced quality controller checked everything using our file manager as a guide, walk through every single page we’ve created—everything from the home page to the submission confirmation page—and we make sure everything is in working order and we haven’t missed anything visually or functionally.
5. Approved by Authority
Now this step our designer will show the demo website our authority or departmental head & he take approved from our authority or departmental head.
6. Web Site Shown
Now this step our designer will show the demo website to our client. Then client checked everything in his/her website is ok or not or any changes.
7. Requirement Changes or Revisions
If anything changes from client side then this step our designer will completed changes & finally our designer will prepare this web site for live/public.
8. Go Live
The purpose of the launch step is to prepare the website for public viewing. This requires final polishing of design elements, deep testing of interactivity and features and, most of all, a consideration of the user experience. An important early step in this step 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.
Particularly if we’re not scrambling to meet the deadline, polishing a basically completed design can make a big difference. Here, we can identify parts of the website that could be improved in small ways. After all, we want to be as proud of this website as the client is.
- Transfer to live server
This could mean transferring to a live Web server, unhiding the website or removing the Under construction page. our last-minute review of the live website happens now. Be sure the client knows about this stage, and be sensitive to timing if the website is already popular.
Run the website through the final diagnostics using the available tools: code validators, broken-link checkers, website health checks, spell-checker and the like. We want to find any mistakes ourself rather than hearing complaints from the client or an end-user.
- Final cross-browser check (IE, Firefox, Chrome, Safari, Opera, iPhone, BlackBerry)
We don’t forget to check the website in multiple browsers one last time. Just because code is valid, doesn’t mean it will sparkle with a crisp layout in IE 6.
9. Post-Lunch, Training, Hand Over & receive Feedback
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. 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; communicate that we’re available for future maintenance and are committed to ongoing support. If maintenance charges haven’t already been shared, establish them now.
- Hand off to client
Be sure 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 we and the client satisfied, with no burned bridges.
- Provide documentation and source files
Provide documentation for the website, 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, final documentation
Get the client to sign off on the last checks, 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.
As stated, this is merely a sample process. Our version will be modified according to our client base and style of designing. Processes can also differ based on the nature of the product; for example, e-commerce websites, Web applications and digital marketing all have unique requirements.