You are on page 1of 25

Fast Track Company is an Accounting firm established some one year back.

They have around twenty employees in there acco section is maintaining huge data in excel and word. The data maintained is of prime importance to Fast Track. All employees s information on file server located inside the office premises. Later in evening the network administrator backs up the file on tape back up procedure to be automated. Following parameters govern the way backup process is processed:1)Start time when the backup process will start. 2)Folders that has to be backed up. 3)Folder where the back up will be done. 4)Path where the log file will be stored. In case of back up fails a report is generated and stored in log file. Lets start first with writing a Use Case Assumptions: - Trust me having a good assumption list helps out. 1)Back ups are not incremental they just override existing back ups. 2)Log file has only details when the back up failed and which file the back up failed.

wenty employees in there accounting section. Accounting o Fast Track. All employees store there backup strator backs up the file on tape. Fast Track wants the

Function Point Analysis Project Name ILF EIF EO EQ EI Total Unadjusted Function Points Total GSC Total Adjusted Function Points Programmer can complete how much FP per day Total Man Days Use Case Point Analysis Project Name Use Case Entity Total UAW Total UUCW Total UUCP Adjusted UCP Hours Days (By Karner Way) Comparison Between Unadjusted Function Points and Unadjusted Use Case Points Total Difference between Unadjusted Values (UUCP-UAFP) Factor Difference UAFP/UUCP Number of elements in FP EI EO EQ ILF EIF Total Elements in FP Number of Use Case in UCP Number of actors Total Elements in UCP Total Difference in Elements (FP-UCP)

Backup Project Fast Track 7 0 0 6 14 27 1.23 33.21 0.85 39.07058824 Backup Project fast Track Use Case Entity Values 4 25 29 15.0249 300.498 37.56225 2 0.931034483 3 0 2 1 0 6 3 2 5 1

Functionality

DET

RET

Value

Backup Policy

7 0 0 0

DET's considers

RET's considerd

Start time, Folders to be backed up, Backup folder name , Folders to be backed up, Log file path , Add back folders , Start Backup , Start timer Backup policy

Functionality DET

RET

Value 0

Functionality DET

FTR

Value 0

Functionality Display folders to be backed up Display Backup Policy

DET 2 7

FTR 1 1

Value

DET's FTR's 3 Folder name Folders 3 0 0

Functionality

DET

FTR

Value

Add Backup Policy

Update Backup Policy

Check timer and start back up

6 0 0 0 0 0 0 0 0 0 0 0

DET's Start time, Folders to be backed up, Backup folder name , Log file path , Add back folders , Start Backup , Start timer Start time, Folders to be backed up, Backup folder name , Log file path , Add back folders , Start Backup , Start timer

FTR's

Backup , Folders to be backed up

Backup , Folders to be backed up

Time of the timer ,Start time, Folders to be backed up, Backup folder name , Log file path , Add back folders , Start Backup , Start timer Current time , backup policy , backup folders and log file

GSC Attribute Data communications

Definitions How many communication facilities are there to aid in the transfer or exchange of information with the application or system? How are distributed data and processing functions handled? Did the user require response time or throughput? How heavily used is the current hardware platform where the application will be executed? How frequently are transactions executed; daily, weekly, monthly, etc.? What percentage of the information is entered On-Line? Was the application designed for end-user efficiency? How many ILFs are updated by On-Line transaction? Does the application have extensive logical or mathematical processing? Was the application developed to meet one or many users needs? How difficult is conversion and installation? How effective and/or automated are startup, back up, and recovery procedures? Was the application specifically designed, developed, and supported to be installed at multiple sites for multiple organizations? Was the application specifically designed, developed, and supported to facilitate change?

Value

1 5 5

Distributed data processing Performance Heavily used configuration Transaction rate On-Line data entry End-user efficiency On-Line update Complex processing Reusability Installation ease Operational ease

1 5 5 1 5 5 5 5

Multiple sites

Facilitate change

GSC

5 1.23

Guidelines from ifpug.org CPM guide EI Counting Rules Control information is received from outside the application boundary. The control information is specified by the user to ensure compliance with business function requirements. For the identified process, one of the following two rules applies: 1) Processing logic is unique from other external inputs for the application. 2) Data elements are different from other external inputs identified. FTR Counting Rules Count each ILF maintained. Count each ILF or EIF read during processing. Count only one FTR when an ILF is both maintained and read. DET Counting Rules Count each user recognizable and nonrecursive field. Each user recognizable and nonrecursive field must be maintained on an ILF. Count each field that is not entered by the user, but through an EI is maintained on an ILF Count physical implementation techniques as a single DET for the entire group of fields. EIF Counting Rules The group of data is a logical group that fulfills specific user requirements. The group of data is referenced by, and external to, the application being counted. The group of data is not maintained by the application being counted. The group of data is counted as an ILF for at least one other application. The group of data identified has not been counted as an ILF for the application. EO Counting Rules The process sends data or control information external to the application boundary. The process is the smallest unit of activity that is meaningful to the end user in the business. The elementary process is self-contained and leaves the business in a consistent state. For the identified process, one of the following two rules applies: Processing logic is unique from other EOs. Data elements are different from other EOs. EQ Counting Rules An input request enters the application boundary. Output results exit the application boundary. Data is retrieved. The process is the smallest unit of activity that is meaningful to the end user in the business. The elementary process is self-contained and leaves the business in a consistent state. The data retrieved does not contain derived data. The processing does not update an ILF. For the identified process, one of the following two rules applies: Processing logic is unique from other EQs. Data elements are different from other EQs.

