Iteration Assessment Report (IAR)Version 1.1

Iteration Assessment Report (IAR)

LADOT Scanning

Team 08

Name / Primary Role / Secondary Role
Anirudh Govil / Project Manager / Life Cycle Planner
Jeffrey Colvin / Prototyper / Systems and Software Architect
Aditya Kumar / Feasibility Analyst / Project Manager
Nisheeth Joshi / Systems and Software Architect / Life Cycle Planner
Niraj Brahmkhatri / Operational Concept Engineer / Requirements Engineer
Corey Painter / IIV&V / Shaper

Version History

Date / Author / Version / Changes made / Rationale
11/21/11 / JC / 1.0 /
  • Original copy using with Instructional ICM-Sw v1.0 template
/
  • Initial Draft

11/21/11 / JC / 1.1 /
  • Update on project progress
/
  • Document needs to accurately reflect the project progress

Table of Contents

Iteration Assessment Report (IAR)

Version History

Table of Contents

Table of Tables

Table of Figures

1.Overview

1.1Capabilities Implemented

1.1.1Use-Cases

1.1.2Additional Requirements

1.2Summary of Test Results

2.Adherence to Plan

3.Summary of Core Capability Drive-through

Table of Tables

Table of Figures

1

IAR_TRR_F11a_T08_V1.1.docVersion Date: 12/05/11

Iteration Assessment Report (IAR)Version 1.1

1.Overview

1.1Capabilities Implemented
1.1.1Use-Cases
  • Login: Implemented. SSRD requirement CR-2.
  • Logout: Implemented. SSRD requirement CR-2.
  • Select job: Implemented.
  • Perform job: Implemented.
  • Log job call: Implemented.
  • Register job issues: Implemented. SSRD requirement SR-3.
1.1.2Additional Requirements
  • Validation: Implemented. SSRD requirement CR-1.
  • Retrieval of validation codes: Implemented. SSRD requirement SR-2.
  • English as language: Implemented. SR-1.
  • Auto-Complete fields: Implemented. No requirement, suggestion of LADOT employee.
  • Short-cut keys: Implemented. No requirement, suggestion of LADOT employee.
1.2Summary of Test Results

Testing has only been done locally by the developers with limited input from LADOT. The system, as it stands, currently is capable in overall functionality (has log-in, log-out, log calls, perform jobs) as well as some additional functionality such as auto-complete boxes and shortcut keys for common functions (to help if a call is received while driving).

Each facet of the application has been run over by the client multiple times and overall functionality has been approved.

2.Adherence to Plan

The project is on time and completed. Each facet has been tested and most have been approved. The finished code is still being reviewed by LADOT for final approval.

Most of the issues come not from mismanagement, but from the project being re-scoped so late in the process, delaying the start of the development phase. In the future, the project should be fully scoped from the beginning, instead of changing in the middle of the model phase. Additionally, issues arose with the team having to engaged in other commitments for other courses, which took away some planned time of development.

3.Summary of Core Capability Drive-through

The client was very impressed with the prototype when shown at the CCD. They were able to do a complete run-through of the application without any issues, only commenting on the layout of the pages. The project was finished on Friday, December 2nd for final comments on the code as well as the functionality.

1

IAR_TRR_F11a_T08_V1.1.docVersion Date: 12/05/11