Final Project Report

Energy Consumption Calculator

Project Supervisor
Adnan Asif
Submitted By
F11CS61993648
Kashif Nadeem mc090201436
Muhammad Bilal mc090200972
Software Projects Researc! Section"
#epartment of Computer Sciences"
$irtual %ni&ersity of Pa'istan
CER()F)C*(E
This is to certify that Kashif Nadeem (mc09020143!" #uhammad Bi$a$
(mc0902009%2! have worked on and completed their Software Project at Software &
Research Projects Section, Department of Computer Sciences, Virtual niversity of
Pakistan in partial fulfillment of the re!uirement for the de"ree of #S in Computer
Sciences under my "uidance and supervision$
%n our opinion, it is satisfactory and up to the mark and therefore fulfills the
re!uirements of #S in Computer Sciences$
Supervisor & '(ter(a$ )*ami(er
+d(a( +sif
Supervisor,
Software Projects & Research Section,
Department of Computer Sciences
Virtual niversity of Pakistan
&&&&&&&&&&&&&&&&&&&
'Si"nature(
)*ter(a$ )*ami(er&Subject Specia$ist
))*+ternal Supervisor ,ame--
&&&&&&&&&&&&&&&&&&&
'Si"nature(
+ccepted By,
-------------
'.or office use(
E+,R#)%-
11
In the name of Allah, the Compassionate, the Merciful.
Praise be to Allah, Lord of Creation,
The Compassionate, the Merciful,
King of Judgmentda!"
#ou alone $e $orship, and to #ou alone $e pra! for help,
%uide us to the straight path
The path of those $ho #ou ha&e fa&ored,
'ot of those $ho ha&e incurred #our $rath,
'or of those $ho ha&e gone astra!.
1(
#E#)C*(),.
(o ,ur Parent
Than) !ou !our unconditional support $ith our studies and our efforts.
*e are honored to ha&e !ou as our parents.
Than) !ou for gi&ing us a chance to pro&e and impro&e oursel&es through all
our $al)s of life.
1+
*C/.,01E#2E-E.(

1,
$e o$e a great man! than)s to a great man! people $ho helped
and supported me during the $riting of this boo). -ur deepest
than)s to Lecturer,
*#.*. *S)F"
*ho %uides me in the pro.ect for lead and correcting &arious
documents of mine $ith attention and care. /e has ta)en pain to go
through the pro.ect and ma)e necessar! correction as and $hen
needed. *e e0press our than)s to the all people for e0tending their
support. Than)s and appreciation to the helpful people at 1irtual
2ni&ersit! Pro.ect Team, for their support .*e $ould also than)
our Institution and our facult! members $ithout $hom this pro.ect
$ould ha&e been a distant realit!. *e also e0tend our heartfelt
than)s to our famil! and $ell $ishers.
PREF*CE
13
This calculator brings the e0penses to light and also 4uantifies
the sa&ing possible. -ur hope is that based on the four pieces of readil!
a&ailable data !ou can enter in this calculator 5current and desired
P2678Ci6, IT load, and cost per )*h9, it $ill help the parties
appreciate the &alue of their efficienc! efforts. After ta)ing the user
desired inputs this calculator $ill calculate all sa&ings including ser&er
energ! sa&ings after &irtuali:ation, no. of rac)s in ;age sa&ings, total IT
load and total data center po$er sa&ing per !ears.
<inall! calculate the bill amount in the case of pre&irtuali:ation
and post &irtuali:ation. 6nerg! consumption calculator $ill calculate
both P26 7 8Ci6 according to their specifications. As $e )no$ that
P26 is defined as the ratio of total po$er to run the data center facilit!
to the total po$er dra$n b! all IT e4uipment.
6nerg! consumption calculator pro&ides a feature of current
energ! le&el sliding bar to enter !our data center=s current P26 5Po$er
2sage 6ffecti&eness978Ci6 58ata Center Infrastructure 6fficienc!9.
>oth are $idel! used and accepted as $ell as adopted benchmar)s for
efficienc! in data centers. 2ser can enter his current IT center load and
Total data center 6lectricit! capacit!.
(*31E ,F C,.(E.(S
C4*P(ER .,5 1
2*(4ER).2 *.*167).2 ).F,5555555555555555555555555555555555555555555555555555555555555555555555555581
151 )ntro9uction :::::::::::::::::: 88
158 Purpose :::::::::::::::::: 83
153 Scope :::::::::::::::::: 83
1.+.1 6CC ?cope @@@@@@@@@@@@@@@ (,
1.+.( Current 6nerg! Le&el7Input @@@@@@@@@ (3
1.+.+ Current 6nerg! -utput @@@@@@@@@ (3
1.+., P2678Ci6 @@@@@@@@@@@@@@@ (3
1.+.3 6nerg! ?a&ing 5Per !ear9 @@@@@@@@@ (A
154 #efinitions an9 a;;re&iations ::::::::: 8<
1.,.1 8efinitions @@@@@@@@@@@@@@@ (B
1.,.( Abbre&iations @@@@@@@@@@@@@@@ (C
15= %se case an9 usage scenarios ::::::::: 8<

1.3.1 2se case 8iagram @@@@@@@@@@@@ +D
1.3.( 2sage scenarios @@@@@@@@@@@@ +D
1.3.(.1 Administrator entered the total capacit! of data center @ +D
1.3.(.( Administrator entered the total IT Load @@ +1
1.3.(.+ Cost per )* @@@@@@@@@@@@ +(
1.3.(., 1irtuali:ed IT e4uipment @@@@@@ ++
1.3.(.3 %raph representation of data @@@@@@ ++
1.3.(.A Po$er 2sage 6ffecti&eness 5P269 Calculation @ +,
1.3.(.B 8ata Center Infrastructure 6fficienc! 58Ci69 Calculation +3
1.3.(.E 6nerg! sa&ings Calculation @@@@@@ +3
1A
156 Supplementary re>uirements ::::::::: 36
1.A.1 2sabilit! @@@@@@@@@@@@@@@ +B
1.A.( Performance @@@@@@@@@@@@@@@ +B
1.A.+ ?upportabilit! @@@@@@@@@@@@@@@ +B
C4*P(ER .,5 8
P1*..).2 (4E PR,?EC(5555555555555555555555555555555555555555555555555555555555555555555555555555555555555555538
851 )ntro9uction :::::::::::::::::: 39
(.1.1 Planning phase @@@@@@@@@@@@ +C
(.1.( -b.ecti&es of Planning Phase for 6CC @@@ ,D
(.1.+ %oals of Planning Phase for 6CC @@@ ,D
858 -et!o9ologies ::::::::::::: 4@
853 *&aila;le -et!o9ologies ::::::::::::: 4@
(.+.1 *aterfall Method @@@@@@@@@@@@@ ,1
(.+.( Incremental Process Models @@@@@@@@@@ ,(
(.+.+ 6&olutionar! Process Models @@@@@@@@@@ ,,
(.+.+.1 Protot!ping @@@@@@@@@@@@@ ,,
(.+.+.( The ?piral Model @@@@@@@@@@ ,3
(.+., Agile soft$are de&elopment Model @@@@@@@ ,A
(.+.,.1 Characteristics @@@@@@@@@@ ,A
(.+.3 ?crum 8e&elopment Model @@@@@@@@@@ ,B
(.+.3.1 Characteristics@@@@@@@@@@@@@ ,B
(.+.A 1 Model @@@@@@@@@@@@@@@@ ,E
854 *9opte9 -et!o9ologies ::::::::::::: 48
(.,.1 *aterfall Process Model @@@@@@@@@@ ,C
(.,.1.1 8efinition ?tud!7Anal!sis7Fe4uirements @ 3D
(.,.1.( >asic 8esign7?pecification Phase @@@@ 3D
(.,.1.+ Technical 8esign78etailed 8esign @@@@ 3D
1B
(.,.1., Construction7Implementation @@@@ 3D
(.,.1.3 Testing @@@@@@@@@@@@@ 3D
(.,.1.A Integration @@@@@@@@@@@@... 31
(.,.1.B Maintenance and management @@@... 31
85= Reasons for c!oosing met!o9ology :::::::::: =1
856 0or' Plan ::::::::::::::::::: =8
(.A.1 *or) Plan definition @@@@@@@@@@@@... 3(
(.A.( Importance in ?oft$are 6ngineering @@@@@@@ 3+
85< Project Structure :::::::::::::::: =4
(.B.1 Team ?tructure @@@@@@@@@@@@@ 3,
(.B.( Pro.ect ?chedule 5?ubmission Calendar9 @@@@ 3,
C4*P(ER .,5 3
#ES)2.).2 (4E PR,?EC(555555555555555555555555555555555555555555555555555555555555555555555555555555555555555=6
351 )ntro9uction ::::::::::::::::::: =<
+.1.1 6CC Anal!sis @@@@@@@@@@@@@@@@ 3B
+.1.( Anal!sis needs @@@@@@@@@@@@@ 3E
+.1.+ <easibilit! ?tud! @@@@@@@@@@@@@ 3E
+.1., 8ata %athering @@@@@@@@@@@@@ 3E
+.1.,.1 *riting 8ocuments @@@@@@@@@@ 3E
+.1.,.( Inter&ie$s @@@@@@@@@@@@@ 3E
+.1.,.+ Guestionnaires @@@@@@@@@@ 3C
+.1.,., -bser&ations @@@@@@@@@@@@@ 3C
+.1.,.3 ?ampling @@@@@@@@@@@@@ 3C
+.1.,.A 8ata Anal!sis @@@@@@@@@@@@@ 3C
+.1.,.B Anal!sis report @@@@@@@@@@ AD
+.1.3 Introduction to design phase @@@@@@@@@@ AD
358 Purpose ::::::::::::::::::: 61
353 Scope ::::::::::::::::::: 68
354 *rc!itectural representation :::::::::: 63
+.,.1 Architecture design diagram definition @@@@ A+
+.,.( Architecture design diagram instructions @@@@ A,
+.,.+ Architecture design diagram @@@@@@@@@@ A,
1E
35= #ynamic mo9eling Ase>uence 9iagramB ::::::: 6=
+.3.1 ?e4uence diagram definition @@@@@@@ A,
+.3.( ?e4uence diagram instructions @@@@@@@ A3
+.3.+ ?e4uence diagram 56CC9 @@@@@@@@@.... AA
+.3., ?e4uence diagram of P26 and 8Ci6 Calculation @ AA
+.3.3 >ill and energ! sa&ing calculation @@@@@@@ AB
+.3.A %raphical representation @@@@@@@ AB
356 ,;jectC1ogical mo9el AClass 9iagramB ::::::: 68
+.A.1 Class diagram definition @@@@@@@@@@ AE
+.A.( Class diagram of 6CC @@@@@@@@@@ AE
35< #eployment -o9el :::::::::::::::55 69
+.B.1 8eplo!ment diagram definition @@@@@@.. AC
+.B.( 8eplo!ment diagram of 6CC @@@@@@.. AC
358 #ata;ase -o9el A#ata;ase #iagramB ::::::55 <@
+.E.1 8atabase 8iagram definition @@@@@@.. BD
+.E.( 8atabase 8iagram of 6CC @@@@@@.. BD
359 2rap!ical %ser )nterface ::::::::::::55 <1
+.C.1 Interface diagram definition @@@@@@.. B1
+.C.( Interface design of 6CC @@@@@@@@@.. B1
+.C.+ Input %2I 5Pre1irtuali:ation9 @@@@@@.. B(
+.C., Input %2I 5Post1irtuali:ation9 @@@@@@.. B(
+.C.3 -utput %2I 5Fesults9 @@@@@@@@@.. B(
+.C.A -utput %2I 5%raphical representation9 @@@.. B+
+.C.B -utput %2I 5P26 H 8Ci6 %raph9 @@@@@@.. B+
+.C.E %2I helping /I'T? @@@@@@@@@.. B,
C4*P(ER .,54
#E$E1,P-E.(555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555<=
,.1 8e&elopment Introduction @@@@@@@@@@@@.. BA
,.( 8e&elopment plan Architecture diagram @@@@@. BA
,.(.1 Architecture design diagram instructions ...@@@@.. BA
,.(.( Architecture design diagram of 6CC @@@@@. BB
1C

C4*P(ER .,5=
#EP1,6-E.(555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555<8
3.1 8eplo!ment Introduction @@@@@@@@@@@@@@ BC
3.( 8eplo!ment plan @@@@@@@@@@@@@@ BC
3.(.1 8eplo!ment t plan instruction @@@@@@@@ BC
3.(.( 8eplo!ment plan of 6CC @@@@@@@@ ED
REFERE.CES555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555581
(D
C4*P(ER 1
%athering H Anal!:ing Info
(1
151 ).(R,#%C(),.
8ata gathering 5some time called primaril! in&estigation9 is &er! important
part of this document because all future $or) $ill be done on the basis of this data
gathering. All rele&ant information searched and colleted form different sources to
co&er up the tas). 8uring this phase research is being conducted $hich includes
brainstorming about the soft$are, $hat it is going to be and $hat purpose is it going
to fulfill. 2nless !ou )no$ $hat !ou are going to design, !ou cannot approach the
problem. /ere, the specifications of the output or the final product are studied and
mar)ed. If the soft$are that is going to be designed should not contain certain
features, for reasons li)e securit!, then it is also mentioned in this stage. Problems are
defined and understand in this phase.
An attracti&e, informati&e, and userfriendl! report can be used as outreach
material to inform the public about pro.ects ta)ing place in their $atershed and can
help to gain $idespread support for these and future pro.ects. A short fact sheet or
brochure that includes information from the report can help to spread the $ord about
the pro.ect.
The <inal Pro.ect Feport refers to finali:e the pro.ect, $hich includes basic
gathering and anal!:ing information, planning and method that are used to establish
or adopted to de&elop 6nerg! Consumption Calculator, de&elopment $hich include
all logical designing phases and deplo!ment $hich indicates the structural process of
6nerg! Consumption Calculator. The introduction should contain bac)ground
information on the pro.ect, including the pro.ect area.
158 P%RP,SE
((
The purpose of this document is to present a detailed description of the
6nerg! Consumption Calculator. It $ill e0plain features of the 6CC, the interfaces of
the 6CC, $hat the 6CC $ill do, the constraints under $hich it must operate and ho$
the 6CC $ill react to e0ternal stimuli. In the final pro.ect report all documents are
re&isited and e0plained in detailed.
Feports communicate information $hich has been compiled as a result of
research and anal!sis of data and of issues. Feports can co&er a $ide range of topics,
but usuall! focus on transmitting information $ith a clear purpose, to a specific
audience. %ood reports are documents that are accurate, ob.ecti&e and complete. The!
should also be $ell$ritten, clearl! structured and e0pressed in a $a! that holds the
readerIs attention and meets their e0pectations. The true &alue of the research ma! be
assessed through a report since the $ritten report ma! be the Jonl! tangible product
of hundreds of hours of $or). -ften reports are structured in a $a! that reflects the
information finding process and the $riting up of the findingsK that is, summar! of the
contents, introduction or bac)ground, methods, results, discussion, conclusion and7or
recommendations. The inclusion of recommendations is one reason $h! reports are a
common form of $riting in industr!, as the informed recommendations are useful for
decision ma)ing.
In this report, all functional characteristics of 6nerg! Consumption Calculator
$ill be discussed in detailed. It is &er! important that this report co&er all necessar!
aspects of 6nerg! Consumption Calculator.
153 SC,PE
>efore entering in the topic of the scope of the 6nerg! Consumption
Calculator let us start from the basic concept of, $hat is the pro.ect scope meanL
Actuall! pro.ect scope is the $or) that needs to be accomplished to deli&er a product,
ser&ice or result $ith the specified features and function. ?cope pla!s an important
role in pro.ects. It is the first step $hile $riting ?F? documents.
In 6nerg! Consumption Calculator scope includes the e0pected $or) effort
and results and it must be documented and accepted before the pro.ect begins. It is a
(+
challenging .ob for the soft$are de&eloper to $rite accurate ?F? document to e0press
under de&eloping soft$are. >ecause $e )no$ that all pro.ects are defined b! their
goals, ob.ecti&es, boundaries and constraints. %etting a detailed but clear picture of
our pro.ect scope $ill put us to$ard completing the pro.ect successfull!.
15351 ECC Scope
6nerg! use is a central issue for the data centers. Po$er dra$ for data centers
ranges from a fe$ )* for a rac) of ser&ers in a closet to se&eral tens of M* for large
facilities. 6nerg! Consumption Calculator helps IT professionals and CLe&el
management understand the short term and the long term sa&ings that can be achie&ed
b! impro&ing the energ! efficienc! of there data center infrastructure. <or energ!
sa&ing, different tools and application are a&ailable that compute o&erall energ!
consumption and manage all calculation to displa! the efficienc! and sa&ings. <or
this purpose $e are designing a des)top application $ith named M6nerg!
Consumption CalculatorN, $hich $ill help the data centers to sa&e energ! and o&erall
cost !earl! basics or monthl! basics. This soft$are can be used for small data centers
as $ell as large data centers and it $ill help the data centers to reduce their electricit!
cost.
The scope of this pro.ect $ill broadl! co&er the 6nerg! consumption calculator
features a&ailable in this pro.ect. The features co&ered in this calculator $ill enable to
administrator to calculate Total Load a&ailable to IT e4uipment details i.e. ?er&ers,
'et$or)ing 64uipment, and 6n&ironment Control 64uipment. The goal of this
pro.ect is to calculate total 6nerg! 2sed b! IT 64uipment.
This $ill also help to Total 6lectricit! Cost calculation 5per month or !earl!
basis9 H 6nerg! sa&ing b! &irtuali:ation. %raphics Fepresentation of Po$er 2sage
6ffecti&eness 5P269 H 8ata Center Infrastructure 6fficienc! 58CI69 $ill add that
$ill reflect the impact of energ!. >ased upon this information this $ill enable to
administrator to ma)e comparison of energ! sa&ing.
15358 Current Energy 1e&elC)nput
(,
6nerg! consumption calculator pro&ides a feature of current energ! le&el sliding
bar to enter !our data center=s current P26 5Po$er 2sage 6ffecti&eness978Ci6 58ata
Center Infrastructure 6fficienc!9. >oth are $idel! used and accepted as $ell as
adopted benchmar)s for efficienc! in data centers. 2ser can enter his current IT
center load and Total data center 6lectricit! capacit!. 2ser also able to mention
electricit! cost per )* to calculate the result.
15353 Current Energy ,utputC*nnual #ata Center Efficiency Sa&ing
This calculator brings the e0penses to light and also 4uantifies the sa&ing
possible. -ur hope is that based on the four pieces of readil! a&ailable data !ou can
enter in this calculator 5current and desired P2678Ci6, IT load, and cost per )*h9, it
$ill help the parties appreciate the &alue of their efficienc! efforts. After ta)ing the
user desired inputs this calculator $ill calculate all sa&ings including ser&er energ!
sa&ings after &irtuali:ation, no. of rac)s in ;age sa&ings, total IT load and total data
center po$er sa&ing per !ears. <inall! calculate the bill amount in the case of pre
&irtuali:ation and post &irtuali:ation.

15354 P%EC#C)E
6nerg! consumption calculator $ill calculate both P26 7 8Ci6 according to
their specifications. As $e )no$ that P26 is defined as the ratio of total po$er to run
the data center facilit! to the total po$er dra$n b! all IT e4uipment.


Total Facility Power
PUE
IT Equipment Power
=
fig. 1.1
An a&erage data center has a P26 of (.DO ho$e&er se&eral super efficient data
centers ha&e )no$n to achie&e a P26 as lo$ as 1.1.
As $e )no$ that 8Ci6 is defined as the ratio of total po$er dra$n b! all IT
e4uipment to the total po$er to run the data center facilit! or $e can sa! that it is the in&erse
of P26.
Stan9ar9 2oo9 3etter
(.D 1., 1.1
(3
1

IT Equipment Power
DCiE
Total Facility Power PUE
= =
fig. 1.2
1535= Energy Sa&ings Aper yearB
1irtuali:ed en&ironments can also result in dramaticall! lo$ered energ!
consumption. 'ot onl! is the number of ph!sical ser&ers dramaticall! lo$ered, but the
soft$are can monitor host resource utili:ation based on predefined thresholds. 6nerg!
consumption calculator $ill help the user to find out the all efficienc! cost sa&ings. *hile
ta)ing the inputs as total capacit! of facilit!, IT e4uipment load and cost per )*, our
calculator pro&ide 4uic) solutions and results that $ill displa! in the form of numeric
calculations and graphs representation.
1., #EF).)(),.S *.# *33RE$)*(),.S
15451 #EF).)(),.S
8efinitions are )e!$ord used in this document. It is important to define all important
term and )e!$ord used in this document. It $ill help the reader to understand in effecti&e
$a!. All $ords and term $hich $e used during our pro.ect documentations are discussed
belo$.
KEYWORDS DEFINITIONS
Scope ?cope is the $or) that needs to be accomplished to deli&er a
product, ser&ice or result $ith the specified features and function.
Power %sage
Effecti&eness
P26 is defined as the ratio of total po$er to run the data center
facilit! to the total po$er dra$n b! all IT e4uipment.
#ata Center
)nfrastructure
Efficiency
8Ci6 is defined as the ratio of total po$er dra$n b! all IT
e4uipment to the total po$er to run the data center facilit! or $e
can sa! that it is the in&erse of P26.
Software re>uirements A specification of an e0ternall! obser&able beha&ior of the
s!stemO for e0ample, inputs to the s!stem, outputs from the
s!stem, functions of the s!stem, attributes of the s!stem, or
attributes of the s!stem en&ironment.
Functional
Re>uirement
<unctional re4uirement bringin the s!stem=s &ie$ and define
from the s!stem=s perspecti&e the soft$are functionalit! the
Stan9ar9 2oo9 3etter
D.3 D.B D.C
(A
de&elopers must build into the product to enable users to
accomplish their tas)s stated in the user re4uirements thereb!
satisf!ing the business re4uirements.
.on Functional
re>uirement
'on<unctional re4uirements tend to identif! MuserN constraints
and Ms!stemN constraints.
$irtualiDation
Virtuali/ation in computin" is the creation of a virtual 'rather than actual(
version of somethin", such as a hardware platform, operatin" system,
stora"e device, or network resources$
%se Case #iagram A use case is a functionalit! the user needs from the s!stem. A use
case diagram depicts the relationship among the actors and use
cases.
*9ministrator A person $hich control or maintain the calculation process, it is
said to be a user.
%sage scenario
A usage scenario is li)el! to ha&e &arious sections depending
upon the le&el of details re4uired in a gi&en s!stem.
0or' plan
A $or) 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 $or), and defines the
4ualit! assurance for the program.
#ata Flow #iagram
A t$odimensional diagram, $hich e0plains ho$ data is
processed and transferred in a s!stem, is called Data Flow
Diagram.
Entity Relations!ip
#iagram
6ntit! Felationship 8iagram is an abstract and conceptual
representation of data.
*cti&ity 9iagram An acti&it! diagram illustrates the d!namic nature of a s!stem b!
modeling the flo$ of control from acti&it! to acti&it!
Se>uence 9iagram A se4uence diagram is a t!pe of interaction diagram that
highlights the interdependencies bet$een messages.
*rc!itecture 9iagrams Architecture diagrams displa! the organi:ation of architecture and
their elements, as $ell as corresponding namespaces.
Class 9iagram The class diagram is the main building bloc) of ob.ect
oriented modeling.
#ata;ase 9esign 8atabase design is the process of producing a detailed data
model of a database. This logical data model contains all the
needed logical and ph!sical design choices and ph!sical storage
parameters needed to generate a design in a 8ata 8efinition
Language, $hich can then be used to create a database
)nterface #esign An interface enables a user to interact $ith a s!stem to perform a
tas). Interface design has &er! important role in soft$are
(B
engineering.
#eployment 9iagram The deplo!ment diagram specifies a set of constructs that can be
used to define the e0ecution architecture of s!stems that represent
the assignment of soft$are artifacts to nodes.
(est case A test case in soft$are engineering is a set of conditions or
&ariables under $hich a tester $ill determine $hether
an application or soft$are s!stem is $or)ing correctl! or not.
%sa;ility 6ffort re4uired to learn, operate, prepare input, and interpret
output of a program
PerformanceCEfficiency The amount of computing resources re4uired b! a program to
perform its function.
Supporta;ility 6ffort re4uired to modif! or supportabilit! an operational
program.
System ;oun9ary This internal s!stem functional area of use case diagram is called
Ms!stem boundar!N.
0aterfall -o9el It suggests a s!stematic, se4uential approach to the soft$are
de&elopment that begins $ith customer specification of
re4uirements and progresses through planning, modeling,
construction, and deplo!ment.
)ncremental Process
-o9els
It combines elements of linear and parallel process flo$s. The
incremental model applies linear se4uences in staggered fashion
as calendar time processes
Spiral -o9el It is an e&olutionar! soft$are process model that couples the
iterati&e nature of protot!ping $ith the controlled and s!stematic
aspects of the $aterfall model.
*gile 9e&elopment
-o9el
It promotes adapti&e planning, e&olutionar! de&elopment and
deli&er!, a timebo0ed iterati&e approach, and encourages rapid
and fle0ible response to change.
Scrum #e&elopment
-o9el
?crum is an iterati&e, incremental frame$or) for pro.ect
management often seen in agile soft$are de&elopment, a t!pe of
soft$are engineering.
15458 *33R)$)*(),.S
(E
*;;re&iations Stan9s for
ECC 6nerg! Consumption Calculator
)( Information Technolog!
P%E Po$er 2sage 6ffecti&eness
#C)E 8ata Center Infrastructure 6fficienc!
SRS ?oft$are Fe4uirement ?pecifications
'0! Kilo *att /our
$- 1irtual Machine
%C# 2se Case 8iagram
-0P Methodolog! and *or) Plan
P-P Pro.ect Management Phase
## 8esign 8ocument
#F# 8ata <lo$ 8iagram
ER# 6ntit! Felationship 8iagram
*# Acti&it! 8iagram
S## ?e4uence 8iagram 8efinition
*## Architectural 8esign 8iagram
C# Class 8iagram
### 8atabase 8esign 8iagram
)## Interface 8esign 8iagram
2%) %raphical 2ser Interface
(C Test Case
(C( Test Case Title
15= %SE C*SE *.# %S*2E SCE.*R),S
A use case is a functionalit! the user needs from the s!stem. A 2C8 depicts
the relationship among the actors and use cases. Actors represent e0ternal entities of
the s!stem. These can be people or things, such as e0ternal hard$are that interact
$ith s!stem.
15=51 %SE C*SE #)*2R*-
In our 6nerg! Consumption Calculator $e are going to use an actor named
MAdministratorN. All functionalit! that this calculator performed is based on the
administrator because he $ill pro&ide e0ternal input and after that final calculation is
performed b! the internal s!stem of the calculator. This internal s!stem functional
area is called Ms!stem boundar!N.
(C

15=58 %S*2E SCE.*R),SE
2sage scenario is the actual te0tbased representation of the use case, among
&arious representation methods discussed abo&e. A usage scenario is li)el! to ha&e
&arious sections depending upon the le&el of details re4uired in a gi&en s!stem.
15=5851 *9ministrator entere9 t!e total capacity of 9ata centerE
%se Case (itle Enter (otal Capacity of #ata center
*;;re&iate9
(itle
%se Case )9 +.1.1
Re>uirement )9 1
#escriptionE This case is used to ta)e input of total capacit! 5in )*9 of the data center.
6&er! data center has it o$n 6lectricit! capacit! that is $ritten in the input te0t field
$ith name 8ata Center Capacit! 5in )*9, because all calculation $ill be carr! on $ith
this &alue
Pre Con9itionsE Administrator $ill open the soft$are and it is important to input &alues
as total data center capacit! to ma)e calculations. The default &alue $ill be set to 1DDD
)*.
(as' Se>uence EFceptions
1. Administrator input the &alue.
(. Administrator able to input numerical &alue
+. ?!stem $ill response $hen e&er user change the &alues
Post Con9itionsE Total 8ata center capacit! is entered and corresponding result $ill
displa!.
%nresol&e9 issuesE
+D
*ut!orityE Administrator
-o9ification !istoryE 1.D
*ut!orE <11C?A1CC+A,E
#escriptionE
15=5858 *9ministrator entere9 t!e total )( 1oa9E
%se Case (itle Enter (otal )( 1oa9
*;;re&iate9
(itle
%se Case )9 +.1.(
Re>uirement )9 (
#escriptionE This case is used to ta)e input of total IT Load 5in )*9 of the data center.
Administrator entered the Total IT Load that it includes all ser&er, rac)s and all
e4uipments used in IT.
Pre Con9itionsE Administrator $ill open the soft$are and it is important to input &alues
as total data center capacit! to ma)e calculations. The default &alue $ill be set to 1DDD
)*.
(as' Se>uence EFceptions
1. Administrator input the &alue.
(. Administrator able to input numerical &alue
+. ?!stem $ill response $hen e&er user change the &alues
Post Con9itionsE Total IT Load is entered and corresponding result $ill displa!.
%nresol&e9 issuesE
*ut!orityE Administrator
-o9ification !istoryE 1.D
*ut!orE <11C?A1CC+A,E
#escriptionE
15=5853 Costs per '0E
%se Case (itle Cost per '0
*;;re&iate9
(itle
%se Case )9 +.1.+
Re>uirement )9 +
#escriptionE In this case administrator $ill input the cost per )*. It is important &alue.
An! administrator can input his o$n cost per )* amount in Fs.
Pre Con9itionsE Administrator $ill pro&ide the amount of cost per )* because it is the
feature and results $ill occur on the basics of that &alue.
(as' Se>uence EFceptions
+1
1. Administrator $ill pro&ide the re4uired such cost &alue that is
charged in his data center.
(. ?!stem $ill response $hen e&er user change the &alues
Post Con9itionsE Total cost per )* $ill be added
%nresol&e9 issuesE
*ut!orityE Administrator
-o9ification !istoryE 1.D
*ut!orE <11C?A1CC+A,E
#escriptionE
15=5854 $irtualiDe9 )( e>uipmentE
%se Case (itle $irtualiDe9 )( e>uipment
*;;re&iate9
(itle
%se Case )9 +.1.,
Re>uirement )9 ,
#escriptionE This case is used to ta)e input from the administrator as ho$ man! IT
e4uipment he $ant to &irtuali:ed. This &alue must be in the form of percentage.
Pre Con9itionsE Administrator $ill pro&ide the amount of IT e4uipment $hich he
$ants to &irtuali:ed because it is the feature and results $ill occur on the basics of that
&alue.
(as' Se>uence EFceptions
1. Administrator find out the no. of IT e4uipment that he $ant to
&irtuali:es.
(. Administrator enter the percentage of IT e4uipment that used in
data centers.
+. ?!stem $ill response $hen e&er user change the &alues
Post Con9itionsE Total data center=s &irtuali:ed IT e4uipment $ill be added
%nresol&e9 issuesE
*ut!orityE Administrator
-o9ification !istoryE 1.D
*ut!orE <11C?A1CC+A,E
#escriptionE
15=585= 2rap! representation of 9ataE
%se Case (itle 2rap! representation of 9ata
*;;re&iate9
(itle
+(
%se Case )9 +.1.3
Re>uirement )9 3
#escriptionE This case is used to displa! the graphical representation of results li)e as
P26, 8Ci6, etc.
Pre Con9itionsE ?!stem $ill ta)e the resulted &alue of P26 and 8Ci6 to represent
efficienc! and !earl! bill efficienc!.
(as' Se>uence EFceptions
1. ?!stem ta)es resulted &alue of P26.
(. ?!stem ta)e resulted &alue of 8Ci6.
+. ?!stem $ill ta)e the resulted amount of bill before and after
&irtuali:ation.
,. ?!stem $ill response $hen e&er user change the &alues
3. ?!stem $ill displa! the final graph of abo&e acti&ities.
Post Con9itionsE %raphical representation $ill displa! in graph..
%nresol&e9 issuesE
*ut!orityE ?!stem
-o9ification !istoryE 1.D
*ut!orE <11C?A1CC+A,E
#escriptionE
15=5856 Power %sage Effecti&eness AP%EB CalculationE
%se Case (itle Power %sage Effecti&eness Calculation
*;;re&iate9
(itle
P%E APower %sage Effecti&enessB
%se Case )9 +.1.A
Re>uirement )9 A
#escriptionE This case is used to calculate the P26 $ith formula as it is e4ual to The
total data center capacit! is di&ided to the total IT e4uipment load. It better efficienc!
le&el is (.D
Pre Con9itionsE ?!stem $ill ta)e the total capacit! of data center and total Load of IT
e4uipment to calculate P26.
(as' Se>uence EFceptions
1. ?!stem ta)e input as Total data center capacit!.
(. ?!stem ta)es input as Total IT e4uipment load.
+. ?!stem $ill calculate the amount of P26.
,. ?!stem $ill response $hen e&er user change the &alues
Post Con9itionsE P26 5Po$er 2sage 6ffecti&eness9 $ill be calculated.
%nresol&e9 issuesE
*ut!orityE ?!stem
-o9ification !istoryE 1.D
*ut!orE <11C?A1CC+A,E
#escriptionE
++
15=585< #ata Center )nfrastructure Efficiency A#CiEB CalculationE
%se Case (itle #ata Center )nfrastructure Efficiency Calculation
*;;re&iate9
(itle
#CiE A#ata Center )nfrastructure EfficiencyB
%se Case )9 +.1.B
Re>uirement )9 B
#escriptionE This case is used to calculate the 8Ci6 $ith formula as it is e4ual to The
total IT e4uipment load is di&ided to the total data center capacit!. It better efficienc!
le&el is D.3
Pre Con9itionsE ?!stem $ill ta)e total Load of IT e4uipment and the total capacit! of
data center to calculate 8Ci6.
(as' Se>uence EFceptions
1. ?!stem ta)es input as Total IT e4uipment load.
(. ?!stem ta)e input as Total data center capacit!.
+. ?!stem $ill calculate the amount of 8Ci6.
,. ?!stem $ill response $hen e&er user change the &alues
Post Con9itionsE 8Ci6 58ata Center Infrastructure 6fficienc!9 $ill be calculated.
%nresol&e9 issuesE
*ut!orityE ?!stem
-o9ification !istoryE 1.D
*ut!orE <11C?A1CC+A,E
#escriptionE
15=5858 Energy sa&ings CalculationE
%se Case (itle Energy Sa&ing Calculation
*;;re&iate9
(itle
%se Case )9 +.1.E
Re>uirement )9 E
#escriptionE This case is used to calculate the 6nerg! sa&ings $ith formulas on the
basics of cost per )*.
Pre Con9itionsE ?!stem $ill ta)e cost per )* and total used energ! in IT before and
after It e4uipment &irtuali:ation.
(as' Se>uence EFceptions
1. ?!stem ta)es input as Total IT e4uipment load.
(. ?!stem ta)es input as Total data center capacit!.
+. ?!stem ta)es input as cost per )*.
,. ?!stem calculates the energ! sa&ings.
3. ?!stem $ill response $hen e&er user change the &alues
Post Con9itionsE Total 6nerg! sa&ings $ill be calculated.
%nresol&e9 issuesE
+,
*ut!orityE ?!stem
-o9ification !istoryE 1.D
*ut!orE <11C?A1CC+A,E
#escriptionE
156 S%PP1E-E.(*R6 REG%)RE-E.(S
?upplementar! re4uirements tend to identif! MuserN constraints and
Ms!stemN constraints. >usiness re4uirements should be )ept pure and not reflect an!
solution thin)ing. It is a document that describes all the ser&ices pro&ided b! the
s!stem along $ith the constraints under $hich it must operate. That is, the
re4uirement document should not onl! describe the functionalit! needed and
pro&ided b! the s!stem, but it must also specif! the constraints under $hich it must
operate. 'on functional re4uirement are difficult to testO therefore the! are usuall!
e&aluated sub.ecti&el!.
Constraints are restrictions that are placed on the choices a&ailable to the
de&eloper for design and construction of the soft$are product. These )inds of
re4uirements are called 'on<unctional Fe4uirements. These are used to describe
e0ternal s!stem interfaces, design and implementation constraints, 4ualit! and
performance attributes. These also include regulations, standards, and contracts to
$hich the product must conform.
?upplementar! re4uirement pla! a significant role in the de&elopment of the
s!stem. If not captured properl!, the s!stem ma! not fulfill some of the basic business
needs. If proper care is not ta)en, the s!stem ma! collapse. The! dictate ho$ the
s!stem architecture and frame$or).
15651 %sa;ilityE
?!stem must be eas! to use and learn. 'a&igation s!stem must be user
friendl!. Along $ith clic) buttons, shortcut )e!s should be pro&ided for simple
interaction $ith the s!stem.
15658 PerformanceE
+3
The accomplishment of a gi&en tas) measured against preset )no$n standards
of accurac!, completeness, cost, and speed. In 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.
15653 Supporta;ilityE
Code should be simple and easil! readable $ith proper comments $here need.
'aming con&entions should be according to the polic! of standards.

+A
C4*P(ER 8
Planning the Pro.ect
851 ).(R,#%C(),.
In the planning phase the purpose of this document is to present a detailed description
of e0isting methodologies, adopted methodolog! and reasons for choosing the methodolog!
+B
for the 6nerg! Consumption Calculator. It $ill e0plain features of the 6CC, the interfaces of
the 6CC, $hat the 6CC $ill do, the constraints under $hich it must operate and ho$ the
6CC $ill react to e0ternal stimuli.
85151 Planning P!aseE
>efore entering in the topic of the planning phase of the 6nerg! Consumption
Calculator let us start from the basic concept of, $hat is the pro.ect planning phase
meanL The Planning Phase focuses principall! on re4uired pro.ect planning $or).
Proper comprehensi&e pro.ect planning is essential to a successful IT pro.ect, and
incomplete pro.ect planning and anal!sis are fre4uentl! root causes of pro.ect failure.
Actuall! pro.ect planning is the $or) that needs to be accomplished to deli&er
a product, ser&ice or result $ith the specified features and function. Planning phase
pla!s an important role in pro.ects. It is the second step $hile $riting Planning phase
and methodolog! documents.
*ith planning, pro.ects can run on time and interact effecti&el! $ith both
customers and suppliers. 6&er!one in&ol&ed understands $hat is $anted and
emerging problems are seen 5and dealt $ith9 long before the! cause damage. If $e
$ant our pro.ects to run this $a! then $e must in&est time in planning.
85158 ,;jecti&es of Planning P!ase for ECCE
?uccessful completion of the Planning Phase should compriseK
Assessment and description of the procurement management strateg!.
6laboration and refinement of the pro.ect scope, schedule, ris)s, and costs.
8efinition of procedures for ho$ the pro.ect $ill be e0ecuted, monitored,
controlled, and closed.
Planning the future course of action.
Appro&al to progress to the Fe4uirements Anal!sis Phase
It must be fle0ible because it is updated $hene&er issue $ill arise regain the
e0ecution of the pro.ect.
85153 2oals of Planning P!ase for ECCE
+E
The purpose of the Planning Phase is to plan all pro.ect processes and acti&ities
re4uired to ensure pro.ect success and to create a comprehensi&e set of plans, )no$n as the
PMP, to manage the pro.ect from this phase until pro.ect termination.
858 -E(4,#,1,26
A s!stem of principles or rules from $hich specific methods or procedures ma! be
deri&ed to interpret or sol&e different problems $ithin the scope of a particular discipline.
2nli)e an algorithm, a methodolog! is not a formula but a set of practices.
To be fair, Jason ad&ocates the follo$ing definition of a methodolog!K
JA methodolog! is a set of guidelines or principles that can be tailored and applied to
a specific situation. In a pro.ect en&ironment, these guidelines might be a list of things to do.
A methodolog! could also be a specific approach, templates, forms, and e&en chec)lists used
o&er the pro.ect life c!cle.J
853 *$*)1*31E -E(4,#,1,2)ES
In the planning phase of 6nerg! consumption calculator, it is &er!
important to stud! the e0isting s!stem. Actuall! in this step, it is necessar! to ta)e
all preliminar! in&estigations of e0isting s!stem. There are man! calculators
a&ailable for calculating energ! consumption $ith a lot number of ad&antages but
it is noticed that all ha&e separate ad&antages. There $ill be soft$are that $ill
pro&ide all in one feature. In this regard 6nerg! consumption calculator is being
designed but before discussing m! o$n calculator=s specifications let us round up
the e0isting methodologies of e0isting energ! consumption calculators.
As much as 3D; of a data centerIs energ! bill is from infrastructure
5po$er H cooling e4uipment9. There are man! Interacti&e data center efficienc!
calculator $hich find out ho$ reducing P26 $ill result in significant energ! and
cost sa&ings"
Prescripti&e process models $ere originall! proposed to bring order to
the chaos of soft$are de&elopment. /istor! has indicated that these traditional
+C
models ha&e brought a certain amount of useful structure to soft$are engineering
$or) and ha&e pro&ided a reasonabl! effecti&e road map for soft$are teams.
All soft$are process models can accommodate the generic frame $or)
acti&ities. >ut each applies a different emphasis to these acti&ities and defines a
process flo$ that in&o)es each frame$or) acti&it! in the different manner.
85351 0aterfall -et!o9E
The $aterfall method, sometimes called the classic life c!cle, suggests a
s!stematic, se4uential approach to the soft$are de&elopment that begins $ith
customer specification of re4uirements and progresses through planning, modeling,
construction, and deplo!ment.

Fig. 1 aterfall Proce!! "o#el
The $aterfall model is the oldest paradigm for soft$are engineeringI /o$e&er, o&er
the past three decades, criticism of this process model has caused e&en ardent
supporters to 4uestion its efficac!. Among the problems that are sometimes
encountered $hen the $aterfall model is applied areK
Feal pro.ects rarel! follo$ the se4uential flo$ that the model
proposes. Although the linear model can accommodate iteration, it
does so indirectl!. As a result, changes can cause confusion as the
pro.ect team proceeds.
It is often difficult for the customer to state all re4uirements e0plicitl!.
The *aterfall model re4uires this and has difficult! accommodating
the natural uncertaint! at e0ists the beginning of man! pro.ects.
The customer must ha&e patience. A $or)ing &ersion of the program
5s9 $ill not be a&ailable until late in the pro.ect time span. A ma.or
blunder, if undetected until the $or)ing program is re&ie$ed can be
disastrous.
,D
85358 )ncremental Process -o9elsE
There are man! situations in $hich initial soft$are re4uirements are
reasonabl! $ell defined, but the o&er all scope of the de&elopment effort pre&ent a
purel! linear process.
The incremental model combines elements of linear and parallel process
flo$s. The incremental model applies linear se4uences in staggered fashion as
calendar time processes. *hen an incremental model is used, the first increment is
often a core product.
That is, basic re4uirements are addressed but man! supplementar! features
remain undeli&ered. The core product is used b! the customer. As a result of use
and7or e&aluation, a plan is de&eloped.

Fig. 2 Incremental Proce!! "o#el!
The plan addresses the modification of the core product to better meet the
needs of the customer and the deli&er! of the additional features and functionalit!.
This process is repeated follo$ing the deli&er! of each increment, until the complete
product is produced.
,1
The increment process model focuses on deli&er! of an operational product
$ith each increment. 6arl! increments are strippeddo$n &ersions of the final
product, but the do pro&ide capabilit! that ser&es that user and also pro&ide platform
for the e&aluation b! the user.
Incremental de&elopment is particularl! useful $hen staffing is una&ailable
for a complete Implementation b! the business deadline that has been established for
the pro.ect. 6arl! increments can be implemented $ith fe$er people. If the core
product is $ell recei&ed then additional staff can be added to implement the ne0t
increment.
In addition, increments can be planned to manage technical ris)s I<or
e0ample, a ma.or s!stem might re4uire the a&ailabilit! of ne$ hard$are that is under
de&elopment and $hose deli&er! date is uncertain. It might be possible to plan earl!
increments in a $a! that a&oids the use of this hard$are, thereb! enabling partial
functionalit! to be deli&ered to end users $ithout inordinate dela!.
85353 E&olutionary Process -o9elsE
6&olutionar! models are iterati&e. The! are characteri:ed in a manner that
enables !ou to de&elop increasingl! more complete &ersions of the soft$are. There
are t$o commonl! e&olutionar! process models
Protot!ping
?piral Model
8535351 PrototypingE
-ften a customer defines a set of general ob.ecti&es of soft$are but does not
identif! detailed re4uirements for the functions and features. In other cases, the
de&eloper ma! be unsure of the efficienc! of an algorithm, the adapt abilit! of an
operating s!stem, or the form that human machine interaction should ta)e. In these,
and man! other situations, a protot!ping paradigm ma! offer the best approach.
Protot!ping iteration is planned 4uic)l!, and modeling occurs. A 4uic) design
focuses on the representation of those aspects of the soft$are that $ill be &isible to
end users.
,(

The 4uic) design leads to the construction of a protot!pe. The protot!pe is
de&eloped and e&aluated b! sta)eholders, $ho pro&ide feedbac) that is used to
further refine re4uirements.
8535358 (!e Spiral -o9elE
The spiral model is an e&olutionar! soft$are process model that couples the
iterati&e nature of protot!ping $ith the controlled and s!stematic aspects of the
$aterfall model. It pro&ides the potential for the rapid de&elopment of increasingl!
more complete &ersions of the soft$are.
The spiral de&elopment model is a ris) dri&en process model generator that is
used to guide multista)eholder concurrent engineering of the soft$are intensi&e
s!stems. It has t$o distinguishing features.
-ne is Cyclic approach for the incrementall! gro$ing a
s!stem=s degree of definition and implementation $hile
decreasing its degree of ris).
,+
The other is set of anc$or point mile!tone! for ensuring
sta)eholder commitment to feasible and mutuall! satisfactor!
s!stem solutions.
2sing the spiral model, soft$are is de&eloped in a series of e&olutionar!
releases. 8uring earl! iterations, the release might be a model or protot!pe. 8uring
later iterations, increasingl! more complete &ersions of the engineered s!stem are
produced.
(.+., Agile soft$are de&elopment Model
Agile soft$are de&elopment is a group of soft$are de&elopment
methodologies based on iterati&e and incremental de&elopment, $here re4uirements
and solutions e&ol&e through collaboration bet$een organi:ing, crossfunctional
teams. It promotes adapti&e planning, e&olutionar! de&elopment and deli&er!, a time
bo0ed iterati&e approach, and encourages rapid and fle0ible response to change. It is a
conceptual frame$or) that promotes foreseen interactions throughout the
de&elopment c!cle.
,,
8535451 C!aracteristicsE
There are man! specific agile de&elopment methods. Most promote de&elopment,
team$or), collaboration, and process adaptabilit! throughout the lifec!cle of the
pro.ect. Agile methods brea) tas)s into small increments $ith minimal planning and
do not directl! in&ol&e longterm planning.
Agile methods are sometimes characteri:ed as being at the opposite end of the
spectrum from plan dri&en or discipline methods. Agile teams ma!, ho$e&er, emplo!
highl! disciplined formal methods. A more accurate distinction is that methods e0ist
on a continuum from adapti&e to predicti&e. Agile methods lie on the adapti&e side of
this continuum.
8535= Scrum #e&elopment -o9el
?crum is an iterati&e, incremental frame$or) for pro.ect management often
seen in agile soft$are de&elopment, a t!pe of soft$are engineering. Although the
?crum approach $as originall! suggested for managing product
de&elopment pro.ects, its use has focused on the management of soft$are
de&elopment pro.ects, and it can be used to run soft$are maintenance teams or as a
general pro.ect7program management approach.
,3
Fig. % &crum #e'elopment mo#el
8535=51 C!aracteristicsE
?crum is a process s)eleton that contains sets of practices and predefined
roles. The main roles in ?crum areK
The M?crum MasterN, $ho maintains the processes 5t!picall! in
lieu of a pro.ect manager9
The MProduct -$nerN, $ho represents the sta)eholders and the
business
The MTeamN, a crossfunctional group $ho do the actual
anal!sis, design, implementation, testing, etc
85356 $H -o9elE
The 1model represents a soft$are de&elopment process 5also applicable to
hard$are de&elopment9 $hich ma! be considered an e0tension of the $aterfall
model. Instead of mo&ing do$n in a linear $a!, the process steps are bent up$ards
after the coding phase, to form the t!pical 1 shape. The 1Model demonstrates the
relationships bet$een each phase of the de&elopment life c!cle and its associated
phase of testing.
The hori:ontal and &ertical a0es represents time or pro.ect completeness 5left
toright9 and le&el of abstraction 5coarsestgrain abstraction uppermost9, respecti&el!.
,A
854 *#,P(E# -E(4,#,1,2)ES
<or energ! sa&ing, different tools and application are a&ailable that compute
o&erall energ! consumption and manage all calculation to displa! the efficienc! and
sa&ings. <or this purpose $e are designing a des)top application $ith named M6nerg!
Consumption CalculatorN, $hich $ill help the data centers to sa&e energ! and o&erall
cost !earl! basics or monthl! basics. This soft$are can be used for small data centers
as $ell as large data centers and it $ill help the data centers to reduce their electricit!
cost.
The features co&ered in this calculator $ill enable to administrator to
calculate Total Load a&ailable to IT e4uipment details i.e. ?er&ers, 'et$or)ing
64uipment, and 6n&ironment Control 64uipment. The goal of this pro.ect is to
calculate total 6nerg! 2sed b! IT 64uipment.
This $ill also help to Total 6lectricit! Cost calculation 5per month or !earl!
basis9 H 6nerg! sa&ing b! &irtuali:ation. %raphics Fepresentation of Po$er 2sage
6ffecti&eness 5P269 H 8ata Center Infrastructure 6fficienc! 58CI69 $ill add that
$ill reflect the impact of energ!. >ased upon this information this $ill enable to
administrator to ma)e comparison of energ! sa&ing.
85451 0aterfall Process -o9el
In the planning phase $e are using *aterfall process method for better
documentations and $or) planning. The $aterfall model is a model $hich $as
de&eloped for soft$are de&elopmentO that is to create soft$are. It is called as such
,B
because the model de&elops s!stematicall! from one phase to other in a do$n$ard
fashion, li)e a $aterfall.
As said earlier the $aterfall model has been structured on multiple phases
especiall! to help out the soft$are construction companies to de&elop an organi:ed
s!stem of construction. >! follo$ing this method, the pro.ect $ill be di&ided into
man! stages thus easing out the $hole process.
<or e0ample !ou start $ith PhaseI and according to this model, one onl!
progress to the ne0t Phase once the pre&ious one has been completed. This $a! one
mo&es progressi&el! to the final stage and once that point is reached, !ou cannot turn
bac)O similar to the $ater in a $aterfall.
8545151 #efinition Stu9yC*nalysisCRe>uirements
8uring this phase research is being conducted $hich includes brainstorming
about the soft$are, $hat it is going to be and $hat purpose is it going to fulfill.
2nless !ou )no$ $hat !ou are going to design, !ou cannot approach the problem.
/ere, the specifications of the output or the final product are studied and mar)ed. If
the soft$are that is going to be designed should not contain certain features, for
reasons li)e securit!, then it is also mentioned in this stage.
8545158 3asic #esignCSpecification P!ase
,E
If the first phase gets successfull! completed and a $ell thought out plan for
the soft$are de&elopment has been laid then the ne0t step in&ol&es formulating the
basic design of the soft$are on paper. *ith all the re4uirements and constraints in
hand, a final &ie$ of ho$ the product should e0actl! be, is decided. The e0act $a! in
$hich the soft$are should function is mentioned in this stage.
8545153 (ec!nical #esignC#etaile9 #esign
After 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 e0ample modules, programs etc.
8545154 ConstructionC)mplementation
In this phase the source code of the programs is $ritten. 'o$ starts the
coding part. /ere, the soft$are is designed as per the algorithm. /ence it becomes
&er! important that the algorithm should be properl! designed.
854515= (esting
At this phase, the $hole design and its construction is put under a test to
chec) its functionalit!. If there are an! errors then the! $ill surface at this point of the
process. The soft$are designed as per the algorithm needs to go through constant
soft$are testing and error correction processes to find out if there are an! fla$ or
errors. /ere the &arious codes designed b! different programmers are integrated and
is tested if the soft$are $or)s as per the specifications pro&ided.
8545156 )ntegration
In the phase of Integration, the compan! puts it in use after the s!stem has
been successfull! tested. The setup of the final soft$are $hich needs to be installed at
the clients s!stem is also designed and tested so that the client does not face an!
problem during the installation of the soft$are.
854515< -anagement an9 -aintenance
,C
Maintenance and management is needed to ensure that the s!stem $ill
continue to perform as desired. The $or) of soft$are de&elopment does not end $ith
the handing of the soft$are to the client. The soft$are designers ma! ha&e to
constantl! pro&ide support to the client to resol&e an! of the issues $hich ma! arise.
There ma! be some fla$s $hich get detected during the actual implementation of the
pro.ect. 8uring the maintenance phase, support and debugging is pro&ided for all
such problems.
85= RE*S,.S F,R C4,,S).2 -E(4,#,1,2)ES
In the &er! near future this $ill become clearer $ith our gro$ing data center
po$er and cooling capacit! issues, carbon regulations on the hori:on, and the
gro$ing importance of en&ironmental good$ill. In the near future, more and more
companies and consumers $ill insist on doing business $ith right companies $ho
share their en&ironmental concerns and $hich are ta)ing appropriate measures to
minimi:e their natural path.
There are a lot of reasons $hich forced me to de&elop a most efficient 6nerg!
Consumption calculator. 2ptime and redundanc! are &isibl! primar! concerns, but
too fe$ on either side are trac)ing ho$ much energ! their organi:ation uses in a !ear,
ho$ much it is costing their compan!, and ho$ much it is costing en&ironmentall!.
>ecause of the di&ide bet$een facilities and IT, some data center managers
donIt !et grip the significance of energ! costs in their data centers. -ur calculator
brings these e0penses to light and also 4uantifies the sa&ings possible through
efficienc! impro&ements.
*e are using $aterfall process method for the soft$are energ! consumption
calculator because of its $ide use in soft$are engineering. The $aterfall model is the
oldest and most $idel! used model in the field of soft$are de&elopment. There are
certain ad&antages of the $aterfall model, $hich causes it to be the most $idel! used
model as !et. ?ome of them can be listed as under.
3D
The pro.ect re4uires the fulfillment of one phase, before proceeding to the
ne0t. Therefore if there is a fault in this soft$are it $ill be detected during one
of the initial phases and $ill be sealed off for correction.
A lot of emphasis is laid on paper$or) in this method as compared to the
ne$er methods. *hen ne$ $or)ers enter the pro.ect, it is easier for them to
carr! on the $or) from $here it had been left. The ne$er methods don=t
document their de&elopmental process $hich ma)es it difficult for a ne$er
member of the team to understand $hat step is going to follo$ ne0t. The
*aterfall Model is a straight for$ard method and lets one )no$ easil! $hat
stage is in progress.
The *aterfall method is also $ell )no$n amongst the soft$are de&elopers
therefore it is eas! to use. It is easier to de&elop a lot of soft$are through this
method in short span of time$
-ne great ad&antage of the $aterfall model is that documentation is produced
at e&er! stage of the $aterfall model de&elopment. This ma)es the
understanding of the product designing procedure simpler.
856 0,R/ P1*.
85651 0or' Plan 9efinition
A $or) 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
$or), and defines the 4ualit! assurance for the program.
The pro.ect $or) plan is created along $ith the appropriate Pro.ect 8efinition.
It ma! seem ob&ious, but the $or) plan is a &ital tool to ensure that the pro.ect team
)no$s $hat the! need to do. Man! people are uncomfortable creating a $or) plan.
2suall! this is because the pro.ect has not been $ell defined.
85658 )mportance in Software Engineering
31
8efining and planning the pro.ect are not necessaril! a se4uential process.
#ou $ill often find that !ou cannot complete the Pro.ect 8efinition $ithout starting
to la! out the o&erall pro.ect $or) plan. In man! cases, these t$o deli&erables need to
be $or)ed on in parallel.
As !ou gather information around scope and deli&erables, !ou $ill need to
start la!ing out an o&erall timeline so that !ou can get !our hands around estimated
effort and duration. As !ou get more information, fill in more detail on the $or) plan.
85< PR,?EC( S(R%C(%RE
The main function of the pro.ect structure is to define standards the team $ill
use during the pro.ect. These include communication standards, documentation
standards, and change control procedure standards. Program Management ta)es the
lead in defining the pro.ect structure.
3(
85<51 (eam Structure
Apportionment of responsibilit! and authorit! among the members of an
organi:ation. <2'CTI-'AL -F%A'IPATI-', MATFIQ -F%A'IPATI-', and
line organi:ation are three common t!pes of organi:ational structure.
., Stu9ent )# .ame Responsi;ilities
1 MCDCD(D1,+A KA?/I< 'A866M
/e is information collector and
maintains and manages all basic
re4uirements. /e also participates in
basic design and architecture. /e is
responsible of basic coding and testing.
( MCDCD(DDCB( M. >ILAL K/A'
/e is senior code tester and he $ill guide
and communicate the other team
member. /e also participates in high
le&el design and architecture.
85<58 Project Sc!e9ule ASu;mission Calen9arB
In pro.ect management, a schedule consists of a list of a pro.ectIs terminal
elements $ith intended start and finish dates. Terminal elements are the lo$est
element in a schedule, $hich is not further subdi&ided. Those items are often
estimated in terms of resource re4uirements, budget and duration, lin)ed b!
dependencies and scheduled.
'- Phases 8eli&erables 8escription ?ubmission 8ate
1
%AT/6FI'% H
A'AL#PI'%
F6G2IF6M6'T
?F? 8ocument
8escribes the scope of
the pro.ect, functional
H nonfunctional
re4uirements, use case
diagram5s9, usage
scenarios
'o&ember (,, (D11
(
PLANNING
PHASE
Method & Work
Plan
Describes the
methodology &
schedle o! the "ro#ect
December $%&
$'((
+ ANAL)SIS AND
DESIGN PHASE
Design
Docment
Acti*ity Diagram&
Se+ence diagrams&
,anary %'& $'((
3+
I
Architectre Design
Diagram& D-D.s/ and
E0D i! the "ro#ect
domain re+ires
Design
Docment
II
1b#ect model &class
diagram& inter!ace
design& database design
i! the "ro#ect domain
re+ires database& test
cases& De"loyment
Diagram & 2om"onent
Diagram
March ($& $'($
,
-inal
Deli*erables
2ode
&
-INAL 0EP103
2om"lete Pro#ect
coding and !inal "ro#ect
re"ort
,ne (4& $'($
3,
C4*P(ER 3
8esigning the Pro.ect
33
351 ).(R,#%C(),.
In the 8esigning phaseD1, the purpose of this document is to present a
detailed description of logical designing b! using &arious design modelsO the design
document describes a plan to implement the re4uirements. This phase represents the
RRho$II phase. 8etails on computer programming languages and en&ironments,
machines, pac)ages, application architecture, distributed architecture la!ering,
memor! si:e, platform, algorithms, data structures, global t!pe definitions, interfaces,
and man! other engineering details are established.
The design ma! include the usage of e0isting components. It $ill e0plain
features of the 6CC, the interfaces of the 6CC, $hat the 6CC $ill do, the constraints
under $hich it must operate and ho$ the 6CC $ill react to e0ternal stimuli.
35151 ECC *nalysis
>efore entering in the topic of the anal!sis phase of the 6nerg! Consumption
Calculator let us start from the basic concept of, $hat is the pro.ect anal!sis phase
meanL The process of stud!ing the e0isting s!stem in detailed is called analy!i! of t$e
!y!tem. The e0isted s!stem is studied carefull! before designing the ne$ s!stem or to
modif! the e0isting s!stem. ?e&eral steps are in&ol&ed at anal!sis stage $hile
designing soft$are. In this phase, the current s!stem is studied in detail. A person
responsible for the anal!sis of the s!stem is )no$n as anal!st. In s!stem anal!sis, the
anal!st conducts the follo$ing acti&ities.
35158 *nalysis .ee9s
This acti&it! is )no$n as re4uirements anal!sis. In this step $e sum up the
re4uirements of the s!stem from the user and the managers. The de&eloped s!stem
should satisf! these re4uirements during testing phase. *e need to anal!sis the
e0isting calculators $hich are designed for the same purpose. In this $a! $e can get
)no$ledge to achie&e the goal of Energy Con!umption Calculator.
35153 Feasi;ility Stu9yE
The $orld feasibilit! means Mpossibilit!N. <easibilit! stud! is also called
preliminary in'e!tigation. In this step, the financial, political, technical, and time
3A
frame feasibilities for the soft$are are proposed. Actuall!, feasibilit! stud! is
conducted to find out $hether the proposed s!stem is possible to de&elop and
acceptable for the organi:ation. The ob.ecti&e of feasibilit! stud! is to e&aluate
different solutions and to propose the most feasible and least e0pensi&e solution. This
step is most important in designing phase of MEnergy Con!umption Calculator.
35154 #ata 2at!ering
In this step, $e collect data about the s!stem 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 follo$ing $a!s these areK
3515451 0riting #ocuments
*e ma! collect the information7data from $ritten documents a&ailable
from manualfiles of an organi:ation. This method of data gathering is
normall! used if $e $ant to computeri:e the e0isting manual s!stem or
upgrade the e0isting computer based s!stem. The $ritten documents ma! be
reports, forms, memos, business plans, polic! statements, organi:ational
charts and man! others. The $ritten documents pro&ide &aluable information
about the e0isting s!stem.
3515458 )nter&iews
Inter&ie$ is another data gathering techni4ue. *e can inter&ie$s, managers,
users7 clients, suppliers, and competitors to collect the information about the
s!stem. It must be noted that the 4uestions to be as)ed from them should be
precise, rele&ant and to the point in this $a! $e can collect precise data for
Energy Con!umption Calculator.
3515453 Guestionnaires
Guestionnaires are the feedbac) forms used to collect Information.
The inter&ie$ techni4ue to collect information is timeconsuming method, so
Guestionnaires are designed to collect information from as man! people as $e
li)e. It is &er! con&enient and ine0pensi&e method to collect information but
sometimes the response ma! be Confusing or unclear and insufficient.
3B
3515454 ,;ser&ations
In addition to the abo&ementioned three techni4ues to collect
information, the anal!st 5or his team9 ma! collect Information through
obser&ation. In this collect techni4ue, the $or)ing, beha&ior, and other related
information of the e0isting s!stem are obser&ed. It means that $or)ing of
e0isting s!stem is $atched carefull!.
351545= Sampling
If there are large numbers of people or e&ents in&ol&ed in the s!stem,
$e can use sampling method to collect information. In this method, onl! a
part of the people or e&ents in&ol&ed are used to collect information. <or
e0ample to test the 4ualit! of a fruit, $e test a piece of the fruit.
3515456 #ata *nalysis
After completion of 8ata %athering step the collected data about the
s!stem is anal!:ed to ensure that the data is accurate and complete. <or this
purpose, &arious tools ma! be used. The most popular and commonl! tools,
$hich $e are going to be used for data anal!sis, areK
8<8s 58ata <lo$ 8iagrams9
6F8s 56ntit! Felationship 8iagrams9
Acti&it! 8iagrams
?e4uence 8iagrams
Architectural 8esign 8iagrams

351545< *nalysis Report
After completing the $or) of anal!sis, the re4uirements collected for
the s!stem are documented in a presentable form. It means that the anal!sis
report is prepared. It is done for re&ie$ and appro&al of the pro.ect from the
higher management. This report should ha&e three parts.
First" it should e0plain ho$ the current s!stem $or)s.
3E
Secon9, it should e0plain the problems in the e0isting s!stem.
Finally" it should describe the re4uirements for the ne$ s!stem and
ma)e recommendations for future.
Anal!:ing the tradeoffs of necessar! comple0it! allo$s for man! things to
remain simple $hich, in turn, $ill e&entuall! lead to a higher 4ualit! product. The
architecture team also con&erts the t!pical scenarios into a test plan.
In our approach, the team, gi&en a complete re4uirement document, must also
indicate critical priorities for the implementation team. A critical implementation
priorit! leads to a tas) that has to be done right. If it fails, the product fails. If it
succeeds, the product might succeed. At the &er! least, the confidence le&el of the
team producing a successful product $ill increase. This $ill )eep the implementation
team focused. 60actl! ho$ this information is con&e!ed is a s)ill based on e0perience
more than a science based on fundamental foundations.
3515= )ntro9uction to #esign P!ase
In s!stems design the design functions and operations are described in detail,
including screen la!outs, business rules, process diagrams and other documentation.
The output of this stage $ill describe the ne$ s!stem as a collection of modules or
subs!stems. The design stage ta)es as its initial input the re4uirements identified in
the appro&ed re4uirements document. <or each re4uirement, a set of one or more
design elements $ill be produced as a result of inter&ie$s, $or)shops, and7or
protot!pe efforts.
8esign elements describe the desired soft$are features in detail, and generall!
include functional hierarch! diagrams, screen la!out diagrams, tables of business
rules, business process diagrams, pseudo code, and a complete entit!relationship
diagram $ith a full data dictionar!. These design elements are intended to describe
the soft$are in sufficient detail that s)illed programmers ma! de&elop the soft$are
$ith minimal additional input design.
In the 8esigning phase of 6nerg! consumption calculator, it is &er! important
to stud! the e0isting s!stem. Actuall! in this step, it is necessar! to ta)e all
preliminar! in&estigations of e0isting s!stem. There are man! calculators a&ailable
3C
for calculating energ! consumption $ith a lot number of ad&antages but it is noticed
that all ha&e separate ad&antages. There $ill be soft$are that $ill pro&ide all in one
feature
358 P%RP,SE
The features co&ered in this calculator $ill enable to administrator to calculate
Total Load a&ailable to IT e4uipment details i.e. ?er&ers, 'et$or)ing 64uipment, and
6n&ironment Control 64uipment. The goal of this pro.ect is to calculate total 6nerg!
2sed b! IT 64uipment.
This $ill also help to Total 6lectricit! Cost calculation 5per month or !earl!
basis9 H 6nerg! sa&ing b! &irtuali:ation. %raphics Fepresentation of Po$er 2sage
6ffecti&eness 5P269 H 8ata Center Infrastructure 6fficienc! 58CI69 $ill add that
$ill reflect the impact of energ!. >ased upon this information this $ill enable to
administrator to ma)e comparison of energ! sa&ing.
<or energ! sa&ing, different tools and application are a&ailable that compute
o&erall energ! consumption and manage all calculation to displa! the efficienc! and
sa&ings. <or this purpose $e are designing a des)top application $ith named M6nerg!
Consumption CalculatorN, $hich $ill help the data centers to sa&e energ! and o&erall
cost !earl! basics or monthl! basics. This soft$are can be used for small data centers
as $ell as large data centers and it $ill help the data centers to reduce their electricit!
cost.
In the &er! near future this $ill become clearer $ith our gro$ing data center
po$er and cooling capacit! issues, carbon regulations on the hori:on, and the
gro$ing importance of en&ironmental good$ill. In the near future, more and more
companies and consumers $ill insist on doing business $ith right companies $ho
share their en&ironmental concerns and $hich are ta)ing appropriate measures to
minimi:e their natural path.
There are a lot of reasons $hich forced me to de&elop a most efficient 6nerg!
Consumption calculator. 2ptime and redundanc! are &isibl! primar! concerns, but
AD
too fe$ on either side are trac)ing ho$ much energ! their organi:ation uses in a !ear,
ho$ much it is costing their compan!, and ho$ much it is costing en&ironmentall!.
>ecause of the di&ide bet$een facilities and IT, some data center managers
donIt !et grip the significance of energ! costs in their data centers. -ur calculator
brings these e0penses to light and also 4uantifies the sa&ings possible through
efficienc! impro&ements.
353 SC,PE
The 8esign phase is $hen $e build the plan for ho$ $e $ill ta)e our pro.ect
through the rest of the ?8L process from implementation, to &erification, to release.
8uring the 8esign phase $e establish best practices to follo$ for this document b!
$a! of functional and design specifications, and $e perform ris) anal!sis to identif!
threats and &ulnerabilities in !our soft$are.
*e need to demonstrate the ph!sical $or)ing of 6nerg! Consumption
Calculator. All implementations and test cases are applied to it. In this document $e
are going to end the designing phase and be sure that our soft$are $ill $or) properl!.
The design document S II ma! include the usage of presented method. It $ill
e0plain features of the 6CC, the interfaces of the 6CC, $hat the 6CC $ill do, the
constraints under $hich it must operate and ho$ the 6CC $ill react to e0ternal
stimuli. >! using different diagrams $e $ill describe the process and $or)ing of
6nerg! Consumption Calculator.
In this 8esign phase, $e are describing some illustration for 6nerg!
Consumption Calculator. *e e0press class diagram that describes the structure of a
s!stem b! sho$ing the s!stemIs classes, their attributes, operations 5or methods9, and
the relationships among the classes. To e0press in detailed $e describing 8atabase
8iagram, 8atabase design is the process of producing a detailed data model of
a database. The term database design can be used to describe man! different parts of
the design of an o&erall database s!stem.
A1
*e are using Interface design $hich deals $ith the process of de&eloping a
method for t$o 5or more9 modules in our Calculator to connect and communicate.
These modules can appl! to hard$are, soft$are or the interface bet$een a user and a
machine. An e0ample of a user interface could include a %2I, a control panel for a
nuclear po$er plant, or e&en the coc)pit of an aircraft. In s!stems engineering, all the
inputs and outputs of a s!stem, subs!stem, and its components are listed in
an interface control document often as part of the re4uirements of the engineering
pro.ect. The de&elopment of a user interface is a uni4ue field.
>! using deplo!ment diagram $e can specif! a set of constructs that can be
used to define the e0ecution architecture of our calculator that represent the
assignment of soft$are artifacts to nodes. In the test case $e test our 6nerg!
Consumption Calculator to meet all re4uirements mention in ?F? S 8ocument. In
this $a! $e can chec) all use case scenarios.
354 *RC4)(EC(%R*1 PRESE.(*(),.
35451 *rc!itecture #esign #iagram #efinitionE
Architecture diagrams displa! the organi:ation of architecture and their
elements, as $ell as corresponding namespaces. Architecture diagrams are t!picall!
used to depict the highle&el organi:ation of a soft$are pro.ect. Architecture design
diagrams e0press the $hole process of the s!stem in the form of real life ob.ects and
components that are used in the soft$are.
35458 *rc!itecture #esign #iagram )nstructionsE
?oft$are architecture is commonl! defined in terms of structural elements and
relationships. ?tructural elements are identified and assigned responsibilities that
client elements interact $ith through JcontractedJ interfaces. ?oft$are architecture
must be distinguished from lo$erle&el design 5e.g., design of component internals
and algorithms9 and implementation, on the one hand, and other )inds of related
architectures, on the other.
<or instance, soft$are architecture is not the information 5or data9 model,
though it uses the information model to get t!pe information for method signatures on
A(
interfaces, for e0ample. It is also not the architecture of the ph!sical s!stem, including
processors, net$or)s, and the li)e, on $hich the soft$are $ill run.
35453 *rc!itecture #esign #iagram of Energy Consumption
CalculatorE
35= #6.*-)C -,#E1).2 ASEG%E.CE #)*2R*-B
35=51 Se>uence #iagram #efinition
A se4uence diagram is a t!pe of interaction diagram that highlights the
interdependencies bet$een messages. A se4uence diagram sho$s, as parallel &ertical
lines, different processes or ob.ects that li&e simultaneousl!, and, as hori:ontal
arro$s, the messages e0changed bet$een them, in the order in $hich the! occur. This
allo$s the specification of simple runtime scenarios in a graphical manner. ?e4uence
diagrams are sometimes called e&ent diagrams, e&ent scenarios, and timing diagrams.
35=58 Se>uence #iagram )nstructions
A+
2ML se4uence diagrams model the flo$ of logic $ithin !our s!stem in a
&isual manner, enabling !ou both to document and &alidate !our logic, and are
commonl! used for both anal!sis and design purposes. ?e4uence diagrams are the
most popular 2ML artifact for d!namic modeling, $hich focuses on identif!ing the
beha&ior $ithin !our s!stem.
In ?e4uence diagram, An action initiator is used.
This s!mbol mar)s the ob.ect that initiates the
message.
In ?e4uence diagram. An action duration s!mbol is
used. 8uration notations indicate the length of time
needed to complete a tas).
In se4uence diagram, 2se arro$s or lines to
represent communication bet$een ob.ects. 2se
halfarro$ed lines to represent as!nchronous
messages. As!nchronous messages are sent from an
ob.ect that $ill not $ait for a response from the
recei&er before continuing its tas)s.
35=53 Se>uence #iagram of Energy Consumption Calculator
35=54 P%E an9 #CiE Calculation
A,
35=5= 3ill Energy Sa&ing Calculation
Fig. (% &equence Diagram of )ill an# Energy &a'ing Calculation
35=56 2rap!ical Representation
A3
Fig. (* &equence Diagram of +rap$ical repre!entation
356 ,3?EC(C1,2)C*1 -,#E1 AC1*SS #)*2R*-B
35651 Class #iagram #escription
The class diagram is the main building bloc) of ob.ect oriented modeling.
Class diagrams can also be used for data modeling. The classes in a class diagram
represent both the main ob.ects and or interactions in the application and the ob.ects
to be programmed. In a class diagram, the classes are arranged in groups that share
common characteristics.
A class diagram resembles a flo$chart in $hich classes are portra!ed as
bo0es, each bo0 ha&ing three rectangles inside. The top rectangle contains the name
of the classO the middle rectangle contains the attributes of the classO the lo$er
rectangle contains the methods, also called operations, of the class. Lines, $hich ma!
ha&e arro$s at one or both ends, connect the bo0es. These lines define the
relationships, also called associations, bet$een the classes.
35658 Class #iagram of Energy Consumption Calculator
AA
In the Class 8iagram of 6nerg! Consumption Calculator $e need to ma)e all
class of all entities in&ol&ed in the s!stem. In e&er! class each entit! has its o$n
attributes and functions $hich better e0press the $or)ing of 6nerg! Consumption
Calculator.
In Class 8iagram $e also need to represent relationships among all entities
$hich describe interaction of each entit! $ith other entit! or entities.
35< #EP1,6-E.( -,#E1
35<51 #eployment #iagram #escription
The deplo!ment diagram specifies a set of constructs that can be used to
define the e0ecution architecture of s!stems that represent the assignment of soft$are
artifacts to nodes. 'odes are connected through communication paths to create
net$or) s!stems of arbitrar! comple0it!.
'odes are t!picall! defined in a nested manner, and represent either hard$are
de&ices or soft$are e0ecution en&ironments. Artifacts represent concrete elements in
the ph!sical $orld that are the result of a de&elopment process. 8eplo!ment diagrams
AB
sho$ a s!stemIs ph!sical la!out, re&ealing $hich pieces of soft$are run on $hat
pieces of hard$are.
35<58 #eployment #iagram of Energy Consumption Calculator
358 #*(*3*SE -,#E1A#*(*3*SE #)*2R*-B
35851 #ata;ase #esign #escription
8atabase design is the process of producing a detailed data model of
a database. This logical data model contains all the needed logical and ph!sical
design choices and ph!sical storage parameters needed to generate a design in a 8ata
8efinition Language, $hich can then be used to create a database. A full! attributed
data model contains detailed attributes for each entit!.
The term database design can be used to describe man! different parts of the
design of an o&erall database s!stem. Principall!, and most correctl!, it can be
thought of as the logical design of the base data structures used to store the data. In
the relational model these are that tables and &ie$s.
35858 #ata;ase #esign of Energy Consumption Calculator
AE
359 2R*P4)C*1 %SER ).(ERF*CE
35951 )nterface #esign #escription
An interface enables a user to interact $ith a s!stem to perform a tas).
Interface design has &er! important role in soft$are engineering. ?ometimes users
.udge s!stem b! its interface rather than its functionalit! so $e can sa! that poorl!
designed interface can cause a user to ma)e catastrophic errors.
8ue to poor user interface man! soft$are are ne&er used. >ecause most users
interact $ith s!stem through graphical user interface although, in some cases, legac!
te0tbased interfaces are still used. ?o in this document $e use some good loo)ing
interface to attract the attention of the user.

