cohesive paper

HWE Accessories Website: Contract Plan and System Testing Document

February 27, 2017

HWE Accessories Website: Contract Plan and System Testing Document

HWE Accessories Contract Plan

BSA/515r3 - HWE Website

Contract Plan

Initiating Office: HWE Accessories

Project Title: HWE Website

Requiring Activity: HWE Website Development

Estimated Value: $30,000

Contract Type: Time Specific Contract

Evaluation and selection process is used to determine the best responsive bid, as specified in the solicitation document. As per HWE accessories, assessment and selection process should be based on the following criteria:

The proposals should entail all the necessary and required accompanying information and documents
Technical evaluation should be conducted to determine the expertise or specialization of the contractor.
Financial evaluation of the bid should be performed to detail out the price of the contract.
The financial status of the contractor as well plays an important responsibility in determining their trustworthiness (Software Evaluation, (n.d.).

Contract management is the process of managing contracts from the point of creation, execution, and analysis with a goal of maximizing operational and financial gain at an organization while reducing financial risk. The following mechanism needs to be employed:

Quality Assurance Surveillance Plan. It manages contractor performance assessment by ensuring that systematic quality control methods are utilized to validate that the contractor's quality control efforts are timely, efficient, and are delivering the results specified in the contract or task order.
Management Plan. It’s an assessment tool for accessing the set goal and help in creating a realistic, detailed plan for meeting those goals.
Work Plan. It outlines the systematic procedure to be followed to achieve the set goals during the contract period (Tinnirello, 2000).

Vendor risk and relationship management. Contract agreement with an outside third party will subjects HWE accessories to risks of financial and reputational harm, such as from breach of contract, fraud, error, data loss, breach of confidentiality, and so on. The risks associated with vendor relationships for HWE accessoriesbasically lies on the data to be handled during the contract period. The following measure will be put into consideration during the process:

Confidential and non-disclosure agreement will be drafted and signed by both parties.
Security policies such as insurance will be employed to take care of any industrial risk (Gentle, 2002).

Software escrow. It is the depositing of software systems source code with a third party escrow agent. By arranging a software escrow agreement, you are taking responsibility for your business continuity and ensuring that the systems you rely on are always available.

Enterprise escrow. HWE accessories shall enter into a corporate escrow agreement with the contractor. The escrow covers multiple user software systems, usually 6 or more, as well as the arrangement, provides a cost-efficient solution to managing a software escrow portfolio.

Software licensing. It is a contract between the licensing party and the party purchasing the software product, establishing the purchaser's right to use the software. HWE shall retain the right to use and modify the software as well as hosting to their local servers.

System Testing Document:

Black box testing. It concentrates on internal construction of a program. This test will be carried out on the following:

The loop testing – loops are crucial measurement point in a program to get lead of thing such as infinite loops
Cyclomatic complexity – which will measure the logical complexity of the program
Data flow testing – select paths of the program based on the variable definition.
Graph matrix – shall be used for testing conditions

White box testing. It focuses on functional requirements of the software. It attempts to find errors in the following categories:

Missing or incorrect functions
Performance errors such as memory exhaustion, overheating, etc.
Data structures errors such as stack overflowing
Interfaces errors where two modules are unable to communicate or misbehave after integration (Crawford, 2014).

Functional testing. Determine whether the stated requirement are meet by the software product. It includes both functional requirements and non-functional requirements.
Environment. A setup of hardware and software for the testing teams to execute test cases. The website will be tested in its working environment and subjected to equivalent traffic as expected working traffic.
Security testing. It attempts to verify that protection mechanism built into the system works. The site will be subjected to penetration testing using various tools to reveal all vulnerabilities that might pose a security risk.
User Acceptance Testing. The software is acceptable to the users if they are to use it and also meet their functional requirements. It can;

Unit testing. Here the team shall test specific parts of the software for specific functions. It emphasizes on the local data structure, boundaries and interfaces among others (Singh, 2013).

References

Top of Form

Crawford, S. (2014). CompTIA CASP CAS-002: Black Box, White Box, and Gray Box Testing.

Gentle, M. (2002). The CRM project management handbook: Building realistic expectations and managing risk. London: Kogan Page.

Singh, Y. (2013). Software testing.

Software evaluation. (n.d.). Montreal: SDM.

Top of Form

Tinnirello, P. C. (2000). Project management. Boca Raton: Auerbach.

Bottom of Form