Final Project Report

Energy Consumption Calculator

Project Supervisor
Adnan Asif
Submitted By
F11CS61993648
Kashif Nadeem mc090201436
Muhammad Bilal mc090200972
Software Projects & Research Section,
Department of Computer Sciences,
10
Virtual University of Pakistan
CERTIFICATE
This is to certify that as!if "adeem #mc$%$&$'()*+, -u!ammad
Bilal #mc$%$&$$%.&+ have wored o! a!d com"leted their #oftware
$ro%ect at #oftware & 'esearch $ro%ects #ectio!( )e"artme!t of *om"uter
#cie!ces( +irtual ,!iversity of $aista! i! "artial ful-llme!t of the
re.uireme!t for the de/ree of B# i! *om"uter #cie!ces u!der my
/uida!ce a!d su"ervisio!0
1! our o"i!io!( it is satisfactory a!d u" to the mar a!d therefore ful-lls
the re.uireme!ts of B# i! *om"uter #cie!ces0
Supervisor / Internal E0aminer
Adnan Asif
#u"ervisor(
#oftware $ro%ects & 'esearch #ectio!(
)e"artme!t of *om"uter #cie!ces
+irtual ,!iversity of $aista!
2222222222222222222
3#i/!ature4
E0ternal E0aminer/Subject Specialist
5567ter!al #u"ervisor Name88
2222222222222222222
3#i/!ature4
Accepted By1
2222222222222
39or o:ce use4
11
E34R5I6-
1! the !ame of ;llah( the *om"assio!ate( the
Merciful0
$raise <e to ;llah( =ord of *reatio!(
The *om"assio!ate( the Merciful(
Ki!/ of >ud/me!t?day@
Aou alo!e we worshi"( a!d to Aou alo!e we "ray
for hel"(
Buide us to the strai/ht "ath
The "ath of those who Aou have favored(
Not of those who have i!curred Aour wrath(
Nor of those who have /o!e astray0
12
5E5ICATI4"
To Our Parent
Tha! you your u!co!ditio!al su""ort with our studies a!d our
eCorts0
De are ho!ored to have you as our "are!ts0
Tha! you for /ivi!/ us a cha!ce to "rove a!d im"rove
ourselves throu/h all our wals of life0
13
AC"478E59E-E"T

14
we owe a great many thanks to a great many people who helped
and supported me during the writing of this book. Our deepest
thanks to Lecturer,
A5"A" ASIF,
ho !uides me in the pro"ect for lead and correcting #arious
documents of mine with attention and care. $e has taken pain to go
through the pro"ect and make necessary correction as and when
needed. e e%press our thanks to the all people for e%tending their
support. &hanks and appreciation to the helpful people at 'irtual
(ni#ersity )ro"ect &eam, for their support .e would also thank
our *nstitution and our faculty members without whom this pro"ect
would ha#e been a distant reality. e also e%tend our heartfelt
thanks to our family and well wishers.
PREFACE
1+
&his calculator brings the e%penses to light and also ,uantifies
the sa#ing possible. Our hope is that based on the four pieces of readily
a#ailable data you can enter in this calculator -current and desired
)(./01i., *& load, and cost per kh2, it will help the parties
appreciate the #alue of their efficiency efforts. 3fter taking the user
desired inputs this calculator will calculate all sa#ings including ser#er
energy sa#ings after #irtuali4ation, no. of racks in 5age sa#ings, total *&
load and total data center power sa#ing per years.
6inally calculate the bill amount in the case of pre7#irtuali4ation
and post #irtuali4ation. .nergy consumption calculator will calculate
both )(. / 01i. according to their specifications. 3s we know that
)(. is defined as the ratio of total power to run the data center facility
to the total power drawn by all *& e,uipment.
.nergy consumption calculator pro#ides a feature of current
energy le#el sliding bar to enter your data center8s current )(. -)ower
(sage .ffecti#eness2/01i. -0ata 1enter *nfrastructure .fficiency2.
9oth are widely used and accepted as well as adopted benchmarks for
efficiency in data centers. (ser can enter his current *& center load and
&otal data center .lectricity capacity.
TAB8E 4F C4"TE"TS
CHAPTER NO. 1
GATHERING & ANALYZING INFO....................................................21
1.1 Introduction 22
1.2 Purpose 23
1.3 Scope 23
1.3.1 .11 :cope ;;;;;;;;;;;;;;; 24
1.3.2 1urrent .nergy Le#el/*nput ;;;;;;;;; 2+
1.3.3 1urrent .nergy Output ;;;;;;;;; 2+
1.3.4 )(./01i. ;;;;;;;;;;;;;;; 2+
1.3.+ .nergy :a#ing -)er year2 ;;;;;;;;; 2<
1.4 Definitions and abbreviations 2
1.4.1 0efinitions ;;;;;;;;;;;;;;; 2=
1.4.2 3bbre#iations ;;;;;;;;;;;;;;; 2>
1.! "se case and usa#e scenarios 2

1.+.1 (se case 0iagram ;;;;;;;;;;;; 30
1.+.2 (sage scenarios ;;;;;;;;;;;; 30
1.+.2.1 3dministrator entered the total capacity of data center ; 30
1.+.2.2 3dministrator entered the total *& Load ;; 31
1.+.2.3 1ost per k ;;;;;;;;;;;; 32
1.+.2.4 'irtuali4ed *& e,uipment ;;;;;; 33
1.+.2.+ !raph representation of data ;;;;;; 33
1.+.2.< )ower (sage .ffecti#eness -)(.2 1alculation ; 34
1.+.2.= 0ata 1enter *nfrastructure .fficiency -01i.2 1alculation 3+
1.+.2.? .nergy sa#ings 1alculation ;;;;;; 3+
1<
1.6 Supp$e%entar& re'uire%ents 36
1.<.1 (sability ;;;;;;;;;;;;;;; 3=
1.<.2 )erformance ;;;;;;;;;;;;;;; 3=
1.<.3 :upportability ;;;;;;;;;;;;;;; 3=
CHAPTER NO. 2
PLANNING THE PROJECT..............................................................38
2.1 Introduction 39
2.1.1 )lanning phase ;;;;;;;;;;;; 3>
2.1.2 Ob"ecti#es of )lanning )hase for .11 ;;; 40
2.1.3 !oals of )lanning )hase for .11 ;;; 40
2.2 (et)odo$o#ies 4*
2.3 +vai$ab$e (et)odo$o#ies 4*
2.3.1 aterfall @ethod ;;;;;;;;;;;;; 41
2.3.2 *ncremental )rocess @odels ;;;;;;;;;; 42
2.3.3 .#olutionary )rocess @odels ;;;;;;;;;; 44
2.3.3.1 )rototyping ;;;;;;;;;;;;; 44
2.3.3.2 &he :piral @odel ;;;;;;;;;; 4+
2.3.4 3gile software de#elopment @odel ;;;;;;; 4<
2.3.4.1 1haracteristics ;;;;;;;;;; 4<
2.3.+ :crum 0e#elopment @odel ;;;;;;;;;; 4=
2.3.+.1 1haracteristics;;;;;;;;;;;;; 4=
2.3.< '7 @odel ;;;;;;;;;;;;;;;; 4?
2.4 +dopted (et)odo$o#ies 48
2.4.1 aterfall )rocess @odel ;;;;;;;;;; 4>
2.4.1.1 0efinition :tudy/3nalysis/Ae,uirements ; +0
2.4.1.2 9asic 0esign/:pecification )hase ;;;; +0
2.4.1.3 &echnical 0esign/0etailed 0esign ;;;; +0
2.4.1.4 1onstruction/*mplementation ;;;; +0
1=
2.4.1.+ &esting ;;;;;;;;;;;;; +0
2.4.1.< *ntegration ;;;;;;;;;;;;... +1
2.4.1.= @aintenance and management ;;;... +1
2.! ,easons for c)oosin# %et)odo$o#& !1
2.6 -or. P$an !2
2.<.1 ork )lan definition ;;;;;;;;;;;;... +2
2.<.2 *mportance in :oftware .ngineering ;;;;;;; +3
2. Pro/ect Structure !4
2.=.1 &eam :tructure ;;;;;;;;;;;;; +4
2.=.2 )ro"ect :chedule -:ubmission 1alendar2 ;;;; +4
CHAPTER NO. 3
DESIGNING THE PROJECT............................................................56
3.1 Introduction !
3.1.1 .11 3nalysis ;;;;;;;;;;;;;;;; +=
3.1.2 3nalysis needs ;;;;;;;;;;;;; +?
3.1.3 6easibility :tudy ;;;;;;;;;;;;; +?
3.1.4 0ata !athering ;;;;;;;;;;;;; +?
3.1.4.1 riting 0ocuments ;;;;;;;;;; +?
3.1.4.2 *nter#iews ;;;;;;;;;;;;; +?
3.1.4.3 Buestionnaires ;;;;;;;;;; +>
3.1.4.4 Obser#ations ;;;;;;;;;;;;; +>
3.1.4.+ :ampling ;;;;;;;;;;;;; +>
3.1.4.< 0ata 3nalysis ;;;;;;;;;;;;; +>
3.1.4.= 3nalysis report ;;;;;;;;;; <0
3.1.+ *ntroduction to design phase ;;;;;;;;;; <0
3.2 Purpose 61
3.3 Scope 62
3.4 +rc)itectura$ representation 63
3.4.1 3rchitecture design diagram definition ;;;; <3
3.4.2 3rchitecture design diagram instructions ;;;; <4
3.4.3 3rchitecture design diagram ;;;;;;;;;; <4
3.! D&na%ic %ode$in# 0se'uence dia#ra%1 6!
1?
3.+.1 :e,uence diagram definition ;;;;;;; <4
3.+.2 :e,uence diagram instructions ;;;;;;; <+
3.+.3 :e,uence diagram -.112 ;;;;;;;;;.... <<
3.+.4 :e,uence diagram of )(. and 01i. 1alculation ; <<
3.+.+ 9ill and energy sa#ing calculation ;;;;;;; <=
3.+.< !raphical representation ;;;;;;; <=
3.6 2b/ect34o#ica$ %ode$ 0C$ass dia#ra%1 68
3.<.1 1lass diagram definition ;;;;;;;;;; <?
3.<.2 1lass diagram of .11 ;;;;;;;;;; <?
3. Dep$o&%ent (ode$ .. 69
3.=.1 0eployment diagram definition ;;;;;;.. <>
3.=.2 0eployment diagram of .11 ;;;;;;.. <>
3.8 Database (ode$ 0Database Dia#ra%1 .. *
3.?.1 0atabase 0iagram definition ;;;;;;.. =0
3.?.2 0atabase 0iagram of .11 ;;;;;;.. =0
3.9 5rap)ica$ "ser Interface .. 1
3.>.1 *nterface diagram definition ;;;;;;.. =1
3.>.2 *nterface design of .11 ;;;;;;;;;.. =1
3.>.3 *nput !(* -)re7'irtuali4ation2 ;;;;;;.. =2
3.>.4 *nput !(* -)ost7'irtuali4ation2 ;;;;;;.. =2
3.>.+ Output !(* -Aesults2 ;;;;;;;;;.. =2
3.>.< Output !(* -!raphical representation2 ;;;.. =3
3.>.= Output !(* -)(. C 01i. !raph2 ;;;;;;.. =3
3.>.? !(* helping $*D&: ;;;;;;;;;.. =4
CHAPTER NO.4
DEVELOPMENT.............................................................................75
4.1 0e#elopment *ntroduction ;;;;;;;;;;;;.. =<
4.2 0e#elopment plan 3rchitecture diagram ;;;;;. =<
4.2.1 3rchitecture design diagram instructions ...;;;;.. =<
4.2.2 3rchitecture design diagram of .11 ;;;;;. ==
1>

CHAPTER NO.5
DEPLOYMENT...............................................................................78
+.1 0eployment *ntroduction ;;;;;;;;;;;;;; =>
+.2 0eployment plan ;;;;;;;;;;;;;; =>
+.2.1 0eployment t plan instruction ;;;;;;;; =>
+.2.2 0eployment plan of .11 ;;;;;;;; ?0
REFERENCES................................................................................81
20
CHAPTER 1
Gathering & Analyzing Info
21
':' I"TR456CTI4"
0ata gathering -some time called primarily in#estigation2 is #ery important
part of this document because all future work will be done on the basis of this data
gathering. 3ll rele#ant information searched and colleted form different sources to
co#er up the task. 0uring this phase research is being conducted which includes
brainstorming about the software, what it is going to be and what purpose is it going
to fulfill. (nless you know what you are going to design, you cannot approach the
problem. $ere, the specifications of the output or the final product are studied and
marked. *f the software that is going to be designed should not contain certain
features, for reasons like security, then it is also mentioned in this stage. )roblems are
defined and understand in this phase.
;! attractive( i!formative( a!d user?frie!dly re"ort ca! <e
used as outreach material to i!form the "u<lic a<out "ro%ects tai!/
"lace i! their watershed a!d ca! hel" to /ai! wides"read su""ort
for these a!d future "ro%ects0 ; short fact sheet or <rochure that
i!cludes i!formatio! from the re"ort ca! hel" to s"read the word
a<out the "ro%ect0
&he 6inal )ro"ect Aeport refers to finali4e the pro"ect, which includes basic
gathering and analy4ing information, planning and method that are used to establish
or adopted to de#elop .nergy 1onsumption 1alculator, de#elopment which include
all logical designing phases and deployment which indicates the structural process of
.nergy 1onsumption 1alculator. The i!troductio! should co!tai!
<ac/rou!d i!formatio! o! the "ro%ect( i!cludi!/ the "ro%ect area0
22
':& P6RP4SE
&he purpose of this document is to present a detailed description of the
.nergy 1onsumption 1alculator. *t will e%plain features of the .11, the interfaces of
the .11, what the .11 will do, the constraints under which it must operate and how
the .11 will react to e%ternal stimuli. *n the final pro"ect report all documents are
re#isited and e%plained in detailed.
Aeports communicate information which has been compiled as a result of
research and analysis of data and of issues. Aeports can co#er a wide range of topics,
but usually focus on transmitting information with a clear purpose, to a specific
audience. !ood reports are documents that are accurate, ob"ecti#e and complete. &hey
should also be well7written, clearly structured and e%pressed in a way that holds the
readerEs attention and meets their e%pectations. &he true #alue of the research may be
assessed through a report since the written report may be the Fonly tangible product
of hundreds of hours of work. Often reports are structured in a way that reflects the
information finding process and the writing up of the findingsG that is, summary of the
contents, introduction or background, methods, results, discussion, conclusion and/or
recommendations. &he inclusion of recommendations is one reason why reports are a
common form of writing in industry, as the informed recommendations are useful for
decision making.
*n this report, all functional characteristics of .nergy 1onsumption 1alculator
will be discussed in detailed. *t is #ery important that this report co#er all necessary
aspects of .nergy 1onsumption 1alculator.
':) SC4PE
9efore entering in the topic of the scope of the .nergy 1onsumption
1alculator let us start from the basic concept of, what is the pro"ect scope meanH
3ctually pro"ect scope is the work that needs to be accomplished to deli#er a product,
ser#ice or result with the specified features and function. :cope plays an important
role in pro"ects. *t is the first step while writing :A: documents.
23
*n .nergy 1onsumption 1alculator scope includes the e%pected work effort
and results and it must be documented and accepted before the pro"ect begins. *t is a
challenging "ob for the software de#eloper to write accurate :A: document to e%press
under de#eloping software. 9ecause we know that all pro"ects are defined by their
goals, ob"ecti#es, boundaries and constraints. !etting a detailed but clear picture of
our pro"ect scope will put us toward completing the pro"ect successfully.
':):'ECC Scope
.nergy use is a central issue for the data centers. )ower draw for data centers
ranges from a few k for a rack of ser#ers in a closet to se#eral tens of @ for large
facilities. .nergy 1onsumption 1alculator helps *& professionals and 17Le#el
management understand the short term and the long term sa#ings that can be achie#ed
by impro#ing the energy efficiency of there data center infrastructure. 6or energy
sa#ing, different tools and application are a#ailable that compute o#erall energy
consumption and manage all calculation to display the efficiency and sa#ings. 6or
this purpose we are designing a desktop application with named I.nergy
1onsumption 1alculatorJ, which will help the data centers to sa#e energy and o#erall
cost yearly basics or monthly basics. &his software can be used for small data centers
as well as large data centers and it will help the data centers to reduce their electricity
cost.
&he scope of this pro"ect will broadly co#er the .nergy consumption calculator
features a#ailable in this pro"ect. &he features co#ered in this calculator will enable to
administrator to calculate &otal Load a#ailable to *& e,uipment details i.e. :er#ers,
Detworking .,uipment, and .n#ironment 1ontrol .,uipment. &he goal of this
pro"ect is to calculate total .nergy (sed by *& .,uipment.
&his will also help to &otal .lectricity 1ost calculation -per month or yearly
basis2 C .nergy sa#ing by #irtuali4ation. !raphics Aepresentation of )ower (sage
.ffecti#eness -)(.2 C 0ata 1enter *nfrastructure .fficiency -01*.2 will add that
will reflect the impact of energy. 9ased upon this information this will enable to
administrator to make comparison of energy sa#ing.
24
':):&Current Energy 8evel/Input
.nergy consumption calculator pro#ides a feature of current energy le#el sliding
bar to enter your data center8s current )(. -)ower (sage .ffecti#eness2/01i. -0ata
1enter *nfrastructure .fficiency2. 9oth are widely used and accepted as well as
adopted benchmarks for efficiency in data centers. (ser can enter his current *&
center load and &otal data center .lectricity capacity. (ser also able to mention
electricity cost per k to calculate the result.
':):)Current Energy 4utput/Annual 5ata Center E;ciency
Saving
&his calculator brings the e%penses to light and also ,uantifies the sa#ing
possible. Our hope is that based on the four pieces of readily a#ailable data you can
enter in this calculator -current and desired )(./01i., *& load, and cost per kh2, it
will help the parties appreciate the #alue of their efficiency efforts. 3fter taking the
user desired inputs this calculator will calculate all sa#ings including ser#er energy
sa#ings after #irtuali4ation, no. of racks in 5age sa#ings, total *& load and total data
center power sa#ing per years. 6inally calculate the bill amount in the case of pre7
#irtuali4ation and post #irtuali4ation.

':):(P6E/5CIE
.nergy consumption calculator will calculate both )(. / 01i. according to
their specifications. 3s we know that )(. is defined as the ratio of total power to run
the data center facility to the total power drawn by all *& e,uipment.


Total Facility Power
PUE
IT Equipment Power
=
fig. 1.1
Standard 5ood 6etter
2.0 1.4 1.1
2+
3n a#erage data center has a )(. of 2.0K howe#er se#eral super efficient data
centers ha#e known to achie#e a )(. as low as 1.1.
3s we know that 01i. is defined as the ratio of total power drawn by all *&
e,uipment to the total power to run the data center facility or we can say that it is the in#erse
of )(..
1

IT Equipment Power
DCiE
Total Facility Power PUE
= =
fig. 1.2
':):<Energy Savings #per year+
'irtuali4ed en#ironments can also result in dramatically lowered energy
consumption. Dot only is the number of physical ser#ers dramatically lowered, but the
software can monitor host resource utili4ation based on pre7defined thresholds. .nergy
consumption calculator will help the user to find out the all efficiency cost sa#ings. hile
taking the inputs as total capacity of facility, *& e,uipment load and cost per k, our
calculator pro#ide ,uick solutions and results that will display in the form of numeric
calculations and graphs representation.
':( 5EFI"ITI4"S A"5 ABBRE=IATI4"S
':(:'5EFI"ITI4"S
0efinitions are keyword used in this document. *t is important to define all important
term and keyword used in this document. *t will help the reader to understand in effecti#e
way. 3ll words and term which we used during our pro"ect documentations are discussed
below.
E>74R5S 5EFI"ITI4"S
Scope :cope is the work that needs to be accomplished to deli#er a
product, ser#ice or result with the specified features and function.
Po7er "sa#e
8ffectiveness
)(. is defined as the ratio of total power to run the data center
facility to the total power drawn by all *& e,uipment.
Data Center 01i. is defined as the ratio of total power drawn by all *&
Standard 5ood 6etter
0.+ 0.= 0.>
2<
Infrastructure
8fficienc&
e,uipment to the total power to run the data center facility or we
can say that it is the in#erse of )(..
Soft7are re'uire%ents 3 specification of an e%ternally obser#able beha#ior of the
systemK for e%ample, inputs to the system, outputs from the
system, functions of the system, attributes of the system, or
attributes of the system en#ironment.
Functiona$
,e'uire%ent
6unctional re,uirement bring7in the system8s #iew and define
from the system8s perspecti#e the software functionality the
de#elopers must build into the product to enable users to
accomplish their tasks stated in the user re,uirements 7 thereby
satisfying the business re,uirements.
9on Functiona$
re'uire%ent
Don76unctional re,uirements tend to identify IuserJ constraints
and IsystemJ constraints.
:irtua$i;ation
Virtualization in computing is the creation of a virtual (rather than actual)
version of something, such as a hardware platform, operating system,
storage device, or network resources.
"se Case Dia#ra% 3 use case is a functionality the user needs from the system. 3 use
case diagram depicts the relationship among the actors and use
cases.
+d%inistrator 3 person which control or maintain the calculation process, it is
said to be a user.
"sa#e scenario
3 usage scenario is likely to ha#e #arious sections depending
upon the le#el of details re,uired in a gi#en system.
-or. p$an
3 work plan is a document that, at a minimum, describes the
program, defines the program ob"ecti#es and goals, outlines the
technical approach, pro#ides a scope of work, and defines the
,uality assurance for the program.
Data F$o7 Dia#ra%
3 two7dimensional diagram, which e%plains how data is
processed and transferred in a system, is called Data Flow
Diagram.
8ntit& ,e$ations)ip
Dia#ra%
.ntity Aelationship 0iagram is an abstract and conceptual
representation of data.
+ctivit& dia#ra% 3n acti#ity diagram illustrates the dynamic nature of a system by
modeling the flow of control from acti#ity to acti#ity
Se'uence dia#ra% 3 se,uence diagram is a type of interaction diagram that
highlights the interdependencies between messages.
+rc)itecture dia#ra%s 3rchitecture diagrams display the organi4ation of architecture and
their elements, as well as corresponding namespaces.
C$ass dia#ra% &he class diagram is the main building block of ob"ect
2=
oriented modeling.
Database desi#n 0atabase design is the process of producing a detailed data
model of a database. &his logical data model contains all the
needed logical and physical design choices and physical storage
parameters needed to generate a design in a 0ata 0efinition
Language, which can then be used to create a database
Interface Desi#n 3n interface enables a user to interact with a system to perform a
task. *nterface design has #ery important role in software
engineering.
Dep$o&%ent dia#ra% &he deployment diagram specifies a set of constructs that can be
used to define the e%ecution architecture of systems that represent
the assignment of software artifacts to nodes.
<est case 3 test case in software engineering is a set of conditions or
#ariables under which a tester will determine whether
an application or software system is working correctly or not.
"sabi$it& .ffort re,uired to learn, operate, prepare input, and interpret
output of a program
Perfor%ance38fficienc& &he amount of computing resources re,uired by a program to
perform its function.
Supportabi$it& .ffort re,uired to modify or supportability an operational
program.
S&ste% boundar& &his internal system functional area of use case diagram is called
Isystem boundaryJ.
-aterfa$$ (ode$ *t suggests a systematic, se,uential approach to the software
de#elopment that begins with customer specification of
re,uirements and progresses through planning, modeling,
construction, and deployment.
Incre%enta$ Process
(ode$s
*t combines elements of linear and parallel process flows. &he
incremental model applies linear se,uences in staggered fashion
as calendar time processes
Spira$ (ode$ *t is an e#olutionary software process model that couples the
iterati#e nature of prototyping with the controlled and systematic
aspects of the waterfall model.
+#i$e deve$op%ent
(ode$
*t promotes adapti#e planning, e#olutionary de#elopment and
deli#ery, a time7bo%ed iterati#e approach, and encourages rapid
and fle%ible response to change.
2?
Scru% Deve$op%ent
(ode$
:crum is an iterati#e, incremental framework for pro"ect
management often seen in agile software de#elopment, a type of
software engineering.
':(:&ABBRI=IATI4"S
+bbreviations Stands for
8CC .nergy 1onsumption 1alculator
I< *nformation &echnology
P"8 )ower (sage .ffecti#eness
DCI8 0ata 1enter *nfrastructure .fficiency
S,S :oftware Ae,uirement :pecifications
.-) Lilo att $our
:( 'irtual @achine
"CD (se 1ase 0iagram
(-P @ethodology and ork )lan
P(P )ro"ect @anagement )hase
DD 0esign 0ocument
DFD 0ata 6low 0iagram
8,D .ntity Aelationship 0iagram
+D 3cti#ity 0iagram
SDD :e,uence 0iagram 0efinition
+DD 3rchitectural 0esign 0iagram
CD 1lass 0iagram
DDD 0atabase 0esign 0iagram
IDD *nterface 0esign 0iagram
5"I !raphical (ser *nterface
<C &est 1ase
<C< &est 1ase &itle
':< 6SE CASE A"5 6SA9E SCE"ARI4S
3 use case is a functionality the user needs from the system. 3 (10 depicts
the relationship among the actors and use cases. 3ctors represent e%ternal entities of
the system. &hese can be people or things, such as e%ternal hardware that interact
with system.
2>
':<:'6SE CASE 5IA9RA-
*n our .nergy 1onsumption 1alculator we are going to use an actor named
I3dministratorJ. 3ll functionality that this calculator performed is based on the
administrator because he will pro#ide e%ternal input and after that final calculation is
performed by the internal system of the calculator. &his internal system functional
area is called Isystem boundaryJ.

':<:&6SA9E SCE"ARI4S1
(sage scenario is the actual te%t7based representation of the use case, among
#arious representation methods discussed abo#e. 3 usage scenario is likely to ha#e
#arious sections depending upon the le#el of details re,uired in a gi#en system.
':<:&:' Administrator entered t!e total capacity of data
center1
"se Case <it$e 8nter <ota$ Capacit& of Data center
+bbreviated
<it$e
"se Case Id 3.1.1
,e'uire%ent Id 1
Description= &his case is used to take input of total capacity -in k2 of the data center.
.#ery data center has it own .lectricity capacity that is written in the input te%t field
with name 0ata 1enter 1apacity -in k2, because all calculation will be carry on with
30
this #alue
Pre Conditions= 3dministrator will open the software and it is important to input #alues
as total data center capacity to make calculations. &he default #alue will be set to 1000
k.
<as. Se'uence 8>ceptions
1. 3dministrator input the #alue.
2. 3dministrator able to input numerical #alue
3. :ystem will response when e#er user change the #alues
Post Conditions= &otal 0ata center capacity is entered and corresponding result will
display.
"nreso$ved issues=
+ut)orit&= 3dministrator
(odification )istor&= 1.0
+ut)or= 6111:<1>>3<4?
Description=
':<:&:& Administrator entered t!e total IT 8oad1
"se Case <it$e 8nter <ota$ I< 4oad
+bbreviated
<it$e
"se Case Id 3.1.2
,e'uire%ent Id 2
Description= &his case is used to take input of total *& Load -in k2 of the data center.
3dministrator entered the &otal *& Load that it includes all ser#er, racks and all
e,uipments used in *&.
Pre Conditions= 3dministrator will open the software and it is important to input #alues
as total data center capacity to make calculations. &he default #alue will be set to 1000
k.
<as. Se'uence 8>ceptions
1. 3dministrator input the #alue.
2. 3dministrator able to input numerical #alue
3. :ystem will response when e#er user change the #alues
Post Conditions= &otal *& Load is entered and corresponding result will display.
"nreso$ved issues=
+ut)orit&= 3dministrator
(odification )istor&= 1.0
+ut)or= 6111:<1>>3<4?
Description=
31
':<:&:) Costs per ?71
"se Case <it$e Cost per .-
+bbreviated
<it$e
"se Case Id 3.1.3
,e'uire%ent Id 3
Description= *n this case administrator will input the cost per k. *t is important #alue.
3ny administrator can input his own cost per k amount in As.
Pre Conditions= 3dministrator will pro#ide the amount of cost per k because it is the
feature and results will occur on the basics of that #alue.
<as. Se'uence 8>ceptions
1. 3dministrator will pro#ide the re,uired such cost #alue that is
charged in his data center.
2. :ystem will response when e#er user change the #alues
Post Conditions= &otal cost per k will be added
"nreso$ved issues=
+ut)orit&= 3dministrator
(odification )istor&= 1.0
+ut)or= 6111:<1>>3<4?
Description=
':<:&:( =irtuali@ed IT eAuipment1
"se Case <it$e :irtua$i;ed I< e'uip%ent
+bbreviated
<it$e
"se Case Id 3.1.4
,e'uire%ent Id 4
Description= &his case is used to take input from the administrator as how many *&
e,uipment he want to #irtuali4ed. &his #alue must be in the form of percentage.
Pre Conditions= 3dministrator will pro#ide the amount of *& e,uipment which he wants
to #irtuali4ed because it is the feature and results will occur on the basics of that #alue.
<as. Se'uence 8>ceptions
1. 3dministrator find out the no. of *& e,uipment that he want to
#irtuali4es.
2. 3dministrator enter the percentage of *& e,uipment that used in
data centers.
3. :ystem will response when e#er user change the #alues
Post Conditions= &otal data center8s #irtuali4ed *& e,uipment will be added
"nreso$ved issues=
32
+ut)orit&= 3dministrator
(odification )istor&= 1.0
+ut)or= 6111:<1>>3<4?
Description=
':<:&:< 9rap! representation of data1
"se Case <it$e 5rap) representation of data
+bbreviated
<it$e
"se Case Id 3.1.+
,e'uire%ent Id +
Description= &his case is used to display the graphical representation of results like as
)(., 01i., etc.
Pre Conditions= :ystem will take the resulted #alue of )(. and 01i. to represent
efficiency and yearly bill efficiency.
<as. Se'uence 8>ceptions
1. :ystem takes resulted #alue of )(..
2. :ystem take resulted #alue of 01i..
3. :ystem will take the resulted amount of bill before and after
#irtuali4ation.
4. :ystem will response when e#er user change the #alues
+. :ystem will display the final graph of abo#e acti#ities.
Post Conditions= !raphical representation will display in graph..
"nreso$ved issues=
+ut)orit&= :ystem
(odification )istor&= 1.0
+ut)or= 6111:<1>>3<4?
Description=
':<:&:* PoBer 6sage ECectiveness #P6E+ Calculation1
"se Case <it$e Po7er "sa#e 8ffectiveness Ca$cu$ation
+bbreviated
<it$e
P"8 0Po7er "sa#e 8ffectiveness1
"se Case Id 3.1.<
,e'uire%ent Id <
Description= &his case is used to calculate the )(. with formula as it is e,ual to &he
total data center capacity is di#ided to the total *& e,uipment load. *t better efficiency
le#el is 2.0
Pre Conditions= :ystem will take the total capacity of data center and total Load of *&
e,uipment to calculate )(..
<as. Se'uence 8>ceptions
33
1. :ystem take input as &otal data center capacity.
2. :ystem takes input as &otal *& e,uipment load.
3. :ystem will calculate the amount of )(..
4. :ystem will response when e#er user change the #alues
Post Conditions= )(. -)ower (sage .ffecti#eness2 will be calculated.
"nreso$ved issues=
+ut)orit&= :ystem
(odification )istor&= 1.0
+ut)or= 6111:<1>>3<4?
Description=
':<:&:. 5ata Center Infrastructure E;ciency #5CiE+
Calculation1
"se Case <it$e Data Center Infrastructure 8fficienc& Ca$cu$ation
+bbreviated
<it$e
DCi8 0Data Center Infrastructure 8fficienc&1
"se Case Id 3.1.=
,e'uire%ent Id =
Description= &his case is used to calculate the 01i. with formula as it is e,ual to &he
total *& e,uipment load is di#ided to the total data center capacity. *t better efficiency
le#el is 0.+
Pre Conditions= :ystem will take total Load of *& e,uipment and the total capacity of
data center to calculate 01i..
<as. Se'uence 8>ceptions
1. :ystem takes input as &otal *& e,uipment load.
2. :ystem take input as &otal data center capacity.
3. :ystem will calculate the amount of 01i..
4. :ystem will response when e#er user change the #alues
Post Conditions= 01i. -0ata 1enter *nfrastructure .fficiency2 will be calculated.
"nreso$ved issues=
+ut)orit&= :ystem
(odification )istor&= 1.0
+ut)or= 6111:<1>>3<4?
Description=
':<:&:D Energy savings Calculation1
"se Case <it$e 8ner#& Savin# Ca$cu$ation
+bbreviated
<it$e
"se Case Id 3.1.?
,e'uire%ent Id ?
34
Description= &his case is used to calculate the .nergy sa#ings with formulas on the
basics of cost per k.
Pre Conditions= :ystem will take cost per k and total used energy in *& before and
after *t e,uipment #irtuali4ation.
<as. Se'uence 8>ceptions
1. :ystem takes input as &otal *& e,uipment load.
2. :ystem takes input as &otal data center capacity.
3. :ystem takes input as cost per k.
4. :ystem calculates the energy sa#ings.
+. :ystem will response when e#er user change the #alues
Post Conditions= &otal .nergy sa#ings will be calculated.
"nreso$ved issues=
+ut)orit&= :ystem
(odification )istor&= 1.0
+ut)or= 6111:<1>>3<4?
Description=
':* S6PP8E-E"TAR> REE6IRE-E"TS
:upplementary re,uirements tend to identify IuserJ constraints and
IsystemJ constraints. 9usiness re,uirements should be kept pure and not reflect any
solution thinking. *t is a document that describes all the ser#ices pro#ided by the
system along with the constraints under which it must operate. &hat is, the
re,uirement document should not only describe the functionality needed and
pro#ided by the system, but it must also specify the constraints under which it must
operate. Don functional re,uirement are difficult to testK therefore they are usually
e#aluated sub"ecti#ely.
1onstraints are restrictions that are placed on the choices a#ailable to the
de#eloper for design and construction of the software product. &hese kinds of
re,uirements are called Don76unctional Ae,uirements. &hese are used to describe
e%ternal system interfaces, design and implementation constraints, ,uality and
performance attributes. &hese also include regulations, standards, and contracts to
which the product must conform.
:upplementary re,uirement play a significant role in the de#elopment of the
system. *f not captured properly, the system may not fulfill some of the basic business
3+
needs. *f proper care is not taken, the system may collapse. &hey dictate how the
system architecture and framework.
':*:'6sability1
:ystem must be easy to use and learn. Da#igation system must be user
friendly. 3long with click buttons, shortcut keys should be pro#ided for simple
interaction with the system.
':*:&Performance1
&he accomplishment of a gi#en task measured against preset known standards
of accuracy, completeness, cost, and speed. *n a contract, performance is deemed to
be the fulfillment of an obligation, in a manner that releases the performer from
all liabilities under the contract.
':*:)Supportability1
1ode should be simple and easily readable with proper comments where need.
Daming con#entions should be according to the policy of standards.

3<
CHAPTER 2
Planning the Project
3=
&:' I"TR456CTI4"
*n the planning phase the purpose of this document is to present a detailed description
of e%isting methodologies, adopted methodology and reasons for choosing the methodology
for the .nergy 1onsumption 1alculator. *t will e%plain features of the .11, the interfaces of
the .11, what the .11 will do, the constraints under which it must operate and how the
.11 will react to e%ternal stimuli.
&:':' Planning P!ase1
9efore entering in the topic of the planning phase of the .nergy 1onsumption
1alculator let us start from the basic concept of, what is the pro"ect planning phase
meanH &he )lanning )hase focuses principally on re,uired pro"ect planning work.
)roper comprehensi#e pro"ect planning is essential to a successful *& pro"ect, and
incomplete pro"ect planning and analysis are fre,uently root causes of pro"ect failure.
3ctually pro"ect planning is the work that needs to be accomplished to deli#er
a product, ser#ice or result with the specified features and function. )lanning phase
plays an important role in pro"ects. *t is the second step while writing )lanning phase
and methodology documents.
ith planning, pro"ects can run on time and interact effecti#ely with both
customers and suppliers. .#eryone in#ol#ed understands what is wanted and
emerging problems are seen -and dealt with2 long before they cause damage. *f we
want our pro"ects to run this way 7 then we must in#est time in planning.
&:':&4bjectives of Planning P!ase for ECC1
:uccessful completion of the )lanning )hase should compriseG
3?
3ssessment and description of the procurement management strategy.
.laboration and refinement of the pro"ect scope, schedule, risks, and costs.
0efinition of procedures for how the pro"ect will be e%ecuted, monitored,
controlled, and closed.
)lanning the future course of action.
3ppro#al to progress to the Ae,uirements 3nalysis )hase
*t must be fle%ible because it is updated whene#er issue will arise regain the
e%ecution of the pro"ect.
&:':)9oals of Planning P!ase for ECC1
&he purpose of the )lanning )hase is to plan all pro"ect processes and acti#ities
re,uired to ensure pro"ect success and to create a comprehensi#e set of plans, known as the
)@), to manage the pro"ect from this phase until pro"ect termination.
&:& -ETF454849>
3 system of principles or rules from which specific methods or procedures may be
deri#ed to interpret or sol#e different problems within the scope of a particular discipline.
(nlike an algorithm, a methodology is not a formula but a set of practices.
&o be fair, Mason ad#ocates the following definition of a methodologyG
F3 methodology is a set of guidelines or principles that can be tailored and applied to
a specific situation. *n a pro"ect en#ironment, these guidelines might be a list of things to do.
3 methodology could also be a specific approach, templates, forms, and e#en checklists used
o#er the pro"ect life cycle.F
&:) A=AI8AB8E -ETF454849IES
*n the planning phase of .nergy consumption calculator, it is #ery
important to study the e%isting system. 3ctually in this step, it is necessary to take
all preliminary in#estigations of e%isting system. &here are many calculators
a#ailable for calculating energy consumption with a lot number of ad#antages but
it is noticed that all ha#e separate ad#antages. &here will be software that will
pro#ide all in one feature. *n this regard .nergy consumption calculator is being
3>
designed but before discussing my own calculator8s specifications let us round up
the e%isting methodologies of e%isting energy consumption calculators.
3s much as +05 of a data centerEs energy bill is from infrastructure
-power C cooling e,uipment2. &here are many *nteracti#e data center efficiency
calculator which find out how reducing )(. will result in significant energy and
cost sa#ingsN
)rescripti#e process models were originally proposed to bring order to
the chaos of software de#elopment. $istory has indicated that these traditional
models ha#e brought a certain amount of useful structure to software engineering
work and ha#e pro#ided a reasonably effecti#e road map for software teams.
3ll software process models can accommodate the generic frame work
acti#ities. 9ut each applies a different emphasis to these acti#ities and defines a
process flow that in#okes each framework acti#ity in the different manner.
&:):' 7aterfall -et!od1
&he waterfall method, sometimes called the classic life cycle, suggests a
systematic, se,uential approach to the software de#elopment that begins with
customer specification of re,uirements and progresses through planning, modeling,
construction, and deployment.
Fig. 1 aterfall Proce!! "o#el
&he waterfall model is the oldest paradigm for software engineeringE $owe#er, o#er
the past three decades, criticism of this process model has caused e#en ardent
supporters to ,uestion its efficacy. 3mong the problems that are sometimes
encountered when the waterfall model is applied areG
40
Aeal pro"ects rarely follow the se,uential flow that the model
proposes. 3lthough the linear model can accommodate iteration, it
does so indirectly. 3s a result, changes can cause confusion as the
pro"ect team proceeds.
*t is often difficult for the customer to state all re,uirements e%plicitly.
&he aterfall model re,uires this and has difficulty accommodating
the natural uncertainty at e%ists the beginning of many pro"ects.
&he customer must ha#e patience. 3 working #ersion of the program
-s2 will not be a#ailable until late in the pro"ect time span. 3 ma"or
blunder, if undetected until the working program is re#iewed can be
disastrous.
&:):& Incremental Process -odels1
&here are many situations in which initial software re,uirements are
reasonably well defined, but the o#er all scope of the de#elopment effort pre#ent a
purely linear process.
&he incremental model combines elements of linear and parallel process
flows. &he incremental model applies linear se,uences in staggered fashion as
calendar time processes. hen an incremental model is used, the first increment is
often a core product.
&hat is, basic re,uirements are addressed but many supplementary features
remain undeli#ered. &he core product is used by the customer. 3s a result of use
and/or e#aluation, a plan is de#eloped.
41
Fig. 2 Incremental Proce!! "o#el!
&he plan addresses the modification of the core product to better meet the
needs of the customer and the deli#ery of the additional features and functionality.
&his process is repeated following the deli#ery of each increment, until the complete
product is produced.
&he increment process model focuses on deli#ery of an operational product
with each increment. .arly increments are stripped7down #ersions of the final
product, but the do pro#ide capability that ser#es that user and also pro#ide platform
for the e#aluation by the user.
*ncremental de#elopment is particularly useful when staffing is una#ailable
for a complete *mplementation by the business deadline that has been established for
the pro"ect. .arly increments can be implemented with fewer people. *f the core
product is well recei#ed then additional staff can be added to implement the ne%t
increment.
*n addition, increments can be planned to manage technical risks E6or
e%ample, a ma"or system might re,uire the a#ailability of new hardware that is under
de#elopment and whose deli#ery date is uncertain. *t might be possible to plan early
42
increments in a way that a#oids the use of this hardware, thereby enabling partial
functionality to be deli#ered to end users without inordinate delay.
&:):) Evolutionary Process -odels1
.#olutionary models are iterati#e. &hey are characteri4ed in a manner that
enables you to de#elop increasingly more complete #ersions of the software. &here
are two commonly e#olutionary process models
)rototyping
:piral @odel
&:):):' Prototyping1
Often a customer defines a set of general ob"ecti#es of software but does not
identify detailed re,uirements for the functions and features. *n other cases, the
de#eloper may be unsure of the efficiency of an algorithm, the adapt ability of an
operating system, or the form that human machine interaction should take. *n these,
and many other situations, a prototyping paradigm may offer the best approach.
)rototyping iteration is planned ,uickly, and modeling occurs. 3 ,uick design
focuses on the representation of those aspects of the software that will be #isible to
end users.

43
&he ,uick design leads to the construction of a prototype. &he prototype is
de#eloped and e#aluated by stakeholders, who pro#ide feedback that is used to
further refine re,uirements.
&:):):& T!e Spiral -odel1
&he spiral model is an e#olutionary software process model that couples the
iterati#e nature of prototyping with the controlled and systematic aspects of the
waterfall model. *t pro#ides the potential for the rapid de#elopment of increasingly
more complete #ersions of the software.
&he spiral de#elopment model is a risk dri#en process model generator that is
used to guide multi7stakeholder concurrent engineering of the software intensi#e
systems. *t has two distinguishing features.
One is Cyclic approach for the incrementally growing a
system8s degree of definition and implementation while
decreasing its degree of risk.
&he other is set of anc$or point mile!tone! for ensuring
stakeholder commitment to feasible and mutually satisfactory
system solutions.
44
(sing the spiral model, software is de#eloped in a series of e#olutionary
releases. 0uring early iterations, the release might be a model or prototype. 0uring
later iterations, increasingly more complete #ersions of the engineered system are
produced.
&:):( ;/ile software develo"me!t Model
3gile software de#elopment is a group of software de#elopment
methodologies based on iterati#e and incremental de#elopment, where re,uirements
and solutions e#ol#e through collaboration between organi4ing, cross7functional
teams. *t promotes adapti#e planning, e#olutionary de#elopment and deli#ery, a time7
bo%ed iterati#e approach, and encourages rapid and fle%ible response to change. *t is a
conceptual framework that promotes foreseen interactions throughout the
de#elopment cycle.
&:):(:' C!aracteristics1
&here are many specific agile de#elopment methods. @ost promote de#elopment,
teamwork, collaboration, and process adaptability throughout the life7cycle of the
pro"ect. 3gile methods break tasks into small increments with minimal planning and
do not directly in#ol#e long7term planning.
4+
3gile methods are sometimes characteri4ed as being at the opposite end of the
spectrum from plan dri#en or discipline methods. 3gile teams may, howe#er, employ
highly disciplined formal methods. 3 more accurate distinction is that methods e%ist
on a continuum from adapti#e to predicti#e. 3gile methods lie on the adapti#e side of
this continuum.
&:):< Scrum 5evelopment -odel
:crum is an iterati#e, incremental framework for pro"ect management often
seen in agile software de#elopment, a type of software engineering. 3lthough the
:crum approach was originally suggested for managing product
de#elopment pro"ects, its use has focused on the management of software
de#elopment pro"ects, and it can be used to run software maintenance teams or as a
general pro"ect/program management approach.
Fig. % &crum #e'elopment mo#el
&:):<:' C!aracteristics1
:crum is a process skeleton that contains sets of practices and predefined
roles. &he main roles in :crum areG
&he I:crum @asterJ, who maintains the processes -typically in
lieu of a pro"ect manager2
&he I)roduct OwnerJ, who represents the stakeholders and the
business
&he I&eamJ, a cross7functional group who do the actual
analysis, design, implementation, testing, etc
4<
&:):* =G -odel1
&he '7model represents a software de#elopment process -also applicable to
hardware de#elopment2 which may be considered an e%tension of the waterfall
model. *nstead of mo#ing down in a linear way, the process steps are bent upwards
after the coding phase, to form the typical ' shape. &he '7@odel demonstrates the
relationships between each phase of the de#elopment life cycle and its associated
phase of testing.
&he hori4ontal and #ertical a%es represents time or pro"ect completeness -left7
to7right2 and le#el of abstraction -coarsest7grain abstraction uppermost2, respecti#ely.
&:( A54PTE5 -ETF454849IES
6or energy sa#ing, different tools and application are a#ailable that compute
o#erall energy consumption and manage all calculation to display the efficiency and
sa#ings. 6or this purpose we are designing a desktop application with named I.nergy
1onsumption 1alculatorJ, which will help the data centers to sa#e energy and o#erall
cost yearly basics or monthly basics. &his software can be used for small data centers
as well as large data centers and it will help the data centers to reduce their electricity
cost.
&he features co#ered in this calculator will enable to administrator to
calculate &otal Load a#ailable to *& e,uipment details i.e. :er#ers, Detworking
.,uipment, and .n#ironment 1ontrol .,uipment. &he goal of this pro"ect is to
calculate total .nergy (sed by *& .,uipment.
4=
&his will also help to &otal .lectricity 1ost calculation -per month or yearly
basis2 C .nergy sa#ing by #irtuali4ation. !raphics Aepresentation of )ower (sage
.ffecti#eness -)(.2 C 0ata 1enter *nfrastructure .fficiency -01*.2 will add that
will reflect the impact of energy. 9ased upon this information this will enable to
administrator to make comparison of energy sa#ing.
&:(:' 7aterfall Process -odel
*n the planning phase we are using aterfall process method for better
documentations and work planning. &he waterfall model is a model which was
de#eloped for software de#elopmentK that is to create software. *t is called as such
because the model de#elops systematically from one phase to other in a downward
fashion, like a waterfall.
3s said earlier the waterfall model has been structured on multiple phases
especially to help out the software construction companies to de#elop an organi4ed
system of construction. 9y following this method, the pro"ect will be di#ided into
many stages thus easing out the whole process.
6or e%ample you start with )hase7* and according to this model, one only
progress to the ne%t )hase once the pre#ious one has been completed. &his way one
mo#es progressi#ely to the final stage and once that point is reached, you cannot turn
backK similar to the water in a waterfall.
4?
&:(:':' 5eHnition Study/Analysis/ReAuirements
0uring this phase research is being conducted which includes brainstorming
about the software, what it is going to be and what purpose is it going to fulfill.
(nless you know what you are going to design, you cannot approach the problem.
$ere, the specifications of the output or the final product are studied and marked. *f
the software that is going to be designed should not contain certain features, for
reasons like security, then it is also mentioned in this stage.
&:(:':& Basic 5esign/SpeciHcation P!ase
*f the first phase gets successfully completed and a well thought out plan for
the software de#elopment has been laid then the ne%t step in#ol#es formulating the
basic design of the software on paper. ith all the re,uirements and constraints in
hand, a final #iew of how the product should e%actly be, is decided. &he e%act way in
which the software should function is mentioned in this stage.
&:(:':) Tec!nical 5esign/5etailed 5esign
3fter the basic design gets appro#ed, then a more elaborated technical design
can be planned. $ere the functions of each of the part are decided and the engineering
units are placed for e%ample modules, programs etc.
&:(:':( Construction/Implementation
*n this phase the source code of the programs is written. Dow starts the
coding part. $ere, the software is designed as per the algorithm. $ence it becomes
#ery important that the algorithm should be properly designed.
&:(:':< Testing
3t this phase, the whole design and its construction is put under a test to check
its functionality. *f there are any errors then they will surface at this point of the
process. &he software designed as per the algorithm needs to go through constant
software testing and error correction processes to find out if there are any flaw or
4>
errors. $ere the #arious codes designed by different programmers are integrated and
is tested if the software works as per the specifications pro#ided.
&:(:':* Integration
*n the phase of *ntegration, the company puts it in use after the system has
been successfully tested. &he setup of the final software which needs to be installed at
the clients system is also designed and tested so that the client does not face any
problem during the installation of the software.
&:(:':. -anagement and -aintenance
@aintenance and management is needed to ensure that the system will
continue to perform as desired. &he work of software de#elopment does not end with
the handing of the software to the client. &he software designers may ha#e to
constantly pro#ide support to the client to resol#e any of the issues which may arise.
&here may be some flaws which get detected during the actual implementation of the
pro"ect. 0uring the maintenance phase, support and debugging is pro#ided for all
such problems.
&:< REAS4"S F4R CF44SI"9
-ETF454849IES
*n the #ery near future this will become clearer with our growing data center
power and cooling capacity issues, carbon regulations on the hori4on, and the
growing importance of en#ironmental goodwill. *n the near future, more and more
companies and consumers will insist on doing business with right companies who
share their en#ironmental concerns and which are taking appropriate measures to
minimi4e their natural path.
&here are a lot of reasons which forced me to de#elop a most efficient .nergy
1onsumption calculator. (ptime and redundancy are #isibly primary concerns, but
too few on either side are tracking how much energy their organi4ation uses in a year,
how much it is costing their company, and how much it is costing en#ironmentally.
+0
9ecause of the di#ide between facilities and *&, some data center managers
donEt yet grip the significance of energy costs in their data centers. Our calculator
brings these e%penses to light and also ,uantifies the sa#ings possible through
efficiency impro#ements.
e are using waterfall process method for the software energy consumption
calculator because of its wide use in software engineering. &he waterfall model is the
oldest and most widely used model in the field of software de#elopment. &here are
certain ad#antages of the waterfall model, which causes it to be the most widely used
model as yet. :ome of them can be listed as under.
&he pro"ect re,uires the fulfillment of one phase, before proceeding to the
ne%t. &herefore if there is a fault in this software it will be detected during one
of the initial phases and will be sealed off for correction.
3 lot of emphasis is laid on paperwork in this method as compared to the
newer methods. hen new workers enter the pro"ect, it is easier for them to
carry on the work from where it had been left. &he newer methods don8t
document their de#elopmental process which makes it difficult for a newer
member of the team to understand what step is going to follow ne%t. &he
aterfall @odel is a straight forward method and lets one know easily what
stage is in progress.
&he aterfall method is also well known amongst the software de#elopers
therefore it is easy to use. *t is easier to de#elop a lot of software through this
method in short span of time0
One great ad#antage of the waterfall model is that documentation is produced
at e#ery stage of the waterfall model de#elopment. &his makes the
understanding of the product designing procedure simpler.
&:* 74R P8A"
&:*:' 7or? Plan deHnition
+1
3 work plan is a document that, at a minimum, describes the program, defines
the program ob"ecti#es and goals, outlines the technical approach, pro#ides a scope of
work, and defines the ,uality assurance for the program.
&he pro"ect work plan is created along with the appropriate )ro"ect 0efinition.
*t may seem ob#ious, but the work plan is a #ital tool to ensure that the pro"ect team
knows what they need to do. @any people are uncomfortable creating a work plan.
(sually this is because the pro"ect has not been well defined.
&:*:& Importance in SoftBare Engineering
0efining and planning the pro"ect are not necessarily a se,uential process.
Oou will often find that you cannot complete the )ro"ect 0efinition without starting to
lay out the o#erall pro"ect work plan. *n many cases, these two deli#erables need to be
worked on in parallel.
3s you gather information around scope and deli#erables, you will need to
start laying out an o#erall timeline so that you can get your hands around estimated
effort and duration. 3s you get more information, fill in more detail on the work plan.
+2
&:. PR4IECT STR6CT6RE
&he main function of the pro"ect structure is to define standards the team will
use during the pro"ect. &hese include communication standards, documentation
standards, and change control procedure standards. )rogram @anagement takes the
lead in defining the pro"ect structure.
&:.:' Team Structure
3pportionment of responsibility and authority among the members of an
organi4ation. 6(D1&*OD3L OA!3D*P3&*OD, @3&A*Q OA!3D*P3&*OD, and
line organi4ation are three common types of organi4ational structure.
"
4
Student I5 "ame Responsibilities
1 @10>020143< L3:$*6 D30..@
$e is information collector and
maintains and manages all basic
re,uirements. $e also participates in
basic design and architecture. $e is
responsible of basic coding and testing.
2 @10>0200>=2 @. 9*L3L L$3D
$e is senior code tester and he will guide
and communicate the other team
member. $e also participates in high
le#el design and architecture.
&:.:& Project Sc!edule #Submission Calendar+
*n pro"ect management, a schedule consists of a list of a pro"ectEs terminal
elements with intended start and finish dates. &erminal elements are the lowest
element in a schedule, which is not further subdi#ided. &hose items are often
estimated in terms of resource re,uirements, budget and duration, linked by
dependencies and scheduled.
+3
NE $hases )elivera<les )escri"tio!
#u<missio!
)ate
1
!3&$.A*D! C
3D3LOP*D!
A.B(*A.@.D&
:A: 0ocument
0escribes the scope of
the pro"ect, functional
C non7functional
re,uirements, use case
diagram-s2, usage
scenarios
Do#ember 24, 2011
2
$=;NN1NB
$F;#6
Method &
Dor
$la!
)escri<es the
methodolo/y &
schedule of the "ro%ect
)ecem<er 23(
2011
3
;N;=A#1# ;N)
)6#1BN $F;#6
)esi/!
)ocume!t
1
;ctivity )ia/ram(
#e.ue!ce dia/rams(
;rchitecture )esi/!
)ia/ram( )9)3s4 a!d
6') if the "ro%ect
domai! re.uires
>a!uary 30(
2011
)esi/!
)ocume!t
11
E<%ect model (class
dia/ram( i!terface
desi/!( data<ase
desi/!
if the "ro%ect domai!
re.uires data<ase( test
cases( )e"loyme!t
)ia/ram ( *om"o!e!t
)ia/ram
March 12( 2012
4
9i!al
)elivera<les
*ode
&
91N;= '6$E'T
*om"lete $ro%ect
codi!/ a!d -!al "ro%ect
re"ort
>u!e 19( 2012
+4
CHAPTER 3
Designing the Project
++
):' I"TR456CTI4"
*n the 0esigning phase701, the purpose of this document is to present a
detailed description of logical designing by using #arious design modelsK the design
document describes a plan to implement the re,uirements. &his phase represents the
RRhowEE phase. 0etails on computer programming languages and en#ironments,
machines, packages, application architecture, distributed architecture layering,
memory si4e, platform, algorithms, data structures, global type definitions, interfaces,
and many other engineering details are established.
&he design may include the usage of e%isting components. *t will e%plain
features of the .11, the interfaces of the .11, what the .11 will do, the constraints
under which it must operate and how the .11 will react to e%ternal stimuli.
):':' ECC Analysis
9efore entering in the topic of the analysis phase of the .nergy 1onsumption
1alculator let us start from the basic concept of, what is the pro"ect analysis phase
meanH &he process of studying the e%isting system in detailed is called analy!i! of t$e
!y!tem. &he e%isted system is studied carefully before designing the new system or to
modify the e%isting system. :e#eral steps are in#ol#ed at analysis stage while
designing software. *n this phase, the current system is studied in detail. 3 person
responsible for the analysis of the system is known as analyst. *n system analysis, the
analyst conducts the following acti#ities.
+<
):':& Analysis "eeds
&his acti#ity is known as re,uirements analysis. *n this step we sum up the
re,uirements of the system from the user and the managers. &he de#eloped system
should satisfy these re,uirements during testing phase. e need to analysis the
e%isting calculators which are designed for the same purpose. *n this way we can get
knowledge to achie#e the goal of Energy Con!umption Calculator.
):':) Feasibility Study1
&he world feasibility means IpossibilityJ. 6easibility study is also called
preliminary in'e!tigation. *n this step, the financial, political, technical, and time
frame feasibilities for the software are proposed. 3ctually, feasibility study is
conducted to find out whether the proposed system is possible to de#elop and
acceptable for the organi4ation. &he ob"ecti#e of feasibility study is to e#aluate
different solutions and to propose the most feasible and least e%pensi#e solution. &his
step is most important in designing phase of IEnergy Con!umption Calculator.
):':( 5ata 9at!ering
*n this step, we collect data about the system to be de#eloped. e use different
tools and methods, depending on situation. e can gather data for our Energy
Con!umption Calculator in the following ways these areG
):':(:' 7riting 5ocuments
e may collect the information/data from written documents a#ailable
from manual7files of an organi4ation. &his method of data gathering is
normally used if we want to computeri4e the e%isting manual system or
upgrade the e%isting computer based system. &he written documents may be
reports, forms, memos, business plans, policy statements, organi4ational
charts and many others. &he written documents pro#ide #aluable information
about the e%isting system.
):':(:& IntervieBs
*nter#iew is another data gathering techni,ue. e can inter#iews, managers,
users/ clients, suppliers, and competitors to collect the information about the
+=
system. *t must be noted that the ,uestions to be asked from them should be
precise, rele#ant and to the point in this way we can collect precise data for
Energy Con!umption Calculator.
):':(:) Euestionnaires
Buestionnaires are the feedback forms used to collect *nformation. &he
inter#iew techni,ue to collect information is time7consuming method, so
Buestionnaires are designed to collect information from as many people as we
like. *t is #ery con#enient and ine%pensi#e method to collect information but
sometimes the response may be 1onfusing or unclear and insufficient.
):':(:( 4bservations
*n addition to the abo#e7mentioned three techni,ues to collect
information, the analyst -or his team2 may collect *nformation through
obser#ation. *n this collect techni,ue, the working, beha#ior, and other related
information of the e%isting system are obser#ed. *t means that working of
e%isting system is watched carefully.
):':(:< Sampling
*f there are large numbers of people or e#ents in#ol#ed in the system,
we can use sampling method to collect information. *n this method, only a
part of the people or e#ents in#ol#ed are used to collect information. 6or
e%ample to test the ,uality of a fruit, we test a piece of the fruit.
):':(:* 5ata Analysis
3fter completion of 0ata !athering step the collected data about the
system is analy4ed to ensure that the data is accurate and complete. 6or this
purpose, #arious tools may be used. &he most popular and commonly tools,
which we are going to be used for data analysis, areG
060s -0ata 6low 0iagrams2
.A0s -.ntity Aelationship 0iagrams2
3cti#ity 0iagrams
+?
:e,uence 0iagrams
3rchitectural 0esign 0iagrams

):':(:. Analysis Report
3fter completing the work of analysis, the re,uirements collected for
the system are documented in a presentable form. *t means that the analysis
report is prepared. *t is done for re#iew and appro#al of the pro"ect from the
higher management. &his report should ha#e three parts.
First? it should e%plain how the current system works.
Second, it should e%plain the problems in the e%isting system.
Fina$$&? it should describe the re,uirements for the new system and
make recommendations for future.
3naly4ing the trade7offs of necessary comple%ity allows for many things to
remain simple which, in turn, will e#entually lead to a higher ,uality product. &he
architecture team also con#erts the typical scenarios into a test plan.
*n our approach, the team, gi#en a complete re,uirement document, must also
indicate critical priorities for the implementation team. 3 critical implementation
priority leads to a task that has to be done right. *f it fails, the product fails. *f it
succeeds, the product might succeed. 3t the #ery least, the confidence le#el of the
team producing a successful product will increase. &his will keep the implementation
team focused. .%actly how this information is con#eyed is a skill based on e%perience
more than a science based on fundamental foundations.
):':< Introduction to 5esign P!ase
*n systems design the design functions and operations are described in detail,
including screen layouts, business rules, process diagrams and other documentation.
&he output of this stage will describe the new system as a collection of modules or
subsystems. &he design stage takes as its initial input the re,uirements identified in
the appro#ed re,uirements document. 6or each re,uirement, a set of one or more
+>
design elements will be produced as a result of inter#iews, workshops, and/or
prototype efforts.
0esign elements describe the desired software features in detail, and generally
include functional hierarchy diagrams, screen layout diagrams, tables of business
rules, business process diagrams, pseudo code, and a complete entity7relationship
diagram with a full data dictionary. &hese design elements are intended to describe
the software in sufficient detail that skilled programmers may de#elop the software
with minimal additional input design.
*n the 0esigning phase of .nergy consumption calculator, it is #ery important
to study the e%isting system. 3ctually in this step, it is necessary to take all
preliminary in#estigations of e%isting system. &here are many calculators a#ailable
for calculating energy consumption with a lot number of ad#antages but it is noticed
that all ha#e separate ad#antages. &here will be software that will pro#ide all in one
feature
):& P6RP4SE
&he features co#ered in this calculator will enable to administrator to calculate
&otal Load a#ailable to *& e,uipment details i.e. :er#ers, Detworking .,uipment, and
.n#ironment 1ontrol .,uipment. &he goal of this pro"ect is to calculate total .nergy
(sed by *& .,uipment.
&his will also help to &otal .lectricity 1ost calculation -per month or yearly
basis2 C .nergy sa#ing by #irtuali4ation. !raphics Aepresentation of )ower (sage
.ffecti#eness -)(.2 C 0ata 1enter *nfrastructure .fficiency -01*.2 will add that
will reflect the impact of energy. 9ased upon this information this will enable to
administrator to make comparison of energy sa#ing.
6or energy sa#ing, different tools and application are a#ailable that compute
o#erall energy consumption and manage all calculation to display the efficiency and
sa#ings. 6or this purpose we are designing a desktop application with named I.nergy
1onsumption 1alculatorJ, which will help the data centers to sa#e energy and o#erall
cost yearly basics or monthly basics. &his software can be used for small data centers
<0
as well as large data centers and it will help the data centers to reduce their electricity
cost.
*n the #ery near future this will become clearer with our growing data center
power and cooling capacity issues, carbon regulations on the hori4on, and the
growing importance of en#ironmental goodwill. *n the near future, more and more
companies and consumers will insist on doing business with right companies who
share their en#ironmental concerns and which are taking appropriate measures to
minimi4e their natural path.
&here are a lot of reasons which forced me to de#elop a most efficient .nergy
1onsumption calculator. (ptime and redundancy are #isibly primary concerns, but
too few on either side are tracking how much energy their organi4ation uses in a year,
how much it is costing their company, and how much it is costing en#ironmentally.
9ecause of the di#ide between facilities and *&, some data center managers
donEt yet grip the significance of energy costs in their data centers. Our calculator
brings these e%penses to light and also ,uantifies the sa#ings possible through
efficiency impro#ements.
):) SC4PE
&he 0esign phase is when we build the plan for how we will take our pro"ect
through the rest of the :0L process 7 from implementation, to #erification, to release.
0uring the 0esign phase we establish best practices to follow for this document by
way of functional and design specifications, and we perform risk analysis to identify
threats and #ulnerabilities in your software.
e need to demonstrate the physical working of .nergy 1onsumption
1alculator. 3ll implementations and test cases are applied to it. *n this document we
are going to end the designing phase and be sure that our software will work properly.
&he design document S ** may include the usage of presented method. *t will
e%plain features of the .11, the interfaces of the .11, what the .11 will do, the
<1
constraints under which it must operate and how the .11 will react to e%ternal
stimuli. 9y using different diagrams we will describe the process and working of
.nergy 1onsumption 1alculator.
*n this 0esign phase, we are describing some illustration for .nergy
1onsumption 1alculator. e e%press class diagram that describes the structure of a
system by showing the systemEs classes, their attributes, operations -or methods2, and
the relationships among the classes. &o e%press in detailed we describing 0atabase
0iagram, 0atabase design is the process of producing a detailed data model of
a database. &he term database design can be used to describe many different parts of
the design of an o#erall database system.
e are using *nterface design which deals with the process of de#eloping a
method for two -or more2 modules in our 1alculator to connect and communicate.
&hese modules can apply to hardware, software or the interface between a user and a
machine. 3n e%ample of a user interface could include a !(*, a control panel for a
nuclear power plant, or e#en the cockpit of an aircraft. *n systems engineering, all the
inputs and outputs of a system, subsystem, and its components are listed in
an interface control document often as part of the re,uirements of the engineering
pro"ect. &he de#elopment of a user interface is a uni,ue field.
9y using deployment diagram we can specify a set of constructs that can be
used to define the e%ecution architecture of our calculator that represent the
assignment of software artifacts to nodes. *n the test case we test our .nergy
1onsumption 1alculator to meet all re,uirements mention in :A: S 0ocument. *n
this way we can check all use case scenarios.
):( ARCFITECT6RA8 PRESE"TATI4"
):(:' Arc!itecture 5esign 5iagram 5eHnition1
3rchitecture diagrams display the organi4ation of architecture and their
elements, as well as corresponding namespaces. 3rchitecture diagrams are typically
used to depict the high7le#el organi4ation of a software pro"ect. 3rchitecture design
<2
diagrams e%press the whole process of the system in the form of real life ob"ects and
components that are used in the software.
):(:& Arc!itecture 5esign 5iagram Instructions1
:oftware architecture is commonly defined in terms of structural elements and
relationships. :tructural elements are identified and assigned responsibilities that
client elements interact with through FcontractedF interfaces. :oftware architecture
must be distinguished from lower7le#el design -e.g., design of component internals
and algorithms2 and implementation, on the one hand, and other kinds of related
architectures, on the other.
6or instance, software architecture is not the information -or data2 model,
though it uses the information model to get type information for method signatures on
interfaces, for e%ample. *t is also not the architecture of the physical system, including
processors, networks, and the like, on which the software will run.
):(:) Arc!itecture 5esign 5iagram of Energy
Consumption Calculator1
<3
):< 5>"A-IC -45E8I"9 #SEE6E"CE
5IA9RA-+
):<:' SeAuence 5iagram 5eHnition
3 se,uence diagram is a type of interaction diagram that highlights the
interdependencies between messages. 3 se,uence diagram shows, as parallel #ertical
lines, different processes or ob"ects that li#e simultaneously, and, as hori4ontal
arrows, the messages e%changed between them, in the order in which they occur. &his
allows the specification of simple runtime scenarios in a graphical manner. :e,uence
diagrams are sometimes called e#ent diagrams, e#ent scenarios, and timing diagrams.
):<:& SeAuence 5iagram Instructions
(@L se,uence diagrams model the flow of logic within your system in a
#isual manner, enabling you both to document and #alidate your logic, and are
commonly used for both analysis and design purposes. :e,uence diagrams are the
<4
most popular (@L artifact for dynamic modeling, which focuses on identifying the
beha#ior within your system.
*n :e,uence diagram, 3n action initiator is used.
&his symbol marks the ob"ect that initiates the
message.
*n :e,uence diagram. 3n action duration symbol is
used. 0uration notations indicate the length of time
needed to complete a task.
*n se,uence diagram, (se arrows or lines to
represent communication between ob"ects. (se
half7arrowed lines to represent asynchronous
messages. 3synchronous messages are sent from an
ob"ect that will not wait for a response from the
recei#er before continuing its tasks.
):<:) SeAuence 5iagram of Energy Consumption
Calculator
):<:( P6E and 5CiE Calculation
<+
):<:< Bill J Energy Saving Calculation
Fig. (% &equence Diagram of )ill an# Energy &a'ing Calculation
):<:* 9rap!ical Representation
<<
Fig. (* &equence Diagram of +rap$ical repre!entation
):* 4BIECT/849ICA8 -45E8 #C8ASS
5IA9RA-+
):*:' Class 5iagram 5escription
&he class diagram is the main building block of ob"ect oriented modeling.
1lass diagrams can also be used for data modeling. &he classes in a class diagram
represent both the main ob"ects and or interactions in the application and the ob"ects
to be programmed. *n a class diagram, the classes are arranged in groups that share
common characteristics.
3 class diagram resembles a flowchart in which classes are portrayed as
bo%es, each bo% ha#ing three rectangles inside. &he top rectangle contains the name
of the classK the middle rectangle contains the attributes of the classK the lower
rectangle contains the methods, also called operations, of the class. Lines, which may
ha#e arrows at one or both ends, connect the bo%es. &hese lines define the
relationships, also called associations, between the classes.
):*:& Class 5iagram of Energy Consumption Calculator
<=
*n the 1lass 0iagram of .nergy 1onsumption 1alculator we need to make all
class of all entities in#ol#ed in the system. *n e#ery class each entity has its own
attributes and functions which better e%press the working of .nergy 1onsumption
1alculator.
*n 1lass 0iagram we also need to represent relationships among all entities
which describe interaction of each entity with other entity or entities.
):. 5EP84>-E"T -45E8
):.:' 5eployment 5iagram 5escription
&he deployment diagram specifies a set of constructs that can be used to
define the e%ecution architecture of systems that represent the assignment of software
artifacts to nodes. Dodes are connected through communication paths to create
network systems of arbitrary comple%ity.
Dodes are typically defined in a nested manner, and represent either hardware
de#ices or software e%ecution en#ironments. 3rtifacts represent concrete elements in
<?
the physical world that are the result of a de#elopment process. 0eployment diagrams
show a systemEs physical layout, re#ealing which pieces of software run on what
pieces of hardware.
):.:& 5eployment 5iagram of Energy Consumption
Calculator
):D 5ATABASE -45E8#5ATABASE 5IA9RA-+
):D:' 5atabase 5esign 5escription
0atabase design is the process of producing a detailed data model of
a database. &his logical data model contains all the needed logical and physical
design choices and physical storage parameters needed to generate a design in a 0ata
0efinition Language, which can then be used to create a database. 3 fully attributed
data model contains detailed attributes for each entity.
&he term database design can be used to describe many different parts of the
design of an o#erall database system. )rincipally, and most correctly, it can be
thought of as the logical design of the base data structures used to store the data. *n
the relational model these are that tables and #iews.
):D:& 5atabase 5esign of Energy Consumption
Calculator
<>
):% 9RAPFICA8 6SER I"TERFACE
):%:' Interface 5esign 5escription
3n interface enables a user to interact with a system to perform a task.
*nterface design has #ery important role in software engineering. :ometimes users
"udge system by its interface rather than its functionality so we can say that poorly
designed interface can cause a user to make catastrophic errors.
0ue to poor user interface many software are ne#er used. 9ecause most users
interact with system through graphical user interface although, in some cases, legacy
te%t7based interfaces are still used. :o in this document we use some good looking
interface to attract the attention of the user.

=0
):%:& Interface 5esign of Energy Consumption
Calculator
):%:) Input 96I #PreG=irtuali@ation+
*n this !(* user or administrator can input all #alues.
):%:( Input 96I #PostG=irtuali@ation+
=1
*n this !(* partition user or administrator enters #irtuali4ed *&
.,uipments.
):%:< 4utput 96I #Results+
*n the gi#en partition of output !(* user can get resulted #alue.
):%:* Impact on Bill #9rap!ical representation+
*n this partition of !(* user can get graphical representation of
mentioned #alues like as )(. C 01i. as well as *mpact on 9ill.
=2
):%:. 4utput 96I #P6E J 5CiE 9rap!+
*f user 1lick on !raph button I)(. C 01i.J following graph
representation will display.
):%:D 96I !elping FI"TS
$elping $ints is #ery important feature of our .nergy consumption
1alculator. *t will guide user or 3dministrator to input proper #alues.
3bo#e graphic symbol is represented for each input case and if user wants to
see what is &otal *& Load he "ust put mouse courser on the helping hint icon and
following guideline will display.
=3
CHAPTER 4
Development
=4
(:$ 5E=E84P-E"T I"TR456CTI4"
0e#elopment is a comple% issue, with many different and sometimes
contentious definitions. 3 basic perspecti#e e,uates de#elopment with economic
growth. &he (nited Dations 0e#elopment )rogram uses a more detailed definition7
according to them de#elopment is Eto lead long and healthy li#es, to be
knowledgeable, to ha#e access to the resources needed for a decent standard of li#ing
and to be able to participate in the life of the community.E
3chie#ing human de#elopment is linked to a third perspecti#e of de#elopment
which #iews it as freeing people from obstacles that affect their ability to de#elop
their own li#es and communities. 0e#elopment, therefore, is empowermentG it is
about local people taking control of their own li#es, e%pressing their own demands
and finding their own solutions to their problems.
(:' 5E=E84P-E"T P8A"
#ARCFITECT6RE 5IA9RA-+
3rchitecture diagrams display the organi4ation of architecture and their
elements, as well as corresponding namespaces. 3rchitecture diagrams are typically
used to depict the high7le#el organi4ation of a software pro"ect. 3rchitecture design
diagrams e%press the whole process of the system in the form of real life ob"ects and
components that are used in the software.
(:':' Arc!itecture 5esign 5iagram
Instructions1
=+
:oftware architecture is commonly defined in terms of structural elements and
relationships. :tructural elements are identified and assigned responsibilities that
client elements interact with through FcontractedF interfaces. :oftware architecture
must be distinguished from lower7le#el design -e.g., design of component internals
and algorithms2 and implementation, on the one hand, and other kinds of related
architectures, on the other.
6or instance, software architecture is not the information -or data2 model,
though it uses the information model to get type information for method signatures on
interfaces, for e%ample. *t is also not the architecture of the physical system, including
processors, networks, and the like, on which the software will run.
(:':& Arc!itecture 5esign 5iagram of Energy
Consumption Calculator1
=<
CHAPTER 5
Deployment
==
<:$ 5EP84>-E"T I"TR456CTI4"
&o deploy -from the 6rench #eplorer2 is Fto spread out or arrange
strategically.F Long used in the conte%t of military strategy, it has now gained
currency in information technology. *n its *& conte%t, deployment encompasses all the
processes in#ol#ed in getting new software or hardware up and running properly in its
en#ironment, including installation, configuration, running, testing, and making
necessary changes. &he word implementation is sometimes used to mean the same
thing.
<:' 5EP84>-E"T P8A"
<:':' 5eployment Plan/5eployment
5iagram Instructions
&he deployment diagram specifies a set of constructs that can be used
to define the e%ecution architecture of systems that represent the assignment
of software artifacts to nodes. Dodes are connected through communication
paths to create network systems of arbitrary comple%ity.
Dodes are typically defined in a nested manner, and represent either
hardware de#ices or software e%ecution en#ironments. 3rtifacts represent
concrete elements in the physical world that are the result of a de#elopment
=?
process. 0eployment diagrams show a systemEs physical layout, re#ealing
which pieces of software run on what pieces of hardware.
<:':& Arc!itecture 5esign 5iagram of
Energy Consumption Calculator1
=>
REFERENCES
.nergy 1onsumption 1alculator basic concepts
httpG//www.42u.com/efficiency/energy7efficiency7calculator.htm
)(./01i. basic concepts
httpG//www.42u.com/measurement/pue7dcie.htm
1alculating &otal )ower Ae,uirements for 0ata 1enters -by Aichard L. :awyer2
www.apcmedia.com/salestools/'3'A7+&0&.6TA1T.D.pdf
)hysical working concepts of .nergy 1onsumption 1alculator
httpG//www.apcmedia.com/salestools/&OL7=1@!)LTA3T.D.swf
!(* concepts of .nergy 1onsumption 1alculator
httpG//www.apcmedia.com/salestools/&OL7=9<:61TA0T.D.swf
0esign )hase 1oncepts
www.smartdraw.com
0esign )hase 1oncepts
httpG//www.edrawsoft.com/(@L70iagrams.php
ork )lan guidance
httpG//www.mhhe.com/mayfieldpub/tsw/workplan.htm
?0
?1