Badger’s Rental

DVD/Game Rental System

Estimate of Effort

Version No: / 1.1
Draft/Final as of: / September 20, 2003
Author: / Ryan Thernes
Recipient: / Badger’s Rental
First issued to Recipient on: / September 23, 2003
Last issued to Recipient on: / September 23, 2003
Provided by: / Twilight Development

A Note on Document Control

The official document, also being the latest revision, can be obtained in copy form by contacting . All other forms may be transparent and not reflect the latest changes made.

The holder of this document takes full responsibility for ensuring that this document is unchanged in ALL areas in order to be kept in accordance with the official document. Any changes made to this document will cause it to be obsolete and no longer hold any legal merit whatsoever. This document will also be considered obsolete if it is not a first hand copy of the official document.

If at any time the holder is unsure of the validity of this document, contact should be made with Twilight Development to receive a guaranteed copy of the official document.

This document is subject to change and will be done without notification outside of the recipient and author. These changes may include the complete removal of a section, removal of part of a section or increased refinement in details of the project.

Revision history

Version / Date / Author / Summary of changes / Revision marks
0.1 / September 20, 2003 / Ryan Thernes / Initial Draft (incomplete: missing sections and tables) / No
0.2 / September 22, 2003 / Ryan Thernes / Table Notes Modified. Some sections still missing. Table of contents modified but still not complete. / No
0.3 / September 23, 2003 / Ryan Thernes / Missing sections filled in. Table of contents updated accordingly. / No
0.4 / September 24, 2003 / Ryan Thernes, Philip Westendorp, Greg Farrell and, Andriy Baranskyy / Revised after proof reading. Tables enlarged to become more viewable. LDAP and DB definitions added to glossary. / No
0.5 / September 24, 2003 / Ryan Thernes / Minor changes only. / No
0.6 / September 24, 2003 / Ryan Thernes / Added optimal duration and assumption. / No
1.0 / September 24, 2003 / Ryan Thernes / Final adjustments / No
1.1 / October 1, 2003 / Philip Westendorp / Estimate has been adjusted and reduced. Screen #s, code factors, and employee costs modified. / No

Table of Contents

Page 1 of 11

Introduction ______

1. Overview

1.1 Business Statement______

1.2 Approach______

1.3 Scope______

1.4 Conventions ______

2. Estimate

2.1 Development Effort Guidelines______

2.2 Use Case Development______

2.3 Project Estimate______

2.4 Resource Requirements______

3. Assumptions______

3.1 Technical______

3.2 Business______

3.3 General______

3.4 Candidates for Reducing Scope______

4. Glossary of Terms______

4

5

5

5

5

5

6

6

6

7

7

8

8

8

9

9

10

Page 1 of 11

Introduction

This document was written by Twilight Development at the request of Badger’s Rental. It provides an estimate for the effort required to change their current manual rental tracking system to a more efficient computerized one. This will result in easier tracking of items, rentals, and customer account information.

More information about Badger’s Rental can be obtained by emailing .

1. Overview

1.1 Business Statement

Badger’s Video is a rental facility that operates in the lower Mainland offering DVD’s and video games. Currently there are a total of 10 locations across the area.

Prior to this proposed project Badger’s video has done all rentals through a manual basis where upon customers must find their rentals on the store walls. For rentals, customers must fill out a card attached to the rental item that is kept by the store until the item is returned. This process has led to many items being lost since the card is the only record of a transaction. As well, store Employees have spent about half their time helping customers locate movies as well as giving advice on what items to rent. An aim of this software System proposal is to help to improve efficiency and security of the Customer’s rental operations.

1.2 Approach

The approach for the estimate was as follows:

  • Use case complexity, actors, numbers of screens, and confidence was analyzed to determine effort for each case;
  • The work breakdown was examined to identify items that could be removed from the scope.
  • All requirements and use cases were built off of the Requirements Document. An up-to-date version of the Requirements Document can be obtained from Twilight Development.

The workload was broken down into various sections that could be
encapsulated into single themed processes such as Customer Account Process
System. Each "theme" encapsulates all use cases that relate to it
specifically.
The estimate proposed is by no means a definitive or set amount. Various
suggestions are made to help reduce scope and price of the final
implementation. Actual production with the estimate will be done in phases
coordinated with the listed use-cases and will involve at least one phase of
prototyping during implementation for customer assessment.

Results of this estimate will be used for metrics for future estimates in similar projects.

2. Estimate

2.1 Development Effort Guidelines

Code Characteristic / Factor / Factor / Factor
Screens / 10 hours per screen
Database access / 10 hours per use case for read access / 20 hours per use case for update access
External System / LDAP requires 30 hours per use case / DB requires 10 hours per use case
Use Case Business Logic Complexity Multiplier / *1 for low complexity / *1.5 for medium complexity / *3.0 for high complexity

2.2 Use Case Development


2.3 Project Estimate

2.4 Resource Requirements

3. Assumptions

The following assumptions are divided into technical (covering product dependencies), business (covering business requirements) and general (covering everything else).

3.1 Technical

  • The Customer has secure and reliable Internet connection in all of the branches of Badger’s Rental.
  • The Customer is in possession of bar-code readers that have been installed before the system installation.
  • The Customer provides LDAP, and database environments before system testing begins.
  • Badger’s Rentals will have sufficient means of verifying that the Identification Documents supplied by the customers of Badger’s Rentals are not counterfeit.
  • The Customer will be using hardware approved by this Project team.

3.2 Business

  • The Customer will decide on which use cases (processes) to implement before the project initiation and any modifications to these use
    cases (processes) after the proposal has been accepted will be negotiated by the customer and Twilight Development
  • Validation of hours will be performed on weekly basis.
  • The deployment of the project will consider specific requirements of Badger’s Rental only.
  • The design and architecture of the system will be constructed for the Lower Mainland, BC, Canada branches of Badger’s Rental only.
  • The Customer will be easily accessible via email (will respond within 48 hours) for further requirements verification.

3.3 General

  • There will be a maximum of 20 use cases.
  • Status reports will be produced weekly beginning with September 30th till the end of the project.
  • Twilight Development is not responsible for the delays caused by factors that are not within control of this development team.
  • Team will be restricted to four (4) members.

3.4 Candidates for Reducing Scope

The following is a list of ideas, which can be used to reduce the overall effort and shorten the schedule of the development of the system.

  • Remove remaining non-functional requirements (Availability, Maintainability, Manageability, Security, Usability, and Performance), keeping only simple interface and functions.
  • Eliminate use cases not deemed “essential” by the customer.
  • Implement training in a later phase.
  • Reduce item search fields to search by only one criterion at a time.
  • Adding more team members up to the optimal level (average of approximately 7.7).

4. Glossary of Terms

Term / Definition
Billing Department (BD) / Employees of Badger’s Rental that can manage to billing functionality of the System as well as Employee accounts.
Cashier (CS) / An Employee of Badger’s Rental that deals specifically with checking-out of items.
Customer / Badger’s Rental representative in direct contact with Twilight Development
Customer Representative (CR) / An Employee of Badger’s Rental that can facilitate activities between the System and the customer. (i.e. search for items, add new customer accounts, edit customer accounts)
Employee (E) / Anyone who has access to the System with a valid ID and password.
Field / An element of a database record in which one piece of information is stored. (i.e. an item’s price field will contain the current price of the item) Fields may or may not be editable.
Item / An item that can be rented at Badger’s Rental. Information about the Item will be recorded in the System’s database.
LDAP / Lightweight Directory Access Protocol. A secure protocol, which we will be using for usernames and passwords.
Database (DB) / System storing all the data for items and store customers.

Page 1 of 11