AC
35958 )nterface #esign of Energy Consumption Calculator
35953 )nput 2%) APreH$irtualiDationB
In this %2I user or administrator can input all &alues.
35954 )nput 2%) APostH$irtualiDationB
BD
In this %2I partition user or administrator enters &irtuali:ed IT
64uipments.
3595= ,utput 2%) AResultsB
In the gi&en partition of output %2I user can get resulted &alue.
35956 )mpact on 3ill A2rap!ical representationB
In this partition of %2I user can get graphical representation of
mentioned &alues li)e as P26 H 8Ci6 as $ell as Impact on >ill.
B1
3595< ,utput 2%) AP%E #CiE 2rap!B
If user Clic) on %raph button MP26 H 8Ci6N follo$ing graph
representation $ill displa!.
35958 2%) !elping 4).(S
/elping /ints is &er! important feature of our 6nerg! consumption
Calculator. It $ill guide user or Administrator to input proper &alues.
Abo&e graphic s!mbol is represented for each input case and if user $ants to
see $hat is Total IT Load he .ust put mouse courser on the helping hint icon and
follo$ing guideline $ill displa!.
B(
C4*P(ER 4
8e&elopment
B+
45@ #E$E1,P-E.( ).(R,#%C(),.
8e&elopment is a comple0 issue, $ith man! different and sometimes
contentious definitions. A basic perspecti&e e4uates de&elopment $ith economic
gro$th. The 2nited 'ations 8e&elopment Program uses a more detailed definition
according to them de&elopment is Ito lead long and health! li&es, to be
)no$ledgeable, 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 communit!.I
Achie&ing human de&elopment is lin)ed to a third perspecti&e of de&elopment
$hich &ie$s it as freeing people from obstacles that affect their abilit! to de&elop
their o$n li&es and communities. 8e&elopment, therefore, is empo$ermentK it is
about local people ta)ing control of their o$n li&es, e0pressing their o$n demands
and finding their o$n solutions to their problems.
451 #E$E1,P-E.( P1*. A*RC4)(EC(%RE
#)*2R*-B
Architecture diagrams displa! the organi:ation of architecture and their
elements, as $ell as corresponding namespaces. Architecture diagrams are t!picall!
used to depict the highle&el organi:ation of a soft$are pro.ect. Architecture design
diagrams e0press the $hole process of the s!stem in the form of real life ob.ects and
components that are used in the soft$are.
45151 *rc!itecture #esign #iagram )nstructionsE
?oft$are architecture is commonl! defined in terms of structural elements and
relationships. ?tructural elements are identified and assigned responsibilities that
client elements interact $ith through JcontractedJ interfaces. ?oft$are architecture
B,
must be distinguished from lo$erle&el design 5e.g., design of component internals
and algorithms9 and implementation, on the one hand, and other )inds of related
architectures, on the other.
<or instance, soft$are architecture is not the information 5or data9 model,
though it uses the information model to get t!pe information for method signatures on
interfaces, for e0ample. It is also not the architecture of the ph!sical s!stem, including
processors, net$or)s, and the li)e, on $hich the soft$are $ill run.
45158 *rc!itecture #esign #iagram of Energy
Consumption CalculatorE
B3
C4*P(ER =
8eplo!ment
BA
=5@ #EP1,6-E.( ).(R,#%C(),.
To deplo! 5from the <rench #eplorer9 is Jto spread out or arrange
strategicall!.J Long used in the conte0t of militar! strateg!, it has no$ gained
currenc! in information technolog!. In its IT conte0t, deplo!ment encompasses all
the processes in&ol&ed in getting ne$ soft$are or hard$are up and running properl!
in its en&ironment, including installation, configuration, running, testing, and ma)ing
necessar! changes. The $ord implementation is sometimes used to mean the same
thing.
=51 #EP1,6-E.( P1*.
=5151 #eployment PlanC#eployment #iagram
)nstructions
The deplo!ment diagram specifies a set of constructs that can be used
to define the e0ecution architecture of s!stems that represent the assignment
of soft$are artifacts to nodes. 'odes are connected through communication
paths to create net$or) s!stems of arbitrar! comple0it!.
'odes are t!picall! defined in a nested manner, and represent either
hard$are de&ices or soft$are e0ecution en&ironments. Artifacts represent
concrete elements in the ph!sical $orld that are the result of a de&elopment
process. 8eplo!ment diagrams sho$ a s!stemIs ph!sical la!out, re&ealing
$hich pieces of soft$are run on $hat pieces of hard$are.
=5158 *rc!itecture #esign #iagram of Energy
Consumption CalculatorE
BB
BE
REFERE.CES
6nerg! Consumption Calculator basic concepts
httpK77$$$.,(u.com7efficienc!7energ!efficienc!calculator.htm
P2678Ci6 basic concepts
httpK77$$$.,(u.com7measurement7puedcie.htm
Calculating Total Po$er Fe4uirements for 8ata Centers 5b! Fichard L. ?a$!er9
$$$.apcmedia.com7salestools71A1F3T8T6<TF1T6'.pdf
Ph!sical $or)ing concepts of 6nerg! Consumption Calculator
httpK77$$$.apcmedia.com7salestools7*T-LBCM%PLTF+T6'.s$f
%2I concepts of 6nerg! Consumption Calculator
httpK77$$$.apcmedia.com7salestools7*T-LB>A?<CTFDT6'.s$f
8esign Phase Concepts
$$$.smartdra$.com
8esign Phase Concepts
httpK77$$$.edra$soft.com72ML8iagrams.php
*or) Plan guidance
httpK77$$$.mhhe.com7ma!fieldpub7ts$7$or)plan.htm
BC