Actor Name Network Administrator Timer

Weight 3 1

Description so that third person can understand Network administrator has GUI which will be used for defining backup policy It will only use simple API for timer functionality.NO database interaction or GUI present

Use Case Name

Number of Transactions

Weight

Define Back up Policy

10

Start Timer

Start Back up

10

Description so that third person can understand Main Scenario 1. Network Administrator opens define Backup Policy. Back up policy screen starts with default values for start time equal to 12:00 PM if there is not policy defined previously. 2. Network administrator can specify the following details a. Start time if he wants to change. b. Folders which is to be backed up. This is multiple entries data. c. Backup folder where the backup will be done. d. Log files location where the log details will be stored. 3. Administrator can then start the Back up Task. This initiates the Start Timer Use Case. 4. Administrator also has option to start the back up at that moment. In that case Start Backup Use Case is triggered. Please note there is no Update alternate scenario or delete scenario it left to readers to think why there is no update routine Main Scenario 1. Timer checks the current time with time specified by the Network Administrator. 2. If the time is Equal to or greater than the time specified by the network administrator it start the Start Backup process. 3. If the time is less than time specified by network administrator it goes to step 1 again of this use case, Alternate Scenario Main Scenario 1. Program picks the folder from folders specified by the network administrator to be backed up. 2. Program copies all files to the folder where the backup will be saved. 3. Program checks if any folders are remaining to be backed up. If any folder are remaining to be backed up it repeats step2 of this Use Case 4. If there are no folders remaining it returns the control to Use Case invoking it. That means either Start Timer or Define Backup Policy. alternate scenario 1. If there is failure in backup the program writes the following details to log file Filename and Date and time

Technical Factor Distributed System Response time End user efficiency Complex internal processing Reusable code Installation ease Easy use Portable Easy to change Concurrent Security objectives Direct access to third parties User training facilities

Weight 2 1 1 1 1 0.5 0.5 2 1 1 1 1 1

Value 1 0 0 2 0 0 4 0 0 0 0 0 0 Total TCF

Weighted Value 2 0 0 2 0 0 2 0 0 0 0 0 0 0.66

Guide lines for each factor is inside comments : Please note these are guidelines provided by me depending on my experi

Description so a third person can understand Application copies files to main back up system No special requirement as its batch process which runs at night speed is of not prime importance Simple navigation for Network administrator. There is extensive logical processing in terms of browsing through folders and files and copying them across This is first time the company is making this application so no reusable code is available and second there is no scope for reusabilit Network administrator are technical guys who can do themselves As used by network administrator no special user freindliness is needed.As network administrator are them self quiet technical guys Only should work on windows 2000 server.See assumptions for details No special requirement as such for now. No requirement as such Its in house no requirement as such No requirement as such Network administrator can understand the application by themselves

se are guidelines provided by me depending on my experience and some taken from function point guidelines itself. There is no governing bod

cond there is no scope for reusability in application itself as its too small

or are them self quiet technical guys.

itself. There is no governing body who has approved it so use it at your own risk

Environmental Factor Familiarity with project Application experience Object-oriented programming experience Lead analyst capability Motivation Stable requirements Part-time Staff Difficult programming language

Weight Value Weighted Value 1.5 5 7.5 0.5 2 1 1 2 2 0.5 2 1 1 0 0 2 5 10 -1 0 0 -1 1 -1 Total EF 0.785

Guide lines for each factor is inside comments : Please note these are guidelines provided by me depending on my ex

Description so that third person can understand everybody know the project very well as the requirements are very clear 20 % percent application experience people are available Have 2 years of OOPs experience Have around 2 years experience lead analyst leading the project Project beign small team has less motivation Requirements do no changes No part time staff Programming language is VB.NET

e guidelines provided by me depending on my experience and some taken from function point guidelines itself. There is no gover

uidelines itself. There is no governing body who has approved it so use it at your own risk

Use Case Look Up 0 1 2 3 4 5 6 7 8 9 10 0 5 5 5 10 10 10 10 15 15 15

These are look up values used in use case do not touch this section

Counting Rules For Use Case Points Use Case Scenario should be non-recursive and processing logic should be different from other Use Cases. Role / Actor should be non-recursive. Minimum User goal level use case should be indentified. If two Use Cases have 60 % in common try to accommodate them using alternate scenario. Example CRUD operation Create,Read,Update and delete should come in one Use Case with alternate scenarios. If UseCase is exceeding 25 transactions split Use Case in two UseCases. Every transaction in Use Case should add buisness value from User Perspective. Sub-function level Use Case should be used to Capture algorothmic complexity.

Mapping Rules to be followed so that Use Case Point and Function Point can be compared. Every Elementary process (EI,EO,EQ,ILF and EIF) should be mapped to a Use Case,. Comparison can only be done on Unadjusted values that is on Unadjusted Function Points and Unadjusted Use Case Points Group of Function Point EP's can map in to one Use Case.Its possible than Use Case and EP will not have one to one mapping. Every ILF and it associated EI should be mapped to a Use Case Every EIF and it associated EI should be mapped to a Use Case Actors have no equivalent mapping in EP