Unit 2 Quality Systems in IT Assignment

Introduction

Task 2: Be able to employ standard quality control documentation

2.1 Quality control document for each stage of the development of Management Information Systems for Jack & Jill PLC

Quality control will need to be involved at each stage of system development. An early detection of bugs often proves to be less costly in fixing and doesn’t affect the budget. Some of the most prominent quality control activities include the following:

• Definition and classification of bugs and their severity
• Inspection of project related documents and code
• Testing of the software
• Recording and logging of bugs
• Setting up quality control boundaries
• Performing boundary tests and corrective actions

Each activity in the quality control process require their own documentation to be created and reserved for ensuring proper planning, execution and control of the processes (Weinberg, 1991). ISO 9001:2008 specifically mentions the documents such as a Quality Policy, Quality Objectives, and a Quality Manual. However, several other documents can be prepared by the MIS project team at Jack & Jill Plc. for ensuring the quality of the system at each stage of the system development. These documents include:

Requirements Review Document: Once the requirements have been gathered by the MIS project team from business, a quality review of the SRS needs to be carried out. The template which can be followed for this purpose can be the following:

Reviewer:                                                                   Reviewer: Requirements Review Checklist Organization   Does the SRS follow the prescribed template?   Have the requirements been properly prioritized?   Have the requirements been properly cross-referenced? Completeness   Have the requirements been properly detailed?   Are all the users or system needs identified in the SRS?   Missing information identified?   Error conditions documented? Correctness   Duplication of requirements identified?   Is the language concise and understandable? Non-functional Specifications   Are all performance, security and safety considerations appropriately identified?   Quality attributes documented properly with acceptable adjustments?

Project Plan Review Documents: The project plan review checklist is to be used by the system owners, project managers and is intended to ascertain whether all the necessary standards have been following while preparing a project plan. A very elementary project plan review checklist is given below which can be used by the MIS development team:

Project Name: <<Name of Project>>                                    Program Project ID#: <<Project #>> Reviewer: _____________________                                   Date: ___________________

Content Project plan adheres to the prescribed template? Document management procedures being followed? Stakeholders appropriately identified? Scope, boundaries and assumptions are clearly mentioned? Work breakdown structure prepared? Key Milestones, tasks and resources have been identified? Milestones have been assigned a target date? Resources have been allocated to each task? Schedule buffer has been considered? Budget Estimates of project efforts and budget are included? Buffer for project cost has been considered? <<More sections can be added as and when required>>

Design Review Checklist: The template for the design review checklist is the following:

Project Name: <<Name of Project>>                                    Program Project ID#: <<Project #>> Reviewer: _____________________                                   Date: ___________________

Design methodology has been selected based on the finalized requirements? Software architecture has been identified? Input, output and other entities have been identified? A User interface approved by the business owner has been designed? A Data model has been identified and designed? Function design document has been created and reviewed? Physical data model has been designed? Appropriate Error handling mechanisms have been identified? The system design is approved along with the system architecture?

Code Review Checklist:

Following is the template for code review checklist:

Project Name: <<Name of Project>>                                    Program Project ID#: <<Project #>> Reviewer: _____________________                                   Date: ___________________

Does the code totally and appropriately comply with the design? Does the code adhere to any appropriate coding best practices? Is the code well-formatted, stable in style, and properly organized? Is there any untraceable code block or any unnecessary procedure written in the code? Does the code contain any discarded stubs? Is there a possibility to replace a code block by calling a library function or external component? Are there any repeated procedures which can be merged in a single class? Is memory management and garbage collection properly handled? Are the variables clearly defined and adhere to the established naming conventions? Is the code appropriately documented with proper commenting?

Test Documents:

Contact us

Get assignment help from full time dedicated experts of BTEC HND & HNC assignments.

Call us: +44 – 7497 786 317
Email: support@locusrags.com

Order Now!!

• Test Approach Document: A test approach document is created out of the SRS and project plan defining the overall approach while testing the software. This document needs to be reviewed by the product manager, Dev. Lead, Business contact, and other stakeholders before signing off.
• Test Plan: A test plan document is created based on the test approach document and is required to identify the features of software to be tested and procedures to be following while testing those features. Test plan also identifies the tools, resources, contact persons, risks, bug management steps etc.