NYSS Software Solutions

Bar-Coded Assessment System for Independent Learning

Iteration Assessment
Version 1.0

Author Saqib Abbas

Bar Coded Assessment System for Independent Leaning (BASIL) Iteration Assessment BASIL_Iteration_Assessment.docx

Version: 1.0 Date: 19/11/2010

Revision History
Date 19/11/2010 Version 1.0 Final Version Description Author Saqib Abbas

Confidential

<Company Name>, 2012

Page 2 of 6

Bar Coded Assessment System for Independent Leaning (BASIL) Iteration Assessment BASIL_Iteration_Assessment.docx

Version: 1.0 Date: 19/11/2010

Table of Contents
1. Introduction 1.1 1.2 1.3 1.4 1.5 2. 3. 4. 5. 6. 7. 8. Purpose Scope Definitions, Acronyms, and Abbreviations References Overview 4 4 4 4 4 4 4 4 5 5 6 6 6

Iteration Objectives Reached Adherence to Plan Use Cases and Scenarios Implemented Results Relative to Evaluation Criteria Test Results External Changes Occurred Rework Required

Confidential

<Company Name>, 2012

Page 3 of 6

Bar Coded Assessment System for Independent Leaning (BASIL) Iteration Assessment BASIL_Iteration_Assessment.docx

Version: 1.0 Date: 19/11/2010

Iteration Assessment
1.
1.1

Introduction
Purpose The purpose of Iteration Assessment is to assess and evaluate the iteration plan to see what has been achieved after the iteration is complete. It specifies the list of use-cases and various scenarios implemented during the iteration.

1.2

Scope This iteration assessment artifact assesses the iteration plan of the inception phase of BASIL project. This iteration assessment document will look into how far iteration plan objectives have been achieved. This document will give an insight into the progress of the project and will also throw light on what needs to be improved on in the next iteration/phase.

1.3

Definitions, Acronyms, and Abbreviations BASIL Bar-coded Assessment System for Independent Learning.

1.4

References Iteration Plan Risk Management & Risk List Software Development Plan Use-Case Model Survey

1.5

Overview The rest of this document describes the iteration plan objectives which have been met/not met. It also lists the use-cases and scenarios implemented, whether the iteration went according to the plan and if any external changes were introduced during this iteration. The results achieved against the evaluation criteria set in the iteration plan are also described later in this document.

2.

Iteration Objectives Reached

Most of the objectives which were set in iteration plan have been achieved. The main actors, use-cases, risk list and risk management, software development plan and requirements specification has been achieved in this iteration. More details about the results of this iteration are described in section 5 of this artifact.

3.

Adherence to Plan
The project has gone according to the plan during this iteration. The details of the plan for this iteration were set in Iteration Plan artifact and have been met as planned. Further details regarding what has been achieved during this iteration is described in later sections of this artifact.

Confidential

<Company Name>, 2012

Page 4 of 6

Bar Coded Assessment System for Independent Leaning (BASIL) Iteration Assessment BASIL_Iteration_Assessment.docx

Version: 1.0 Date: 19/11/2010

4.

Use Cases and Scenarios Implemented

The use-cases and scenarios implemented in this iteration are: Log in to BASIL Track Status Generate Reports Email Notification Manage User Accounts Scan/Swipe Assessment Log Off

5.

Results Relative to Evaluation Criteria

Iteration Plan Identify functional and non-functional requirements.

Result Major functional and non-functional requirements have been identified in the form of use-cases and supplementary specifications. The use-cases and relevant views are listed in UseCase Model artifact while as non-functional requirements are listed in Supplementary Specifications artifact. Major risks have been identified and are listed in Risk Management & Risk List artifact. Risk Management plan for the project has been devised and is described in Risk Management & Risk List artifact. Major actors (users) of the system along with the functions (use-cases) they would perform on the system have been identified and are described in Use-Case Model artifact. User interface prototype has been designed and developed for the system and is described in User Interface Prototype artifact. Software Development Plan has been developed for the system and is described in Software Development Plan artifact. The schedule and cost of the system has been formulated and are described in Software Development Plan artifact.

Identify major risks

Devise risk management plan

Design main actors and use-cases

Design initial user interface prototype

Develop Software Development Plan

Agreement on estimated cost and schedule

Confidential

<Company Name>, 2012

Page 5 of 6

Bar Coded Assessment System for Independent Leaning (BASIL) Iteration Assessment BASIL_Iteration_Assessment.docx

Version: 1.0 Date: 19/11/2010

6.

Test Results
As project is at a very early stage, no tests have been carried out so far.

7.

External Changes Occurred

No new changes in requirements or users needs have been identified at this stage of the project.

8.

Rework Required
As it becomes clearer as to how much effort and time this project will take, cost estimate will have to be reworked in the next iteration. As more use-cases develop during the further iterations, user interface prototype will have to be adapted in order to accommodate change in use-cases.

Confidential

<Company Name>, 2012

Page 6 of 6