Standard Operating Procedure

As soon as the project is inputted on the project management software (PHP collab) this will be assign to a group of production member with their corresponding task. Designer which will be assigned for the look and feel of the website, Programmer for codding the website functionality and content, QA for checking of website vulnerabilities and bugs / error. Each project will be handle by the project coordinator and their corresponding consultant.

Below are the list of phases and their corresponding standard operating procedure.

Planning

1. All materials used on the design and development of the project must be provided by the client. In case that the client can’t provide images and write ups for their website, the developer / designer will be using stock photos and dummy text for temporary website content. If the client choose to use the temporary stock photo for their website, there will be a corresponding charge for it especially if it’s a license photo from the internet.
   
   Below are list of supported file extension for the materials.
   
   • Photos – jpg, png, gif, psd
   • Write-up – doc, docx, pdf, xls, xlsx, ppt, pptx
   • Template – psd
   • Flash – fla, swf

Design

1. Answered design questionnaire and 90% materials (company logo, write ups, template, preferred color for the website, and other images) must be provided before the project will be schedule for design.
2. If the client prefer a design from their end, they have to submit the source file of the said design on either in psd or in html. On the other hand, the designer should produce below deliverables.
   
   • Home page design – raw file (psd format)
   • Subpage design – raw file (psd format)
   • HTML pages – both homepage and sub page

Production

1. For a project to be schedule in programming the design signoff must be signed by the client and the materials must be 100% completed. Each project must be turnover by the project coordinator or web consultant to the developer especially if there’s a special request or instruction provided by the client.
2. Developer should produce the full functional project based on its scope. Once the programmer is done with the development the given project will undergo to a testing.

Sign-off

1. A sign off form must be signed by the client to prove that the project is approved and ready for uploading. For project uploading, we still have to wait for clients go signal to upload their website because there are scenarios that the client sign off the project but they don’t want to put it on live for some reason.

Scanning Before Uploading

All WSI Projects will undergo Accunetix Vulnerability Scanning prior uploading to live. This is part of the Web development phase.

1. After the Programming phase, the project is subject for QA/Testing using Accunetix Vulnerability Scan to scrutinize security holes brought by faulty programming.
2. The Production/project Supervisor shall create a JO request under Web development – Vulnerability Scan.
3. Said JO request shall be forwarded to our QA Specialist thru the assigned Sales Admin.
4. Accunetix Scan report shall be analysed by the QA Specialist (Lory) together with the SRM Engineer (Jerico) and Project Supervisor (Olivet). If found clean or free from bugs, the QA Specialist shall reply to the Job Order discussion with ‘’QA PASSED”. If found vulnerable, the QA Specialist shall reply to the Job Order discussion with “QA FAILED”. The website will be subject for debugging and/or security patch.

Note: The website project can still be presented to the client even if it’s under Vulnerability scanning.