Backup Project f Pandu Cp

8/13/2019 Backup Project f Pandu Cp

1/25

Fast Track Company is an Accounting firm established some one year back. They have around twenty emplosection is maintaining huge data in excel and word. The data maintained is of prime importance to Fast Trackinformation on file server located inside the office premises. Later in evening the network administrator backsback 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.


2/25

ees in there accounting section. Accounting. All employees store there backupup the file on tape. Fast Track wants the


3/25

Function Point AnalysisProject NameILFEIFEOEQEITotal Unadjusted Function PointsTotal GSCTotal Adjusted Function PointsProgrammer can complete how much FP per dayTotal Man DaysUse Case Point AnalysisProject NameUse Case EntityTotal UAWTotal UUCWTotal UUCP

Adjusted UCPHours

Days (By Karner Way)Comparison Between Unadjusted Function Points and Unadjusted Use Case PointsTotal Difference between Unadjusted Values (UUCP-UAFP)Factor Difference UAFP/UUCPNumber of elements in FPEIEOEQILFEIFTotal Elements in FPNumber of Use Case in UCPNumber of actorsTotal Elements in UCPTotal Difference in Elements (FP-UCP)


4/25

Backup Project Fast Track7006

1427

1.2333.21

0.8539.07058824

Backup Project fast TrackUse Case Entity Values

42529

15.0249300.498

37.56225

20.931034483

3021063251


5/25

Functionality DET RET Value

Backup Policy 7 2 700

0


6/25

DET's considers RET's considerd

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

Folders to be backed up,Backup policy


7/25

Functionality DET RET Value0


8/25

Functionality DET FTR Value0


9/25

Functionality DET FTR Value DET's FTR'sDisplay folders to be backed up 2 1 3 Folder name FoldersDisplay Backup Policy 7 1 3

00


10/25

Functionality DET FTR Value

Add Backup Policy 7 2 4

Update Backup Policy 7 2 4

Check timer and start back up 8 4 60000000

0000


11/25

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

Start Backup , Start timer Backup , Folders to be backed up

Time of the timer ,Start time, Folders to bebacked up, Backup folder name , Log file path ,

Add back folders , Start Backup , Start timer Current time , backup policy , backup folders and log file


12/25

GSC Attribute Definitions Value

Data communicationsHow many communication facilities arethere to aid in the transfer or exchange ofinformation with the application or system? 1

Distributed data processingHow are distributed data and processing

functions handled? 5Performance

Did the user require response time orthroughput? 5

Heavily used configuration How heavily used is the current hardwareplatform where the application will beexecuted? 1

Transaction rate How frequently are transactionsexecuted; daily, weekly, monthly, etc.? 5

On-Line data entryWhat percentage of the information isentered On-Line? 5

End-user efficiencyWas the application designed for end-userefficiency? 1

On-Line update How many ILFs are updated by On-Linetransaction? 5

Complex processingDoes the application have extensivelogical or mathematical processing? 5

ReusabilityWas the application developed to meetone or many users needs? 5

Installation easeHow difficult is conversion andinstallation? 5

Operational easeHow effective and/or automated are start-up, back up, and recovery procedures? 5

Multiple sites

Was the application specifically designed,

developed, and supported to be installedat multiple sites for multiple organizations? 5

Facilitate changeWas the application specifically designed,developed, and supported to facilitatechange? 5

GSC 1.23


13/25

Guidelines from ifpug.org CPM guideEI Counting RulesControl information is received from outside the application boundary.The control information is specified by the user to ensure compliance with business functionrequirements.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 RulesCount 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 RulesCount each user recognizable and nonrecursive field. Each user recognizable andnonrecursive 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 RulesThe 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 RulesThe 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.


14/25

Actor Name WeightNetwork Administrator 3Timer 1


15/25

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


16/25

Use Case Name Number of Transactions Weight

Define Back up Policy 4 10

Start Timer 3 5

Start Back up 5 10


17/25


18/25

Technical Factor Weight Value Weighted ValueDistributed System 2 1 2Response time 1 0 0End user efficiency 1 0 0Complex internal processing 1 2 2Reusable code 1 0 0Installation ease 0.5 0 0Easy use 0.5 4 2Portable 2 0 0Easy to change 1 0 0Concurrent 1 0 0Security objectives 1 0 0Direct access to third parties 1 0 0User training facilities 1 0 0

Total TCF 0.66

Guide lines for each factor is inside comments : Please note these are guidelines pr


19/25


20/25

for reusability in application itself as its too small

echnical guys.

verning body who has approved it so use it at your own risk


21/25

Environmental Factor Weight Value Weighted ValueFamiliarity with project 1.5 5 7.5

Application experience 0.5 2 1Object-oriented programming experience 1 2 2Lead analyst capability 0.5 2 1Motivation 1 0 0

Stable requirements 2 5 10Part-time Staff -1 0 0Difficult programming language -1 1 -1

Total EF 0.785

Guide lines for each factor is inside comments : Please note these are guideline


22/25

Description so that third person can understandeverybody know the project very well as the requirements are very clear 20 % percent application experience people are availableHave 2 years of OOPs experienceHave around 2 years experience lead analyst leading the projectProject beign small team has less motivation

Requirements do no changesNo part time staff Programming language is VB.NET

provided by me depending on my experience and some taken from function point guidelines its


23/25

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


24/25

Use Case Look Up0 01 52 53 54 10

5 106 107 108 159 15

10 15

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


25/25

Counting Rules For Use Case PointsUse 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 CRUDoperation 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 PointsGroup of Function Point EP's can map in to one Use Case.Its possible than Use Case and EP will not have oneto one mapping.Every ILF and it associated EI should be mapped to a Use CaseEvery EIF and it associated EI should be mapped to a Use Case

Actors have no equivalent mapping in EP

Documents

Backup Project f Pandu Cp